I just installed SSMS 2014 on a new Win 10 machine and I was going to search for a SQL script that I had used before, so clicked open file, then tried to click on the search box in the upper right to enter part of the file name I was looking for. This caused SSMS to crash. I tried to "repair" the program through control panel to no avail. This is a feature I have used a lot on SSMS 2014 in other computers, both Win 7 & 10
Do you have any app crash reports or anything in the error log to see why SSMS crashed?
Also whats the reason behind using SSMS2014 and not SSMS 18.#?
Thanks for reply, to be honest, it didn't occur to me to download SSMS 2018 since I just used the version that came on the SQL Server ISO. I did and it solved the problem. I had run 2014 on other win 10 machines without having this issues. BTW, it didn't produce any report, log or anything, SSMS 2014 just went away when I clicked on the file explorer search box. But not an issue anymore. Thanks @anthony.green
Not a problem, would of thought it would of logged to your local event log the application crash so it could be narrowed down as to what caused it, but hey ho this is MS we are talking about.
Also as a side note I hope you have an extended support agreement with MS or an Enterprise Agreement as 2014 is out of mainstream support now, so without the extension or an EA you wont get the extended support lifecycle.
@anthony.green you were right. It did put out a couple of errors each time. I am attaching them if you want to look at it, however, I have resolved it by upgrading to SSMS 2018, so at this point it is only a matter of curiosity. Thanks again.ssms-2014-error.txt
17 People are following this question.
