EventID 6398 – You do not have permission to run ‘SP_TRACE_CREATE’

This error occurs due to installing and configuring SharePoint 2010 Administration Toolkit which adds three new SP Diagnostics Provider reports.  These require a database permission level of SP_TRACE_CREATE and RECONFIGURE.  Quite possibly the queries are failing because the account they are running with does not have sufficient permissions.  In my case in the server event log was running these under my Farm account.

Here are the 3 jobs that are added by the SP 2010 Administration Toolkit, this can be confirmed by running this PowerShell command (Get-SPDiagnosticsProvider):
  • job-diagnostics-sql-deadlock-provider
  • job-diagnostics-sql-blocking-report-provider
  • job-diagnostics-io-intensive-query-provider
Here are the three jobs that failed in the Central Administration Timer Service jobs:
Diagnostic Data Provider: IO Intensive SQL Queries <servername> 0:00:00 Failed 6/3/2013 9:57 AM
Diagnostic Data Provider: SQL Deadlocks <servername> 0:00:00 Failed 6/3/2013 9:57 AM
Diagnostic Data Provider: SQL Blocking Reports <servername> 0:00:00 Failed 6/3/2013 9:57 AM

I fixed this by going into the SQL database server(s) and selecting the database node (database server, not an individual database), then Properties, then Permissions.  Select the account in the right pane, then choose allow for these two permissions: "Alter Settings" and "Alter Trace".  These jobs run every minute and were fixed almost immediately.  I verified their success by going into Central Administration, Monitoring, Job Status and looking for the jobs in the History to see if they now succeed.

Here is where I found this information, with a cached copy of it included after:

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’.
image

What I like on this error message is that it tells you exactly what caused the error, missing permissions.


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.

image

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.

image

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.

image

After applying this setting check the timer job status again it should succeed now and the eventlog error should disappear.

Comments

Popular posts from this blog

SharePoint Designer 2013 Approval Workflow with Comments

Change SharePoint server hostname and Web Application Names

The Timer Service Failed to Recycle