SQL Server 2014 Snapshot agent duplicating constraints
Hello,
We are upgrading our server from SQL Server 2008 R2 Std. Ed. to SQL Server 2014 Std. Ed.
Our server works with Merge and Transactional publications.
Our current problem happens when trying to generate the first snapshot using the snapshot agent. Since this is the first time, the snapshot will create all the system tables related with replication and the error happens when creating the table MSmerge_conflict_<publication>_<article>
because now the snapshot agent is trying to create the constraints from the <article> (a table in our case) with the same name, so it brings the conflict of having duplicated constraints names and because of that the snapshot agent fails.
This didn't happen on 2008 because the snapshot agent didn't try to create the constraints before.
This is the error that we see on the Snapshot Agent Status: There is already an object named"NewAccountPermission" in the database. Could not create constraint or index. See previous errors.
The exact T-sql statement that is failing is shown on the replication monitor:
Error messages:
Message: There is already an object named 'NewAccountPermission' in the database.
Could not create constraint or index. See previous errors.
Command Text: CREATE TABLE [dbo].[MSmerge_conflict_Roster_AccountPermissions](
[AccountPermissionID] [int] NOT NULL CONSTRAINT [NewAccountPermission] DEFAULT ([dbo].[getNewAccountPermissionID]()),
[PermissionName] [varchar](255) NULL,
[Description] [varchar](255) NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL
Digging a bit further I searched and compared the snapshot files that creates this table. Here it can be seen that the snapshot files only differ on the creation or not of the constraint.
Here is an extract o f the 2014 file called AccountPermissions_3.cft
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[MSmerge_conflict_Roster_AccountPermissions](
[AccountPermissionID] [int] NOT NULL CONSTRAINT [NewAccountPermission] DEFAULT ([dbo].[getNewAccountPermissionID]()),
[PermissionName] [varchar](255) NULL,
[Description] [varchar](255) NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL
Here is the 2008 version of the same file:
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[MSmerge_conflict_Roster_AccountPermissions](
[AccountPermissionID] [int] NOT NULL,
[PermissionName] [varchar](255) NULL,
[Description] [varchar](255) NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL
Any ideas on what is going on? Do I have to configure some properties on the publication now to disallow creating the constraints on the msmerge_conflict table?
Thank you,
Alejandro Rivera
Hi Hilary,
1) There is an user table called dbo.AccountPermissions. The problem happens when the snapshot agent tries to create MSmerge_conflicts_Roster_AccountPermissions (system table). The database is called Roster.
2) We use the default dbo schema. Here is the create script for that table (just in case):
USE [Roster]
GO
/****** Object: Table [dbo].[AccountPermissions] Script Date: 11/17/2014 7:48:27 PM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[AccountPermissions](
[AccountPermissionID] [int] NOT NULL CONSTRAINT [NewAccountPermission] DEFAULT ([dbo].[getNewAccountPermissionID]()),
[PermissionName] [varchar](255) NULL,
[Description] [varchar](255) NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_13B9434FF11A44ACB63F5D2927C053FD] DEFAULT (newsequentialid()),
CONSTRAINT [pk_accountpermissions] PRIMARY KEY CLUSTERED
[AccountPermissionID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
GO
I'd put a screenshot too, but sadly the forum doesn't allow me until it verifies my account.
Let me know if you any more info.
Thank you,
Similar Messages
-
SQL Server 2014 Replication: Peer-to-peer replication
SQL Server 2014 Replication wizard: Peer-to-peer replication -> Agent Security Settings setup only Log Reader Agent Security Settings are available.
After I selected replication type and articles only Log Reader Agent Status was available, the Snapshot Agent Reader Status displays text:
"A Snapshot Agent job has not been created for this publication."
Another issue with replication:
"Peer-to-peer publications only support a '@sync_type' parameter value of 'replication support only', 'initialize with backup' or 'initialize from lsn'.
The subscription could not be found."
Search how to resolve issues in SQL Server 2014?Please check this similar post ..
http://blogs.msdn.com/b/sqljourney/archive/2013/10/01/an-interesting-issue-with-peer-to-peer-replication.aspx
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/15701595-f5b1-4a10-b4aa-c56a94d64785/peertopeer-publications-only-support-a-synctype-parameter-value-of-replication-support-only?forum=sqlreplication
Raju Rasagounder Sr MSSQL DBA -
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.
h2007You 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 -
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" -
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. -
Overlapped I/O error 997 installing SQL Server 2014 Express on Windows Server 2012 R2
I'm attempting to install SQL Server 2014 Express on a Windows Server 2012 R2 system. When I do the install, it fails (several times) with an "Error: 997. Overlapped I/O operation is in progress.". From searching the web, I can see many people
have had this problem with this installer and other non-SQL server installers.
I've tried every solution I can find discussed, but none help with my problems The system is fully updated, with the exception of the KB2538243 (VC 2008 SP1 redist), which is probably failing for the same reason.
I've tried removing several updates mentioned in other articles (KB2918614). I've confirmed that I'm not using a temporary profile.
Does anyone have an idea of how I can solve this issue?
Thanks,
Zack
Partial detail from install log file:
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio 2010 Redistributables
Component error code: 997
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150205_151618\VC10Redist_Cpu64_1.log
Error description: Error 997.Overlapped I/O operation is in progress.
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=vc_red.msi%40ProcessComponents%40997
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio 2010 Redistributables
Component error code: 997
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150205_151618\VC10Redist_Cpu64_1.log
Error description: Error 997.Overlapped I/O operation is in progress.
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=vc_red.msi%40ProcessComponents%40997
Partial detail from component log file:
MSI (s) (D8:3C) [15:18:29:173]: Resolving source.
MSI (s) (D8:3C) [15:18:29:173]: Resolving source to launched-from source.
MSI (s) (D8:3C) [15:18:29:173]: Setting launched-from source as last-used.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\'.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\'.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{1D8E6291-B0D5-35EC-8441-6616F567A0F7}'.
MSI (s) (D8:3C) [15:18:29:188]: SOURCEDIR ==> C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\
MSI (s) (D8:3C) [15:18:29:188]: SOURCEDIR product ==> {1D8E6291-B0D5-35EC-8441-6616F567A0F7}
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: A general error running CryptAcquireContext
MSI (s) (D8:3C) [15:18:29:188]: Determining source type
MSI (s) (D8:3C) [15:18:29:188]: Source type from package 'VC_RED.MSI': 2
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (D8:3C) [15:18:29:204]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: New Hash Database creation complete.
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:997
MSI (s) (D8:3C) [15:18:29:235]: SECUREREPAIR: Failed to CreateContentHash of the file: install.res.1040.dll: for computing its hash. Error: 997
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (D8:3C) [15:18:29:235]: SECUREREPAIR: SecureRepair Failed. Error code: 3e561F257D8
Action start 15:18:29: ProcessComponents.
MSI (s) (D8:3C) [15:19:28:843]:
Error 997.Overlapped I/O operation is in progress.Alberto,
Thanks for your help. Unfortunately, I've already tried that. I did try it again and I get an "This update is not applicable to your computer."
I tried to post the Windows Update log, but it was too large. I've posted some of it below.
Here is the WU log:
2015-02-06 11:24:25:793
5048 50
Misc =========== Logging initialized (build: 7.9.9600.17489, tz: -0500) ===========
2015-02-06 11:24:25:793
5048 50
Misc = Process: C:\Windows\system32\wusa.exe
2015-02-06 11:24:25:793
5048 50
Misc = Module: C:\Windows\System32\wuapi.dll
2015-02-06 11:24:25:793
5048 50
COMAPI ----------- COMAPI: IUpdateServiceManager::AddScanPackageService -----------
2015-02-06 11:24:25:793
5048 50
COMAPI - ServiceName = Windows Update Standalone Installer
2015-02-06 11:24:25:793
5048 50
COMAPI - ScanFileLocation = C:\c5f288db3c43a7e4613232ca1a3c\wsusscan.cab
2015-02-06 11:24:25:808
920 111c
Misc =========== Logging initialized (build: 7.9.9600.17489, tz: -0500) ===========
2015-02-06 11:24:25:808
920 111c
Misc = Process: C:\Windows\system32\svchost.exe
2015-02-06 11:24:25:808
920 111c
Misc = Module: c:\windows\system32\wuaueng.dll
2015-02-06 11:24:25:808
920 111c
Service *************
2015-02-06 11:24:25:808
920 111c
Service ** START ** Service: Service startup
2015-02-06 11:24:25:808
920 111c
Service *********
2015-02-06 11:24:25:824
920 111c
IdleTmr Non-AoAc machine. Aoac operations will be ignored.
2015-02-06 11:24:25:824
920 111c
Agent * WU client version 7.9.9600.17489
2015-02-06 11:24:25:824
920 111c
Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2015-02-06 11:24:25:824
920 111c
Agent * Base directory: C:\Windows\SoftwareDistribution
2015-02-06 11:24:25:824
920 111c
Agent * Access type: No proxy
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 12.
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 4.
2015-02-06 11:24:25:824
920 111c
Agent * Network state: Connected
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 12.
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 4.
2015-02-06 11:24:25:855
920 b64
Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2015-02-06 11:24:25:855
920 111c
Agent *********** Agent: Initializing global settings cache ***********
2015-02-06 11:24:25:887
920 111c
Agent * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2015-02-06 11:24:25:887
920 111c
Agent * WSUS server: <NULL>
2015-02-06 11:24:25:887
920 111c
Agent * WSUS status server: <NULL>
2015-02-06 11:24:25:887
920 111c
Agent * Target group: (Unassigned Computers)
2015-02-06 11:24:25:887
920 111c
Agent * Windows Update access disabled: No
2015-02-06 11:24:25:902
920 b64
WuTask WuTaskManager delay initialize completed successfully..
2015-02-06 11:24:25:902
920 b64
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-02-07 08:14:01, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2015-02-06 19:30:54, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
AU Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2015-02-06 19:30:54, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2015-02-06 11:24:25:902
920 b64
Report CWERReporter::Init succeeded
2015-02-06 11:24:25:902
920 b64
Agent *********** Agent: Initializing Windows Update Agent ***********
2015-02-06 11:24:25:902
920 b64
DnldMgr Download manager restoring 0 downloads
2015-02-06 11:24:25:902
920 111c
AU ########### AU: Initializing Automatic Updates ###########
2015-02-06 11:24:25:902
920 111c
AU AIR Mode is disabled
2015-02-06 11:24:25:902
920 111c
AU # Approval type: Scheduled (User preference)
2015-02-06 11:24:25:902
920 111c
AU # Auto-install minor updates: Yes (User preference)
2015-02-06 11:24:25:902
920 111c
AU # Will interact with non-admins (Non-admins are elevated (User preference))
2015-02-06 11:24:25:902
920 111c
Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=2250
2015-02-06 11:24:25:918
920 111c
AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2015-02-06 11:24:25:918
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:918
920 111c
AU AU finished delayed initialization
2015-02-06 11:24:25:933
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:933
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:933
920 b64
Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\a487aa0f-3e53-4fee-a784-6171b00254e4\Source.cab with dwProvFlags 0x00000080:
2015-02-06 11:24:25:933
920 111c
AU Adding timer:
2015-02-06 11:24:25:933
920 111c
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-02-07 08:14:01, not idle-only, not network-only
2015-02-06 11:24:25:949
920 af0
DnldMgr Asking handlers to reconcile their sandboxes
2015-02-06 11:24:25:949
920 b64
Misc Microsoft signed: Yes
2015-02-06 11:24:26:154
920 b64
DtaStor Default service for AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
2015-02-06 11:24:26:154
920 b64
IdleTmr Incremented idle timer priority operation counter to 1
2015-02-06 11:24:26:154
5048 50
COMAPI - Added scan package service, ServiceID = {A487AA0F-3E53-4FEE-A784-6171B00254E4} Third party service
2015-02-06 11:24:26:154
5048 50
COMAPI -------------
2015-02-06 11:24:26:154
5048 50
COMAPI -- START -- COMAPI: Init Search [ClientId = wusa]
2015-02-06 11:24:26:154
5048 50
COMAPI ---------
2015-02-06 11:24:26:154
5048 50
COMAPI -------------
2015-02-06 11:24:26:154
5048 50
COMAPI -- START -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:26:154
5048 50
COMAPI ---------
2015-02-06 11:24:26:169
920 b64
IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 17; does use network; is not at background priority
2015-02-06 11:24:26:169
920 b64
IdleTmr Incremented idle timer priority operation counter to 2
2015-02-06 11:24:26:341
920 b64
Report *********** Report: Initializing static reporting data ***********
2015-02-06 11:24:26:341
920 b64
Report * OS Version = 6.3.9600.0.0.131344
2015-02-06 11:24:26:341
920 b64
Report * OS Product Type = 0x00000021
2015-02-06 11:24:26:357
920 b64
Report * Computer Brand = PowerSpec
2015-02-06 11:24:26:357
920 b64
Report * Computer Model = S Series
2015-02-06 11:24:26:357
920 b64
Report * Platform Role = 1
2015-02-06 11:24:26:357
920 b64
Report * AlwaysOn/AlwaysConnected (AOAC) = 0
2015-02-06 11:24:26:357
920 b64
Report * Bios Revision = 1.1a
2015-02-06 11:24:26:357
920 b64
Report * Bios Name = 1.1a
2015-02-06 11:24:26:357
920 b64
Report * Bios Release Date = 2013-08-20T00:00:00
2015-02-06 11:24:26:357
920 b64
Report * Bios Sku Number = S Series
2015-02-06 11:24:26:357
920 b64
Report * Bios Vendor = American Megatrends Inc.
2015-02-06 11:24:26:357
920 b64
Report * Bios Family = Server
2015-02-06 11:24:26:357
920 b64
Report * Bios Major Release = 4
2015-02-06 11:24:26:357
920 b64
Report * Bios Minor Release = 6
2015-02-06 11:24:26:357
920 b64
Report * Locale ID = 1033
2015-02-06 11:24:26:357
920 b64
Handler Calculating current update level for this session
[ Omitted data ]
http://support.microsoft.com/?kbid=3000850, timestamp 01d039c57a22c0be
2015-02-06 11:24:28:388
920 b64
Handler Done calculating current update level for this session
2015-02-06 11:24:28:982
920 b64
Agent *** START *** Queueing Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
5048 50
COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:28:982
920 11f4
Agent *** END *** Queueing Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
920 11f4
Agent *************
2015-02-06 11:24:28:982
920 11f4
Agent ** START ** Agent: Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
920 11f4
Agent *********
2015-02-06 11:24:28:982
920 11f4
Agent * Online = Yes; Ignore download priority = No
2015-02-06 11:24:28:982
920 11f4
Agent * Criteria = "DeploymentAction='Installation'"
2015-02-06 11:24:28:982
920 11f4
Agent * ServiceID = {A487AA0F-3E53-4FEE-A784-6171B00254E4} Third party service
2015-02-06 11:24:28:982
920 11f4
Agent * Search Scope = {Machine}
2015-02-06 11:24:28:982
920 11f4
Agent * Caller SID for Applicability: S-1-5-21-3157695610-3447843402-2534478823-500
2015-02-06 11:24:28:982
920 11f4
Agent * RegisterService is set
2015-02-06 11:24:29:185
920 11f4
PT +++++++++++ PT: Synchronizing server updates +++++++++++
2015-02-06 11:24:29:185
920 11f4
PT + Offline serviceId = {A487AA0F-3E53-4FEE-A784-6171B00254E4}
2015-02-06 11:24:29:185
920 11f4
PT WARNING: Cached cookie has expired or new PID is available
2015-02-06 11:24:29:185
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:185
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:185
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:294
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:294
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:294
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:357
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:357
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:357
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:638
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:638
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:638
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:013
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:30:013
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:30:013
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:044
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:30:044
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:30:044
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:044
920 11f4
PT + SyncUpdates round trips: 5
2015-02-06 11:24:30:076
920 11f4
PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2015-02-06 11:24:30:076
920 11f4
PT + Offline serviceId = {A487AA0F-3E53-4FEE-A784-6171B00254E4}
2015-02-06 11:24:30:138
920 11f4
Agent * Found 0 updates and 54 categories in search; evaluated appl. rules of 126 out of 284 deployed entities
2015-02-06 11:24:30:138
920 11f4
Agent *********
2015-02-06 11:24:30:138
920 11f4
Agent ** END ** Agent: Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:30:138
920 11f4
Agent *************
2015-02-06 11:24:30:138
920 11f4
IdleTmr WU operation (CSearchCall::Init ID 1, operation # 17) stopped; does use network; is not at background priority
2015-02-06 11:24:30:138
920 11f4
IdleTmr Decremented idle timer priority operation counter to 1
2015-02-06 11:24:30:154
5048 1428
COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:30:154
5048 1428
COMAPI - Updates found = 0
2015-02-06 11:24:30:154
5048 1428
COMAPI ---------
2015-02-06 11:24:30:154
5048 1428
COMAPI -- END -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:30:154
5048 1428
COMAPI ------------- -
SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur
Hi All,
I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
advice in the end was to post a question here.
SQL Server Nodes, 2014 (12.0.2480.0)
1 Share witness (on separate subnet)
1 Cluster
1 Listener
I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
a small table and hit execute.
The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
Availability DB is 200Mb and is not actively used. The nodes are synchronised.
SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
Questions:
1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
Msg 983, Level 14, State 1, Line 2
Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
00001090.00002128::2015/02/25-03:05:08.255 INFO [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:10.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:11.888 INFO [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
00001090.00002698::2015/02/25-03:05:11.889 INFO [GUM] Node 2: Processing RequestLock 2:49
00001090.00002128::2015/02/25-03:05:11.890 INFO [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
00001090.00002698::2015/02/25-03:05:11.890 INFO [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
00001090.00002128::2015/02/25-03:05:12.890 INFO [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:15.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:16.988 INFO [GUM] Node 2: Processing RequestLock 1:28
Thanks in advance.
KeeganHi Keegan,
From these event log , what I can see is "Sending request Netname" wasted the time .
Could you please tell us the network configuration of that cluster nodes ?
If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
https://support.microsoft.com/kb/258750?wa=wsignin1.0
After that please test again .
Best Regards,
Elton JI
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] . -
SQL Server 2014 Express Installation Failure
Hi,
Now trying to install SQL Server 2014 Express on my work machine. Here is the error log. Any ideas? The error help link is useless.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-06-19 16:24:17
End time: 2014-06-19 16:38:03
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 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: PC12345
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
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
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Scott\Software\SQLEXPRADV_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
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: C:\SQL Server Data
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: INTERNAL\sbass
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140619_162416\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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
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%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
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%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
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%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
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%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
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\20140619_162416\SystemConfigurationCheck_Report.htmThanks Shanky, that fixed my issue. I reinstalled, specifying NT AUTHORITY\LOCALSYSTEM for the SQL Server Database Engine account. After the successful installation, I used Sql Server Configuration Manager to change the account to LocalService
(NT AUTHORITY\LocalService). The Database Engine is restarting OK.
So, my accounts are:
SQL Server (MSSQLSERVER): NT AUTHORITY\LocalService
SQL Full-text Fiter Daemon Launcher (MSSQLSERVER): NT Service\MSSQLFDLauncher
SQL Server Reporting Services (MSSQLSERVER): NT Service\ReportServer
SQL Server Browser: NT AUTHORITY\LOCALSERVICE
SQL Server Agent (MSSQLSERVER): NT AUTHORITY\NETWORKSERVICE
I check out the link http://msdn.microsoft.com/en-us/library/ms143504.aspx#Serv_Perm. I'm a bit confused how the NT Service\* accounts are created, such as NT Service\MSSQLSERVER. However, I did see this http://msdn.microsoft.com/en-us/library/ms191153.aspx#manual;
perhaps I need to read it further.
Regardless, this is my desktop machine, the installation is for development only, it's inside our network, and no external users will be accessing this SQL Server instance. So, while I haven't fully read the details on running under LocalService, I
believe this will meet my needs.
Thanks again for your help. -
Help installing Sql server 2014
Sir i am currently using Visual studio 2013 (with built in Local DB v11), sir i need to use SQL Server Agent (for timed jobs) and cannot find that option in Local DB. Do i need to install SQL Server management studio 2014 for this purpose? If yes, i DON'T know
which version should i install ? will it affect my currently available Local DB ? i was thinking about installing this:
Express with Advanced Services (SQLEXPRADV_Architecture_Language.exe)
Please help and reply, thank you so much.. !i need to use SQL Server Agent
Hello,
The feature SQL Server Agent is only available in Web/BI/Standard/Enterprise Edition, not in Express nor LocalDB, see
Features Supported by the Editions of SQL Server 2014
You could use Windows Scheduler + SqlCmd tool to run scheduled Jobs.
Olaf Helper
[ Blog] [ Xing] [ MVP] -
SSIS packages are failing after upgrade to SQL server 2014
Hi,
I have some SSIS packages running on SQL server 2012 .
After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
I read some articles about this and they say it not able to connect to SQL server agent job.
And, I can see that the package is running if i run manually using SQL 2012 run time.
Why its not running on SQL 2014 ?
did i miss anything while upgrading SQL server 2014 ?
Please give me some suggestions to solve this issue.
And is there any way i can change the SQL server agent 2014 to adapt this and run ?
Below is the error :
The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
errors.: This occures when CPackage::LoadFormXML fails.
Regards,
Vinodh Selvaraj.I think you have typed this error message by yourself.
Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
You may try executing package in 32 bit mode from SQL Agent Job.
Please refer:
http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
-Vaibhav Chaudhari -
How to convert Oracle User defined datatype to SQL Server 2014 using SSMA Version 6.0
I am trying to convert Oracle 11g OE schema to SQL Server 2014, using SSMA version 6.0
Getting an error in converting the Oracle View to SQL Server
CREATE OR REPLACE VIEW OC_CUSTOMERS OF OE.CUSTOMER_TYP WITH OBJECT IDENTIFIER (customer_id) AS
SELECT c.customer_id, c.cust_first_name, c.cust_last_name, c.cust_address,
c.phone_numbers,c.nls_language,c.nls_territory,c.credit_limit,
c.cust_email,
CAST(MULTISET(SELECT o.order_id, o.order_mode,
MAKE_REF(oc_customers,o.customer_id),
o.order_status,
o.order_total,o.sales_rep_id,
CAST(MULTISET(SELECT l.order_id,l.line_item_id,
l.unit_price,l.quantity,
MAKE_REF(oc_product_information,
l.product_id)
FROM order_items l
WHERE o.order_id = l.order_id)
AS order_item_list_typ)
FROM orders o
WHERE c.customer_id = o.customer_id)
AS order_list_typ)
FROM customers c
* SSMA error messages:
* O2SS0461: Conversion of object view is not supported.
* OF OE.CUSTOMER_TYP
* WITH OBJECT IDENTIFIER (customer_id)
CREATE VIEW dbo.OC_CUSTOMERS
AS
/*Generated by SQL Server Migration Assistant for Oracle version 6.0.0.*/
* SSMA error messages:
* O2SS0481: Conversion of statement containing user defined type column 'c.cust_address' not supported.
* O2SS0481: Conversion of statement containing user defined type column 'c.phone_numbers' not supported.
* O2SS0430: Conversion of multiset conditions is not supported.
* CAST(MULTISET
* SELECT
* o.order_id,
* o.order_mode,
* MAKE_REF(oc_customers, o.customer_id),
* o.order_status,
* o.order_total,
* o.sales_rep_id,
* CAST(MULTISET
* SELECT
* l.order_id,
* l.line_item_id,
* l.unit_price,
* l.quantity,
* MAKE_REF(oc_product_information, l.product_id)
* FROM order_items l
* WHERE o.order_id = l.order_id
* ) AS order_item_list_typ)
* FROM orders o
* WHERE c.customer_id = o.customer_id
* ) AS order_list_typ)
SELECT
c.CUSTOMER_ID,
c.CUST_FIRST_NAME,
c.CUST_LAST_NAME,
c.cust_address,
c.phone_numbers,
c.NLS_LANGUAGE,
c.NLS_TERRITORY,
c.CREDIT_LIMIT,
c.CUST_EMAIL,
NULL
FROM dbo.CUSTOMERS AS c */
Any suggestion on converting this view would be helpful.
Kind regards.Thanks Lydia Zhang for your reference urls.
Please let me know if you come across any reference articles related to
Creating a SQL Server table and View with columns as SQL Server TVP similar to Oracle UDT like
CREATE TABLE "OE"."CUSTOMERS"
( "CUSTOMER_ID" NUMBER(6,0),
"CUST_FIRST_NAME" VARCHAR2(20 BYTE) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE,
"CUST_LAST_NAME" VARCHAR2(20 BYTE) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE,
"CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" ,
"PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" ,
"NLS_LANGUAGE" VARCHAR2(3 BYTE),
And also creating a SQL Server TVP inside an another SQL Server TVP as in Oracle
create or replace TYPE customer_typ
AS OBJECT
( customer_id NUMBER(6)
, cust_first_name VARCHAR2(20)
, cust_last_name VARCHAR2(20)
, cust_address cust_address_typ
, credit_limit NUMBER(9,2)
, cust_email VARCHAR2(30)
, cust_orders order_list_typ
NOT FINAL;
Kind regards.
Venkatesha -
Sql Server 2014 - Error message: Failed to read BLOB column
Hi all,
Am experiencing this error in Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Enterprise Edition (Build 7601: Service Pack 1).
Error messages:
Message: Failed to read BLOB column
Stack: at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper)
at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint, String
strWhereClause, Boolean useTableLockHint, Int32 bcpFileFormatVersion)
at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.DoWork(WorkItem workItem)
at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()
at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 0)
Get help: http://help/0
Message: Shared Memory Provider: No process is on the other end of the pipe.
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Message: Communication link failure
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Message: Shared Memory Provider: No process is on the other end of the pipe.
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Message: Communication link failure
Stack: (Source: MSSQLServer, Error number: 233)
Get help: http://help/233
Please can you assist me on this issue.The error message states a communication link failure has occurred.
This is most likely a network related error and usually is transient.
Try to generate the snapshot again and see if the error still occurs. If the error still occurs, you will need to have a network admin check the links.
Brandon Williams (blog |
linkedin) -
SQL SERVER 2014 Installation error
Hi, I'm having great difficulty in installing SQL server 2014 developer edition 64- bit . When I use to run setup it says sql server boot strapper.dll is missing although it is present inside the folder and when I opened the sql setup bootstrapper.dll it
gives the error "This file doesn't have a program associated with it for performing this action". ? I've attached the snapshot of the error as well.
Needs immediate help.Hello,
Are you trying to install from a network share/location? Could you try to copy the media to a folder on the c:\ drive.
If the media is an .ISO file, please unzip it using WinRAR and install from that folder on the C:\ drive.
If the above does not help, could you try to download the media again.
The following article may be useful.
http://www.sqlcoffee.com/SQLServer2014_0005.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Moving sql server 2000 to sql server 2014
Moving sql server 2000 to sql server 2014. Could someone please give me steps to move everything from sql 2000 one server to sql 2014. I have 2 instance on sql 2000. 8 databases on each of them. On both instances we have store procedure and jobs.
i think your SQL Server 2000 is hosted on old Windows server version so based on that you should prepare new environment for SQL Server 2014 from Win Server 2012 Sp1 and SQL Server 2014 and build your clusters then start your Migration from Old Servers to
new servers and here below is 10 configurations outlines that you should look after carefully for any DB consolidation or migration from a server to a server and indeed they represent unique potentials for your DB Consolidation /migration service that
can leverage distinctly your service quality and shape you very well in front of your customers:
1- Backup DBs and restore DBs with ZERO down time and ZERO data loss in the same time …Awesome …!
2- Cloning all DB special features that are not covered by backups and restores such as :
RCSI (Read committed snapshot isolation level using row versioning)
Service brokers
Encryption keys and certificates
3- Cloning identically all SQL logins with their mapped DB users including their passwords (if SQL authenticated logins ) and privileges on both server and DB levels .
4- Copying .rdl and .rds files between different versions of reporting services where backup and restore reportserver and reportservertemp DBs is not an option
5- Cloning all special Jobs like certain business jobs configured to perform some business stuff .
6- Cloning all mail profiles with their mail accounts
7- Cloning all Linked server + Aliases might be used inside old DB servers
8- Cloning some server configurations like CLR ,CPU parallelism, Replication size , Network packet size , optimize for ad hoc workloads
9- Cloning all Replications configurations for publishers and subscribers
10- Cloning all DTC configurations for both local and clustered DTC services
Follow the below links to know the steps by the scripts:
http://sqlserver-performance-tuning.net/?p=5262
http://sqlserver-performance-tuning.net/?p=5359
http://sqlserver-performance-tuning.net/?p=5398
http://sqlserver-performance-tuning.net/?p=5415
http://sqlserver-performance-tuning.net/?p=5458
Mustafa EL-Masry
Principle Database Administrator & DB Analyst
SQL Server MCTS-MCITP
M| +966 54 399 0968
MostafaElmasry.Wordpress.com -
Error message when installing SQL Server 2014 Express
When installing SQL Server 2014 Express,
I get the error shown below.
Why do I get this and how to correct for it?
TITLE: Microsoft SQL Server 2014 Setup
The following error has occurred:
An error occurred during the installation of assembly 'Microsoft.VC80.MFC,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more
information. HRESULT: 0x80070422.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xDF039760%25401201%25401
BUTTONS:
OK
ThanksHi,
here is the log file:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068052081
Start time: 2015-04-14 10:25:00
End time: 2015-04-14 10:38:21
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for Browser: Use the following information to resolve the error, and then try the setup process again.
Next step for ComponentUpdate: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: BRENDA-PC-HOME
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: italiano (Italia)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Brenda\Downloads\SQLEXPRWT_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\SERVIZIO DI RETE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, CONN, BC, SDK, SSMS, ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Brenda-PC-Home\Brenda
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: true
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: SQL Browser
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Setup Support Files
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SystemConfigurationCheck_Report.htm
Maybe you are looking for
-
Custom tag attribute case insensitive??
We ran in to an interesting "feature" of custom tags: The attributes in the tags seem to be case insensitive. For example, if you play with the "tagext/quote" example provided with the WebLogic server installation, you c
-
Hello, using webcenter and UCM 11.1.1.6 we have dropped content presenter. we go to CTRL SHIFT C mode. we click first icon "Create New" thinking we will create a New Content. At this point, we do not want to use Oracle Site Studio Create New screen.
-
Unable to calculate text snippet height
Hello, I am trying to dinamically adjust the size (height) of a container so a text snippet doesn't move to the next container. In other words I try to make sure that this exact snippet belongs to only one container. The way I try to achieve it is by
-
There are links on site that open in new windows and close after you are done. Like A review link/box. The window opens but it's a blank page and the url books just says "search bookmarks and history". == This happened == Every time Firefox opened ==
-
CS4 (PS 11) constant crashes with larger files -
I am encountering persistent program crashes with Photoshop 11 (CS4) when I have multiple layers (four or more) and the file size exceeds 75 mb. The error message that Photoshop has encountered a problem and is closing appears without further details