From: genew@ocis.net   
      
   On Wed, 13 Oct 2010 23:42:04 +0200, Erland Sommarskog   
    wrote:   
      
   >Gene Wirchenko (genew@ocis.net) writes:   
   >> Yesterday, I tried to install SQL Express for the first time on   
   >> this new installation. It failed with   
   >> Wait on the Database Engine recovery handle failed.   
   >> This is worse than before. At least I was able to install it a few   
   >> times.   
   >   
   >If it comes this far, there is an error log in   
   >C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\LOG\ERRORLOG   
   >   
   >Setup tries to start SQL Server, but something prevents SQL Server from   
   >starting successfully. Please post this log here.   
      
    I just finished trying yet another install. It failed again. I   
   have saved all of the files of the installation so if you need another   
   log file, I have it. I do not have the registry since I restored to a   
   pre-SQL Express ever installed partition copy.   
      
    Here is the file:   
      
   ***** Start of Log *****   
   2010-10-14 13:20:15.48 Server Microsoft SQL Server 2008 (RTM) -   
   10.0.1600.22 (Intel X86)   
    Jul 9 2008 14:43:34   
    Copyright (c) 1988-2008 Microsoft Corporation   
    Express Edition with Advanced Services on Windows NT 5.1    
   (Build 2600: Service Pack 3)   
      
   2010-10-14 13:20:15.51 Server (c) 2005 Microsoft Corporation.   
   2010-10-14 13:20:15.53 Server All rights reserved.   
   2010-10-14 13:20:15.53 Server Server process ID is 464.   
   2010-10-14 13:20:15.53 Server Authentication mode is MIXED.   
   2010-10-14 13:20:15.53 Server Logging SQL Server messages in file   
   'c:\Program Files\Microsoft SQL   
   Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.   
   2010-10-14 13:20:15.54 Server Registry startup parameters:   
    -d c:\Program Files\Microsoft SQL   
   Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf   
    -e c:\Program Files\Microsoft SQL   
   Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG   
    -l c:\Program Files\Microsoft SQL   
   Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf   
   2010-10-14 13:20:15.54 Server Command Line Startup Parameters:   
    -m SqlSetup   
    -f   
    -Q   
    -q Latin1_General_CI_AS   
    -T 4022   
    -T 4010   
    -T 3659   
    -T 3610   
    -d c:\Program Files\Microsoft SQL   
   Server\MSSQL10.SQLEXPRESS\MSSQL\Template Data\master.mdf   
    -l c:\Program Files\Microsoft SQL   
   Server\MSSQL10.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf   
   2010-10-14 13:20:15.65 Server Warning: The server instance was   
   started using minimal configuration startup option (-f). Starting an   
   instance of SQL Server with minimal configuration places the server in   
   single-user mode automatically. After the server has been started   
   with minimal configuration, you should change the appropriate server   
   option value or values, stop, and then restart the server.   
   2010-10-14 13:20:15.65 Server SQL Server is starting at normal   
   priority base (=7). This is an informational message only. No user   
   action is required.   
   2010-10-14 13:20:15.65 Server Detected 2 CPUs. This is an   
   informational message; no user action is required.   
   2010-10-14 13:20:17.32 Server Perfmon counters for resource   
   governor pools and groups failed to initialize and are disabled.   
   2010-10-14 13:20:17.43 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.   
   2010-10-14 13:20:18.60 Server Node configuration: node 0: CPU   
   mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a   
   description of the NUMA configuration for this computer. This is an   
   informational message only. No user action is required.   
   2010-10-14 13:20:18.87 Server Support for distributed   
   transactions was not enabled for this instance of the Database Engine   
   because it was started using the minimal configuration option. This is   
   an informational message only. No user action is required.   
   2010-10-14 13:20:18.99 spid7s Warning ******************   
   2010-10-14 13:20:19.01 spid7s SQL Server started in single-user   
   mode. This an informational message only. No user action is required.   
   2010-10-14 13:20:19.26 spid7s Starting up database 'master'.   
   2010-10-14 13:20:19.74 spid7s Recovery is writing a checkpoint in   
   database 'master' (1). This is an informational message only. No user   
   action is required.   
   2010-10-14 13:20:20.31 spid7s FILESTREAM: effective level = 0,   
   configured level = 0, file system access share name = 'SQLEXPRESS'.   
   2010-10-14 13:20:20.34 spid7s Server started with '-f' option.   
   Auditing will not be started. This is an informational message only;   
   no user action is required.   
   2010-10-14 13:20:20.37 spid7s Starting up database   
   'mssqlsystemresource'.   
   2010-10-14 13:20:20.42 spid7s The resource database build version   
   is 10.00.1600. This is an informational message only. No user action   
   is required.   
   2010-10-14 13:20:22.87 spid8s Starting up database 'model'.   
   2010-10-14 13:20:22.90 spid7s Server name is 'LOOP\SQLEXPRESS'.   
   This is an informational message only. No user action is required.   
   2010-10-14 13:20:23.74 spid8s Clearing tempdb database.   
   2010-10-14 13:20:24.31 Server Error: 17190, Severity: 16, State:   
   1.   
   2010-10-14 13:20:24.31 Server FallBack certificate initialization   
   failed with error code: 1.   
   2010-10-14 13:20:24.37 Server Unable to initialize SSL encryption   
   because a valid certificate could not be found, and it is not possible   
   to create a self-signed certificate.   
   2010-10-14 13:20:24.42 Server Error: 17182, Severity: 16, State:   
   1.   
   2010-10-14 13:20:24.42 Server TDSSNIClient initialization failed   
   with error 0x80092004, status code 0x80. Reason: Unable to initialize   
   SSL support. Cannot find object or property.   
      
   2010-10-14 13:20:24.42 Server Error: 17182, Severity: 16, State:   
   1.   
   2010-10-14 13:20:24.42 Server 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.   
      
   2010-10-14 13:20:24.42 Server Error: 17826, Severity: 18, State:   
   3.   
   2010-10-14 13:20:24.42 Server 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.   
   2010-10-14 13:20:24.42 Server Error: 17120, Severity: 16, State:   
   1.   
   2010-10-14 13:20:24.42 Server SQL Server could not spawn FRunCM   
   thread. Check the SQL Server error log and the Windows event logs for   
   information about possible related problems.   
   ***** End of Log *****   
      
    I really would like to see this thing work.   
      
   Sincerely,   
      
   Gene Wirchenko   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|