Problem using SQL Debugger

Hello. I have only used the Debugger a few times, mostly from within VB. At a
client site, we had used the Debugger from an XP SP2 machine to a
WindowsServer 2000 machine with SQL Server 2000 (unknown service pack level)
without problem. It had not been used for several months, during which time
the server was replaced with a Windows 2003 Server, SQL Server 2000 (SP2+,
but unsure of actual SP level).
The problems? We can't install the VB software on the server to enable the
debugger. So we thought we'd just use the Query Analyzer debugger instead.
But when we try to run it, we get the error: "The debugger interface is not
installed. Please re-run setup and select 'add components to your existing
installation' ..". We did rerun setup (on both the client and server) but
when we ran it on the client it already clearly had the debugger interface
option installed. Verifying files on the server I found that I could not
register the file 'mssdi98.dll', it would error "the file was loaded but the
entry point was not found'". This file was then re-copied from the SQL Server
CD and tried again, same error.
Is there some known issue using the debugger when SQL Server is on a Windows
Server 2003 machine? This stored procedure is particularly nasty and we have
no chance of debugging it without this interface. Please advise.
Thank you,
Brad Ashforth
Hello Brad,
mssdi98.dll is not a Activex control dll. Therefore, you could not regsiter
it by using regsvr32.
This issue can occur if SQLDebugger account does not have the porper
rights. Normally SQLDebugger has "Log on as a batch job" and "Deny logon
locally" user rights. Please run gpedit.msc and go to Computer
Configuration->Windows Settings->Security Settings->Local Policie->User
rights assignments to check if SQLDebugger account has the proper rights.
See: 818374 INF: SQL Server 2000 SP3 Creates a SQLDebugger Windows User
Account
http://support.microsoft.com/?id=818374
Also, the following article shall be a good reference
280101 INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for
SQL
http://support.microsoft.com/?id=280101
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner 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.
| Thread-Topic: Problem using SQL Debugger
| thread-index: AcVhOfWOQfF7UKMrR42/aEn39rd3uA==
| X-WBNR-Posting-Host: 71.113.19.127
| From: "=?Utf-8?B?QnJhZCBBc2hmb3J0aA==?=" <banospam@.nospam.nospam>
| Subject: Problem using SQL Debugger
| Date: Wed, 25 May 2005 07:56:41 -0700
| Lines: 25
| Message-ID: <5A3081B3-D52B-46B6-A2BF-E53C9BF35403@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.tools
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4469
| X-Tomcat-NG: microsoft.public.sqlserver.tools
|
| Hello. I have only used the Debugger a few times, mostly from within VB.
At a
| client site, we had used the Debugger from an XP SP2 machine to a
| WindowsServer 2000 machine with SQL Server 2000 (unknown service pack
level)
| without problem. It had not been used for several months, during which
time
| the server was replaced with a Windows 2003 Server, SQL Server 2000
(SP2+,
| but unsure of actual SP level).
|
| The problems? We can't install the VB software on the server to enable
the
| debugger. So we thought we'd just use the Query Analyzer debugger
instead.
| But when we try to run it, we get the error: "The debugger interface is
not
| installed. Please re-run setup and select 'add components to your
existing
| installation' ..". We did rerun setup (on both the client and server) but
| when we ran it on the client it already clearly had the debugger
interface
| option installed. Verifying files on the server I found that I could not
| register the file 'mssdi98.dll', it would error "the file was loaded but
the
| entry point was not found'". This file was then re-copied from the SQL
Server
| CD and tried again, same error.
|
| Is there some known issue using the debugger when SQL Server is on a
Windows
| Server 2003 machine? This stored procedure is particularly nasty and we
have
| no chance of debugging it without this interface. Please advise.
|
| Thank you,
|
| Brad Ashforth
|
|||Hi Peter. Thank you for your reply. I checked the machine in question and I
do not see a "SQLDebugger" account. Would this account have been created
automatically during the install? Or do I need to create it manually? I will
review the article you mention but am surprised to find this so difficult to
set up. Perhaps this will be easier in SQL2005?
Brad Ashforth
"Peter Yang [MSFT]" wrote:

