FIX: Replication AddSubscription Method Causes Handle Leak on Failure

Article translations Article translations
Article ID: 243740 - View products that this article applies to.
This article was previously published under Q243740
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56598 (SQLBUG_70)
Expand all | Collapse all


When the Replication AddSubscription method fails, 2-3 handle leaks are generated within the application that activates the method. This may cause a problem in a retry scenario where the AddSubscription method is called repeatedly until success is achieved.

All handles opened by an application are closed when the application stops. Therefore, when the application invoking the AddSubscription method detects an error with AddSubscription, the calling application could be coded to return a message and exit. The application is subsequently restarted after correcting the cause of the failure during AddSubscription.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


If the application using the AddSubscription method cannot be stopped for business reasons, consider activating the Addsubscription method from another process outside the business application to prevent the business application from suffering the handle leak.


Article ID: 243740 - Last Review: October 22, 2013 - Revision: 2.1
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix kbqfe KB243740

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from