SQL Debugging

[Guest]

I am trying to debug stored procedures via VS.NET. I've set up the debugging components and made the necessary configurations (security, DCOM, etc.). I was able to start successfully debugging stored procs. It worked for a few hours, then, after VS.NET crashed (trying to do a search/replace in the stored proc), after restarting, I started getting an error message as follows, when I try to step into the stored proc:

"An old version of SQL debugging components found on machine running SQL Server "SROBINSON-W2K". Run remote debugging component install on the machine.
The program 'SQL Debugger: T-SQL' has exited with code 0 (0x0)."

Any help would be much appreciated.

 

[Tian Min Huang]

Hello,

Thanks for your post. As I understand, the problem you are facing is you
fails to debug stored procedure in VS .NET 2003. Please correct me if there
is any misunderstanding. I think more information is needed before moving
forward:

1. Where is the SQL Server, on local host or on remote machine?

2. DCOM must be set up to allow remote users to debug on server. Also in
some circumstances DCOM must be set up correctly to allow local SQL
Debugging.

Configuring DCOM for SQL Debugging
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/htm
l/vxtskconfiguringdcomforsqldebugging.asp

3. Is remote procedure call (RPC) service started?

4. Please check Server Event Logs (server where SQL Server is running) -
Application and System. This often gives us clues to what is causing the
failure.

5. Make sure that you have correct versions of T-SQL Debugger component
files.
Server components include Mssdi98.dll and Sqldbg.dll.
Client components include Sqldbreg.exe and Sqldbg.dll.

Please refer to the following KB article for troubleshooting:

INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for SQL
Server 2000
http://support.microsoft.com/?id=280101

INFO: Troubleshooting Tips for T-SQL Debugger in Visual Studio .NET
http://support.microsoft.com/?id=817178

I look forward to your response.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

 

[Guest]

I have tried all of the above. I configured DCOM, security, etc.
Like I mentioned, it WAS WORKING for a little while. I was stepping into the stored proc with the debugger. Then, it stopped working, and displays the error I mentioned in my first post ever since VS.NET crashed and I had to reboot. The event log shows nothing (I looked in the Application, Security, and System logs)

Thanks for your help.