none
DQS Installer ( DqsInstaller ) syntax error RRS feed

  • Question

  • I am getting a syntax error when executing DqsInstaller

    i am running sql 2012 cu3

    here is the log file.

    Microsoft (R) DQS Installer Command Line Tool
    Copyright (c) 2012 Microsoft. All rights reserved.

    [10/1/2012 7:38:30 AM] DQS Installer started. Installation log will be written to C:\MSSQL11.MSSQLSERVER\MSSQL\Log\DQS_install.log
       
       
    [10/1/2012 7:38:30 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
    [10/1/2012 7:38:30 AM] Using instance: MSSQLSERVER, catalog: DQS.
    [10/1/2012 7:38:30 AM] Executing action: Validate collation argument.
    [10/1/2012 7:38:30 AM] Action 'Validate collation argument' finished successfully.
    [10/1/2012 7:38:30 AM] Executing action: Check whether system reboot is pending.
    [10/1/2012 7:38:30 AM] Action 'Check whether system reboot is pending' finished successfully.
    [10/1/2012 7:38:30 AM] Executing action: Create data quality event source.
    [10/1/2012 7:38:30 AM] Action 'Create data quality event source' finished successfully.
    [10/1/2012 7:38:30 AM] Executing action: Request Database Master Key password from user..
    [10/1/2012 7:38:48 AM] Action 'Request Database Master Key password from user.' finished successfully.
    [10/1/2012 7:38:48 AM] Executing action: Approve removal of data quality services previous schema.
    [10/1/2012 7:38:48 AM] Action 'Approve removal of data quality services previous schema' finished successfully.
    [10/1/2012 7:38:48 AM] Executing action: Load Installation Scripts.
    [10/1/2012 7:38:48 AM] Extracting script to: C:\Users\user\AppData\Local\Temp\1\x52ds55g.rpp
    [10/1/2012 7:38:49 AM] Extracting script: db\create_core_db_objects.sql
    [10/1/2012 7:38:49 AM] Extracting script: db\create_logic_db_objects.sql
    [10/1/2012 7:38:49 AM] Extracting script: db\create_transient_db_objects.sql
    [10/1/2012 7:38:49 AM] Extracting script: db\static_data.sql
    [10/1/2012 7:38:49 AM] Extracting script: db\drop_dq_databases.sql
    [10/1/2012 7:38:49 AM] Extracting script: db\db_version.sql
    [10/1/2012 7:38:49 AM] Extracting script: helper\DeleteSchemaDs.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\drop_all_assemblies.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\create_databases.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\drop_databases.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\drop_all_tables.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\drop_database_properties.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\master_create.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\master_recreate.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\register_assemblies.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\register_assemblies_tsql.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\register_dq_assemblies.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\create_service_broker_objects.sql
    [10/1/2012 7:38:49 AM] Extracting script: sql\drop_service_broker_objects.sql
    [10/1/2012 7:38:49 AM] Extracting script: db\set_dq_databases_single_user.sql
    [10/1/2012 7:38:49 AM] Extracting script: db\set_dq_databases_multi_user.sql
    [10/1/2012 7:38:49 AM] Extracting script: db\upgrade_all_versions.sql
    [10/1/2012 7:38:49 AM] Extracting script: recreate_schema.bat
    [10/1/2012 7:38:49 AM] Extracting script: upgrade_schema.bat
    [10/1/2012 7:38:49 AM] Extracting script: upgrade_version_tables.bat
    [10/1/2012 7:38:49 AM] Extracting script: drop_databases.cmd
    [10/1/2012 7:38:49 AM] Extracting script: register_dlls.cmd
    [10/1/2012 7:38:49 AM] Extracting script: unregister_dlls.cmd
    [10/1/2012 7:38:49 AM] Extracting script: assembly_paths_retail.txt
    [10/1/2012 7:38:49 AM] Extracting script: DQS_Data.dqs
    [10/1/2012 7:38:49 AM] Extracting script: DefaultKbs.xml
    [10/1/2012 7:38:49 AM] Total scripts extracted: 31
    [10/1/2012 7:38:49 AM] Action 'Load Installation Scripts' finished successfully.
    [10/1/2012 7:38:49 AM] Executing action: Create data quality schema.
    [10/1/2012 7:38:49 AM] Script: 'recreate_schema.bat SomeSqlInstnce DQS SQL_Latin1_General_CP1_CI_AS'
    [10/1/2012 7:38:49 AM] .  Trying to connect using Windows Authentication and db name...
    [10/1/2012 7:38:49 AM] Changed database context to 'master'.
    [10/1/2012 7:38:49 AM] Msg 911, Level 16, State 1, Server SomeSqlInstnce, Line 107
    [10/1/2012 7:38:49 AM] Database 'DQS_MAIN' does not exist. Make sure that the name is entered correctly.
    [10/1/2012 7:38:49 AM] Msg 102, Level 15, State 1, Server SomeSqlInstnce, Line 106
    [10/1/2012 7:38:49 AM] Incorrect syntax near 'Creating'.
    [10/1/2012 7:38:49 AM] ERROR - An error occured, check message above
    [10/1/2012 7:38:49 AM]
    [10/1/2012 7:38:49 AM]
    [10/1/2012 7:38:49 AM] Script process returned unexpected exit code: '1'.
    [10/1/2012 7:38:49 AM] Action 'Create data quality schema' finished with errors, aborting installation.
    [10/1/2012 7:38:49 AM] Starting installation rollback...
    [10/1/2012 7:38:49 AM] Installation rollback completed successfully.
    [10/1/2012 7:38:49 AM] DQS Installer finished with errors. Please see installation log file at C:\MSSQL11.MSSQLSERVER\MSSQL\Log\DQS_install.log


    • Edited by MelColo Monday, October 1, 2012 11:15 PM
    Monday, October 1, 2012 2:33 PM

All replies

  • One thing I always like to try is a different TMP folder:

    md C:\temp
    SET tmp=c:\temp
    cd "c:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLServer\MSSQL\Binn\"

    DQSInstaller.exe

    Another thing is to check the PATH environment variable. I have seen trouble when the path has SQL 80/90/100/150 folders in front of 110 folders in the Path, since it might pick up the wrong version of SQLCMD.exe or something like that.

    SET path

    I haven't seen this one before. The only sort of new thing here is that you are using CU3 to install DQS Fresh. I don't think many people have done that yet, so I don't if this problem is particular to a fresh dqsinatller when on a CU3 build, or just to this server particular environment where something is amiss.

    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

    Thursday, October 11, 2012 6:15 PM
    Moderator
  • Ok,

    I set tmp to C:\Temp

    and Cd'd directly to the binn dir

    which is C:\MSSQL11.MSSQLSERVER\MSSQL\Binn on my workstation

    and i got the same basic set of errors msgs

    As further background i have TFS 2010 installed on my workstation.

    we were also an early tester for sql 2012, and therefore i had various pre-release versions

    of sql installed prior to installing the rtm version. and then followed up with cu3

    the disk was completely cleared of any of the pre-rtm code before installing the rtm version.

    there may have been some stuff left over in the registry.

    You can go ahead an close out the issue, as the company has moved on to a different solution.

    Thanks,

    Mel

    [10/23/2012 3:25:58 PM] Changed database context to 'master'.
    [10/23/2012 3:25:58 PM] Msg 102, Level 15, State 1, Server SomeInstance, Line 10
    6
    [10/23/2012 3:25:58 PM] Incorrect syntax near 'Creating'.
    [10/23/2012 3:25:58 PM] Msg 102, Level 15, State 1, Server SomeInstance, Line 11
    4
    [10/23/2012 3:25:58 PM] Incorrect syntax near 'Creating'.
    [10/23/2012 3:25:58 PM] Msg 102, Level 15, State 1, Server SomeInstance, Line 11
    5
    [10/23/2012 3:25:58 PM] Incorrect syntax near 'Certificate'.
    [10/23/2012 3:25:58 PM] Msg 102, Level 15, State 1, Server SomeInstance, Line 11
    6
    [10/23/2012 3:25:58 PM] Incorrect syntax near ')

    Tuesday, October 23, 2012 9:37 PM
  • This error is pretty outdated, but just in case: I ran into this issue today. Turned out my strong password generator created a password with an apostrophe (') in it. Therefore, the create database script did not run. After generating a new password without ambiguous characters, the installer ran successfully.

    Wednesday, January 30, 2019 10:36 AM