Some weeks ago a SQLUG user (Franky) reported a problem when importing existing maintenance plans on a SQL server. You can find more information on this thread. After some research franky found a KB article that describes the problem and you can solve it.
Follow step reproduce the error:
Here you can download a simple maintenance package to reproduce the bug.
- Import an existing maintenance package on your sql server. Connect to the SSIS Store on your SQL SERVER and import the maintenance package under the Maintenance Plans folder of your MSDB store. (Don't change the name of your package)
- Expand the maintenance Plans node under the management node of your object explorer and double click on the imported package. Define a schedule and hit save. If everything went right you should retrieve an error like "Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)."
To workarround this problem I created a tool called Maintenance Plan fixer. It contains the workarround that microsoft suggests to solve the problem. It only works on a SQL server 2005 with SP1. You can download the source of the tool here.
The tool contains so built in checks here is an overview:
- Check if the SQL Server is running
- Check if the version of the version of sql server is SQL SERVER 2005 with SP1
- Check if the package is an maintenance package and if it is not empty.
- Check if there is not a job that is named "Package Name" + "Job"
So here a screenshot of the tool:
If there is any problem please leave me a comment. And enjoy.