Error opening Source control 4 after upgrading to SSMS 2016
staggerlee011
Posts: 19 Bronze 1
Hi,
I can no longer use SQL source control (4.1) after upgrading sql server management studio 2016 to the feb edition. Is this a known problem (with a fix) or just me? tried downloading a new developer suite to get the latest version (I was already on it) and doing a repair from Programs and features.
I have then uninstalled sql source control rebooted and reinstalled still getting the same error:
after sending that i then get another error:
I also have SSMS 2008r2 on my workstation and that has completely lost all the tools except tab history and sql prompt.
Any suggestions?
I can no longer use SQL source control (4.1) after upgrading sql server management studio 2016 to the feb edition. Is this a known problem (with a fix) or just me? tried downloading a new developer suite to get the latest version (I was already on it) and doing a repair from Programs and features.
I have then uninstalled sql source control rebooted and reinstalled still getting the same error:
Exception has been thrown by the target of an invocation.
after sending that i then get another error:
Requested value 'm_ToCommitTab' was not found.
I also have SSMS 2008r2 on my workstation and that has completely lost all the tools except tab history and sql prompt.
Any suggestions?
Comments
I assume you are using SSMS 2016 RC0. If that's the case your issue should be resolved by updating to the latest Frequent Update (version 4.3.0), which was released today.
http://documentation.red-gate.com/displ ... nt+Updates
Thank you,
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
Saw it was broke in another support call.
uninstall the SSMS 2016 feb (aka SSMS 2016 rc0) and reinstall SSMS 2016 jan (aka SSMS 2016 CTP3.3) resolved the issue for me, both 2016 and 2008r2 SSMS are working for me again
must have both wrote replies at the same time!
thanks for the possible solution as im back up and running im a bit cautius to go messing again! I will try it next week or something!
cheers for the reply!
S