FIX: You can’t create or open SSIS projects or maintenance plans after you apply Cumulative Update 3 for SQL Server 2012 SP1

Applies to: SQL Server 2012 Business IntelligenceSQL Server 2012 EnterpriseSQL Server 2012 Developer More

Symptoms



Issue 1

Assume that you apply Cumulative Update 3 for Microsoft SQL Server 2012 Service Pack 1 (SP1) to your instance of SQL Server. When you create a SQL Server Integration Services 2012 (SSIS 2012) project, or when you open an existing SSIS project in SQL Server Data Tools (SSDT), you receive the following error message:
TITLE: Microsoft Visual Studio
------------------------------
The type initializer for 'Microsoft.DataTransformationServices.Design.SharedIcons' threw an exception.
------------------------------
ADDITIONAL INFORMATION:
Value of 'null' is not valid for 'stream'. (System.Drawing)
Issue 2

Assume that you apply Cumulative Update 3 for SQL Server 2012 SP1 to your instance of SQL Server. When you create a maintenance plan, or when you edit an existing maintenance plan in Microsoft SQL Server Management Studio (SSMS), you receive the following error message:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Provide value on 'System.Windows.Markup.StaticExtension' threw an exception. (PresentationFramework)
------------------------------
ADDITIONAL INFORMATION:
Exception has been thrown by the target of an invocation. (mscorlib)
------------------------------
The type initializer for 'Microsoft.SqlServer.Graph.Extended.HighContrastSupport' threw an exception. (Microsoft.SqlServer.IntegrationServices.Graph)


Resolution


Cumulative update information

Cumulative Update 4 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to go to the article in the Microsoft Knowledge Base:
2833645 Cumulative update 4 for SQL Server 2012 SP1
Note Given that 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 go to 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

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.



Status


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