Forum Discussion
Solved
"Object reference not set to an instance of an object. (SqlManagerUI)"
I have installed SSMS 18.10 and I have connected to Azure SQL Managed Instance, then trying to edit SQL Agent Job always failing to open and resulting is this error "Object reference not set to an ...
- adamoumagaji I do not have that issue with SSMS 19.3, which is the latest release. Can you please try with SSMS 19.3? Thanks.
Goodmorning, same problem on 19.1, tried on multiple Windows (10 & 11).
erinstellato
Microsoft
MicrosoftHi Leonardo_Cursi - can you please provide the steps to recreate? I just tested with 19.1 against Managed Instance with the following steps:
1. I created a new SQL Agent job that had one step - it just runs a simple select statement (SELECT @@VERSION).
2. I saved the job, and then manually executed it to make sure it worked. (It did.)
3. I then right-clicked on the job and selected Properties.
4. In the properties window, I went to the Steps page, selected the job step, and then selected Edit.
5. I modified the script (added another query - select * from msdb.sys.databases) and then selected OK.
6. I selected OK again from the properties window, and then ran the job again.
I did not encounter any errors. If you are able to share your exact steps, that would be helpful to try and recreate the issue here. Thank you.
1. I created a new SQL Agent job that had one step - it just runs a simple select statement (SELECT @@VERSION).
2. I saved the job, and then manually executed it to make sure it worked. (It did.)
3. I then right-clicked on the job and selected Properties.
4. In the properties window, I went to the Steps page, selected the job step, and then selected Edit.
5. I modified the script (added another query - select * from msdb.sys.databases) and then selected OK.
6. I selected OK again from the properties window, and then ran the job again.
I did not encounter any errors. If you are able to share your exact steps, that would be helpful to try and recreate the issue here. Thank you.