MSI Install Problems over UNC Share
-
Hi All, I have a shared folder on an SBS2003 Server. The folder contains an MSI, and the permissions on the folder give Everyone & Guest full access. Whenever a user attempts to double click the MSI via the share (\\Server\Share1\folder\App.msi) Windows Installer pops up the following message "The Installation package could not be opened. Verify the package exists..." and the Event ID is: 11708 Install Operation Failed. However, if a user maps a drive - such as Z:\ - and runs the msi, installation works fine. I'm not sure what the problem here is... anyone got any ideas? Thanks, Martin.
-
Hi All, I have a shared folder on an SBS2003 Server. The folder contains an MSI, and the permissions on the folder give Everyone & Guest full access. Whenever a user attempts to double click the MSI via the share (\\Server\Share1\folder\App.msi) Windows Installer pops up the following message "The Installation package could not be opened. Verify the package exists..." and the Event ID is: 11708 Install Operation Failed. However, if a user maps a drive - such as Z:\ - and runs the msi, installation works fine. I'm not sure what the problem here is... anyone got any ideas? Thanks, Martin.
Hey, there are two possibilities as far as I can tell ... 1. the windows installer package, when run from the shared folder, does not know how to parse its own 'home address' and thus tells you that it doesn't exist... In this case I think that your only solution is to have your users map the network drive in order to access the software. 2. it's also possible that, since users enter a username and password (I'm supposing they are) when mapping the network drive, they are getting different permissions to the file than when they access the share. You should make sure that users are not accessing the shared folder as a 'guest' or 'anonymous' user. Also, you might want to check your permissions to make sure that "Eeveryone" and "Guest" have the "Execute" box checked off, as sometimes "Full Access" still leaves "execute" disabled. I'm sorry that I can't be of any more help, good luck! Akseli A.
-
Hey, there are two possibilities as far as I can tell ... 1. the windows installer package, when run from the shared folder, does not know how to parse its own 'home address' and thus tells you that it doesn't exist... In this case I think that your only solution is to have your users map the network drive in order to access the software. 2. it's also possible that, since users enter a username and password (I'm supposing they are) when mapping the network drive, they are getting different permissions to the file than when they access the share. You should make sure that users are not accessing the shared folder as a 'guest' or 'anonymous' user. Also, you might want to check your permissions to make sure that "Eeveryone" and "Guest" have the "Execute" box checked off, as sometimes "Full Access" still leaves "execute" disabled. I'm sorry that I can't be of any more help, good luck! Akseli A.
Hi Akseli, Thanks for the suggestions -
akseli wrote:
the windows installer package, when run from the shared folder, does not know how to parse its own 'home address' and thus tells you that it doesn't exist... In this case I think that your only solution is to have your users map the network drive in order to access the software.
I think you may be on to something here - I think the developer is using an old version of the package tool (VB 6 or earlier), I shall have a go at using a more recent version of the tool. Thanks, Martin.