Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > AppInsight for SQL cannot poll databases without guest access when agent uses Windows authentication inherited from node for polling (SAM)

AppInsight for SQL cannot poll databases without guest access when agent uses Windows authentication inherited from node for polling (SAM)

Updated February 4, 2018

Overview

If an agent uses Windows authentication inherited from a node for polling, AppInsight for SQL cannot poll databases without guest access and the status of polled applications switches to Unknown. 

When this occurs, the following text may appear next to component names in AppInsight widgets:

No valid data was received. The server principal is not able to access the database under the current security context. 

The following text may appear in agent diagnostic logs (see :

System.Data.SqlClient.SqlException (0x80131904): The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "TestDb" under the current security context.

AppInsight for SQL should be able to poll databases without requiring that the guest account be enabled.

Environment

  • SAM 6.6

Cause 

If credentials defined for the node are not passed down to the Orion agent, the agent uses LocalSystem credentials that may not be able to access all databases unless guest user access is enabled in SQL Server. (In SQL Server, the guest account permits access to a database for any logins that are not mapped to a specific database user.)

Resolution

Until this issue is resolved, use this workaround: 

  1. In the Orion Web Console, access the Appinsight for SQL application (for example, MSSQLSERVER).
  2. Click Edit Application.
  3. Verify that <New Credential> is selected in the Choose Credential field.
  4. Type credentials in the User Name, Password, and Confirm Password that match credentials for the node.
  5. Click Test to verify credentials.
  6. Click Submit.
 

 

 

Last modified

Tags

Classifications

Public