Sunday, 26 June 2016

Unable to start the Transact-SQL debugger, could not connect to the Database Engine instance ‘XXXX’. Make sure you have enabled the debugging firewall exceptions and are using a login that is a member of the sysadmin fixed server role.

Issue :

          When i am trying to debug the Stored Procedure from sql, i got the below issue.

"Unable to start the Transact-SQL debugger, could not connect to the Database Engine instance ‘XXXX’. Make sure you have enabled the debugging firewall exceptions and are using a login that is a member of the sysadmin fixed server role."

Solution : 
     
Step 1 :Expand the Security
Step 2 :Right click of Logins
Step 3 :Select New Login



Step 4 : Enter your windows user name
Step 5 : User name should be Domain\User Name
Step 6 : Go to Server roles
Step 7 : Select Public
Step 8: Go to User Mappings and select Database(Which database against you want to debug)
Step 9 : Assign role member ship as Public and DYNGRP
Step 10 : Select OK
Now try to debug it will work.
      

6 comments:

  1. Replies
    1. This comment has been removed by the author.

      Delete
    2. Works anyway but also when on server roles try include checking systemadmin securityadmin.

      Delete
    3. What is DYNGRP???
      Please dont share non practical solutions

      Delete
  2. user has sysadmin role given to login, though unable to use debugger & gives error "Unable to start the Transact-SQL debugger, could not connect to the Database Engine instance ‘XXXX’. Make sure you have enabled the debugging firewall exceptions and are using a login that is a member of the sysadmin fixed server role." pls suggest solution for this.

    ReplyDelete
  3. On the server role, the user who will be debugging must have PUBLIC and SYSADMIN access

    ReplyDelete