Post reply

Error 26073

  • January 7, 2013 at 5:00 am

    #272526

    Hello,

    We are also getting similar error on our SQL server in cluster environment

    Error 26073

    TCP connection closed but a child process of SQL Server may be holding a duplicate of the connection's socket. Consider enabling the TcpAbortiveClose SQL Server registry setting and restarting SQL Server. If the problem persists, contact Technical Support.

    Below articles suggest to install CUP 6 on SQL 2008 R2 and a hotfix on Windows 2008 R2

    http://support.microsoft.com/kb/2491214

    But we are already running on higher version than suggested in above article. Our server is running with SQL 2008 R2 SP1 and Windows server 2008 R2 SP1, still we are getting above error. Has anybody faced similar issue on SQL 2008 R2 SP1. Any suggestion would be appreciated.

    Thanks in advanced,

    SB

  • January 8, 2013 at 7:00 am

    #1574800

    Did you try any of the items in this article?

    http://support.microsoft.com/kb/307197

  • January 8, 2013 at 8:51 am

    #1574865

    Thanks for the reply SanDroid, but making these registry changes has been already suggested in the article

    http://support.microsoft.com/kb/2491214

    But it is applicable for SQL 2008 R2, where it also suggest to apply CUP 6 on it and our server is running with SQL 2008 R2 SP1 (i.e. higher version than suggested in the article). And also when this issue occurs our SQL box gets hang; So I am not sure about this work around and have not tried yet.

    Thanks,

    SB

  • January 8, 2013 at 9:20 am

    #1574890

    Still not clear if you enabled the registry setting and other items recomended in the article. They are not service pack specific.

    Check your cluster server IP and Port settings.

    This error is very specific to SQL server not being able to own the default listening port on the servers default IP Address.

    That would cause SQL server, and the OS, to hang like you mention.

  • January 9, 2013 at 6:34 am

    #1575211

    No, registry setting not enabled yet. I am not fully convinced with this work around yet. Are we sure enabling this setting would not cause any issue, are there any downsides of it. It’s not mentioned anywhere.

    Do you think extensive use of mirroring could cause this TCP issue.

    Thanks,

    SB

  • January 9, 2013 at 6:37 am

    #1575214

    Also we have checked server IP and Port settings, all are looks good. In fact server is running with these setting quite a while now and this issue occurred all of a sudden; there is no changes happened on this server.

    Thanks,

    SB

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

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