SSMS automatically restarts after I close it

• 
  Hi @irisoft
  
  Thanks for all of the information. 
  
  I've tried replicating this on a fresh install of SSMS 19.3 as well as installing SQL Prompt and SQL Source Control. I opened multiple stored procedures across the two instances I had open, but upon closing, nothing strange was occurring for me.
  
  I can't say exactly why you're having this issue, but it might be worth trying to cleanly uninstall SQL Source Control as well as SSMS. This can help ensure that all components are correctly removed. Afterwards, try restarting your machine and cleanly installing SSMS 19.3 and the Redgate products.
  

  Kurt_M January 24, 2024 02:30

  - 0 +
• 
  Hi @Kurt_M
  
  Thank you for your answer. I uninstalled all Redgate products and SSMS, restarted and installed everything back. The result is the same.
  
  I uninstalled SQL Source Control 7.7.1 and installed 7.6.34 - same error. I installed version 7.6.28 and it works. So, the error appeared somewhere between 7.6.28 and 7.6.34. I don't have all the versions in between (probably missed them in december).
  
  If you can check the changes between these versions related to the error in the first post (RedGate.SQLSourceControl.Engine.LinkedDatabaseStore.TryGetLinkedDatabase) maybe you can add a try-catch or a null check or something to prevent that exception.
  
  For now, I will stay on version 7.6.28 and I will try on a future version to see if the error disappears.
  
  Thank you.
  
  

  irisoft January 25, 2024 14:42

  - 0 +
• 
  Is there a planned fix for this? It's very annoying and been happening for a few weeks now!

  TonyRMT March 18, 2024 07:34

  - 0 +
• 
  I am seeing this same error as well. I deleted some previously linked databases recently because I no longer needed to track them... could this be a problem?

  CHP March 18, 2024 15:42

  - 0 +
• 
  I'm getting this as well. At the end of the day I want to get away but when I close SSMS, it restarts itself. It's super annoying, please fix!!

  SUR March 20, 2024 17:24

  - 0 +
• 
  I have this issue as well. I'm in the habit of closing down my SSMS periodically and reopening to start afresh on a separate piece of work. Wondering why i've got 2 SSMS instances open. And it appears that the closure is prompting a delayed restart of SSMS.

  kalo March 21, 2024 17:16

  - 0 +
• 
  Also seeing this issue after installing SSMS 19.3 (uninstalled Redgate Toolkit and reinstalled to get the extensions in 19.3)

  MartinP_UK March 21, 2024 20:57

  - 0 +
• 
  This started happening to me also a few weeks ago.  I close SSMS, and after a delay of a minute or two it restarts.  When I close it a second time it then stays down for the count.

  
  

  Windows 10 on an oldish computer.
  

  SSMS 17.9.1.

  SQL Prompt 10.14.10.7538, along with other Toolbelt utilities updated at the same time.

  
  

  And here's another observation that may mean something:  when I first start SSMS it starts up normally; but when it is restarting itself it is a resource hog and interferes with normal responsiveness of other programs.
  

  
  

  It's not the end of the world, but it is a bit annoying when it starts back up as I want to go home, or if I'm in a hurry for other programs to respond.

  Mike_B April 03, 2024 23:59

  - 0 +
• 
  So having moved off SSMS 18.12 to 19.3 prompted by this issue, I've updated SQL Prompt today and now introduced this issue into 19.3
  
  Ironically, because i'm now on 19.3 and having to uninstall and re-install redgate products to get them to show in the new version, I am prompted to close SSMS to allow the update, but after you close SSMS you actually see the second SSMS instance in the 'Quit applications' screen. And have to go and close that as well before being able to install.
  
  
  
  Is there a fix in the works for this issue raised at the start of this year?

  kalo April 05, 2024 12:10

  - 0 +
• 
  im getting a similar effect where ssms always restarts when closing and loses some of my history.  my log error is slightly different tho:
  
  

  Application: Ssms.exe

  Framework Version: v4.0.30319

  Description: The process was terminated due to an unhandled exception.

  Exception Info: System.NullReferenceException

     at RedGate.SQLSourceControl.Engine.LinkedDatabaseStore.TryGetLinkedDatabase(RedGate.SQLSourceControl.Engine.Model.Comparison.DatabaseId, RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabase ByRef)

     at RedGate.SQLSourceControl.Engine.Diff.LinkedDatabaseConfigStore.TryGetLinkedDatabase(RedGate.SQLSourceControl.Engine.Model.Comparison.DatabaseId, RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabase ByRef)

     at RedGate.SQLSourceControl.Engine.Diff.LinkedDatabaseConfigStore.TryGetLinkedDatabase(RedGate.SQLSourceControl.Engine.Model.Comparison.DatabaseId, RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabaseDetails ByRef)

     at RedGate.SQLSourceControl.Engine.Diff.Controller.TryGetLinkedDatabase(RedGate.SQLSourceControl.Engine.Model.Comparison.DatabaseId, RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabaseDetails ByRef)

     at RedGate.SQLSourceControl.CommonUI.DatabaseViewController.TryGetCurrentLinkedDatabase(RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabaseDetails ByRef)

     at RedGate.SQLSourceControl.CommonUI.DatabaseViewController.get_IsFlywayProject()

     at RedGate.SQLSourceControl.CommonUI.ViewController.get_IsFlywayProject()

     at RedGate.SQLSourceControl.CommonUI.Controls.DatabaseAndBranchNameControl.UpdateFlywayWarningVisibility()

     at RedGate.SQLSourceControl.CommonUI.Controls.Commit.ToCommitTabControl.EnableControls(Boolean)

     at RedGate.SQLSourceControl.CommonUI.Controls.Commit.ToCommitTabControl.OperationChanged(System.Object, System.EventArgs)

     at RedGate.SQLSourceControl.CommonUI.Controls.ChangeSetViewerControl.RefreshChangeSet()

     at RedGate.SQLSourceControl.CommonUI.Controls.ChangeSetViewerControl.ManagedVisibleChanged(System.Object, System.EventArgs)

     at System.EventHandler.Invoke(System.Object, System.EventArgs)

     at System.Windows.Forms.Control.OnVisibleChanged(System.EventArgs)

     at System.Windows.Forms.ScrollableControl.OnVisibleChanged(System.EventArgs)

     at System.Windows.Forms.Control.WmShowWindow(System.Windows.Forms.Message ByRef)

     at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)

     at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)

     at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)

  
  

  Adievo April 05, 2024 22:04

  - 0 +
• 
  This occurs 100% of the time on my machine as well, SSMS 19.3.4.0, SQL Prompt 10.14.12.7945, super annoying. Hmm, I didn't realize the thread was for source control. Will uninstall and test.
  

  mikegalusha April 10, 2024 17:14

  - 0 +
• 
  I'm seeing this as well:

  
  

  Windows 10

  SSMS 20.0.70.0
  

  SQL Source Control 7.7.9.18623
  

  Bowman April 29, 2024 22:39

  - 0 +
• 
  I have been having this problem too for a few months.
  
  Today I upgraded from SSMS 19.3 to SSMS 20.1 (Windows 11 box). Although SSMS is supposed to import options and customisations, it definitely doesn't do them all - including toolbars. I like my toolbars to have my most used tools and not filled with stuff I don't want.
  
  So I modified the toolbars to the way I wanted, then exited out of SSMS. Unfortunately, SSMS automatically restarted (again) and the toolbars had all reverted (or, more specifically, nothing had been saved).
  
  After various fumbling about, I found a workaround how to stop this happening:
  

  • Disconnect from all servers before exiting SSMS. 

  
  The object explorer should be empty. This will stop SSMS restarting, and also allow you to save changes to toolbars (and perhaps other things).
  
  (Note that it seems to be OK if you didn't actually open any databases, but if you have opened a database, then disconnecting from the server, before exiting SSMS, allows you to exit without restarting).
  
  
  

  SeanB April 30, 2024 00:28

  - 0 +
• 
  I'm having the same issues after upgrading to SSMS 20.1. Didn't happen with SSMS 19. Suuuuuper annoying. Can confirm that disconnecting from the server works.

  mcook May 24, 2024 13:20

  - 0 +
• 
  This is a consistent problem.
  Is there a plan to fix this?
  Is there any response from Redgate on this issue?

  shauntorres June 07, 2024 08:06

  - 0 +
• 
  Same issue here!
  
  

  AngeloCec June 10, 2024 14:18

  - 0 +
• 
  Redgate is ignorant on this issue. No update whatsoever whether they are planning to fix it or not...
  Very annoying!

  TonyRMT June 10, 2024 15:26

  - 0 +
• 
  Upgraded yesterday and this has started happening for me as well.

  scollis June 14, 2024 12:27

  - 0 +
• 
  Add me to the list.

  pmclci June 18, 2024 19:19

  - 0 +
• 
  Add another one to the list here. Sean B's  work around of closing connections before closing program seems to work. 
  
  SeanB said:

  I have been having this problem too for a few months.
  
  Today I upgraded from SSMS 19.3 to SSMS 20.1 (Windows 11 box). Although SSMS is supposed to import options and customisations, it definitely doesn't do them all - including toolbars. I like my toolbars to have my most used tools and not filled with stuff I don't want.
  
  So I modified the toolbars to the way I wanted, then exited out of SSMS. Unfortunately, SSMS automatically restarted (again) and the toolbars had all reverted (or, more specifically, nothing had been saved).
  
  After various fumbling about, I found a workaround how to stop this happening:
  

  • Disconnect from all servers before exiting SSMS. 

  
  The object explorer should be empty. This will stop SSMS restarting, and also allow you to save changes to toolbars (and perhaps other things).
  
  (Note that it seems to be OK if you didn't actually open any databases, but if you have opened a database, then disconnecting from the server, before exiting SSMS, allows you to exit without restarting).
  
  
  

  jembree June 28, 2024 18:58

  - 0 +
• 
  This is happening to me as well, even on servers that have no linked database so source control.  What sucks, is all the remembered tabs are closed as well.

  mmoore July 22, 2024 10:21

  - 0 +
• 
  so, is this a SSMS issue or a Red-Gate issue?
  

  jembree said:

  Add another one to the list here. Sean B's  work around of closing connections before closing program seems to work. 
  
  SeanB said:

  I have been having this problem too for a few months.
  
  Today I upgraded from SSMS 19.3 to SSMS 20.1 (Windows 11 box). Although SSMS is supposed to import options and customisations, it definitely doesn't do them all - including toolbars. I like my toolbars to have my most used tools and not filled with stuff I don't want.
  
  So I modified the toolbars to the way I wanted, then exited out of SSMS. Unfortunately, SSMS automatically restarted (again) and the toolbars had all reverted (or, more specifically, nothing had been saved).
  
  After various fumbling about, I found a workaround how to stop this happening:
  

  • Disconnect from all servers before exiting SSMS. 

  
  The object explorer should be empty. This will stop SSMS restarting, and also allow you to save changes to toolbars (and perhaps other things).
  
  (Note that it seems to be OK if you didn't actually open any databases, but if you have opened a database, then disconnecting from the server, before exiting SSMS, allows you to exit without restarting).
  
  
  

  
  

  mmoore July 22, 2024 10:22

  - 0 +
• 
  Here is my Error log from Event Viewer.
  
  

  Application: Ssms.exe

  Framework Version: v4.0.30319

  Description: The process was terminated due to an unhandled exception.

  Exception Info: System.NullReferenceException

     at RedGate.SQLSourceControl.Engine.LinkedDatabaseStore.TryGetLinkedDatabase(RedGate.SQLSourceControl.Engine.Model.Comparison.DatabaseId, RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabase ByRef)

     at RedGate.SQLSourceControl.Engine.Diff.LinkedDatabaseConfigStore.TryGetLinkedDatabase(RedGate.SQLSourceControl.Engine.Model.Comparison.DatabaseId, RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabase ByRef)

     at RedGate.SQLSourceControl.Engine.Diff.LinkedDatabaseConfigStore.TryGetLinkedDatabase(RedGate.SQLSourceControl.Engine.Model.Comparison.DatabaseId, RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabaseDetails ByRef)

     at RedGate.SQLSourceControl.Engine.Diff.Controller.TryGetLinkedDatabase(RedGate.SQLSourceControl.Engine.Model.Comparison.DatabaseId, RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabaseDetails ByRef)

     at RedGate.SQLSourceControl.CommonUI.DatabaseViewController.TryGetCurrentLinkedDatabase(RedGate.SQLSourceControl.Engine.Interfaces.Comparison.ThreeDatabase.ILinkedDatabaseDetails ByRef)

     at RedGate.SQLSourceControl.CommonUI.DatabaseViewController.get_IsFlywayProject()

     at RedGate.SQLSourceControl.CommonUI.ViewController.get_IsFlywayProject()

     at RedGate.SQLSourceControl.CommonUI.Controls.DatabaseAndBranchNameControl.UpdateFlywayWarningVisibility()

     at RedGate.SQLSourceControl.CommonUI.Controls.Commit.ToCommitTabControl.EnableControls(Boolean)

     at RedGate.SQLSourceControl.CommonUI.Controls.Commit.ToCommitTabControl.OperationChanged(System.Object, System.EventArgs)

     at RedGate.SQLSourceControl.CommonUI.Controls.ChangeSetViewerControl.RefreshChangeSet()

     at RedGate.SQLSourceControl.CommonUI.Controls.ChangeSetViewerControl.ManagedVisibleChanged(System.Object, System.EventArgs)

     at System.EventHandler.Invoke(System.Object, System.EventArgs)

     at System.Windows.Forms.Control.OnVisibleChanged(System.EventArgs)

     at System.Windows.Forms.ScrollableControl.OnVisibleChanged(System.EventArgs)

     at System.Windows.Forms.Control.WmShowWindow(System.Windows.Forms.Message ByRef)

     at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)

     at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)

     at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)

     at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)

     at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)

  
  
  I have submitted a bug to Red-Gate with this same error.

  mmoore July 22, 2024 10:30

  - 0 +
• 
  is anyone trying to fix this?

  Adievo July 22, 2024 14:44

  - 0 +
• 

  Adievo said:

  is anyone trying to fix this?

  I was told to update to the latest SQL Source Control version, which I am going to do later today to find out if this fixes the problem (7.7.17.19083).. What is funny though, when you do "Check for update" in Sql Source Control, it says there are no updates, and I am currently on (7.7.10.18663)

  mmoore July 22, 2024 17:31

  - 0 +
• 
  Hi - I just wanted to let you know that we are looking at this problem, but we're currently unable to reproduce it. We'll update you as soon as we have any more information.

  Mike U July 22, 2024 19:13

  - 0 +
• 
  Contact me if you want to see it happen in real time.  It is very annoying.  It has been an issue on both my current and previous laptops.

  Jlynn July 22, 2024 21:28

  - 0 +
• 
  Hi, we have now released the following version 7.7.18.19115 which should hopefully solve the restart after shutdown issue
  
  Please let us know if this helps!

  DanC July 30, 2024 10:03

  - 0 +
• 
  The first fix they gave me about a week ago did not solve the problem, but it seems to aggravate it even more.  I just downloaded the newest version now and will test it shortly.

  mmoore July 30, 2024 10:31

  - 0 +
• 
  7.7.18.19115 isnt in the latest sql toolbelt download.  how do i get it?

  Adievo July 30, 2024 15:54

  - 0 +

Add comment

Please sign in to leave a comment.