Question

My web application was running absolutely fine. Just 2 days back, I got an error saying. SERVER APPLICATION UNAVAILABLE

I am pretty certain that nothing was changed on IIS. Unless my automatic Windows updates screwed it up completely.

My event viewer had zillions of following errors in Application category.

aspnet_wp.exe could not be started. The error code for the failure is C0000005. This error can be caused when the worker process account has insufficient rights to read the .NET Framework files. Please ensure that the .NET Framework is correctly installed and that the ACLs on the installation directory allow access to the configured account.

I reinstalled IIS. After installing, i ran aspnet_regiis -i for framework v2 and now it throws error saying - The application could not be initialized properly.

Any ideas what going on?

Answer 1

Have you tried deleting the application from the application pool and recreating it? Have you customized any security settings? What version of Windows/IIS?

Answer 2

No security settings were changed. Its a Windows XP professional box with IIS Version: 5.1

Answer 3

Hi . We have the same issue in our company on many machines. We assume it has something to do with KB 974417 installed through windows updates..

Did you find any solution ?!?

We are desperate..

Answer 4

Alex,

No, I haven't found any solution yet. My IT admin is working on since 2 days now but now leads on that issue yet. Please keep me posted if you find something.

Answer 5

We have the same problem right now. Nothing has changed except for a restart following a Windows update that ran yesterday (12-Nov-2009). The OS is Windows XP Professional with IIS 5.1.

Answer 6

Alex,

By any chance do you have Symantec Endpoint Protection version 11.0.5002.333 running on your machines? I saw the same issue being mentioned on Symantec forums.

Just curious? As this update came out along the same time as the Windows Update KB 974417

Answer 7

Check this article: http://support.microsoft.com/kb/2009746. That's caused by KB973917 froom the Dec 09 patching. The error message is a bit different than yours though.

Also, if you recently updated your app pool identity, make sure that your custom app pool identity user is in the IIS_WPG group.

Answer 8

I've been fighting this one as well. Assuming it's a 11.0.5002.333 issue. Considering rolling back to an earlier version if that's possible.