I'm wondering if anyone has come across this before and can offer any advice.

As part of my installer, we write a folder and a shortcut within that folder to PersonalFolder, which usually maps to "My Documents". I'm getting a report from a customer that the installation is failing with the error:

"An error occurred while attempting to create the directory: \\<server>\public\homedrives".

(I've replaced some machine and folder names with stuff in <>. Just assume anything in <> is an irrelevant name).

I asked for a log file, and this is what it says:

MSI (s) (3C:F0) [18:22:43:772]: Executing op: SetTargetFolder(Folder=\\<server>\public\homedrives\<user>\My Folder\)
MSI (s) (3C:F0) [18:22:43:772]: Executing op: ShortcutCreate(Name=Predefin.bui|Predefined Stuff,,,FileName=C:\Program Files\<InstallDir>\gallery\,,,,,,,)
CreateShortcuts: Shortcut: Predefin.bui|Predefined Stuff
MSI (s) (3C:F0) [18:22:43:788]: Note: 1: 1317 2: \\<server>\public\homedrives
MSI (s) (3C:F0) [18:22:43:788]: Note: 1: 2205 2: 3: Error
MSI (s) (3C:F0) [18:22:43:788]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1317
Error 1317. An error occurred while attempting to create the directory: \\<server>\public\homedrives

So it looks like the installer is trying to create the directory "homedrives", but it doesn't have permission...I've confirmed that \\<server>\public\homedrives\<user> exists and is writable by the user.

Other information that may be useful: The following environment variables are set:


He has the home directory mounted to H:\. The operating system is Windows XP SP3.

The worst part is that the installer errors on this and doesn't complete, so we can't get the thing installed. Does anyone know why he is getting this error and what we can do to fix it, or at least what we can do to work around it so that I can get the thing installed.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Is your client installing from the command line or via some deployment system? If the latter, it's almost certain that it will be using the local System account which by default has no network access.
Answered 06/01/2011 by: VBScab
Red Belt

Please log in to comment
Check your deployment contex. May be you are installing package under SYSTEM contex. But "\\<server>\public\homedrives\<user>" can be accessable only for User (modify permissions).
1) Ask customer to give you permissions list for this folder.
2) Recomend to try to install package with "Iteract with user contex" option.
Answered 06/01/2011 by: itolutions
Purple Belt

Please log in to comment
Thanks for the replies. They are installing from the command line and invoking the installer as the current user. Does the installer switch to using the SYSTEM account when doing the actual installation? How can I run an MSI installer with the "Interact with user context" option?

He has sent me a screenshot of the permissions on that folder, and it looks like "SYSTEM" has Full Control on that folder...
Answered 06/01/2011 by: garnold54
Yellow Belt

Please log in to comment
"Interact with user context" is option for deployment system. You are using manual instllation...

1) if you use Windows 7/Vista try elevated mode (right click on cmd.exe => run as administrator).
2) Try to create "H:\My Folder" folder instead of "\\<server>\public\homedrives\<user>\My Folder\"
Answered 06/01/2011 by: itolutions
Purple Belt

Please log in to comment
it looks like "SYSTEM" has Full Control on that folder.Yes, but that will be the System account on the box hosting the folder, not the System account of the machine you're installing to. In any event, you've already told us that they're installing from the command line and using the currently logged-in user account. I *hope* that that account is a local administrator account and NOT that their ordinary users have administrator privileges (although that's not your problem, of course...)

When they're logged in, can they create the folder from the command line? Obviously, they'll need to use a mapped drive, as DOS doesn't understand UNC. It might be that the users have Modify rights but not Create rights. Also, if they're using a local administrator account, does THAT account have permissions to create the folder. Unlikely, in my view...
Answered 06/02/2011 by: VBScab
Red Belt

Please log in to comment