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
- :
- error opening log file (1622) after reboot on 2008
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
Jan 20, 2011
10:18 AM
error opening log file (1622) after reboot on 2008
Hi all,
I have an msi project with a setup.exe wrapper that requires a reboot in the middle of the install. This works fine on Server 2003. On 2008, I'm getting this error:
"There was an error opening installation log file. Verify that the specified log file location exists and is writable."
Msiexec bails at that point and the user finishes logging in. My best guess is that since the msi is not being launched by setup.exe after the reboot, it isn't running with administrative rights. I tried adding "runas /user:administrator" to the runonce entry before it reboots, but apparently the msi changes it back again after you click "Yes" to allow it to reboot.
Even if I get the log file working, the installation performs other actions that will probably need admin rights. Does anyone have a suggestion for how to get around this?
Jim
I have an msi project with a setup.exe wrapper that requires a reboot in the middle of the install. This works fine on Server 2003. On 2008, I'm getting this error:
"There was an error opening installation log file. Verify that the specified log file location exists and is writable."
Msiexec bails at that point and the user finishes logging in. My best guess is that since the msi is not being launched by setup.exe after the reboot, it isn't running with administrative rights. I tried adding "runas /user:administrator" to the runonce entry before it reboots, but apparently the msi changes it back again after you click "Yes" to allow it to reboot.
Even if I get the log file working, the installation performs other actions that will probably need admin rights. Does anyone have a suggestion for how to get around this?
Jim
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 02, 2011
08:30 AM
I found a solution to this. Caching the install locally fixed it.
When I turned off the default logging available in later versions of Windows Installer, it complained about not even being able to find the msi. Caching locally fixed this also.
Hope this helps someone.
When I turned off the default logging available in later versions of Windows Installer, it complained about not even being able to find the msi. Caching locally fixed this also.
Hope this helps someone.