The April CTP was working well but both the June and Sept CTP seem to be having problems with connections outside the local machine. It does not seem to matter how the connection is to be established (from code, from SQL managment studio etc) the same error comes up repeatedly.
Cannot connect to SEPTCTP.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
Any suggestions besides rolling back to the April CTP (our current solution)?
Is the Named Pipes protocol enabled on server?On server machine, run SQL Server configuration manager,
open SQL Server Network Configurations and enable Named Pipes.
Or switch client to use TCP/IP protocol rather than Named Pipes.
Thanks,
Michael.
P.S. This seems to be general SQL question, you might
get better response in SQL Server Database Engine group,
rather than in this SSIS-specific group.|||I'm not sure why, but we needed to access remote servers with their IP address AND a specific non-standard port once we upgraded to the newest CTP. This seemed fine for our test applications (we're not releasing anything until the final version is released).
Josh|||
This should be fine, provided that client is also configured
to use TCP/IP protocol and appropriate port. But the error
indicates the connection is using Named Pipes protocol.
It seems like the connection or SQL Client defaults is not
configured properly.
I'm not really a pro in SQL Client configuration, forum
SQL Server Database Engine might have people more
knowlegable in this area.
The answer may depend on whether you are using OLEDB or
ADO.NET connection managed, and in former case - SQL Native
OLEDB provider or Microsoft OLEDB provider for SQL Server.
No comments:
Post a Comment