I have installed SQL Server 2012 management studio in client machine and it is giving error while open new query window.

When I click "New query" it returns have an error: "Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED))"

Cheers,

Hi ALl,

I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')

Contents of summary log:

Overall summary:
   Final result:                  Failed: see details below
   Exit code (Decimal):           -2068578304
   Exit facility code:            1204
   Exit error code:               0
   Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
   Start time:                    2015-01-09 10:19:12
   End time:                      2015-01-09 10:20:07
   Requested action:              Install

Setup completed with required actions for features.
 Troubleshooting information for those features:
   Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BIDS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.

 Machine Properties:
   Machine name:                  IDCSQLTST11
   Machine processor count:       2
   OS version:                    Future Windows Version
   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

Package properties:
   Description:                   Microsoft SQL Server 2012
   ProductName:                   SQL Server 2012
   Type:                          RTM
   Version:                       11
   SPLevel:                       0
   Installation location:         E:\SQL_Server_2012_StandardEdition\x64\setup\
   Installation edition:          Standard

Product Update Status:
   None discovered.

User Input Settings:
   ACTION:                        Install
   ADDCURRENTUSERASSQLADMIN:      false
   AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
   AGTSVCPASSWORD:                <empty>
   AGTSVCSTARTUPTYPE:             Automatic
   ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
   ASCOLLATION:                   Latin1_General_CI_AS
   ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
   ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
   ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
   ASPROVIDERMSOLAP:              1
   ASSERVERMODE:                  MULTIDIMENSIONAL
   ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
   ASSVCPASSWORD:                 <empty>
   ASSVCSTARTUPTYPE:              Manual
   ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
   ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
   BROWSERSVCSTARTUPTYPE:         Disabled
   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:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
   CTLRSTARTUPTYPE:               Manual
   CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
   CTLRSVCPASSWORD:               <empty>
   CTLRUSERS:                     DOMAINAA\user12345
   ENABLERANU:                    false
   ENU:                           true
   ERRORREPORTING:                false
   FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
   FILESTREAMLEVEL:               0
   FILESTREAMSHARENAME:           <empty>
   FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
   FTSVCPASSWORD:                 <empty>
   HELP:                          false
   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\MsDtsServer110
   ISSVCPASSWORD:                 <empty>
   ISSVCSTARTUPTYPE:              Automatic
   MATRIXCMBRICKCOMMPORT:         0
   MATRIXCMSERVERNAME:            <empty>
   MATRIXNAME:                    <empty>
   NPENABLED:                     0
   PID:                           *****
   QUIET:                         true
   QUIETSIMPLE:                   false
   ROLE:                         
   RSINSTALLMODE:                 DefaultNativeMode
   RSSHPINSTALLMODE:              SharePointFilesOnlyMode
   RSSVCACCOUNT:                  NT Service\ReportServer
   RSSVCPASSWORD:                 <empty>
   RSSVCSTARTUPTYPE:              Manual
   SAPWD:                         <empty>
   SECURITYMODE:                  SQL
   SQLBACKUPDIR:                  <empty>
   SQLCOLLATION:                  Latin1_General_CI_AS
   SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
   SQLSVCPASSWORD:                <empty>
   SQLSVCSTARTUPTYPE:             Automatic
   SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
   SQLTEMPDBDIR:                  F:\TempDB
   SQLTEMPDBLOGDIR:               <empty>
   SQLUSERDBDIR:                  E:\SQLData
   SQLUSERDBLOGDIR:               D:\SQLLog
   SQMREPORTING:                  false
   TCPENABLED:                    1
   UIMODE:                        Normal
   UpdateEnabled:                 true
   UpdateSource:                  MU
   X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini

Detailed results:
   Feature:                       Database Engine Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Server Replication
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Full-Text and Semantic Extractions for Search
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Data Quality Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Analysis Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Reporting Services - Native
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Reporting Services - SharePoint
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Reporting Services Add-in for SharePoint Products
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Data Quality Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Integration Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Client Tools Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Management Tools - Complete
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Client Tools SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Client Tools Backwards Compatibility
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Distributed Replay Controller
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Distributed Replay Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Server Data Tools
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Management Tools - Basic
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Client Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Client Connectivity SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Writer
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Documentation Components
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Browser
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm

