Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After an unexpected server shutdown due to a power failure, I can no longer connect to the internal windows database MICROSOFT##SSEE which is hosting Central Admin for my SBS 2008 server.

The log shows:

  Error: 18456, Severity: 14, State: 16.
  Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>]

I've tried to connect using the SQL Management studio (connecting to .pipemssql$microsoft##sseesqlquery) but no luck.

The SQL Server Configuration Manager doesn't show a entry for 'Protocols for MICROSOFT##SSEE' (but shows it for 2 other database hosted on the same SQL server 2005 Express edition.

I have tried to restore the master.ldf and mastlog.log files from a backup, but the issue persists.

share|improve this question
I'm doing a little tour of questions that relate to WID on Windows 2008 to note that Windows 2012 changes the pipe to \\.\pipe\MICROSOFT##WID\tsql\query – Richard Gadsden Dec 11 '12 at 15:01
A blog entry about Error: 18456 and the state codes: Troubleshooting Error 18456 seems to suggest the default database isn't accessible. – Brian Mar 16 '14 at 20:55

Have you tried using sqlcmd to connect to the service when it's running in single user mode?

Configure the service's startup options for '-m' and restart the service.

Then use this to connect from a command line:

sqlcmd -E -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Alternatively, this article can help you connect via SSMS in single user mode:

Check and see if 'NT AUTHORITY\NETWORK SERVICE' has a login to the instance with login rights.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.