Export to Excel Error in SQL Server 2014 Report Builder/Viewer

Hi,
I am using the 2014 version of ReportViewer in a WinForm to display an RDL report.
The report was originally created in Report Builder 2.0 (SQL 2008 R2), but has since been edited in Report Builder 3.0 (SQL 2014).
The report loads and displays OK, and even exports to Word and PDF. But when exporting to Excel and then opening the Excel document, the following error occurs:
"We found a problem with some content in <filename>. Do you want us to try and recover as much as we can? If you trust the source of this workbook, click Yes."
If you click Yes, then a second message appears:
"Removed Part: /xl/styles.xml part.  (Styles)
Repaired Records: Cell information from /xl/worksheets/sheet1.xml part"
The Excel document then opens, and the data is there, but there is no formatting (no border columns, colours, bolds etc.)
The three interesting things are:
- When exported from SQL 2008 R2 Report Builder 3.0, which exports to .xsl instead of .xslx, it works
- A brand new report created in 2014 Report Builder 3.0 exports to .xslx great
- In Report Builder 2014, I stripped everything back and removed all rows and columns so the original table in the report only has one empty row and column it the export still errors - it is only by removing the original table and creating a brand new table
that export works OK
It appears to be a problem with the tablix, but ideally we don't want to have to recreate our reports from scratch to fix this issue.
Has anyone come across an issue like this before, and know of any potential resolutions to it?
Thank you.

