Re: SQL2k debugging broken/problem
- From: v-sguo@xxxxxxxxxxxxxxxxxxxx (Sophie Guo [MSFT])
- Date: Fri, 03 Jun 2005 12:32:12 GMT
Hello,
Many factors can cause the issue. For example,
1. DCOM Component is disabled.
2. Firewall existing between the client and the server.
I suggest that you perform the following steps:
1. Test to see if you can use Transact-SQL Debugger to debug the stored
procedure in another local SQL instance installed on another local
computer. Please make sure both computers locate in the same domain and no
firewall between them.
2. Install a new SQL instance on another Windows 2003 SP1 machine then
check if it can debug the stored procedure on another local computer.
3. Turn off any firewall installed on the client computer and the server.
Check the issue again.
4. Run dcomcnfg both on the client machine and the server when firewall is
turned off. Go to the Dcom Config properties under default properties.
Locate the check box stating "enable Distributed COM on this computer" and
check it if it isn't checked.
5. Refer to steps in the "Incorrect DCOM Permission Settings" in the
"Troubleshooting the Transact-SQL Debugger" topic in BOL to allow remote
users to attach the debugger to a process on the database server.
6. Follow these steps to manually install and register missing debugger
components when the server and client are running on different machines:
On the client:
1. Copy file sdiclnt.dll from the \x86\binn folder of your SQL Server 2000
CD-ROM to c:\program files\microsoft sql server\mssql\80\tools\binn, then
register it:
regsvr32 sdiclnt.dll
2. Create folder c:\program files\common files\microsoft shared\SQL
Debugging.
3. Copy the following files from \x86\other\sdi to c:\program files\common
files\microsoft shared\SQL Debugging:
sqldbg.dll
sqldbreg.exe
then, register the files:
regsvr32 sqldbg.dll
sqldbreg /RegServer
On the server:
1. Create folder c:\program files\common files\microsoft shared\SQL
Debugging.
2. Copy the following file from \x86\other\sdi to c:\program files\common
files\microsoft shared\SQL Debugging:
sqldbg.dll
then, register the file:
regsvr32 sqldbg.dll
3. Copy file mssdi98.dll from \x86\other\sdi to where sqlservr.exe resides
(e.g. c:\program files\microsoft sql server\mssql\binn)
4. Restart the SQL Server service
Reboot the computer.
7. If the issue still exists, disable the firewalll, then run
netstat -ano 5
while running the debugger.
Check the port is used by QA. Then open these ports on firewall.
Some customers resolved their issue by performing above steps. I hope the
information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
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.
.
- References:
- SQL2k debugging broken/problem
- From: Brad
- RE: SQL2k debugging broken/problem
- From: Sophie Guo [MSFT]
- Re: SQL2k debugging broken/problem
- From: Brad
- SQL2k debugging broken/problem
- Prev by Date: Re: Any help on sp_trace_getdata
- Next by Date: User-Defined string Functions Transact-SQL
- Previous by thread: Re: SQL2k debugging broken/problem
- Next by thread: More Remote tsql Debugging headaches.....
- Index(es):
Relevant Pages
|