Forum Discussion

StephanGee's avatar
StephanGee
Iron Contributor
Jan 14, 2026

Information Scanner - SQL connection fails

Hello everyone,

we are currently deploying the information scanner.

The issue appeared after the scanner was already installed successfully
SQL Server is running on a custom TCP port (49999), encrypted connection, and the scanner database is existing with the correct owner (service account). We also acquired the Entra token

 

Error

Failed to access scanner database. Verify the database is up and running and can be accessed by scanner service account and by the currently logged in user that executes the command.

Troubleshooting steps taken:

Diag show:

Invalid database schema or cannot access the scanner DB. To update the database schema, run Update-ScannerDatabase. Make sure all nodes run the same MIP client version. SQL error: Message Could not obtain information about Windows NT group/user 'Domain\scanaccount', error code 0x5.

Update-ScannerDatabase executed - same error

Login to SQL Servers are successful

 

SQL CMD:

sqlcmd -S SQL.company.de,4321 -E -N -Q "SELECT @@VERSION" ## Worked

 

Other configs:
Tried to reregister database multiple times / service account is sysadmin at SQL server (shared)
SQL DB Alias used instead of Port / SQL Browser did not work
Allowed everything through firewall on SQL server - still fail

 

4h of troubleshooting gone by - and i am stuck - what can i do next?

 

BR

Stephan

2 Replies

  • Hi Stephan!
    Could your SQL Service be running under a local account (LocalSystem / LocalService) or under an identity that lacks permission? When SQL runs under a local account, Windows principal resolution fails and 0x5 errors are expected. Typically the scanner relies on SQL validating Windows principals during schema validation and Update-ScannerDatabase. If SQL can’t resolve the domain account, schema checks likely fail. Tru running the SQL Server engine service should run under a domain account

    • StephanGee's avatar
      StephanGee
      Iron Contributor

      Forgot to reply with my answer - some OUs lack the right for authorized users to read user details. And my service account was in one of them. 
      Allowed the SQL computer account to read the user and it works. 

Resources