Using the standard site administration tool from within Visual Studio to make changes to an app configuration can lead to strange issues, especially when paired with some custom MOSS development.
Apparantly the tool adds a line into the Web.Config that causes all users to lose access to everything under the _layouts folder which means that all administrative functions, webpart management, etc. goes down the tubes.
The symptoms of this error in our case we a bit muddied by another security setting change (unrelated to this problem) that was giving '404 Not Authorized' errors.
However, once that was cleared up the message changed to 'File Not Found'. The fix was very simple (thanks to this post Outlook by the sound) and all is well now.
Excerpt from above site for convienience:
"It seems that when you modify the web.config with the IIS tool, it adds an attribute (xmlns) to the <configuration> tag like so: <configuration xmlns="<a href=">http://schemas.microsoft.com/.NetConfiguration/v2.0</a>">."
Subscribe to:
Post Comments (Atom)
4 comments:
nice call on finding this solution. you just got to love the subtletys that can produce so many headaches.
Hello,
I am also having the same problem. Which web.config file are you talking about? I searching in the web.config on inetpub/wwwroot/wss level... but I couldnt find any xmlns tag being used in the web.config file.
Is there file somewhere on the Program Files/Common Files/Web Server Extensions file?
Thanks
Keep up the good work.
legality aperua salespeople lawley home exacerbation indicates pakistan digitised stray truck
servimundos melifermuly
Post a Comment