Failed to start debugger - Data is Null.

• garrett.bates

  SSC Veteran

  Points: 239

  More actions

  March 10, 2016 at 8:57 am

  #316715

  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 ensured that the requirements listed here are met. I am using a Windows login with a sysadmin role, and all necessary firewall rules are in place on the server and my PC.

  https://msdn.microsoft.com/en-us/library/cc646024.aspx

  The remote debugger was working when our database was a SQL Server 2008 R2 instance, but it seems that it stopped working after upgrading to 2014. I can still debug on my local SQL Server 2014 instance (which hosts copy of the remote database), but not remotely. I have confirmed that other developers are having the same problem, so it seems to be an issue with the server itself, not my PC.

  Are there any additional steps I can take to troubleshoot this issue?

• DouglasH

  SSCommitted

  Points: 1669

  More actions

  March 17, 2016 at 11:11 am

  #1865938

  I don't know if this is the answer to your issue but it has a resolution to a similar issue in 2012. Seems like permissions/registry.

  https://social.msdn.microsoft.com/Forums/sqlserver/en-US/bc1d8e04-723e-4340-9595-c94dced8580a/failed-to-start-debugger-data-is-null-sql-server-2012?forum=sqltools

• ManicStar

  SSCoach

  Points: 17992

  More actions

  March 17, 2016 at 2:03 pm

  #1865991

  Check that a firewall rule or 2 isn't blocking the DTC.

• tim 28156

  Grasshopper

  Points: 19

  More actions

  November 14, 2017 at 9:29 am

  #1968022

  I am having the exact same problem and have not found any responses that have a solution.  My firewall is turned off and I am on the DB server when trying to debug using the local administrator account.

  Here is my SQL info
  Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64)   Apr 29 2016 23:23:58   Copyright (c) Microsoft Corporation  Developer Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)

  My application server is running Windows Server 2012 R2