Post reply

Error

  • March 23, 2009 at 5:49 am

    #129973

    Hi experts,

    While connecting to one of our server,i am getting errors like this.can anyone help me since it is a live one.

    TIA

    [font="Comic Sans MS"]+++BLADE+++[/font]:cool:

  • March 23, 2009 at 5:50 am

    #964332

    please check the attachment for error

    [font="Comic Sans MS"]+++BLADE+++[/font]:cool:

  • March 23, 2009 at 6:00 am

    #964338

    Is the SQL Service running? That's 2005's generic 'can't connect' error.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • March 23, 2009 at 6:11 am

    #964340

    Yes..........its still running

    [font="Comic Sans MS"]+++BLADE+++[/font]:cool:

  • March 23, 2009 at 6:12 am

    #964342

    Hi,

    Check whether you enabled TCP/IP of your database engine remote connections section.

    Go to SQL Server > Configuration tools > SQL Server 2005 Surface Area configuration

    Click on Surface Area configuration for Services and Connections.

    Go to Remote connections section of your database instance.

    Select option Local and Remote connections.

    Select Using both TCP/IP and named pipes.

    Apply.

    Restart your SQL Server service.

    It should work now.

    cheers,

  • March 23, 2009 at 6:13 am

    #964343

    Check whether you have enabled the remote connections..TPC IP & Named pipes.

  • March 23, 2009 at 6:14 am

    #964344

    Thanks TIRU....but i checked all and i didnt find any problems with that......i cant restart the service since its a live server.....will check as it got freed and confirm.......Thanks in advance

    Cheers

    [font="Comic Sans MS"]+++BLADE+++[/font]:cool:

  • March 23, 2009 at 6:19 am

    #964347

    Try giving port number with the connection string.

    Check using the machine name rather than IP Address.

  • March 23, 2009 at 6:20 am

    #964349

    Ratheesh,

    itz our 0.147 server....wht to do

    [font="Comic Sans MS"]+++BLADE+++[/font]:cool:

  • March 23, 2009 at 6:26 am

    #964354

    Hi RK,

    Alternately you check on which port your SQL Server instance is running. Default port is 1433. For security reasons, usually this port will be changed. So check your server port and add an exception to your local firewall to allow this port.

    cheers,

  • March 23, 2009 at 6:33 am

    #964357

    Are you using Windows Authentication? You could try to connect using both domain / sql authentication. If domain auth, make sure the accounts aren't locked out.

    Is this instance in the same domain as the user in case of domain auth?

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

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