Have Geek Brain

.Net client connecting to SQL 2005 with wrong provider

I am trying to connect to a database on a server from a development machine. The server has disabled the named pipes protocol. For some reason, the following error message appears from one developer window. The other two dev blocks can connect using the same code just fine (using tcp / ip). I tried to disable the named pipes protocol on the client and still get the following message.

The client was unable to establish due to an error during the connection initialization process before login. Possible reasons include the following: the client was trying to connect to an unsupported version of SQL Server. the server was too busy to accept new connections; or resource limitation (insufficient memory or maximum allowed connections) on the server. (Vendor: Named Pipes Vendor, Error: 0 - Process not included other end of pipe.)

Connection string used:

data source = SERVER_NAME; database = DATABASE_NAME; trusted_connection = yes; Timeout Time = 120;

Thanks for any ideas.

+1


a source to share


2 answers


From Win98 and ADO clients, we used forced TCPIP for the connection by adding this to the connection string: Network Library = dbmssocn;

In XP, you can do the same: Network Library = TCPIP;



Not sure if this is still supported or encouraged by M $ for ADO.Net connections.

+2


a source


You can try running the command "CliConfg.exe" and set the default protocol to "TCP / IP"



+1


a source






More articles:


All Articles