Recurrent exception events for MOSS in application log
Hi
We are getting a recurring sequence of 4 exception errors in the application event log of our MOSS server. (1 MOSS server and 1 SQL server). The event ID's are:
6482 Office Server Shared Services, 6482 Office Server Shared Services, 7076 Office Server Shared Services and 6398 Timer in that order.
The events occur every few minutes (varies between every 5mins to every 20ish).
Event details: (sorry it's so long but the errors are just very verbose!)
Event 6482:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (3176e02c-f6c1-4c54-a71c-b1576a75ee16).
Reason: Exception from HRESULT: 0x80005006
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
at Microsoft.SharePoint.Metabase.ApplicationPool.set_IdentityType(ApplicationPoolIdentityType value)
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)
Event 6482:
Application Server Administration job failed for service instance Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance (494a5ead-fe04-4d64-821c-4f6306d31afa).
Reason: Exception from HRESULT: 0x80005006
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
at Microsoft.SharePoint.Metabase.ApplicationPool.set_IdentityType(ApplicationPoolIdentityType value)
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)
Event 7076:
An exception occurred while executing the Application Server Administration job.
Message: Exception from HRESULT: 0x80005006
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
at Microsoft.SharePoint.Metabase.ApplicationPool.set_UserName(String value)
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)
Event 6398:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 689dfa2e-568b-4cd2-b0a8-e74450909ee2) threw an exception. More information is included below.
Exception from HRESULT: 0x80005006
After these events we get a second set that appear very similar but the detail is different:
Event 6482:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (3176e02c-f6c1-4c54-a71c-b1576a75ee16).
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)
Event 6482:
Application Server Administration job failed for service instance Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance (494a5ead-fe04-4d64-821c-4f6306d31afa).
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)
Event 7076:
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)
Event 6398:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 689dfa2e-568b-4cd2-b0a8-e74450909ee2) 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.
I have tried applying the hotfix detailed here:
http://support.microsoft.com/default.aspx/kb/923028/en-us
but this has not fixed the problem. Does anyone have any idea what could be wrong?
Thanks for your help.
Cheers
Mike
Answers
- I've now seen this problem in several MOSS environments since the OP and http://support.microsoft.com/kb/946517 has fixed it in every case.
Cheers
Mike- Marked As Answer byMikeV1 Thursday, August 28, 2008 2:28 PM
All Replies
Hi Mike,
We are getting the identical error messages. The difference on our network is that we are running MS Load Balancing on 2 Front End servers and a SQL 2005 Cluster with 2 servers on the backend.
If you find a fix, can you please post it here? I will do the same if we find a solution.
Thanks,
RamanI am seeing these same errors as well.
Our environment is the same as Raman's. Although we are using a hardware solution to load balance (fail over) and we have a SQL 2005 Cluster with 2 db servers on the backend.
Sharepoint is running on Windows 2003 servers. I am curious if the reason is because our Active Directory Service is Windows 2000 SP4.
I am getting:
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80028019): Old format or invalid type library.
This error seems to occur at this point:
Server stack trace:
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_IsContainer()
What version of Active Directory are you running?
Hi Raman
The events on our server stopped as mysteriously as they started at about 10pm on a Saturday night. I'm afraid I didn't get a cause or anything to indicate why they suddenly stopped. As I don't have any administrative function over the SQL server or AD I'm wonderig if it was something to do with them..but it's a bit of a stab in the dark to be honest.
Sorry not to be more help!
Cheers
Mike
I also got these error messages, and found that an IISRESET or reboot would make the errors go away for a couple of days and then they were back. The 923028 hotfix that you mentioned above did the job although I only applied it a couple of days ago. Might be a delay between when the hotfix is run and when it filters through your server, was the server rebooted or iisreset at that 10pm time you mentioned? Also what schedules like backup or indexing were running at that time?
I'll let you know if the errors return.
Hi
I have exactly the same error messages in the event log. MOSS is installed in a small server farm.
- Webserver: w2k3 x64
- DBserver: w2k3 x64; SQL 2005 x64
One week ago, I made an update on w2k3 SP2. The whole last week, the server was running without errors. This weekend, all begun from new. The event log is full of error messages. As well the hotfix http://support.microsoft.com/default.aspx/kb/923028/en-us didn't solve the problem.
Thanks for your help.
Cheers
Chris
- Have you seen the error return? I am getting this on one server within my farm but not on others. I also have a couple of clients and friends who have seen this error. I am attempting a reboot of the server first and if that does not work I am going to try the hotfix and/or call microsoft.
Hi,
I am also getting similar problem. Did anyone manage to find the cause and fix?
The proposed fixes which I have come across are:
i) Apply Windows Server 2003 SP2.
ii) Apply the hotfix KB923028 FIX: Error message when you run a .NET Framework 2.0 Remoting application: "Unhandled Exception: System.AccessViolationException" http://support.microsoft.com/?id=923028.
iii) Re-provision the Central admin site.
iv) Check that the SharePoint Service account had the right privileges on the SharePoint Box. Retype all the passwords including that for the account of the SharePoint timer job service.
Thanks.
Hi.
Also have the same problem, not surprised, i always run in to trouble..
Anyhow, after checking my moss installation inside and out i find a scheduled job running at exactly the same time as my errors get logged, i get them every minute btw.
The job running is something like: timer job for applicationserver administrativeservice (i have the swedish version so therefor the odd translation)
Anyhow "again", i want to know what this service does, anyone can help here? i deactivated it on my lab server and nothing odd came out of it, not a solution to the problem but might point me out in where the thing is broken..
Any help at all appreciated.
Kind Regards
//D
- the hotfix solved for a while and has reduced occurence of error but it is back.....
- I'm having the exact same error messages. Has anyone found a solution to get rid of them?
Same here, after installing the hotfix (for x64 you can get it through support, not download) the error went away for some time. After a day it's back although not as frequent as before.
- Is anybody with this problem using an agent from Trend Micro Security for SMB on that machine?
- No, I had mcafee installed but removed that, same problem....
- I started getting these events after installing the 120 day trial version of MS Forefront for Sharepoint. Recently I removed Forefront, and for now the problem seems to have disappeared.
- We're are seeing these same errors as well. x64, SP2, kb923028 applied throughout farm. I'm not sure if it's related, but I'm seeing strange behavior in IIS Manager when these errors start (Rebooting and/or IIS reset helps for a while). The IIS tree doesn't load and when I try to connect, I get a 'The path specified cannot be used at this time.' error.
Hi,
I am experiencing the same problem.
Can any one solve this. ?
Thanks,
PM
I have the same situation ... I think we may wait for MOSS 2007 Sp1 ...
With an IISRESET I cleared my logs for 2 weeks (and solve IISManager access problem) but then ... the issue restarts ... I have no idea ...
Yep, we're getting exactly the same issue.
Its a fresh install of MOSS 2007 on Win 2003 R2 x64.
Cheers for the suggestions, will try the iisreset to see what happens.
Many thanks
Nick
- I'm having the same problems and didn't solve it up to now.
But you don't have to restart IIS to make the problem disappear for a while. It is enough to stop and start the "Windows Sharepoint Services Administration" service in the MMC. This might even take longer than an iisreset, but does not affect endusers and the application pool cache is still alive so the responses from Sharepoint stay quick. Hi,
I had the same problem and resolved it by adding the sharepoint service accounts to iis services in DCOM.
Regards
Suboor
Hi Suboor,
Would you be willing to provide some more details about what permissions you added and to which DCOM services?
Thanks,
MindyI've been getting the same issues with my setup which is similar to a number here, only way to get access to IIS again was to reboot. I then found that DCOM error and made the permission changes this morning, instructions for this was provided my MicroSoft by clicking the link ont he event log. Waiting to see if this fixes the issue all together.
- Suoboor, thanks for the good advice, but unfortunately this is not the error we are talking about in this post. The steps you've listed should be followed anyway, but that won't help with the errors listed at the beginning of this thread. The consultant that helped us set up our MOSS farm told us the hint with DCOM. We've done that right at the beginning but we still have the errors described here.
MikeV1 wrote: Hi
We are getting a recurring sequence of 4 exception errors in the application event log of our MOSS server. (1 MOSS server and 1 SQL server). The event ID's are:
6482 Office Server Shared Services, 6482 Office Server Shared Services, 7076 Office Server Shared Services and 6398 Timer in that order.
The events occur every few minutes (varies between every 5mins to every 20ish).
Event details: (sorry it's so long but the errors are just very verbose!)
Event 6482:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (3176e02c-f6c1-4c54-a71c-b1576a75ee16).
Reason: Exception from HRESULT: 0x80005006
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
at Microsoft.SharePoint.Metabase.ApplicationPool.set_IdentityType(ApplicationPoolIdentityType value)
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)
Event 6482:
Application Server Administration job failed for service instance Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance (494a5ead-fe04-4d64-821c-4f6306d31afa).
Reason: Exception from HRESULT: 0x80005006
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
at Microsoft.SharePoint.Metabase.ApplicationPool.set_IdentityType(ApplicationPoolIdentityType value)
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)
Event 7076:
An exception occurred while executing the Application Server Administration job.
Message: Exception from HRESULT: 0x80005006
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
at Microsoft.SharePoint.Metabase.ApplicationPool.set_UserName(String value)
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)
Event 6398:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 689dfa2e-568b-4cd2-b0a8-e74450909ee2) threw an exception. More information is included below.
Exception from HRESULT: 0x80005006
After these events we get a second set that appear very similar but the detail is different:
Event 6482:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (3176e02c-f6c1-4c54-a71c-b1576a75ee16).
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)
Event 6482:
Application Server Administration job failed for service instance Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance (494a5ead-fe04-4d64-821c-4f6306d31afa).
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)
Event 7076:
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)
Event 6398:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 689dfa2e-568b-4cd2-b0a8-e74450909ee2) 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.
I have tried applying the hotfix detailed here:
http://support.microsoft.com/default.aspx/kb/923028/en-us
but this has not fixed the problem. Does anyone have any idea what could be wrong?
Thanks for your help.
Cheers
Mike
Same issues here. No resolution in sight. Hopefully escalating to Microsoft QFE Team
MIke,
Check in administration site of MOSS 2007 to see whether all the above services are running or not. Most of the time these exceptions occurs in event log because of the disabled services.
Thanks
Matt.
- Yep, we're seeing the exact same errors here too. Thanks everyone for posting....We'll be watching this thread closely.
I have seen this error a lot within my customer's environment as well. The "fix" for them appears to be simply restarting the affected services as in some cases it's Project Server 2007 (restart the Project Application service) and in other cases it appears to be the WSSAdmin and/or OWSTimer service. I have noticed that in particular when this happens the WSSAdmin service dies with an access violation -- check to see if you have an AV record via drwtsn32.exe and if you do send the dumps to Microsoft Support for analysis.
As far as what is causing these errors, I have yet to determine a pattern. This occured this morning and the root cause was a stuck job in the Project Server queue but next week or the week after it will be something different.
Thanks,
I only had the error on our index server, and after making all my service accounts members of this group (on the index server):WSS_ADMIN_WPG
the errors are gone.
OD
Hi,
Sorry, got mixed up with my troubleshooting....the fix i applied to fix the "Recurrent exception events for MOSS in application log" was the .net hotfixes.
I have applied them and the errors have not appeared since 25/6.
Lets hope they don't come back!!
I have also experienced these error trains....
Conditions: I suspected these errors came from a de-provisioned and deleted SharedServices (SharedServices1) instance on MOSS
Observations: Checking the Application Pool on the existing provisioned Shared Service instance revealed it to be using the pool with the name of the deleted SharedService(SharedServices1)... also there were errors on the SQL server showing failed logins, due to SQL Agent Jobs not being deleted during the de-provisioning process.
Solution: Changed the Application Pool to use the one created with the new Shared Service Instance(Configured from within MOSS Shared Services Admin). Deleted the SQL Server agent jobs.
Poof... no more errors
- In my case a deleted SSP can't be the cause of the error. I have only one SSP and never deleted one.
I think the post Suoboor should have linked to is http://soerennielsen.wordpress.com/2007/06/29/%e2%80%9dnot-enough-storage%e2%80%9d-event-log-error/
The hotfix did solve the error on my servers, but please note that I tested TWO versions of that hotfix, only one worked.
Might the same be the case for you guys?
I had this same error message and found that it was related to SQL permissions.
I had to ensure that my farm service account had DB owner permissions on my SSP Search database in SQL. This fixed the problem
I am having the same exact error. Can you please tell me how you resolved?
- Nothing has worked for me thus far, I still get these errors and a reboot is the only way to get rid of them for a few days. I can't even restart IIS if I wanted to because when these errors are in the log IIS won't show me any of my sites, I get an error that "The path specified cannot be used at this time"
I am encountering the same problem. I have heard that reprovisioning the SSP since specifically I am getting errors with
-
Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance
-
Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (14e33b9c-dee1-47f5-88bc-535570ddbca9).
Reason: Exception from HRESULT: 0x80005006
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006
-
我也遇到了同样的问题，虽然安装了hot fix 923028，但问题依然存在 :-(
I also encountered the same problem,Who effective solutions, please return to the articles or my e-mail, thank you!Well I think I finally solved the problem.
First I installed the hotfix. Which fixed for a day or so but then came back. But if I did an iisreset the snap in would come back. But who can do an iisreset in production on a daily basis.
Then I spoke to Microsoft and they recommended changing the service account passwords. So I followed this KB article.http://support.microsoft.com/kb/934838 Well then when I went to IIS I saw old Web app pools. I deleted the old ones and I haven't gotten the error messages back. So I believe because I had deleted an SSP and some WEB Apps and recreated I got these errors. Hopefully it works for everyone else. If I get the error messages back I will reply and let all know. So far so good.
Well spoke to soon. Errors are back. So, so far everything I have tried works for a bit but then comes back. Has anyone got this fixed and have it stayed fixed for more than a week or 2.I've been seeing this problem as well. I tried the hotfix, which fixed it for a few days, but now I'm seeing the errors come back. An odd behavior is I'm unable to create new app pools & sites when the errors are new in the applog. If I run iisreset, I'm able to make new sites, for a while. Anyone else seeing that behavior as well?
Still looking for a fix if anyone knows more about this.
Well I have bad news for all.
I've had these reoccuring errors on our web farm since it was created in January of this year. I've tried everything listed here. Sometimes jostling things (reseting passwords) helps but only for a while.
I now have a scheduled job to reboot each server in the farm every second day in off peak hours.
I have another open ticket with Microsoft related to 'This List' and 'This Site' searches failing due to server errors and on the phone we discussed these errors. It's a known issue at Microsoft and even they don't have a solution!
Is there any impact to MOSS if this error keeps ocurring?
iisreset stopped the errors. will post later if they return.
about every 90 seconds this group occurs:
Windows SharePoint Sharepoint Services 3 Timer 6398
Office SharePoint Server Office Server Shared Services 7076
Office SharePoint Server Office Server Shared Services 6482
Office SharePoint Server Office Server Shared Services 6482
(that's not a typo, the 6482 occurs twice in a row.)
i am running Windows Server 2003 r2 fully patched
sharepoint 2007 - not in production, so users are not hammering it.
is 1 of 2 ad dc's
other than sharepoint 3.0 admin tools, and mcafee av, no other software...
dell poweredge, two 3ghz dual core cpu's 4gb ram
I believe this, and other similar problems with different S.P. services is caused by the fact that memory leaks in OWSTIMER and WSSEARCH affect the other services' ability to execute.
I have a ritual of running these commands whenever i see errors like this in my log, and so far it has been successful at least for a little while in clearing out these errors.
net stop "Office SharePoint Server Search"
net start "Office SharePoint Server Search"
net stop "Windows SharePoint Services Timer"
net start "Windows SharePoint Services Timer"
I have a batch that schedules these every morning but I think I have to run them more often than that, because I still keep getting the errors every day or so
Temmu, did you read this entire thread? On a June 7th 2007 posting someone else mentioned reseting IIS and the problem reappeared!
Yeah. It makes sense that they would return.
If it is a memory leak, it is only a matter of time before whatever resource limitation or memory collision that has been happening happens again. I'm guessing it stops temporarily because of the many services on a system, iis application pools and sites take up a substantial chunk of memory. When you iisreset Ii'm guessing that things run smoothly until the app pools return to their former size.
I propose that the actual problem is not IIS, but the services that collide memory space with IIS. (WSSEARCH and OWSTIMER)
An IISReset is extremely intrusive to a SP Farm, but WSSEARCH reset or OWSTIMER reset should be pretty transparent to the end user and is extremely effective.
Also it would be healthy to recycle your app pools on a schedule and perhaps use a JIT warmup script so users don't notice the restart so much.
http://blogs.msdn.com/joelo/archive/2006/08/13/697044.aspx
Hi All
As the OP I just thought I'd let you know how we got rid of these errors. Firstly we made sure all our service account passwords had been entered correctly using the procedure mentioned here:
http://support.microsoft.com/kb/934838/en-us
This appeared to have some effect (there was less regular pattern to the errors) but we were still left with quite a few 6398, 7076 and 6492 errors. We then un-provisioned and then re-provisioned our central admin site:
Re-provision the Central admin site
=======================
1. Select SharePoint Products and Technologies Configuration Wizard
2. Select Next. And yes to the IIS, SharePoint Admin Service, and the SharePoint Timer Service popup.
3. Select Next leaving the default "Do not disconnect from this server farm" selected
4. Select "Yes, I want to remove the web site from this machine" then click next.
5. Click next again to confirm.
6. There are a series of 8 steps that transpire, when they complete, your Central Admin site will be removed. Click finish.
7. Go back to SharePoint Products and Technologies Configuration Wizard
8. Select Next. And yes to the IIS, SharePoint Admin Service, and the SharePoint Timer Service popup.
9. Select the "Do not disconnect from this server farm" radio button, and click next.
10. You can specify a port, or leave the default port selected and click next.
11. Then Select Next on the Completing the SharePoint Products and Technologies Configuration Wizard.
12. Click Finish. And your Central Admin Site will be launched.
Since this was performed most of the errors have gone. We do still get them if MOSS has a problem connecting to the DB server for whatever reason (the timer service seems particularly sensitive to DB connection problems and appears to hang sometimes when this happens - restarting it in services is then required). In general though the app log is much cleaner.
Hope that helps some of you.
Mike
I agree with phydroxide.
As a workaround I've put in daily timer service restart job (net stop/start) - a lot less intrusive than iisreset and seems to do the trick (for my environment at least). Cleared the errors, but until MS come up with mem leak fix for this it'll have to do. Also workaround for IIS Manager's "'The path specified cannot be used at this time." problem.
Will add search service restart and/or schedule more frequently if the errors continue to come up.
Waiting for SP1....
I found that the 'Windows SharePoint Services Search' service startup type had been set to disable. changing this to automatic and starting the service sorted my problem.Im in the same situation as most of you with MOSS 2007. Restarting the 2 search services doesn't seem to work and IIS is locked out until I use iisreset.
I have been looking at the SQL Server event logs and noticed recurring errors that come exactly 1sec before getting the 3 Sharepoint errors (6398, 7076 and 6482).
These 2 SQL Server 2005 errors are:
[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'DOMAIN\SVC_ACCOUNT', error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
[298] SQLServer Error: 3621, The statement has been terminated. [SQLSTATE 01000] (ConnIsLoginSysAdmin)
After some googling I have found out that this is likely to be because my SQL Server main service is run on a local account which doesn't have permission to query AD.
Has anyone else got these SQL events or similiar?
- Anyone with these errors update to SP1 yet? Wondering if that update has fixed this issue.
Our MOSS 2007 farm has these errors but I've started using warmup scripts in the morning and adding some restarts of services and app pools. This has minimized the amount of times the errors resurface (only once since I started the schedule). I recently updated to SP1 and haven't seen the errors since.
I guess I could stop running my warmup script, but I was just curious if anyone has had any luck with SP1. Yesterday I installed the SP1 on our MOSS, unfortunatelly it didn't help.
I have now installed the NDP20-KB923028-X64.exe hotfix, hopefully this will help. You can read more about it at:
http://gpeiris.blogspot.com/2007/03/event-id-6482-7888-6398-7076-errors.html
- SP1 did not resolve the issue for me.
I installed KB923028 hotfix a long time ago, it didn't resolve the issue.
I've updated to .net 2.0/3.0 SP1, those updates did not resolve the issue.
Has anyone else tried to re-provision the central admin site as MikeV1 suggests? Can anyone confirm that this solution works?Hi!
I managed to solve the issue, read about the workaround at our Blog:
http://tahoesolutions.blogspot.com/2008/01/event-6482-and-6398-errors-in-event.html
// Adam
Adam,
Wait for a few days, I bet the error will come back on your server. Here is what I did on our servers, and they have worked for long time so far: http://www.sharepointfusion.com/2007/12/part-8-of-sharepoint-2007-setup-and.html
Basically, here is the procedure:
1. Make sure there is no DCOM error with event ID 10016 in the SYSTEM event log. If there is any, check here and fix it.
2. Reboot the SharePoint server
3. Schedule a daily task (off hours) to stop and start "Windows SharePoint Services Timer" service. You can use following commands in your daily batch task:
net stop sptimerv3
net start sptimerv3Trent (SharePoint Fusion)
I already have the script running, notice that my events were related to error code: 80070005 which is Access Denied. The only way to stop the flooding of the event log was by the approach described in our blog. Thanks anyway!
By the way, great posts about Sharepoint 2007 setup and configuration in your blog.
Hi all,
Not sure if this helps, but it looks like this IIS error and not SharePoint. Check out the attached blog and kb article. I haven't applied the hotfix yet.
http://sharepoint.microsoft.com/blogs/fromthefield/default.aspx
http://support.microsoft.com/?id=946517
I can confirm that the hotfix on KB 946517 finally resolved these recurring errors for me. I had this in three different farms, and it fixed all three. It's been over a week, and no more errors in the application log.
Yep, confirmed here as well. Finally fixed the issue.
It fixed our 7 server farm as well. We setup this farm 1 year ago and have had the errors almost from the begining. It's been one week since applying the fix and the errors are gone! A part of me was still worried but since reading these last two posts I'm convinced it will take.
- Ok fine, but where can we download this hotfix?
- You have to contact Microsoft and request it.
Thank you! I searched many posts and this is the only with a fix.
Johanna Aqui wrote: Thank you! I searched many posts and this is the only with a fix.
By the way, it's now been two months since I applied the fix and the errors have not reoccurred.
The hotfix will not fix it. It will come back in a few days. What a nightmare.
I have been getting the below 4 errors for the last 4 days , every minute.
---------------------------------------------------------
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date: 4/9/2008
Time: 12:20:02 PM
User: N/A
Computer: TESTMOSS1
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 56728fe5-259f-4ac8-a034-60072280500b) 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: 4/9/2008
Time: 12:20:02 PM
User: N/A
Computer: TESTMOSS1
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.
------------------------------------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 4/9/2008
Time: 12:20:02 PM
User: N/A
Computer: TESTMOSS1
Description:
Application Server Administration job failed for service instance Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance (ece19334-f597-4fbd-8174-cbadf80e001e).
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.
--------------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 4/9/2008
Time: 12:20:02 PM
User: N/A
Computer: TESTMOSS1
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (8b537f92-5b44-4ed9-9e8b-8a6cfaa9cf9c).
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.
This i believe is the answer to this problem. I am waiting for the service pack to come out that will address this.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;946517
Hi,
check the follwoing URL it may be usefull for your issue, i have the same issue in my enviroment and i will try them both :
http://support.microsoft.com/kb/946517
http://support.microsoft.com/kb/923028
Good Luck for all of you
Bashar Zaour
- I've now seen this problem in several MOSS environments since the OP and http://support.microsoft.com/kb/946517 has fixed it in every case.
Cheers
Mike- Marked As Answer byMikeV1 Thursday, August 28, 2008 2:28 PM
- Great! KB KB946517 Hot Fix worked! I got rid of those pesty error messages.
- Is this a part of the infrastructure update? I am not sure and would want to know.
- Amar D said:It's not included in the Infrastructure Update (IU). The IU was for MOSS / WSS 3.0, while the hotfix was for IIS 6.0 and 7.0. To double check, I compared the dll's for each, and those affected by the hotfix are not included in the IU.
Is this a part of the infrastructure update? I am not sure and would want to know.
Dan Lewis
http://weblogs.asp.net/danlewis
