Issue about upgrading sql server 2012 sp1

Question

After upgrading to sql server 2012 sp1, running dqsintaller.exe -upgrade,then an issue happens:

An error occurred in the Microsoft .NET Framework while trying to load assembly id 65572. 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:
[7/30/2011 11:28:06 PM] System.IO.FileLoadException: Could not load file or assembly 'microsoft.ssdqs.core, 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.
[7/30/2011 11:28:06 PM] System.IO.FileLoadException:
[7/30/2011 11:28:06 PM]    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
[7/30/2011 11:28:06 PM]    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
[7/30/2011 11:28:06 PM]    at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
[7/30/2011 11:28:06 PM]    at System.Reflection.Assembly.Load(String assemblyString)

How to fix it?

Answer 1

Running -upgradedlls, DQS client is working now. But when I check the version of dqs_main and dqs_project, it still is 11.0.2845, not 11.0.3000.

So, how to upgrade these databases?

Answer 2

I take it you are running something like

SELECT * FROMDQS_MAIN.dbo.A_DB_VERSION WHERESTATUS=2; 

1000 2012-11-15 08:11:07.650 1200 11.0.3000.0
1001 2012-11-15 08:13:42.410 1600 11.0.3000.0

SELECT * FROMDQS_PROJECTS.dbo.A_DB_VERSION WHERESTATUS=2;

1000 2012-11-15 08:11:07.667 1200 11.0.3000.0
1001 2012-11-15 08:13:42.413 1600 11.0.3000.0

  

With you getting the version for the CTP4 I would uninstall both the SP1 and CTP4 updates and then re-apply the SP1.

Answer 3

incognito007,

11.0.2845 is SP1 CTP - community technical preview of SP1 -. you need to install the final release of  SP1 http://www.microsoft.com/en-us/download/details.aspx?id=35575

If you still have question or issues with this I recomend you use the SQL Server Setup & Upgrade forum http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/threads

---

Help Others! Don't forget to mark your thread as answered

Answer 4

My issue is:

Everything such as database enigne,analysis service,etc. is 11.0.3000, except these two DQS databases is 11.0.2845.

Also, I uninstall the DQS feature and reinstall it, the version still is 11.0.2845.

Answer 5

You can post the issue on Connect:

https://connect.microsoft.com/SQLServer

Also you may call MS customer support.

---

Kalman Toth SQL 2008 GRAND SLAM
New Book: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2012

Answer 6

You may not have any problems at all now since you fixed it with -upgradedlls.

Maybe there is no schema change since the version that you had - did you start with a later CU3 build then you might have the latest schema update.

Thanks, Jason

---

Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance

Answer 7

Right now I am still quite confused about this issue.

According to the latest article from DQS team blog, it should run the command of DQSinstaller -upgrade since there is a shcema upgrading required(the version 11.0.3000.0). My problem is that when I run this command, the log file displays that

DQS version is up to date, no upgrade scripts will be run.

Action 'Upgrade data quality schema' finished with errors, aborting installation.

DQS Installer finished with errors Please see installation log at C:\Program Files\Microsoft SQL Server\MSSQL11.InstanceName\MSSQL\Lot\DQS_install.log

Press any key to continue...

That means, based upon Microosft Technet "Upgrade DQS: Installing Cumulative Updates or Hotfix Patches on Data Quality Services (en-US)",if no schema upgrade is required, DQSInstaller will report failure text immediately.

My current version is:

DQS client help: 11.0.3000.0

DQS database

1000 2012-04-21 08:57:13.650 1400 11.0.2316.0 2 
1001 2012-11-03 14:51:14.757 1600 11.0.2845.0 2 

Also, I check my SQL Server 2012 updating history:

KB2765331    Version 11.0.3321.0

KB2674319    Version 11.0.3000.0

KB2674317    Version 11.0.2845.0

My question is, in the above two articles, I could not find the version 11.0.2845.0 and KB2674317, how can I upgrade the schema from the version 11.0.2845.0 to the version 11.0.3000.0?

Answer 8

I think that version 11.0.2845 is the CTP beta for Service Pack 1, so I didn't include it in the wiki page I made, since I figured most folks wouldn't have that build since it is not a common release build for a production system. Did you remember installing the CTP? I didn't test that myself (Not enough PCs to test each permutation) so I couldn't commit to putting it in the wiki chart.

KB2674317    Version 11.0.2845.0 aka http://support.microsoft.com/kb/2674317

Wiki here for quick reference by others - http://social.technet.microsoft.com/wiki/contents/articles/8442.upgrade-dqs-installing-cumulative-updates-or-hotfix-patches-on-data-quality-services-en-us.aspx

I think you have the latest schema updates to the DQS  databases. At the time of CTP they couldn't know what the final build number would be, so they couldn't bump the schema version to 3000 at that time.

There were changes made after the CTP to the binaries before the final SP1 release, such as making the .Net framework updates compatible with DQS, so they did bump up the version to 3000 on the binaries.

I have noticed that discrepancy before - when a DQS binary upgrade doesn't have a DQS schema update, the binary revision is required using the -upgradedlls switch, and that switch doesn't touch the table to upgrade the version number. I wish it did, because the discrepancy in version numbers is unnerving. Its messy at best - yes.

Thanks, Jason

---

Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance