none
SSMS Database Diagrams - crashes when using SQL Azure databases RRS feed

  • Question

  • I'm using SSMS on a laptop to connect to SQL Azure to work on a database.

    Configuration.

    SQL Server Management Studio      15.0.18183.0
    Microsoft Analysis Services Client Tools      15.0.1487.0
    Microsoft Data Access Components (MDAC)      10.0.17763.1
    Microsoft MSXML      3.0 6.0
    Microsoft Internet Explorer      9.11.17763.0
    Microsoft .NET Framework      4.0.30319.42000
    Operating System      10.0.17763

    I can create a Database Diagram and use the diagram for varying lengths of time until SSMS crashes.

    The Event Log always contains entries as per below....

    Faulting application name: Ssms.exe, version: 2019.150.18183.0, time stamp: 0x5d91b0d3
    Faulting module name: DataDesigners.dll, version: 2019.150.18183.0, time stamp: 0x5d91b0fe
    Exception code: 0xc0000005
    Fault offset: 0x00004be8
    Faulting process ID: 0x3880
    Faulting application start time: 0x01d57d10bf1898f1
    Faulting application path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
    Faulting module path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Tools\VDT\DataDesigners.dll
    Report ID: d11e43d8-89c5-486c-a6dc-a4ff46a27f6b
    Faulting package full name:
    Faulting package-relative application ID:

    Application: Ssms.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
       at Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(System.Guid ByRef, UInt32, UInt32, IntPtr, IntPtr)
       at Microsoft.VisualStudio.Platform.WindowManagement.DocumentObjectSite.Exec(System.Guid ByRef, UInt32, UInt32, IntPtr, IntPtr)
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.Exec(System.Guid ByRef, UInt32, UInt32, IntPtr, IntPtr)
       at Microsoft.Internal.VisualStudio.Shell.Interop.IVsTrackSelectionExPrivate.Register()
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConnectSelectionContext()
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.Activate()
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowManagerService.viewManager_ActiveViewChanged(System.Object, Microsoft.VisualStudio.PlatformUI.Shell.ActiveViewChangedEventArgs)
       at System.EventHandler`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Invoke(System.Object, System.__Canon)
       at Microsoft.VisualStudio.PlatformUI.ExtensionMethods.RaiseEvent[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.EventHandler`1<System.__Canon>, System.Object, System.__Canon)
       at Microsoft.VisualStudio.PlatformUI.Shell.ViewManager.SetActiveView(Microsoft.VisualStudio.PlatformUI.Shell.View, Microsoft.VisualStudio.PlatformUI.Shell.ActivationType)
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ShowInternal(ShowFlags)
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.<Show>b__505_0()
       at Microsoft.VisualStudio.ErrorHandler.CallWithCOMConvention(System.Func`1<Int32>, Boolean, Boolean)
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.Show()
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame+MarshalingWindowFrame.<Microsoft.VisualStudio.Shell.Interop.IVsWindowFrame.Show>b__12_0()
       at Microsoft.VisualStudio.Shell.ThreadHelper.Invoke[[System.Int32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Func`1<Int32>)
       at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame+MarshalingWindowFrame.Microsoft.VisualStudio.Shell.Interop.IVsWindowFrame.Show()
       at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VirtualProject.CreateDesigner(Microsoft.SqlServer.Management.Sdk.Sfc.Urn, Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DocumentType, Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DocumentOptions, Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.IManagedConnection, System.String)
       at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VirtualProject.Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ISqlVirtualProject.CreateDesigner(Microsoft.SqlServer.Management.Sdk.Sfc.Urn, Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DocumentType, Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DocumentOptions, Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.IManagedConnection, System.String)
       at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ISqlVirtualProject.CreateDesigner(Microsoft.SqlServer.Management.Sdk.Sfc.Urn, Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DocumentType, Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DocumentOptions, Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.IManagedConnection, System.String)
       at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDocumentMenuItem.CreateDesignerWindow(Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.IManagedConnection, Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DocumentOptions)
       at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDocumentMenuItem.InvokeDesigner(Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.IManagedConnection)
       at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDocumentMenuItem.Invoke()
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItemBase.MenuInvokedHandler(System.Object, System.EventArgs)
       at System.Windows.Forms.ToolStripItem.RaiseEvent(System.Object, System.EventArgs)
       at System.Windows.Forms.ToolStripMenuItem.OnClick(System.EventArgs)
       at System.Windows.Forms.ToolStripItem.HandleClick(System.EventArgs)
       at System.Windows.Forms.ToolStripItem.HandleMouseUp(System.Windows.Forms.MouseEventArgs)
       at System.Windows.Forms.ToolStripItem.FireEventInteractive(System.EventArgs, System.Windows.Forms.ToolStripItemEventType)
       at System.Windows.Forms.ToolStripItem.FireEvent(System.EventArgs, System.Windows.Forms.ToolStripItemEventType)
       at System.Windows.Forms.ToolStrip.OnMouseUp(System.Windows.Forms.MouseEventArgs)
       at System.Windows.Forms.ToolStripDropDown.OnMouseUp(System.Windows.Forms.MouseEventArgs)
       at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
       at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.ToolStrip.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.ToolStripDropDown.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)

    Is this a known fault, or should I be using .NET 4.5?  The database is in Development and has been deployed and beinig maintained using Entity Framework.  Should I be scripting the schema amd deploying the schema locally (not Azure)?

    Kind Regards.

    Nick

    Monday, October 7, 2019 2:32 PM

All replies

  • Hi 

    This is a known issue as part of SSMS V18.3.1 & Build No - 15.0.18183.0 release notes hope the below is your case.

    Meaning: 

    Database Diagram created from SSMS running on machine A cannot be modified from machine B (SSMS crashes). See UserVoice for more details.

    Reference:- https://docs.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-2017#known-issues-1831

    SQL Server team is working on this. Please vote in the below feedback forum for the same issue resolution request.

    Feedback Forum:- https://feedback.azure.com/forums/908035/suggestions/37992649

    Hope this is helpful !!

    Thank you


    If this post helps to resolve your issue, please click the "Mark as Answer" of that post and/or click Answered "Vote as helpful" button of that post. By marking a post as Answered and/or Helpful, you help others find the answer faster.

    Monday, October 7, 2019 3:23 PM
  • Hi Nick,

    As nkumar states, this is the known issue of SSMS.

    Kirk Hall already raised the same in Azure Feedback forum as below.

    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

    Please go to the below link and vote and subscribe there-

    https://feedback.azure.com/forums/908035/suggestions/37992649

    Currently MSFT team is working on this. you can also subscribe there. So Once the issue has been fixed, MSFT Team will send mail to you.

    Please mark this as answer if it solved your issue. 
    Please vote this as helpful if it helps to solve your issue. 

    Thanks,
    Arulmouzhi



    • Edited by Arulmouzhi Monday, October 7, 2019 5:40 PM Edited for grammer
    Monday, October 7, 2019 5:39 PM
  • Hi Nick McNair,

     

    As mentioned by nkumar230, it is a known issue in ssms18.x. Before it is fixed, I recommend you using ssms17.9.1 first.

     

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Tuesday, October 8, 2019 6:50 AM
  • Hi

    Just checking in to see if my initial reply helped or you still facing any issues.

     

    If my initial reply answers your query, do click “Mark as Answer” and Up-Vote for the same which might be beneficial to other community members reading this thread .

    And, if you have any further query do let us know.

    Thank you


    If this post helps to resolve your issue, please click the "Mark as Answer" of that post and/or click Answered "Vote as helpful" button of that post. By marking a post as Answered and/or Helpful, you help others find the answer faster.

    Tuesday, October 22, 2019 3:41 AM