how to fix maintinence plans wizard for SQL Server 2022 this is unavailable

how to fix maintinence plans wizard for SQL Server 2022 this is unavailable

Even with adding the SSIS and SSAS components on install, SSMS 22 won't open or modify maintenance plans. So we're stuck with having SSMS 21.6.17 with SSIS and SSAS installed.

Here's the error message:

Value cannot be null.

Parameter name: component (System.Design)

------------------------------

Program Location:

at System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent component)

at Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)

at Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()

I was able to go through the wizard and add a plan on my machine.

I recommend that you report this on the feedback site for SSMS. Try to be as detailed as possible, and include the steps you take. If the SSMS cannot repro the issue, it will be very difficult for them to fix it.

You don't give much details, so I will have to do some guessworks and my answer may not match your situation. If so, please provide more details.

Originally, when SSMS 21 was released, support for SSIS and maintenance plans was not present. This was added in later releases. However, it is an optional component, so just upgrading SSMS 21 is not enough.

You need to go to https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms to download vs_SSMS.exe (unless you know where you have it locally). Start it, and then select Modify:

In the screen you get, select SSIS:

This will also select SSAS.

Hi Martinez,

I hope the explanation helped you with your question. If you have any query, you can reach out.

Thank You
Shruti

Hi Martínez Peña Eusebio II,

Since we didn't hear back, we would be closing this thread. If you need any assistance, feel free to reach out.

Thank you for reaching out on SQL Community Forum
Regards,
Shruti

I have the same problem. Unfortunately installing SSIS and SSAS didn't solve the problem for me.

So what happens in your case? Any error message? Screenshot to illustrate?

I get a error popup, when I try to open a maintenance plan:

Invalid class string

Value cannot be null.
Parameter name: component (System.Design)

------------------------------
Program Location:

   at System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent component)
   at Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)
   at Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()

That's not the behaviour when you don't have the SSIS support installed - in that case, the alternative is entirely grey out or missing.

You seem to have gone past stage, but unfortunately something is not working on your machine. I'm afraid that I have very little clue what might be wrong. I can only suggest things like uninstall/reinstall, but I'm only clutching at straws.

Hi Erland, last SSMS Update fixed this for me. Maintenance Plan Editor now opens and works like expected.

Hello,

I have the opposite problem: Last update broke this feature. Maintenance Plans worked before the last update, now it is broken with the same error message:

===================================

Value cannot be null.
Parameter name: component (System.Design)

------------------------------
Program Location:

   at System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent component)
   at Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)
   at Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()

I already disabled and re-enabled SSIS (and SSAS and SSRS) in the visual studio installer and even did a repair-installation, but to no avail.

Any ideas how to fix this?

Not that I think we can help you much, but can you please ask a new Question rather than piggybacking on an old. Please also give the exact steps for this to happen.

Hello,

just FYI: the next update - SSMS 22.3.0 - fixed the problem again.