Re: VS2005: SQL Debugging "T-SQL execution ended without debugging. You may not have sufficient permissions to debug"

Hi Gary,

Thanks for your reply. I've only just got back into the office after the
holidays!

But I'm afraid those links didn't help :-(

Btw I'm trying to debug T-SQL on a remote SQL Server **2005** - does that
make a difference?



> To use the SQL debugging, the application account must be a member of the
> sysadmin group in the target SQL Server being debugged, and the
> connection
> account also must be a member of the sysadmin role in the target SQL
> Server, please refer to the following MSDN documentation for details:

Can I check - does "application account" mean the windows/domain account
that I'm logged on as?

I don't think it's a firewall problem because we're running corporate builds
and the Windows firewall is disabled on both client & server.
(i.e. when I click "Control Panel" -> "Windows Firewall" I get a message
saying that the service isn't running.)

To explain my situation - I am using a single domain logon (my own network
username).
This is the account I log onto Windows with, so it will be the account that
VS2005 is running under.
I am using this account (with Windows Authentication) for my Data Connection
to the remote SQL Server 2005.
This account has been added as a login to SQL Server, and has been granted
the sysadmin role.
(the account is also in the administrators group on both client & server)

But I'm still getting the "T-SQL execution ended without debugging. You may
not have sufficient permissions to debug" message when I try to "Step Into
Stored Procedure".

Do you have any other ideas? Are there any specific changes I need to make
in the SQL Server Surface Area Configuration Tool perhaps?
The server is a virtual machine (VMware) - does that make any difference?

Thanks in advance for any help!

Paul.

""Gary Chang[MSFT]"" <v-garych@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:ciBWDpqBGHA.1236@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Paul,
>
>>The Windows account under which I'm running VS2005
>>has the sysadmin role, and this is the same account that's
>>used for the data connection.
>
> To use the SQL debugging, the application account must be a member of the
> sysadmin group in the target SQL Server being debugged, and the
> connection
> account also must be a member of the sysadmin role in the target SQL
> Server, please refer to the following MSDN documentation for details:
>
> How to: Set SQL Server Permissions for Debugging
> http://msdn2.microsoft.com/en-us/library/w1bhybwz.aspx
>
>
> By the way, the Windows XP Service Pack 2 and Windows 2003 have enhanced
> security features, remote debugging on Windows XP SP2 platforms requires
> some additional steps to configure the Windows Firewall. I suggest you may
> also take a look on the following doc:
>
> How to: Set Up Remote Debugging
> http://msdn2.microsoft.com/en-us/library/bt727f1t.aspx
>
>
> Thanks!
>
> Best regards,
>
> Gary Chang
> Microsoft Community Support
> --------------------
> Get Secure! ¡§C www.microsoft.com/security
> Register to Access MSDN Managed Newsgroups!
> http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
> &SD=msdn
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>


.