SQL Data Compare Conflicts With SQL Source Control "you have another management studio window open"

anotaro

Noticing over the past few versions of SQL Source Control and SQL Data Compare that sometimes if I already have an instance of SQL Data Compare running and then I open MS SQL Server Management Studio and try to use SQL Source Control I will receive the following error message "SQL Source Control is disabled because you have another Management Studio window open".

I understand that there is an option in setup that I can change to allow SQL Source Control to run in multiple windows. I do not want to change this setting. I just don't want this message to appear when, in fact, I only have one instance of Management Studio running. I've checked running tasks to confirm this. Closing Management Studio and reopening does not resolve the problem. I have to close SQL Data Compare and then restart Management Studio. I can then reopen SQL Data Compare and SQL Source Control will continue to work. The problem seems to happen when SQL Data Compare is already running when Management Studio is launched.

Versions:
SQL Data Compare: 13.1.5.5427 Professional
SQL Source Control: 6.0.2.6908
MS SQL Management Studio: 17.4

twurm

I agree with anotaro, the best solution would be to allow them to be open at the same time. I noticed the issue with SQL Compare instead of Data Compare. If this isn't possible please at least make the error message helpful. Saying there is to SSMS windows open when there isn't just confuses people.

Tianjiao_Li

Hi @anotaro and @twurm

Thanks for posting and sorry for the inconvenience caused.

We are not aware of this issue and couldn't reproduce it with the latest version.

Can you please upgrade to the latest version and test again?

BenKentzer

Hello,

This is happening to me as well - I have (as far as I'm aware) got the latest version of Source Control.

When I check Task Manager (without Management Studio open) I have a task called ssms.exe running which reports itself as a "Windows Session Manager".

How do I check whether I have the latest version if I can't get into Source Control, and how do I set it up to allow multiple instances if I can't get into Source Control?

Thanks

Ben

BenKentzer

Update - three reboots later, and it's opened successfully. Something strange on my PC which is making Source Control think it's already open when quite clearly it isn't!

Ben

adam_hafner

@BenKentzer , I actually opened a ticket with Red Gate support on this very issue.  They found that for some reason SQL Source Control is not releasing itself from the instances when you deselect the database from the Object Explorer.  They are aware of this and submitted a bug to development to resolve this, but it effects anyone running SSMS 2017.

anotaro

@Tianjiao_Li No longer able to reproduce the issue since updating to SQL Data Compare 13.1.11.5591. Versions of SSMS and SQL Source Control the same as original post. Seems to be resolved for now. Thanks!

scollis

I experienced this for the first time today as well, updated PC so a brand new installation of SQL Source Control 6.1.8.7584. Turned out I had to close SQL Compare as well as SQL Data Compare (both version 13.4.5.6953).