This article was previously published under Q243741
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56599 (SQLBUG_70)
When the Replication Initialize method fails, some handles are not closed properly, resulting in handle leaks within the application that activates the method. This may result in an increased memory consumption by this application and may result in abnormal termination of the process.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
File name Version Platform ------------------------------------ s70889i.exe 7.00.889 Intel s70889s.exe 7.00.889 Alpha
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.
All the handles opened by an application will be closed when the application stops. When the application detects an error with Initialize, the application could be stopped and restarted after fixing the problem that generated the failure.
If the application using the Initialize method cannot be stopped for business reasons, consider activating the method from outside the application.
Microsoft has confirmed this to be a problem in SQL Server 7.0.