Post reply

SQL Server stops listening

  • May 22, 2003 at 1:59 pm

    #160116

    Our Production SQL Server recently out of blue stopped listening to any new connections. I tried to telnet to the port 1433 and found that the telnet was failing, but I could connect to the server using named pipes, then we restarted the machine, but I was unable to telnet to that port.

    Then I changed the listening port to a different number and then restarted the SQL Server and it worked.

    This happened againg last week after a month or so.

    I was not able to find any errors in the log files.

    Does anyone have an idea what may be wrong?

    Thanks

    Ravi.

  • May 22, 2003 at 2:03 pm

    #458258

    Sounds like there's wax in the network card. Take an ear bud and give it a clean.

    Sorry, a VERY lame attempt at humour. It's late

    Cheers,

    Crispin

    Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!

  • May 22, 2003 at 5:27 pm

    #458278

    Starting with the card isnt a bad idea - but did you lose total connectivity, or SQL just stop listening - could you still ping the box?

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

    Andy
    SQLAndy - My Blog!
    Connect with me on LinkedIn
    Follow me on Twitter

  • May 22, 2003 at 5:38 pm

    #458280

    I was able to ping and the machine was in a running state. I could open the Enterprise manager and view all the data etc.

    Ravi.

Viewing 4 posts - 1 through 3 (of 3 total)

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