THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Jamie Thomson

This is the blog of Jamie Thomson, a data mangler in London working for Dunnhumby

SSIS Catalog, Windows updates and deployment failures due to System.Core mismatch

This is a heads-up for anyone doing development on SSIS.

On my current project where we are implementing a SQL Server Integration Services (SSIS) 2012 solution we recently encountered a situation where we were unable to deploy any of our projects even though we had successfully deployed in the past. Any attempt to use the deployment wizard resulted in this error dialog:


The text of the error (for all you search engine crawlers out there) was:

A .NET Framework error occurred during execution of user-defined routine or aggregate "create_key_information":
System.IO.FileLoadException: Could not load file or assembly 'System.Core, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
   at Microsoft.SqlServer.IntegrationServices.Server.Security.CryptoGraphy.CreateSymmetricKey(String algorithm)
   at Microsoft.SqlServer.IntegrationServices.Server.Security.CryptoGraphy.CreateKeyInformation(SqlString algorithmName, SqlBytes& key, SqlBytes& IV)
. (Microsoft SQL Server, Error: 6522)

After some investigation and a bit of back and forth with some very helpful members of the SSIS product team (hey Matt, Wee Hyong) it transpired that this was due to a .Net Framework fix that had been delivered via Windows Update. I took a look at the server update history and indeed there have been some recently applied .Net Framework updates:


This fix had (in the words of Matt Masson) “somehow caused a mismatch on System.Core for SQLCLR” and, as you may know, SQLCLR is used heavily within the SSIS Catalog. The fix was pretty simple – restart SQL Server. This causes the assemblies to be upgraded automatically. If you are using Data Quality Services (DQS) you may have experienced similar problems which are documented at Upgrade SQLCLR Assemblies After .NET Framework Update. I am hoping the SSIS team will follow-up with a more thorough explanation on their blog soon.

You DBAs out there may be questioning why Windows Update is set to automatically apply updates on our production servers. We’re checking that out with our hosting provider right now Smile

You have been warned!


Published Wednesday, July 11, 2012 4:36 PM by jamiet

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



andyleonard said:

Good catch, Jamie!


July 11, 2012 11:48 AM

Mike Davis said:

Good to know!

July 11, 2012 12:38 PM

Mario said:

I checked my update history and i have the same update from 2/18/2013. I restarted my SQL SErver and i still get the same message. Any other ideas? I am sysadmin and have CLR enabled.

February 19, 2013 4:27 PM

Anil said:

Thanks, You just saved my life.

February 13, 2014 5:12 PM

CJ said:

Thanks for this. Just had this issue and this helped.

February 9, 2015 1:51 PM

Lavanya said:

Thank you for the resolution

September 28, 2015 3:42 AM

Prasad emani said:

Thanks worked

May 23, 2016 4:00 AM

Leave a Comment


This Blog


Privacy Statement