This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 64%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENB%3C/text%3E%3C/svg%3E)
I have SSMS installed 18.10 version and I am trying to edit a job step in Azure Managed Instance, that is always causing error "Object reference not set to an instance of an object. (SqlManagerUI)"
Here is the full error details.
===================================
Object reference not set to an instance of an object. (SqlManagerUI)
Program Location:
at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition.OnDeselecting(Object sender, TabControlCancelEventArgs e)
at System.Windows.Forms.TabControl.OnDeselecting(TabControlCancelEventArgs e)
at System.Windows.Forms.TabControl.WmSelChanging()
at System.Windows.Forms.TabControl.set_SelectedIndex(Int32 value)
at System.Windows.Forms.TabControl.ControlCollection.Remove(Control value)
at System.Windows.Forms.Control.ControlCollection.Clear()
at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition.InitializeControls()
at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition..ctor(CDataContainer dataContainer, IMessageBoxProvider messageProvider)
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepSubSystems.CreateJobStepSubSystemSsis(AgentSubSystem agentSubSystem, CDataContainer dataContainer, JobStepData data, IMessageBoxProvider messageProvider)
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepSubSystems.CreateJobStepSubSystem(AgentSubSystem agentSubSystem, CDataContainer dataContainer, JobStepData data, IMessageBoxProvider messageProvider, IServiceProvider serviceProvider)
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepSubSystems..ctor(CDataContainer dataContainer, JobStepData data, IMessageBoxProvider messageProvider, IServiceProvider serviceProvider)
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.get_SubSystems()
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.FilterStepCombo(DatabaseEngineEdition engineEdition)
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.InitializeStepCombo()
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.InitializeData()
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.OnInitialization()
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SetView(Int32 index, TreeNode node)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SelectCurrentNode()
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.InitializeUI(ViewSwitcherTreeView treeView, ISqlControlCollection viewsHolder, Panel rightPane)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(ISqlControlCollection control, IServiceProvider provider)
at Microsoft.SqlServer.Management.SqlManagerUI.JobSteps.OnDoubleClick(Object sender, MouseButtonDoubleClickedEventArgs args)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseButtonDoubleClicked(HitTestResult htArea, Int64 nRowIndex, Int32 nColIndex, Rectangle rCellRect, MouseButtons btn, GridButtonArea headerArea)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlManagerUIDlgGrid.OnMouseButtonDoubleClicked(HitTestResult htArea, Int64 rowIndex, Int32 colIndex, Rectangle cellRect, MouseButtons btn, GridButtonArea headerArea)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseDown(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
Additional SQL Server features and topics not covered by specific categories
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 2%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESX%3C/text%3E%3C/svg%3E)
Hi @Nama Budidi ,
We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.
Best regards,
Seeya
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 84%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKI%3C/text%3E%3C/svg%3E)
I have found a solution to this, first uninstall SSMS then download SSMS v18.9.2 from here
I think this is an issue with SSMS v.18.10, so I removed it and downgraded to the lower version and now I'm able to edit job steps.
Interesting. You don't seem to be the original poster. When you had problems with 18.10, was that also with Managed Instance?
It could be that the uninstall and re-install repaired something that was broken on your machine and the SSMS version as such does not matter. But I understand if you don't want try to upgrade again, but prefer to be sure that things are working.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 50%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Just to add that I tried a repair on v18.10 and that didnt work. I am going to uninstall this version. Other versions work fine.
Hi,
You should open a feedback at Microsoft system and provide the link to the feedback so we will be able to vote for it.
As I wrote several hours ago, this seems like a bug in the SSMS 18.10 specifically. Open the feedback and get the credit as the one who reported it :-)
https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0
Hi, yes it was on a managed instance
Hi all - This issue has been fixed in SSMS 18.11 https://learn.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-ver15
Hi everyone. I wanted to update this thread that the PG is aware of this issue and working on a fix. The issue is specific to the code path with Managed Instance and SSMS 18.10. Barring any unforeseen changes, this issue should be resolved with the next release of SSMS. Please keep in mind this is unlikely to but possibly could change. Unfortunately I cannot provide a timeline for the release at this moment in time. For now, the recommended mitigation is to downgrade your installation of SSMS to prior to 18.10 as was already suggested and implemented in this thread.
We apologize for any inconvenience and appreciate you flagging this issue.
Thanks,
James Ferebee - MSFT
I can confirm that there is a bug in SSMS 18.10
when I try to use steps in the job using SSMS 18.10 on Azure managed instance we get error, but this works well in SSMS 18.9.1
Hi @Nama Budidi ,
Welcome to Microsoft Q&A!
It seems that you are using the GUI to edit the job step.
At present, it seems that the GUI of ssms does not support some functions in Azure Managed Instance.
It seems that the GUI of ssms does not support some functions in Azure Managed Instance.
You can use T-SQL to perform the steps you want to complete: Modify a Job.
You can also submit feedback about SSMS here: https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0
Best regards,
Seeya
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
At present, it seems that the GUI of ssms does not support some functions in Azure Managed Instance.
If that would be the case, SSMS should expose the option, so that alone would be a bug.
I find it difficult to believe that SSMS would support editing jobs in Azure MI. Unfortunately, I don't have any Azure MI myself (it's a bit pricey :-( ), so I cannot test myself.
But surely, Seeya, as working for Microsoft, you have an access to MI to run a test?
I also have the same issue with this version, 18.10 and all 3 Managed Instances, but all the server based SQL Server instances I connect to are still fine\ do not have this error.
I am going to uninstall v18.10 like another poster suggested as the repair didnt work.
It is far too laborious to use TSQL for all purposes that I regularly use SQL Agent for - I would be there all day making scripts and changing scripts.
This is yet another MI PaaS related issue that I have seen - not great for PaaS offering, very buggy and time consuming platform indeed in general.
PaaS MI offerings don't really live up to all the hype, if you ask me :)
I should add that I have edited SQL Agent jobs on MI's with previous versions of SSMS without issue and I have another platform running an older SSMS that I can still use to edit via GUI. So it is this SSMS version that has this issue \ introduced the bug we see now
Here is the link of feedback:
https://feedback.azure.com/d365community/forum/04fe6ee0-3b25-ec11-b6e6-000d3a4f0da0
Well, it was working perfectly before I upgrade to 18.10 with all other versions, I was able to edit the jobs steps using GUI for a managed instances