Named Pipes provider error for SDK on Sql Express

Automate and integrate using the SQL comparison API

Named Pipes provider error for SDK on Sql Express

Postby kawai » Thu Mar 11, 2010 5:39 pm

Hi there-

I'm running the .NET SQL Comparison SDK to automate data migrations between two databases on a local server. We are running against Sql Server Express 2005. When I attempt migration, I get a named pipes provider error:

"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)."

Relevant stack trace:

System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase) +332
System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData) +425
a.EndInvoke(IAsyncResult result) +0
w.a() +142
w.PopulateVersionInformation() +43
p.d() +53
p.b() +143
RedGate.SQLCompare.Engine.Database.RegisterForDataCompare(ConnectionProperties connectionProperties, Options options) +105


I've attempted to allow both TCP/IP and named pipes. What's additionally odd is that I am not having trouble connecting to the db with the same credentials when I use SQL Compare tool. Are they somehow connecting thru different ports/mechanisms?

Appreciate any help!
-Ka Wai
Posts: 3
Joined: Thu Mar 11, 2010 5:30 pm

Postby kawai » Thu Mar 11, 2010 6:54 pm


As it turns out, I had my connection string parser wrong so it wasn't even passing in the right conn string.
Posts: 3
Joined: Thu Mar 11, 2010 5:30 pm

Return to SQL Comparison SDK Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests