DQS Install Issue for Denali

Question

When execute DQSInstaller.exe, the log for error is below:

 Msg 10314, Level 16, State 11, Server USER-PC\MARTIN, Line 1
[7/30/2011 11:51:40 AM] 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:51:40 AM] 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:51:40 AM] System.IO.FileLoadException:
[7/30/2011 11:51:40 AM]    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:51:40 AM]    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
[7/30/2011 11:51:40 AM]    at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
[7/30/2011 11:51:40 AM]    at System.Reflection.Assembly.Load(String assemblyString)

 

How can I resolve the issue?

 

Answer 1

Hi,

The simple solution is to install Denali CTP3 on a clean machine (with no previous DQS installation).

We're investigating the problem and we'll update you soon with a workaround, in case you can't install on a clean machine.

Thanks,

Omer

Answer 2

The problem is caused by inappropriate handling of DQS assemblies installed in the GAC from previous version.
If you would like to prevent the need to use a clean machine, a possible solution is to uninstall the DQS and SSIS features from your current installation (this will remove the old assemblies), and then install Denali CTP3.

Thanks,

Omer

Answer 3

I got this exact same error message on a clean install of Denali.  I am running on Windows 7 64-bit platform.  It seems there is some sort of .NET patch or something that is causing a dependency issue with CTP3.  Is there any additional information that I can provide to resolve this issue?  I really would like to play with DQS as I have a really good project that could utilize it, but can't get past the install.

Answer 4

Hello,

Can you please check the following, go to C:\Windows\assembly find the file Microsoft.SSDQS.core, right click properties, go to the version tab and let us know which file version is listed there ?

Thanks,
Neta

Answer 5

Microsoft.Ssdqs.Core.dll

11.0.1515.0

public key token: 89845dcd8080cc91

Answer 6

There are two variations I know of this error.

1. If you install a .Net Patch from Windows update, and DQS stops working with this error, to fix it, follow the steps and the script in section 4.23 of this article.

Release notes: http://social.technet.microsoft.com/wiki/contents/articles/3711.aspx see section 4.23

Note this method only works for .Net patches such as patch to system.web that were made via KB2416472 or other .Net patches.

To see if you have this variation, check in your Control Panel > Add Remove Programs, check the box to show the updates, and it will show "Update for Microsoft .NET Framework 4 Client Profile (KB2473228)" or a similar .Net Framework update.

Normally DQSInstaller.exe can repair the variation of the error , but it will drop any projects you have already started working on, which makes the script in the above URL more desirable for most folks.

2. If you have recently deployed a special SQL Denali test patch 11.0.1515 that comes from Microsoft Update used for testing SQL Denali SmartSetup, as Peter Saddow from the SQL Setup team describes here in his blog, it may be a bug that is not fully understood yet. Microsoft is investigating currently.

http://blogs.msdn.com/b/petersad/archive/2011/07/13/provide-feedback-on-the-sql-server-code-name-denali-product-update-feature.aspx

Peter gives the instructions in his blog on how to deploy the test 1515 patch, but you have found there is a problem with that patch for DQS assemblies.

For now, if you rely on DQS, don't try that 11.0.1515 product update until we can further investigate the root cause. Without the 1515 patch, I don't think you will have this problem. If you reomve the 1515 patch, and go back to the plain CTP 3 version 11.0.1440.19 you may get your DQS working until we find a better answer.

If you have deployed the 1515 patch, even DQSInstaller.exe will not run to completion to install DQSInstaller, so there is an assembly mismatch in the GAC that we need to investigate further. This is how I saw the error from my DQSInstaller attempt:

• C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\DQS_install.log:
•       * Creating the internal_core schema
•          - Registering Microsoft.Ssdqs.Infra T-SQL executable objects.
•  Msg 10314, Level 16, State 11, Server SERVERNAME, Line 1
   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:
• 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.

You might get this Error if your DQSInstaller has failed, and you try to Connect with DQ Client:

• Cannot find either column "KnowledgebaseManagement" or the user-defined function or aggregate "KnowledgebaseManagement.SetDataQualitySessionPhaseOne", or the name is ambiguous.

 I think the problem is related to this mismatch in dll version for all Microsoft.Ssdqs files between program files and the .Net frameworks GAC. To show an example, Microsoft.Ssdqs.Core.dll has this pattern in my test:

• C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\Microsoft.Ssdqs.Core.dll = 11.0.1440.19
• C:\Program Files\Microsoft SQL Server\110\Tools\Binn\DQ\Microsoft.Ssdqs.Core.dll = 11.0.1440.19
• C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\DQ\Microsoft.Ssdqs.Core.dll = 11.0.1440.19
• C:\Windows\assembly\GAC_MSIL\Microsoft.Ssdqs.Core\11.0.0.0__89845dcd8080cc91\Microsoft.Ssdqs.Core.dll = 11.0.1515.0

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

I did not knowingly download the 1515 patch, but it seems that somehow the CTP3 installer automatically downloaded this hotfix.  I'm going to try to start over from scratch and see if I can not install the hotfix.  Is there anything in the 1515 patch that I might need unrelated to the "SmartSetup".  Would it be possible for me to register the assemblies manually?  Also, I have the same exact file versions as in your test case.  Did you ever get DQSInstaller to work in your test case?

Answer 8

During the installation, the following automatically happened.  I'm going to try an install without these 2 updates to see what happens.  If I do the install without these updates, will I later be able to add them in once DQSInstaller is run through completely?

Answer 9

Yes - uncheck that "Include SQL Server product updates" and it will give you a working copy of DQS. 

Thanks for clarifying - indeed that screenshot shows the new Smart Setup feature. The smart setup allows you to deploy the latest patch- it will automatically download the patch from Microsoft Update, and include it into the single setup experience (ie. slipstream the CTP3 + KB 2580208 11.0.1515 build). This helps make the DBA job easier, because you can install the latest greatest without having to go through multiple setups.

At present, the 1515 build is just a "test" of smart setup itself, and doesn't have any "fixes" or changes to the product features themselves. In the future, that will change, but for now, its just a test of the patching mechanism itself, so its a bit of a dummy patch.

This thread reveals that the there is an problem in that 1515 build. The problem is that SSIS is patched but DQS and DQ Client is not patched. The team at Microsoft is currently working on fixing that.

Meanwhile, to get DQS installed and working, you can uncheck the checkbox "Include SQL Server product updates" and it will install CTP3 without any extra patches, and will not have those DQS failures.

If you already have a broken installation, there may be a way to uninstall the KB 2580208  patch and get it to work. Let me check on that here.

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 10

After I broke DQS with the 1515 patch in the smart setup, I am able to remove the patch like this and get DQSInstaller working:

 

Control Panel > Uninstall a program - click "View installed updates"

 

Choose the main CTP3 update called "Hotfix 1515 for SQL Server "Denali" CTP3 (KB2580208)". The various other related Hotfix 1515 patches like Policies, CLR types, SQL Browser, VSS Writer, etc will also be removed as part of the same uninstall.

On the "Select Feature" page in the uninstall, I Selected all the features. For example "MSSQLServer" and "Shared Features"

Then ran the uninstall to completion with success.

Afterwards, the patch level is 11.0.1440.

Then I found DQSInstaller via explorer, right click to launch with elevated permissions "Run as Administrator" gave the password, said Yes to overwrite the existing DQS installation. It ran to completion without failure this time.

C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\ DQSInstaller.exe

Please let me know if either approach works for your - unchecking the checkbox "Include SQL Server product updates" for a new CTP3 setup attempt, or using add-remove programs to uninstall the Product Update patch 1515 from an existing CTP3 installation.

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 11

I completely uninstalled Denali CTP3 and then reinstalled and unchecked the checkbox and it seems to be working now.  Thanks for the help, I appreciate it.

Answer 12

Great - glad to know.

Just watch for Microsoft Update alerts if you have it enabled (not common), since it may try to install the same SQL patch again.

We are working on a better resolution, hopefully by next week or sooner, so this is for the short term only.

 

 

Summarizing this issue in case others hit the same thread:

Symptoms

·      DQSInstaller.exe will fail with error when attempting to finish the installation of the DQS catalog it takes the steps to registering assemblies:

[8/15/2011 8:29:14 PM] 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:

[8/15/2011 8:29:14 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.

[8/15/2011 8:29:14 PM] System.IO.FileLoadException:

[8/15/2011 8:29:14 PM]    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

[8/15/2011 8:29:14 PM]    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)

[8/15/2011 8:29:14 PM]    at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

[8/15/2011 8:29:14 PM]    at System.Reflection.Assembly.Load(String assemblyString)

[8/15/2011 8:29:14 PM] ERROR - An error occured, check message above

·         This happens if SQL Server Denali CTP3 Setup is run with default options, and smart -setup has downloaded and applied the test product update KB 2580208 (build 11.0.1515) as part of CTP3 Setup (11.0.1440), or if the patch KB 2580208 is deployed with WSUS after CTP3 is already installed.

·        Other DQS failures with a similar error may occur in DQS if it is already installed, and product update from KB 2580208 / Hotfix 1515 is deployed by Microsoft Update.

Cause

The problem is related to this mismatch for the  dll version for all Microsoft.Ssdqs.* assembly files as compared between program files folders and the .Net frameworks GAC.

To show an example, Microsoft.Ssdqs.Core.dll has this pattern in my test:

• C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\Microsoft.Ssdqs.Core.dll = 11.0.1440.19
• C:\Program Files\Microsoft SQL Server\110\Tools\Binn\DQ\Microsoft.Ssdqs.Core.dll = 11.0.1440.19
• C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\DQ\Microsoft.Ssdqs.Core.dll = 11.0.1440.19

Vs.

• C:\Windows\assembly\GAC_MSIL\Microsoft.Ssdqs.Core\11.0.0.0__89845dcd8080cc91\Microsoft.Ssdqs.Core.dll = 11.0.1515.0

The root cause is that there are 3 msi's that install the Ssdqs assemblies, including SSIS components (sql_is.msi), DQS server (sql_dq.msi) and DQS client (sql_dqc.msi).

However, only the SSIS component file list had updated files in the KB 25802080 download to 11.0.1515.0, and the two DQ msi's are missing in the test patch. Therefore, the CTP3 version 11.0.1440.19 of those two DQ packages are used, causing the mismatch in the assemblies between the GAC and Program Files.

Current Status

This is a known issue under investigation by Microsoft.

If you already have this failure, you will need to uninstall the SmartSetup patch and then re-run DQS installer. After you uninstall the patch, your build should indicate 11.0.1440.19 again.

If you have yet to install DQS this week, avoid the test product update KB 2580208 that has been made available as the default choice until the issue is resolved.

Resolutions

Final resolution TBD – update expected next week 8/22.

Workaround

1.       If you have not yet installed SQL Denali CTP3, are planning to install SQL Server Denali this week, and need to use DQS:  

Uncheck the default checkbox "Include SQL Server product updates" to get a workable copy of DQS. By default this box is checked to help test smart-setup which means the download happens automatically and behind the scenes as CTP3 setup runs.

Uncheck the checkbox highlighted here in Setup… to avoid the product update and the subsequent DQS failures.

2.       If you already are in the broken DQS state where patch 11.0.1515 is already installed, remove the product update from Control Panel > Uninstall programs.

Control Panel > Uninstall a program - click "View installed updates"

Choose the main CTP3 update called "Hotfix 1515 for SQL Server "Denali" CTP3 (KB2580208)". The various other related Hotfix 1515 patches like Policies, CLR types, SQL Browser, VSS Writer, etc. will also be removed as part of the same uninstall.

On the "Select Feature" page in the uninstall, I Selected all the features. For example "MSSQLServer" and "Shared Features"

Then run the update's uninstall to completion with success.

Afterwards, the patch level of all Microsoft.Ssdqs.*  files is 11.0.1440.19

Then try DQSInstaller again. Via explorer, right click to launch with elevated permissions "Run as Administrator", provide a strong new master key password, said Yes to overwrite the existing DQS installation.

Caution – if you have data in the DQS_MAIN and DQS_PROJECTS database already, this command will remove any data you have added.

C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\DQSInstaller.exe

---

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 13

Hi jason,

 

I haven't the Hotfix 1515 on my sql server, but I get same warning on my CTP3  DQSInstaller

---

http://www.rad.pasfu.com

Answer 14

1. Is SSIS installed, if so, check what build. Is it the CTP3 build or a higher build? I have seen problems if SSIS and DQS were mismatched versions, since the GAC copy of assemblies came from SSIS but Program Files copies came from DQS - creating the assemblies as part of DQSInstaller may fails if the files are mismatched.

Do you have SSDQS assemblies in the GAC already - C:\Windows\Assembly

Check the version, that might be problematic if so.

2. Just to confirm - you didn't have DQS installed before by chance? There is no DQS_MAIN already - shouldn't be but just double checking.

If it was installed once and you have DQS_MAIN already, could be this variation but there is a manual approach offered in the release notes section 4.23. See the link if so.

{

If you install a .Net Patch from Windows update, and DQS stops working with this error, to fix it, follow the steps and the script in section 4.23 of this article.

Release notes: http://social.technet.microsoft.com/wiki/contents/articles/3711.aspx see section 4.23

Note this method only works for .Net patches such as patch to system.webthat were made via KB2416472 or other .Net patches.

To see if you have this variation, check in your Control Panel > Add Remove Programs, check the box to show the updates, and it will show "Update for Microsoft .NET Framework 4 Client Profile (KB2473228)" or a similar .Net Framework update.

Normally DQSInstaller.exe can repair the variation of the error , but it will drop any projects you have already started working on, which makes the script in the above URL more desirable for most folks.

}

Thx, 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