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: Error: -5081: Could not write to setup.ini
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
‎Mar 18, 2009
08:03 PM
Error: -5081: Could not write to setup.ini
Any one had this error message??? I am using a basic MSI... :mad:
I have changed my release location suggested in the support site. What else can I do? What is this error message?
I have changed my release location suggested in the support site. What else can I do? What is this error message?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 18, 2009
08:20 PM
http://community.acresso.com/showthread.php?p=430944 - I reported the message here as well, this time, I can not restart the project. Its too time consuming.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 19, 2009
11:49 AM
The error is exactly what it says - a problem writing to the setup.ini file, and it looks like it can only come from a failure writing to the file. Unfortunately this occurs in a helper method that could be called from one of many different places. I assume it's an early call, though, as it's unlikely to suddenly start failing partway through the build. Here's some steps you can try to debug it yourself:
- Build using iscmdbld /v in order to receive verbose build messages. This may help track down exactly when it is occurring.
- Use a tool like ProcessMonitor to see what error is being returned for what file location (probably ending in setup.ini), and whether previous accesses succeeded.
- If you can reproduce this error building in a stripped down environment containing none of your source files, I can try to reproduce this with your ISM (if you can email it to me).
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)