all groups > visual studio .net debugging > june 2004 >
You're in the

visual studio .net debugging

group:

Visual Studio SQL Debugging



RE: Visual Studio SQL Debugging Isidoro Aguilera
6/4/2004 12:56:03 AM
visual studio .net debugging:
RE: Visual Studio SQL Debugging v-garych NO[at]SPAM online.microsoft.com
6/4/2004 8:27:33 AM
Hi Damon,

Do you have installed the SQL Server 2000 SP1 or SP2 *before* the
installment of the VS.NET?

Please make sure the MSSDI98.DLL in the following directories:
C:\Program Files\Microsoft SQL Server\MSSQL$SQL\Binn
C:\Program Files\Microsoft SQL Server\MSSQL\Binn
is from your Server 2000 SP1 or SP2(e.g. C:\sql2ksp1\x86\other\sdi
directory) instead of from the VS.NET(e.g. D:\Program Files\Microsoft
Visual Studio .NET\sqlserver) , you can check their versions to validate
that.


If the above apporach does not work or does not apply, there are a two more
troubleshooting steps that may be necessary to pursue. These include:

a) Re-registering SQLDBREG2.EXE and proxy\stub dll SQLDBG.DLL

b) Checking DCOM security configuration settings:
Run DCOMCNFG.EXE.
In the Distributed COM Configuration Properties window, select the Default
Security tab. Under Default Access Permissions, click Edit Default. If
group Everyone does not already have permissions, you may add it by
clicking
Add. Select the local machine name from the List Name From list. Select
Everyone and make sure that Type of Access is set to Allow Access. Then
click OK.

OR

If you prefer to limit debugging to specific users, you can add individual
domain user accounts (e.g. domain\account) with administrator privileges.
If you choose to add only domain accounts instead of Everyone, make sure to
add the SYSTEM account as well.
Switch to the Applications tab of the Distributed COM Configuration
Properties dialog.
Scroll through the Applications list and select SQLDBREG. Then click
Properties. Select the Identity tab and make sure that The interactive user
is selected as the user to run this application.
Click OK to close the dialog box.
Restart the SQL Server service.

Reboot your machine.


Additionally you can refer to the following MSDN link:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/htm
l/vxtbstroubleshootingsqldebuggingsetuperrormessageunabletostartsqldebugsess
ion.asp


Thanks!
Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Visual Studio SQL Debugging Damon
6/4/2004 10:34:08 AM
I'm trying to get SQL debugging up and running. We have remote debugging
working fine but when we try and use SQL debugging the following message
displays:

Unable to start SQL debug session. Ensure sqldbreg2.exe and proxy/stud DLL
sqldbg.dll are registered on this machine.

The server wtih SQL 2000 on it is Windows 2003, I've also verified that the
sqldbreg2.exe file is on the server.

Can anyone help with this?

Cheers

Damon

Re: Visual Studio SQL Debugging Damon
6/4/2004 9:26:13 PM
Hi Gary,

SQL Server 2000 was installed before the installation of VS.NET. The version
of SQL that is installed is SP3a.

I have MSSDI98.DLL in c:\program files\Micrsoft Visual Studio .NET
2003\sqlserver & E:\program files\microsoft SQL server\mssql\binn.

The version of both of these files is: 7.11.3077.0

I do not have a MSSQL$SQL\Binn directory.

I am running Windows 2003 server so when I typed DCOMCNFG.EXE into run it
opens Component Services, not DCOMCNFG.exe from Windows 2000 which your
instructions below seem to be for.

I did however look under DCOM Config in Windows 2003 and saw that SQLDBREG
identity is set to The interactive user.

The account that I am using has administrative rights on the server.

I have also checked out the troubleshooting article you mentioned below:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxtbstroubleshootingsqldebuggingsetuperrormessageunabletostartsqldebugsession.asp

I have now given the SQLDebugger user specific access to both of these
directories but the same message displays and I cannot debug.

What do you advise next?

Cheers

Damon

[quoted text, click to view]

Re: Visual Studio SQL Debugging v-garych NO[at]SPAM online.microsoft.com
6/5/2004 2:14:20 AM
Hi Damon,

Since you have installed the SQL Server 2K SP3, there would be a sql2ksp3
directory in your machine, please copy the SP3's MSSDI98.DLL from the
sql2ksp3 directory(e.g. C:\sql2ksp3\x86\other\sdi) to your E:\program
files\microsoft SQL server\mssql\binn, overwriting the VS.NET 's DLL.

Then if it does not work or does not apply, you can try to re-register
SQLDBREG2.EXE and proxy\stub dll SQLDBG.DLL.


Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Re: Visual Studio SQL Debugging Damon
6/7/2004 11:27:34 PM
Hi Gary,

I changed that DLL to be the DLL from the service pack did not work. Also
the DLL from the service pack is 7.11.2316.0 which is an older version than
the one that comes with visual studio .NET 7.11.3077.0.

I would like to try and re-register SQLDBREG2.EXE and proxy\stub dll
SQLDBG.DLL. Do you have some instructions for re-registering these on
Windows 2003 server? The only registratoin instructions I have found for
these is for Windows 2000 server.

Cheers

Damon

[quoted text, click to view]

Re: Visual Studio SQL Debugging v-garych NO[at]SPAM online.microsoft.com
6/8/2004 9:17:34 AM
Hi Damon,

[quoted text, click to view]
yes, it is as expected.

[quoted text, click to view]

The registratoin instructions under Windows 2003 server would be same as
Windows 2000 server, does it not work?


Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Re: Visual Studio SQL Debugging Damon
6/8/2004 10:03:34 PM
Hi Gary,

Cheers for that I was not registering the files correctly.

I have registered both SQLDBREG2.exe and SQLDB.DLL on my machine and on the
server. I have put the visual studio DLL back into the SQL bin directory and
it now works perfectly.

Thanks heaps for your help.

Damon

[quoted text, click to view]

Re: Visual Studio SQL Debugging v-garych NO[at]SPAM online.microsoft.com
6/9/2004 7:32:04 AM
Hi Damon,

I am very glad to know you can get your SQL debugging now :)


Good Luck!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
RE: Visual Studio SQL Debugging Randy
10/5/2005 12:00:00 AM
I have the same problem as Damon,
I have followed to the point where he r reregistered the dll's and his problem was resolved (lucky guy;)) only i run "regsvr32 mssdbi98.dll" and get "mssdi98.dll was loaded, but the DLLRegisterServer entry point was not found." error ...

Can anyone help?

From http://www.developmentnow.com/g/51_2004_6_0_0_281401/Visual-Studio-SQL-Debugging.htm

Posted via DevelopmentNow.com Groups
AddThis Social Bookmark Button