Unable to Connect to WSUS Database: Solved!
The saga continues… I still can’t get a successful ConfigMgr software update sync from my WSUS server. The latest issue is now I couldn’t access the Windows Internal Database to run any kind of maintenance script. When trying to connect either via sqlcmd or Management Studio via my logged in Windows credentials I was receiving the error system cannot find the file specified when attempting to connect with the server name nb:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query and the error login failed when connecting with the server name nb:\\.\pipe\MICROSOFT\##WID\tsql\query . Also, event ID 18456 – Token-based server access validation failed with an infrastructure error… was being generated in the Application event log along with Login failed for user…. server is in script upgrade mode in the C:\Windows\WID\Log\error.log.
Microsoft support suspected problems with the WID so we had to get SQL access to it. To anyone that’s trying to access the WSUS Windows Internal Database via SQL Server Management Studio Express and cannot get connected, here’s what I had to go through:
- Download and install SQL Server Management Studio Express.
- Open up SQL Server Configuration Manager and go to Native Client 11.0 Configuration -> Client Protocols and ensure TCP/IP is enabled.
- Connect to database on command line via sqlcmd -S np:\\.\pipe\MICROSOFT##WID\tsql\query
- Execute the query
PgSQL123SELECT session_id from sys.dm_Exec_requests where status <> 'sleeping' and session_id <> @@spidSELECT @@spid --This gets the allowed user SPIDsp_who 53 --The 53 was my @@spid. This is used to figure out the account that has access
For some reason, this fixed the connection issue and we were now able to connect!
Latest posts by Adam Bertram (see all)
- The Pester Book Challenge - September 4, 2017
- #PSBlogWeek: PowerShell Blogging for an Entire Week - August 23, 2017
- Be Wary of PowerShell’s OutputType Keyword - August 17, 2017