0

Attempting to connect using the SQL Server Native Client 10.0 Results in the below error: Client Unable to establish connection Shared Memory Provider: No Process is on the other end of the pipe.

Forcing the connection to use TCP just changes the error to a TCP error with similar contents

Using the SQL Server Native Client 11.0 works fine, unfortunately the application I am trying to connect with does not give me that option as the built in SSIS Packages were built for SQL Server 2008.

I have never had this issue before with the same basic deployment scenario (SQL Server 2014 and Windows Server 2012 R2)

I have been googling the issue but all the issues I can find relate to general connection issues, not ones that only occur with the Native Client 10.0. I checked the listed solutions like checking the protocols are enabled, firewalls and services are running regardless and everything appears configured correctly which explains why the Native Client 11 works

No errors show up in Windows or SQL Event logs when this happens

I have also updated to the latest release of the SQL Native Client which has not helped

The same problem occurs no matter what software I initiate the connection from (e.g. SSAS, ODBC) nor what source computer (Local or Remote)

Has anyone else seen this or a similar issue before?

4
0

I Found the issue for this one, the owners of this server have removed all but TLS 1.2/AES encryption which isn't supported by the SQL Native Client 10.0

I was able to download an on-request hotfix from the below link which resolved the issue for me. https://support.microsoft.com/en-au/help/3135244/tls-1-2-support-for-microsoft-sql-server

If you need to determine which ciphers are available for a server you can check the registry or use a tool like IISCrypto https://www.nartac.com/Products/IISCrypto

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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