SQL Source Control 3.1 Failed to load or caused an exception

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

Moderators: Chris Auckland, David Atkinson, sherr, PhilScrace, andy.campbell.smith

Postby ScottA » Mon Mar 25, 2013 2:30 pm

Bump!

Can this item be made a priority? I'm looking forward to some of the new features since 3.1 and am completely blocked from installing the new version with this error (the 'keep the selections when navigating away and coming back to the commit window' one alone should save me quite a lot of time)

As previously mentioned am happy to assist in diagnosing the issue if you guys can't reproduce it.

Also - Sproatba, I'm not using any (non redgate) SSMS plugins and haven't had any installed since my last rebuild a while ago.

Cheers,
ScottA
 
Posts: 8
Joined: Fri Apr 13, 2012 7:50 am
Location: Australia

Postby sproatba » Wed May 15, 2013 9:31 pm

The latest version 3.4 installed correctly for me. No more crash on startup.
sproatba
 
Posts: 10
Joined: Fri Jan 27, 2012 9:59 pm

Happened to me after installing 3.4.1.73

Postby acrawford » Wed May 29, 2013 3:27 pm

I was good until I installed 3.4.2.61. It seems there is some version mismatch? Below is my error.

Unable to find assembly 'RedGate.SQLSourceControl.AtomicIO, Version=3.4.1.73, Culture=neutral, PublicKeyToken=7f465a1c156d4d57'.
acrawford
 
Posts: 7
Joined: Wed Apr 20, 2011 5:57 pm

Support solved my issue

Postby acrawford » Wed May 29, 2013 6:46 pm

My issue is solved now, support sent me this:

Hi,

Thank you for submitting an error report.

Your problem is a known issue and we recommend trying the following as a workaround:

1. Delete the contents of this folder in your user profile:
%userprofile%\\AppData\\Local\\Red Gate\\sql source control 3\\generic\\journal 2. Check any repository folders you are using for source control and delete any files called _lock_redgate

Previously-failed transactions may remain from a previous installation of SQL Source Control. This should remove them permanently.

If the advice above does not resolve your problem, and you would like us to investigate the issue further, please reply to this email and we will log a support ticket.
acrawford
 
Posts: 7
Joined: Wed Apr 20, 2011 5:57 pm

Previous

Return to SQL Source Control 3

Who is online

Users browsing this forum: Yahoo [Bot] and 1 guest