I had the same problem, and it happened right after updating Windows, hmm ... First of all, someone (Windows Update) changed the user account in the service "Internal Windows Database (MICROSOFT ## SSEE)". Changed to the correct account, and WSS started to work, but with an error (application / error or something else)
This new problem was something that I got for free after I launched the Exchange Analyzer Tool and made some changes to my system that were recommended by the tool.
If I changed my web.config, also look like this (c: /inetpub/wss-dir/web.config):
<configuration> <system.web> <customErrors mode="RemoteOnly"/> </system.web> </configuration>
I found that the problem is the access / security issue. The error message told me:
Access to the path "C: \ WINDOWS \ Microsoft.NET \ Framework \ v1.1.4322 \ Temporary ASP.NET files \ root \ 8c91a6b5 \ 649b28ba" is denied.
But it wasn’t really true ... access was denied not to the folder .. \ Temporary ASP.NET Files \ root \ 8c91a6b5 \ 649b28ba, it was in the% TEMP% folder, which I just moved because of an offer from the Exchange analyzer.
Have a nice day!
Anders r
source share