FIX: SQL Debugger Stops WorkingLast reviewed: September 19, 1997Article ID: Q158978 |
The information in this article applies to:
SYMPTOMSAfter working for a while, the SQL Debugger starts to skip breakpoints set in SQL code. The Event Viewer log on the server reveals the following error message:
CreateDispatch failed (Class not registered). Check to make sure Automation manager is running on debugger machine. CAUSEThere is a bug in Autprx32.dll (version 4.00.2415) that shipped with Visual C++ Enterprise Edition, version 4.2, that causes leaks of thread local storage indices each time it completes a load and unload cycle. There is a per process limit of 64 thread local storage indices on Windows NT. While remote SQL debugging is in process, Autprx32.dll is loaded and unloaded on the server. It is unloaded each time the number of remote debugging sessions hits zero. The debugger starts to skip breakpoints set in SQL code after approximately 25 load/unload cycles of Autprx32.dll.
RESOLUTIONTo resolve this problem, stop and restart the SQL Server.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ version 5.0.
MORE INFORMATIONThis problem only happens during remote debugging (when Visual C++ and SQL Server reside on different computers). It doesn't happen during local debugging (when Visual C++ and SQL Server reside on the same computer).
Keywords : vcbuglist420 VCEntIss VCEntSQLDebug kberrmsg kbinterop Technology : kbMfc Version : 4.2 Platform : NT WINDOWS Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |