DQS Not working after SQL 2012 SP2 Applied

Question

Hi all,
On Friday we had our service provider install SQL SERVER SP2 to our dev server from release 11.0.3000 to 11.0.5058 (Post SP deploy), so that we could test it, before rolling out to the production servers. However on this mornings scheduled job we received
the following error from the DQS component : 
=================================================
The component has detected potential metadata corruption during validation.
Error at DFT Maintain Riskcode [DQS Cleansing [61]]: System.Data.SqlClient.SqlException (0x80131904): An error occurred in the Microsoft .NET Framework while trying to load assembly id 65629. The server may be running out of resources, or the assembly may not
be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:
System.IO.FileLoadException: Could not load file or assembly 'microsoft.ssdqs, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' 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 949080 for more information.
System.IO.FileLoadException:
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Ssdqs.Infra.Database.DBAccess.ExecCommand()
   at Microsoft.Ssdqs.Proxy.Database.DBAccessClient.Exec()
   at Microsoft.Ssdqs.Proxy.EntryPoint.BaseEntryPointClient.SetDataQualitySession(Nullable`1 clientId, Nullable`1 knowledgebaseId)
   at Microsoft.Ssdqs.Proxy.EntryPoint.BaseEntryPointClient..ctor(String serverName, String databaseName, Nullable`1 clientId, Nullable`1 knowledgebaseId)
   at Microsoft.Ssdqs.Proxy.EntryPoint.NotificationEntryPointClient..ctor(String serverName, String databaseName)
   at Microsoft.Ssdqs.Component.Common.Utilities.ComponentUtility.VerifyServer(String connectionString, String databaseName)
   at Microsoft.Ssdqs.Component.DataCorrection.Logic.DataCorrectionComponent.Validate()
   at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostValidate(IDTSManagedComponentWrapper100 wrapper)
ClientConnectionId:4c673c65-aa29-43f9-89eb-41eba1aaea13I
=============================
Luckily we only had one component using the DQS as it was a PoC idea to show the business what could be done, without significant overheads to the underlying system, so it was easy to strip out, however I would like to know how to fix this for future reference,
is there a separate SP for DQS or CU that needs to be applied.
We are also seeing the same issue within BIDS, on the work stations that open the relevant package.
Regards
Jason.
Jason

Answer 1

Thanks Pau,
Many thanks for this.
I have been looking around during the day and it seems that its the local machines that are out of sync as well especially with the DQS component.
Its a good job our prod server wasn't updated at the same time, thankfully we have separate DQS servers for dev and Prod, so the impact was limited to Dev alone.
Regards
Jason.
Jason