github twitter linkedin
SSMS 2012–Object Reference issue with Maintenance Plans
21 Jul 2014
2 minutes read

I am amazed at some of the information you can find on the Internet when searching for an issue. Especially with forum posts that mention your issue (or flat out are the exact same), but do not include any final resolution. The best one I came across was this one on SQLTeam’s forum site, the post by “prett”, and note that this is posted back in 2013:

The Maintenance Plan is actually built with few services which Microsoft releases such as SSIS and SQL Server Job Agent, hence if you want to schedule the maintenance plan then your server needs to have SSIS in order to build the maintenance plan, and Job Agent in order to run at regular periods. This error message “Object reference not set to an instance of an object” occurs because of one of the required component was not available on the server.

SQL Server 2005 started out requiring SSIS to be installed for maintenance plans to run, however when Service Pack 2 was released they removed that requirement. As far as I know after that any release of SQL Server kept that same functionality.

Well I came across this issue on my VMWare View desktop that I utilize for one particular client. I was getting this pretty little box every time I tried to create a new maintenance plan on a newly built SQL Server 2012 Failover Cluster Instance:

The version of SSMS I was using:

I thought I would apply Service Pack 2 to try and resolve it and noted during that installation it was showing “SQLExpress”. Which did bring to mind that I had installed SQL Server 2012 Management Studio for Express when it was announced that it was the full version of SSMS now. I confirmed this by going to the “Setup Bootstrap” and checking the Summary files for the previous installations on the desktop. I found this:

So I went to Programs and Features and removed it. I then located the installation media for SQL Server 2012 Standard Edition and installed the Management Tools. Then for good measure applied Service Pack 2 for SQL Server 2012:

Low and behold, that solved my issue. I hope those in the future can find this bit of information useful.

Tags: sqlserver

Back to posts