SP2 Failed Only On The Database Engine; The MSSQLSERVER Service Cannot Start
Mar 18, 2007
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 FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_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 FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG' 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: sqlsetuplibservice.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 FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'.
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 FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf
2007-03-18 19:46:11.53 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
2007-03-18 19:46:11.53 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.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.
I am not able to start the sql server 2005 database engine services...
Sql server 2005 server is installed in one machine(SERVER) and we have 10 client machine connecting to the server
When i try to start the service from the Service.msc in the SERVER i am getting the following error
===================================
Cannot connect to KEYSKILL.
===================================
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
I have installed sqlserver 2005 using the standard msdn universal installation discs on my laptop running vista business.
The mssqlserver service will not start automatically as the setup configures it and I cannot start the service manually because I get the 'Access Denied' error message
I am logged on the the computer with adminstration privileges
The operation system is windows xp, and before i installed the SQL SERVER2005 the SQL SERVER2000 had installed. the course of installing the SQL SERVER2005 has no error at all. but i can not find the Database Engine under MSSQLSERVER from surface area configuration ============== thank you in advance for any help
we had activity last night we need to truncate Transactional Logs we pressed Restart button to initiate service , but it stopped successfully and failed to start the SQL Server service.We did not find anything find anything unusual in log file. Please confirm are we facing any bug or needing any fixes to installed on the server.Windows Server 2008 R2 Standard Service Pack 1Â ( 64bit)
I am getting the following errors in the NT Event Log on a system using SQL 6.5 SP3 on an NT 4.0 SP3 machine (with selected hotfixes). Perhaps someone here will have experienced this problem. Any suggestions are appreciated.
Service Control Manager - Event ID 7009 Timeout (120000 milliseconds) waiting for service to connect.
Service Control Manager - Event ID 7000 The SQLExecutive service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Thanks,
Matt Combs Product Development Engineer Eaton Corporation - TISD Clemmons, NC
I had installed SQL express yesterday, and it did function, but due some other problems, i uninstalled it, and reinstalled SQL express 2005. Appearantly, there is some rest of the old installation, blocking me to start a new installation.
The link provided by the program (below) does not connect to any page. I would appreciate some help, thanks in advance.
Regards,
Ruud
TITLE: Microsoft SQL Server 2005 Setup ------------------------------ 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." For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlShutDownRANUInstance%40sqls%3a%3aService%3a%3aStart%40x3 ------------------------------ BUTTONS: &Retry Cancel ------------------------------
I'm newbe with SQL Server , I'm looking for help with sql server express edition 2005. At the end of installation ocurrs an 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. Error Number : 29503 . (Summary file) Rest of components has status : Successfully installed
I've go installed .Net Framework 2.0, I'm using XP with SP2 , no anty-virus software during instalatin is activated, the XP firewall is off during instalation.All system check requirements are passed successufully (running on Athlon64)
No additional software bound with SQL is installed.(in add/remove programs there is nothing additional connected with sql)
I've re-installed it few times with some other options (network , local) ,different installation path ,but allways the same result - fail. I've tried to find help in few similar posts but that didn't help.Mayby i've miss somethin'
I have mentioned this problem before but it has not been resolved. I am installing MS SQL Server Express Advanced i.e. using SQLEXPR_ADV.EXE.
During the initial checks, i get a warning about hardware requirements and I have read the posts about the install failing if the CPU does not support prefetching but I am running a P4 3.0GHz (twin core) CPU with 512MB RAM on Windows XP Pro SP2.
The installation fails at SQL Server Database Services during "Configuring Microsoft SQL Server":
"Starting SQL Service: MSSQL$SQLEXPRESS"
If I click the Retry button, the system goes away and then comes back with the same message. If I click cancel, various roll-back actions are performed and the install fails
Is this the default name for the SQL Server instance ? I thought it would be named after my machine name i.e. GLKD239680SQLExpress ?
Any ideas anyone ? I have not had much luck with installing this despite 2 PC rebuilds and scanning the forums for solutions.... I can post any log files if needed
Hi all, I'm new to SSRS. I installed reporting services with my other services in SQL Server 2005. When I started Reporting Service Configuration tool,I see that my Reporting Server Status Stopped. When i am trying to start the service, i get the following error(exception)....also attached are the logfiles....
EXCEPTION DETAILS: System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed. at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
LOGFILE1: ----------------------- ------------------------------ ReportingServicesService!library!8!3/6/2008-20:26:48:: e ERROR: Sql error:System.Data.SqlClient.SqlException: Could not find stored procedure 'GetDBVersion'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery() at Microsoft.ReportingServices.Library.ConnectionManager.EnsureCorrectDBVersion() ReportingServicesService!library!8!3/6/2008-20:26:48:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. ReportingServicesService!library!8!3/6/2008-20:26:48:: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. at Microsoft.ReportingServices.Library.ConnectionManager.EnsureCorrectDBVersion() at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage() at Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread() ReportingServicesService!library!8!3/6/2008-20:26:48:: Attempting to start service again...
LOGFILE2: ------------ -------------------- ReportingServicesService!library!4!3/6/2008-20:26:47:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'MACHINE_NAMEASPNET' is not recognized., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'MACHINE_NAMEASPNET' is not recognized. ReportingServicesService!servicecontroller!9!3/6/2008-20:26:47:: Total Physical memory: 1063641088 ReportingServicesService!servicecontroller!4!3/6/2008-20:26:47:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'MACHINE_NAMEASPNET' is not recognized. at Microsoft.ReportingServices.Library.Native.NameToSid(String name) at Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServer(Boolean firstTime)
I had a strange experience with MS SQL Server 2005 Express Edition installation, I am running a P4 3G Processor, 1 GB of RAM, Windows XP SP2, 300 GB HDD (SATA if it matters at all :) ) And using Visual Studio Pro 2005.
I have managed to install the SQL Express with no hassle at all, then had to format my HDD, and start from scratch, to make a new home for my VS 2005 Pro (The 300 GB HDD) And managed to install the SQL Express as part of the VS 2005 without any problems, after using it for 3 months now, I've started a new project in VS 2005, and tried to add a new SQL DB, but it had failed for several times.
I€™ve decided that the files got corrupted for some reason and tried to reinstall the MS SQL 2005 using the original SQL Express installation file I've used before, but without joy.
I thought that it is conflicting with some new MS Update patch and downloaded the latest SQL Express advanced installation, but that did not fix the problem either.
The message I'm getting every time I attempt the installation is" SQL Server service failed to start" with all the bla bla about the online books and whatever useless stuff to learn how to start the service manually.
I have uninstalled the whole thing, including VS 2005, .NET Framework, and any registry trace of the SQL Server installation, but again all in vain.
Finally, some smart wizard suggested in one of the threads that if your computer is not part of a domain, you should run the SQL service as a local service, using the advanced option during the first step of the setup.
And guess what! It worked!!!! My Question is why did it work during the first two installations, without me fiddling with the advanced installation feature? My computer was and still is, not part of any domain, my hardware did not change at all, and I had the installation failing with or without any software installed!
System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed. at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
i get the above error when attepting to install reporting services
I'm trying to install SQL 2005 onto a 2012 R2 server. The install is failing at the end when it is trying to start the database service. I have looked in the install logs and I'm getting the following error. I'm running 8 virtual processors on the virtual machine (8 Cores). URL...
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 (1067) The process terminated unexpectedly.       <Failure Type='Fatal' Error='1067'>    <EndFunc Name='LaunchFunction' Return='1067' GetLastError='203'>    CustomAction Do_sqlScript.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)    05/18/2015 14:56:41.705 [4924]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396    [code]...
Is there a trick to getting this installed correctly? Everything works great until it gets up to starting the service. Here is the complete section of my setup log file.
SQL 2005 Standard.
Machine : KINGSERVER550 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 : KINGSERVER550 Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_KINGSERVER550_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 (1067) The process terminated unexpectedly. Error Number : 29503
I searched a previous thread dealing with this error, but seems like nobody has found a solution.
MSSQLSERVER won't restart. I can't uninstall SS7, either, because it says I have MSSEARCH running, which Task Manager can't kill (access denied, even to me the administrator). Tried changing the registry keys for MSSQL to MSSQL_old and then the install goes forward but fails at the end because some of the TEMPDB files cannot be activated. This trick worked on my Win98SE once, for the same problem. I ignorantly deleted IE4 from the server's C:drive because I needed more room to reinstall. I tried reinstalling the SS7 "components" (no apparent problem, except it detects that I have now installed IE5.5)(IE5.5 automatically installs to C:Program FilesMicrosoft or thereabouts, not C: where IE4 was, by the way). I was up to SP2 on SS7, and SP6 on NT4. The name of the server hasn't changed, but the name of the c:drive is new. Why would a new install care? I ran scandisk inbetween reboots as a caution, but the install always fails. Should I be choosing the default "allow 5 connections" rather than "5 per computer licenses"? TIA, Jeb
Help! I just took over for a new company and after logging in to one of the servers I tried to click on the Symantec Backup Exec on the desktop. It failed and said that none of the services are started, looking in my services I can not get any of the services related to sql to start. In the bottom right hand corner in the system tray I have a red dot on the sql server and it is stopped. All the event logs say that: During redoing of a logged operation in database 'master', an error occurred at log record ID (199:200:5). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
I installed a copy of SQL server 2005 on a Win 2003 machine. I connected remotely from another machine and started Sql Server Configuration manager. The MSSQLServer is stopped. So, I click to start and it failed. The error it gave me was that it time out. I am new to SQL 2005 and I thought the next step after installing was to configure. Can anyone help me please.
Straight from the sqlagent error file: (the username and login I'm providing is correct. for testing purposes only its and admin account and works on another instance)
2007-05-14 15:12:07 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001] 2007-05-14 15:12:07 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2007-05-14 15:12:07 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001] 2007-05-14 15:12:07 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start 2007-05-14 15:12:38 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001] 2007-05-14 15:12:38 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2007-05-14 15:12:38 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001] 2007-05-14 15:12:38 - ! [382] Logon to server '(local)' failed (DisableAgentXPs) 2007-05-14 15:12:39 - ? [098] SQLServerAgent terminated (normally)
I want to create a package which start and stop the SQL server's services... i know i can achive this via NET COMMAND.... but i coudnt find in which task (SSIS) I can place that command?..
I also came across that I can achieve this using Execute Process task but for this I have to define executable file.... actually i dont want ne thing outside from my SSIS package
In the last step of installing the SQL Server 2005 Express edition I get the following error:
Doing Action: Do_sqlScript PerfTime Start: Do_sqlScript : Thu Jun 21 19:38:35 2007 Service MSSQL$SQLEXPRESS with parameters '-d"c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Datamaster.mdf" -l"c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Datamastlog.ldf" -m SqlSetup -Q -qLatin1_General_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Thu Jun 21 19:38:35 2007 Service failed unexpectedly (1814) Error Code: 0x80070716 (1814) Windows Error Text: The specified resource name cannot be found in the image file. Source File Name: sqlsetuplibservice.cpp Compiler Timestamp: Wed Jun 14 16:29:04 2006 Function Name: sqlservicetart Source Line Number: 301
Do_sqlScript SqlScriptHlpr Start service MSSQL$SQLEXPRESS
Error Code: 1814 MSI (s) (80!08) [19:39:58:265]: 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 (1814) The specified resource name cannot be found in the image file. .
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 (1814) The specified resource name cannot be found in the image file. . <Func Name='GetCAContext'> <EndFunc Name='GetCAContext' Return='T' GetLastError='203'> Doing Action: Do_sqlScript PerfTime Start: Do_sqlScript : Thu Jun 21 19:39:58 2007 Service MSSQL$SQLEXPRESS with parameters '-d"c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Datamaster.mdf" -l"c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Datamastlog.ldf" -m SqlSetup -Q -qLatin1_General_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Thu Jun 21 19:39:58 2007 Service failed unexpectedly (1814) Error Code: 0x80070716 (1814) Windows Error Text: The specified resource name cannot be found in the image file. Source File Name: sqlsetuplibservice.cpp Compiler Timestamp: Wed Jun 14 16:29:04 2006 Function Name: sqlservicetart Source Line Number: 301
Product : Database Services (MSSQLSERVER) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29512 Error Description : MSP Error: 29512 SQL Server Setup was unable add user NT AUTHORITYSYSTEM to local group DCCIBERSQLServer2005SQLAgentUser$DCSQL01$MSSQLSERVER.
I am getting this message in the SQL Server error log:
Could not start Service Broker for database id: 10. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
It appears even when the broker is disabled on the database. How can I eliminate this error?
I have a clean SQL 2005 Ent. x64 SP1 clean with no user db's.....applied SP2 and everything showed "Success" except the Database Services (Error 29534)......
Time: 02/22/2007 08:29:50.134 KB Number: KB921896 Machine: TORCA8 OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790) Package Language: 1033 (ENU) Package Platform: x64 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_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 (1067) The process terminated unexpectedly.
---------------------------------------------------------------------------------- Product : Analysis Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Reporting Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB921896_sqlrun_rs.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Notification Services Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixNS9_Hotfix_KB921896_sqlrun_ns.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlncli.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 3890 Product Version (Final) : 6.10.1129.0 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_msxml6.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : SQLXML4 Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlxml4.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 1704 Product Version (Final) : 2004 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Microsoft SQL Server VSS Writer Product Version (Previous): 2047 Product Version (Final) : 3042 Status : Success Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlWriter.msi.log Error Number : 0 Error Description : ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 29534
Now SQL Server service won't restart.....
2007-02-22 10:16:31.28 Server Microsoft SQL Server 2005 - 9.00.3042.00 (X64) Feb 10 2007 00:59:02 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-22 10:16:31.28 Server (c) 2005 Microsoft Corporation. 2007-02-22 10:16:31.28 Server All rights reserved. 2007-02-22 10:16:31.28 Server Server process ID is 2056. 2007-02-22 10:16:31.28 Server Authentication mode is MIXED. 2007-02-22 10:16:31.28 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-02-22 10:16:31.28 Server This instance of SQL Server last reported using a process ID of 576 at 2/22/2007 10:16:15 AM (local) 2/22/2007 3:16:15 PM (UTC). This is an informational message only; no user action is required. 2007-02-22 10:16:31.28 Server Registry startup parameters: 2007-02-22 10:16:31.28 Server -d E:SQLDatamaster.mdf 2007-02-22 10:16:31.28 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-02-22 10:16:31.28 Server -l F:SQLLogsmastlog.ldf 2007-02-22 10:16:31.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-02-22 10:16:31.28 Server Detected 4 CPUs. This is an informational message; no user action is required. 2007-02-22 10:16:31.28 Server Cannot use Large Page Extensions: lock memory privilege was not granted. 2007-02-22 10:16:31.40 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-02-22 10:16:31.42 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-02-22 10:16:31.50 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 36200, committed (KB): 104760, memory utilization: 34%. 2007-02-22 10:16:33.45 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-02-22 10:16:33.45 Server Database mirroring has been enabled on this instance of SQL Server. 2007-02-22 10:16:33.47 spid5s Starting up database 'master'. 2007-02-22 10:16:33.47 spid5s SQL Trace ID 1 was started by login "sa". 2007-02-22 10:16:33.48 spid5s Starting up database 'mssqlsystemresource'. 2007-02-22 10:16:33.48 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-02-22 10:16:33.48 spid5s Error: 5173, Severity: 16, State: 1. 2007-02-22 10:16:33.48 spid5s One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup. 2007-02-22 10:16:33.48 spid5s Error: 5173, Severity: 16, State: 1. 2007-02-22 10:16:33.48 spid5s One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup. 2007-02-22 10:16:33.48 spid5s Log file 'F:SQLLogsmssqlsystemresource.ldf' does not match the primary file. It may be from a different database or the log may have been rebuilt previously. 2007-02-22 10:16:33.48 spid5s The log cannot be rebuilt when the primary file is read-only. 2007-02-22 10:16:33.48 spid5s Error: 945, Severity: 14, State: 2. 2007-02-22 10:16:33.48 spid5s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. 2007-02-22 10:16:33.48 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Tried reinstalling SP 2 in quiet mode using sapwd parameter.....now everything is showing the correct SP2 version but SQL Server Service won't start.......anyone????????
I am hoping someone can help me. I am having issues changing the service account MSSQLSERVER. I changed it to Local System only due to issues installing Service Packs up SP2 Critical. I used the Configuration tool to do so. I have installed all patches up to and including Critical update ( KB 934458 ). I had a heck of a time getting them to install under custom service accounts. Now when I change the service accounts back to a custom account using the configuration tool the service wont start at all.
To be clear. The service runs fine under Local System Account, but I want to run it under a limited account. I used the config tool and made sure the permissions groups were added, but it still fails to start. I am not sure what SSL log entries below is referring to.
I am running:
SQL Server Standard Edition x86 Windows 2003 Stnd SP2
Below is the log file: 2007-09-01 23:50:16.15 spid9s Starting up database 'model'. 2007-09-01 23:50:16.20 Server Error: 17190, Severity: 16, State: 1. 2007-09-01 23:50:16.20 Server FallBack certificate initialization failed with error code: 1. 2007-09-01 23:50:16.20 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-09-01 23:50:16.21 Server Error: 17182, Severity: 16, State: 1. 2007-09-01 23:50:16.21 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80. 2007-09-01 23:50:16.21 Server Error: 17182, Severity: 16, State: 1. 2007-09-01 23:50:16.21 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1. 2007-09-01 23:50:16.21 Server Error: 17826, Severity: 18, State: 3. 2007-09-01 23:50:16.21 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-09-01 23:50:16.21 Server Error: 17120, Severity: 16, State: 1. 2007-09-01 23:50:16.21 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 am not DBA or very heavy IT, but rather a developer wearing multiple hats, for the time being. So any help is greatly appreciated.
I have a ABC service on a server1 that is dependent on MSSQLSERVER service running on server2. Does anyone know how to setup the service ABC on server1 to have a dependancy on MSSQLSERVER running on server2?
When we try to connect the Sql server from our client, the MSSQLServer service stops and when we try to restart the service it goes back to the stop state after few seconds.
Server Configuration in order of installation, 1.WINNT 4. 2.SP4 3.SQL SERVER 6.5 4.Service PAck 5a for Sql Server 6.5 5.SP6a for NT
Workstation setup. 1.Member of the domain inwhich the SQL SERVER 6.5 is present 2.Sql client 6.5 3.SP4(for NT) 4.SP6a(for NT) No Service packs were installed in the workstation.
When we try to connect the server from the server the MSSQLServer service stops.We even tried reinstalling the entire setup from scratch. Kindly help us in this regard.
I am experiencing an issue with the MSSQLSERVER shutting down automically at 6:00 every 3 days. I do have 2 jobs that run at this time, but they run everyday. We did not install anything additional on the server and we are running SP3a. This just started on April 15, 2006. The Windows Event log displays the following message:
4/21/20066:00:08 PMMSSQLSERVERError(2)17052N/A<server name>The MSSQLSERVER service terminated unexpectedly.
The service stops and does not restart. It required me to restart the service manually.
For 15 days now my SQL server service is terminating with the following error
MSSQLSERVER service terminated unexpectedly. It has done this 2 Time(s). This service terminates and restarts automatically and sometimes doesnt restart we have to mannuly start it again. Event ID: 7034.
Version Details
Version: MSSQL Server 2000 Service Pack: 3a Build: 8.0.0.760
I have checked many forums most of them suggest to apply the latest service pack. But the same error has been reported by sites having SP4 also. Kindly help.
