Diana Moldovan


  I tried to apply the SP2 on a newly installed SQL Server 2005 Developer edition. The installation failed and the MSSQLSERVER service does not start. I work on 32 bits Windows Server 2003 Standard Edition SP1 with all the patches up to date. I downloaded SQL Server 2005 SP2 on March 15, 2007.

Here are the error messages from 2 of the log files:

Summary.txt:

Product                   : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number              : 29534
Error Description         : MSP Error: 29534  Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (-2146885628) Cannot find object or property.

SQL9_Hotfix_KB921896_sqlrun_sql.msp.log:

Doing Action: ComponentUpgradeInstall
PerfTime Start: ComponentUpgradeInstall : Sun Mar 18 17:37:33 2007
<Func Name='ComponentUpgradeInstall'>
<Func Name='ComponentUpgrade'>
Failed to add file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG' to datastore in AddFileToFailureHandling
Service MSSQLSERVER with parameters '-r' is being started at Sun Mar 18 17:37:33 2007
Failed to start service MSSQLSERVER. Error code 2148081668
Service failed unexpectedly (2148081668)
        Error Code: -2146885628
Windows Error Text: Cannot find object or property.
  Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Wed Jun 14 16:29:04 2006
     Function Name: sqls::Service::Start
Source Line Number: 301

And below you can see the content of the SQL error log:

2007-03-18 19:46:11.51 Server      Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
 Feb  9 2007 22:47:07
 Copyright (c) 1988-2005 Microsoft Corporation
 Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2007-03-18 19:46:11.51 Server      (c) 2005 Microsoft Corporation.
2007-03-18 19:46:11.51 Server      All rights reserved.
2007-03-18 19:46:11.53 Server      Server process ID is 796.
2007-03-18 19:46:11.53 Server      Authentication mode is WINDOWS-ONLY.
2007-03-18 19:46:11.53 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-18 19:46:11.53 Server      This instance of SQL Server last reported using a process ID of 712 at 3/18/2007 5:39:48 PM (local) 3/18/2007 3:39:48 PM (UTC). This is an informational message only; no user action is required.
2007-03-18 19:46:11.53 Server      Registry startup parameters:
2007-03-18 19:46:11.53 Server        -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-18 19:46:11.53 Server        -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-18 19:46:11.53 Server        -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-18 19:46:11.56 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-03-18 19:46:11.56 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2007-03-18 19:46:11.87 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-18 19:46:11.98 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-03-18 19:46:14.06 Server      Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-03-18 19:46:14.06 Server      Database mirroring has been enabled on this instance of SQL Server.
2007-03-18 19:46:14.07 spid5s      Starting up database 'master'.
2007-03-18 19:46:14.15 spid5s      1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2007-03-18 19:46:14.17 spid5s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2007-03-18 19:46:14.17 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2007-03-18 19:46:14.37 spid5s      SQL Trace ID 1 was started by login "sa".
2007-03-18 19:46:14.42 spid5s      Starting up database 'mssqlsystemresource'.
2007-03-18 19:46:14.50 spid5s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2007-03-18 19:46:14.89 spid5s      Server name is 'YODA'. This is an informational message only. No user action is required.
2007-03-18 19:46:14.89 spid9s      Starting up database 'model'.
2007-03-18 19:46:15.06 spid9s      Clearing tempdb database.
2007-03-18 19:46:15.67 spid9s      Starting up database 'tempdb'.
2007-03-18 19:46:15.79 spid12s     The Service Broker protocol transport is disabled or not configured.
2007-03-18 19:46:15.79 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2007-03-18 19:46:15.82 spid12s     Service Broker manager has started.
2007-03-18 19:46:21.62 Server      The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid.
2007-03-18 19:46:21.62 Server      Error: 17190, Severity: 16, State: 1.
2007-03-18 19:46:21.62 Server      FallBack certificate initialization failed with error code: 1.
2007-03-18 19:46:21.62 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-03-18 19:46:21.64 Server      Error: 17182, Severity: 16, State: 1.
2007-03-18 19:46:21.64 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
2007-03-18 19:46:21.64 Server      Error: 17182, Severity: 16, State: 1.
2007-03-18 19:46:21.64 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1.
2007-03-18 19:46:21.64 Server      Error: 17826, Severity: 18, State: 3.
2007-03-18 19:46:21.64 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-18 19:46:21.64 Server      Error: 17120, Severity: 16, State: 1.
2007-03-18 19:46:21.64 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.

Any advice

 


 

 

 




Re: SP2 failed only on the Database engine; the MSSQLSERVER service cannot start

Samuel Lester - MSFT


Are you able to start the services manually through Service Manager

Thanks,
Sam Lester (MSFT)







Re: SP2 failed only on the Database engine; the MSSQLSERVER service cannot start

Peter Saddow MSFT

