Post reply

Unable to connect to SQL 2005

  • January 8, 2006 at 11:27 am

    #67130

    Hello,

    We are using the following from a app server to try and connect to a SQL 2005 server: System.Data.SqlClient.SqlConnection

    The connection string looks like the following:

    "Persist Security Info=False;User ID=test;Password=test-123;Initial Catalog=testsb;Data Source=SQLDevDbTest01 "

    We get the following message:

    System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

    Any ideas?

     

  • January 8, 2006 at 12:07 pm

    #613438

    You need to open the surface area configuration tool and click the option for remote connections and then click local and remote connections option. Use bol 2005 for more dtails 

  • January 8, 2006 at 12:14 pm

    #613439

    Sorry - I should have included in my post that I already did that. The server is configured to allow Local and Remote connections over TCP/IP and named pipes.

  • January 8, 2006 at 12:21 pm

    #613440

    have you restarted the service?

  • January 8, 2006 at 1:05 pm

    #613443

    Yes;manually restarted each service as well as bounced the server.

  • January 9, 2006 at 2:19 am

    #613475

    Can you ping the server? Have you tried specifying IP-address instead of server name? Can you connect using TCP/IP? Is the server installed as default instance?

    --
    Chris Hedgate http://www.hedgate.net/
    Contributor to the Best of SQL Server Central volumes
    Articles: http://www.sqlservercentral.com/columnists/chedgate/

  • January 9, 2006 at 5:38 am

    #613505

    I was playing this morning with a SQL 2005 instance and I'd stopped the "SQL Service Broker" service and couldn't connect from my PC with a similar message.

    A long shot, and it assumes the server is healthy and SQL is running

    Cheers

  • January 9, 2006 at 8:25 am

    #613587

    Q: Can you ping the server?
    A: Yes
     
    Q: Have you tried specifying IP-address instead of server name?
    A: Yes
     
    Q: Can you connect using TCP/IP?
    A: Yes (tried w/query analyzer)
     
    Q: Is the server installed as default instance?
    A: Yes
     
     
     
     

  • January 9, 2006 at 8:34 am

    #613595

    I did not install service broker as part of the setup. I have not read anywhere where it is required to connect to the server from a client. Are you sayin it is needed?

     

  • January 9, 2006 at 8:42 am

    #613598

    Q: Have you tried specifying IP-address instead of server name?
    A: Sorry - thought we had tried it but had not. My developer just tried connecting his app via ip instead of by server name and it works. Any thoughts on why connecting by name would not work?

  • January 9, 2006 at 7:21 pm

    #613706

    When I experience similar problems I usually try to made an entry in the hosts file

    C:\WINDOWS\system32\drivers\etc\hosts and lmhosts

    Cheers,

    david russell

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply