Event viewer Errors : Event ID 7076,6398,6482

Posted: November 9, 2008 in Errors, SharePoint
Tags: , , ,

It’s strange but it was solved ! some kind of errors today morning appeared in my Event viewer.

  1. Source : Windows SharePoint Services 3
    Category : Timer
    Event ID : 6398
    The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID c3a1161b-2f29-4521-bb48-6262616a4f19) threw an exception. More information is included below.

    The path specified cannot be used at this time. (Exception from HRESULT: 0x80070094)

  2. Source : Office SharePoint Server
    Category : Office Server Shared Services
    Event ID : 7076

    An exception occurred while executing the Application Server Administration job.

    Message: The path specified cannot be used at this time. (Exception from HRESULT: 0x80070094)

  3. Source : Office SharePoint Server
    Category : Office Server Shared Services
    Event ID : 6482

    Application Server Administration job failed for service instance Microsoft.Office.Excel.Server.ExcelServerSharedWebServiceInstance (0ea7d1b0-28f7-4c5c-9286-63c2ba7d1f90).

    Reason: The path specified cannot be used at this time. (Exception from HRESULT: 0x80070094)

Resolve : It was very simple ! I don’t know why, but all of them stop appearing in event viewer after I restared the Office Sharepoint Server Search in the Services console.
  1. gary b says:

    I am no SharePoint guru! However, I was faced with these same errors in the Application Event Log *and* I had the IIS Mgr error (wherein IIS was blank and would not connect).

    In most Google results, the poster said to do IISRESET or stop/start SharePoint timer service. This is a work-around as you must repeat these steps periodically — the problems still exist. I fixed the problem — but I do not know which action (or combination) was the actual ‘solution’ So I offer what I did for you to try. The actions appear quite benign, so trying them to fix these issues should do no harm.

    (Speaking of harm, I applied the ‘hot fix’ spoken of in almost all Google results for this issue and it trashed my server OS. Use hot fix with caution.)

    To fix the 6482/7076/6398 and IIS problems:
    1. Put all web applications in separate ‘app pools’
    2. I configured the SharePoint Cent Admin App Pool to recycle worker processes every 30 minutes.

    I do not know which action “worked” or if both were needed. I was just very happy to eliminate these problems. I do not think the disappearance of these problems was just coincidental to my changes.

  2. gary b says:

    My only answer is:

    Because it appears to have stopped the problems.

    24 hours later, the Applic Log is free of 6482/7076/6398 errors.
    IIS maintains connectivity and is operational when I want it.

    I have seven web applications on this server. The Default app pool originally serviced four applications. I removed all but two — leaving two in the Default app pool. SharePoint is not in the default app pool.

    As I mentioned, I do not believe the disappearance of my problems was coincidental. But… I would not attempt to explain ‘why’ this worked because I do not know.

    As I said, my changes are quite benign to my knowledge. Are they worth a try?

  3. gary b says:

    Allow me to add something — again in response to your question…

    I also made a SharePoint change — configuring the worker processes to be recycled every thirty minutes. Perhaps THIS was the solution and the separate App Pools was itself merely coincidental!

    If someone has this issue, I would try the SharePoint change first and assess impact. If that does not clear the problem, make the app pool changes.


    • Navid.R says:

      For the section you said that IIS were blank and could not connect , I think the problem was about the WWW publishing service . I encountered this problem a few times and just restarting this service or restarting the server could simply solve it.

      maybe recycling the worker process is doing the same thing . maybe …

      but there’s something and it’s that all of these errors are related to office sharepoint search or timer service. ( according to the category of the events )
      didn’t you try restarting search & timer service with appropriate service account ???

  4. gary b says:

    Yes sir… did that! Many times!! That is the point. By my definitions, a process is not a ‘solution’ if *you* must continue to apply/perform the actions. [Ex: manually reset timer] A ‘work-around’ is when the root causes remains but *you* do not have to keep performing actions to get around the problem(s).

    I followed the many suggestions returned by Google search — including the ‘hot fix’ which caused *bad* problems. I check service accounts, SharePoint job definitions, etc, etc…

    Only when I made the changes noted did the errors stop and IIS resume ‘normal’ operation. I suspect that the app pool changes were not part of what worked. I believe setting the ‘recycle worker processes’ to be the key. (From 0700 to 1700 hrs, the process recycles every 30 minutes. Other times, recycle occurs every 60 minutes.)

    I also recognize that my ‘solution’ may not be a solution, either. It may be a ‘work-around’. It may simply be an automated method of Timer or IIS reset — not really resolving/clearing the cause. But the manifestations (log errors and IIS unavailability) no longer appear. That, after all, was my objective.

    I wish someone had these issues and could try the ‘recycle worker processes’ approach.

  5. Chua says:

    I solved the problem by restarting the Windows SharePoint Services Administration service. Btw, my servers having MOSS & WSS Dec 2008 Cumulative Patch.

  6. Amuro Ray says:

    I’m having the same issues.

    Gary, how do you recycle the worker processes? Tell me how so I can try your fix.

    • Navid.R says:

      Hi Amuro Ray
      You can find it in your IIS.
      Check the properties of the your site web application pool.
      It’s in the first tab ( Recycling )

  7. gary b says:

    I have done some additional testing and must conclude that ‘recycling worker processes’ helps… but that is NOT the answer to the problem. The disappearance of the problem (originally) and implementation of worker process recycling now appears to be coincidental.

    However, I did manage to find a workaround for the problem. The ‘problem’ is that (for whatever reason!!) the SharePoint Timer Service fails. The SharePoint Timer service is initiated by OWSTimer.exe. I finally ‘fixed’ the problem by:
    1. Created a ‘batch file’ that ‘runs’ owstimer.exe (recycleOWS.bat)
    2. Created a Scheduled Task that executes RECYCLEows.BAT
    3. Scheduled Task set to run every 30 min from 7AM to 7PM
    4. Scheduled Task revised to run every 60 minutes — 30 min seemed to be too frequent
    5. Recycle Worker Processes still runs during ‘business day’
    — Recycle Worker processes is in Properties of App Pool (IIS) —

    So the ‘real’ solution is to run OWSTimer.exe on a scheduled basis throughout the business day.


    gary b

    • Navid.R says:

      Thanks gary for sharing your experience with us.
      yup I also think this reason in more acceptable about these errors.
      The problem for stopping OWSTimer could be because of log on credentials !


  8. Roxane says:


    I have the same problem.
    I just found that : http://support.microsoft.com/?id=946517

    I’m about to try it soon.
    Just wanted to let you know.

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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s