If you are using a non-administrator account, you should use SQL Server Configuration Manager to set the account and start the service. By using SQL Server Configuration Manager, it ensure the account specificed has the required permissions.

Thanks,

Peter Saddow







Re: SP2 failed only on the Database engine; the MSSQLSERVER service cannot start

Diana Moldovan

Thank you for your help.

During installaion, I specified that all the SQL services should use a domain account with no privileges on the local machine. But I am a local admin and the setup program granted to various SQL$ groups the appropriate privileges (i.e. "logon as a service", "log on a as a batch job", etc...). This account became a member of all these groups (for example SQLServer2005MSSQLUser$MyComputerName$MSSQLSERVER, etc...). SQL Server works fine on my machine after a clean install with or without SP1 (in fact it ran perfectly in both these combinations) I obtain the errors only after trying to apply the SP2.

I am using a domain account with no priviledges because this was a requirement in order to perform replication in SQL2000 and I suppose that this is still a requirement for SQL2005.





Re: SP2 failed only on the Database engine; the MSSQLSERVER service cannot start

Tjomme Vergauwen

Hello all,

I just installed SP2 (KB921896) and I have the same problem. After applying KB933508 the problem remains.

System worked perfect wit and without SP1.

Uninstall of SP2 is not possible...

Anyone any ideas

Regards,

Tjomme Vergauwen





Re: SP2 failed only on the Database engine; the MSSQLSERVER service cannot start

R Reid

I just "solved" (well, hacked around) this with a similar error installing SP2 on Enterprise on x64. Same error messages.

It would no longer start the server using the domain account I had set up for that purpose after I started the SP2 upgrade.

It's when the SP2 process is unable to restart the engine that it fails. I determined that I also could no longer start the engine with that account.

I set the MSSQLSERVER service account back to "LOCAL SYSTEM", and found that then SQL Server would start. I reran the upgrade and it worked.

The reason I thought to do this is because that's how I had to do the original install. Then I went back, hand added the domain account to the local groups that LOCAL SYSTEM had been added to, and changed the service account through the SQL Server config screen. Now I'm going to go see what happens when I try and turn this - once more - back the the domain account I use.

This isn't a solution, but it worked for me. I'd love to know what's reallty at issue.

One more thing - I logged on as local administrator to do this. Most SQL Server 2005 install issues seem to work better that way, not sure how necessary it is.





Re: SP2 failed only on the Database engine; the MSSQLSERVER service cannot start

Nick E

I am also seeing the same problem on my windows 2003 server with SP2 installed. Would love to have a solution. I have tried the install like 5 times so far and it always fails with the same error. I am going to try a different account and see if that works.



Re: SP2 failed only on the Database engine; the MSSQLSERVER service cannot start

Nick E

Tried with local account and it still fails to install, here is the excerpt from the install log. Any suggestions are appreciated.

Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Thu May 24 17:31:21 2007
Service MSSQL$BKUPEXEC with parameters '-m SqlSetup -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Thu May 24 17:31:21 2007
Service failed unexpectedly (2148081668)
Error Code: -2146885628
Windows Error Text: Cannot find object or property.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Wed Jun 14 16:29:04 2006
Function Name: sqls:Tongue Tiedervice:Tongue Tiedtart
Source Line Number: 301

---- Context -----------------------------------------------


Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$BKUPEXEC

Error Code: -2146885628
MSI (s) (78!78) [17:31:27:937]: Product: Microsoft SQL Server 2005 Express Edition -- Error 29503. 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 29503. 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.
.
<Failure Type='Fatal' Error='-2146885628'>
<EndFunc Name='LaunchFunction' Return='-2146885628' GetLastError='0'>





Re: SP2 failed only on the Database engine; the MSSQLSERVER service cannot start

Nick E

Found the problem. I have SSL enabled for IIS on my server and when installing SQL Express 2005 SP2 integrated, I get the following failures in my ERRORLOG file.

2007-05-24 18:24:30.74 spid4s Starting up database 'msdb'.
2007-05-24 18:24:30.70 Server Error: 17190, Severity: 16, State: 1.
2007-05-24 18:24:30.70 Server FallBack certificate initialization failed with error code: 1.
2007-05-24 18:24:30.78 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-05-24 18:24:30.79 Server Error: 17182, Severity: 16, State: 1.
2007-05-24 18:24:30.79 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
2007-05-24 18:24:30.79 Server Error: 17182, Severity: 16, State: 1.
2007-05-24 18:24:30.79 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1.
2007-05-24 18:24:30.79 Server Error: 17826, Severity: 18, State: 3.
2007-05-24 18:24:30.79 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-05-24 18:24:30.79 Server Error: 17120, Severity: 16, State: 1.
2007-05-24 18:24:30.79 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.

I performed an interactive install and specified not to start the SQL server service during the install, and it completed successfully. Then I was able to start the service fine. Not the perfect solution, but at least its installed now. Now to see if I can get it installed using the SQL Express command line.