SQL Server 2005 Connectivity problem from .NET -


I am unable to connect to .NET from SQL Server 2005. I'm getting the error "A network-related or example-specific error occurred when installing a connection to the SQL server. The server was not found or was not accessible. Verify that the name of the instance is correct and to configure SQL Server Remote Connection is configured for. (Provider: Named Pipes Provider, Error: 40 - Can not open connection to SQL Server) ". The strange thing is, I'm able to connect through a management studio using the same credentials (SQL Server Authentication).

My connection string is: server = server name; User ID = xxx; Password = xxx

I am using the 2005 Native Client.

Besides, I just realized that the management studio can not connect using the designated pipes, only TCP / IP.

Which protocol does ADO.NET ask to use?

SQL Server 2005 can not allow inbound pipe connections. It can be configured separately for the old SQL Server Protocol and the 2005 + Native Client.

(And yes, management studios will still be able to connect to remote databases if named pipes were rejected.)


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -