Avatar of sio2y
sio2y
 asked on

sharepoint 2010 error 5586 & 6398

Hi,

We are recieving two sharepoint errors however we dont currently use sharepoint.

The errors are listed below:

Event Id - 5586
 Could not find stored procedure 'proc_UpdateStatisticsNVP'. 2012-05-21T00:00:04.720: Starting 2012-05-21T00:00:04.720:

Event Id - 6398

string0 Microsoft.SharePoint.Administration.SPSqmTimerJobDefinition
  string1 5bd7dfd5-dd60-47db-b55a-4401d2bd24c6
  string2 Data is Null. This method or property cannot be called on Null values.


We have looked through several solutions online and as of yet we have not found one that we can follow. Your help is appreciated.

Thanks
Microsoft SharePointMicrosoft Legacy OSSBS

Avatar of undefined
Last Comment
sio2y

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
wbsn

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
wbsn

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
sio2y

ASKER
Much appreciated - it's going to take some time to look at these but I will not abandon this post.
sio2y

ASKER
Ok well I had some free time this morning and the first link you posted regarding error 6398 appears to be spot on.
sio2y

ASKER
Those two resources provide great resolution steps. I am closing the question based on the statement by MS that:

RESOLUTION

This is a known issue that will be fixed in a future release of the product. The error does not affect the functionality of the product in any way and can be safely ignored.

Sooooo - until I can get around to applying the solution I'll call it answered.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23