Post reply

A .NET Framework error in SQL server 2008 R2

  • January 18, 2013 at 11:58 am

    #268832

    Hi All,

    one of our System monitor job is failing with the below error.

    '' Executed as user: REDMOND\MyServiceAccount. Start - SP spAddSGUsersToRGMetaData at 2013-01-17T12:00:01.9155919 [SQLSTATE 01000] (Message 50000) Msg 6522, Level 12, State 1, Procedure spGetSGMembers, Line 0 A .NET Framework error occurred during execution of user-defined routine or aggregate "spGetSGMembers": System.IO.FileLoadException: Could not load file or assembly 'System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Assembly in host store has a different signature than assembly in GAC. (Exception from HRESULT: 0x80131050) See Microsoft Knowledge Base article 9490 [SQLSTATE 42000] (Error 50000). The step failed.

    A .NET Framework error occurred during execution of user-defined routine or aggregate : System.IO.FileLoadException: Could not load file or assembly 'System.DirectoryServices, , Culture=neutral, one of its dependencies. Assembly in host store has a different signature than assembly in GAC. (Exception from HRESULT: 0x80131050) See Microsoft Knowledge Base article 9490 [SQLSTATE 42000] (Error 50000). The step failed.''

    Select * from sys.dm_clr_properties gave me C:\Windows\Microsoft.NET\Framework64\v2.0.50727\.

    But when i go and checked at the actual location I saw a newer version folder which was installed yesterday i,e v4.0.30319

    I'm not sure how to change the version from older to newer version from SQL Instance point of view..

    Can you please help me resolve this issue...

  • January 21, 2013 at 3:59 am

    #1579173

    http://support.microsoft.com/kb/949080

    Workaround 1

    To work around scenario 1 in the "Symptoms" section, you must manually update the .NET Framework assemblies in SQL Server. To do this, use the ALTER ASSEMBLY statement to point to the new version of the .NET Framework assembly in the following folder:

    %Windir%\Microsoft.NET\Framework\Version

    Note Version represents the version of the .NET Framework that you installed or updated.

    Workaround 2

    To work around scenario 2 in the "Symptoms" section, use the ALTER ASSEMBLY statement to update the assembly in the database.

    If the problem still exists after you do this, drop the assembly from the database, and then register the new version of the assembly in the database.

    The SQL Guy @ blogspot[/url]

    @SeanPearceSQL

    About Me[/url]

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply