{"id":1586,"date":"2012-02-20T19:01:41","date_gmt":"2012-02-20T19:01:41","guid":{"rendered":"http:\/\/www.obieta.com\/?p=1586"},"modified":"2012-02-20T19:01:41","modified_gmt":"2012-02-20T19:01:41","slug":"sql-aliases-and-sp_trace_create-errors-on-sharepoint-2010","status":"publish","type":"post","link":"http:\/\/obieta.com\/?p=1586","title":{"rendered":"SQL Aliases and SP_TRACE_CREATE errors on SharePoint 2010"},"content":{"rendered":"

When you use SQL Aliases (something that most people believe to be a good practice as it\u2019s a locally controlled link to the database, and unlike DNS it updates instantly, and Microsoft recommend it here http:\/\/technet.microsoft.com\/en-us\/library\/cc298801.aspx#Section6_3<\/a>) and you have installed SPDiag from the SharePoint Administrator Toolkit<\/a>, you also need to ensure the Alias name resolves to the IP Address of the cluster \/ DB Server. These guys hit the same issue \u2013 http:\/\/social.technet.microsoft.com\/Forums\/en\/sharepoint2010setup\/thread\/4b397f6c-249a-43f0-aa91-ff210e4e132b<\/a> and this guy mentions it in his \u201cLeast Privilege\u201d build documentation \u2013 http:\/\/craighumphrey.blogspot.com\/2010\/06\/sharepoint-2010-rtm-least-privledge.html<\/a> \u2013 as an extra bonus SQL Step \"Smile\"<\/p>\n

What happens is that the timer jobs that the SPDiag application creates in SharePoint make an RPC call to start up a Performance \/ logging Trace on the SQL Server; however while local SQL Servers, Remote SQL Servers and SQL Clusters addressed by their DNS name and instance work fine, SQL Aliases confuse SPDiag into thinking that you have a Database Server out there somewhere with the Alias name.<\/p>\n

The errors we saw were:<\/p>\n

The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDatabaseServerDiagnosticsPerformanceCounterProvider (ID 4fc4e5b8-c7ab-4b51-b5e7-57f40038dc81) threw an exception. More information is included below.
SPNL_Prod:The network path was not found.
Please ensure that the database server is available and that the SharePoint Timer service account is a member of the Performance Monitor Users group<\/span><\/strong> on the database server.<\/span><\/p>\n

And<\/span><\/p>\n

The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPSqlBlockingReportDiagnosticProvider (ID d26d4741-0244-4e6a-b4ff-b78c3421ca8c) threw an exception. More information is included below.<\/span><\/p>\n

The blocking query diagnostics provider could not set the \u2018blocked process threshold\u2019 for the sql instance SPNL_Prod.\u00a0 Blocking queries will not be captured in this instance.\u00a0 Error Code: User does not have permission to perform this action.<\/span><\/p>\n

You do not have permission to run the RECONFIGURE statement.<\/span><\/p>\n

User does not have permission to perform this action.<\/span><\/p>\n

You do not have permission to run the RECONFIGURE statement.<\/span><\/p>\n

And<\/p>\n

The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPSqlDeadlockDiagnosticProvider (ID 8d638793-8aa8-4f55-ae04-0efa42b679ee) threw an exception. More information is included below.<\/span><\/p>\n

You do not have permission to run \u2018SP_TRACE_CREATE\u2019.<\/span><\/p>\n

And<\/p>\n

The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPSqlBlockingReportDiagnosticProvider (ID d26d4741-0244-4e6a-b4ff-b78c3421ca8c) threw an exception. More information is included below.<\/span><\/p>\n

You do not have permission to run \u2018SP_TRACE_CREATE\u2019.<\/span><\/p>\n

And<\/p>\n

The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPIOIntensiveQueryDiagnosticProvider (ID 0b0f8d31-08d5-4592-96ef-05e84a2f33a6) threw an exception. More information is included below.<\/span><\/p>\n

You do not have permission to run \u2018SP_TRACE_CREATE\u2019.<\/span><\/p>\n

Phew! Also we saw these every 5 minutes, which appear if you have Event Log Flooding protection enabled in the SharePoint Settings\u2026<\/p>\n

Event 6398 (SharePoint Foundation) of severity \u2018Critical\u2019 occurred 22 more time(s) and was suppressed in the event log<\/span><\/p>\n

Easy to fix: Uninstall the Admin toolkit or (if you must have it) set up entries in your DNS system or Host File.<\/p>\n","protected":false},"excerpt":{"rendered":"

When you use SQL Aliases (something that most people believe to be a good practice as it\u2019s a locally controlled link to the database, and unlike DNS it updates instantly, and Microsoft recommend it here http:\/\/technet.microsoft.com\/en-us\/library\/cc298801.aspx#Section6_3) and you have installed SPDiag from the SharePoint Administrator Toolkit, you also need to ensure the Alias name resolves […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[5,1],"tags":[],"_links":{"self":[{"href":"http:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/posts\/1586"}],"collection":[{"href":"http:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/obieta.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1586"}],"version-history":[{"count":0,"href":"http:\/\/obieta.com\/index.php?rest_route=\/wp\/v2\/posts\/1586\/revisions"}],"wp:attachment":[{"href":"http:\/\/obieta.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1586"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/obieta.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1586"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/obieta.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1586"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}