Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Log & Event Manager (LEM) > Microsoft.SqlServer.Management.Trace.SqlTraceException: Failed to initialize object as reader

Microsoft.SqlServer.Management.Trace.SqlTraceException: Failed to initialize object as reader

Table of contents

Updated May 17, 2017

Overview

This article provides information on the following error in the Windows application event logs:

Thread ID: 01: InitializeAsReader Exception: Microsoft.SqlServer.Management.Trace.SqlTraceException: Failed to initialize object as reader. ---> System.Runtime.InteropServices.COMException
   at ?A0xc799a991.ProcessError(Int32 hr, UInt16* lpszMessage)
   at Microsoft.SqlServer.Management.Trace.CTraceControllerBase.InitSource(Boolean bReOpe

 

The MSSQL Auditor service is configured to run as a local system account and uses a different account to connect to the MSSQL database (all on the same machine). The events from the MSSQL Auditor do not display but the OS/Application events from the same machine are accessible. 

Environment

  • LEM 6.3.1
  • MSSQL Auditor
  • SQL Server 2014

Detail

The issue is caused when the user account running MSSQL Auditor service does not have Alter Trace permissions.

Take note of the following to avoid the issue:

  • Use localhost as the server name in the MSSQL Auditor configuration. Do NOT append a backslash followed by the default DB instance.
  • Use the local system account (NT AUTHORITY\SYSTEM) to run the Auditor service.
  • The NT AUTHORITY\SYSTEM must have Alter Trace permission granted in the SQL Server Management Studio.

 

Last modified
18:49, 25 May 2017

Tags

Classifications

Public