Tuesday, March 17, 2009

Attempted to read or write protected memory

I have installed WSS 3 and Search Server Express on a Windows Server 2008 machine. No problems with that, all is fine. But today I found that three errors were logged in Event Viewer. They are:

Event ID 6398
Event ID 6482
Event ID 7076



Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (02203890-d48f-4db7-9704-017c33fe14ff).

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.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

I have not noticed any errors inside of SharePoint or that any functions are corrupt. The only issue I found was that my scheduled task for the Backup has not run as it should.

Found this article today, and I will probably not install the hotfix until other issues inside SharePoint are reported. The customer runs a Sharepoint agent within Backup Exec which should take care of the backup task issue.

10 comments:

Saanj said...

Hi,
We are also facing the same issue. We are also afraid to install the Hotfix because the problem still persists after installing the hotfix as reported by some people. We are still waiting for any clear solution.

Lise said...

Hey Saanj!
Okey, thank you for the information. Please post if you get a solution to this.
Best regards
/Lise

danzero said...

Lise, this may not be the cause of your problem (or Saanj's problem) but we encountered the exact same errors on our MS Office Project Server (MOPS) 2007 (uses WSS 3). The cause in our case was domain controller related. Our servers are all virtual machines (VMs) and we had created a template of our MOPS server post-installation. The problem occured when we tried to use that VM template to build a staging server; the template was already joined to the domain. Long story short, the domain controller was confused with 2 servers with the same name (and GUID). I think similar problems could still occur even when not using VMs. I just thought I'd share in case this can bring insight to others with the problem.

Lise said...

Hi Danzero,

Thank you so much for sharing this info!

Take care,
/Lise

Russell Giddings said...

This hotfix should resolve your issues...

http://support.microsoft.com/default.aspx/kb/946517

:-)

Lise said...

Thanks alot, I will try that!
/Lse

Kyle said...

Did this hotfix solve your problem. We are also getting these alerts on a similar setup as yours.

Lise said...

Hi Kyle! I have not worked with this customer for a while, and have therefore not been able to test it. But I will post here if it helped :)
/Lise

Jim said...

Lise,
This worked for me. I had the same exact errors in my App log. You saved me a lot of time and aggrevation. Thank you.

Lise said...

Hi Jim!
Nice to hear, thanks for posting!
Take care,
/Lise