debugger problems in query analyzer

I am receiving the folowing error when trying to use the stored procedure
debugger in query analyzer: [Microsoft][ODBC SQL Server Driver][SQL
Server]Unable to connect to debugger on [machinename] (Error = 0x800401f3).
Ensure that client-side components, such as SQLLE.DLL, are installed and
registered on [machinename]. Debugging disabled for connection 55.
This is using SqlServer 2000 installed on the same machine running windows
2000. I have read the troubleshooting document, and have verified that DCOM
is set up correctly and that all DLLs mentioned in the document are present
in their correct location and registered on the machine. The DLL mentioned in
the error, sqlle.dll, is only present on the machine under a vstudio6\common
folder and a vstudio8\common folder; the vsstudio6\common copy is the one
that is registered. This seems strange to me, as I would expect sqlle.dll to
be installed with other sqlserver tools and dll's, and not to depend upon
visual studio being installed upon the same machine. Is it possible that
installing vs has somehow replaced the original sqlle.dll? I know that
debugging did work in the past, although it has been several months since it
was last used, and it is possible that vs was installed during that time.
Anyway, any suggestions on how to fix this? I know that sp debuggung can be
done from vs, but would prefer to do it from query analyzer. I have system
administrator privileges on the machine and within Sqlserver. Thanks.
MunchingBill
MunchingBill (munchingbill@.newsgroups.nospam) writes:
>The DLL mentioned in
> the error, sqlle.dll, is only present on the machine under a
> vstudio6\common folder and a vstudio8\common folder; the
> vsstudio6\common copy is the one that is registered. This seems strange
> to me, as I would expect sqlle.dll to be installed with other sqlserver
> tools and dll's, and not to depend upon visual studio being installed
> upon the same machine.
This is also the SQLLE.DLL which is registered on my machine. SQL Debugging
seems to work on my machine.

> I know that debugging did work in the past, although it has been several
> months since it was last used, and it is possible that vs was installed
> during that time.
This is precisely why I have more or less completely abandoned the
SQL debugger. I used only occasionally, and it seemed that every time I
had to fight a battle to get it to work. That was mainly at work, where
I tried to debug on a common development server. I thought it would normally
work on a local server - but apparently I was wrong.
It's simply to easy to use debug SELECTs and PRINTs to make it worth
all the hassle with the debugger. If stuff are really hairly, the Profiler
can help too.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||Hello Bill,
I would like to know whether you are debuging a stored procedure from the
terminal client computer through a terminal server session.
You cannot debug a stored procedure from the terminal client computer
through a terminal server session.
For additional information about how to solve this problem, click the
following article number to view the article in the Microsoft Knowledge
Base:
280100 BUG: Transact-SQL Debugger Is Not Available Through Terminal Server
Session
Here also some articles for your reference
280101INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for
SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;280101
Hope it helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks for the reply. No, I am not using a terminal server. I am using Query
Analyzer from the same machine that hosts the SqlServer 200 instance. I have
read the documents you mentioned, but the problem persists. Any other ideas?
MunchingBill
"Wei Lu [MSFT]" wrote:

> Hello Bill,
> I would like to know whether you are debuging a stored procedure from the
> terminal client computer through a terminal server session.
> You cannot debug a stored procedure from the terminal client computer
> through a terminal server session.
> For additional information about how to solve this problem, click the
> following article number to view the article in the Microsoft Knowledge
> Base:
> 280100 BUG: Transact-SQL Debugger Is Not Available Through Terminal Server
> Session
> Here also some articles for your reference
> 280101INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for
> SQL Server 2000
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;280101
> Hope it helps.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hello Bill,
First, I would like to know whether you have applied the latest service
pack for SQL 2000.
How to obtain the latest SQL Server 2000 service pack
http://support.microsoft.com/?id=290211
Also, there is an article maybe helpful:
839280FIX: SQL debugging does not work in Visual Studio .NET after you
install Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?scid=kb;EN-US;839280
Second, please let me know if you have installed any anti-virus software or
firewall. If so, please disable those software and try to debug it again.
If you still could not debug the stored procedure, please let me get your
Application Event log for further troubleshoot.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Just want to say Hi, and I was wondering how everything is going. If
anything is unclear, please let me know. It is my pleasure to be of
assistance.
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
================================================== ===
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix
issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====