Hello,
Based on your description, you render a report originally created in Report Builder 2.0 (SQL 2008 R2) and export the report to excel with format of Excel 2007-2010.
Edit the report in Report Builder will not upgrader the report. In that case the report still with SSRS 2008 R2 RDL schema. Please try to upgrade the report by open the report in Report Designer in SQL Server Data Tools (SSDT) and then try again.
If you don’t want to upgrade the report, please try to export the report
with Excel 2003 rendering extension and check if the issue persists.
The SQL Server 2014 and SQL Server 2012 Reporting Services Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010 with .xlsx as file extension. Only the Excel rendering extension is available by default.
You must update the Reporting Services configuration files to make the Excel 2003 rendering extension available.
For example, changing the value of Visible to
true in the following line in the RSReportServer.config:
<Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"
Visible="true"/>
Reference:Upgrade Reports
Exporting to Microsoft Excel (Report Builder and SSRS)
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Similar Messages

  • SQL Server 2014 Reporting Services export to Excel

    Hello,
    We recently upgraded to SQL Server 2014 from 2008 R2.
    In SSRS With the new version of SQL Server we are having an issue with the Cell Border Expression logic when exporting to Excel.
    This Cell is a Grouped By Column on the Staff ID
    Here is the expression for the Cell Border
    BorderStyle:
              =IIF(Fields!StaffParttime.Value = "Y", "Solid","None")
    The report renders correctly however when exporting the report the Border is not correct in the spreadsheet.
    Example:  Cell 1 Parttime = "N" there is no border, Cell 2 Parttime = "Y" there is a border, Cell 3 Parttime = "N" there is a border
    Cell 3 should not have a border, also the subsequent sheets all have borders when they should not.  Once the border is set it does not change.
    Has anyone had this same/similar problem and if so what was your resolution?
    Thanks

    Hi Jrod T,
    Based on your description, you are experiencing an issue with the Cell Border Expression logic when exporting the report to Excel, you can’t see the expression added for the Border Style (=IIF(Fields!StaffParttime.Value = "Y", "Solid","None")
    ) work fine in the recently upgraded SQL Server 2014, right?
    I have tested it on my local environment in both the early version and the later version and reproduced the issue in SQL Server 2014.
    The issue due to in the earlier versions of Reporting Services (2005), there was limited support for translating expressions in RDL to Microsoft Excel formulas. But in the newly version, when you export a report to Excel, RDL expressions will not translated
    to Excel formulas, So in the version 2014 the expression will not work.
    Below links of articles are for your reference about more details:
    http://msdn.microsoft.com/en-us/library/ms143380%28v=sql.100%29.aspx
    https://connect.microsoft.com/SQLServer/feedback/details/684666/excel-formulas-not-supported-in-reporting-services-export
    http://msdn.microsoft.com/en-us/library/dd255234.aspx
    Regards
    Vicky Liu

  • MS SQL Server 2014 Report Services Link error

    I have installed SQL Server 2014 with Report builder 3 for 2014 report builder is perfect working, but report services is not working when click on this link "http://microsoft:80/ReportServer" then message is alerted " Reporting
    Services error" The permissions granted to user 'Microsoft\MCSD'
    are insufficient for performing this operation. (rsAccessDenied)and when click on this link "http://microsoft:80/Reports" then message is alerted:
    "User 'Microsoft\MCSD' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed."
    i am using MCSD account as administrator so how resolve this problem?

    Hi Visio,
    I think this issue can be caused by BUILTIN\Administrators might be deleted by someone else. Local Administrators group is equal to BUILTIN\Administrators group on Report Manager. By default, BUILTIN\Administrators user is granted with Content Manger Role.
    When someone delete the BUILTIN\Administrators group in the Folder Settings, Local Administrators group cannot access report manager and report server any more.
    To fix this issue, please use an account which has access to report server to assign some sufficient permissions to the account “Microsoft\MCSD”.
    Another possible is the operating systems limit the overuse of elevated permissions by removing administrator permissions when accessing applications. To fix this issue, please open the Report Manager in Internet Explorer with Run as administrator option.
    References:
    http://technet.microsoft.com/en-us/library/aa337491(v=sql.105).aspx
    http://social.technet.microsoft.com/Forums/exchange/en-US/f095f769-2081-4173-ac16-b806941f0811/uireportmanager01219c08072014161821-e-error?forum=sqlreportingservices
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • MOF Syntax Error Installing SQL Server 2014 Express

    I am trying to install SQL Server 2014 Express With Tools on a fully updated Win 8.1 system having already installed Visual Studio Community 2013 with Update 4. During the installation of SQL Server, I am getting a "MOF Syntax Error".
    I found this http://support.microsoft.com/kb/2387686 on the web but I can't see that that applies to me as I would have thought that any suggested fixes from this article would have been already installed
    or corrected in Win 8.1 or SQL Server 2014. Neither do I know what fix I should install anyway.
    An entry on this forum suggested that running Winmgmt /salvagerepository command fixed the problem. I ran the command in the Command Prompt and a /verifyrepository said it was consistent. However, the error still occurred when I installed SQL Server.
    Can anyone help with this?

    Hi wagham,
    From your description, you encounter the error when installing SQL Server 2014 Express on Windows 8.1. For further analysis, please help to post the summary and detail logs which locate under 
    %ProgramFiles%\Microsoft SQL Server\120\Setup Bootstrap\Log. For more details about viewing SQL Server setup log files, you can refer to this
    article.
    Additionally, based on my research, “MOF Syntax Error” could be caused by various reasons, such as insufficient account permissions, corrupted .NET Framework and so on. There are some proposals for you installing SQL Server 2014 Express as follows.
    1. Make sure that the account you use to install SQL Server has admin rights. If you are using a domain administrator, please ensure that it is added to local administrator group.
    2. Make sure that you right-click the SQL Server setup file (setup.exe) and choose “Run as administrator” to complete the installation.
    3. Check that if the .NET Framework is corrupted on your system. You can verify the installation state of the .NET Framework via the
    .NET Framework Setup Verification Tool. If the .NET Framework is corrupted, please
    repair it using
    .NET Framework Repair Tool, then reinstall SQL Server.
    Here is a similar blog about “MOF Syntax Error” for your reference.
    http://sqlservertimes2.com/?p=641
    Thanks,
    Lydia Zhang

  • System Center Operations Manager 2012 R2 and SQL Server 2014 Reporting Services

    I was able to connect SCOM12 to SQL14, however when I attempted to install Reporting Service in SCOM12 the pull down box was blank.
    I installed reporting services on the same instance of SystemCenter, when that didn't work I tried creating a new instance that only included SSRS; remote registry is also running. The drop-down box within the SCOM installer is blank.
    Is this an issue with reporting between SC12 and SQL14, yes I understand documentation says only sql server 2012 is supported, however I've seen many threads with SCOM12 and SQL12 that are having the same issues.
    Is there something I may be missing, or do I have to install SQL12 and go through the process again?

    Hi,
    As far as I know, the SCOM reporting server role should be installed on the same server where SQL reporting service installed.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Report Builder beyond SQL Server 2014?

    Where can I find details of the Microsoft Roadmap for the future plans for Report Builder?
    Will Report Builder continue to be supported?  Or will it be replaced by other tools?
    Thanks

    Hi Wolley66,
    For the
    document of Documentation for SQL Server 2014 Tools and Add-in Components section, we can know that Report Builder is still supported in SQL Server 2014. If you want to download Microsoft® SQL Server® 2014 Report Builder tool, we can refer to the following
    link:
    http://www.microsoft.com/en-in/download/details.aspx?id=42301
    If you have any concern and requirement about Report Builder in Microsoft Roadmap, please submit a feedback at
    https://connect.microsoft.com/SQLServer/Feedback. Connect site is a connection point between you and Microsoft, and ultimately the larger community. Your feedback enables Microsoft to make software
    and services the best that they can be, and you can learn about and contribute to exciting projects.
    Regards,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Sql server 2005 reports with sql server 2014

    Can i upload SSRS 2005 reports as it is on SSRS 2014 and use it without doing anything extra or without changing anything ??
    I can use SSRS 2005 reports as it is with SSRS 2012. But for SSRS 2014 not sure.
    h2007

    You can upgrade the the RDL schema will be upgraded.
    Report definition (.rdl) files are automatically upgraded in the following ways:
    When you open a report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008 or SQL Server 2008 R2 report server in the project properties, the report
    definition is saved in a schema that is compatible with the target server.
    When you upgrade a Reporting Services installation to a SQL Server 2014 Reporting Services (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first
    time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.
    Reports are not upgraded when you upload a report definition file directly to the report server or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
    After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying
    problems in the report are detected. For more information, see Reporting Services Backward Compatibility.
    For more information about new features for SQL Server 2014 Reporting Services (SSRS), see
    What's New (Reporting Services).
    Check the below Microsoft link for more information
    http://msdn.microsoft.com/en-us/library/ms143674.aspx
    Mudassar

  • Moving sql server 2000 to sql server 2014

    Moving sql server 2000 to sql server 2014. Could someone please give me steps to move everything from sql 2000 one server to sql 2014. I have 2 instance on sql 2000. 8 databases on each of them. On both instances we have store procedure and jobs.

    i think your SQL Server 2000 is hosted on old Windows server version so based on that you should prepare new environment for SQL Server 2014 from Win Server 2012 Sp1 and SQL Server 2014 and build your clusters then start your Migration from Old Servers to
    new servers and here below is 10 configurations outlines that you should look after carefully for any DB consolidation or migration from a server to  a server and indeed they represent unique potentials for your DB Consolidation /migration service that
    can leverage distinctly your service quality and shape you very well in front of your customers:
    1-      Backup DBs and restore DBs with ZERO down time and ZERO data loss in the same time …Awesome …!
    2-      Cloning all DB special features that are not covered by backups and restores such as :
    RCSI (Read committed snapshot isolation level using row versioning)
    Service brokers
    Encryption keys and certificates
    3-      Cloning identically all SQL logins with their mapped DB users including their passwords (if SQL authenticated logins ) and privileges on both server and DB levels .
    4-      Copying .rdl and .rds files between different versions of reporting services where backup and restore reportserver and reportservertemp DBs is not an option
    5-      Cloning all special Jobs like certain business jobs configured to perform some business stuff .
    6-      Cloning all mail profiles with their mail accounts
    7-      Cloning all Linked server + Aliases might be used inside old DB servers
    8-      Cloning some server configurations like CLR ,CPU parallelism, Replication size , Network packet size , optimize for ad hoc workloads
    9-      Cloning all Replications configurations for publishers and subscribers
    10-   Cloning all DTC configurations for both local and clustered DTC services
    Follow the below links to know the steps by the scripts:
    http://sqlserver-performance-tuning.net/?p=5262
    http://sqlserver-performance-tuning.net/?p=5359
    http://sqlserver-performance-tuning.net/?p=5398
    http://sqlserver-performance-tuning.net/?p=5415
    http://sqlserver-performance-tuning.net/?p=5458
    Mustafa EL-Masry
    Principle Database Administrator & DB Analyst
    SQL Server MCTS-MCITP
    M| +966 54 399 0968
    MostafaElmasry.Wordpress.com

  • SQL Server 2000 Reporting withJava

    Hi All,
    Can any one give the code to open SQL Server 2000 Reporting file (i.e, with the extension '.rdl') as we do for the crystal reports '.rpt' file in jsp.
    Is there any eclipse plugin for SQL Server 2000 Reporting service.
    thanks in advance.

    For versions above than SQL 2000, you can refer to sql reporting services configuration tool.
    For SQL server 2000, reporting services view the database deatils as mentioned in below thread
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/e4263367-600d-4bb1-94e7-6b66e5df295d/how-do-i-find-configuration-details-on-sql-server-2000-ssrs?forum=sqlreportingservices
    To find the SQL Server name that host the report server database, please check the server name of the “ReportServerURL” in the RSWebApplication configuration file. The configuration file is located in the following folder:
    <drive>:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager
    By default, the report server database name is ReportServerDB, and the report server temporary database name is ReportServerTempDB. To check the report server database name the SSRS 2000 uses currently, we can try to join a report server
    instance to a Web farm by using different database. If the target database is not validated during the setup, it cannot be the report server database. Besides, we can also expand the tables of the databases; a report server database has different tables with
    common databases.
    For more information, please see:
    RSWebApplication Configuration File
    Installing a Report Server Web Farm
    Please click the Mark as answer button and vote as helpful if this reply solves your problem

  • SQL SERVER 2000 - REPORTING SERVICES DATABASE ?

    Hi!
    A very basic question, how to know where reporting services points to the database and server ?
    miga

    For versions above than SQL 2000, you can refer to sql reporting services configuration tool.
    For SQL server 2000, reporting services view the database deatils as mentioned in below thread
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/e4263367-600d-4bb1-94e7-6b66e5df295d/how-do-i-find-configuration-details-on-sql-server-2000-ssrs?forum=sqlreportingservices
    To find the SQL Server name that host the report server database, please check the server name of the “ReportServerURL” in the RSWebApplication configuration file. The configuration file is located in the following folder:
    <drive>:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager
    By default, the report server database name is ReportServerDB, and the report server temporary database name is ReportServerTempDB. To check the report server database name the SSRS 2000 uses currently, we can try to join a report server
    instance to a Web farm by using different database. If the target database is not validated during the setup, it cannot be the report server database. Besides, we can also expand the tables of the databases; a report server database has different tables with
    common databases.
    For more information, please see:
    RSWebApplication Configuration File
    Installing a Report Server Web Farm
    Please click the Mark as answer button and vote as helpful if this reply solves your problem

  • Power Pivot Configuration error while refreshing connection on excel sheet for SharePoint 2013 and Sql server 2014 using BISM file connection

    I am getting following error while refreshing connection on excel sheet in power pivot gallery,
    my scenario,
    using BISM file connection to create and  refresh power pivot excel sheet in power pivot gallery
    throws error and we have sql server 2014 CU6 updated installed plus sharepoint 2013. i checked following msolap110.dll is available in our environment but assembly
    Microsoft.AnalysisServices.ChannelTransport is not available. 
    i found error in event viewer,
    "Activation context generation failed for "C:\Program Files\Microsoft Analysis
    Services\AS OLEDB\110\msolap110.dll". Dependent Assembly
    Microsoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
    not be found. Please use sxstrace.exe for detailed diagnosis.
    what should i do to fix it?
    Thanks for help.
    Deepak Patel

    Rebecca,
    yes, this is issue i am getting.
    Activation
    context generation failed for "C:\Program
    Files\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll".
    Dependent AssemblyMicrosoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
    not be found. Please use sxstrace.exe for detailed diagnosis.
    let me know if you can find fix for it.
    THanks,

  • Fatal error while executing the DQS installer on SQL Server 2014

    Hi all.
    I am receiving the following error when attempting to install DQS on the following platform:
    Windows Server 2012
    Microsoft SQL Server 2014 - 12.0.2000.8 (X64)   Feb 20 2014 20:04:26   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    (no entries in event viewer)
    Error is:
    [4/15/2015 8:45:04 AM] Fatal error while executing the DQS installer.
    Microsoft.Ssdqs.Proxy.ImportExport.ImportExportException: Error occurred in a server proxy call during the import/export process. ---> Microsoft.Ssdqs.Proxy.ImportExport.ImportProcessFailedException: System.NullReferenceException: Object reference not set
    to an instance of an object.
       at System.Security.Cryptography.CryptoStream..ctor(Stream stream, ICryptoTransform transform, CryptoStreamMode mode)
       at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportReader..ctor(Stream stream)
       at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportManager.Import(Stream input)
       at Microsoft.Ssdqs.ImportExportManagement.Calibrator.ImportKnowledgebaseCalibrator.Calibrate(IMasterContext masterContext, CalibrationMode calibrationMode, ConfigurationDomParameter calibratorConfiguration)
       at Microsoft.Ssdqs.Core.Service.Calibration.Impl.ExecuteCalibratorFlow.Process(IMasterContext context)
       --- End of inner exception stack trace ---
       at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.WaitUntillProcessCompletes(Int64 processId, Int64 knowledgebaseId, ImportExportCancellationToken cancelToken)
       at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.KnowledgebaseImport(String kbName, String kbDescription, String fileName, ImportExportCancellationToken cancelToken)
       at Microsoft.Ssdqs.DqsInstaller.Logic.Actions.LoadOutOfTheBoxDataAction.Execute()
       at Microsoft.Ssdqs.DqsInstaller.Logic.ActionExecuter.ExecuteAllActions()
       at Microsoft.Ssdqs.DqsInstaller.Logic.Installer.Main(String[] args)
    Thanks for any advice you can give.
    Full log below:
    Microsoft (R) DQS Installer Command Line Tool
    Copyright (c) 2014 Microsoft. All rights reserved.
    [4/15/2015 7:58:20 AM] DQS Installer started. Installation log will be written to C:\Program Files\Microsoft SQL Server\MSSQL12.DW01\MSSQL\Log\DQS_install.log
    [4/15/2015 7:58:20 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
    [4/15/2015 7:58:20 AM] Using instance: DW01, catalog: DQS.
    [4/15/2015 7:58:20 AM] Executing action: Validate collation argument.
    [4/15/2015 7:58:20 AM] Action 'Validate collation argument' finished successfully.
    [4/15/2015 7:58:20 AM] Executing action: Check whether system reboot is pending.
    [4/15/2015 7:58:20 AM] Action 'Check whether system reboot is pending' finished successfully.
    [4/15/2015 7:58:20 AM] Executing action: Create data quality event source.
    [4/15/2015 7:58:20 AM] Action 'Create data quality event source' finished successfully.
    [4/15/2015 7:58:20 AM] Executing action: Request Database Master Key password from user..
    Microsoft (R) DQS Installer Command Line Tool
    Copyright (c) 2014 Microsoft. All rights reserved.
    [4/15/2015 8:39:59 AM] DQS Installer started. Installation log will be written to C:\Program Files\Microsoft SQL Server\MSSQL12.DW01\MSSQL\Log\DQS_install.log
    [4/15/2015 8:39:59 AM] Parsing DqsInstaller command line arguments.
    [4/15/2015 8:39:59 AM] Setting the catalog to default value: DQS
    [4/15/2015 8:39:59 AM] Setting the collation to default value: SQL_Latin1_General_CP1_CI_AS
    [4/15/2015 8:39:59 AM] Using instance: DEV01, catalog: DQS.
    [4/15/2015 8:39:59 AM] Executing action: Validate collation argument.
    [4/15/2015 8:39:59 AM] Action 'Validate collation argument' finished successfully.
    [4/15/2015 8:39:59 AM] Executing action: Check whether system reboot is pending.
    [4/15/2015 8:39:59 AM] Action 'Check whether system reboot is pending' finished successfully.
    [4/15/2015 8:39:59 AM] Executing action: Create data quality event source.
    [4/15/2015 8:39:59 AM] Action 'Create data quality event source' finished successfully.
    [4/15/2015 8:39:59 AM] Executing action: Request Database Master Key password from user..
    [4/15/2015 8:41:05 AM] Action 'Request Database Master Key password from user.' finished successfully.
    [4/15/2015 8:41:05 AM] Executing action: Approve removal of data quality services previous schema.
    [4/15/2015 8:41:05 AM] Action 'Approve removal of data quality services previous schema' finished successfully.
    [4/15/2015 8:41:05 AM] Executing action: Load Installation Scripts.
    [4/15/2015 8:41:05 AM] Extracting script to: C:\Users\SqlServiceAcct\AppData\Local\Temp\3mo2vwbu.xch
    [4/15/2015 8:41:06 AM] Extracting script: db\create_core_db_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\create_logic_db_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\create_transient_db_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\static_data.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\drop_dq_databases.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\db_version.sql
    [4/15/2015 8:41:06 AM] Extracting script: helper\DeleteSchemaDs.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_all_assemblies.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\create_databases.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_databases.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_all_tables.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_database_properties.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\master_create.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\master_recreate.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\register_assemblies.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\register_assemblies_tsql.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\register_dq_assemblies.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\create_service_broker_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: sql\drop_service_broker_objects.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\set_dq_databases_single_user.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\set_dq_databases_multi_user.sql
    [4/15/2015 8:41:06 AM] Extracting script: db\upgrade_all_versions.sql
    [4/15/2015 8:41:06 AM] Extracting script: recreate_schema.bat
    [4/15/2015 8:41:06 AM] Extracting script: upgrade_schema.bat
    [4/15/2015 8:41:06 AM] Extracting script: upgrade_version_tables.bat
    [4/15/2015 8:41:06 AM] Extracting script: drop_databases.cmd
    [4/15/2015 8:41:06 AM] Extracting script: register_dlls.cmd
    [4/15/2015 8:41:06 AM] Extracting script: unregister_dlls.cmd
    [4/15/2015 8:41:06 AM] Extracting script: assembly_paths_retail.txt
    [4/15/2015 8:41:06 AM] Extracting script: DQS_Data.dqs
    [4/15/2015 8:41:06 AM] Extracting script: DefaultKbs.xml
    [4/15/2015 8:41:06 AM] Total scripts extracted: 31
    [4/15/2015 8:41:06 AM] Action 'Load Installation Scripts' finished successfully.
    [4/15/2015 8:41:06 AM] Executing action: Create data quality schema.
    [4/15/2015 8:41:06 AM] Script: 'recreate_schema.bat CMTSQLSVR04\DEV01 DQS SQL_Latin1_General_CP1_CI_AS'
    [4/15/2015 8:41:06 AM] .  Trying to connect using Windows Authentication and db name...
    [4/15/2015 8:41:06 AM] Run create_databases.sql to create Data Quality Service databases if they do not exist.
    [4/15/2015 8:41:07 AM] 
    [4/15/2015 8:41:07 AM]  --> Running File: create_databases.sql
    [4/15/2015 8:41:07 AM] ---[ Creating databases ]---
    [4/15/2015 8:41:07 AM] Changed database context to 'master'.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_dq_database.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping Data Quality Databases ]---
    [4/15/2015 8:41:10 AM] Creating DQS databases (DQS_MAIN, DQS_PROJECTS, DQS_STAGING_DATA)...
    [4/15/2015 8:41:10 AM] Configuring DQS databases
    [4/15/2015 8:41:10 AM] Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.
    [4/15/2015 8:41:10 AM] Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    [4/15/2015 8:41:10 AM] Configuration option 'xp_cmdshell' changed from 0 to 1. Run the RECONFIGURE statement to install.
    [4/15/2015 8:41:10 AM] Creating Master Key for database DQS_MAIN...
    [4/15/2015 8:41:10 AM] Creating Module Signing Certificate for database DQS_MAIN...
    [4/15/2015 8:41:10 AM] Exporting Certificate from DQS_MAIN
    [4/15/2015 8:41:10 AM] Importing Certificate into DQS_PROJECTS
    [4/15/2015 8:41:10 AM] Configuration option 'xp_cmdshell' changed from 1 to 0. Run the RECONFIGURE statement to install.
    [4/15/2015 8:41:10 AM] Creating DQS roles
    [4/15/2015 8:41:10 AM] Run master_recreate.sql to recreate Data Quality Service Main and Projects Databases and drop all tables including known temporary tables.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running master_recreate.sql
    [4/15/2015 8:41:10 AM] ---[ Recreate DQS Main and Projects Databases ]---
    [4/15/2015 8:41:10 AM] Changed database context to 'DQS_STAGING_DATA'.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_database_properties.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping Database Properties]---
    [4/15/2015 8:41:10 AM] Changed database context to 'DQS_PROJECTS'.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_all_tables.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping all SSDQS Database objects and KB schemas ]---
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all Symmetric Keys ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all Certificates ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all FK constraints ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all views ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all tables and synonyms ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all database triggers ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all stored procedures in Knowledge Base schemas ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all types in Knowledge Base schemas ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --[ Drop all Knowledge Base schemas ]
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_database_properties.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping Database Properties]---
    [4/15/2015 8:41:10 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:10 AM] 
    [4/15/2015 8:41:10 AM]  --> Running File: drop_all_tables.sql
    [4/15/2015 8:41:10 AM] ---[ Dropping all SSDQS Database objects and KB schemas ]---
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all Symmetric Keys ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all Certificates ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all FK constraints ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all views ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all tables and synonyms ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all database triggers ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all stored procedures in Knowledge Base schemas ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all types in Knowledge Base schemas ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --[ Drop all Knowledge Base schemas ]
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running File: drop_database_properties.sql
    [4/15/2015 8:41:11 AM] ---[ Dropping Database Properties]---
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running master_create.sql
    [4/15/2015 8:41:11 AM] ---[ Creating and Populating Main DQS DB ]---
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_STAGING_DATA'.
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running File: create_core_db_objects.sql
    [4/15/2015 8:41:11 AM] ---[  Creating Certificates  ]---
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM] ---[  Creating Symmetric Keys  ]---
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM] ---[  Creating Tables  ]---
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEST   
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEST2   
    [4/15/2015 8:41:11 AM] Creating Table:     A_FLOW   
    [4/15/2015 8:41:11 AM] Creating Table:     A_FLOW_ANSWER   
    [4/15/2015 8:41:11 AM] Creating Table:     A_EXECUTION_UNIT
    [4/15/2015 8:41:11 AM] Creating Table:     A_CODE_GROUP   
    [4/15/2015 8:41:11 AM] Creating Table:     A_CODE_MEMBER   
    [4/15/2015 8:41:11 AM] Creating Table:     A_CONFIGURATION   
    [4/15/2015 8:41:11 AM] Creating Table:     A_PROCESS   
    [4/15/2015 8:41:11 AM] Creating Table:     A_SERVICE_BROKER_TASK   
    [4/15/2015 8:41:11 AM] Creating Table:     A_KNOWLEDGEBASE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_KNOWLEDGEBASE_AUDIT   
    [4/15/2015 8:41:11 AM] Creating Table:     A_KNOWLEDGEBASE_ACTIVITY   
    [4/15/2015 8:41:11 AM] Creating Table:     A_PROFILING_ACTIVITY_ARCHIVE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_CLIENT_SESSION   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_PROVIDER   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_PROVIDER_SCHEMA   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_CACHE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_CACHE_SUGGESTION   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_CACHE_SUGGESTION_PARSED   
    [4/15/2015 8:41:11 AM] Creating Table:     A_REFERENCE_DATA_AUDIT   
    [4/15/2015 8:41:11 AM] Creating Table:     A_IMPORTED_PROJECT   
    [4/15/2015 8:41:11 AM] Creating Table:     A_SPELLER_DICTIONARY_VALUE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_SPECIAL_CHARACTER_RULE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_PERSISTENT_CACHE   
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEMPLATE_OBJECTS   
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEMPLATE_FOREIGN_KEYS   
    [4/15/2015 8:41:11 AM] Creating Table:     A_TEMPLATE_COLUMNS   
    [4/15/2015 8:41:11 AM] ---[ Creating Views ]---
    [4/15/2015 8:41:11 AM] Creating View:      V_A_FLOW
    [4/15/2015 8:41:11 AM] Creating View:      V_A_KNOWLEDGEBASE
    [4/15/2015 8:41:11 AM] Creating View:      V_A_KNOWLEDGEBASE_AUDIT
    [4/15/2015 8:41:11 AM] Creating View:     V_A_REFERENCE_DATA_PROVIDER   
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running File: static_data.sql
    [4/15/2015 8:41:11 AM] ---[ Inserting Data ]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Cleansing configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Logging settings section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Logging settings section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Association configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert DataValueService configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Association rules configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert IndexService configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Knowledgebase configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Notification configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert Interactive Cleansing configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Reference Data configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert client paging configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Insert client process sampling configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Matching configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Profiling configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Process configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[FileStorageManager configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[ImportExportManager configuration section]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Reference Data Add provider]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Reference Data Add provider schema]---
    [4/15/2015 8:41:11 AM] ---[Add Special characters for term normalization]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] 
    [4/15/2015 8:41:11 AM]  --> Running File: db_version.sql
    [4/15/2015 8:41:11 AM] ---[ Running version related work ]---
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION_INFO   
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION   
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION_UPGRADE_SCRIPTS   
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION_UPGADE_SCRIPT_PATH   
    [4/15/2015 8:41:11 AM] Creating view:     V_DB_VERSION 
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM] ---[Add DB Version information]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (0 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts path]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] ---[Add DB Version upgrade scripts path]---
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] (1 rows affected)
    [4/15/2015 8:41:11 AM] Changed database context to 'DQS_PROJECTS'.
    [4/15/2015 8:41:11 AM] Creating Table:     A_DB_VERSION in PROJECTS database 
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM]
    [4/15/2015 8:41:11 AM] Action 'Create data quality schema' finished successfully.
    [4/15/2015 8:41:11 AM] Executing action: Register data quality assemblies and stored procedures.
    [4/15/2015 8:41:11 AM] Script: 'register_dlls.cmd CMTSQLSVR04\DEV01 DQS'
    [4/15/2015 8:41:12 AM] .  Trying to connect using Windows Authentication and db name...
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Running File: drop_all_assemblies.sql
    [4/15/2015 8:41:12 AM] ---[ Dropping all SSDQS Executable Objects ]---
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop all SSDQS Types
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop all SSDQS Assemblies
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop all SSDQS Schemas
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop all CLR Assemblies
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Drop DQ startup stored procedure DQInitDQS_MAIN
    [4/15/2015 8:41:12 AM] Changed database context to 'master'.
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Running File: drop_service_broker_objects.sql
    [4/15/2015 8:41:12 AM] ---[ Dropping all SSDQS Service Broker Objects ]---
    [4/15/2015 8:41:12 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:12 AM] Dropping Service Broker Services.
    [4/15/2015 8:41:12 AM] Dropping Service Broker Queues.
    [4/15/2015 8:41:12 AM] Dropping Service Broker Contracts.
    [4/15/2015 8:41:12 AM] Dropping Service Broker Messages.
    [4/15/2015 8:41:12 AM] Completed - Service Broker objects dropped.
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Running register_assemblies.sql
    [4/15/2015 8:41:12 AM] ---[ Registering Assemblies ]---
    [4/15/2015 8:41:12 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]  --> Registering Assemblies
    [4/15/2015 8:41:12 AM]      The following Warnings are benign to DQSInstaller and may be ignored.
    [4/15/2015 8:41:12 AM] 
    [4/15/2015 8:41:12 AM]      * Register .NET dependency assemblies
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.management, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.configuration.install, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'smdiagnostics, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.windows.forms, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.drawing, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'accessibility, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.serialization.formatters.soap, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the
    SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:25 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.jscript, version=10.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:26 AM] Warning: The Microsoft .NET Framework assembly 'system.management.instrumentation, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
    hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:27 AM] Warning: The Microsoft .NET Framework assembly 'system.messaging, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:27 AM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.enterpriseservices, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.remoting, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.web, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=amd64.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.framework, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.xaml, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.runtime.caching, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.utilities.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
    hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.directoryservices.protocols, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server
    hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.design, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.drawing.design, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.web.regularexpressions, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.build.tasks.v4.0, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted
    environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM] Warning: The Microsoft .NET Framework assembly 'system.serviceprocess, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:44 AM]      * Register Microsoft.Practices assemblies
    [4/15/2015 8:41:47 AM] Warning: The Microsoft .NET Framework assembly 'microsoft.csharp, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:47 AM] Warning: The Microsoft .NET Framework assembly 'system.dynamic, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment
    and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
    [4/15/2015 8:41:47 AM] 
    [4/15/2015 8:41:47 AM]      The preceding Warnings are benign to DQSInstaller and may be ignored.
    [4/15/2015 8:41:48 AM] 
    [4/15/2015 8:41:48 AM]  --> Running register_dq_assemblies.sql
    [4/15/2015 8:41:48 AM] ---[  Registering Data Quality assemblies ]---
    [4/15/2015 8:41:49 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.infra, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:50 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.core, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:51 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.dataservice, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:51 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.referencedata, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:52 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.index, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:52 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.associationrules, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:53 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.datavalueservice, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:54 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.domainrules, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:54 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.cleansing, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:55 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.association, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:55 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.flow, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:56 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs.matching, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:57 AM] Warning: The SQL Server client assembly 'microsoft.ssdqs, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.
    [4/15/2015 8:41:57 AM] Resource file was not copied
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]  --> Running register_assemblies_tsql.sql
    [4/15/2015 8:41:57 AM] ---[ Registering Assemblies for TSQL]---
    [4/15/2015 8:41:57 AM] Changed database context to 'master'.
    [4/15/2015 8:41:57 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]      * Clear the Code Member Table A_CODE_MEMBER.
    [4/15/2015 8:41:57 AM]
    [4/15/2015 8:41:57 AM] (0 rows affected)
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]      * Clear the Code Group Table A_CODE_GROUP.
    [4/15/2015 8:41:57 AM]
    [4/15/2015 8:41:57 AM] (0 rows affected)
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]      * Register assemblies T-SQL executable objects
    [4/15/2015 8:41:57 AM]         - Creating assemblies T-SQL registeration stored procedure.
    [4/15/2015 8:41:57 AM] 
    [4/15/2015 8:41:57 AM]      * Creating the internal_core schema
    [4/15/2015 8:41:57 AM]         - Registering Microsoft.Ssdqs.Infra T-SQL executable objects.
    [4/15/2015 8:42:05 AM]         - Registering Microsoft.Ssdqs.Core T-SQL executable objects.
    [4/15/2015 8:42:11 AM]         - Registering Microsoft.Ssdqs.DataService T-SQL executable objects.
    [4/15/2015 8:42:16 AM]         - Registering Microsoft.Ssdqs.ReferenceData T-SQL executable objects.
    [4/15/2015 8:42:21 AM]         - Registering Microsoft.Ssdqs.Index T-SQL executable objects.
    [4/15/2015 8:42:26 AM]         - Registering Microsoft.Ssdqs.Cleansing T-SQL executable objects.
    [4/15/2015 8:42:32 AM]         - Registering Microsoft.Ssdqs.Association T-SQL executable objects.
    [4/15/2015 8:42:37 AM]         - Registering Microsoft.Ssdqs.Flow T-SQL executable objects.
    [4/15/2015 8:42:42 AM]         - Registering Microsoft.Ssdqs T-SQL executable objects.
    [4/15/2015 8:42:51 AM]         - Registering Microsoft.Ssdqs.DataValueService T-SQL executable objects.
    [4/15/2015 8:42:56 AM]         - Registering Microsoft.Ssdqs.DomainRules T-SQL executable objects.
    [4/15/2015 8:43:01 AM]         - Registering Microsoft.Ssdqs.AssociationRules T-SQL executable objects.
    [4/15/2015 8:43:06 AM]         - Registering Microsoft.Ssdqs.Matching T-SQL executable objects.
    [4/15/2015 8:43:12 AM]         - Creating refresh assemblies stored procedure.
    [4/15/2015 8:43:12 AM] Changed database context to 'master'.
    [4/15/2015 8:43:12 AM]         - Creating refresh assemblies helper linked server.
    [4/15/2015 8:43:12 AM]         - Creating and registering [dbo].[DQInitDQS_MAIN] (calls internal_core.InitServer) as startup stored procedure.
    [4/15/2015 8:43:12 AM] 
    [4/15/2015 8:43:12 AM]  --> Running File: create_service_broker_objects.sql
    [4/15/2015 8:43:12 AM] ---[ Registering Service Broker Objects ]---
    [4/15/2015 8:43:12 AM] Changed database context to 'DQS_MAIN'.
    [4/15/2015 8:43:12 AM]         - Creating SB dispatcher stored procedure, messages and contract
    [4/15/2015 8:43:13 AM]         - Creating parallel execution SB queues and services
    [4/15/2015 8:43:13 AM]         - Creating calibration SB queues and services
    [4/15/2015 8:43:13 AM]         - Creating parallel calibration SB queues and services
    [4/15/2015 8:43:13 AM]
    [4/15/2015 8:43:13 AM]
    [4/15/2015 8:43:13 AM] Successfully registered all assemblies.
    [4/15/2015 8:43:13 AM]
    [4/15/2015 8:43:13 AM]
    [4/15/2015 8:43:13 AM] Action 'Register data quality assemblies and stored procedures' finished successfully.
    [4/15/2015 8:43:13 AM] Executing action: Set product version property.
    [4/15/2015 8:43:13 AM] Action 'Set product version property' finished successfully.
    [4/15/2015 8:43:13 AM] Executing action: Create MDS user (if MDS login exists).
    [4/15/2015 8:43:13 AM] Action 'Create MDS user (if MDS login exists)' finished successfully.
    [4/15/2015 8:43:13 AM] Executing action: Load out of the box data.
    [4/15/2015 8:43:22 AM] Started loading knowledgebase 'DQS Data'
    [4/15/2015 8:45:04 AM] Starting installation rollback...
    [4/15/2015 8:45:04 AM] Installation rollback completed successfully.
    [4/15/2015 8:45:04 AM] Fatal error while executing the DQS installer.
    Microsoft.Ssdqs.Proxy.ImportExport.ImportExportException: Error occurred in a server proxy call during the import/export process. ---> Microsoft.Ssdqs.Proxy.ImportExport.ImportProcessFailedException: System.NullReferenceException: Object reference not set
    to an instance of an object.
       at System.Security.Cryptography.CryptoStream..ctor(Stream stream, ICryptoTransform transform, CryptoStreamMode mode)
       at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportReader..ctor(Stream stream)
       at Microsoft.Ssdqs.ImportExportManagement.ImportExport.ImportExportManager.Import(Stream input)
       at Microsoft.Ssdqs.ImportExportManagement.Calibrator.ImportKnowledgebaseCalibrator.Calibrate(IMasterContext masterContext, CalibrationMode calibrationMode, ConfigurationDomParameter calibratorConfiguration)
       at Microsoft.Ssdqs.Core.Service.Calibration.Impl.ExecuteCalibratorFlow.Process(IMasterContext context)
       --- End of inner exception stack trace ---
       at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.WaitUntillProcessCompletes(Int64 processId, Int64 knowledgebaseId, ImportExportCancellationToken cancelToken)
       at Microsoft.Ssdqs.Proxy.ImportExport.ImportAsProcessManager.KnowledgebaseImport(String kbName, String kbDescription, String fileName, ImportExportCancellationToken cancelToken)
       at Microsoft.Ssdqs.DqsInstaller.Logic.Actions.LoadOutOfTheBoxDataAction.Execute()
       at Microsoft.Ssdqs.DqsInstaller.Logic.ActionExecuter.ExecuteAllActions()
       at Microsoft.Ssdqs.DqsInstaller.Logic.Installer.Main(String[] args)
    Microsoft (R) DQS Installer Command Line Tool
    Copyright (c) 2014 Microsoft. All rights reserved.

    Thank you for the quick response.
    Unfortunately running cmd as admin had no effect on the result. Same exact error.
    After the rollback indicated in the log above, only the DQS_STAGING_DATA database remains in the sql server instance.

  • Beginner installing SQL Server 2014 for Excel Data Mining

    Hello, I'm a complete beginner with servers but Im desperately trying to gain access to the SQL server for use with the data mining addin for excel.
    Could someone please help. When I try to make a connection in Excel by choosing DATA MINING> <No Connection> New> it then asks me for a Server Name in the connect to Analysis Services box. How can I find out what my Sever name is please? I have
    tried all sorts of names that I have found such as SQLEXPRESS or localhost but nothing works. It also tells me to 'Ensure that the Server is running'. Another error message I receive: No connection can be
    made because 'the target machine actively refused it'.
    I would be really grateful for some troubleshooting tips.
    Thank you

    Hi Alberto,
    Thanks very much for getting back to me.
    Here are the results of the Analysis Services report:
    Microsoft SQL Server 2014 Setup Discovery Report
    Product
    Instance
    Instance ID
    Feature
    Language
    Edition
    Version
    Clustered
    Configured
    Microsoft SQL Server 2014
    SQLEXPRESS
    MSSQL12.SQLEXPRESS
    Database Engine Services
    1033
    Express Edition
    12.0.2000.8
    No
    Yes
    Microsoft SQL Server 2014
    SQLEXPRESS
    MSSQL12.SQLEXPRESS
    SQL Server Replication
    1033
    Express Edition
    12.0.2000.8
    No
    Yes
    I then ran the System Configuration Checker and these are the results:
    Passed: 9. Failed: 1.
    Edition WOW 64 Platform    Failed
    (I can't paste the images as my account has not been verified)
    Should I assume that I have installed the wrong version? I am running 64 Bit Windows 8.
    I just need the most basic version for personal data analysis in Excel with the Data Mining Add-in. 
    Thanks again

  • Script to export data frmo SQL Server 2014 to xls file

    Hi All:
    I want to export data form a table in SQl Server 2014 to an xls file.
    Currently I have a working script for SQL Server 2005 in the below lines, but the same script doesnot work for SQL Server 2014.
    set @outFileName='D:\Folder1\File1.xls'
    SET @QueryString = 'INSERT INTO OPENROWSET( ''Microsoft.Jet.OLEDB.4.0'', ' + @outFileName +                             
     ',''select * ' + 'from [Sheet1$A1:IV65000]'') select * from Table1 ' --order by CreatedDate'                             
    EXEC ( @QueryString )                  .
    I have checked on the web but didnot get a good answer. Please share with me if any one has a working script for SQL Server 2014.
    Thanks... Happy Diwali.. :)

    Ok, I have downloaded the exe from the above link.
    As I have to install this on a production environment, I want to be sure of certain things ...
    Say I have installed the Provider, what would be the syntax for exporting the data from sql server 2014 to xls.
    It would certainly not be the same ... i feel.. please let me know.
    Thanks
    Yes
    provider connection string would be different
    like
    INSERT INTO OPENROWSET("Microsoft.ACE.OLEDB.12.0", "Excel 12.0;Database=<full file name>.xlsx;HDR=YES", "SELECT * FROM [SheetName$]")
    SELECT ..
    FROM table
    Please Mark This As Answer if it solved your issue
    Please Mark This As Helpful if it helps to solve your issue
    Visakh
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Error message when installing SQL Server 2014 Express

    When installing SQL Server 2014 Express,
    I get the error shown below.
    Why do I get this and how to correct for it?
    TITLE: Microsoft SQL Server 2014 Setup
    The following error has occurred:
    An error occurred during the installation of assembly 'Microsoft.VC80.MFC,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more
    information. HRESULT: 0x80070422. 
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xDF039760%25401201%25401
    BUTTONS:
    OK
    Thanks

    Hi,
    here is the log file:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068052081
      Start time:                    2015-04-14 10:25:00
      End time:                      2015-04-14 10:38:21
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
      Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
      Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
      Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
      Next step for Browser:         Use the following information to resolve the error, and then try the setup process again.
      Next step for ComponentUpdate: Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  BRENDA-PC-HOME
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   italiano (Italia)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Brenda\Downloads\SQLEXPRWT_x64_ENU\x64\setup\
      Installation edition:          Express
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT AUTHORITY\SERVIZIO DI RETE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    true
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, CONN, BC, SDK, SSMS, ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLEXPRESS
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Latin1_General_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           Brenda-PC-Home\Brenda
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            true
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
      Feature:                       SQL Browser
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
      Feature:                       Setup Support Files
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                SQL Server Setup Support Files
      Component error code:          1935
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
      Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
    Please refer to Help and Support for more information. HRESULT: 0x80070422.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SystemConfigurationCheck_Report.htm

Maybe you are looking for