Thursday, November 13, 2008

Empty/Blank IIS Manager When SharePoint Timer Throws Error

Ugly Error

I've seen this error often enough that I think it deserves a brief entry. Essentially the symptoms are:

  1. When you open up the Internet Information Services (IIS) Manager it takes a long time to load and when it finally does the console is blank. Running iisreset (Start->Run->iisreset) will temporarily fix the problem.Empty/blank IIS manager from SharePoint Timer error.
  2. In the event viewer under Application you see error codes for 6398, 7076, and 6482. Specifically they look like:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date: 11/13/2008
Time: 1:34:47 PM
User: N/A
Computer: [COMPUTER NAME]
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID [GUID]) threw an exception. More information is included below.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 7076
Date: 11/13/2008
Time: 1:34:47 PM
User: N/A
Computer: [COMPUTER NAME]
Description:
An exception occurred while executing the Application Server Administration job.
Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Techinal Support Details:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Server stack trace:
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAdsContainer.GetObject(String className, String relativeName)
[...]


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 11/13/2008
Time: 1:34:47 PM
User: N/A
Computer: [COMPUTER NAME]
Description:
Application Server Administration job failed for service instance Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance ([GUID]).

Reason: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Techinal Support Details:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Server stack trace:
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAdsContainer.GetObject(String className, String relativeName)
[...]

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

A Fix

Supposedly this behavior takes place when the Windows SharePoint Services Timer (OWSTimer.exe) has two threads that try to access IIS at the same time. There's currently a hot fix and description for this problem that patches IIS that. Ideally there'll be an IIS update that comes out in the future that isn't a hot fix. If you can bear it I would consider waiting.

Best,
Tyler

2 comments:

Matthew Chestnut said...

In my experience iisreset has not resolved the problem. Instead, I've had to restart the timer service itself.

Tyler Holmes said...

Depending on the timing this could definitely be the case. The sure fire bet is to stop the timer service and then reset IIS. After that, you should be good until you start the timer service again and it breaks IIS...this may happen immediately or only after a while (as long as weeks in some cases I've seen). Unfortunately on some machines it's intermittent and you never know how soon it will be until it rears it's head again.

That's one reason why if you can limp along I would suggest doing so until the fix is out of "hotfix" status.

The only consistent elements I've seen are the error codes/descriptions and the behavior from the IIS Console.