SuperSocket Info: Bind failed errors have been found

  • Hi all,

    I have this error in my error log

    SuperSocket Info: Bind failed on TCP port xxxx

    I also have this entry in error log

    SQL server listening on Shared Memory, Named Pipes.

     My server network utility has Named Pipes followed by TCP/IP as enabled protocols

    and Client netwok utility has Tcp/Ip followed by Named Pipes as enabled protocols.

     

    What is wrong can any one point me this. What should I do?

    Any help is appreciated


    Helen
    --------------------------------
    Are you a born again. He is Jehova Jirah unto me

  • This was removed by the editor as SPAM

  • Do you have multiple instances? Or are you running smething else that could possibly use the SQL ports? Looks like a problem getting the port assigned to SQL Server from the OS.

  • Thank u Steve. I have only a single instance. I ran netstat -an to take a look at port usage. But could not figure out anything. Does it have any thing to do with dynamic port allocation

    Can this help.


    Helen
    --------------------------------
    Are you a born again. He is Jehova Jirah unto me

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

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