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 27519. Error updating XML file ...\web.config -2147024891
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jan 14, 2011
11:11 AM
Error 27519. Error updating XML file ...\web.config -2147024891
We've recently started to see an error in a previously* fine IS2008 built installer similar to the following:
Error 27519. Error updating XML file ...\web.config -2147024891
The XML step is writing a database string to the web.config file, and as I say, it's been fine. It's an installscript project, and the sources are definitely read/write (ie. read only is not checked). If built without compression, the sources in the installer disk are the same - read/write. However once the installer is run, they're written to the local website with the read only flag checked.
I've tried running this as a compiled installer as somebody suggested but it exhibits the same behaviour. I've also added the "SetAttributesNormal" function, which is called in OnInstallFilesActionBefore() to set the directory (and content) properties to normal. No luck. Have I got the right place in the sequence? And where is the read only flag coming from?
*The last time we ran this in anger will have been at least 12 months ago.
Error 27519. Error updating XML file ...\web.config -2147024891
The XML step is writing a database string to the web.config file, and as I say, it's been fine. It's an installscript project, and the sources are definitely read/write (ie. read only is not checked). If built without compression, the sources in the installer disk are the same - read/write. However once the installer is run, they're written to the local website with the read only flag checked.
I've tried running this as a compiled installer as somebody suggested but it exhibits the same behaviour. I've also added the "SetAttributesNormal" function, which is called in OnInstallFilesActionBefore() to set the directory (and content) properties to normal. No luck. Have I got the right place in the sequence? And where is the read only flag coming from?
*The last time we ran this in anger will have been at least 12 months ago.
(3) Replies
‎Jan 15, 2011
06:01 PM
Are you installing on Vista by chance?
If so, checkout:
http://blog.deploymentengineering.com/2010/09/troubleshooting-iis-problems-on-vista.html
Also googling "iis 0x80070005" will probably be helpful. ( That's your negative error code in hexadecimal. )
PS- Check that your web.config isn't marked read only. If it's being installed this way, make sure that it's not marked read only in your build environment.
If so, checkout:
http://blog.deploymentengineering.com/2010/09/troubleshooting-iis-problems-on-vista.html
Also googling "iis 0x80070005" will probably be helpful. ( That's your negative error code in hexadecimal. )
PS- Check that your web.config isn't marked read only. If it's being installed this way, make sure that it's not marked read only in your build environment.
‎Jan 17, 2011
01:59 AM
Sadly not - XP SP3.
The Web.config, as stated, is not read only in the sources - and also if I build an uncompressed installer, you can see it isn't read only in there too. It's only when it passes through the copy process that a read-only flag is set.
The Web.config, as stated, is not read only in the sources - and also if I build an uncompressed installer, you can see it isn't read only in there too. It's only when it passes through the copy process that a read-only flag is set.
‎Jan 17, 2011
07:14 AM
Open up InstallShield and go to the component that has the web.config. Do a right properties on the file. Does it show marked as read only there?
If so, this makes it into the File table and will cause the file to be read only when deployed.
If so, this makes it into the File table and will cause the file to be read only when deployed.