SQL Debugging Problems and Solutions
Feature Only in Enterprise Edition This feature is supported only in Visual C++ Enterprise Edition. For more information, see .
There are two important places to begin troubleshooting the SQL debugging process:
The Windows NT event log that contains messages for all activities on the computer.
The Application Log that is generated by MSDEVSDI on the Server machine has messages from the SDI50.DLL. Some of the more common SDI50.DLL messages are discussed below.
By default, SETUP installs the SQL Server to use both logs, but by using SQL Enterprise Manager or SQL SETUP, you can control whether SQL Server uses one or both of the logs.
This section covers the following topics and error messages:
How Can I Step from a PowerBuilder Application Into a Stored Procedure?
My Debugging SQL Server Was Disabled Because No User Is Logged On to NT 4.0
How Can I Tell If Ad-Hoc Updates to SQL Server System Catalogs Are Required?
The SQL Server Fails to Accept a Value Change While SQL Debugging
Error: SQL Server when started as service must not log on as System Account
Error: Could not find appropriate protocol for SDI to Debugger Communication
Error: Attempt to initialize OLE library failed. Check for correct versions of OLE DLLs
Error: An unexpected error ( %1 ) occurred. Debugging will be turned off for connection %2, %3
Error: Cannot do SQL debugging with this version of SQL Server...