Post reply

Sql server is not listening on TCP

  • August 16, 2007 at 1:37 pm

    #174292

    Hello,

     I'm having an issue with a J2EE app trying to connect to Sql 2005 (note: I also have Sql 2k installed on this same laptop).

     Now I have Sql 05 configured to listen on the default of port 1433 (verified via Sql Config Mngr). However the ErrorLog file in the Sql Server LOG directory does NOT show that it's listening on TCP.

     The log entry shows this :

       server SQL server listening on Shared Memory, Named Pipes, Rpc.

    but it does NOT show the normal log entries I see on other servers, for example :

    SQL server listening on TCP, Shared Memory, Named Pipes.<BR/>

    SQL server listening on 157.54.178.42:1433, 127.0.0.1:1433

     So what's going on ? Is there a conflict with the Sql 2k server manager that's running in my task bar ? I'm almost ready to just backup my sql files, uninstall sql 2000 and then rebuild Sql 2005.

    Thanks,

    Bob

  • August 16, 2007 at 2:26 pm

    #727494

    Is TCP disabled in Surface Area Config?



    A.J.
    DBA with an attitude

  • August 17, 2007 at 2:50 am

    #727570

    If you have SQL2K and SQL 2005 started at the same time on the same machine, they cannot listen both on 1433. One of the instance is probably listening on dynamic port. You can define a fixed port if you want.

    You can also check with a port scanner like tcpview a freeware from sysinternals.

  • August 17, 2007 at 8:31 am

    #727662

    Inh Sql Svr Config Mngr, TCP is in fact enabled. However, when I bring up Surface Are Config I get a nasty error saying "No Sql 2005 components found. Either no comps are installed or you are not the admin"

    I am definitely the admin user on my laptop. Should I rerun the sql 05 install ?

     

  • August 17, 2007 at 8:44 am

    #727664

    I changed sql 2005 to listen on port 5000 as a test and kept sql 2k on port 1433. I'm still having the problem.

    How do I tell if listening on a dynamic port ?

    thanks,

    Bob

  • August 19, 2007 at 3:20 am

    #727866

    It may be a stupid question, but you have installed sql 2005 as named instance ? If both are as default, you will have definitely a problem. The error you the is strange. Run a port scanner to make sure on which port sql is listening (if it is...).

  • August 20, 2007 at 1:47 am

    #727895

    Is your SQL Server Browser Service running?

    Andras

    Andras Belokosztolszki, MCPD, PhD
    GoldenGate Software

Viewing 7 posts - 1 through 6 (of 6 total)

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