From: PeterSadd on
Was the installation successful? Do you see an error through Microsoft
Update? Can you provide the contents of the summary.txt log file located at
%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG?

Thanks,
Peter Saddow

"Robert Aldwinckle" <robald(a)techemail.com> wrote in message
news:OcHdqAOaHHA.4772(a)TK2MSFTNGP05.phx.gbl...
> "Dr. George" <DrGeorge(a)discussions.microsoft.com> wrote in message
> news:2FA4E25A-B32F-4CA2-96CE-C60092E6651C(a)microsoft.com...
>>I also tried to start the MSSMLBIZ service from the Microsoft SQL
>> Configuation console. The blue bar got 95% of the way across when the
>> following message suddenly appeared: "The request failed or the service
>> did
>> not respond in a timely fashion. Consult the event log or other
>> applicable
>> error log for details. I searched for and did not find a new error log
>> or
>> summary text file.
>
>
> How were you searching and for what?
>
> E.g. in your previous post perhaps you could use log
> as a find argument and then try to open directly:
>
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
>
> (space character for Setup Bootstrap is likely)
>
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlncli.msi.log
>
> (ditto)
>
> Etc.
>
> So, then I would try opening the containing subdirectory
>
> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\
>
> to see what else is in there. E.g. perhaps there would also be initial
> logs
> with more clues for the products which "do not qualify for this update"?
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>

From: Dr. George on
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build
2600)
Time : Mon Feb 12 19:28:46 2007

Machine : BERACAH
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_BERACAH_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : BERACAH
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_BERACAH_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : BERACAH
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_BERACAH_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : BERACAH
Product : MSXML 6.0 Parser (KB927977)
Product Version : 6.00.3890.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_BERACAH_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : BERACAH
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.1.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_BERACAH_SQL.log
--------------------------------------------------------------------------------

Setup succeeded with the installation, inspect the log file completely for
status on all the components.

Time : Mon Feb 12 19:36:32 2007

From: Dr. George on
MS...BIZ error log

2007-03-14 08:38:47.13 Server Microsoft SQL Server 2005 - 9.00.2047.00
(Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.0 (Build 6000: )

2007-03-14 08:38:47.15 Server (c) 2005 Microsoft Corporation.
2007-03-14 08:38:47.15 Server All rights reserved.
2007-03-14 08:38:47.15 Server Server process ID is 3176.
2007-03-14 08:38:47.15 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-14 08:38:47.15 Server This instance of SQL Server last reported
using a process ID of 2152 at 3/14/2007 12:01:35 AM (local) 3/14/2007 4:01:35
AM (UTC). This is an informational message only; no user action is required.
2007-03-14 08:38:47.15 Server Registry startup parameters:
2007-03-14 08:38:47.15 Server -d C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-14 08:38:47.15 Server -e C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-14 08:38:47.15 Server -l C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-14 08:38:47.15 Server -T 840
2007-03-14 08:38:47.15 Server -T 2324
2007-03-14 08:38:47.16 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-14 08:38:47.16 Server Detected 2 CPUs. This is an informational
message; no user action is required.
2007-03-14 08:38:48.27 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.
2007-03-14 08:38:48.55 Server Database mirroring has been enabled on
this instance of SQL Server.
2007-03-14 08:38:49.00 spid5s Starting up database 'master'.
2007-03-14 08:38:49.75 spid5s SQL Trace ID 1 was started by login "sa".
2007-03-14 08:38:49.80 spid5s Starting up database 'mssqlsystemresource'.
2007-03-14 08:38:49.83 spid5s The resource database build version is
9.00.2047. This is an informational message only. No user action is required.
2007-03-14 08:38:50.36 spid5s Server name is 'BERACAH\MSSMLBIZ'. This
is an informational message only. No user action is required.
2007-03-14 08:38:50.36 spid8s Starting up database 'model'.
2007-03-14 08:38:50.36 spid5s Starting up database 'msdb'.
2007-03-14 08:38:50.50 Server Error: 17190, Severity: 16, State: 1.
2007-03-14 08:38:50.50 Server FallBack certificate initialization
failed with error code: 4.
2007-03-14 08:38:50.52 Server Error: 26015, Severity: 16, State: 1.
2007-03-14 08:38:50.52 Server Unable to load user-specified
certificate. Because connection encryption is required, the server will not
be able to accept any connections. You should verify that the certificate is
correctly installed. See "Configuring Certificate for Use by SSL" in Books
Online.
2007-03-14 08:38:50.53 Server Error: 17182, Severity: 16, State: 1.
2007-03-14 08:38:50.53 Server TDSSNIClient initialization failed with
error 0x80092004, status code 0x80.
2007-03-14 08:38:50.53 Server Error: 17182, Severity: 16, State: 1.
2007-03-14 08:38:50.53 Server TDSSNIClient initialization failed with
error 0x80092004, status code 0x1.
2007-03-14 08:38:50.53 Server Error: 17826, Severity: 18, State: 3.
2007-03-14 08:38:50.53 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.
2007-03-14 08:38:50.53 Server Error: 17120, Severity: 16, State: 1.
2007-03-14 08:38:50.53 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.

From: Dr. George on
I have not been able to use Microsoft Outlook Contact Manager because of this
problem. It won't activate. When I try to create a new database, it says
that it is unable to do so.
From: Dr. George on
Last summary.txt

Time: 03/09/2007 22:37:29.610
KB Number: KB921896
Machine: BERACAH
OS Version: Professional (Build 6000)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level
Platform Edition
Setup Support Files ENU 9.2.3042
x86
Database Services (MSSMLBIZ) ENU SP1 2005.090.2047.00
x86 EXPRESS
SQL Server Native Client ENU 9.00.3042.00
x86
MSXML 6.0 Parser ENU 6.00.3890.0
x86
Microsoft SQL Server VSS Writer ENU 9.00.3042.00
x86

**********************************************************************************
Products Disqualified & Reason
Product Reason
Database Services (MSSMLBIZ) The edition of product instance
MSSMLBIZ does not qualify for this update.

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name
PID

**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Database Services (MSSMLBIZ)
Product Version (Previous): 2047
Product Version (Final) :
Status : NA
Log File :
SQL Express Features :
Error Description : The edition of product instance MSSMLBIZ does
not qualify for this update.
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : MSXML 6.0 Parser
Product Version (Previous): 3890
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 3042
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------

**********************************************************************************
Summary
Success
Exit Code Returned: 0