Archive

Posts Tagged ‘Named Pipes’

Error 17182: SQL Service Error

May 30, 2010 Leave a comment

While fixing SQL Server configuration I ran into some rather interseting/unique errors:

Server local connection provider failed to listen on [ \\.\pipe\sql\query ]. Error: 0x50
Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x50, status code 0x50
Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x50, status code 0x1.

As the error indicates that it can’t listen to named piped connection.  [1] pointed me to looking if multiple instances were installed which was not the case.  But looking at the network protocols in SQL Server Manager found Named Pipes were disabled.  Enabled the Named Pipes *poof* went the error.

References

  1. SQL Protocols. Microsft SQL Server Protocol Team. TDSSNIClient initialization failed with error 0x50, status code 0x50. Link.

Windows Internal Database

May 25, 2010 Leave a comment

I haven’t ran into this much, as it seems it is optional component that can be installed when configuring Microsoft Windows.  The reason I say its optional is I don’t see this configured on every Windows 2008 Server.

Only seen it on handful servers so far; I have not had much chance or need to dig into it.  But this database stores information for “Active Directory Rights Management Services, Windows System Resource Manager, UDDI Services, and Windows SharePoint Services” [1].

It uses SQL Server Embedded/Internal/Express Edition and is not remotely manageable.  I had to deal with this instance of SQL Server because there seem to be some contention issue on a server running full version of SQL Server (sorry don’t remember details).

Anyhow this article is more on just this database exists, and how to connect to it.  Since this SQL Server instance is not remote manageable or TCP/IP manaageable; you have to use Named-pipe protocol to connect or all attempts at a connection will fail.

Server Connection name is “\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query” (without quotes).

Again please note this is local to server, you cannot manage this remotelly.

References

  1. Wikipedia. Windows Internal Database. Link.
  2. MSSQL Tips. Administrating your Windows Internal Database (MICROSOFT##SSEE). Link.
  3. Microsoft TechNet. How to migrate your WSUS WIndows Internal Database. Link.
  4. Microsoft KB. Uninstalling Windows Internal Database. Link.
%d bloggers like this: