SSMS Database Designer crash - Microsoft.SqlServer.GridControl

[jparker_alpine]

Hi. New user here. I need to post a bug with the Microsoft.SqlServer.GridControl causing a continual crash in SSMS. Please advise or redirect me to the correct location if this is not a good place to address it.

Issue: SSMS crashes on open of existing database design.

SSMS version Info:

SQL Server Management Studio 15.0.18386.0
SQL Server Management Objects (SMO) 16.100.46437.65
Microsoft Analysis Services Client Tools 15.0.19618.0
Microsoft Data Access Components (MDAC) 10.0.19041.1
Microsoft MSXML 3.0 6.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.19042

Event Viewer Logs:

Application: Ssms.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
at Microsoft.SqlServer.Management.UI.Grid.ScrollManager.SetHorizontalScrollUnitForArrows(Int32)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnFontChanged(System.EventArgs)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.InitDefaultEmbeddedControls()

Exception Info: System.Reflection.TargetInvocationException
at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.WndProc(System.Windows.Forms.Message ByRef)
at Microsoft.SqlServer.Management.DataTools.UI.Grid.GridControl.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)

Log 2:

Faulting application name: Ssms.exe, version: 2019.150.18386.0, time stamp: 0x60e54ecb
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1202, time stamp: 0x448a4f5d
Exception code: 0xe0434352
Fault offset: 0x0012b5b2
Faulting process id: 0x7a28
Faulting application start time: 0x01d7b0b7022ce738
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: ba25200d-260a-478f-b438-6106a11e12c6

Log 3:

Fault bucket 1412788278358014022, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Ssms.exe
P2: 2019.150.18386.0
P3: 60e54ecb
P4: Microsoft.SqlServer.GridControl
P5: 15.0.18386.0
P6: 60e54ec3
P7: 52d
P8: e
P9: System.ArgumentException
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERECBB.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6CF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6EF.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6F1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF730.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Ssms.exe_fa52bfc67d7b82349cb58e838d6520f21f5a88_62713db4_8e17df09-e7a4-424c-a2fe-7cb4525ed0e7

Analysis symbol:
Rechecking for solution: 0
Report Id: ba25200d-260a-478f-b438-6106a11e12c6
Report Status: 268435456
Hashed bucket: 5363fcfa51f78614739b3b74325d7846
Cab Guid: 0

Please let me know if any other information will help or if I need to post in another location.

Thanks,

Jon

[#2]

@jparker_alpine , what for a "Database Designer" do you mean, I am not aware there is one in SSMS?

---

SSMS version Info:

SQL Server Management Studio 15.0.18386.0

---

That's a very old version, current one, latest is 18.9.2, you can download it from Download SQL Server Management Studio (SSMS)

[#3]

@olafhelper Ty for your reply. That is odd that the version info for ssms would indicate that it's old. I do have the latest version installed. 

Any thoughts on why it would be different? Am I upgrading it wrong I wonder?

Yes, it's had a database designer for some time. Although I've been getting hints that it's lacking some love from MS. :unamused_face: This is the feature I'm referring to when it crashes.

[#4]

@jparker_alpine That's the ERD = Entity Relationship diagram, it's known as buggy and no one uses it.

[#5]

@olafhelper I use it all the time. It does have bugs. I'd like to get them fixed if possible.