Event 7076, 6398, 6482 regularly displayed in the Event Log on a SharePoint Server

Hi,

The SharePoint Product Group has experienced a lot of customers reporting an issue where they would get Event 7076, 6398, 6482 regularly displayed in the Event Log on a SharePoint Server. Information to help identify the event log messages is below.

Apart from the Event Log messages the symptoms that the customer may see is:

•	In SharePoint Server 2007, tasks that are scheduled do not run.
•	When you try to manage IIS 6.0 by using Server Manager, you receive a blank page, or you receive the following error message: the path specified cannot be used at this time

A Windows Server 2003 hotfix is now available for this issue.

946517    FIX: You may be unable to manage IIS 6.0 by using Server Manager if two threads access IIS 6.0 at the same time
http://support.microsoft.com/default.aspx?scid=kb;EN-US;946517

Event Log details:

Event Id: 7076
Event Source: Office SharePoint Server
The Message text will contain:
- "Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance"

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

- A reference to the Metabase in the call stack.

Event Id: 6398
Event Source: Windows SharePoint Services 3
The Message text will contain:  
- "Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob"

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

Event Id: 6482
Event Source: Office SharePoint Server
The Message text will contain:
- "Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance"

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

- A reference to the Metabase in the call stack.

Nick.

Published Thursday, January 31, 2008 5:22 PM by nickmac

Filed under: MOSS 2007, Supportability

Comments

# MSDN Blog Postings » Event 7076, 6398, 6482 regularly displayed in the Event Log on a SharePoint Server

PingBack from http://msdnrss.thecoderblogs.com/2008/01/31/event-7076-6398-6482-regularly-displayed-in-the-event-log-on-a-sharepoint-server/

Thursday, January 31, 2008 2:08 AM by MSDN Blog Postings » Event 7076, 6398, 6482 regularly displayed in the Event Log on a SharePoint Server

# re: Event 7076, 6398, 6482 regularly displayed in the Event Log on a SharePoint Server

A workaround for us, in lieu of the hotfix, was to simply restart the "Windows SharePoint Services Timer" service.

The restart of this service fixed the "corrupt memory" events and also got rid of the blank Internet Information Services Administrator page.

The SharePoint trace logs also contained error information that was cleared up once we restarted this service.

Monday, February 04, 2008 5:50 PM by mcnga1

Adding robots.txt to SharePoint

by Randy Drisgill

Friend of mine asked me about this today and I had to look it up because its been a while since I have done anything with robots.txt. Turns out its not as easy as just adding the robots.txt file to the web server root. SharePoint likes to block access to the file, so you will need to add a managed path from Central Admin.
Here are the steps:

1. Open Central Admin and navigate to Application Management > Define Managed Paths
2. Select your specific web application from the drop down
3. Add a new path for /robots.txt
4. Switch the type to Explicit inclusion
5. Click OK
6. Run IISREST

This is all you need to do, but if you still get a permissions problem, right-click on robots.txt and give "Everyone" Read permissions to the file.

Posted by Randy Drisgill Monday, January 26, 2009