The information in this article applies to:
SYMPTOMS
After installing both SQL Server and Visual Basic Enterprise Edition
on your local machine, you will be able to perform local SQL debugging.
When running the local SQL debugger after remote debugging (Visual Basic
and SQL Server reside on two different computers), the T-SQL debugger
starts to skip breakpoints set in the SQL stored procedure with the
following error message:
The Event Viewer log on the server reveals the following error message:
CAUSEWhen installing the T-SQL Debugger client-side component, Visual Basic will create several Registry keys for VBSDISERVR.SDIEVENT under HKEY_CLASSES_ROOT in the Registry. The \LocalServer32 key for VBSDISERVR.SDIEVENT's CLSID is one of them that is being used by the local SQL debugging. When doing remote debugging from another computer, this key is deleted and some other keys for inprocServer are created. If you do local SQL Debugging after a remote SQL debugging session has been performed, Automation Manager will not be able to find the \LocalServer32 key in the Registry, resulting in the above error. RESOLUTION
You can add the LocalServer32 key manually in REGEDT32.EXE to enable the
next local SQL debugging. However, this key will be deleted again after
another remote SQL debugging.
Steps to Add the LocalServer32 Key:
Q145679 : HOWTO: Use the Registry API to Save and Retrieve Setting STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATIONThis problem only occurs with local debugging. It doesn't happen during remote debugging. Additional query words: kbVBp500 kbVBp600 kbdse kbDSupport kbVBp kbVS97 KbRegistry kbAPI
Keywords : kbGrpVBDB |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |