SQL Server 2014 active directory requirements
Hi,
Does anybody know if there are any issues or changes needed to be made on domain controllers, when installing/using SQL Server 2014 advanced services like Always On and In-Memory OLTP?
Thanks.
Calin
Hello,
No changes from previous version of SQL Server (2012). You only have to take in consideration the last section of the following
article.
https://msdn.microsoft.com/en-us/library/ms143506.aspx#DC_support
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Similar Messages
-
Require list of all events for Windows Server 2008 Active Directory
Hi all,
I require list of all events for Windows Server 2008 Active Directory. Event Log name for Active Directory log is "Directory Service".
Regards,
SRHi,
Thanks for your posting.
Do you mean you want to list all Active Directory logs into one file named “Directory Services”?
If that, it’s hard to achieve. There are kinds of Active Directory logs stored in different locations and they have different file formats. It’s hard
to collect them into one file.
Active directory records events in the directory services log in Event Viewer. By default, Active Directory records only critical error events. To instruct Active
Directory to record other events in the directory services log, we need to modify registry.
For more information please refer to following MS articles:
Active Directory Diagnostic Logging
http://technet.microsoft.com/en-us/library/cc961809.aspx
How to configure Active Directory diagnostic event log
http://support.microsoft.com/kb/314980
Lawrence
TechNet Community Support -
SSDT/VisualStudio requirements for SQL Server 2014
Hi
What is the minimum version of SSDT (VS Shell) is required for the creation of BI solutions in SQL Server 2014?
I have VS2010 (was installed from SQL Server 2012 installation media) but this will not work with SQL Server 2014.Hello Roger,
the current Releases of SSDT are not longer available for Visual Studio 2010, only for VS 2012/2013.
When you install a current SSDT Version, also the related VS as integrated Shell be installed, you can get SSDT-BI/Tooling here: http://msdn.microsoft.com/en-us/data/hh297027
Olaf Helper
[ Blog] [ Xing] [ MVP] -
Sharepoint Foundation 2010 compatibility with SQL Server 2014
Due to a requirement to use Sharepoint without Active Directory access. I am trying to find explicit confirmation whether Sharepoint Foundation 2010 is compatible with SQL Server 2014. I have seen that Sharepoint Server 2010 and 2013 are compatible
with SQL Server 2014 as of CU 1 (released in April). But there is no mention of Sharepoint Foundation.
This chart is great except it doesn't mention whether the Foundation versions are supported.
http://msdn.microsoft.com/en-us/library/gg492257.aspx
Thanks.Note that that is for the Reporting Services component, but not necessarily for the SQL Database Engine component (which comes from the SharePoint Product Group, rather than the SQL Product Group). I haven't seen any confirmation that SharePoint 2010 is
supported at all with SQL 2014 as a Database Engine.
Trevor Seward
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
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" -
Allowing users access to SQL Server 2014 analysis server cubes
I am using SQL Server 2014 analysis server and have created a number of cubes. These all function as expected however it seems that only windows users who are in an
administrator group can get access. All other users are denied access with the very vague error of 'Communication error'.
If I then add that user to our administrators group within the windows domain they instantly get access. I have defined roles for each cube (within analysis services) and then added both individuals (i.e. their windows domain user id) as well as their windows
domain groups to these roles but they still cannot get access - just get the error 'Communication error'.
I am using ADOMD on the client side which I know works because users in the administrators group can see the data. I have granted cube permissions using Management studio however no matter what front end we use (either our own App or EXCEL) if the user in
question is NOT in the administrator group in the domain they cannot get access to any of the cubes.
Any help anyone can provide would be much appreciated.Hamishr,
According to your description, you want to grant the access permission to cube for the users who are not belong to Administrator group, right?
By default, no one except a Server Administrator or Database Administrator has permission to query cubes in a database. Cube access by a non-administrator requires membership in a role created for the database containing the cube. Membership is supported
for Windows user or group accounts, defined in either Active Directory or on the local computer. So in your scenario, please ensure the steps to grant permission are correct, you can refer to the link below check it.
http://msdn.microsoft.com/en-in/library/ms174799.aspx
Regards,
Charlie Liao
TechNet Community Support -
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 extract file parameter?
I am working to bundle SQL Server 2014 Express with an application. I am using the following command line to install via an InstallShield prerequisite: /qs /INSTANCENAME=MYINSTANCE /ACTION="Install" /FEATURES=SQLEngine,Conn,SSMS
/SECURITYMODE=SQL /SAPWD="Password" /TCPENABLED=1 /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /IACCEPTSQLSERVERLICENSETERMS
The installer I am using is SQLEXPRWT_x86_ENU.exe.
When the installer starts up their is a dialog named: Choose Directory for Extract Files. In earlier versions of SQL Server Express this dialog did not require the user to press Ok to continue. Since it takes several minutes to install
SQL Server Express I prefer to show the installation to the user, so they can see that something is taking place. The /q (Quiet) parameter will suppress this dialog, but nothing is seen for several minutes. Note: the Installer documentation
does state that: The /QS switch only shows progress, does not accept any input, and displays no error messages if encountered. The /QS parameter is only supported when /Action=install is specified. Consequently, I believe the /QS parameter
should not be requiring input.
All that for these questions:
1) Is there away to suppress this dialog while still using the /qs (Quiet Simple) parameter.
2) Is there a parameter to tell the installer to extract the files to a specified location?
Thanks,
LesHi,
After you download the installation package of SQL Server Express 2014, and extracts it to the specified location, the dialog of “Choose Directory for Extract Files” will appear when you install the SQL Server Express. Usually, we need to use the following
steps to extract the setup files to a temporary location.
1.In the Command Prompt window type %USERPROFILE%\Downloads\ SQLEXPRWT_x86_ENU.exe /x
2.When prompted to Choose Directory For Extracted Files type C:\SQLEXPR and click OK to extract the files.
Or suppress the dialog to extract the right location in SQL Server Express 2008 or other lower version. Such as
c:\temp>SQLEXPRWT_x64_ENU.exe /extract: "c:\temp".
However, in SQL Server Express 2014, I do a test, we could not suppress the dialog or use the parameters directly to extract in command line. For more information about
installing SQL Server 2014 from the Command Prompt, you can review the following article.
http://msdn.microsoft.com/en-us/library/ms144259.aspx
If necessary, personally, I recommend you can provide Microsoft a feature request at
https://connect.microsoft.com/SQLServer so that we can try to modify and expand the product features based on your needs.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support -
Cannot uninstall instance of SQL Server 2014
Hello,
I have two instances of SQL Server 2014 installed and i want to uninstall them (and install SQL Server 2012 evaluation). I managed to uninstall the one instance. When i try to uninstall the second a message informs me that the operating system does not meet
the minimum requirements. I had the same proble when uninstalling SQL Server 2012 and i went to the setup file and changed the compatibility mode to Windows Vista. Is there something similar that i should do in the case of SQL Server 2014 or i should do something
totally different?
Thanks in advance,
AndreasHi,
Personally I have not faced this situation but this seems bug below Connect Item MS closed as not reproducable
https://connect.microsoft.com/SQLServer/feedback/details/707706/unable-to-uninstall-sql-server-2012-rc0-from-control-panel
Below connect Item deals with same issue as your
https://connect.microsoft.com/SQLServer/feedback/details/974626/cannot-uninstall-sql-express-2014-on-windows-7-sp1
Workaround should be instaed of uninstalling using GUI please use command prompt
Launch setup.exe from an elevated command shell. Change to the directory "c:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\SQLServer2014", then type:
Setup.exe /action=uninstall
Please change uninstall script as per need
Normal uninstall Script would look like
Setup.exe /Action=Uninstall /FEATURES=SQL,AS,RS,IS,Tools /INSTANCENAME=InstanceName
Please refer to
this link for uninstall parameters
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP -
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 -
Unable to install SQL Server 2014 Express LocalDb on Windows 8.1 Update 1
Apologies if this is not the right place or this has been posted before (I looked and didn't find anything)
I am unable to install SQL Server 2014 Express LocalDb on Windows 8.1 Update 1, as I get an 'Operating System not Supported' error message right away.
What can I do to get this working?Hi Zgreve,
Usually, from
hardware and software requirements for installing SQL Server 2014, we can install SQL Server Express version on the Windows 8.1. For more information, see:
Microsoft SQL Server 2014 Express.
Before you install SQL Server 2014 Express version, you should ensure installing the .NET Framework 4, then run as administrator for the SQL Server setup.exe again.
There is a similar detail about install SQL Server Express LocalDB via GUI and command line. You can also review the following steps.
http://www.mssqltips.com/sqlservertip/2694/getting-started-with-sql-server-2012-express-localdb/
If the same error about OS still exists, I recommend you submitting a feedback to Microsoft such issues at
https://connect.microsoft.com/SQLServer/Feedback, Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the
exciting projects on Microsoft Connect.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support -
Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core
I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition
Hi KamarasJaranger,
According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
and refer to the
PDF file.
1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
2.Discover target portals.
3.Connect targets and configuring Multipathing.
4.Initialize and format the Disks.
5.Verify the Storage Replication Process.
6.Run the Failover Cluster Validation Wizard.
7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
8.Tune Cluster Heartbeat Settings.
9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
12.Test application connectivity.
Regards,
Michelle Li -
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 ------------- -
Error when installing SQL Server 2014 Express
I am running a Win 8.1 desktop 64bit (fully updated) with already installed SQL Server 2012 and Visual Studio 2010 and 2013 (non Express versions). I need to keep SQL Server 2012 for development purposes but also need SQL Server 2014 for a database
provided to me by others which needs this version. I found out it should be possible to run the two versions side-by-side. During installation of SQL Server 2014 Express I selected all features except 'Local Db' and used a named instanc
e. The setup runs through without any notice of problems but at the end fails with error code 1638 the reason being 'Error installing Microsoft Visual Studio 2010 Redistributables'. Also at the end a window pops up mention 'The working of SQL Server
2014 stopped - Trying to find a solution'. Doing nothing on my part the window disappears and nothing else happens. So I uninstalled any 'Redistributable' and ran setup again. Same result though both 'Microsoft Visual C++ 2008 Redistributable
- x86 9.0.30729.4974' and 'Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219' re-appear in Control Panel as being
p
roperly installed! All features are marked as 'failed' with one and the same error 1638. Even tried just upgrading to see if that would work but also here same error.
I have not been able to find the proper solution so I am now stuck. Hopefully someone can give me the right steps to take? Ruud van der SpoelHello,
Error 1638 means another version of the product is already installed. Probably you have a 32-bit version installed but
the installation requires a 64-bit version of VC.
Try to manually install both 32-bit and 64-bit versions of each VC.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
I am getting following error while refreshing connection on excel sheet in power pivot gallery,
my scenario,
using BISM file connection to create and refresh power pivot excel sheet in power pivot gallery
throws error and we have sql server 2014 CU6 updated installed plus sharepoint 2013. i checked following msolap110.dll is available in our environment but assembly
Microsoft.AnalysisServices.ChannelTransport is not available.
i found error in event viewer,
"Activation context generation failed for "C:\Program Files\Microsoft Analysis
Services\AS OLEDB\110\msolap110.dll". Dependent Assembly
Microsoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
not be found. Please use sxstrace.exe for detailed diagnosis.
what should i do to fix it?
Thanks for help.
Deepak PatelRebecca,
yes, this is issue i am getting.
Activation
context generation failed for "C:\Program
Files\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll".
Dependent AssemblyMicrosoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
not be found. Please use sxstrace.exe for detailed diagnosis.
let me know if you can find fix for it.
THanks,
Maybe you are looking for
-
ITunes (Windows) does not quit properly
Closing windows version using "x" at top right corner of screen or selecting Exit from file menu makes iTunes clear the screen, but it's still runnning. I have to do a ctrl-alt-del and then manually quit the process tree. Otherwise, re-clicking on th
-
Understanding A/P credit memo
Hi everyone, I have some transactions as the following: 1. Goods Receipt PO No. 1 ItemCode_______________________ItemCost_______Quantity M001G0A001NAC0030020_________1,235,205.44_______300 M001G0A001NAC0055020_________1,680,397.84_______400 M001G0A00
-
Smf / sometimes does not configure network interfaces in single-user mode?
From http://groups.yahoo.com/group/solarisx86/message/14785 When booting into single user mode, I often get a message on the console t_optmgmt: System error: Cannot assign requested addressand only the loopback interface is configured (lo0 inet, and
-
Process.destoy() problem
Hi ! I've got a problem using jdk 1.2.2 on an alpha system java -versionjava version "1.2.2-6" Classic VM (build J2SDK.v.1.2.2:04/26/2000-09:58, native threads, jit_122) uname -aOSF1 <host> V4.0 878 alpha The problem is that when I start a process us
-
When we create internal order of mobile
Hi All, when we create internal order of mobile then the shown are error messages that number is not within valid enterval. Firstly over company mobile expenses are on reliance what we move in airtel. plz solve the problem. Moderator: Please, avoid a