Results 1 to 9 of 9
  1. #1
    Join Date
    Sep 2003
    Posts
    32

    Unhappy Unanswered: sql tcp/ip connection problems?

    Hi gang, I think i have a tough one here:

    I have a server that I've installed sql 2000 standard on Win2003 standard. I've applied sp3. When I run select @@version i get:

    Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
    Dec 17 2002 14:22:05
    Copyright (c) 1988-2003 Microsoft Corporation
    Standard Edition on Windows NT 5.2 (Build 3790: )

    I've re-applied sp3a, rebooted, and I still get the same thing, so I THINK this is the latest version.

    When I go to network config, network libraries, TCP/IP, the file is SSNETLIB.dll 8.0.766 2/19/2003, does that look right or should it be newer?

    I would just leave it alone, but I'm having problems connecting to the db after a reboot. I have to restart the sql service to get my web site to connect again. After it reboots, I cannot even create a ODBC connection to it (over TCP/IP), but I CAN connect to it with named pipes. Restart the sql service, and it works again. This server had MSDE installed on it previously, could that be a problem? I un-installed it before installing sql 2000 standard.

    Thanks
    Tommy

  2. #2
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    What was the error when connecting from website using Tcp/ip protocol.

    From SQL server server network utility ensure TCP/IP is enabled and same as in client network utility.
    Try to connect from SQLclient when unable to connect from website.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  3. #3
    Join Date
    Sep 2003
    Posts
    32
    Originally posted by Satya
    What was the error when connecting from website using Tcp/ip protocol.

    From SQL server server network utility ensure TCP/IP is enabled and same as in client network utility.
    Try to connect from SQLclient when unable to connect from website.
    Thanks for your help. The error is "access denied, bla bla bla".

    TCP/IP is enabled in both. Remember, restarting the sql service magically makes it start working again.

    I'm stumped on this one.

    Tommy

  4. #4
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    You should refer to sql server error logs & event viewer logs for this behaviour.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  5. #5
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Originally posted by tommy
    Thanks for your help. The error is "access denied, bla bla bla".
    That's a new error to me, I've never heard of it. All the ones that I've seen have error numbers and more descriptive text.

    On a more serious note, please post the exact text of the error message. Like cut and paste grade exact. That is the quickest route to allow us to help you find a solution.

    -PatP

  6. #6
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    I agree with Pat, few posts doesn't give much information rather referring that '.... this query doesn't work.... nothing happened...' terms are used.

    The best and quick response will get if originator supplies SQL & SP version used and exact error text.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  7. #7
    Join Date
    Sep 2003
    Posts
    32
    Originally posted by Pat Phelan
    That's a new error to me, I've never heard of it. All the ones that I've seen have error numbers and more descriptive text.

    On a more serious note, please post the exact text of the error message. Like cut and paste grade exact. That is the quickest route to allow us to help you find a solution.

    -PatP
    ok ok....

    Microsoft OLE DB Provider for ODBC Drivers error '80004005'
    [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

    I cannot connect remotey from EM, even if I use the sa un and pw.

    One error in event viewer:
    SuperSocket info: gethostbyname(MSAFD Tcpip [TCP/IP]) : Error 11004.

    I'm going over these KB's now to see if I can figure this out.
    http://support.microsoft.com/?id=328306
    http://support.microsoft.com/default...&Product=sql2k

    I'm wondering if this has something to do with MSDE previously being installed on this machine. There was a default instance and another named instance too. Maybe there is something in the registry trying to use port 1433.

    Thanks
    Tommy

  8. #8
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    For example, to test the SQL Server listening on port 1433 of the computer named "myhost", type:


    $ telnet myhost 1433
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  9. #9
    Join Date
    Mar 2004
    Posts
    4
    Originally posted by Satya
    For example, to test the SQL Server listening on port 1433 of the computer named "myhost", type:


    $ telnet myhost 1433
    Check the password you're using to connect with in the global.asa if you're using a connection string or for your ODBC connection.

    If you've changed the password to the account recently and just restarted SQL for the first time during the SP install, problems like this can begin.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •