I've got problems to start SQL Debugger in Management Studio 17 with a specific Windows Domain User in the following scenario:
I have 2 Windows Servers in the same domain, one holding the database, the other one got the management studio installed. I'm logging into the application server with the management studio with 2 different domain accounts. One of the accounts is the domain administrator, the other one is "just" the local administrator for the application and the database server.
I'm testing parallel in two different RDP sessions with two different domain accounts, connected with the application server. From there I'm starting the management studio as administrator in both RDP sessions and connect to database with the same SQL SA account. The only difference is the domain account which I'm using to connect to the application server. In the RDP session, logged in as domain admin, I'm able to start debugging. In the RDP session started as local administrator I'm not."The Transact-SQL-Debugger could not be started...". I'll get the same behavior in Visual Studio 2019 Community edition. Does anyone have an idea to solve this?
I have 2 Windows Servers in the same domain, one holding the database, the other one got the management studio installed. I'm logging into the application server with the management studio with 2 different domain accounts. One of the accounts is the domain administrator, the other one is "just" the local administrator for the application and the database server.
I'm testing parallel in two different RDP sessions with two different domain accounts, connected with the application server. From there I'm starting the management studio as administrator in both RDP sessions and connect to database with the same SQL SA account. The only difference is the domain account which I'm using to connect to the application server. In the RDP session, logged in as domain admin, I'm able to start debugging. In the RDP session started as local administrator I'm not."The Transact-SQL-Debugger could not be started...". I'll get the same behavior in Visual Studio 2019 Community edition. Does anyone have an idea to solve this?