locked
SharePoint 2013 Error 6398 The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDiagnosticsMetricsProvider threw an exception. RRS feed

  • Question

  • We have installed a SharePoint 2013 Server Farm with three Servers running on Windows Server 2008 R2. On two of the servers we get the following error message periodically. Any ideas what the reason is and how to fix it?

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          2013-03-06 06:12:01
    Event ID:      6398
    Task Category: Timer
    Level:         Critical
    Keywords:
    User:          DOMAIN\svc_spfarm
    Computer:      SERVER1.DOMAIN.com
    Description:
    The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDiagnosticsMetricsProvider (ID fbf22d1b-720e-49e9-b652-25f8cde1a7c6) threw an exception. More information is included below.

    An update conflict has occurred, and you must re-try this action. The object SPWebService was updated by DOMAIN\svc_spfarm, in the OWSTIMER (6900) process, on machine DANCER.  View the tracing log for more information about the conflict.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
      <EventID>6398</EventID>
      <Version>15</Version>
      <Level>1</Level>
      <Task>12</Task>
      <Opcode>0</Opcode>
      <Keywords>0x4000000000000000</Keywords>
      <TimeCreated SystemTime="2013-03-06T05:12:01.353658300Z" />
      <EventRecordID>4738</EventRecordID>
      <Correlation ActivityID="{9D04059C-6367-604E-BE32-1955F25C6022}" />
      <Execution ProcessID="7116" ThreadID="2712" />
      <Channel>Application</Channel>
      <Computer>SERVER1.DOMAIN.com</Computer>
      <Security UserID="S-1-5-21-624851280-1259239050-440149190-17630" />
    </System> <EventData>
      <Data Name="string0">Microsoft.SharePoint.Diagnostics.SPDiagnosticsMetricsProvider</Data>
      <Data Name="string1">fbf22d1b-720e-49e9-b652-25f8cde1a7c6</Data>
      <Data Name="string2">An update conflict has occurred, and you must
    re-try this action. The object SPWebService was updated by
    DOMAIN\svc_spfarm, in the OWSTIMER (6900) process, on machine
    SERVER2.  View the tracing log for more information about the
    conflict.</Data> </EventData> </Event>

    Wednesday, March 20, 2013 1:24 PM

All replies

  • I'm seeing the exact same error, did you ever find a solution?

    Wednesday, March 27, 2013 12:47 PM
  • I'm sorry. Until now I didn't find a solution. Any help is very apprechiated.

    Wednesday, April 3, 2013 1:29 PM
  • I have same issue. Any resolutions?

    spvrz, did this error have any visible projection? I mean - is it ok to ignore it? Do you have any problems in the farm, related to this error?

    Wednesday, April 24, 2013 8:32 AM
  • I'm still receiving this error. But I cannot see any impact on the farm caused by this error. I ignore this error at the moment, but it's just annoying.
    Wednesday, April 24, 2013 8:39 AM
  • I followed the steps here http://support.microsoft.com/kb/939308 and I no longer see those errors.

    Monday, April 29, 2013 3:38 PM
  • It seems like this error can be safely ignored but has anyone found a real fix for this issue?

    Tuesday, August 6, 2013 3:54 PM
  • I tried KB939308 (the title says it's for WSS, but the "applies to" includes SharePoint Server 2013). The critical application events ("errors") went away, but were back within 24 hours.
    • Edited by PaulE Friday, August 9, 2013 3:49 PM Correct application of KB
    Friday, August 9, 2013 3:47 PM
  • Microsoft.SharePoint.Diagnostics.SPDiagnosticsMetricsProvider

    Facing the same problem on 2 SP 2013 farms.
    Ran the cleanup dozen times as per > http://support.microsoft.com/kb/939308

    How to fix this?

    Tuesday, October 8, 2013 10:21 AM
  • Any solution?
    Friday, October 25, 2013 2:06 PM
  • I am having the same problem as well and KB939308 did not help. Is there still no solution to this?
    Monday, January 13, 2014 8:49 AM
  • I have cleared the cache several times, but the error continues to come back. Has anyone found a permanent solution to this error?
    Monday, February 17, 2014 5:54 PM
  • Follow the http://support.microsoft.com/kb/939308 advice and,

    Make sure that the Domain\svc_spFarm account has read write permissions on the share and ntfs folder where logging is configured

    if you haven't modified this, it will be located here: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS

    check that Domain\svc_spfarm is a member in WSS_ADMIN_WPG and if all of the above are true,

    make sure that the same location exists on all front end servers.

    If that is case, then check that Process Model - Shutdown time limit for Central Admin application pool is not causing the problem, use these steps to increase it: http://support.microsoft.com/kb/2543306/en-us

    or

    http://anothersharepointblog.blogspot.com/2013/12/web-application-not-getting-created-on.html


    Stacy Anothersharepointblog.blogspot.com


    Monday, February 17, 2014 8:21 PM
  • Thank you for your reply. The account does have access to the log files. It was not a member of WSS_ADMIN_WPG. I have added it and will let you know if that resolve the issue.
    Tuesday, February 18, 2014 8:17 PM
  • I have this exact same issue on 5 separate SharePoint 2013 jobs that I am managing.  The job runs perfectly fine for the entire day except for when the job to recycle the timer service runs.  Everyday at 6:11am, I get the 6398 error stating that I have a conflict.
    Tuesday, April 15, 2014 8:24 PM
  • The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDiagnosticsMetricsProvider (ID eb4c8c7c-e327-4f39-9504-85cc4391a961) threw an exception. More information is included below.  An update conflict has occurred, and you must re-try this action. The object SPWebService was updated by Domain\SP_Admin, in the OWSTIMER (18560) process, on machine ServerAPP1.  View the tracing log for more information about the conflict.


    Could you please help me out in this issue.
    Tuesday, June 17, 2014 12:01 PM
  • The link provided by SteveTheManMann will fix it. http://support.microsoft.com/kb/939308

    Stacy Anothersharepointblog.blogspot.com

    Saturday, November 8, 2014 1:19 PM
  • I've tried the suggestion to clear the cache (http://support2.microsoft.com/kb/939308) without any success. Im seeing the error when the "Performance Metric Provider" timer job fails. It's failing on all servers in my 2013 enterprise farm. I've confirmed all of the settings for logging permissions are OK as suggested by Stacey Simpkins. Anyone have any other suggestions? 

    We are running 15.0.4420.1017 (RTM)

    Cheers,

    clarky

    Wednesday, November 12, 2014 12:18 AM