Re: SQL Sever 2008 RC0 fail to install almost all services



Try to look in the SQL Server errorlog file. That is the file in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory.

"Gé Brander" <ge brander microsoft> wrote in message news:1B1D7137-32DA-49CE-B1D3-7176B801FAE1@xxxxxxxxxxxxxxxx
Configuration error description: Wait on the Database Engine recovery
handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20080618_231335\Detail.txt

What does this file mention? The SQL Server Error Log file, is what I mean here.

Gé Brander


"Pedro Gonçalves" <PedroGonalves@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F040789D-E6D9-4B4E-BA8B-FB82CE7F2D17@xxxxxxxxxxxxxxxx
Hi,

I've a new and clean installation of Windows 2008 Standard and I'm trying to
install SQL Server 2008 RC0 but almost all services failed to install:
databse engine, replication services, full-text search services, reporting
services, and books online(!)

I read the logs but can't understand exactly what is the problem and how to
fix it.
Can someone help me, please?

The Summary log file:
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 23:19:59
End time: 2008-06-18 23:57:51
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20080618_231335\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%4024

Machine Properties:
Machine name: MYSERVER
Machine processor count: 2
OS version: Windows Server 2008
OS service pack: Service Pack 1
OS region: Portugal
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No

Product features discovered:
Product Instance Instance ID
Feature Language Edition
Version Clustered

Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: D:\x86\setup\
Installation edition: STANDARD

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: MYDOMAIN\SQLServerServices
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: C:\Program Files\Microsoft SQL
Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL
Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL
Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL
Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: MYDOMAIN\SQLServerServices
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: MYDOMAIN\administrador
ASTEMPDIR: C:\Program Files\Microsoft SQL
Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Manual
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20080618_231335\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: True
FAILOVERCLUSTERDISKS: <empty>
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERIPADDRESSES: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FAILOVERCLUSTERROLLOWNERSHIP: 2
FEATURES:
SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,BOL,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 3
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
FTUPGRADEOPTION: Import
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: MYDOMAIN\SQLServerServices
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: D:\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSCATALOGSERVERINSTANCENAME: Unknown
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: MYDOMAIN\SQLServerServices
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
RSUPGRADEDATABASEACCOUNT:
RSUPGRADEPASSWORD: *****
RULES: <empty>
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLDOMAINGROUP: <empty>
SQLSVCACCOUNT: MYDOMAIN\SQLServerServices
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: MYDOMAIN\administrador
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: True
TCPENABLED: 1
X86: False

Configuration file: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20080618_231335\ConfigurationFile.ini

Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed

Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed

Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed

Feature: Analysis Services
Status: Passed
MSI status: Passed
Configuration status: Passed

Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed

Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed

Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed

Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed

Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed

Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed

Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed

Feature: SQL Server Books Online
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code:
Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@24
Configuration error description: Wait on the Database Engine recovery
handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20080618_231335\Detail.txt

Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:\Program Files\Microsoft SQL
Server\100\Setup
Bootstrap\Log\20080618_231335\SystemConfigurationCheck_Report.htm



.



Relevant Pages

  • Re: SQL Sever 2008 RC0 fail to install almost all services
    ... Check the SQL Server error log for potential causes. ... The SQL Server Error Log file, ...
    (microsoft.public.sqlserver.setup)
  • Error during backup verify
    ... Doing an SQL backup to a network shared drive on our file server. ... See the SQL Server error log for more details. ... I get the following info from the SQL Server Error Log: ...
    (microsoft.public.sqlserver.server)
  • Re: Help - Recovering SQL 2000 Database
    ... Can you check the SQL Server error log and post the error messages here? ... "Santosh" wrote in message ...
    (microsoft.public.sqlserver.server)
  • Re: trace 1204
    ... you can turn on trace flag 3605 so that the deadlock ... diagnostics are written to the SQL Server error log. ...
    (microsoft.public.sqlserver.programming)
  • Re: Unable to connect to SQLExpress Remotely - no matter what
    ... If there is no error in the SQL Server error log when the login fails then ... that would indicate that the connection is not getting to SQL Server. ...
    (microsoft.public.sqlserver.connect)