SQL Server "GUID should contain 32-digit number with 4 dashes"

Transferred from: http://www.seayee.net/article/info_106.html

The recent maintenance plan for MS SQL Server 2005, which configures a server, automatically backs up the database and can create a maintenance plan, but after setting the run time, save the hint "the GUID should contain a 32-digit number with 4 dashes" ( XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX) "wrong, very uncomfortable!

Check the Internet to see if there is a solution, the first one is Microsoft's help and support of a "error when you try to save a maintenance plan in SQL Server Management Studio: Error message: The Guid should contain 4 dashed lines (xxxxxxxx-xxxx-xxxx-xxxx-xxxx XXXXXXXX 32-digit "" article, should be this error, the error description is very clear, the solution is also very detailed, but it is not to see, too long.

Find out again finally found a master summary of two reasons:

First, no patching

Microsoft SQL Server 2005 Service Pack 3:HTTP://WWW.MICROSOFT.COM/DOWNLOADS/ZH-CN/DETAILS.ASPX?DISPLAYLANG=ZH-CN &familyid=ae7387c3-348c-4faa-8ae5-949fdfbe59c4

Second, the integration service is not installed when you install SQL Server 2005, and you can create a maintenance task successfully after adding some components.

According to the situation I encountered, is able to create a maintenance plan, but set the execution time of the maintenance plan to prompt the above error. So I didn't check this one, just patched it up. Based on previous experience, add the following point.

Third, the SQL Server Agent (MSSQLSERVER) startup mode is set to "automatic"

SQL Server Agent is a task planner and alert manager that, in real-world applications and environments, you can define periodic activities as a single task and have them run automatically with the help of SQL Server Agent. When the SQL Server Agent does not start a scheduled task, it cannot execute, and its startup mode defaults to "manual".

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

Personal solutions:

After you finally try the above steps or cannot insert the data, please use the SQL statement to operate, reduce the effect of unnecessary symbols