I 'm still getting the error:
"Cannot debug stored procedures because the SQL Server database is not setup
correctly or user does not have permission to execute master.sp_sdidebug."
I have configured DCOM on the remote sql server according tothe MSDN
article.
I have added SQLDebugger account to default permissions in dcom.
I have also given full access to Master DB for the user
SQLDebugger and all stored procedures full access.
Does anybody have any idea why is it still giving the above error.
TIA
TSHi
Did you check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
John
"test" wrote:
> I 'm still getting the error:
> "Cannot debug stored procedures because the SQL Server database is not setup
> correctly or user does not have permission to execute master.sp_sdidebug."
> I have configured DCOM on the remote sql server according tothe MSDN
> article.
> I have added SQLDebugger account to default permissions in dcom.
> I have also given full access to Master DB for the user
> SQLDebugger and all stored procedures full access.
> Does anybody have any idea why is it still giving the above error.
> TIA
> TS
>
>|||Hi John,
Thanks for the reply.
According to the support article
I ran EXECUTE sp_sdidebug 'LEGACY_ON'
on the remote DB server on QA.
I am afraid it still gives me the same error.
In the system log file and the Application log file of the remote server
following errors were recorded respectively.
DCOM was unable to communicate with the computer WS06 using any of the
configured protocols.
Error: 504, Severity: 16, State: 1
Unable to connect to debugger on MELB (Error = 0x800706ba). Ensure that
client-side components, such as SQLDBREG.EXE, are installed and registered
on WS06. Debugging disabled for connection 58.
JFI: SQLDBREG.EXE is found on client machine and executed too.
thanks
TS
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8A208FDB-FBC4-43C0-A94F-BC2792FCE9EB@.microsoft.com...
> Hi
> Did you check out
> http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
> John
> "test" wrote:
>> I 'm still getting the error:
>> "Cannot debug stored procedures because the SQL Server database is not
>> setup
>> correctly or user does not have permission to execute
>> master.sp_sdidebug."
>> I have configured DCOM on the remote sql server according tothe MSDN
>> article.
>> I have added SQLDebugger account to default permissions in dcom.
>> I have also given full access to Master DB for the user
>> SQLDebugger and all stored procedures full access.
>> Does anybody have any idea why is it still giving the above error.
>> TIA
>> TS
>>
>>|||Hi
This looks like:
http://support.microsoft.com/default.aspx?scid=kb;en-us;839280
Failing that you may want to check RPC is running
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servtools_5cfm.asp
and if you can use Query Analyser for debugging from this machine and others
as well as on the server.
John
"test" wrote:
> Hi John,
> Thanks for the reply.
> According to the support article
> I ran EXECUTE sp_sdidebug 'LEGACY_ON'
> on the remote DB server on QA.
> I am afraid it still gives me the same error.
>
> In the system log file and the Application log file of the remote server
> following errors were recorded respectively.
> DCOM was unable to communicate with the computer WS06 using any of the
> configured protocols.
> Error: 504, Severity: 16, State: 1
> Unable to connect to debugger on MELB (Error = 0x800706ba). Ensure that
> client-side components, such as SQLDBREG.EXE, are installed and registered
> on WS06. Debugging disabled for connection 58.
> JFI: SQLDBREG.EXE is found on client machine and executed too.
>
> thanks
> TS
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:8A208FDB-FBC4-43C0-A94F-BC2792FCE9EB@.microsoft.com...
> > Hi
> >
> > Did you check out
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
> >
> > John
> >
> > "test" wrote:
> >
> >> I 'm still getting the error:
> >>
> >> "Cannot debug stored procedures because the SQL Server database is not
> >> setup
> >> correctly or user does not have permission to execute
> >> master.sp_sdidebug."
> >>
> >> I have configured DCOM on the remote sql server according tothe MSDN
> >> article.
> >> I have added SQLDebugger account to default permissions in dcom.
> >>
> >> I have also given full access to Master DB for the user
> >> SQLDebugger and all stored procedures full access.
> >>
> >> Does anybody have any idea why is it still giving the above error.
> >>
> >> TIA
> >> TS
> >>
> >>
> >>
> >>
>
>|||John,
By any chance can the problem that I am getting is due to the fact that we
are on two different domains, i.e. sql server and my working machine?
thanks
TS
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:58CD11E4-5320-4107-9384-15ECECC78C3D@.microsoft.com...
> Hi
> This looks like:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;839280
> Failing that you may want to check RPC is running
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servtools_5cfm.asp
> and if you can use Query Analyser for debugging from this machine and
> others
> as well as on the server.
> John
> "test" wrote:
>> Hi John,
>> Thanks for the reply.
>> According to the support article
>> I ran EXECUTE sp_sdidebug 'LEGACY_ON'
>> on the remote DB server on QA.
>> I am afraid it still gives me the same error.
>>
>> In the system log file and the Application log file of the remote server
>> following errors were recorded respectively.
>> DCOM was unable to communicate with the computer WS06 using any of the
>> configured protocols.
>> Error: 504, Severity: 16, State: 1
>> Unable to connect to debugger on MELB (Error = 0x800706ba). Ensure that
>> client-side components, such as SQLDBREG.EXE, are installed and
>> registered
>> on WS06. Debugging disabled for connection 58.
>> JFI: SQLDBREG.EXE is found on client machine and executed too.
>>
>> thanks
>> TS
>>
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:8A208FDB-FBC4-43C0-A94F-BC2792FCE9EB@.microsoft.com...
>> > Hi
>> >
>> > Did you check out
>> >
>> > http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
>> >
>> > John
>> >
>> > "test" wrote:
>> >
>> >> I 'm still getting the error:
>> >>
>> >> "Cannot debug stored procedures because the SQL Server database is not
>> >> setup
>> >> correctly or user does not have permission to execute
>> >> master.sp_sdidebug."
>> >>
>> >> I have configured DCOM on the remote sql server according tothe MSDN
>> >> article.
>> >> I have added SQLDebugger account to default permissions in dcom.
>> >>
>> >> I have also given full access to Master DB for the user
>> >> SQLDebugger and all stored procedures full access.
>> >>
>> >> Does anybody have any idea why is it still giving the above error.
>> >>
>> >> TIA
>> >> TS
>> >>
>> >>
>> >>
>> >>
>>|||Hi
I don't think that should be a problem expecially if you have a trusted
relationship between the two domains (which I assume you have!). The second
article points to a post SP3a hotfix. As you don't give you version numbe I
assume that you are still on SP3a, so you could try loading service pack 4 on
both client and server.
Did you try debugging from Query Analyser?
John
"test" wrote:
> John,
> By any chance can the problem that I am getting is due to the fact that we
> are on two different domains, i.e. sql server and my working machine?
> thanks
> TS
>
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:58CD11E4-5320-4107-9384-15ECECC78C3D@.microsoft.com...
> > Hi
> >
> > This looks like:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;839280
> >
> > Failing that you may want to check RPC is running
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servtools_5cfm.asp
> >
> > and if you can use Query Analyser for debugging from this machine and
> > others
> > as well as on the server.
> >
> > John
> >
> > "test" wrote:
> >
> >> Hi John,
> >>
> >> Thanks for the reply.
> >>
> >> According to the support article
> >> I ran EXECUTE sp_sdidebug 'LEGACY_ON'
> >> on the remote DB server on QA.
> >> I am afraid it still gives me the same error.
> >>
> >>
> >> In the system log file and the Application log file of the remote server
> >> following errors were recorded respectively.
> >>
> >> DCOM was unable to communicate with the computer WS06 using any of the
> >> configured protocols.
> >>
> >> Error: 504, Severity: 16, State: 1
> >> Unable to connect to debugger on MELB (Error = 0x800706ba). Ensure that
> >> client-side components, such as SQLDBREG.EXE, are installed and
> >> registered
> >> on WS06. Debugging disabled for connection 58.
> >>
> >> JFI: SQLDBREG.EXE is found on client machine and executed too.
> >>
> >>
> >> thanks
> >> TS
> >>
> >>
> >> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> >> news:8A208FDB-FBC4-43C0-A94F-BC2792FCE9EB@.microsoft.com...
> >> > Hi
> >> >
> >> > Did you check out
> >> >
> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
> >> >
> >> > John
> >> >
> >> > "test" wrote:
> >> >
> >> >> I 'm still getting the error:
> >> >>
> >> >> "Cannot debug stored procedures because the SQL Server database is not
> >> >> setup
> >> >> correctly or user does not have permission to execute
> >> >> master.sp_sdidebug."
> >> >>
> >> >> I have configured DCOM on the remote sql server according tothe MSDN
> >> >> article.
> >> >> I have added SQLDebugger account to default permissions in dcom.
> >> >>
> >> >> I have also given full access to Master DB for the user
> >> >> SQLDebugger and all stored procedures full access.
> >> >>
> >> >> Does anybody have any idea why is it still giving the above error.
> >> >>
> >> >> TIA
> >> >> TS
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
Showing posts with label debugging. Show all posts
Showing posts with label debugging. Show all posts
Tuesday, March 20, 2012
Wednesday, March 7, 2012
Remote Debugging Problems w/ VS.net 2005 SP1
I have done through all the MSDN documentation and Googled everything I could
on the errors I am receiving about installing and configuring remote
debugging. I believe it is communications related. This is the scenario:
The Visual Studio 2005 Remote Debugger service is started on the remote
database server that I want to debug SQL code on as Local System. I am a
member of the local administrators group on that server and a member of the
sa role in SQL Server. I configured all the DCOM settings on both the remote
server and my local workstation, which is running XP SP2, and opened the
firewall exceptions on my workstation.
When I attempt to step into a procedure, the message " Unable to start T-SQL
Debugging. Could not attach to SQL Server process on 'daysqltest02'. Remote
calls are not allowed for this process." displays. If I manually run the
Visual Studio Remote Debugging Monitor interactively on the remote server,
when I attempt to step into a procedure, an entry is displayed in the monitor
that a connection from my workstation has been made and the following message
is displayed "Unable to start T-SQL Debugging. Could not connect to computer
'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on the
remote computer does not have permission to connect to this computer. Please
see Help for assistance."
Other people in my office on the same network or other networks can
successfully debug and there is not firewall between my workstation and the
remote server so I know it is something with my security or communications
configuration. Any assistance would be much appreciated. Thanks in advance.
Ken
Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Thanks for the information. I will definitely look at this product and would
appreciate a copy of the documentation for review.
With this product, can stored procedures be interactiely debugged?
"The DBA" wrote:
> Hi Parch,
> I suggest you try the tool SQL Ultimate Debugger:
> http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
> This tool is a post factum debugger and allows you to trace and
> debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
> waaaay better than the T-SQL debugger in VS. Also, since this software has
> not yet been officially realeased, I would not recommend (YET) to use it in
> a production environment.
> You can learn more about it here:
> http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
> want a copy of its documentation. shoot me an email and i can send it to
> you.
> I hope that helps.
>
>
> "parchk" <parchk@.discussions.microsoft.com> wrote in message
> news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>
on the errors I am receiving about installing and configuring remote
debugging. I believe it is communications related. This is the scenario:
The Visual Studio 2005 Remote Debugger service is started on the remote
database server that I want to debug SQL code on as Local System. I am a
member of the local administrators group on that server and a member of the
sa role in SQL Server. I configured all the DCOM settings on both the remote
server and my local workstation, which is running XP SP2, and opened the
firewall exceptions on my workstation.
When I attempt to step into a procedure, the message " Unable to start T-SQL
Debugging. Could not attach to SQL Server process on 'daysqltest02'. Remote
calls are not allowed for this process." displays. If I manually run the
Visual Studio Remote Debugging Monitor interactively on the remote server,
when I attempt to step into a procedure, an entry is displayed in the monitor
that a connection from my workstation has been made and the following message
is displayed "Unable to start T-SQL Debugging. Could not connect to computer
'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on the
remote computer does not have permission to connect to this computer. Please
see Help for assistance."
Other people in my office on the same network or other networks can
successfully debug and there is not firewall between my workstation and the
remote server so I know it is something with my security or communications
configuration. Any assistance would be much appreciated. Thanks in advance.
Ken
Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Thanks for the information. I will definitely look at this product and would
appreciate a copy of the documentation for review.
With this product, can stored procedures be interactiely debugged?
"The DBA" wrote:
> Hi Parch,
> I suggest you try the tool SQL Ultimate Debugger:
> http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
> This tool is a post factum debugger and allows you to trace and
> debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
> waaaay better than the T-SQL debugger in VS. Also, since this software has
> not yet been officially realeased, I would not recommend (YET) to use it in
> a production environment.
> You can learn more about it here:
> http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
> want a copy of its documentation. shoot me an email and i can send it to
> you.
> I hope that helps.
>
>
> "parchk" <parchk@.discussions.microsoft.com> wrote in message
> news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>
Remote debugging problems
I'm having remote debugging problems. Here is what I've done so far:
Set CLR Enabled to 1 on the target server and executed Reconfigure.
Setup the Visual Studio 2005 Remote Debugger as a service on the target server, log on set to the same user id/password that I'm using on the client machine. User is in administrator group on both machines.
Ensured that Remote Procedure Call and Remote Procedure Call Locator are started on the server, log on as Network Service.
Created a VS database project on the client and added a stored procudure, during this created a server connection to the target server.
Checked application and SQLCLR debugging for the connection.
Added code to insert a record.
Modified the test.sql script to execute the stored procedure.
Verified that I'm in the debug configuration and not a release configuration.
Set a break point on the first line of code.
Press F5.
In the Output window in VS I get:
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
Debugging script from project script file.
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
Auto-attach to process '[1288] [SQL] servername' on machine 'servername' succeeded.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SqlAccess.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'MyStoredProcedure', No symbols loaded.
Auto-attach to process '[1288] sqlservr.exe' on machine 'servername' succeeded.
At this point it appears that it hangs. I've let it sit for over an hour and it never gets to the breakpoint. Also, if I click the Stop Debugging button I get a dialog box saying "Debugging is being stopped but is not yet complete. You can force debugging to stop immediately, but any process being detached may be terminated instead. This window will automatically close when the debugging has completely stopped." with a button saying Stop Now. I've let this sit overnight to see if it disappears on its own and it does not.
Any help would be greatly appreciated.
John
A little more info. I set the project database permission level to external then granted the user permission and set the database to trustworthy on. I then truncated the table. The test.sql script file contains:
exec myStoredProcedure '20040522'
select * from mytable where period = '20040522'
I tried to debug again by pressing F5. It still appeared to hang so after a while I stopped it. This time I noticed that the select statement returned a row so it obviously executed without going into the debugger.
John
|||
Hi,
I am having the exact same problem. Is there any new information regarding this issue?
Thanks,
Rocco
|||Same here, it's been posted for quite some time and there are no responses for solutions. It seems to happen on a variety of systems, whether Vista, XP, or 2003, local or remote, and it would appear only a few of us are affected. There doesn't seem to be much interest in addressing the problem.|||Have you found a solution for this issue? I am also experiencing the same problem.|||I still have not found a solution. I'm back living in the era of writing debug messages to a debug table to try and debug stored procedures and have basically given up on using the CLR. It's very frustrating. I wouldn't wish this on anyone but if more people had the problem someone would probably come up with a solution.John
|||
What editions of VS do you use? and of SQL Server 2005? I hope they are not Express or Standard or lower than2005?
If no connection has been enabled for multi-tier debugging, or if the credentials are not sufficient for debugging, breakpoints set in SQL Server objects on the corresponding server will not be hit.[1]
Have you enabled multi-tier debugging by checking "Application Debugging" (on rigt-clicking db connection in Server Explorer)?
To successfully debug multi-tier applications, you must have enabled debugging for the application project [2]
Have you temporarily disabled SQl Server connection pooling
("Pooling = false" in connection string)? [3]
Do you have firewalls? Have you configured them on both machines [4]
Is the account under which VS2005 runs is the same as the account under which you connect to SQL server? [5]
Debugging automatic enabling is possible only if you use Windows Authentication for connectrion [ 6 ]
[1]
How to: Enable Multi-tier Debugging
http://msdn2.microsoft.com/en-us/library/ms165060(VS.80).aspx
[2]
How to: Enable SQL Debugging For a Project
http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx
[3]
SQL Debugging Limitations
http://msdn2.microsoft.com/en-us/library/kkyhd4yb(VS.80).aspx
[4]
How to: Enable SQL Server 2005 Debugging
http://msdn2.microsoft.com/en-us/library/s0fk6z6e(VS.80).aspx
[5]
How to: Set SQL Server Permissions for Debugging
http://msdn2.microsoft.com/en-us/library/w1bhybwz(VS.80).aspx
[ 6 ]
How to: Enable SQL Debugging For a Project
http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx
|||Hi John,
I had exactly the same problem: Debugging hangs right after auto-attaching to SQL Server.
Following procedure solves the problem for me:
In VS <Server Explorer> right click on the data connection you're using and click on "Allow SQL/CLR Debugging" to disallow debugging. Now re-allow it the same way ( answer popup question if managed threads should be stopped on the server with yes ).
At this moment debugging works for me again.
Not sure if this helps for you but I wanted to share my finding ...
HTH,
Karsten|||Rumtata,
Thanks very much for posting that workaround. I was having the same problem and your solution fixed the problem as well. I filed bug 287329 on the issue.
Remote debugging problems
I'm having remote debugging problems. Here is what I've done so far:
Set CLR Enabled to 1 on the target server and executed Reconfigure.
Setup the Visual Studio 2005 Remote Debugger as a service on the target server, log on set to the same user id/password that I'm using on the client machine. User is in administrator group on both machines.
Ensured that Remote Procedure Call and Remote Procedure Call Locator are started on the server, log on as Network Service.
Created a VS database project on the client and added a stored procudure, during this created a server connection to the target server.
Checked application and SQLCLR debugging for the connection.
Added code to insert a record.
Modified the test.sql script to execute the stored procedure.
Verified that I'm in the debug configuration and not a release configuration.
Set a break point on the first line of code.
Press F5.
In the Output window in VS I get:
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
Debugging script from project script file.
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
Auto-attach to process '[1288] [SQL] servername' on machine 'servername' succeeded.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SqlAccess.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'MyStoredProcedure', No symbols loaded.
Auto-attach to process '[1288] sqlservr.exe' on machine 'servername' succeeded.
At this point it appears that it hangs. I've let it sit for over an hour and it never gets to the breakpoint. Also, if I click the Stop Debugging button I get a dialog box saying "Debugging is being stopped but is not yet complete. You can force debugging to stop immediately, but any process being detached may be terminated instead. This window will automatically close when the debugging has completely stopped." with a button saying Stop Now. I've let this sit overnight to see if it disappears on its own and it does not.
Any help would be greatly appreciated.
John
A little more info. I set the project database permission level to external then granted the user permission and set the database to trustworthy on. I then truncated the table. The test.sql script file contains:
exec myStoredProcedure '20040522'
select * from mytable where period = '20040522'
I tried to debug again by pressing F5. It still appeared to hang so after a while I stopped it. This time I noticed that the select statement returned a row so it obviously executed without going into the debugger.
John
|||
Hi,
I am having the exact same problem. Is there any new information regarding this issue?
Thanks,
Rocco
|||Same here, it's been posted for quite some time and there are no responses for solutions. It seems to happen on a variety of systems, whether Vista, XP, or 2003, local or remote, and it would appear only a few of us are affected. There doesn't seem to be much interest in addressing the problem.|||Have you found a solution for this issue? I am also experiencing the same problem.|||I still have not found a solution. I'm back living in the era of writing debug messages to a debug table to try and debug stored procedures and have basically given up on using the CLR. It's very frustrating. I wouldn't wish this on anyone but if more people had the problem someone would probably come up with a solution.John
|||
What editions of VS do you use? and of SQL Server 2005? I hope they are not Express or Standard or lower than2005?
If no connection has been enabled for multi-tier debugging, or if the credentials are not sufficient for debugging, breakpoints set in SQL Server objects on the corresponding server will not be hit.[1]
Have you enabled multi-tier debugging by checking "Application Debugging" (on rigt-clicking db connection in Server Explorer)?
To successfully debug multi-tier applications, you must have enabled debugging for the application project [2]
Have you temporarily disabled SQl Server connection pooling
("Pooling = false" in connection string)? [3]
Do you have firewalls? Have you configured them on both machines [4]
Is the account under which VS2005 runs is the same as the account under which you connect to SQL server? [5]
Debugging automatic enabling is possible only if you use Windows Authentication for connectrion [ 6 ]
[1]
How to: Enable Multi-tier Debugging
http://msdn2.microsoft.com/en-us/library/ms165060(VS.80).aspx
[2]
How to: Enable SQL Debugging For a Project
http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx
[3]
SQL Debugging Limitations
http://msdn2.microsoft.com/en-us/library/kkyhd4yb(VS.80).aspx
[4]
How to: Enable SQL Server 2005 Debugging
http://msdn2.microsoft.com/en-us/library/s0fk6z6e(VS.80).aspx
[5]
How to: Set SQL Server Permissions for Debugging
http://msdn2.microsoft.com/en-us/library/w1bhybwz(VS.80).aspx
[ 6 ]
How to: Enable SQL Debugging For a Project
http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx
|||Hi John,
I had exactly the same problem: Debugging hangs right after auto-attaching to SQL Server.
Following procedure solves the problem for me:
In VS <Server Explorer> right click on the data connection you're using and click on "Allow SQL/CLR Debugging" to disallow debugging. Now re-allow it the same way ( answer popup question if managed threads should be stopped on the server with yes ).
At this moment debugging works for me again.
Not sure if this helps for you but I wanted to share my finding ...
HTH,
Karsten|||Rumtata,
Thanks very much for posting that workaround. I was having the same problem and your solution fixed the problem as well. I filed bug 287329 on the issue.
Remote debugging problems
I'm having remote debugging problems. Here is what I've done so far:
Set CLR Enabled to 1 on the target server and executed Reconfigure.
Setup the Visual Studio 2005 Remote Debugger as a service on the target server, log on set to the same user id/password that I'm using on the client machine. User is in administrator group on both machines.
Ensured that Remote Procedure Call and Remote Procedure Call Locator are started on the server, log on as Network Service.
Created a VS database project on the client and added a stored procudure, during this created a server connection to the target server.
Checked application and SQLCLR debugging for the connection.
Added code to insert a record.
Modified the test.sql script to execute the stored procedure.
Verified that I'm in the debug configuration and not a release configuration.
Set a break point on the first line of code.
Press F5.
In the Output window in VS I get:
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
Debugging script from project script file.
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
Auto-attach to process '[1288] [SQL] servername' on machine 'servername' succeeded.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SqlAccess.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'MyStoredProcedure', No symbols loaded.
Auto-attach to process '[1288] sqlservr.exe' on machine 'servername' succeeded.
At this point it appears that it hangs. I've let it sit for over an hour and it never gets to the breakpoint. Also, if I click the Stop Debugging button I get a dialog box saying "Debugging is being stopped but is not yet complete. You can force debugging to stop immediately, but any process being detached may be terminated instead. This window will automatically close when the debugging has completely stopped." with a button saying Stop Now. I've let this sit overnight to see if it disappears on its own and it does not.
Any help would be greatly appreciated.
JohnA little more info. I set the project database permission level to external then granted the user permission and set the database to trustworthy on. I then truncated the table. The test.sql script file contains:
exec myStoredProcedure '20040522'
select * from mytable where period = '20040522'
I tried to debug again by pressing F5. It still appeared to hang so after a while I stopped it. This time I noticed that the select statement returned a row so it obviously executed without going into the debugger.
John|||
Hi,
I am having the exact same problem. Is there any new information regarding this issue?
Thanks,
Rocco
|||Same here, it's been posted for quite some time and there are no responses for solutions. It seems to happen on a variety of systems, whether Vista, XP, or 2003, local or remote, and it would appear only a few of us are affected. There doesn't seem to be much interest in addressing the problem.|||Have you found a solution for this issue? I am also experiencing the same problem.|||I still have not found a solution. I'm back living in the era of writing debug messages to a debug table to try and debug stored procedures and have basically given up on using the CLR. It's very frustrating. I wouldn't wish this on anyone but if more people had the problem someone would probably come up with a solution.John|||
What editions of VS do you use? and of SQL Server 2005? I hope they are not Express or Standard or lower than2005?
If no connection has been enabled for multi-tier debugging, or if the credentials are not sufficient for debugging, breakpoints set in SQL Server objects on the corresponding server will not be hit.[1]
Have you enabled multi-tier debugging by checking "Application Debugging" (on rigt-clicking db connection in Server Explorer)?
To successfully debug multi-tier applications, you must have enabled debugging for the application project [2]
Have you temporarily disabled SQl Server connection pooling
("Pooling = false" in connection string)? [3]
Do you have firewalls? Have you configured them on both machines [4]
Is the account under which VS2005 runs is the same as the account under which you connect to SQL server? [5]
Debugging automatic enabling is possible only if you use Windows Authentication for connectrion [ 6 ]
[1]
How to: Enable Multi-tier Debugging
http://msdn2.microsoft.com/en-us/library/ms165060(VS.80).aspx
[2]
How to: Enable SQL Debugging For a Project
http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx
[3]
SQL Debugging Limitations
http://msdn2.microsoft.com/en-us/library/kkyhd4yb(VS.80).aspx
[4]
How to: Enable SQL Server 2005 Debugging
http://msdn2.microsoft.com/en-us/library/s0fk6z6e(VS.80).aspx
[5]
How to: Set SQL Server Permissions for Debugging
http://msdn2.microsoft.com/en-us/library/w1bhybwz(VS.80).aspx
[ 6 ]
How to: Enable SQL Debugging For a Project
http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx
|||Hi John,
I had exactly the same problem: Debugging hangs right after auto-attaching to SQL Server.
Following procedure solves the problem for me:
In VS <Server Explorer> right click on the data connection you're using and click on "Allow SQL/CLR Debugging" to disallow debugging. Now re-allow it the same way ( answer popup question if managed threads should be stopped on the server with yes ).
At this moment debugging works for me again.
Not sure if this helps for you but I wanted to share my finding ...
HTH,
Karsten|||Rumtata,
Thanks very much for posting that workaround. I was having the same problem and your solution fixed the problem as well. I filed bug 287329 on the issue.
Remote debugging problems
I'm having remote debugging problems. Here is what I've done so far:
Set CLR Enabled to 1 on the target server and executed Reconfigure.
Setup the Visual Studio 2005 Remote Debugger as a service on the target server, log on set to the same user id/password that I'm using on the client machine. User is in administrator group on both machines.
Ensured that Remote Procedure Call and Remote Procedure Call Locator are started on the server, log on as Network Service.
Created a VS database project on the client and added a stored procudure, during this created a server connection to the target server.
Checked application and SQLCLR debugging for the connection.
Added code to insert a record.
Modified the test.sql script to execute the stored procedure.
Verified that I'm in the debug configuration and not a release configuration.
Set a break point on the first line of code.
Press F5.
In the Output window in VS I get:
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
Debugging script from project script file.
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
The thread 'servername [55]' (0x14e0) has exited with code 0 (0x0).
Auto-attach to process '[1288] [SQL] servername' on machine 'servername' succeeded.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SqlAccess.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'sqlservr.exe' (Managed): Loaded 'MyStoredProcedure', No symbols loaded.
Auto-attach to process '[1288] sqlservr.exe' on machine 'servername' succeeded.
At this point it appears that it hangs. I've let it sit for over an hour and it never gets to the breakpoint. Also, if I click the Stop Debugging button I get a dialog box saying "Debugging is being stopped but is not yet complete. You can force debugging to stop immediately, but any process being detached may be terminated instead. This window will automatically close when the debugging has completely stopped." with a button saying Stop Now. I've let this sit overnight to see if it disappears on its own and it does not.
Any help would be greatly appreciated.
John
A little more info. I set the project database permission level to external then granted the user permission and set the database to trustworthy on. I then truncated the table. The test.sql script file contains:
exec myStoredProcedure '20040522'
select * from mytable where period = '20040522'
I tried to debug again by pressing F5. It still appeared to hang so after a while I stopped it. This time I noticed that the select statement returned a row so it obviously executed without going into the debugger.
John
|||
Hi,
I am having the exact same problem. Is there any new information regarding this issue?
Thanks,
Rocco
|||Same here, it's been posted for quite some time and there are no responses for solutions. It seems to happen on a variety of systems, whether Vista, XP, or 2003, local or remote, and it would appear only a few of us are affected. There doesn't seem to be much interest in addressing the problem.|||Have you found a solution for this issue? I am also experiencing the same problem.|||I still have not found a solution. I'm back living in the era of writing debug messages to a debug table to try and debug stored procedures and have basically given up on using the CLR. It's very frustrating. I wouldn't wish this on anyone but if more people had the problem someone would probably come up with a solution.John
|||
What editions of VS do you use? and of SQL Server 2005? I hope they are not Express or Standard or lower than2005?
If no connection has been enabled for multi-tier debugging, or if the credentials are not sufficient for debugging, breakpoints set in SQL Server objects on the corresponding server will not be hit.[1]
Have you enabled multi-tier debugging by checking "Application Debugging" (on rigt-clicking db connection in Server Explorer)?
To successfully debug multi-tier applications, you must have enabled debugging for the application project [2]
Have you temporarily disabled SQl Server connection pooling
("Pooling = false" in connection string)? [3]
Do you have firewalls? Have you configured them on both machines [4]
Is the account under which VS2005 runs is the same as the account under which you connect to SQL server? [5]
Debugging automatic enabling is possible only if you use Windows Authentication for connectrion [ 6 ]
[1]
How to: Enable Multi-tier Debugging
http://msdn2.microsoft.com/en-us/library/ms165060(VS.80).aspx
[2]
How to: Enable SQL Debugging For a Project
http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx
[3]
SQL Debugging Limitations
http://msdn2.microsoft.com/en-us/library/kkyhd4yb(VS.80).aspx
[4]
How to: Enable SQL Server 2005 Debugging
http://msdn2.microsoft.com/en-us/library/s0fk6z6e(VS.80).aspx
[5]
How to: Set SQL Server Permissions for Debugging
http://msdn2.microsoft.com/en-us/library/w1bhybwz(VS.80).aspx
[ 6 ]
How to: Enable SQL Debugging For a Project
http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx
|||Hi John,
I had exactly the same problem: Debugging hangs right after auto-attaching to SQL Server.
Following procedure solves the problem for me:
In VS <Server Explorer> right click on the data connection you're using and click on "Allow SQL/CLR Debugging" to disallow debugging. Now re-allow it the same way ( answer popup question if managed threads should be stopped on the server with yes ).
At this moment debugging works for me again.
Not sure if this helps for you but I wanted to share my finding ...
HTH,
Karsten|||Rumtata,
Thanks very much for posting that workaround. I was having the same problem and your solution fixed the problem as well. I filed bug 287329 on the issue.
Remote Debugging in SSIS ?
Hello
I've just heard that Remote Debugging should be possible in SSIS, but how ?
Some of the projects we run require a lot of memory and it's sometimes slow to debug on the local machine ?
Yes i know i can reduce the input rows, but in some cases i need all the data for testing.
Does anyone know how to remote debug ?
Do you have Visual Studio installed?
-Satya SKJ
SQL Server MVP
|||Yes|||And then ?|||cgpl,
Just to clarify, by remote debugging I assume you mean that you want to make a package execute on a remote machine whilst seeing things turn green/yellow/red on your local machine. Is that correct?
As far as I know, that isn't possible. But don't take my word for it. Where did you hear that it WAS possible?
-Jamie
|||green/yellow/red yes
We had a meeting with Kevin Cox from Microsoft who told that remote debugging was possible (the way i understood it). Don't know if you know him, but he told that he would look in to it.
|||No, I haven't heard of Kevin. if you hear anything back I'd be keen to hear it as well.
TIA
-Jamie
|||SSIS does not implement remote debugging. It was considered, but it was too costly to do. Maybe in the next version, if we'll have time.|||If possible, core be able to debug a script component task too...|||We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.
Marc
|||MarcvdW wrote:
We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.
Marc
Marc,
If you want this then the place to ask for it is http://connect.microsoft.com/sqlserver/feedback
-Jamie
|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.
cool. Could you put the link up here? The more people that add their weight to it the more likely it is to happen. I will certainly add some comments.
|||https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262144
Here it is.
Marc
Remote Debugging in SSIS ?
Hello
I've just heard that Remote Debugging should be possible in SSIS, but how ?
Some of the projects we run require a lot of memory and it's sometimes slow to debug on the local machine ?
Yes i know i can reduce the input rows, but in some cases i need all the data for testing.
Does anyone know how to remote debug ?
Do you have Visual Studio installed?
-Satya SKJ
SQL Server MVP
|||Yes|||And then ?|||cgpl,
Just to clarify, by remote debugging I assume you mean that you want to make a package execute on a remote machine whilst seeing things turn green/yellow/red on your local machine. Is that correct?
As far as I know, that isn't possible. But don't take my word for it. Where did you hear that it WAS possible?
-Jamie
|||
green/yellow/red yes
We had a meeting with Kevin Cox from Microsoft who told that remote debugging was possible (the way i understood it). Don't know if you know him, but he told that he would look in to it.
|||No, I haven't heard of Kevin. if you hear anything back I'd be keen to hear it as well.
TIA
-Jamie
|||SSIS does not implement remote debugging. It was considered, but it was too costly to do. Maybe in the next version, if we'll have time.|||If possible, core be able to debug a script component task too...|||
We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.
Marc
|||We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.
Marc
Marc,
If you want this then the place to ask for it is http://connect.microsoft.com/sqlserver/feedback
-Jamie
|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.|||
Thanks Jamie, I wasn't aware of this option. I posted my feedback.
cool. Could you put the link up here? The more people that add their weight to it the more likely it is to happen. I will certainly add some comments.
|||
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262144
Here it is.
Marc
Remote Debugging in SSIS ?
Hello
I've just heard that Remote Debugging should be possible in SSIS, but how ?
Some of the projects we run require a lot of memory and it's sometimes slow to debug on the local machine ?
Yes i know i can reduce the input rows, but in some cases i need all the data for testing.
Does anyone know how to remote debug ?
Do you have Visual Studio installed?
-Satya SKJ
SQL Server MVP
|||Yes|||And then ?|||cgpl,
Just to clarify, by remote debugging I assume you mean that you want to make a package execute on a remote machine whilst seeing things turn green/yellow/red on your local machine. Is that correct?
As far as I know, that isn't possible. But don't take my word for it. Where did you hear that it WAS possible?
-Jamie
|||green/yellow/red yes
We had a meeting with Kevin Cox from Microsoft who told that remote debugging was possible (the way i understood it). Don't know if you know him, but he told that he would look in to it.
|||No, I haven't heard of Kevin. if you hear anything back I'd be keen to hear it as well.
TIA
-Jamie
|||SSIS does not implement remote debugging. It was considered, but it was too costly to do. Maybe in the next version, if we'll have time.|||If possible, core be able to debug a script component task too...|||We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.
Marc
|||We would appreciate if this could be considered as 'must have' functionallity. As we experience great disadvantages from not being able to remotely debug our ssis packages. Now we have to invest in more memory or servers to be able to provide our ssis development team with good performance. For each remote desktop session we will need to provide 1 gb of memory (visual studio, ssms, desktop etc) + memory for sql server 2005. When working with 8 ssis developers we would need 16gb + memory on our development server. Informatica/Business Obects/Oracle Warehouse builder all provide client/server development scenario's. Hopefully Microsoft will consider this functionallity as important for a new release of ssis.
Marc
Marc,
If you want this then the place to ask for it is http://connect.microsoft.com/sqlserver/feedback
-Jamie
|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.|||Thanks Jamie, I wasn't aware of this option. I posted my feedback.
cool. Could you put the link up here? The more people that add their weight to it the more likely it is to happen. I will certainly add some comments.
|||https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262144
Here it is.
Marc
remote debug problem
I am trying to do remote debugging and doesn't seem to be working....I brin
g up query analyzer, select the datbase, select the sp, right click debug, e
nter a value and ok...when I do this it doesn't pass/break...it completes
the query and grays out the
buttons at the top....
steps I have done:got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||Make sure the version of client tools is the same as the server. In Query
Analyzer look in Help/About.
That fixed the problem for me.
"Jamie Elliott" wrote:
> got click happy
> things I have tried...
> 1. i put in a local admin account under properties/security after you righ
t click on the sql instance
> 2. run dcomcnfg
> a. edited the default access permission - gave everyone allow acces
s permission
> b. under applications tab - I went to properties ont he sqldbreg ed
ited the use custom access permission under security to allow everyone permi
ssion
> c. on that same com(sqldbreg) - I changed the identity to use a the
local user I setup with admin rights
> what else can I try?
g up query analyzer, select the datbase, select the sp, right click debug, e
nter a value and ok...when I do this it doesn't pass/break...it completes
the query and grays out the
buttons at the top....
steps I have done:got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||Make sure the version of client tools is the same as the server. In Query
Analyzer look in Help/About.
That fixed the problem for me.
"Jamie Elliott" wrote:
> got click happy
> things I have tried...
> 1. i put in a local admin account under properties/security after you righ
t click on the sql instance
> 2. run dcomcnfg
> a. edited the default access permission - gave everyone allow acces
s permission
> b. under applications tab - I went to properties ont he sqldbreg ed
ited the use custom access permission under security to allow everyone permi
ssion
> c. on that same com(sqldbreg) - I changed the identity to use a the
local user I setup with admin rights
> what else can I try?
remote debug problem
I am trying to do remote debugging and doesn't seem to be working....I bring up query analyzer, select the datbase, select the sp, right click debug, enter a value and ok...when I do this it doesn't pass/break...it completes the query and grays out the
buttons at the top....
steps I have done:
got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||Make sure the version of client tools is the same as the server. In Query
Analyzer look in Help/About.
That fixed the problem for me.
"Jamie Elliott" wrote:
> got click happy
> things I have tried...
> 1. i put in a local admin account under properties/security after you right click on the sql instance
> 2. run dcomcnfg
> a. edited the default access permission - gave everyone allow access permission
> b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
> c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
> what else can I try?
buttons at the top....
steps I have done:
got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||Make sure the version of client tools is the same as the server. In Query
Analyzer look in Help/About.
That fixed the problem for me.
"Jamie Elliott" wrote:
> got click happy
> things I have tried...
> 1. i put in a local admin account under properties/security after you right click on the sql instance
> 2. run dcomcnfg
> a. edited the default access permission - gave everyone allow access permission
> b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
> c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
> what else can I try?
Subscribe to:
Posts (Atom)