SQL debugging uses DCOM to communicate between server and client. You need appropriate permissions to be able to debug against the SQL Server. If you get a message box saying that security has not been set up correctly on a server, check for the following:

• Proper access privileges on the machine running SQL server. For more information, see Configuring DCOM for SQL Debugging.
• Proper registration of SQL Debugger Registry2 on the client.

To check SQL Debugger Registry2

1. From the command prompt, run DCOMCNFG.EXE. (You may need to download and install DCOM first. If so, go to http://www.microsoft.com/com/resources/downloads.asp for the latest version.)
2. In the Distributed COM Configuration Properties dialog box, choose the Applications tab and select SQL Debugger Registry2.
3. Click the Properties button.
4. Look at the Identity tab and verify that the account set to run this application is SQLDebugger.
5. If you change the account setting, you must restart SQL Server and your debugger session.

See Also

Setting Up SQL Debugging | Troubleshooting SQL Debugging Setup | Debug Settings and Preparation