SQL Source Control 184.108.40.20608 Failure to load Add-on to SQL Server 2008 R2
This is actually a defect in the product. After upgrading to 220.127.116.1108 of the SQL Source Control, the Add-On for SQL Server 2008 R2 no longer loads. I had to revert to using 18.104.22.16814
i am also having the same issue.anybody please give a solution
I've dropped C:\Users\...\AppData\Local\Red Gate\SQL Source Control 3. And It's help me.
Abhishek Shrestha commented
The add-in 'sql source control 3' failed to load or caused an exception. Error number 80131604. Just started receiving this when starting SSMS 2014 in Windows 8.1 64 bits. After some time, that too stopped appearing. Now, SSMS doesn't have source control feature anywhere. Repairing and uninstalling and reinstalling didn't help either. Please help.
I had same problem with 22.214.171.124. After few uninstalling and installing previous versions without any luck, finally found version wich is working 126.96.36.19914.
Giving our user a completely new windows profile fixed the issue for them. An extreme solution but maybe this will help others with this issue?
We just updated to 188.8.131.52 and the same user still has this issue so still can't use the software.
Has there been any progress in tracking this down?
I'm thinking that we might have to go down the path of getting this user a clean windows profile and seeing if that resolves it.
This morning we tried updating to the latest version 184.108.40.206 and the same person has the same error occurring on startup of SSMS. As requested, here is some more detailed information on his/our setup.
SQL Source Control setup
Shared environment of 8 developers (4-5 of which are very active) connecting to 4 source controlled databases which are stored in TFS 2012.
(TFS Version reported via the web interface is 11.0.50727.1)
Windows 7 Enterprise 32bit SP1 with 2GB of RAM
Running SQL 2008 R2 Client Tools only.
The About screen in SSMS tells us...
Microsoft SQL Server Management Studio 10.50.1600.1
Microsoft Analysis Services Client Tools 10.50.1600.1
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 9.0.8112.16421
Microsoft .Net Framework 2.0.50727.5466
Operating System 6.1.7601
MS Visual Studio 2012 is installed
SQL Prompt (Normal version) is installed
Demo versions of SQL Compare/ Data Compare are installed.
One final thing which I think will be very interesting to you is that I just tried logging onto his machine as me and running SSMS and it worked fine. So this actually looks like some kind of issue associated with his user profile.
If there is any other info you think might be useful, please let me know.
Exact same error for me. Win 7 x64, SQL 2005, SSMS 9.00.5000.00, nothing in the event log, happens right after SSMS splash screen.
Andy Campbell Smith commented
Any salient information any of you can provide would be really helpful - unfortunately, this is a fairly generic Windows error, which means SQL Source Control is crashing before it loads far enough to give a useful error message or stack trace.
We're doing our best to track this error down, and we've logged it in our internal bug-tracking system as SOC-4649. Since it's not affecting everyone and we can't reproduce it, we're not getting very far, so any information you can provide at all would be helpful - your OS, version of SSMS, any details about how you were using SQL Source Control, or anything else you think might be relevant. Thanks for your help!
Our team of 8 just upgraded to the latest version 220.127.116.1108. One user is reporting this exact same error. We are on a mixture of Win7 32 and 64 bit machines connecting to SQL Server 2008 R2 in a shared environment.
Error text is in a dialog titled "Microsoft SQL Server Management Studio"
The error is
"The Add-in 'SQL Source Control 3.1' failed to load or caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it again.
Error Message: <Unknown Error>
Error number: 80131500
Please could somebody advise? Thanks.
Ben Sproat commented
I'm getting the same error in 2008 R2, 2005, and 2012. I get unknown error 801131500 in 2008 r2 and 2005, and 80131604 in 2012