PRB: SQL Server Debugging with Visual Studio Service Pack 5 Requires a Non-System Account

This article has been archived. It is offered "as is" and will no longer be updated.
With Visual Studio 6.0 Service Pack 5 or later, SQL Server debugging cannot be performed when the SQL Server service is set to run under the Local System account. This is true regardless of whether SQL Server is local to the computer where Visual Studio is installed or is located on a remote computer.

The following error message appears in the application event log from the source MSDEVSDI:
SQL Server when started as service must not log on as System Account. Resetto logon as user account using Control Panel.
Configure the SQL Server service to run under a valid user account instead of the Local System account.
More information
Prior to Visual Studio 6.0 Service Pack 5, SQL Server debugging could be performed successfully on a Microsoft Windows NT 4.0 computer with a local SQL Server, even though SQL Server itself was set to run under the Local System account. In Visual Studio 6.0 Service Pack 5 and later, this has been changed so that the behavior is consistent across all platforms. SQL Server must be running under a non-system account for debugging to be successful.

With Microsoft Windows 2000, SQL Server debugging has never been possible when the server is running under the Local System account, even if the server was on the same computer as Visual Studio.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
156096 INF: Tips for Debugging Stored Procedures from VC++
179235 DOC: SQL Debugging with VC++ 5.0 Requires a Non-System Account

Article ID: 281649 - Last Review: 01/16/2015 21:17:11 - Revision: 3.0

Microsoft SQL Server 6.5 Standard Edition, Microsoft SQL Server 7.0 Standard Edition, Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbfile kbprb kbtsql KB281649
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)