none
DQS Server Installation Failure RRS feed

  • Question

  • Hello,

    DQS Server Installation fails with error (excerpt from DQS_install.log):

    ==========================================================

    [] Script: 'register_dlls.cmd YXZ123 DQS'
    [] .  Trying to connect using Windows Authentication and db name...
    [] 
    []  --> Drop all SSDQS Executable Objects
    [] 
    []  --> Drop all SSDQS Types
    [] 
    []  --> Drop all SSDQS Assemblies
    [] 
    []  --> Drop all SSDQS Schemas
    [] 
    []  --> Drop all CLR Assemblies
    [] 
    []  --> Drop DQ startup stored procedure DQInitDQS_MAIN
    [] Changed database context to 'master'.
    [] 
    []  --> Drop all SSDQS Service Broker Objects
    [] Changed database context to 'DQS_MAIN'.
    [] Dropping Service Broker Services.
    [] Dropping Service Broker Queues.
    [] Dropping Service Broker Contracts.
    [] Dropping Service Broker Messages.
    [] Completed - Service Broker objects dropped.
    [] Changed database context to 'DQS_MAIN'.
    [] 
    []  --> Registering Assemblies
    [] 
    []      * Register .NET dependency assemblies
    [] Msg 6257, Level 16, State 1, Server YXZ123, Line 2
    [] CREATE ASSEMBLY for assembly 'System.Management' failed because the assembly is built for an unsupported version of the Common Language Runtime.
    []
    []
    [] ERROR - An error occured, check message above
    []
    []
    [] Script process returned unexpected exit code: '1'.

    ==================================================

    Additional information:

    Win 7 Pro 64 Bit

    4 GB Ram

    Visual Studio 2010

    Side by Side Installation SQL Server 2008R2 & SQL Server 2012

    Your help is highly appreciated

    Regards

    -ujsr1895

    Thursday, July 12, 2012 7:50 AM

Answers

  • Glad you figured it out. Sorry you had to uninstall/reinstall.

    DQSInstaller uses the instance identifier to try to guess if it is the default instance or named instance, so I see how it makes the mistake in this scenario.

    There is a switch -instance to override the assumed instance name and tell it the right one. For the benefit of others who may have this failure in the future, try this kind of syntax. MSSQLServer is for the default instance of SQL Server 2012, and you can specify just the instance name (not the machine name) for a named instance of SQL Server 2012.

    DQSInstaller.exe -instance MSSQLServer

    DQSInstaller.exe -instance NamedInstanceName

    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

    Monday, July 16, 2012 2:19 PM
    Moderator
  • Hello,

    a quick update on this topic:

    Obviously this issue had something to do with the side-by-side installation. Further investigations have revealed that even though both servers did use different instance names, the instance IDs were the same for any reason (MSSQLSERVER). It seemed that the DQS-installer did connect to the SQL 2008R2 instance during setup. After reinstalling SQL Server 2012 with a different instance id, the DQS installer finished successfully.

    Thanks for your help.

    -ujsr1895

    Monday, July 16, 2012 12:06 PM

All replies

  • Is the instance name that is pointing to your SQL 2012, or your 2008 instance? YXZ123

    By chance did you install .net 4.5 beta on the computer?

    Is the assembly in this folder? C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\

    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

    Sunday, July 15, 2012 3:04 AM
    Moderator
  • Hi Jason,

    thanks for your reply. Here are the answers to your questions:

    (1)

    YXZ123 is the name of the host, where both SQL Server instances have been installed as follows

    -localhost (SQL 2008R2)

    Root: C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER

    Service Name: MSSQLSERVER

    -YXZ123\MSSQLSERVER2012 (SQL 2012)

    Root: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER

    Service Name: MSSQLSERVER2012

    (2)

    .net 4.5 beta is *not* installed on the machine

    (3)

    Yes, System.Management.dll  is in folder:

    C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\

    with version: 4.0.30319.1

    Thanks again for your help.

    Regards

    -ujsr1895

    Monday, July 16, 2012 6:35 AM
  • Hello,

    a quick update on this topic:

    Obviously this issue had something to do with the side-by-side installation. Further investigations have revealed that even though both servers did use different instance names, the instance IDs were the same for any reason (MSSQLSERVER). It seemed that the DQS-installer did connect to the SQL 2008R2 instance during setup. After reinstalling SQL Server 2012 with a different instance id, the DQS installer finished successfully.

    Thanks for your help.

    -ujsr1895

    Monday, July 16, 2012 12:06 PM
  • Glad you figured it out. Sorry you had to uninstall/reinstall.

    DQSInstaller uses the instance identifier to try to guess if it is the default instance or named instance, so I see how it makes the mistake in this scenario.

    There is a switch -instance to override the assumed instance name and tell it the right one. For the benefit of others who may have this failure in the future, try this kind of syntax. MSSQLServer is for the default instance of SQL Server 2012, and you can specify just the instance name (not the machine name) for a named instance of SQL Server 2012.

    DQSInstaller.exe -instance MSSQLServer

    DQSInstaller.exe -instance NamedInstanceName

    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

    Monday, July 16, 2012 2:19 PM
    Moderator