> Hello Brad,
> mssdi98.dll is not a Activex control dll. Therefore, you could not regsiter
> it by using regsvr32.
> This issue can occur if SQLDebugger account does not have the porper
> rights. Normally SQLDebugger has "Log on as a batch job" and "Deny logon
> locally" user rights. Please run gpedit.msc and go to Computer
> Configuration->Windows Settings->Security Settings->Local Policie->User
> rights assignments to check if SQLDebugger account has the proper rights.
> See: 818374 INF: SQL Server 2000 SP3 Creates a SQLDebugger Windows User
> Account
> http://support.microsoft.com/?id=818374
> Also, the following article shall be a good reference
> 280101 INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for
> SQL
> http://support.microsoft.com/?id=280101
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner 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.
>
>
> --
> | Thread-Topic: Problem using SQL Debugger
> | thread-index: AcVhOfWOQfF7UKMrR42/aEn39rd3uA==
> | X-WBNR-Posting-Host: 71.113.19.127
> | From: "=?Utf-8?B?QnJhZCBBc2hmb3J0aA==?=" <banospam@.nospam.nospam>
> | Subject: Problem using SQL Debugger
> | Date: Wed, 25 May 2005 07:56:41 -0700
> | Lines: 25
> | Message-ID: <5A3081B3-D52B-46B6-A2BF-E53C9BF35403@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.tools
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4469
> | X-Tomcat-NG: microsoft.public.sqlserver.tools
> |
> | Hello. I have only used the Debugger a few times, mostly from within VB.
> At a
> | client site, we had used the Debugger from an XP SP2 machine to a
> | WindowsServer 2000 machine with SQL Server 2000 (unknown service pack
> level)
> | without problem. It had not been used for several months, during which
> time
> | the server was replaced with a Windows 2003 Server, SQL Server 2000
> (SP2+,
> | but unsure of actual SP level).
> |
> | The problems? We can't install the VB software on the server to enable
> the
> | debugger. So we thought we'd just use the Query Analyzer debugger
> instead.
> | But when we try to run it, we get the error: "The debugger interface is
> not
> | installed. Please re-run setup and select 'add components to your
> existing
> | installation' ..". We did rerun setup (on both the client and server) but
> | when we ran it on the client it already clearly had the debugger
> interface
> | option installed. Verifying files on the server I found that I could not
> | register the file 'mssdi98.dll', it would error "the file was loaded but
> the
> | entry point was not found'". This file was then re-copied from the SQL
> Server
> | CD and tried again, same error.
> |
> | Is there some known issue using the debugger when SQL Server is on a
> Windows
> | Server 2003 machine? This stored procedure is particularly nasty and we
> have
> | no chance of debugging it without this interface. Please advise.
> |
> | Thank you,
> |
> | Brad Ashforth
> |
>
|||Hello Brad,
The account shall be created automatically. You may want to install SP4 to
see if it fixes this problem
How to obtain the latest SQL Server 2000 service pack
http://support.microsoft.com/?kbid=290211
SQL Server 2000 Service Pack 4
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner 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.
| Thread-Topic: Problem using SQL Debugger
| thread-index: AcVmqY2l2xUiQ0dvSSeg0vsuxcXaRA==
| X-WBNR-Posting-Host: 71.113.19.127
| From: "=?Utf-8?B?QnJhZCBBc2hmb3J0aA==?=" <banospam@.nospam.nospam>
| References: <5A3081B3-D52B-46B6-A2BF-E53C9BF35403@.microsoft.com>
<eW4WbbbYFHA.2184@.TK2MSFTNGXA01.phx.gbl>
| Subject: RE: Problem using SQL Debugger
| Date: Wed, 1 Jun 2005 05:58:06 -0700
| Lines: 114
| Message-ID: <6FC66EE3-C581-4503-95A9-B1A467D93F32@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.tools
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4517
| X-Tomcat-NG: microsoft.public.sqlserver.tools
|
| Hi Peter. Thank you for your reply. I checked the machine in question and
I
| do not see a "SQLDebugger" account. Would this account have been created
| automatically during the install? Or do I need to create it manually? I
will
| review the article you mention but am surprised to find this so difficult
to
| set up. Perhaps this will be easier in SQL2005?
| --
| Brad Ashforth
|
|
| "Peter Yang [MSFT]" wrote:
|
| > Hello Brad,
| >
| > mssdi98.dll is not a Activex control dll. Therefore, you could not
regsiter
| > it by using regsvr32.
| >
| > This issue can occur if SQLDebugger account does not have the porper
| > rights. Normally SQLDebugger has "Log on as a batch job" and "Deny
logon
| > locally" user rights. Please run gpedit.msc and go to Computer
| > Configuration->Windows Settings->Security Settings->Local Policie->User
| > rights assignments to check if SQLDebugger account has the proper
rights.
| >
| > See: 818374 INF: SQL Server 2000 SP3 Creates a SQLDebugger Windows User
| > Account
| > http://support.microsoft.com/?id=818374
| >
| > Also, the following article shall be a good reference
| >
| > 280101 INF: Transact-SQL Debugger Limitations and Troubleshooting Tips
for
| > SQL
| > http://support.microsoft.com/?id=280101
| >
| > Regards,
| >
| > Peter Yang
| > MCSE2000/2003, MCSA, MCDBA
| > Microsoft Online Partner 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.
| >
| >
| >
| >
| > --
| > | Thread-Topic: Problem using SQL Debugger
| > | thread-index: AcVhOfWOQfF7UKMrR42/aEn39rd3uA==
| > | X-WBNR-Posting-Host: 71.113.19.127
| > | From: "=?Utf-8?B?QnJhZCBBc2hmb3J0aA==?=" <banospam@.nospam.nospam>
| > | Subject: Problem using SQL Debugger
| > | Date: Wed, 25 May 2005 07:56:41 -0700
| > | Lines: 25
| > | Message-ID: <5A3081B3-D52B-46B6-A2BF-E53C9BF35403@.microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.sqlserver.tools
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.tools:4469
| > | X-Tomcat-NG: microsoft.public.sqlserver.tools
| > |
| > | Hello. I have only used the Debugger a few times, mostly from within
VB.
| > At a
| > | client site, we had used the Debugger from an XP SP2 machine to a
| > | WindowsServer 2000 machine with SQL Server 2000 (unknown service pack
| > level)
| > | without problem. It had not been used for several months, during
which
| > time
| > | the server was replaced with a Windows 2003 Server, SQL Server 2000
| > (SP2+,
| > | but unsure of actual SP level).
| > |
| > | The problems? We can't install the VB software on the server to
enable
| > the
| > | debugger. So we thought we'd just use the Query Analyzer debugger
| > instead.
| > | But when we try to run it, we get the error: "The debugger interface
is
| > not
| > | installed. Please re-run setup and select 'add components to your
| > existing
| > | installation' ..". We did rerun setup (on both the client and server)
but
| > | when we ran it on the client it already clearly had the debugger
| > interface
| > | option installed. Verifying files on the server I found that I could
not
| > | register the file 'mssdi98.dll', it would error "the file was loaded
but
| > the
| > | entry point was not found'". This file was then re-copied from the
SQL
| > Server
| > | CD and tried again, same error.
| > |
| > | Is there some known issue using the debugger when SQL Server is on a
| > Windows
| > | Server 2003 machine? This stored procedure is particularly nasty and
we
| > have
| > | no chance of debugging it without this interface. Please advise.
| > |
| > | Thank you,
| > |
| > | Brad Ashforth
| > |
| >
| >
|