Posted by: gavinadams | 15 January, 2008

Hotfix released for timer job errors – Event ID’s 7076, 6398 , 6432 and 6482

‘cwhite’ has just posted on the sharepoint ‘from the field’ blog on a hotfix release to fix timer job issues. This has also been known as the ‘timer job shocker’. Initially I read some reports that it might be due to a security update to the .NET framework but it re-appeared for me. This one has been has been a tough one to track down so I’m glad to see that a hotfix has been released.

In the application event log you will see events for 7076, 6398, 6432 and for me I also saw 6482.

I’ll copy and paste the full events from my test server below.

The KB article is here. The anonying thing about this KB article is that it is categorised as only applying to IIS and not sharepoint even though the big driver to fix this seem to have been MOSS related. That means that it would be difficult to find this KB article if you are restricting your KB searches by product.

——————————————–

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Timer
Event ID:    6398
Date:        11/01/2008
Time:        12:10:08 PM
User:        N/A
Computer:    MOSSTEST
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 9668b02b-5f13-4963-bf0b-181c81272dea) 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.

——————————————–

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    6482
Date:        11/01/2008
Time:        12:14:07 PM
User:        N/A
Computer:    MOSSTEST
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (5e5393a6-039a-4896-a727-04818d85b326).

Reason: Exception from HRESULT: 0×80005006

Techinal Support Details:
System.Runtime.InteropServices.COMException (0×80005006): Exception from HRESULT: 0×80005006
   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 Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    7076
Date:        11/01/2008
Time:        12:14:08 PM
User:        N/A
Computer:    MOSSTEST
Description:
An exception occurred while executing the Application Server Administration job.

Message: Exception from HRESULT: 0×80005006

Techinal Support Details:
System.Runtime.InteropServices.COMException (0×80005006): Exception from HRESULT: 0×80005006
   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)

——————————————–

About these ads

Responses

  1. We’re also seeing this under IIS 7 yet the hotfix is specific to IIS 6.

  2. In an effort to fix this problem (6482/7076/6398 Event log sequence), I applied the hot fix. Result: it trashed my server OS! Use caustion!!

    On the bright side, I found a VERY simple “fix”.

    In your *separate* SHAREPOINT App Pool properties – Recycle tab:
    1. Set: Recycle Wrkr Proc in 5 min
    2. Set: Recycle Wrkr Proc at foll times
    Every 30 min from 0700 to 1900 (most web tfc)
    Else, every 60 min

    Works like a charm!!! No Event Log errtries. No IIS Mgr unavailability!!

    Wahoo!!

    • UPDATE:

      It now appears that recycling worker processes is *not* the solution. The disappearance of the errors was simply coincidental!!

      The *real* solution is to create a bat file that stops — then starts — the OWS Timer service!!!

      net stop owstimer.exe
      net start owstimer.exe

      Schedule bat file to run every 60 minutes… Voila!!! Tried and proven! It works!

      gary b

  3. Interesting article on how to resolve time job failures for alerts.

    http://home.dzeee.net/blogs/sp/Lists/Posts/Post.aspx?ID=26

  4. Interesting article on how to resolve time job failures for alerts.

    http://home.dzeee.net/blogs/sp/Lists/Posts/Post.aspx?ID=12

  5. The link in the original article contains full details on the correct fix. http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=47. This is a fix for both IIS 6.0 and IIS 7.0 see http://support.microsoft.com/Default.aspx?id=946517 for the fix.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: