SSMS 17.6 Crash when opening scheduler task for a maintenance task
When conencting for far to
I crash anytime I try to open the scheduler task, I still had a VM with 17.4 and this works correctly on the same versions.
New or already created one. No time to enter or modify as it crash on load.
Event id 1000
Faulting application name: Ssms.exe, version: 2017.140.17230.0, time stamp: 0x5aa77b02
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x15723a35
Faulting process id: 0x163c
Faulting application start time: 0x01d3c19109d5c915
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe
Faulting module path: unknown
Report Id: b943e485-d868-45b1-832e-09b4f570a55b
Faulting package full name:
Faulting package-relative application ID:
Event id 1000
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.grid_MouseButtonClicked(System.Object, Microsoft.SqlServer.Management.UI.Grid.MouseButtonClickedEventArgs)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseButtonClicked(Int64, Int32, System.Drawing.Rectangle, System.Windows.Forms.MouseButtons)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.HandleButtonLBtnUp(Int32, Int32)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.ProcessLeftButtonUp(Int32, Int32)
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 Microsoft.SqlServer.Management.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)
This should be fixed in the current version of SSMS.
It’s a duplicate of https://feedback.azure.com/forums/908035/suggestions/33712924.
If you think it is not fixed (or you see something else wrong), please open a new UserVoice item and provide more detailed steps so we can investigate further. Thanks!
Mike Williams commented
This problem still occurs in 17.7 for me.
John Doe commented
17.7 is already out and this issue has been resolved in that release.
Lawrence McIlhoney commented
Matt - one workaround if you can't go back is to connect from another SQL Management Studio (I'm using 2014 from my own PC, but you could also do it from another server) and do the scheduling via that. It's annoying but will tide you over until Microsoft get their software sorted.
bombs on me every time too. Workaround was to save the SubPlan --> go into the job --> properties --> schedule --> do it there. DON'T expect doing it there will resolve the Maintenance plan schedule icon, it will still bomb SSMS. Just schedule in JOBS area and wait for the ol' SU
Richard Northcott commented
I have the same problem, hopefully 17.7 won't take too long before it's released.
Same here. I uninstalled this version 17.6 and install 17.5. It works. Hope this issue will be fixed soon.
We have the same problem on differnt servers. When is this fix comming? a year later?
Peter Riederer commented
same Problem here, when will the fix in 17.7 arrive?
Unistall 17.6 and reinstall 17.5 worked for me.
(just installing 17.5 without uninstalling 17.6 will not work)
Okay, so what do I do in the meantime?? How do I backup my databases on a daily basis and on a weekly basis? I just moved all my databases to a new server and there is no going back now.