Error 26073

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » Error 26073

Error 26073

Rate Topic

Display Mode

Topic Options

Author

Message

santosh subhash bhosale

Posted Monday, January 07, 2013 5:00 AM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 11:12 AM
Points: 27, Visits: 241

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

Post #1403546

SanDroid

Posted Tuesday, January 08, 2013 7:00 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232, Visits: 1,046

Did you try any of the items in this article?

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

Post #1404222

santosh subhash bhosale

Posted Tuesday, January 08, 2013 8:51 AM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 11:12 AM
Points: 27, Visits: 241

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

Post #1404296

SanDroid

Posted Tuesday, January 08, 2013 9:20 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,232, Visits: 1,046

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.

Post #1404326

santosh subhash bhosale

Posted Wednesday, January 09, 2013 6:34 AM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 11:12 AM
Points: 27, Visits: 241

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

Post #1404737

santosh subhash bhosale

Posted Wednesday, January 09, 2013 6:37 AM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 11:12 AM
Points: 27, Visits: 241

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

Post #1404740

« Prev Topic | Next Topic »

Permissions