Sqlcmd.exe - Shared Memory Provider: No Process Is On The Other End Of The Pipe

I have read numerous posts and articles about the error: Shared Memory Provider: No process is on the other end of the pipe. Communication link failure. ...including these: Err

Solution 1:

I finally figured it out thanks to this post. I had to add -a 32767 as a cmd-line param, presumably because of the massive size of my input script. Infernal sqlcmd could have given a more truthful error message instead of pretending it couldn't connect. The connection was never the problem. Anyway I hope this can help someone else.

Solution 2:

as suggested by @HerrimanCoder the -a 32767 parameter solves the issue, in my case I was running a script 2 scripts, 1.4GB and 1.6GB respectively.

I had a brand new installation for SQL server 2019, on my personal computer. It didn't have the Named Pipes and the TCP/IP enabled, I turned them on, tried again, failed, then added the parameter and executed smoothly.

Thanks for the help.

Solution 3:

I experienced the same, I tried enabling the TCP IP, Shared Memory and Name Pipes it did not help for me, what I followed is from this medium post

It says to add a parameter and it worked for me like a charm, checkout the complete steps.

Solution 4:

In my case, my application could not connect to the database instance even though I had no problem connecting via SSMS. It was simply because the user name I had in my connection string was not there in the user list in the database (someone removed it). SQL server should have simple said something like "Could not find the user name 'xx'" instead of this convoluted one!!