EventID 6398 – You do not have permission to run ‘SP_TRACE_CREATE’
I see a lot of customers downloading and installing the SharePoint 2010 Administration Toolkit which contains a lot of useful tools (e.g. an load – testing kit, the user profile replication engine, SPDiag 3.0 etc.). Especially the SharePoint Diagnostic Studio 2010 (SPDiag 3.0) I see installed on a lot of SharePoint environments.
From time to time when checking some servers which have the SPDiag installed I encounter an error on the eventlog with the EventID 6398 which tells me:
The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPIOIntensiveQueryDiagnosticProvider (ID 753b40f8-375b-472a-bfe1-660118a7735a) threw an exception. More information is included below.
You do not have permission to run ‘SP_TRACE_CREATE’.
What I like on this error message is that it tells you exactly what caused the error :-), missing permissions!!! Have you ever heard of that ;-)???
But before you now stop reading and run to your servers to grant the permissions you should first calm down, take a breath, everything will be good…
Ok… now fire up your central administration site and in the “Monitoring” section hit the “Check job status” link.
Now access job history by clicking on “Job History” and select the “Failed jobs” view in the view section in the upper right corner.
Here you check for the “Diagnostic Data Provider: SQL Blocking Reports” timer job and click on the “Failed” link to get more details about the error.
The blocking query diagnostics provider could not set the ‘blocked process threshold’ for the sql instance Your_SQLInstance. Blocking queries will not be captured in this instance. Error Code: User does not have permission to perform this action. You do not have permission to run the RECONFIGURE statement. The configuration option ‘blocked process threshold’ does not exist, or it may be an advanced option. You do not have permission to run the RECONFIGURE statement.
If you see this error now it is time to first review the installation process of the SPDiag and then to get finally rid of the error, to go to all your SQL servers (within the SharePoint farm of course) and grant your farm account “Alter Trace” and “Alter Settings” in SQL Management studio permissions
After applying this setting check the timerjob status again it should succeed now and the eventlog error should disappear.