BUG: SQL Debugging with SQL Server 7.0 Fails on Third Session in Visual InterDev (248046)
The information in this article applies to:
- Microsoft Visual InterDev 6.0
- Microsoft SQL Server 7.0
This article was previously published under Q248046 SYMPTOMS
You can perform two debug sessions on a Microsoft SQL Server 7.0 stored procedure, but an attempt to do so a third time does not succeed. On Windows NT, the Event Viewer displays the following error in the system log:
Access denied attempting to launch a DCOM Server using DefaultLaunchPermssion.
CAUSE
An error in a Visual InterDev client debugging component causes the failure.
RESOLUTION
To work around this problem, either:
- Restart Visual InterDev. This makes SQL Server debugging sessions successful again.
-or-
- Use Microsoft Visual C++ or Microsoft Visual Basic Enterprise Editions to debug SQL Server 7.0 stored procedures. They do not contain this flaw.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
SQL Server 6.5 does not expose this error in Visual InterDev, so this problem should not occur if you use SQL Server 6.5.
Modification Type: | Major | Last Reviewed: | 10/16/2002 |
---|
Keywords: | kbBug kbDSupport kbTSQL KB248046 |
---|
|