SSMS 2012/2014 Crashing

sql_enthusiast

Starting last week, I noticed SSMS 2012 and 2014 randomly crashing. This weekend, every machine that has SQL Search 3.0 fails to launch. You get that pointless error message from SSMS/Microsoft - "SQL Server Mgmt Studio has stopped working"... Yeah, thanks brainyyack now tell me why...? So, I attached a debugger and ran through a session and found this:

{System.Reflection.TargetInvocationException: An exception occurred during the operation, making the result invalid. Check InnerException for exception details. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)
--- End of inner exception stack trace ---
at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
at TTRider.Supratimas.AddIn.Context.<>c__DisplayClass9.<DownloadVersionInformation>b__7(Object s, DownloadStringCompletedEventArgs e) in f:\Supratimas\Main\SSMSAddIn\Context.cs:line 471
at System.Net.WebClient.OnDownloadStringCompleted(DownloadStringCompletedEventArgs e)
at System.Net.WebClient.DownloadStringOperationCompleted(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(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.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)}


So, I spent two days installing/uninstalling/cursing at SSMS as to why this error kept my team from working. I found out that SQL Search 3.0 was a causing the crash. Once I removed everything Red Gate, SSMS worked. Then I added 1 tool at a time back - checking SSMS after each install. Everything worked great until SQL Search 3.0 was added. Crash... remove SQL Search, works, add a fresh install from the Red-Gate website, crash. So, no one can use SQL Search at my office in SSMS 2012 or 2014 until we find out why we're even connecting to a remote server in the first place and secondly, why does it crash the minute the we install it.

missmansirao

This question is somewhat related to the question below, which was answered:

SSMS 2014 Crashes When Attempting to Attach A Database  

SQL Server  >  SQL Server Manageability

I had a heck of a time getting SQL Server Developer Edition Installed on a Windows 10 machine. It would constantly hang and I had to baby sit it. When it did hang, I had to go and kill the process NGEN.exe and then it would keep going per the post here:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/bee5d51f-3c0f-4814-8ff6-04db3a2c55d4/sql-server-2008-installation-hangs-on-installsqltoolscpu64action-writenativeimage64?forum=sqlsetupandupgrade

I think this action my have corrupted my installation. When I try to attach a database from my 2012 installation, SSMS will crash and restart. Every time. Has anybody else seen this behavior and solved the problem?

Solution : Social MSDN Microsoft

RichardL

Hi @sql_enthusiast & @missmansirao

Thank you for your posts. 

Please try the latest version which was released yesterday. You can download it from my link below. 

ftp://support.red-gate.com/patches/SQLSearch/29Mar2018/SQLSearch_3.1.2.1997.exe

I hope this helps. 

Best

Richard Lynch. 

sql_enthusiast

No joy... Same issue. 
Image shows inner exception from SSMS 2014 - after a fresh install.