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 Knowledge Base
- :
- Installer Failing To Install Website On Some Machines
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Installer Failing To Install Website On Some Machines
Installer Failing To Install Website On Some Machines
Summary
This article presents some information on a possible error when installing a websiteSymptoms
Using a Basic MSI project to install a website, the installation may work on multiple machines, but an installation error will occur on multiple machines as well. This knowledge base article will go over one possible cause for the installation error.Cause
If you generate an MSI log of the failing installation, you may see the following recorded entries...InstallShield 16:51:06: CommitChanges for path 'MACHINE/WEBROOT/APPHOST/TestWebService' and physical path 'C:\wwwroot\Web_Services\TestWebService\'. InstallShield 16:51:06: CommitChanges failed with the following HRESULT: '-2147024891'. InstallShield 16:51:06: Error with IISRT: -2147024891 CustomAction ISIISInstall returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
The above describes the error as CommitChanges failing with HRESULT: '-2147024891'. This error result resolves to ERROR_ACCESS_DENIED and so you may want to look into the user rights, as well as being able to access the physical path listed in the MSI log. Lastly you may want to check the permissions on the 'web.config' file on the system and make sure it is not read-only.
Resolution
Try the following and it should resolve any access errors. You can check...* The user account running the installation should have administrative rights.
* User has access to the physical path listed in the MSI log.
* The 'web.config' file permissions are not set to read only.
Additional Information
You can look at knowledge base article Logging an MSI Installation for more information on how to generate a MSI log file.
No ratings