Microsoft assemblies failed on load due to a signature mismatch after service pack updates

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » Microsoft assemblies failed on load due to a...

Microsoft assemblies failed on load due to a signature mismatch after service pack updates

Rate Topic

Display Mode

Topic Options

Author

Message

daniel.b.handy

Posted Tuesday, November 29, 2011 4:55 AM

Grasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 2:10 PM
Points: 24, Visits: 810

Hi All,

We upgraded SQL and windows on one of our servers last night, details are below:

MS 2008 Standard x64: Before SP1, after SP2.
MS SQL 2008: Before SP1 CU7, after SP3

The upgrade caused Microsoft assemblies to fail on load due to a signature mismatch in the Global Assembly Cache - http://support.microsoft.com/kb/949080. We fixed the issue by reloading the assemblies.

Does anyone have any idea why this incident occurred? Is it a result of the windows SP install, or SQL SP install?

Any help would be much appreciated.

Thanks,
Daniel BigGrin

Post #1213078

Dev

Posted Tuesday, November 29, 2011 5:38 AM

SSCrazy

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:05 PM
Points: 2,013, Visits: 1,566

Scenario 1
You create a common language runtime (CLR) routine that references a Microsoft .NET Framework assembly. The .NET Framework assembly is not documented in Knowledge Base article 922672. Then, you install the .NET Framework 3.5 or a .NET Framework 2.0-based hotfix.

Scenario 2
You create an assembly, and then you register the assembly in a Microsoft SQL Server 2005 database. Then, you install a different version of the assembly in the Global Assembly Cache (GAC).

It looks like scenario 2 but I am not very sure.

~Dev~

Post #1213117

daniel.b.handy

Posted Tuesday, November 29, 2011 8:20 AM

Grasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 2:10 PM
Points: 24, Visits: 810

Thanks, can anyone else help? I still can’t find the cause.

Post #1213301

daniel.b.handy

Posted Wednesday, November 30, 2011 2:15 AM

Grasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 2:10 PM
Points: 24, Visits: 810

EDIT.

Post #1213734

gayatri.krishnan86

Posted Monday, January 23, 2012 10:39 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, October 05, 2012 3:16 AM
Points: 2, Visits: 16

Hi,

Can you please let me know how to fix this issue?

Post #1240335

Megistal

Posted Thursday, January 17, 2013 8:58 AM

Ten Centuries

Group: General Forum Members
Last Login: Today @ 6:35 AM
Points: 1,243, Visits: 1,776

Temporarily, I've dropped and recreated all custom assemblies which used the specific .Net Framework 2.0 DLL in the database and it works.
This is a workaround and not a fix but it has done the trick for me, for now.

More information can be found here: http://support.microsoft.com/kb/949080

Post #1408478

« Prev Topic | Next Topic »

Permissions