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 > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Network Atlas error: An unexpected error occurred - call support

Network Atlas error: An unexpected error occurred - call support

Created by Robert Stidman, last modified by MindTouch on Jun 23, 2016

Views: 2,601 Votes: 1 Revisions: 5

Overview

The following error appears when trying to log in to Network Atlas on the primary Orion server:

An unexpected error occurred - call support

 

The following error also appears in the SolarWinds.Orion.Web.AuthorizationManager file:
(null) Get Auth Groups of scyr in WRBTS. System.DirectoryServices.AccountManagement.PrincipalOperationException: An error (1301) occurred while enumerating the groups. The group's SID could not be resolved.
at System.DirectoryServices.AccountManagement.SidList.TranslateSids(String target, IntPtr[] pSids)
at System.DirectoryServices.AccountManagement.SidList..ctor(SID_AND_ATTR[] sidAndAttr)
at System.DirectoryServices.AccountManagement.AuthZSet..ctor(Byte[] userSid, NetCred credentials, ContextOptions contextOptions, String
flatUserAuthority, StoreCtx userStoreCtx, Object userCtxBase)
at System.DirectoryServices.AccountManagement.ADStoreCtx.GetGroupsMemberOfAZ(Principal p)
at System.DirectoryServices.AccountManagement.UserPrincipal.GetAuthorizationGroupsHelper()
at SolarWinds.Orion.Web.AuthorizationManager.WindowsAuthorizationManager.GetPrincipalGroups(WindowsIdentity identity, String identName,

PrincipalContext context, String domainName, Boolean& faulted)

Environment

All Orion products with Network Atlas

Cause 

This can occur because of the following:

  • The account being used by the application pool is not a member of the local administrator or domain administrator groups.
  • The security identifiers (SIDs) S-1-18-1 and S-1-18-2 cannot be mapped after a Windows 2012 domain controller is added to the network.

Resolution

  1. Open a command prompt on the main poller.
  2. Run the following command:
    psgetsid S-1-18-1
    Note: The following error may appear:
    Error querying SID: No mapping between account names and security IDs was done.
    This specific error mapping the SIDs is limited to Windows 7 and Windows 2008 R2.

3.  Log in to the server with an account that has the correct administrative permissions. If this has already been done and psgetsid fails with the error above, refer to the Microsoft KB Article 2830145.

 

 

Last modified

Tags

Classifications

Public