Hey everyone, alright so I have been beating my head on this one for a few days and I'm at a loss. I've been working on installing SQL Server 2012 SP1 on Windows Server 2012 using "best practices" as much as I can. I've been able to get it to install with all default settings, but when I start modifying the installation configuration I begin to run into problems.
Upfront here is a link to my Install Detail Log: Detail Install Log
A description of the "environment" I am attempting to install it to.
- It's a VMware virtual server.
- Running Windows Server 2012 Datacenter 64bit
- I have it currently configured with 16GB of ram and 8 cores (is intended to end up being a SQL server for a Sharepoint 2013 installation).
- SQL Server 2012 Developer Edition 64bit with SP1
- I'm installing only the Database Engine Services with SQL Server Replication and Full-Text and Semantic Search options + the Management tools
- Running on a Windows Domain that is set at 2008R2 for Forest and Domain
- Using an Enterprise and Domain Admin account for the installation also launching the setup with "Run as Administrator" the Domains "Domain Admin" group is added to the Local Administrator group on the local machine
That's the base, as I said if I install everything default, it works. Once I start making changes things start going south. Here is what I am attempting to do with varying degrees of success.
- Database Engine and Agent are using Managed Service Accounts, both accounts have been created, associated with the computer object in AD, and "installed" on the local machine I have also manually granted the readServicePrincipalName and writeServicePrincipalName permissions in AD (don't really know if this is necessary anymore, but I'm trying to be thorough to figure out what is missing)
- I've created the following drive structure on the server: Local Disk (C:), Programs (P:), SQL (S:), Data (F:), Logs (L:), TempDB (T:), Backup (B:) the intention is to install the binaries to P:, the instance files and data root directory to S:, user data files to F:, user logs to L:, TempDB and Logs to T: and backup to B: (open to changing it upon recommendation, this is based on my best effort to figure out a clear installation base). These are all separate VMware virtual hard disks added to the machine.
- Regarding folder/drive permissions I have largely tracked with: http://sqlblog.com/blogs/jonathan_kehayias/archive/2010/03/22/sql-server-installation-checklist.aspx regarding individual drive permissions to be more exact, my MSA has Full Control of: B:\, P:\ and S:\; List Folder Contents of: L:\, F:\ and T:\ and Full Control of folders at the root of L:\, F:\ and T:\
- I'm utilizing only Windows Authentication for the installation adding my domains SQLDBAs group (of which the account I'm using to install is a member)
When doing this everything seems to work up until the installation gets to: SqlEngineDBStartConfigAction_install_configrc_Cpu64 then it hangs for a minute before giving me an "Attempted to perform an unauthorized operation"
Here is the relevant section from the detail log:
(01) 2012-12-04 14:07:03 SQLEngine: --SqlServerStartup: SQLEngine: Slipstream case: Enable traceflag -T902 (01) 2012-12-04 14:07:03 SQLEngine: : Checking Engine checkpoint 'StartEngineService' (01) 2012-12-04 14:07:03 SQLEngine: --SqlServerServiceSCM: Starting SQL via SCM (-mSqlSetup -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659 -T3610 -T8015 -T902)... (01) 2012-12-04 14:07:03 Slp: Sco: Attempting to start service MSSQL$MOSS2013SQL (01) 2012-12-04 14:07:03 Slp: Sco: Attempting to open SC Manager (01) 2012-12-04 14:07:03 Slp: Sco: Attempting to open service handle for service MSSQL$MOSS2013SQL (01) 2012-12-04 14:07:04 Slp: Prompting user if they want to retry this action due to the following failure: (01) 2012-12-04 14:07:04 Slp: ---------------------------------------- (01) 2012-12-04 14:07:04 Slp: The following is an exception stack listing the exceptions in outermost to innermost order (01) 2012-12-04 14:07:04 Slp: Inner exceptions are being indented (01) 2012-12-04 14:07:04 Slp: (01) 2012-12-04 14:07:04 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException (01) 2012-12-04 14:07:04 Slp: Message: (01) 2012-12-04 14:07:04 Slp: Attempted to perform an unauthorized operation. (01) 2012-12-04 14:07:04 Slp: HResult : 0x84bb0001 (01) 2012-12-04 14:07:04 Slp: FacilityCode : 1211 (4bb) (01) 2012-12-04 14:07:04 Slp: ErrorCode : 1 (0001) (01) 2012-12-04 14:07:04 Slp: Data: (01) 2012-12-04 14:07:04 Slp: WatsonData = MSSQL$MOSS2013SQL (01) 2012-12-04 14:07:04 Slp: DisableRetry = true (01) 2012-12-04 14:07:04 Slp: Inner exception type: System.UnauthorizedAccessException (01) 2012-12-04 14:07:04 Slp: Message: (01) 2012-12-04 14:07:04 Slp: Attempted to perform an unauthorized operation. (01) 2012-12-04 14:07:04 Slp: Stack: (01) 2012-12-04 14:07:04 Slp: at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams) (01) 2012-12-04 14:07:04 Slp: ---------------------------------------- (01) 2012-12-05 06:58:23 Slp: User has chosen to retry this action (01) 2012-12-05 06:58:23 Slp: Sco: Attempting to close service handle for service MSSQL$MOSS2013SQL (01) 2012-12-05 06:58:23 Slp: Sco: Attempting to close SC Manager (01) 2012-12-05 06:58:23 Slp: Sco: Attempting to open SC Manager (01) 2012-12-05 06:58:23 Slp: Sco: Attempting to open service handle for service MSSQL$MOSS2013SQL (01) 2012-12-05 06:58:23 Slp: Prompting user if they want to retry this action due to the following failure: (01) 2012-12-05 06:58:23 Slp: ---------------------------------------- (01) 2012-12-05 06:58:23 Slp: The following is an exception stack listing the exceptions in outermost to innermost order (01) 2012-12-05 06:58:23 Slp: Inner exceptions are being indented (01) 2012-12-05 06:58:23 Slp: (01) 2012-12-05 06:58:23 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException (01) 2012-12-05 06:58:23 Slp: Message: (01) 2012-12-05 06:58:23 Slp: Attempted to perform an unauthorized operation. (01) 2012-12-05 06:58:23 Slp: HResult : 0x84bb0001 (01) 2012-12-05 06:58:23 Slp: FacilityCode : 1211 (4bb) (01) 2012-12-05 06:58:23 Slp: ErrorCode : 1 (0001) (01) 2012-12-05 06:58:23 Slp: Data: (01) 2012-12-05 06:58:23 Slp: WatsonData = MSSQL$MOSS2013SQL (01) 2012-12-05 06:58:23 Slp: DisableRetry = true (01) 2012-12-05 06:58:23 Slp: Inner exception type: System.UnauthorizedAccessException (01) 2012-12-05 06:58:23 Slp: Message: (01) 2012-12-05 06:58:23 Slp: Attempted to perform an unauthorized operation. (01) 2012-12-05 06:58:23 Slp: Stack: (01) 2012-12-05 06:58:23 Slp: at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams) (01) 2012-12-05 06:58:23 Slp: ----------------------------------------
I've ran procmon during a retry to see if I could figure out the permissions issue, I'm at a loss.
I have tried various things to resolve this with varying degrees of success. I've also gotten different errors (including "Could not find the Database Engine startup handle."). I have added my MSA to Local Administrators, didn't fix the problem. If I don't move some files around and leave it on C: I can sometimes get it to install or at least kick a different error.
Any thoughts, suggestions or ideas are welcome, if I missed some pertinent info let me know.
Thanks!
ADD: I selected cancel this time from the "Attempted to perform an unauthorized operation." error upon completion the final error for all Database Engine parts was: "Could not find the Database Engine startup handle." as I mentioned earlier. Here are links to an updated Detail Log: Detail and a Summary Log: Summary
Here is the relevant Summary info:
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: 0x851A0018 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=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024 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: 0x851A0018 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=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024 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: 0x851A0018 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=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024