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: 0×50
Error: 17182, Severity: 16, State: 1.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0×50, status code 0×50
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0×50, status code 0×1.
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
- SQL Protocols. Microsft SQL Server Protocol Team. TDSSNIClient initialization failed with error 0×50, status code 0×50. Link.
Categories: SQL Errors, SQL Protocols
Named Pipes, SQL Error 17182