Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / December 2007

Tip: Looking for answers? Try searching our database.

SQL Server 2005 SP2 update failed

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
finntiger - 27 Dec 2007 17:06 GMT
Hello,

as looking into numerous forum threads I have a common problem with no
common solution.

I'm running Win XP professional SP2 with MS Office 2007 including Business
Manager (if that is of any relevance...).
Windows Update automatically downloads "Microsoft SQL Server 2005 Express
Edition Service Pack 2 (KB921896)", but obviously fails to install as it is
downloaded again and again.
Trying to solve the problem I have manually downloaded the corresponding
file SQLEXPR.EXE from the Microsoft website for manual update. But with the
same result: failure. I have tested and checked most suggestions from forum
threads, but nothing seems to correspond with my problem (and I don't even
know exactly what the SQL server is for...).

Thank you for your support!

Below some log files that may be relevant:

summary.txt:

Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version      : Microsoft Windows XP Professional Service Pack 2 (Build
2600)
Time            : Thu Dec 27 17:48:59 2007

Machine         : MN-ARTIOS
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine         : MN-ARTIOS
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine         : MN-ARTIOS
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine         : MN-ARTIOS
Product         : MSXML 6.0 Parser (KB933579)
Product Version : 6.10.1200.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_MSXML6_1.log
--------------------------------------------------------------------------------
Machine         : MN-ARTIOS
Product         : SQL Server Database Services
Error           : The SQL Server service failed to start. For more
information, see the SQL Server Books Online topics, "How to: View SQL Server
2005 Setup Log Files" and "Starting SQL Server Manually.
--------------------------------------------------------------------------------
Machine         : MN-ARTIOS
Product         : Microsoft SQL Server 2005 Express Edition
Product Version : 9.2.3042.00
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SQL.log
Last Action     : InstallFinalize
Error String    : The SQL Server service failed to start. For more
information, see the SQL Server Books Online topics, "How to: View SQL Server
2005 Setup Log Files" and "Starting SQL Server Manually."
The error is  (-2146885628) Cannot find object or property.
Error Number    : 29503
--------------------------------------------------------------------------------

SQL Server Setup failed. For more information, review the Setup log file in
%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Time            : Thu Dec 27 17:52:20 2007

List of log files:
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_Core(Local).log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SQLSupport_1.log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SQLNCLI_1.log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SqlWriter_1.log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_MSXML6_1.log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SQL.log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_Datastore.xml
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_.NET Framework 2.0.log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_Support.log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_Core.log
    C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SCC.log
    C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_WI.log

ERRORLOG (in MSSQL.1\MSSQL\LOG) shows also 2 errors (15466 and 17190):
2007-12-27 17:52:09.28 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 5.1 (Build 2600: Service Pack 2)

2007-12-27 17:52:09.29 Server      (c) 2005 Microsoft Corporation.
2007-12-27 17:52:09.31 Server      All rights reserved.
2007-12-27 17:52:09.31 Server      Server process ID is 7104.
2007-12-27 17:52:09.31 Server      Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-12-27 17:52:09.31 Server      This instance of SQL Server last reported
using a process ID of 840 at 12/27/2007 5:51:36 PM (local) 12/27/2007 4:51:36
PM (UTC). This is an informational message only; no user action is required.
2007-12-27 17:52:09.31 Server      Registry startup parameters:
2007-12-27 17:52:09.32 Server          -T 840
2007-12-27 17:52:09.32 Server          -T 2324
2007-12-27 17:52:09.32 Server          -l C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-12-27 17:52:09.32 Server          -e C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-12-27 17:52:09.32 Server          -d C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-12-27 17:52:09.34 Server      SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-12-27 17:52:09.34 Server      Detected 2 CPUs. This is an informational
message; no user action is required.
2007-12-27 17:52:10.28 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-12-27 17:52:10.79 Server      Database mirroring has been enabled on
this instance of SQL Server.
2007-12-27 17:52:10.93 spid5s      Starting up database 'master'.
2007-12-27 17:52:11.15 spid5s      1 transactions rolled forward in database
'master' (1). This is an informational message only. No user action is
required.
2007-12-27 17:52:11.28 spid5s      0 transactions rolled back in database
'master' (1). This is an informational message only. No user action is
required.
2007-12-27 17:52:11.28 spid5s      Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-12-27 17:52:11.43 spid5s      SQL Trace ID 1 was started by login "sa".
2007-12-27 17:52:11.48 spid5s      Starting up database 'mssqlsystemresource'.
2007-12-27 17:52:11.49 spid5s      The resource database build version is
9.00.2047. This is an informational message only. No user action is required.
2007-12-27 17:52:11.71 spid5s      Error: 15466, Severity: 16, State: 1.
2007-12-27 17:52:11.71 spid5s      An error occurred during decryption.
2007-12-27 17:52:11.87 spid8s      Starting up database 'model'.
2007-12-27 17:52:11.89 spid5s      Server name is 'MN-ARTIOS\MSSMLBIZ'. This
is an informational message only. No user action is required.
2007-12-27 17:52:11.90 spid5s      Starting up database 'msdb'.
2007-12-27 17:52:11.96 Server      Error: 17190, Severity: 16, State: 1.
2007-12-27 17:52:11.96 Server      FallBack certificate initialization
failed with error code: 1.
2007-12-27 17:52:11.98 Server      Warning:Encryption is not available,
could not find a valid certificate to load.
2007-12-27 17:52:11.98 Server      Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSMLBIZ ].
2007-12-27 17:52:11.98 Server      Server local connection provider is ready
to accept connection on [ \\.\pipe\MSSQL$MSSMLBIZ\sql\query ].
2007-12-27 17:52:11.99 Server      Dedicated administrator connection
support was not started because it is not available on this edition of SQL
Server. This is an informational message only. No user action is required.
2007-12-27 17:52:12.04 Server      SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-12-27 17:52:12.45 spid8s      Clearing tempdb database.
2007-12-27 17:52:12.84 spid8s      Starting up database 'tempdb'.
2007-12-27 17:52:13.62 spid5s      Recovery is complete. This is an
informational message only. No user action is required.
2007-12-27 17:52:13.67 spid11s     The Service Broker protocol transport is
disabled or not configured.
2007-12-27 17:52:13.67 spid11s     The Database Mirroring protocol transport
is disabled or not configured.
2007-12-27 17:52:13.76 spid11s     Service Broker manager has started.
John Bell - 28 Dec 2007 12:12 GMT
Hi

Have you changed the service accounts at all?

Searching google shows "Error: 15466" occuring when the service master key
is corrupted or the service account has changed. e.g
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1741008&SiteID=1

Do you get any messages when starting SQL Server from the services applet in
the admin tools?

My guess is that someone has set up replication and that is why SQL Express
is there.

John

> Hello,
>
[quoted text clipped - 180 lines]
> is disabled or not configured.
> 2007-12-27 17:52:13.76 spid11s     Service Broker manager has started.
finntiger - 28 Dec 2007 19:34 GMT
Hi,

> Have you changed the service accounts at all?
No (or not willingly), my system is only a couple of months old and no
account changes have been made nor any settings or databases imported
(besides Outlook pst-files).

> Do you get any messages when starting SQL Server from the services applet in
> the admin tools?
Starting SQL server from where??? As I said, I don't even know what it is
good for, the only reason I can imagine is the Business Contac Manager using
it somehow (which I haven't started really using yet, but its installed).
Does it use it?

> My guess is that someone has set up replication and that is why SQL Express
> is there.
No one else but me uses or configures this computer...

What will happen if I uninstall the SQL server 2005? Problem solved or
unstable system and even more problems?

Thanks for help,
Martti

> Hi
>
[quoted text clipped - 196 lines]
> > is disabled or not configured.
> > 2007-12-27 17:52:13.76 spid11s     Service Broker manager has started.
John Bell - 28 Dec 2007 23:27 GMT
Hi Martti

You can start the service from the services applet on your administration
menu see see http://msdn2.microsoft.com/en-us/library/ms191193.aspx . You can
check service accounts using Configuration Manager which should be under your
SQL 2005 programs on the start menu (you can also start the service from
this!)

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1366604&SiteID=1 may
help The certificate may be to do with an invalid certificate for SSL
encryption check that it encryption is not set in Configuration Manager see
http://msdn2.microsoft.com/en-us/library/ms191192.aspx

With a named instance MSSMLBIZ it is most likely Business Contact Manager
that installed SQL Express, and I would expect it to provide core
funtionality.

John

> Hi,
>
[quoted text clipped - 220 lines]
> > > is disabled or not configured.
> > > 2007-12-27 17:52:13.76 spid11s     Service Broker manager has started.
finntiger - 29 Dec 2007 01:53 GMT
Hi John,

I got one step further. With SQL server 2005 SP1 running, I could start and
stop the instance MSSMLBIZ as a Network service. No error messages.

Following the suggestion in one of the threads, I switched the instance to
LOCAL SYSTEM. Now I could update to SP2. Good news so far.

When now trying to switch the instance back to NETWORK SERVICE, it failed
starting with the error messages "Cannot find object or property.
[0x80092004]" or a message stating "The request failed or the service did not
respond in a timely fashion. Consult the event log or other applicable error
logs for details."

Below the ERRORLOG file content.

When investigating into these error messages, it is suggested that a
certificate might be missing, but where could I know from which authority and
the registry location mentioned in the articles for Windows server 2003 and
Windows 2000 does not exist for me (WinXP).

Any ideas?
Martti

ERRORLOG:
2007-12-29 02:43:23.07 Server      Microsoft SQL Server 2005 - 9.00.3042.00
(Intel X86)
    Feb  9 2007 22:47:07
    Copyright (c) 1988-2005 Microsoft Corporation
    Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2007-12-29 02:43:23.07 Server      (c) 2005 Microsoft Corporation.
2007-12-29 02:43:23.07 Server      All rights reserved.
2007-12-29 02:43:23.07 Server      Server process ID is 6812.
2007-12-29 02:43:23.07 Server      Authentication mode is WINDOWS-ONLY.
2007-12-29 02:43:23.07 Server      Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-12-29 02:43:23.07 Server      This instance of SQL Server last reported
using a process ID of 7320 at 12/29/2007 2:33:07 AM (local) 12/29/2007
1:33:07 AM (UTC). This is an informational message only; no user action is
required.
2007-12-29 02:43:23.07 Server      Registry startup parameters:
2007-12-29 02:43:23.07 Server          -T 840
2007-12-29 02:43:23.07 Server          -T 2324
2007-12-29 02:43:23.07 Server          -l C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-12-29 02:43:23.07 Server          -e C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-12-29 02:43:23.07 Server          -d C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-12-29 02:43:23.10 Server      SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-12-29 02:43:23.10 Server      Detected 2 CPUs. This is an informational
message; no user action is required.
2007-12-29 02:43:23.10 Server      Error: 8319, Severity: 16, State: 1.
2007-12-29 02:43:23.10 Server      Windows kernel object
'Global\SQL_90_MEMOBJ_MSSMLBIZ_0' already exists. It's not owned by the SQL
Server service account. SQL Server performance counters are disabled.
2007-12-29 02:43:23.12 Server      Error: 3409, Severity: 16, State: 1.
2007-12-29 02:43:23.12 Server      Performance counter shared memory setup
failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that
the instance login account has correct registry permissions.
2007-12-29 02:43:23.62 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-12-29 02:43:23.64 Server      The time stamp counter of CPU on
scheduler id 1 is not synchronized with other CPUs.
2007-12-29 02:43:23.64 Server      Database mirroring has been enabled on
this instance of SQL Server.
2007-12-29 02:43:23.64 spid5s      Starting up database 'master'.
2007-12-29 02:43:23.79 spid5s      1 transactions rolled forward in database
'master' (1). This is an informational message only. No user action is
required.
2007-12-29 02:43:23.90 spid5s      0 transactions rolled back in database
'master' (1). This is an informational message only. No user action is
required.
2007-12-29 02:43:23.90 spid5s      Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-12-29 02:43:23.93 spid5s      SQL Trace ID 1 was started by login "sa".
2007-12-29 02:43:23.95 spid5s      Starting up database 'mssqlsystemresource'.
2007-12-29 02:43:23.98 spid5s      The resource database build version is
9.00.3042. This is an informational message only. No user action is required.
2007-12-29 02:43:24.31 spid5s      Server name is 'MN-ARTIOS\MSSMLBIZ'. This
is an informational message only. No user action is required.
2007-12-29 02:43:24.31 spid7s      Starting up database 'model'.
2007-12-29 02:43:24.31 spid5s      Starting up database 'msdb'.
2007-12-29 02:43:24.35 Server      Error: 17190, Severity: 16, State: 1.
2007-12-29 02:43:24.35 Server      FallBack certificate initialization
failed with error code: 1.
2007-12-29 02:43:24.35 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.
2007-12-29 02:43:24.35 Server      Error: 17182, Severity: 16, State: 1.
2007-12-29 02:43:24.35 Server      TDSSNIClient initialization failed with
error 0x80092004, status code 0x80.
2007-12-29 02:43:24.35 Server      Error: 17182, Severity: 16, State: 1.
2007-12-29 02:43:24.35 Server      TDSSNIClient initialization failed with
error 0x80092004, status code 0x1.
2007-12-29 02:43:24.39 Server      Error: 17826, Severity: 18, State: 3.
2007-12-29 02:43:24.39 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-12-29 02:43:24.39 Server      Error: 17120, Severity: 16, State: 1.
2007-12-29 02:43:24.39 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.

> Hi Martti
>
[quoted text clipped - 239 lines]
> > > > is disabled or not configured.
> > > > 2007-12-27 17:52:13.76 spid11s     Service Broker manager has started.
John Bell - 29 Dec 2007 11:49 GMT
Hi Martti

It is possibly the privileges for the certificate have not been granted for
the certificate. Did you check configuration manager to see if you are using
SSL? Have you conneced to the instance using SQLCMD and see if you can, can
you access the databases?

You should only need to change the service account from local system if you
require to do anything that local system is not privileged to do.
http://msdn2.microsoft.com/en-us/library/ms143170.aspx lists possible options
for the service account and Network Service is not recommended if you can use
a User Account or Local System do so.

Your current error message looks again like permissions the only thing I can
find is at http://tinyurl.com/2279va which indicates that you need to give
the service account access to the registry key although this is not a
Microsoft Fix.

John

> Hi John,
>
[quoted text clipped - 277 lines]
> > > > >     Copyright (c) 1988-2005 Microsoft Corporation
> > > > >     Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
finntiger - 29 Dec 2007 22:36 GMT
Hi John,

I checked the privileges and they seem to be ok, the instance has read
permission.

I couldn't find out how to check if I'm using SSL. I can only guess that
yes, as the ERRORLOG says "...unable to initialize SSL encryption...".

I tried to connect with the sqlcmd command but failure again.

Well, in the end I'll let the service run as Local System and if later I
encounter problems I can still spend another three nights fixing registries
and other stuff I don't really understand.

Thanks for your help!
Martti

> Hi Martti
>
[quoted text clipped - 277 lines]
> > > > > >     C:\Program Files\Microsoft SQL Server\90\Setup
> > > > > > Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SQL.log
John Bell - 30 Dec 2007 14:20 GMT
Hi

You can check SSL encryption in the protocols section of configuration
manager. Check http://technet.microsoft.com/en-us/library/ms189067.aspx for
more detail.

John

> Hi John,
>
[quoted text clipped - 380 lines]
>> > > > > > C:\Program Files\Microsoft SQL Server\90\Setup
>> > > > > > Bootstrap\LOG\Files\SQLSetup0007_MN-ARTIOS_SQL.log
finntiger - 30 Dec 2007 20:12 GMT
Hi again,

well, I had found the article about encryption as well, but in my list of
protocols only "shared memory" is enabled, all other protocols "named pipes",
"TCP/IP" and "VIA" are disabled. In neither of the protocols there is a
"certificate" tab, nor have I found any other information or choice regarding
encryption there. No "flag" tabs neither...

Whats wrong???
Martti

> Hi
>
[quoted text clipped - 274 lines]
> >> > > > >
> >> > > > > > Hello,
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.