The information in this article applies to:
BUG #: 18753 (SQLBUG_65) SYMPTOMSAfter experiencing a handled exception within SQL Server, if SQL Trace was in use and monitoring disconnect events at the time of the exception, SQL Server may generate further exceptions when allocating or freeing memory. The stack trace might include functions such as ntdll!RtlAllocateHeapSlowly, ntdll!RtlFreeHeap, or ntdll!RtlpCoalesceFreeBlocks. The server hangs after several such exceptions. When running under a debugger, a heap manager message is printed after SQL Server finishes handling the exception. For example, a heap message might be:
RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later: NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.STATUSMicrosoft has confirmed this to be a problem in SQL Server version 6.5. MORE INFORMATIONAdditional query words:
Keywords : SSrvAdmin SSrvErr_Log SSrvGPF kbbug6.50 kbSQLServ650bug |
Last Reviewed: November 3, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |