November 29, 2011 at 4:55 am
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 😀
November 29, 2011 at 5:38 am
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.
November 29, 2011 at 8:20 am
Thanks, can anyone else help? I still can’t find the cause.
November 30, 2011 at 2:15 am
EDIT.
January 23, 2012 at 10:39 am
Hi,
Can you please let me know how to fix this issue?
January 17, 2013 at 8:58 am
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
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply