Hi 60MXG, thanks for your comment.
Because of the virus outbreak we've had, (not to mention the time to uninstall a few updates, restart, uninstall, restart ...) I was really hoping to keep the critical updates installed - though I know what you are saying, and have considered this many-many times. I have another update however, hopefully an ASP/IIS guru can make sense of it.
--------------
I found that the sites will work if I open the Application Pool properties, and adjust the "Application pool identity" = Local System.
(Local Service, IWAM_pcname, or NETWORK SERVICE will not work)
--------------
By the look of the notice after making this change, I do not like keeping this setting, and would rather find the folder/files/service/misc that need the correct permission. I also still see the access denied error in the Application Error Log - so I think this is only a dangerous workaround.
Main Topics
Browse All Topics





by: 60MXGPosted on 2009-03-10 at 08:58:42ID: 23848154
Do you have the list of the patches you put on the server? I think one of the patches might cause this permission issue. What I would do is remove all the patches recently installed then reboot the server and see if the server is working or not.
If the server is working that meant the latested 75+ patches you installed must caused this error. It is better that you install 5 patches at a time and then test server to narrow down the patches that caused the problem. For an example, you installed patches from 1 to 5 and the server is working and you installed patches from 6 to 10 and then the server is not working, therefore you can determine that patches 6 to 10 might be the cause of this outage.
I had similar experience like this before althought it was not the same issue. I found out later that one of the patches was causing my server to go down by using the method I provided above.