Exception summary:
 The following is an exception stack listing the exceptions in outermost to innermost order
 Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
     Message:
         The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
     HResult : 0x84b40000
         FacilityCode : 1204 (4b4)
         ErrorCode : 0 (0000)
     Data:
       SQL.Setup.FailureCategory = InputSettingValidationFailure
       DisableWatson = true
     Stack:
         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
         at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
     Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
         Message:
                 The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x87d00006
                 FacilityCode : 2000 (7d0)
                 ErrorCode : 6 (0006)
         Data:
           DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
           SettingName = CLTRESULTDIR
           WatsonData =  Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

Hi Experts,

I have applied patch KB3045313 in one of our MS SQL server 2008 R2 SP2 x64 instance in my environment with 2 nodes cluster. The patch have been applied on both the nodes successfully. But I can see the below difference of versions on both nodes.

Node1: 10.50.4000

Node2: 10.50.4042

Whenever I flip the cluster service from node 1 to node2. The MS SQL internal upgrade script has been initiated and showed the version  10.50.4042 on node2 and when the cluster service flip from node 2 to node1. The MS SQL internal upgrade script (which is basically a downgrade to 4000) initiated and showed the version 10.50.4000 on node1. 

The patches are same on both the nodes. 

Any help !

Usaf

All,

Has anyone been successful installing TP3 on either SQL 2012, 2012 R2, SP2, 2016?

I followed the instructions here Configuring SQL Server AlwaysOn for Configuration Manager and cannot get TP3 to install as instructed. A portion of these instructions are confusing to me. If I point TP3 Setup to the first endpoint on the AG as the instructions state I endup with a ConfigMgrSetup.log with terminating errors as:"ERROR: Failed to set database 'CM_XXX' to SINGLE_USER mode", "ERROR: Failed to set database to SINGLE_USER mode", "ERROR: Failed to set database options". I already tried this several times, I even tried to point TP3 Setup to the AD VCO name created for the "Listener" as suggested by a SQL DBA and still not sucessful..... any thoughts on what might be happening?. If I posted this in the wrong forum please let me know... I figured it was more a SQL question than ConfigMgr

edthefixer

Hello,

SQL Server 2012 install just quits after "install setup files" during the install.  I am installing on Windows

2012 Server.  What can I do?

In the sql install log file:

SQM Service: Sqm does not have active session.

How can I resolve this error?

Paul

Hi everyone,

The following is the description of what I did:

- Fresh install Windows 2012r2 joined to my domain controller

- Installation of MS SQL Server 2012, with the definition of both the windows and SQL authentication

- During the installation I define the group " domain admins " as the authorize group to manage SQL Server

- The problem I face, is when using a member of the domain admins to connect to the MS SQL, the connection fails with the error 

   18456.

- The connection using the SQL authentication "sa" works fine.

- After connecting using the "sa", I verified the properties of the security login " domain admins ", I see windows authentication is

   enabled

Is there something I'm missing?

Thank you for your help.

Hi,  SQL Server 2014 web edition work with Microsoft Dynamics Nav 2015?

I read the Microsoft Dynamics NAV 2015 requirements but not sure. 

Thanks

We are looking at upgrading our automated CI build and deploy of analysis services cubes to SQL 2014. We are using the deployment tool as part of the process and we are looking to upgrade the dependant dll's on our build server to version 12.0

We're unable to locate the required version of Microsoft.SqlServer.WizardFramework.dll. So far we've checked the installs for

• SQL Server
• SSMS
• SSDT

None appear to distribute this DLL.

For reference, the error we see when running Microsoft.AnalysisServices.Deployment.exe (version 12.0) is:

Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.SqlServer.WizardFramework, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
  at Microsoft.AnalysisServices.Deployment.Startup.Main(String[] args)

Microsoft.AnalysisServices.Deployment\Microsoft.AnalysisServices.Deployment.exe (return code was -532462766)

Adam Tappis. (MCSD VB6 & .NET, MCDBA SQL 2000)

Thanks in advance.  I have tried several things and others have experienced similar issues, but people either do not post their fix or the issue is never resolved.

We have 2 separate SQL installs running on Windows 2003 Enterprise Edition Service Pack 2 OS x86.  SQL is currently at 9.0.3175.  The installs of service pack 3 and 4 vboth fail.  The original issue reported the follwing in the summary.txt.

Product Installation Status

Product                   : SQL Server Database Services 2005 (MSSQLSERVER)

Product Version (Previous): 3073

Product Version (Final)   :

Status                    : Failure

Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB954606_sqlrun_sql.msp.log

Error Number              : 1635

Error Description         : Unable to install Windows Installer MSP file

To resolve this issue, the following artickle was done, which has moved me past this error and to a new error: http://blogs.msdn.com/b/sqlserverfaq/archive/2009/01/30/part-1-sql-server-2005-patch-fails-to-install-with-an-error-unable-to-install-windows-installer-msp-file.aspx?PageIndex=1#comments

This approach appear to even be the fix for a post here at Technet, but it does not work for me.

The summary.txt is now reading the following error:

Product                   : Database Services (MSSQLSERVER)
Product Version (Previous): 3175
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
Error Number              : 2902
Error Description         : MSP Error: 2902  The installer has encountered an unexpected error. The error code is 2902. Operation ixfAssemblyCopy called out of sequence.

Searches for this error are very broad and nothing specific to SQL.  Here is a copy of the error from the sqlrun_sql.msp.log.

MSI (s) (24:B8) [13:18:44:538]: Executing op: AssemblyCopy(SourceName=Smo.dll|Microsoft.SqlServer.Smo.dll,SourceCabKey=Microsoft.SqlServer.Smo.DC8FC6AD_FB4A_4A81_8366_0ED2594F1AEA,DestName=Microsoft.SqlServer.Smo.dll,Attributes=20480,FileSize=1603424,PerTick=32768,,VerifyMedia=1,,,,,ComponentId={653612B2-2738-4F92-936D-65DE042BD1BB},IsManifest=1,,,AssemblyMode=0,)
MSI (s) (24:B8) [13:18:44:538]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:570]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:570]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:570]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:570]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:570]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:570]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:570]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:570]: Product: Microsoft SQL Server 2005 -- Error 2902. The installer has encountered an unexpected error. The error code is 2902. Operation ixfAssemblyCopy called out of sequence.

Error 2902. The installer has encountered an unexpected error. The error code is 2902. Operation ixfAssemblyCopy called out of sequence.

Has anyone ever seen this before?  I inherites these SQL Servers and would also like to know what could have caused the issue, but obviously I want to install the latest SP for SQL first.  

Any help or assistance would be greatly appreciated.  Thanks. 

Hello guys,

I'm trying to install SQL 2008 (tried also SQL 2012) in a W2008R2 server that lives in a DMZ site covered by a couple of RODCs.

The RODCs have full access to the RWDCs, but the traffic is blocked from the rest of computers in the DMZ to the RWDCs.

Every time I run the wizard to install SQL server, it fails when trying to setup a domain user to run SQL services (“Server configuration >> Service Account” step). When I temporary allow the communication from that SQL Server to one of the RWDCs, it works.

I have obviously cached and prepopulated passwords in the RODCs and I am using Domain Admins and non-domain admins accounts.

We have more than 30 windows member servers authenticating against those RODCs in the DMZ and everything works fine.

Any ideas why the SQL installation wizard cannot authenticate against a RODC? I have been googling and I didn’t find anything!

I can also provide Wireshark / Network Monitor traces.

Thanks.

When I try to install SQL Server 2014 Express SP1 on a VMware Workstation 11 partition running Windows 10 x64 Professional, it hangs at Install_Watsonx86_32_Action.  Attempting to cancel the installation does not work so I have to restart the VMware partition.  After this I can normally restart the SQL Server installation and it will run to the end. I have seen this behavior on both the "Advanced Services" and "with Tools" versions.  Does anyone know how I can avoid the restart?