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.
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
- SQL Protocols. Microsft SQL Server Protocol Team. TDSSNIClient initialization failed with error 0x50, status code 0x50. Link.
SQL Canada (SQLCAN) 