How can we help you today? How can we help you today?

Source Control causing SSMS to crash frequently

This seems to happen when I introduce a new server and try and act with it in the object browser. Happening frequently since yesterday morning. 

Once it started happening I updated my source-control to the latest version but it is still happening.

Error log below.

FYI: this is also coinciding with an issue where SSMS closing it is prompting it to restart.



2024-03-21 17:12:06.553 +00:00|Warning|RedGate.SQLSourceControl.Engine.Utils.DependencyResolution.AppDomainWideSetup|112| Unhandled Exception: Exception has been thrown by the target of an invocation..  IsTerminating : true
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.MissingMethodException: Method not found: 'Void RedGate.SIPFrameworkShared.DatabaseConnectionDescriptor.set_AccessToken(System.String)'.
   at RedGate.SIPFramework.Services.Wrappers.DatabaseConnectionInfo..ctor(IConnectionProperties connectionProperties)
   at RedGate.SIPFramework.Services.ServicesToPlugins.ObjectExplorerWatcher.<>c.<OnConnectionsChanged>b__14_0(IConnectionProperties conn)
   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at RedGate.SIPFramework.Services.ServicesToPlugins.ObjectExplorerWatcher.OnConnectionsChanged(Object sender, ObjectExplorerConnectionsChangedEvent e)
   at RedGate.SharedSSMS.VersionSpecific.ObjectExplorerShared.InvokeOnConnectionsChanged(ObjectExplorerConnectionsChangedEvent e)
   at RedGate.SharedSSMS.VersionSpecific.ObjectExplorer2012Plus.OnObjectExplorerContextChanged(Object sender, NodesChangedEventArgs args)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Microsoft.SqlServer.Management.SqlStudio.Explorer.BufferedNotification.Fire()
   at Microsoft.SqlServer.Management.SqlStudio.Explorer.BufferedNotification.<StartTimer>b__2(Object state)
   at System.Threading.TimerQueueTimer.CallCallbackInContext(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers()
   at System.Threading.TimerQueue.AppDomainTimerCallback(Int32 id)

kalo
0

Comments

4 comments

Sort by
  • Peter_Laws
    Hi kalo,

    Thanks for raising it with us.

    What version of SSMS are you using please?
    What sort of db are you targeting? (Version, Azure, SSRS etc)
    Peter_Laws
    0
  • kalo
    Hi Peter,

    Thanks for your response,

    I was on 18.12.1 (SSMS). Two colleagues both on this version also, one experiencing the same issue and one not.

    However, I have now upgraded my SSMS to version 19.3 to be able to work and avoid the crashing.

    I have not as yet found a window to setup Source Control against this version.

    James
    kalo
    0
  • Dan_J
    Hi @kalo

    I'm glad that updating SSMS has enabled you to work without experiencing crashes.

    Regarding why you can't see the SQL Source Control in version 19.3, you may need to reinstall SQL Source Control in order for it to install to SSMS 19.3. The latest version of SQL Source Control can be downloaded directly from here: https://download.red-gate.com/checkforupdates/SQLSourceControl/SQLSourceControl_7.7.9.18623.exe 

    I hope this helps!
    Dan_J
    0
  • DamianWise
    I am having the identical issue, with the same version of SSMS (18.12.1).
    DamianWise
    0

Add comment

Please sign in to leave a comment.