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!!! 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.

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 timerjob status again it should succeed now and the eventlog error should disappear.

Advertisements

8 responses to “EventID 6398 – You do not have permission to run ‘SP_TRACE_CREATE’”

  1. Ron says :

    Awesome thanks.. that gets rid of some of the blood in my SP logs!

  2. toddler beds says :

    Hey would you mind stating which blog platform you’re using? I’m going to start my own blog in
    the near future but I’m having a tough time choosing between BlogEngine/Wordpress/B2evolution and Drupal. The reason I ask is because your layout seems different then most blogs and I’m
    looking for something completely unique. P.S Sorry for getting off-topic but I had to ask!

  3. tlach says :

    Hi,

    Having this same problem and I’m not exactly sure where in SQL MS to set the permissions you are referring to. Can you explain further. Thanks!

    • SPSoldier says :

      Hi Tlach,

      you can open your SQL management studio and right click on instance name on the left hand side of the managment studio and click properties. Here you will find the dialog box shown in the blogpost. Select permissions and grant the permission according to the blog post.
      Hope this helps.

  4. www.goacaiberry.com says :

    Very nice article. I certainly appreciate this website.
    Thanks!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: