This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Vista install; setup.exe works, msi fails
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 22, 2008
07:43 AM
Vista install; setup.exe works, msi fails
I have a package that builds as a simple msi project and the output is a msi file and a single setup.exe. It installs a service, filter driver, and a number of executable and support files. Admin privileges are a prerequisite. The setup.exe works fine. The msi works as long as it is run msiexec /i from a command window started with admin privileges. If it is not started from an elevated source, it fails because it calls a dll that attempts to open the service control manager. Cause of failure is lack of privileges (error 5).
Both the msi and the setup.exe are built at the same time with the same properties. As I understand it, the setup.exe is just a wrapper that launches msiexec. The privileges on both packages are the same. Any ideas on why this is happening would be immensely appreciated.
Thanks.
Both the msi and the setup.exe are built at the same time with the same properties. As I understand it, the setup.exe is just a wrapper that launches msiexec. The privileges on both packages are the same. Any ideas on why this is happening would be immensely appreciated.
Thanks.
(2) Replies
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 26, 2008
12:25 PM
MSI Packages don't have a manifest file streamed in to them like setup.exe files do, so cannot indicate from what point privileges should be prompted.
Therefore, the only full resolution is to either require setup.exe or refactor your installation to not perform activities that require administrative context when that might not be available.
Therefore, the only full resolution is to either require setup.exe or refactor your installation to not perform activities that require administrative context when that might not be available.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 28, 2008
07:40 AM
I have a similar problem: I populate a combobox with available websites. Websites are read in CA VB script with the help of GetObject("IIS:..."). The latest statement just fails if the installation is run from .msi. I do not have a work around for this and I need to fix this. Any ideas?