June 18, 2008 at 12:37 pm
The install error log contains the following:
[font="Courier New"]Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2008-06-18 08:54:08
End time: 2008-06-18 09:59:06
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080618_084912\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1442.32%26EvtType%3dMicrosoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart%40Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException%401306%4023[/font]
The Detail Log pointed to in the Summary contains the following:
[font="Courier New"]Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@23
[font="Comic Sans MS"]Configuration error description: Could not find the Database Engine startup handle.[/font]
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080618_084912\Detail.txt[/font]
The ERRORLOG file in the default dump folder contains the following problem entries - "problem" because there's NO e: drive on the machine!
[font="Courier New"]2008-06-18 10:19:40.61 spid10s Starting up database 'model'.
2008-06-18 10:19:40.61 spid10s Error: 17204, Severity: 16, State: 1.
2008-06-18 10:19:40.61 spid10s FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2008-06-18 10:19:40.62 spid10s Error: 5120, Severity: 16, State: 101.
2008-06-18 10:19:40.62 spid10s Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2008-06-18 10:19:40.65 spid10s Error: 17207, Severity: 16, State: 1.
2008-06-18 10:19:40.65 [/font]spid10s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2008-06-18 10:19:40.67 spid10s File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\objfre\i386\modellog.ldf" may be incorrect.
2008-06-18 10:19:40.67 spid10s Error: 945, Severity: 14, State: 2.
2008-06-18 10:19:40.67 spid10s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.[/font]
Clues, anyone, on how to stop the installer referencing invalid drive letters, or any other workaround?
The Detail Log also has these lines:
[font="Courier New"]2008-06-18 09:54:53 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete' to be created
2008-06-18 09:57:55 SQLEngine: --SqlServerServiceSCM: Wait for creation of event handle 'Global\sqlserverRecComplete' has timed out
2008-06-18 09:57:55 SQLEngine: Copying 'C:\DataFiles\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG' to 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080618_084912\SQLServer_ERRORLOG_2008-06-18T09.57.55.txt' ...
2008-06-18 09:57:55 Slp: Sco: Attempting to set file full path to 'C:\DataFiles\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'
2008-06-18 09:57:55 Slp: Sco: Attempting to normalize directory path 'C:\DataFiles\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'
2008-06-18 09:57:55 Slp: Sco: Attempting to check if file 'C:\DataFiles\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG' exists
2008-06-18 09:57:55 SQLEngine: Could not copy non-existant SQL Server Error Log: C:\DataFiles\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
2008-06-18 09:57:55 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2008-06-18 09:57:55 Slp: Could not find the Database Engine startup handle.
2008-06-18 09:57:55 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2008-06-18 09:57:55 Slp: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException: Could not find the Database Engine startup handle.
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerStartup.StartSQLServerForInstall(String sqlCollation, String masterFullPath, String instanceName, Boolean isConfiguringTemplateDBs, Boolean useSharedMemoryOnly)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2008-06-18 09:57:55 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
2008-06-18 09:57:55 Slp: Exception: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException.
2008-06-18 09:57:55 Slp: Source: Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.
2008-06-18 09:57:55 Slp: Message: Could not find the Database Engine startup handle..
2008-06-18 09:57:57 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080618_084912\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2008-06-18 09:57:57 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080618_084912\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2008-06-18 09:57:57 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20080618_084912\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2008-06-18 09:58:13 Slp: Could not find the Database Engine startup handle.
2008-06-18 09:58:14 Slp: Watson bucket for exception based failure has been created
2008-06-18 09:58:27 Slp: Completed Action: SqlEngineDBStartConfigAction_install_configrc_Cpu32, returned False[/font]
I tried a Repair, but was rejected because only successful instals can be repaired - duh! Apparently one must uninstall the Database Service and try again... I'm hesitant as there's no apparent reason for the "handle" going AWOL... and what's to stop it trying the e: drive again...?
The SQL Server Service account existed but the Admin hadn't given it privileges before the install. I added it to the Local Admin group AFTER the problem - maybe that's my issue...?
It is "beta" but this seems a little too bad for an RC0 release...
June 18, 2008 at 1:24 pm
Well, if the Admin HAD done their job, I'd not have to do mine twice!
Make sure you read the Service Accounts permissions required stuff and REQUIRE THAT IT BE DONE before you start the install...
Nice job my Microsoft on the Installer, though - the uninstall-reinstall went perfectly.
August 27, 2008 at 1:34 pm
No body knows how to fix this
March 30, 2009 at 6:05 am
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply