none
Event ID 6398 and 5586 (SharePoint 2010) RRS feed

  • Question

  • I have configured Search on a Single Farm SharePoint 2010 server on Windows Server 2008 R2. The crawls are working and I’m getting results on a search page, but the event log creates these two events every minute:

    Critical Event 6398

    The Execute method of job definition Microsoft.Office.Server.Search.Monitoring.HealthStatUpdateJobDefinition (ID 151f6f19-594d-4ba8-ab82-0b187839325a) threw an exception. More information is included below.

    Could not find stored procedure 'dbo.Search_GetRecentStats'.

     

    Error Event 5586

    Unknown SQL Exception 2812 occurred. Additional error information from SQL Server is included below.

    Could not find stored procedure 'dbo.Search_GetRecentStats'.


     

    I have spent hours trying to get these events go away. Can anyone help?

    Tuesday, August 10, 2010 9:41 PM

Answers

  • After hours of research and testing, I did get the errors in the event log to stop.

    I have the Usage and Health Data Collection Service Application installed. This service application creates a database just for logging. Apparently the Search Service was trying to make entries in that database and couldn’t.

    I read that the logging database grows fast, so I never enable the Usage Data Collection. Once I did, the errors were gone.

    To enable the Usage Data Collection navigate to Central Admin\Application Management\Service Applications\Manage service applications.  Once there highlight the WSS_UsageApplication and select manage from the ribbon.  Under Usage Data Collection check the box. Under Health Data Collection check the Enable health data collection box.  Hit OK and the errors will be gone.

    Friday, August 13, 2010 12:17 PM

All replies

  • Try to run the SharePoint Configuration Wizard and see if errors out or fixes anything. This will be a good place to start since it looks like you are missing a stored procedure in the database.
    Wednesday, August 11, 2010 1:55 AM
  • I tried running the configuration wizard already and no change. I tried deleting the search service application and recreating it, running the wizard again, and still no change.

    Wednesday, August 11, 2010 12:00 PM
  • Hi PawnofGod,

    Have you had any luck fixing this problem? - I have ran into exactly the same issue.

    Thanks

    Thursday, August 12, 2010 10:38 PM
  • After hours of research and testing, I did get the errors in the event log to stop.

    I have the Usage and Health Data Collection Service Application installed. This service application creates a database just for logging. Apparently the Search Service was trying to make entries in that database and couldn’t.

    I read that the logging database grows fast, so I never enable the Usage Data Collection. Once I did, the errors were gone.

    To enable the Usage Data Collection navigate to Central Admin\Application Management\Service Applications\Manage service applications.  Once there highlight the WSS_UsageApplication and select manage from the ribbon.  Under Usage Data Collection check the box. Under Health Data Collection check the Enable health data collection box.  Hit OK and the errors will be gone.

    Friday, August 13, 2010 12:17 PM
  • Unbelievable - thank you.  I too spent hours trying to fix this issue and the answer was as simple as enabling the option.

     

     

    Wednesday, August 18, 2010 9:58 PM
  • This did not work for me as I have this enabled already. My error is reporting as an Event ID 6398, however it is a timer related issue.

    The Execute method of job definition Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob (ID 2421aac6-cb9a-49d4-8f9f-f6367abf99f3) threw an exception. More information is included below.

    An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by domainxx\accountname, in the OWSTIMER (1560) process, on machine <ServerName>.  View the tracing log for more information about the conflict.

    I removed the domain and server information.

    This is preventing me from getting my sites set up.

    Thursday, August 19, 2010 3:28 PM
  • SGGORDY-

    Did you ever get a fix for this.

    I am really getting frustrated. In my testing environment I was not gettint any errors. Now that I am teying to set up on the production server itis just bleeding throught he event logs.

     

    I am getting an error  ID 6398

    Could not find stored procedure 'dbo.Search_GetRecentStats'.

    Unable to find a fix. The workaround listed above is already set as default when navigated there.

    I am getting thrown all sorts of permision errors.

    Got a fix for this -

    Session "WSSUSAGESESSION14" failed to start with the following error: 0xC0000022

    cant figure it out either.

     

    Derek

    Monday, September 20, 2010 3:38 PM
  • Derek,

    I never did get a fix that worked.

    I ended up doing a complete reinstall and did it all manually. Since, I have been lucky enough not to receive this error again, and have everything setup what appears to be "perfectly". I do recommend a manual setup - which can take a bit longer and can be challenging, however, I was able to tackle all erorrs and was able to clear them all. I did not at any time run the Farm Config Wizard, as this will also reset your superuser accounts and other items. I wanted full control over my environment.

     


    SGGordy
    Tuesday, September 21, 2010 12:50 PM
  • Turn off the Usage and Data Collection by navigating to your Central Administration > Monitoring > Configure usage and health data collection.  Uncheck both Enable usage data collection and Enable health data colletion, assuming they are checked, and click OK.

    Once this is done restart the SharePoint 2010 Timer service.  Then re-enable Usage and Data Collection by checking those same items again.  The error should stop appearing in the logs now.

    Thursday, December 16, 2010 5:24 PM
  • That worked for me and I just had to say "THANKS!"
    My server died and went to Dell.
    Friday, January 21, 2011 9:18 PM
  • Darkstu, I was getting similar errors:

    The Execute method of job definition Microsoft.Office.Server.Search.Monitoring.HealthStatUpdateJobDefinition (ID 0f9dad9e-532f-4e43-a48d-50af6e997716) threw an exception. More information is included below.

    Updates are currently disallowed on GET requests. To allow updates on a GET, set the 'AllowUnsafeUpdates' property on SPWeb.

    Your fix solved it for me, thanks!

    • Proposed as answer by Mister Iks Tuesday, December 4, 2012 3:41 PM
    Friday, March 25, 2011 4:02 PM
  • In my own situation I found that the fix to this issue is to make sure the following time job is both enabled and has been executed:

     

    "Search Health Monitoring - Trace Events"

     

    This timer job installs the stored procedures you need for Search admin reports such as dbo.Search_GetRecentStats.

    • Proposed as answer by MrAnubisX Monday, March 26, 2012 10:14 PM
    Thursday, August 18, 2011 4:33 AM
  • In larger farms where a dedicatd account is used to run the oSearch service, make sure you grant the service account running oSearch the proper permissions on the WSS Usage dB as well.

    Wednesday, November 9, 2011 5:02 PM
  • Mine's enabled but still giving the error.

    Wednesday, April 25, 2012 2:56 PM
  • Hi Prashanth

    I have installed SP Server 2010 on a server and I have 2 servers one being a DC and the other one I have SQL Server 2008 r2 installed. I have a user sp_farm on the DC that I will use to create the SharePoint_Config database with. Now when I connect to the sql server server by running the SharePoint Wizard I get this error- Cannot connect to the database master at SQL Server at SQLbox.contoso.com. The database might not exist or the current user does not have permission to connect to it.

    In the event viewer I get this Event: 5586 - A network-related or instance-specific error occured while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, Error:40 - Could not open a connection to SQl Server).

    What I did after this is the finding this out was:

    Check the permissions of the user that I was provisioning the SP Farm with and granted this account with (sysadmin, dbcreator and public). It seems like there might be something that I might be missing. Someone suggested disabling the firewall... Not sure about that but I tried that one as well.. I am in a but of a predicament... Guru's its your time to shine...

    • Proposed as answer by Share.Hans Thursday, December 13, 2012 2:42 PM
    Friday, May 11, 2012 10:17 AM
  • In my own situation I found that the fix to this issue is to make sure the following time job is both enabled and has been executed:

     

    "Search Health Monitoring - Trace Events"

     

    This timer job installs the stored procedures you need for Search admin reports such as dbo.Search_GetRecentStats.

    This worked for me!

    Thanks

    • Proposed as answer by Millard1 Wednesday, May 23, 2012 12:56 PM
    Wednesday, May 23, 2012 12:55 PM
  • Thank you!  This worked for me as well.


    Tina

    Tuesday, May 29, 2012 6:48 PM
  • I had the following errors in my Windows Application event log repeating every minute

    Error   SharePoint Foundation   Event ID 5586   Category  Database
    Unknown SQL Exception 2812 occurred. Additional error information from SQL Server is included below.
    Could not find stored procedure 'dbo.Search_GetRecentStats'.

    and
    Critical   SharePoint Foundatoin   Event ID 6398   Category  Timer
    The Execute method of job definition Microsoft.Office.Server.Search.Monitoring.HealthStatUpdateJobDefinition (ID 34671eb2-bd0d-4c3a-80c0-be80a56eed9a) threw an exception. More information is included below.
    Could not find stored procedure 'dbo.Search_GetRecentStats'.

     

    Per PawnofGod's post above, I checked to make certain the usage application data collection was enabled
    CA > Application Management > Manage Service Applications > SharePoint Usage Application Service
    Enable usage data collection & Enable health data collection were both Already enabled.
    The service application and its proxy were Started.

    I tried the Disable, re-enable approach mentioned below in another post by darkstu, but that did not resolve the issue either.

    After more searching, I found the following which worked for me.  Hope it helps anyone else that has this issue.

    http://www.mysharepointadventures.com/2012/02/event-6398-and-5586-sharepoint-foundation/

    1. Go to Central Administration -> Monitoring -> Review job definitions
    2. Look for the job: Search Health Monitoring – Trace Events and see when it was last run. Chances are the job is set to ‘Disabled’ and never ran.
    3. Enable the job and click on ‘Run now’.
    4. The errors should stop appearing in the event log.

    Friday, July 13, 2012 5:47 PM
  • Running the job Search Health Monitoring - Trace Events worked for me. Thanks a lot.

    This eventlog entry appeared after migrating the databases to SQL 2012...


    Friday, August 3, 2012 3:46 PM
  • I had the same issue and after long googling found this solution.

    Thx Darkstu and Michael__F !

    Tuesday, December 4, 2012 3:42 PM
  • Excellent!!! Thank you very much.
    Tuesday, December 11, 2012 7:12 AM
  • It worked for me, jst turned the Logging on ! Simple but effective, THX so much.
    Tuesday, July 16, 2013 11:06 AM