views:

21

answers:

3

After upgrading to Windows 7, I can no longer debug stored procecures in SQL server management studio (MSSSMS). I get the message "Failed to start debugger". Data is Null. This method or property cannto be called on Null values (System.Data). I tried starting MSSMS with "Run as administrator", but the same thing happens. Any ideas? Thanks, Brian

A: 

Check out this link. Seems to be the same problem: http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/49992b24-7dd7-4f7b-a44e-3a5927844e5c

Vidar Nordnes
I saw that, but it doesn't have any fixes for not being able to debug in MSSMS
BrianK
A: 

Hi,

This can be due to a permission error for debugging.

Try setting these settings

http://msdn.microsoft.com/en-us/library/w1bhybwz(v=VS.80).aspx

To debug on SQL Server, both the account running Visual Studio and the account used to connect to SQL Server must be members of the sysadmin role.

The account used to connect to SQL Server is either your Windows user account (if you are using Windows authentication) or an account with user ID and password (if you use SQL authentication).

Justin King
A: 

I was going to reinstall SQL Server, and then discovered there is now SQL Server 2008 SP2. I intalled that and it fixed it.

BrianK