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), encr...
milgo's avatar
milgo
Icon for Microsoft rankMicrosoft
Jan 21, 2026

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
    Jan 21, 2026

    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