I'm a developer working on a web application using an instance of SQL Server 2014. I use Visual Studio 2010 sp1 for development. For a task I'm currently working on, I'd like to use the SQL Server Remote Debugger to debug a very large stored procedure that we call through our ORM (Entity Framework). To do this, I open SQL Server Management Studio 2014 and type the following into a new query window:
EXEC [dbo].[MoveAllInvoiceStage]and when I press the Debug button, I receive the following error:
===================================
Failed to start debugger
===================================
Data is Null. This method or property cannot be called on Null values. (System.Data)
------------------------------ Program Location:
at System.Data.SqlTypes.SqlBinary.get_Value() at Microsoft.SqlServer.Management.UI.VSIntegration.DebugSession.DebugCallbacks.OnSqlInitializeDebuggingEvent(ISqlInitializeDebuggingEvent sqlInitializeDebuggingEvent) at Microsoft.SqlServer.Management.UI.VSIntegration.DebugSession.DebugCallbacks.Microsoft.VisualStudio.Debugger.Interop.IDebugEventCallback2.Event(IDebugEngine2 debugEngine, IDebugProcess2 debugProcess, IDebugProgram2 debugProgram, IDebugThread2 debugThread, IDebugEvent2 debugEvent, Guid& riidEvent, UInt32 attribute)
Which is followed by a dialog that says:
Unable to start program 'MSSQL:://<servername>/<databasename>/sys/=0'.
I am using a Windows login with a sysadmin role to connect to the database server, and all necessary firewall rules are in place on the server and my PC. I ensured that the requirements listed here are met.
The remote debugger was working when the database server hosted a SQL Server 2008 R2 instance, but it seems that it stopped working after upgrading the instance to SQL Server 2014. I can still debug on my local SQL Server 2014 instance (which hosts a copy of the remote database). Only remote debugging produces this issue.
I have confirmed that another developer on a different PC is experiencing the same issue, so the problem seems to be server-side.
Are there any additional steps I can take to troubleshoot this issue?
