This article was previously published under Q307540
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 355451 (SHILOH_BUGS)
An ODBC application that uses the SQLPutData API may cause a leak of buffer pool memory with each invocation. This buffer pool memory cannot be reclaimed and over time may cause SQL Server to run out of buffer pool memory. This condition can cause the SQL Server program to stop responding (hang). One of the most visible symptoms of the problem is Error 17803 as seen in the SQL Server error log.
SQL Server 2000
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2.
The English version of this fix should have the following file attributes or later:
Version File name Platform ------------------------------------ 8.00.444 Sqlservr.exe i386
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
SQL Server 7.0
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
SQL Server 2000 This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
SQL Server 7.0 This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.
In SQL Server 2000, each invocation of SQLPutData results in a leak of buffer pool memory of approximately 8 K. In SQL Server 7.0 the leak of buffer pool memory is approximately 272 bytes. The only way to reclaim the memory is to restart SQL Server.
It is important to note that although a 17803 error message that occurs when a user connects is a symptom of this problem, the error message can also occur in other circumstances outside of the scope of this problem.