SSMS 18.1 Crashes when Opening a Database Diagram
SSMS 18.1 crashes (and restarts) when opening a database diagram without any error message.
I have created several diagrams from scratch thinking it might have to do with old formatting, but this does not appear to be the case.
You can edit a diagram (adding dozens of tables) with no problem. It is the opening of the diagram that results in the crash.
Latest bits for SSMS and SQL Server 2017 installed today.
SQL Server Management Studio 15.0.18131.0
Microsoft Analysis Services Client Tools 15.0.1347.0
Microsoft Data Access Components (MDAC) 10.0.18362.1
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.18362.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.18362
The fix for database diagrams was included in SSMS 18.6. For more information, please see https://cloudblogs.microsoft.com/sqlserver/2020/07/22/sql-server-management-studio-18-6-is-now-generally-available/.
Matias Espinoza commented
when a new table is created in the diagram, it creates it perfect but then it does not allow you to do anything in the diagram, I have the latest version installed
Dekarske, Mike commented
This isn't fixed. A new diagram created with 18.6 cannot be opened.
I have never had a problem with my DB diagrams, 18.6 absolutely hammered the diagram I created 9 years ago, in 18.6 it is empty, in 18.5.1 it crashes SSMS, what kind of a fix is this???
I have 120+ tables and relationships, recreate it?
what a POS
Dean J. commented
From the release notes for the new 18.6 version...
"If you created a diagram using SSMS 18.0 through 18.5.1, and that diagram includes a Text Annotation, you won't be able to open that diagram in any version of SSMS [it will be blank]."
Jeff Birrer commented
I see that it is not crashing any longer, but it isn't loading the diagram. Just a blank screen. Did I miss something? Seems like I'm not the only one having this issue. Please reopen.
I have the same problem with v18.6. SSMS crashes also when trying to open a query editor window or try to open a table to see the records.
Faulting application name: Ssms.exe, version: 2019.150.18338.0, time stamp: 0x5f08d254
Faulting module name: clr.dll, version: 4.7.3620.0, time stamp: 0x5e7d1e55
Exception code: 0xc00000fd
Fault offset: 0x004557dd
Faulting process id: 0x2720
Faulting application start time: 0x01d6658e957e5575
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: c90a1482-f113-4848-8984-d58e1283a0ff
Faulting package full name:
Faulting package-relative application ID:
Daniel Seara commented
Please, unmark it as completed, since it is not true. I already have 4 hungs in a row with this.
Just SSMS is colsed and reopened (or just closed).
Below is the event data.
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
Rodrigo Ratan commented
It certainly improved but there are some diagrams that I created in SQL 2017 that are not opening (or opening 'blank')... It wont crash/implode anymore but also wont display anything
After installing the new version 18.6 all my diagrams are blank. There is no message just a blank screen. What?!! I have to recreate all my diagrams from scratch? Arghhhh.... How can you provide an "upgrade" to fix an issue without a migration path? It certainly would be nice if there were some sort of tool that could help preserve the existing diagrams and migrate these into a new structure. Can someone please confirm that indeed there is no way to restore my existing diagrams and that i need to recreate them all from scratch? I manage several databases and each database has several diagrams.
Still doesn't work completely. Just tested new version and had to delete all old diagrams. Create new diagram and saved it. This worked, then exited SSMS and came back in. Tried re-loading diagram and while it doesn't crash, all the of the Tables are blank with "Loading..." as the table name title. Ok, then went to close again and it said that I had a modal window blocking (wasn't one open) and had to accept to close anyway. Restarted SSMS and this time, diagram did load. So... works more often than it did before, but definitely not bug-free. Thanks for getting to this point, hopefully it can get more stable in the next release
Thanks Drew for this fix.
I am able to access and edit my database diagrams created in SSMS (SQL Server 2008) without crashing (see exceptions below). Since the diagrams I created in SSMS 18.5 only appear as a blank screen, there's nothing more to do than to delete them and start over in 18.6.
I noticed however that SSMS 18.6 will still crash under the following conditions:
1. When opening a diagram created prior to 18.x that has very many tables. The diagram will open, and after a few seconds 18.6 will report an error message saying "SSMS 18 has stopped working. A problem caused the program to stop working correctly. Windows will close the program to notify you if a solution is available." The buttons shown are Debug and Close Program.
2. While one works with relational joins - specifically when one clicks and holds a relational join for about a minute. Normally, this should never happen. However, few people will click on and hold a relational join line for that length of time. Still, this bug should be looked into.
I'm using SSMS 18.6 with Windows 10 version 2004. We are using SQL Server 2017 RTM.
Jaco Van Zyl commented
Looks to be working up to when I close the saved diagram, the whole SSMS crashes!!
Just a quick thanks Drew for finally getting diagrams fixed. Kudos!
Whilst diagrams are working for me now, I'm still seeing a single schannel error in the event logs each and every time that a diagram is opened.
EventId: 36882, "The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
Fabio La Vitola commented
With few tables it seems not to crash, but when creating a diagram with many tables... BOOM !!!! (as always)
Thomas Phaneuf commented
I use the heck out of the diagrams but SSMS 18 has been a mess. Please fix as soon as possible!
David Lucre commented
Pretty sure this fix just prevents SSMS from crashing when opening a corrupted diagram. They now open to a blank page. As far as I know there is no way to recover that diagram.
Delete it and re-create it, and make sure everyone is upgraded to 18.6.
Not great that the data is lost, but at least re-creating and opening diagrams in 18.6 seems to work fine now. Thanks for the fix!
Dean J. commented
From the release notes for the new 18.6 version...
"If you created or saved a diagram using SSMS 18.0 through 18.5.1, and that diagram includes a Text Annotation, you won't be able to open that diagram in any version of SSMS."
If the diagram previously had a text annotation, but you've already removed that, then it looks like it will still be a blank screen when opening it with 18.6.
Text annotations should be fine if the diagram is first created with 18.6.
Roger Jose Ulate Rivera commented
hiii, ahhhh, the fix is not working for me.
I had several diagrams display a blank layout and several that opened beautifully. The blank layouts had, at one point, text annotations in them but were deleted when they weren't useful anymore. Remaking these diagrams was possible so this is definitely a fix.
Need help with setup