Web.config is overwritten after reboot

[devstylex]

Seems a customized Web.config is overwritten after reboot. Anybody any ideas how to solve this? Maybe there's a way to overrule the server settings by a higher level Web.config?

Regards,
J. Walrave

 

[philhege]

Question is, which web.config are you altering?

http://www.sharepointu.com/forums/p/4872/12512.aspx

Phil H.
Some Bank
-----------
Time's fun when you're having flies.

 

[devstylex]

Hi Philhege,

Changing the 12-hive is pretty stupid, that I already knew.

In fact this is a question I posted for someone else as I am a project leader (with development experience).

To keep a long story short. I seems that a backup of the web.config has been put back into operation. I find this to be a little odd. If you put a web.config.bak file into the root (same folder as where the web application's web.config resides) and after a reboot of the machine this bak file overwrites the web.config. I haven't tested it myself, but this is what they told me.

Regards,
J.

 

[furuknap]

Hello,

I think that sounds highly unlikely and there is nothing that SharePoint would do. In fact, SharePoint encourages modifying the site specific web.config to support deployment of custom code, so why would it destroy any such attempts?

From experience, and I've probably modified a thousand web.configs for SharePoint sites, this does not happen naturally.

What you can do is modify permissions on the file and then audit what process fails to access the file. Try removing all permissions to the web.config file and allow only read for system and the user under which SharePoint is running and of course give yourself full access to the file. Then, enable Windows auditing to see who actually tries to modify the file during a reboot.

.b

Blog for my upcoming SharePoint book
"Building the SharePoint User Experience":

http://www.understandingsharepoint.com/userexperience