• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 590
  • Last Modified:

SQL Server 2000 - unable to debug

I get the following message when i try to debug using SQL Server 2000:

Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger on EMBRYONDEV02 (Error = 0x800401f3). Ensure that client-side components, such as SQLLE.DLL, are installed and registered on 8TT4M81. Debugging disabled for connection 125.

I tried copying over all of the necessary dll's: sqlle.dll, sqldbg.dll, mssdi98.dll, and sqldbreg2.exe to the binn directory, but still getting this error.  I've tried using this: http://msdn2.microsoft.com/en-us/library/aa292301(VS.71).aspx as a guide, but it hasn't worked and I still can't debug.  I have .net 2003 installed on the same computer.

I haven't been able to debug in over a year.
  • 2
1 Solution
Look through this article and see if anything applies:

KaporchAuthor Commented:
I found 2 sqlservr.exe on my computer, one in path c:\sqlksp4\x86 \binn and c:\program files\microsoft sql server\mssql\binn.  The sp4 has a date modified of 5/4/2005, the other 8/6/2000.  I think the sp4 was installed when I ran service pack 4 on my computer, but I'm not sure if I should delete one of them or copy the dll files to both directories.
KaporchAuthor Commented:
Actually, what I needed was to become adminstrator on my computer, and also not to use the anonymous login but synchronize my SQL Server password with the windows password.
PAQed with points refunded (500)

EE Admin

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now