SQL Server 2014 SSRS Login Prompt won't go away

Hi,
I'm attempting to set up SQL Server Reporting Services on one of my environments.  The architecture is:
Database Server: SQL Server 2014 hosting my databases as well as the ReportServer / ReportServerTempDB databases
SSRS Server: SQL Server 2014 with just SSRS installed, hosting the web front end
I created a new SSRS database using the SSRS configuration manager.
When I log into the website on the local machine (http : // localhost/reports),
I'm prompted for my credentials once and once I authenticate (domain\username), everything works as expected.  However, when I attempt to access the server remotely (either http or https : // reportserver.domain.com/reports)
I'm prompted for my credentials at least 12 times.  If I keep re-entering them, the SQL Server Reporting Services Home folder/website will eventually re-appear, but if I try to navigate, I'm once again prompted for my credentials.
I did some research and verified that my AuthenticationTypes in the rsreportserver.config file was set to only RSWindowsNTLM.
Additional environment info: both servers are hosted on AWS, and we are using an ELB to access the SSRS webserver.  I'm using IE11 to attempt web access.
Thanks!

Hi Rob,
I am not sure why you are using the -A while setting up the SPN, Use  -S to set the SPN and make sure you delete the old one(setspn -D HTTP/<server> domain\user )
Use the following command line to set the SPN
SETSPN –S HTTP/hostname.abc.com:<portnumber> DOMAIN\ServiceAccount
Note: The config file for reporting services also needs to be updated to allow Windows
authentication. Do the following:
1. Locate the installation directory of the reporting server instance.
2. Open the ‘rsreportserver.config’ with a text editor such as Notepad.
3. Find the following XML parameters
<Authentication>
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>
4. Change the value
‘RSWindowsNTLM’ to ‘RSWindowsNegotiate
Hope This Helps
Thanks
Bhanu

Similar Messages

  • How to clean uninstall SQL Server 2014?

    Hi,
    I had SQL Server 2014 Management Studio installed, and I decided to try to install CU5 to get some more of the Azure functionality back in SSMS. Unfortunately it didn't work, so I decided to uninstall SQL 2014 MS. After doing so, I realized that the CU5
    update was still 'installed' in add/remove programs, and I could no longer uninstall it. I've tried reinstalling SQL Server 2014 MS, but it won't allow me to apply the CU5 update anymore. Is there any way I can either apply the CU5 update, or just nuke everything
    and try to restart from scratch without reinstalling Windows? Also I have VS2013/VS2015 installed if that makes a difference (I'd really rather not have to reinstall those). Thanks!
    Tommy

     SQL Server 2014 Evaluation, Already installed on Windows 2012 Server .So kindly let me know how to convert in to the License copy. Right now, We have license of SQL Server 2014.
    You need to purchase valid license from Microsoft. before that please read
    upgrade matrix by Microsoft which says what version can be upgraded from evaluation edition.
    If you have cluster direct upgrade has limited supported please read that as well.
    When you have Licensed version Just click on setup.exe file of licensed version then on window which posp up select maintenance and the select edition upgrade
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Is SSRS 2012 compatible with SQL Server 2014?

    Will it still work if a DW database is in SQL Server 2014 but the reporting services is in SSRS 2012?

    Very likely. If not, probably will be at the next service pack.
    Kalman Toth Database & OLAP Architect
    T-SQL Scripts at sqlusa.com
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • Why is the PWDCOMPARE function not supported on an Azure SQL Server 2014 database

    I have tried to publish a database from our local SQL Server to Azure but receive an error saying PWDCOMPARE is not supported with no link to a reason why.
    We are using HASHBYTES function to encrypt passwords in our database and
    PWDCOMPARE to validate them and we currently don't have an alternative (see article: http://sqlity.net/en/2460/sql-password-hash/). The PWDCOMPARE function is referenced by a stored procedure,
    which is what won't publish to Azure.
    It would be useful to know if it will be supported or if we should create a VM instead.
    EDIT: Further Clarified question above, but basically the functions listed are documented in MSDN and there is no mention of them being undocumented unsupported features.
    The error occurs when trying to publish a database to Azure from SQL Server 2014 Management Studio

    Hi,
    I am not an expert to answer this but am trying my best to answer this query.
    Hashes a password and compares the hash to the hash of an existing password. PWDCOMPARE can be used to search for blank SQL Server login passwords or common weak passwords.
    Syntax
    PWDCOMPARE ( 'clear_text_password'
       , password_hash
       [ , version ] )
    Note: This feature will be removed in the next version of Microsoft SQL Server. Do not use this feature in new development work, and modify applications that currently use this feature as soon as possible.
    I am not sure whether this feature is not available on SQL 2014.
    I think you can solve this issue by using the EXECUTE AS. Add this query into a procedure with EXECUTE AS with the user/login with sufficient permissions on the server.
     Refer to belw link for more details on EXECUTE AS
    http://msdn.microsoft.com/en-us/library/ms188354.aspx
    create
    procedure checkpassword
    @UserName
    SYSNAME
    ,@Password
    VARCHAR(1000)
    WITH
    EXECUTE AS
    '<UserName>'
    as
    select
    pwdcompare(@Password,convert(nvarchar(128),password))
    from master.dbo.syslogins
    (nolock)
     where name=@UserName
    GO
    EXEC checkpassword
    @UserName='test',@Password='12345678'
    Girish Prajwal

  • 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

  • SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

    We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.)  Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
    anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
    specifically listed as a SQL DB user tries to use the front end they get an error of:
    Microsoft SQL Server Login
    Connection failed:
    SQL State: '28000'
    SQL Server Error: 18456
    [Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
    After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
    to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
    Thanks a billion in advance ----

    Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
    all other roles, as well as allowing select only, and still have no access for the guest account.
    The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
    and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
    thru MS Access ACCDB, using a (by default) read only OCDB connection.
    This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
    levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
    since the result set would involve hundreds of thousands if not millions of records.
    So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
    as well as running our network on Microsoft's network software.

  • Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

    I tried to install ,deleted and re-installed several times and no help at all.
    visual studio 2013 with update 2 rc and adk installed in my computer.
    error code: 0x851a0019
    error messege in setup: could not find the database engine startup handle
    edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
    logs:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 13:53:29
      End time:                      2014-04-03 14:47:48
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for DQ:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  ARIELUBA-PC
      Machine processor count:       8
      OS version:                    Windows 8
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             Database Engine Services                 1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             SQL Server Replication                   1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    Database Engine Services            
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    SQL Server Replication              
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012                                                          LocalDB        
                             1033                 Express Edition      11.1.3412.0     No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
      Installation edition:          Evaluation
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Hebrew_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            ARIELUBA-PC\Arie Luba
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   
      CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
      CLTSTARTUPTYPE:                Manual
      CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               Manual
      CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     ARIELUBA-PC\Arie Luba
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
      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:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT Service\MsDtsServer120
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              SharePointFilesOnlyMode
      RSSVCACCOUNT:                  NT Service\ReportServer
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Hebrew_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           ARIELUBA-PC\Arie Luba
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       Reporting Services - Native
      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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Database Engine Services
      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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Data Quality 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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Full-Text and Semantic Extractions for Search
      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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Master Data Services
      Status:                        Passed
      Feature:                       Distributed Replay Client
      Status:                        Passed
      Feature:                       Distributed Replay Controller
      Status:                        Passed
      Feature:                       Integration Services
      Status:                        Passed
      Feature:                       Data Quality Client
      Status:                        Passed
      Feature:                       Analysis Services
      Status:                        Passed
      Feature:                       Reporting Services - SharePoint
      Status:                        Passed
      Feature:                       Reporting Services Add-in for SharePoint Products
      Status:                        Passed
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
    2014-04-03 14:14:28.01 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    2014-04-03 14:14:28.01 Server      UTC adjustment: 3:00
    2014-04-03 14:14:28.01 Server      (c) Microsoft Corporation.
    2014-04-03 14:14:28.01 Server      All rights reserved.
    2014-04-03 14:14:28.01 Server      Server process ID is 7148.
    2014-04-03 14:14:28.01 Server      System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
    2014-04-03 14:14:28.01 Server      Authentication mode is WINDOWS-ONLY.
    2014-04-03 14:14:28.01 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-04-03 14:14:28.01 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2014-04-03 14:14:28.01 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-04-03 14:14:28.01 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    -m "SqlSetup"
    -Q
    -q "Hebrew_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    2014-04-03 14:14:28.28 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2014-04-03 14:14:28.28 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-04-03 14:14:28.28 Server      Detected 8099 MB of RAM. This is an informational message; no user action is required.
    2014-04-03 14:14:28.28 Server      Using conventional memory in the memory manager.
    2014-04-03 14:14:28.31 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2014-04-03 14:14:28.34 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-04-03 14:14:28.36 Server      Query Store settings initialized with enabled = 1, 
    2014-04-03 14:14:28.36 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2014-04-03 14:14:28.36 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-04-03 14:14:28.38 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-04-03 14:14:28.39 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2014-04-03 14:14:28.39 spid8s      Warning ******************
    2014-04-03 14:14:28.39 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-04-03 14:14:28.40 spid8s      Starting up database 'master'.
    2014-04-03 14:14:28.42 Server      Software Usage Metrics is disabled.
    2014-04-03 14:14:28.48 Server      CLR version v4.0.30319 loaded.
    2014-04-03 14:14:28.56 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014-04-03 14:14:28.62 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.63 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.64 spid8s      SQL Trace ID 1 was started by login "sa".
    2014-04-03 14:14:28.64 spid8s      Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
    2014-04-03 14:14:28.65 spid16s     Password policy update was successful.
    2014-04-03 14:14:28.66 spid16s     Error: 17190, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-04-03 14:14:28.66 spid16s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17826, Severity: 18, State: 3.
    2014-04-03 14:14:28.66 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-04-03 14:14:28.67 spid16s     Error: 17120, Severity: 16, State: 1.
    2014-04-03 14:14:28.67 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    ________________________________________________________________________________________________

    Is it okay? (see below)
    ;SQL Server 2014 Configuration File
    [OPTIONS]
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 
    ACTION="Install"
    ; Detailed help for command line argument ROLE has not been defined yet. 
    ROLE="AllFeatures_WithDefaults"
    ; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 
    ENU="True"
    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. 
    UIMODE="Normal"
    ; Setup will not display any user interface. 
    QUIET="False"
    ; Setup will display progress only, without any user interaction. 
    QUIETSIMPLE="False"
    ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 
    UpdateEnabled="True"
    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 
    ERRORREPORTING="False"
    ; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 
    USEMICROSOFTUPDATE="False"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
    will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 
    FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
    ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
    or a Windows Update service through the Window Server Update Services. 
    UpdateSource="MU"
    ; Displays the command line parameters usage 
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console. 
    INDICATEPROGRESS="False"
    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 
    X86="False"
    ; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 
    INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 
    INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
    (RS). 
    INSTANCENAME="MSSQLSERVER"
    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 
    SQMREPORTING="False"
    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 
    INSTANCEID="MSSQLSERVER"
    ; The computer name that the client communicates with for the Distributed Replay Controller service. 
    CLTCTLRNAME="SQLDRC"
    ; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 
    CTLRUSERS="ARIELUBA-PC\Arie Luba"
    ; The account used by the Distributed Replay Controller service. 
    CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
    ; The startup type for the Distributed Replay Controller service. 
    CTLRSTARTUPTYPE="Manual"
    ; The account used by the Distributed Replay Client service. 
    CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
    ; The startup type for the Distributed Replay Client service. 
    CLTSTARTUPTYPE="Manual"
    ; The result directory for the Distributed Replay Client service. 
    CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
    ; The working directory for the Distributed Replay Client service. 
    CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
    ; RSInputSettings_RSInstallMode_Description 
    RSINSTALLMODE="DefaultNativeMode"
    ; RSInputSettings_RSInstallMode_Description 
    RSSHPINSTALLMODE="SharePointFilesOnlyMode"
    ; Specify the installation directory. 
    INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
    ; Agent account name 
    AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
    ; Auto-start service after installation.  
    AGTSVCSTARTUPTYPE="Manual"
    ; Startup type for Integration Services. 
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account. 
    ISSVCACCOUNT="NT Service\MsDtsServer120"
    ; The name of the account that the Analysis Services service runs under. 
    ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
    ; Controls the service startup type setting after the service has been created. 
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services. 
    ASCOLLATION="Hebrew_CI_AS"
    ; The location for the Analysis Services data files. 
    ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files. 
    ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files. 
    ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files. 
    ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files. 
    ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
    ; Specifies whether or not the MSOLAP provider is allowed to run in process. 
    ASPROVIDERMSOLAP="1"
    ; Specifies the list of administrator accounts that need to be provisioned. 
    ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 
    ASSERVERMODE="MULTIDIMENSIONAL"
    ; CM brick TCP communication port 
    COMMFABRICPORT="0"
    ; How matrix will use private networks 
    COMMFABRICNETWORKLEVEL="0"
    ; How inter brick communication will be protected 
    COMMFABRICENCRYPTION="0"
    ; TCP port used by the CM brick 
    MATRIXCMBRICKCOMMPORT="0"
    ; Startup type for the SQL Server service. 
    SQLSVCSTARTUPTYPE="Automatic"
    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3). 
    FILESTREAMLEVEL="0"
    ; Set to "1" to enable RANU for SQL Server Express. 
    ENABLERANU="False"
    ; Specifies a Windows collation or an SQL collation to use for the Database Engine. 
    SQLCOLLATION="Hebrew_CI_AS"
    ; Account for SQL Server service: Domain\User or system account. 
    SQLSVCACCOUNT="NT Service\MSSQLSERVER"
    ; Windows account(s) to provision as SQL Server system administrators. 
    SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express. 
    ADDCURRENTUSERASSQLADMIN="True"
    ; Specify 0 to disable or 1 to enable the TCP/IP protocol. 
    TCPENABLED="1"
    ; Specify 0 to disable or 1 to enable the Named Pipes protocol. 
    NPENABLED="0"
    ; Startup type for Browser Service. 
    BROWSERSVCSTARTUPTYPE="Automatic"
    ; Specifies which account the report server NT service should execute under.  When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. 
    RSSVCACCOUNT="NT Service\ReportServer"
    ; Specifies how the startup mode of the report server NT service.  When 
    ; Manual - Service startup is manual mode (default).
    ; Automatic - Service startup is automatic mode.
    ; Disabled - Service is disabled 
    RSSVCSTARTUPTYPE="Automatic"
    ; Add description of input argument FTSVCACCOUNT 
    FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

  • Hybrid Connection fails for Windows SQL Server 2014 - SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted

    Hello,
    I have configured BizTalk Services Hybrid Connection between Standard Azure Website and SQL Server 2014 on premise.
    Azure Management portal shows the status of Hybrid Connection as established.
    However, the website throws an error when trying to open a connection
    <
    addname="DefaultConnection"
    connectionString="Data
    Source=machine name;initial catalog=AdventureWorks2012;Uid=demouser;Password=[my password];MultipleActiveResultSets=True"
    providerName="System.Data.SqlClient"
    />
    (The same website, with the same connection string deployed on SQL Server machine works correctly).
    I tried various options with the connections sting (IP address instead of machine name, Trusted_Connection=False, Encrypt=False, etc. the result is the same
    [Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted]
    [SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.
    I tried various machines - on premise and a clean Azure VM with SQL Server and it results in the same error - below full stack
    The certificate chain was issued by an authority that is not trusted             
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.            
    Exception Details: System.ComponentModel.Win32Exception: The certificate chain was issued by an authority that is not trusted
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.                  
    Stack Trace:
    [Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted]
    [SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)]
    System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +5341687
    System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +546
    System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle, SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean callerHasConnectionLock) +5348371
    System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean canAccumulate) +91
    System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode, Boolean canAccumulate) +331
    System.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec, FeatureExtension requestedFeatures, SessionData recoverySessionData) +2109
    System.Data.SqlClient.SqlInternalConnectionTds.Login(ServerInfo server, TimeoutTimer timeout, String newPassword, SecureString newSecurePassword) +347
    System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover) +238
    System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout) +892
    System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance) +311
    System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData) +646
    System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) +278
    System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions) +38
    System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) +732
    System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) +85
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1057
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +78
    System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) +196
    System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +146
    System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +16
    System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) +94
    System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +110
    System.Data.SqlClient.SqlConnection.Open() +96
    System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +44
    [EntityException: The underlying provider failed on Open.]
    System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +203
    System.Data.EntityClient.EntityConnection.Open() +104
    System.Data.Objects.ObjectContext.EnsureConnection() +75
    System.Data.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) +41
    System.Data.Objects.ObjectQuery`1.System.Collections.Generic.IEnumerable<T>.GetEnumerator() +36
    System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) +369
    System.Linq.Enumerable.ToList(IEnumerable`1 source) +58
    CloudShop.Services.ProductsRepository.GetProducts() +216
    CloudShop.Controllers.HomeController.Search(String SearchCriteria) +81
    CloudShop.Controllers.HomeController.Index() +1130
    lambda_method(Closure , ControllerBase , Object[] ) +62
    System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) +14
    System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) +193
    System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) +27
    System.Web.Mvc.Async.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41() +28
    System.Web.Mvc.Async.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _) +10
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
    System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) +32
    System.Web.Mvc.Async.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33() +58
    System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +225
    System.Web.Mvc.Async.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult) +10
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
    System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) +34
    System.Web.Mvc.Async.<>c__DisplayClass2a.<BeginInvokeAction>b__20() +23
    System.Web.Mvc.Async.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) +99
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
    System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) +27
    System.Web.Mvc.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) +14
    System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
    System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +39
    System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
    System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) +29
    System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) +10
    System.Web.Mvc.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) +25
    System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
    System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +31
    System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) +9
    System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +9651188
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155
    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.36213            
    Regards,
    Michal
    Michal Morciniec

    Same issue here, looking for more information !

  • 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.

  • 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

  • SQL Server Express 2012 Login Error

    I’m trying to access sql database from another PC on the LAN and I’m getting this error message “Login failed for user ‘Officeo1\Guest’. I’m using SQL Server Express 2012 and on the other PC I’m trying to connect with MS Visual Studio 2013. I’m adding a
    data connection with the data source set to Microsoft SQL Server (sqlClient), server name OFFICE01\SQLEXPRESS using windows authentication. I can see the server in the dropdown box but I cannot see any databases in the database name dropdown box.
    why767

    These computers are not on a domain but on the same workgroup. This is the error I get when I try to connect from MS SQL Server 2014 Import and Export
    ==================================
    Could not retrieve table list. (SQL Server Import and Export Wizard)
    ===================================
    Login failed for user 'OFFICE01\Guest'.
    Cannot open user default database. Login failed. (Microsoft SQL Server Native Client 11.0)
    Program Location:
       at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
       at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionInternal.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.OleDb.OleDbConnection.Open()
       at Microsoft.SqlServer.Dts.DtsWizard.SQLServerForm.LoadDatabasesList()
    why767

  • Install SQL Server 2014 in Windows Server 2012 R2

    Hi,
    I had install a Windows server 2012 R2 Standard version in my VM and i make it as my domain server as well. I had create another account "ABC" and login with this new created account "ABC" in the same machine to install SQL server 2014,
    it give me a warning for rule "Computer domain controller" which I understand that I'm installing the SQL server in the domain controller is not recommended. I continue to install and when reach to Server Configuration, I found that SQL Server Analysis
    Service account is missing where I cannot found it. 
    May I know is there any features that I missing or any way to make it done?
    Thank you.

    I found that SQL Server Analysis Service account is missing where I cannot found it. 
    May I know is there any features that I missing or any way to make it done?
    Thank you.
    IIRC (If I remember correct)Configuring Analysis service account is after you have passed the Server configuration page. Did you selected analysis service checkbox when  on feature selection page. What editoon of SQL server 2014 you are installing are
    you installing express edition ? SSAS is not present in express edition
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • SharePoint 2013 and SQL Server 2014

    Does SharePoint 2013 supports SQL Server 2014 for Reporting Services, PowerPivot

    Yes it does (or rather, SSRS 2014/PowerPivot 2014 support SharePoint 2013). They also support SharePoint 2010.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • 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

  • Installing Sql Server 2014 Management studio problem

    Hi,
    I installed a full SQL 2014 evaluation ISO on a 64 bit Windows server 2008 R2 machine:
    (file name - SQLServer2014SP1-FullSlipstream-x64-ENU.ISO)
    On this machine I already have a instance of SQL Server 2008 Express running (with Management Studio).
    I try to download on the Management studio either from:
    https://www.microsoft.com/en-us/download/details.aspx?id=42299 
    or
    https://msdn.microsoft.com/en-us/sqlserver2014express.aspx
    and the download just won't start. Am I missing anything ?
    Is the management studio already on the ISO I installed?
    Thanks,
    Assaf 

    Your issue not clear you installed the SQL Server 2014 instance and you didn't find the management studio for it or what is the issues please explain more about it 
    thanks
    Mustafa EL-Masry
    Principle Database Administrator & DB Analyst
    SQL Server MCTS-MCITP-MCSA-MCSE
    M| +966 54 399 0968

Maybe you are looking for