Hi,

This strange behavior started recently. If I close SSMS, it restarts itself as if it crashed and trying to restore itself. Even if I hit cancel as it's restarting, it will restart itself yet again. This happens twice. Any idea what's causing

Hello,

If you are using SSMS 2012, are you experiencing the issue explained on the following thread?

http://connect.microsoft.com/SQLServer/feedback/details/774317/sql-server-management-studio-2012-crashes-when-closing

Please provide a dump to Microsoft as requested on the thread.

Regards,

Alberto Morillo
SQLCoffee.com

• Proposed as answer by Maggie LuoMicrosoft community contributor, Moderator Friday, March 15, 2013 8:59 AM
• Edited by Alberto MorilloMVP, Moderator Monday, March 18, 2013 2:57 PM
• Marked as answer by Maggie LuoMicrosoft community contributor, Moderator Sunday, March 24, 2013 1:54 PM

The Connect thread pointed to above says that this has been fixed back in August 2013 but there is no way of finding out how to get this fix or even if it has been released to users. It's now nearly February 2014. What's going on? Why is it taking so long to get the fix out?

This happens to me, and it happens to my boss.  Something tells me it happens to a lot of people.  Why is there no response to this?  the other thread claims that the bug cannot be reproduced, but the steps to reproduce are clearly laid out and I can reproduce it easily. 

Also, the other thread requires me to apply a hotfix even though this issue was reported well over a year ago.  seriously wtf.  No way I'm applying a hotfix, at this point I have little faith in the 2012 SSMS developers.

I've been told that this "should be fixed in SQL 2012 SP2" which I believe is due "later this year". Not particularly edifying.

What's even more 'awesome' is this still happens in SSMS 2014...I mean, really?

I can absolutely confirm that this still happens in SSMS 2014. Extremely annoying.

Update: It's bizarre that MS can't repro this, it's the same exact Event Viewer event as the one in the "answer" link above.

Faulting application name: Ssms.exe, version: 2014.120.2000.8, time stamp: 0x5306c06d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0xe0434352
Fault offset: 0x0000c42d
Faulting process id: 0x22cc
Faulting application start time: 0x01cfce953abe5d8f
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\Ssms.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: d54905f7-3e79-11e4-a374-001bdc0f8775

• Edited by SilverSideDown Wednesday, September 17, 2014 3:34 PM

My guess is that the fault does not appear if you start with a clean PC and just install SSMS 2014.

If you previously had SSMS 2013 and upgraded the fault might affect SSMS 2014. Or it may be something to do with also having Visual Studio on the PC.

Obviously more work is required but Microsoft don't see it as a priority. I was told just to keep SSMS running all the time to avoid the bug.

This happens to me with a clean install of Windows 8, SSMS2014, and VS2013.

I did not have 2012 previously on this box.

Happens to me as well. SSMS2014 and Windows 7.

Any fix here yet?

Regards,

Glenn

Happens to me. Just made a clean install of Windows 7 and SSMS2014. Nothing else. It's the first thing I put on (after Office). No upgrade, no import, no nothing.

Just a restart every time I close it... :-(

I just repaved my machine for Windows 10, and freshly installed 2016 CTP 2.2 and it's still happening for me.

It was happening to me before I formatted my hard drive, it's happened on multiple machines.

The - "oh it's because you'd need to format your hard drive" to make it as difficult and time-wasting to diagnose is the kind of excuse I'd expect from my IT support team, not from Microsoft.

I think we can be sure that this bug is probably something to do with what else is also installed on your machine, and possibly what order you installed the applications in.

I don't think it helps that SSMS 2014 installs an old version of Visual Studio Shell or that SSDT-BI also installs several old versions of Visual Studio Shell. Getting the latest versions of SSMS, SSDT-BI and VS installs a raft of Visual C++ redistributables from 2005, 2008, 2010, 2012, 2013 & 2015 and VS Shells from 2010, 2012, 2013 and 2015. It really shouldn't be this messy.

I get that SSMS is built on the Visual Studio Shell but surely it should use the latest version, not install three different versions and a host of other bits and pieces.