Unexpected: Failed to get legacy traces

Problem

SharePoint Server 2010 Enterprise.

Checking the SharePoint Logs, found the following errors repeating each minute:

OWSTIMER.EXE (0x17A8)                     0x3264  SharePoint Foundation           Monitoring                      nasq  Medium    Entering monitored scope (Timer Job job-diagnostics-io-intensive-query-provider)  
OWSTIMER.EXE (0x17A8)                     0x3264  Extended Diagnostic Providers   SqlTrace Provider               2001  Unexpected  Failed to get legacy traces  
OWSTIMER.EXE (0x17A8)                     0x3264  SharePoint Foundation           Timer                           6398  Critical  The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPIOIntensiveQueryDiagnosticProvider (ID c2f9c9c0-5d41-43a4-98bf-c59b007c3065) threw an exception. More information is included below.  You do not have permission to run 'SP\_TRACE\_CREATE'.  
OWSTIMER.EXE (0x17A8)                     0x3264  SharePoint Foundation           Timer                           72ae  Unexpected  Exception stack trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)     at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)     at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)     at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Bo...  
OWSTIMER.EXE (0x17A8)                     0x3264  SharePoint Foundation           Timer                           72ae  Unexpected  ...olean returnStream, String method, DbAsyncResult result)     at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)     at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()     at Microsoft.SharePoint.Diagnostics.SqlTraceHelper.CreateTrace()     at Microsoft.SharePoint.Diagnostics.SqlTraceStreamer.Init(SqlTraceParameters parameters)     at Microsoft.SharePoint.Diagnostics.SPSqlTraceDiagnosticProvider.InitializeBackgroundThreads()     at Microsoft.SharePoint.Diagnostics.SPSqlTraceDiagnosticProvider.Sync()     at Microsoft.SharePoint.Diagnostics.SPDiagnosticsProvider.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTi...  
OWSTIMER.EXE (0x17A8)                     0x3264  SharePoint Foundation           Timer                           72ae  Unexpected  ...merService, Int32& result)  
OWSTIMER.EXE (0x17A8)                     0x3264  SharePoint Foundation           Monitoring                      b4ly  Medium    Leaving Monitored Scope (Timer Job job-diagnostics-io-intensive-query-provider). Execution Time=9.3616   

Solution

Grant the user running the SharePoint 2010 Timer (SPTimerV4) service, which is usually the Farm account, serveradmin or sysadmin rights on the SQL Server. Then, restart the Timer service.

Explanation

blogs.msdn.com/b/kaevans/archive/2012/02/09/sharepoint-error-6398-you-do-not-have-permission-to-run-sp-trace-create.aspx - great article!

---

_{Originally posted to: http://www.thesysadminhimself.com/2012/11/unexpected-failed-to-get-legacy-traces.html}