"0xe0434f4d" exception and "0xC001000A" error message when you create a maintenance plan on an MSX server

Article translations Article translations
Article ID: 2742131 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You use Microsoft SQL Server 2012, Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2005 as a master server (MSX).
  • You use SQL Server 2012 as a target server (TSX).
  • You create a multiserver maintenance plan on the MSX server.
In this scenario, the maintenance plan is not replicated to the TSX Server. Additionally, an exception message that resembles the following is logged in the SQL Server Agent logs on the TSX Server:

[073] An exception (0xe0434f4d) occurred in the Maintenance Plans subsystem

Note In this error message, "Maintenance Sub Plan Name" is a placeholder for the maintenance sub plan.

The jobs that are related to the maintenance plan are replicated. If you try to execute the job on the TSX Server, you receive an error message that resembles the following:

Execution of job 'Maintenance Sub Plan Name' failed. See the history log for details.

Additionally, the information that resembles the following is logged in the job history:

Could not load package "Maintenance Plans Package" because of error 0xC001000A. Description: The specified package could not be loaded from the SQL Server database.

Note In this error message, "Maintenance Plan Package" is a placeholder for the package name of the maintenance plan.

Cause

This issue occurs because SQL Server Agent cannot find the Microsoft .NET Framework 2.0 assemblies of the database maintenance plan tasks on the TSX server.

Note The assemblies of database maintenance plan tasks are upgraded to Microsoft .NET Framework 4.0 in SQL Server 2012.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Resolution

Cumulative update information

Cumulative Update 2 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative Update 5 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2777772 Cumulative update package 5 for SQL Server 2012
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released

To resolve this issue, you can also create a configuration file for SQL Server Agent on the TSX Server. To do this, follow these steps:
  1. Delete all existing distributed maintenance plans on the MSX Server which was not replicated to the TSX server.
  2. Create a file which name is SQLAGENT.EXE.CONFIG under the following folder on the SQL Server 2012 TSX server:
    %Program Files%\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn
  3. Add the following content to the SQLAGENT.EXE.CONFIG file:
    <?xml version ="1.0"?>
    <configuration> 
    <startup useLegacyV2RuntimeActivationPolicy="true"> 
    <supportedRuntime version="v4.0"/> 
    </startup>
    </configuration>
  4. Restart SQL Server Agent on the TSX server.
  5. Create the new multiserver maintenance plans that are targeted to the TSX server.

More information

For more information about the compatibility of MSX server and TSX server, go to the following Microsoft website:

How to create a multiserver environment

Properties

Article ID: 2742131 - Last Review: January 24, 2013 - Revision: 5.0
Applies to
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
Keywords: 
kbtshoot kbsurveynew kbexpertiseadvanced KB2742131

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com