Some days ago i asked here why my debugger in query analyzer never stops at code when i tried to debug a sp. I found the same question to be asked here again and again without any decent answer.
I found out my problem and would like to share it here :
hhtp://support.microsoft.com/?kbid=328151
My sql server was updated with Service Pack 3 but the client wasn't updated.
What i did was to turn on debugging on server for "older" clients with:
exec dbo.sp_sdidebug 'legacy_on'
Hope this will help other ppl too.Thanks for the link!
Showing posts with label debugger. Show all posts
Showing posts with label debugger. Show all posts
Friday, February 24, 2012
Debugging problem
HI,
Running debugger on the server works like a charm, however, when my
developers try to doc the same thing from ther
desktop (with everything setup correctly), thety get the following error
--
Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on myserver (Error = 0x800706ba).
Ensure that client-side components, such as SQLDBREG.EXE, are installed and
registered on W02875.
Debugging disabled for connection 67.
---
Any idea
ThanksHi
Have you checked out
http://support.microsoft.com/defaul...b;en-us;817178,
http://support.microsoft.com/defaul...kb;en-us;839280 or
http://msdn.microsoft.com/library/d...
ols_5cfm.asp?
John
"SalamElias" wrote:
> HI,
> Running debugger on the server works like a charm, however, when my
> developers try to doc the same thing from ther
> desktop (with everything setup correctly), thety get the following error
> --
> Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> on myserver (Error = 0x800706ba).
> Ensure that client-side components, such as SQLDBREG.EXE, are installed an
d
> registered on W02875.
> Debugging disabled for connection 67.
> ---
> Any idea
> Thanks
Running debugger on the server works like a charm, however, when my
developers try to doc the same thing from ther
desktop (with everything setup correctly), thety get the following error
--
Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on myserver (Error = 0x800706ba).
Ensure that client-side components, such as SQLDBREG.EXE, are installed and
registered on W02875.
Debugging disabled for connection 67.
---
Any idea
ThanksHi
Have you checked out
http://support.microsoft.com/defaul...b;en-us;817178,
http://support.microsoft.com/defaul...kb;en-us;839280 or
http://msdn.microsoft.com/library/d...
ols_5cfm.asp?
John
"SalamElias" wrote:
> HI,
> Running debugger on the server works like a charm, however, when my
> developers try to doc the same thing from ther
> desktop (with everything setup correctly), thety get the following error
> --
> Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> on myserver (Error = 0x800706ba).
> Ensure that client-side components, such as SQLDBREG.EXE, are installed an
d
> registered on W02875.
> Debugging disabled for connection 67.
> ---
> Any idea
> Thanks
Sunday, February 19, 2012
debugging a Custom Data Processing Extension
How do I go about debugging a Custom Data Processing Extension written in VB
or C#? How do I tell the debugger which process to attach to?
--
-PeterPlease check RS books online:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_extend_dataproc_9plu.asp?frame=true
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"jpstewart" <jpstewart@.discussions.microsoft.com> wrote in message
news:F42133CD-B143-4E63-8461-0E6785EE8F5B@.microsoft.com...
> How do I go about debugging a Custom Data Processing Extension written in
> VB
> or C#? How do I tell the debugger which process to attach to?
> --
> -Peter
>
or C#? How do I tell the debugger which process to attach to?
--
-PeterPlease check RS books online:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_extend_dataproc_9plu.asp?frame=true
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"jpstewart" <jpstewart@.discussions.microsoft.com> wrote in message
news:F42133CD-B143-4E63-8461-0E6785EE8F5B@.microsoft.com...
> How do I go about debugging a Custom Data Processing Extension written in
> VB
> or C#? How do I tell the debugger which process to attach to?
> --
> -Peter
>
Debugging a .net application makes an sql server hang
Hello everyone,
I have been debugging a module I have coded using the VS.NET debugger. This
makes a call to a SQL 2000 database, and closes the connection, I then start
debugging after this point.
Someone has started to use a web application on a live sever which connects
to a SQL 2000 database, this database is a seperate server on a completly
different machine to the developing computer and DB.
However when I start debugging my application this live database hangs until
I stop debugging, does anyone have any idea why?
Many Thanks
PhilHi Phil
I tried following your post but it's a bit ambiguous, so I'm not 100% sure
what's exactly happening over there.. Anyhow, have you tried running the
"exec sp_who2" TSQL command to see if any connections are blocked whilst the
server appears hung? There are many scenarios where debugging can hang
applications, such as the application not draining cursors - perhaps your
application is doing that? Running sp_who2 will tell you if any connections
(spids) are blocked within the database engine. If youu find any blocked
connections, the next step is to analyse why the blocking connection is
hanging onto locks & fix that problem from there..
Regards,
Greg Linwood
SQL Server MVP
"Philip Poole" <philip@.dontreply.org> wrote in message
news:412628fb$0$193$db0fefd9@.news.zen.co.uk...
> Hello everyone,
> I have been debugging a module I have coded using the VS.NET debugger.
> This
> makes a call to a SQL 2000 database, and closes the connection, I then
> start
> debugging after this point.
> Someone has started to use a web application on a live sever which
> connects
> to a SQL 2000 database, this database is a seperate server on a completly
> different machine to the developing computer and DB.
> However when I start debugging my application this live database hangs
> until
> I stop debugging, does anyone have any idea why?
> Many Thanks
> Phil
>
>
I have been debugging a module I have coded using the VS.NET debugger. This
makes a call to a SQL 2000 database, and closes the connection, I then start
debugging after this point.
Someone has started to use a web application on a live sever which connects
to a SQL 2000 database, this database is a seperate server on a completly
different machine to the developing computer and DB.
However when I start debugging my application this live database hangs until
I stop debugging, does anyone have any idea why?
Many Thanks
PhilHi Phil
I tried following your post but it's a bit ambiguous, so I'm not 100% sure
what's exactly happening over there.. Anyhow, have you tried running the
"exec sp_who2" TSQL command to see if any connections are blocked whilst the
server appears hung? There are many scenarios where debugging can hang
applications, such as the application not draining cursors - perhaps your
application is doing that? Running sp_who2 will tell you if any connections
(spids) are blocked within the database engine. If youu find any blocked
connections, the next step is to analyse why the blocking connection is
hanging onto locks & fix that problem from there..
Regards,
Greg Linwood
SQL Server MVP
"Philip Poole" <philip@.dontreply.org> wrote in message
news:412628fb$0$193$db0fefd9@.news.zen.co.uk...
> Hello everyone,
> I have been debugging a module I have coded using the VS.NET debugger.
> This
> makes a call to a SQL 2000 database, and closes the connection, I then
> start
> debugging after this point.
> Someone has started to use a web application on a live sever which
> connects
> to a SQL 2000 database, this database is a seperate server on a completly
> different machine to the developing computer and DB.
> However when I start debugging my application this live database hangs
> until
> I stop debugging, does anyone have any idea why?
> Many Thanks
> Phil
>
>
Debugging a .net application makes an sql server hang
Hello everyone,
I have been debugging a module I have coded using the VS.NET debugger. This
makes a call to a SQL 2000 database, and closes the connection, I then start
debugging after this point.
Someone has started to use a web application on a live sever which connects
to a SQL 2000 database, this database is a seperate server on a completly
different machine to the developing computer and DB.
However when I start debugging my application this live database hangs until
I stop debugging, does anyone have any idea why?
Many Thanks
PhilHi Phil
I tried following your post but it's a bit ambiguous, so I'm not 100% sure
what's exactly happening over there.. Anyhow, have you tried running the
"exec sp_who2" TSQL command to see if any connections are blocked whilst the
server appears hung? There are many scenarios where debugging can hang
applications, such as the application not draining cursors - perhaps your
application is doing that? Running sp_who2 will tell you if any connections
(spids) are blocked within the database engine. If youu find any blocked
connections, the next step is to analyse why the blocking connection is
hanging onto locks & fix that problem from there..
Regards,
Greg Linwood
SQL Server MVP
"Philip Poole" <philip@.dontreply.org> wrote in message
news:412628fb$0$193$db0fefd9@.news.zen.co.uk...
> Hello everyone,
> I have been debugging a module I have coded using the VS.NET debugger.
> This
> makes a call to a SQL 2000 database, and closes the connection, I then
> start
> debugging after this point.
> Someone has started to use a web application on a live sever which
> connects
> to a SQL 2000 database, this database is a seperate server on a completly
> different machine to the developing computer and DB.
> However when I start debugging my application this live database hangs
> until
> I stop debugging, does anyone have any idea why?
> Many Thanks
> Phil
>
>
I have been debugging a module I have coded using the VS.NET debugger. This
makes a call to a SQL 2000 database, and closes the connection, I then start
debugging after this point.
Someone has started to use a web application on a live sever which connects
to a SQL 2000 database, this database is a seperate server on a completly
different machine to the developing computer and DB.
However when I start debugging my application this live database hangs until
I stop debugging, does anyone have any idea why?
Many Thanks
PhilHi Phil
I tried following your post but it's a bit ambiguous, so I'm not 100% sure
what's exactly happening over there.. Anyhow, have you tried running the
"exec sp_who2" TSQL command to see if any connections are blocked whilst the
server appears hung? There are many scenarios where debugging can hang
applications, such as the application not draining cursors - perhaps your
application is doing that? Running sp_who2 will tell you if any connections
(spids) are blocked within the database engine. If youu find any blocked
connections, the next step is to analyse why the blocking connection is
hanging onto locks & fix that problem from there..
Regards,
Greg Linwood
SQL Server MVP
"Philip Poole" <philip@.dontreply.org> wrote in message
news:412628fb$0$193$db0fefd9@.news.zen.co.uk...
> Hello everyone,
> I have been debugging a module I have coded using the VS.NET debugger.
> This
> makes a call to a SQL 2000 database, and closes the connection, I then
> start
> debugging after this point.
> Someone has started to use a web application on a live sever which
> connects
> to a SQL 2000 database, this database is a seperate server on a completly
> different machine to the developing computer and DB.
> However when I start debugging my application this live database hangs
> until
> I stop debugging, does anyone have any idea why?
> Many Thanks
> Phil
>
>
Debugging a .net application makes an sql server hang
Hello everyone,
I have been debugging a module I have coded using the VS.NET debugger. This
makes a call to a SQL 2000 database, and closes the connection, I then start
debugging after this point.
Someone has started to use a web application on a live sever which connects
to a SQL 2000 database, this database is a seperate server on a completly
different machine to the developing computer and DB.
However when I start debugging my application this live database hangs until
I stop debugging, does anyone have any idea why?
Many Thanks
Phil
Hi Phil
I tried following your post but it's a bit ambiguous, so I'm not 100% sure
what's exactly happening over there.. Anyhow, have you tried running the
"exec sp_who2" TSQL command to see if any connections are blocked whilst the
server appears hung? There are many scenarios where debugging can hang
applications, such as the application not draining cursors - perhaps your
application is doing that? Running sp_who2 will tell you if any connections
(spids) are blocked within the database engine. If youu find any blocked
connections, the next step is to analyse why the blocking connection is
hanging onto locks & fix that problem from there..
Regards,
Greg Linwood
SQL Server MVP
"Philip Poole" <philip@.dontreply.org> wrote in message
news:412628fb$0$193$db0fefd9@.news.zen.co.uk...
> Hello everyone,
> I have been debugging a module I have coded using the VS.NET debugger.
> This
> makes a call to a SQL 2000 database, and closes the connection, I then
> start
> debugging after this point.
> Someone has started to use a web application on a live sever which
> connects
> to a SQL 2000 database, this database is a seperate server on a completly
> different machine to the developing computer and DB.
> However when I start debugging my application this live database hangs
> until
> I stop debugging, does anyone have any idea why?
> Many Thanks
> Phil
>
>
I have been debugging a module I have coded using the VS.NET debugger. This
makes a call to a SQL 2000 database, and closes the connection, I then start
debugging after this point.
Someone has started to use a web application on a live sever which connects
to a SQL 2000 database, this database is a seperate server on a completly
different machine to the developing computer and DB.
However when I start debugging my application this live database hangs until
I stop debugging, does anyone have any idea why?
Many Thanks
Phil
Hi Phil
I tried following your post but it's a bit ambiguous, so I'm not 100% sure
what's exactly happening over there.. Anyhow, have you tried running the
"exec sp_who2" TSQL command to see if any connections are blocked whilst the
server appears hung? There are many scenarios where debugging can hang
applications, such as the application not draining cursors - perhaps your
application is doing that? Running sp_who2 will tell you if any connections
(spids) are blocked within the database engine. If youu find any blocked
connections, the next step is to analyse why the blocking connection is
hanging onto locks & fix that problem from there..
Regards,
Greg Linwood
SQL Server MVP
"Philip Poole" <philip@.dontreply.org> wrote in message
news:412628fb$0$193$db0fefd9@.news.zen.co.uk...
> Hello everyone,
> I have been debugging a module I have coded using the VS.NET debugger.
> This
> makes a call to a SQL 2000 database, and closes the connection, I then
> start
> debugging after this point.
> Someone has started to use a web application on a live sever which
> connects
> to a SQL 2000 database, this database is a seperate server on a completly
> different machine to the developing computer and DB.
> However when I start debugging my application this live database hangs
> until
> I stop debugging, does anyone have any idea why?
> Many Thanks
> Phil
>
>
Debugging "Stored procedure in T-SQL Debugger"
For 2 days already Stored procedures on SQL Server don`t work.
When debugging:
"ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL
mssdi98.dll, or one of the DLLs it references. Reason: 126(The specified
module could not be found.)."
Other object in database (tables,views) work OK.
What is going on?
Vladimir
Did you read the troubleshooting section in Books Online? I searched for below string and found the section:
"Cannot load the DLL"
Make sure you use the updated Books Online:
http://www.microsoft.com/SQL/techinf...00/default.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Majstor" <majstorv@.hotmail-removethis-.com> wrote in message news:O5q2UF0FEHA.1012@.TK2MSFTNGP11.phx.gbl...
> For 2 days already Stored procedures on SQL Server don`t work.
> When debugging:
> "ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL
> mssdi98.dll, or one of the DLLs it references. Reason: 126(The specified
> module could not be found.)."
> Other object in database (tables,views) work OK.
> What is going on?
> Vladimir
>
When debugging:
"ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL
mssdi98.dll, or one of the DLLs it references. Reason: 126(The specified
module could not be found.)."
Other object in database (tables,views) work OK.
What is going on?
Vladimir
Did you read the troubleshooting section in Books Online? I searched for below string and found the section:
"Cannot load the DLL"
Make sure you use the updated Books Online:
http://www.microsoft.com/SQL/techinf...00/default.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Majstor" <majstorv@.hotmail-removethis-.com> wrote in message news:O5q2UF0FEHA.1012@.TK2MSFTNGP11.phx.gbl...
> For 2 days already Stored procedures on SQL Server don`t work.
> When debugging:
> "ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL
> mssdi98.dll, or one of the DLLs it references. Reason: 126(The specified
> module could not be found.)."
> Other object in database (tables,views) work OK.
> What is going on?
> Vladimir
>
debugger question
Is there any good debugger program for SQL 2000 trigger and package?
Never did that to packages, but you can debug triggers if you debug a
stored procedure calling a DML which fires the trigger, the debugger
will automagically jump in.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Is there any third party application which can do the debugging?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1126593394.406063.45780@.g44g2000cwa.googlegro ups.com...
> Never did that to packages, but you can debug triggers if you debug a
> stored procedure calling a DML which fires the trigger, the debugger
> will automagically jump in.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
Never did that to packages, but you can debug triggers if you debug a
stored procedure calling a DML which fires the trigger, the debugger
will automagically jump in.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Is there any third party application which can do the debugging?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1126593394.406063.45780@.g44g2000cwa.googlegro ups.com...
> Never did that to packages, but you can debug triggers if you debug a
> stored procedure calling a DML which fires the trigger, the debugger
> will automagically jump in.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
Friday, February 17, 2012
debugger question
Is there any good debugger program for SQL 2000 trigger and package?Never did that to packages, but you can debug triggers if you debug a
stored procedure calling a DML which fires the trigger, the debugger
will automagically jump in.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Is there any third party application which can do the debugging?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1126593394.406063.45780@.g44g2000cwa.googlegroups.com...
> Never did that to packages, but you can debug triggers if you debug a
> stored procedure calling a DML which fires the trigger, the debugger
> will automagically jump in.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
stored procedure calling a DML which fires the trigger, the debugger
will automagically jump in.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Is there any third party application which can do the debugging?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1126593394.406063.45780@.g44g2000cwa.googlegroups.com...
> Never did that to packages, but you can debug triggers if you debug a
> stored procedure calling a DML which fires the trigger, the debugger
> will automagically jump in.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
debugger question
Is there any good debugger program for SQL 2000 trigger and package?Never did that to packages, but you can debug triggers if you debug a
stored procedure calling a DML which fires the trigger, the debugger
will automagically jump in.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Is there any third party application which can do the debugging?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1126593394.406063.45780@.g44g2000cwa.googlegroups.com...
> Never did that to packages, but you can debug triggers if you debug a
> stored procedure calling a DML which fires the trigger, the debugger
> will automagically jump in.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
stored procedure calling a DML which fires the trigger, the debugger
will automagically jump in.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Is there any third party application which can do the debugging?
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1126593394.406063.45780@.g44g2000cwa.googlegroups.com...
> Never did that to packages, but you can debug triggers if you debug a
> stored procedure calling a DML which fires the trigger, the debugger
> will automagically jump in.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
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.
================================================== ====
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.
================================================== ====
Debugger on remote machine
Looks like a permission issue. Check the permission of the
user connecting locally vs the user connecting remotely.
This might give you some clue.
HTH.
Obaid.
>--Original Message--
>We have a remote server (w 2000, sql 2000) where we can
debug stored procedures locally but cannot debug stored
procedures remotely. Has anyone encountered this?
>.
>It's the same user.
What I'm noticing is that when debugging is done localy, the debugger pause
s on the first line. All of the debugging icons are active. In profler ther
e are two calls to sp_sdidebug (the first passes a 'check', parm the second
passes an 'on' parm) and s
et implicit transactions statement. If you then press F5 the code executes.
In profiler the procedure is executed and then there is a call to sp_sdide
bug (passes an 'off' parm).
When debugging locally, the code appears to immediately execute and the debu
gging icons are grayed out. This is confirmed in profiler where there are t
he two calls to sp_sdidebug, the procedure is executed and there is the call
to sp_sdidebug with the of
f parameter. So the code appears to execute immediately rather than being pa
used, and the debugger is disabled.|||KB article 328151 had the solution to our problem. The T-SQL Debugger is tu
rned off for non-sp3 clients after you install sp3. We're having our develo
pers upgrade their client tools to sp3. You can also run sp_sdidebug 'legacy
_on' each time you reboot t
he server.
user connecting locally vs the user connecting remotely.
This might give you some clue.
HTH.
Obaid.
>--Original Message--
>We have a remote server (w 2000, sql 2000) where we can
debug stored procedures locally but cannot debug stored
procedures remotely. Has anyone encountered this?
>.
>It's the same user.
What I'm noticing is that when debugging is done localy, the debugger pause
s on the first line. All of the debugging icons are active. In profler ther
e are two calls to sp_sdidebug (the first passes a 'check', parm the second
passes an 'on' parm) and s
et implicit transactions statement. If you then press F5 the code executes.
In profiler the procedure is executed and then there is a call to sp_sdide
bug (passes an 'off' parm).
When debugging locally, the code appears to immediately execute and the debu
gging icons are grayed out. This is confirmed in profiler where there are t
he two calls to sp_sdidebug, the procedure is executed and there is the call
to sp_sdidebug with the of
f parameter. So the code appears to execute immediately rather than being pa
used, and the debugger is disabled.|||KB article 328151 had the solution to our problem. The T-SQL Debugger is tu
rned off for non-sp3 clients after you install sp3. We're having our develo
pers upgrade their client tools to sp3. You can also run sp_sdidebug 'legacy
_on' each time you reboot t
he server.
Debugger on remote machine
Looks like a permission issue. Check the permission of the
user connecting locally vs the user connecting remotely.
This might give you some clue.
HTH.
Obaid.
>--Original Message--
>We have a remote server (w 2000, sql 2000) where we can
debug stored procedures locally but cannot debug stored
procedures remotely. Has anyone encountered this?
>.
>
It's the same user.
What I'm noticing is that when debugging is done localy, the debugger pauses on the first line. All of the debugging icons are active. In profler there are two calls to sp_sdidebug (the first passes a 'check', parm the second passes an 'on' parm) and s
et implicit transactions statement. If you then press F5 the code executes. In profiler the procedure is executed and then there is a call to sp_sdidebug (passes an 'off' parm).
When debugging locally, the code appears to immediately execute and the debugging icons are grayed out. This is confirmed in profiler where there are the two calls to sp_sdidebug, the procedure is executed and there is the call to sp_sdidebug with the of
f parameter. So the code appears to execute immediately rather than being paused, and the debugger is disabled.
user connecting locally vs the user connecting remotely.
This might give you some clue.
HTH.
Obaid.
>--Original Message--
>We have a remote server (w 2000, sql 2000) where we can
debug stored procedures locally but cannot debug stored
procedures remotely. Has anyone encountered this?
>.
>
It's the same user.
What I'm noticing is that when debugging is done localy, the debugger pauses on the first line. All of the debugging icons are active. In profler there are two calls to sp_sdidebug (the first passes a 'check', parm the second passes an 'on' parm) and s
et implicit transactions statement. If you then press F5 the code executes. In profiler the procedure is executed and then there is a call to sp_sdidebug (passes an 'off' parm).
When debugging locally, the code appears to immediately execute and the debugging icons are grayed out. This is confirmed in profiler where there are the two calls to sp_sdidebug, the procedure is executed and there is the call to sp_sdidebug with the of
f parameter. So the code appears to execute immediately rather than being paused, and the debugger is disabled.
Debugger Interface Problem in QA
Hello,
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
Derek
I'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
Derek
I'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
Debugger Interface Problem in QA
Hello,
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
DerekI'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
DerekI'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
Marc
It sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
Marc
It sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
Debugger help
Could anyone please give me a quick head start on the debugger in SQL Query
Analyzer. I right click on my 'sp' and select debug. This shows my code in
the right pane. However I seem unable to step though. The only buttons
highlighted are 'Go' and the 2 breakpoint buttons. Only when I click 'go' d
o
the step through, step over, etc buttons become highlighted by which time it
is too late as my sp is already processing.Set a breakpoint at the beginning of the procedure then click 'Go'.
ML|||Hi
I think that if you click on the procedure declaration your buttons should
become active.
John
"Chubbly Geezer" wrote:
> Could anyone please give me a quick head start on the debugger in SQL Quer
y
> Analyzer. I right click on my 'sp' and select debug. This shows my code
in
> the right pane. However I seem unable to step though. The only buttons
> highlighted are 'Go' and the 2 breakpoint buttons. Only when I click 'go'
do
> the step through, step over, etc buttons become highlighted by which time
it
> is too late as my sp is already processing.
Analyzer. I right click on my 'sp' and select debug. This shows my code in
the right pane. However I seem unable to step though. The only buttons
highlighted are 'Go' and the 2 breakpoint buttons. Only when I click 'go' d
o
the step through, step over, etc buttons become highlighted by which time it
is too late as my sp is already processing.Set a breakpoint at the beginning of the procedure then click 'Go'.
ML|||Hi
I think that if you click on the procedure declaration your buttons should
become active.
John
"Chubbly Geezer" wrote:
> Could anyone please give me a quick head start on the debugger in SQL Quer
y
> Analyzer. I right click on my 'sp' and select debug. This shows my code
in
> the right pane. However I seem unable to step though. The only buttons
> highlighted are 'Go' and the 2 breakpoint buttons. Only when I click 'go'
do
> the step through, step over, etc buttons become highlighted by which time
it
> is too late as my sp is already processing.
Subscribe to:
Posts (Atom)