Monday, September 17, 2007

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

This is the error that keeps coming back in a couple of events that are fired at the same time. I have these errors on the web server that is hosting the search queries. Using Google I stumbled upon a fix from the MS SharePoint RRE's, read the following post Timer Job Shocker to solve the errors as stated below:

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Timer 
Event ID:    6398
Date:        17-9-2007
Time:        9:38:18
User:        N/A
Computer:    Webserver
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 3dc44d7a-008a-4c71-8e96-8c19da3d2ce2) 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:        17-9-2007
Time:        9:38:18
User:        N/A
Computer:    Webserver
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.
   at System.DirectoryServices.Interop.UnsafeNativeMethods.IntADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject)
   at System.DirectoryServices.Interop.UnsafeNativeMethods.ADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject)
   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_IsContainer()
   at System.DirectoryServices.DirectoryEntries.CheckIsContainer()
   at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
   at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.Find(String name)
   at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.get_Item(String name)
   at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.Office.Server.Administration.SharedWebServiceInstance.CreateSharedWebServiceApplicationPool(SharedResourceProvider srp)
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

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:        17-9-2007
Time:        9:38:18
User:        N/A
Computer:    Webserver
Description:
Application Server Administration job failed for service instance Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance (836525f4-bb70-4f76-9ea3-759151a1edd4).

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.
   at System.DirectoryServices.Interop.UnsafeNativeMethods.IntADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject)
   at System.DirectoryServices.Interop.UnsafeNativeMethods.ADsOpenObject(String path, String userName, String password, Int32 flags, Guid& iid, Object& ppObject)
   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_IsContainer()
   at System.DirectoryServices.DirectoryEntries.CheckIsContainer()
   at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
   at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.Find(String name)
   at Microsoft.SharePoint.Metabase.MetabaseObjectCollection`1.get_Item(String name)
   at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.Office.Server.Administration.SharedWebServiceInstance.Synchronize()
   at Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

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

Tip: the hotfix that is described in the post is available for download here Download

 

Technorati tags:

10 comments:

Anonymous said...

Getting one as well. Brand new deployment 1 web front end 1 index\query 1 sql, 3 domain accounts, no content. Started after 4 days.

Robin Meuré said...

How did you configure the farm?
Is the Office Search Service enabled on the web server?
What did you select for the crawling?

Anonymous said...

This hotfix does not work. It works for a day or two and then the error comes back and fill up the event logs.

I am experiencing this with x64 bits farm .

Anonymous said...

Same problem here. Did you find a permanent fix?

Anonymous said...

Please share the solution fo rthi sissue

Anonymous said...

If you go to the link above called "MS Sharepoint RRE's" there is an update on this problem, with a new hotfix available from Microsoft. The updated file (adsiis.dll) is dated December 19, 2007. I'm about to install it now.

Anonymous said...

Possible Solution
http://blogs.technet.com/apurdon/archive/2008/01/31/is-your-sharepoint-server-reporting-event-ids-7076-6398-6482.aspx

Anonymous said...

The following link for KB Article 946517 fixed my following errors in sharepoint server.
Error Event ID: 6398, Category: Timer, Source: Windows SharePoint Services 3
Error Event ID: 6482 Category:Office Server Shared services,
Error Event ID: 6398 Category:Timer,
Error Event ID: 7076 Category:Office Server Shared services,

http://support.microsoft.com/default.aspx?scid=kb;EN-US;946517

Thanks
Shaik Maricar

梦中林 said...

When the Wow Gold wolf finally found the Buy Wow Goldhole in the chimney he crawled wow gold cheap down and KERSPLASH right into that kettle of water and that was cheapest wow gold the end of his troubles with the big bad wolf.
The next day the cheap wow gold little pig invited his mother over . She said "You see it is just as mygamegoldI told you. The way to get along in the world is to do world of warcraft gold things as well as you can." Fortunately for that little pig, he buy cheap wow gold learned that lesson. And he just k4gold lived happily ever after!

Anantha RishiKesan said...

Hi,

Even i got the issue and the event Log was flooded with 3 error msgs / minute. After using the below hotfix, i was able to get rid of it... let me check if this is a permanent fix or not

http://support.microsoft.com/default.aspx?scid=kb;EN-US;946517