Hi,
I've been looking for the past 4 hours why SQL Express doesn't install on my Windows XP home and Pro.
Almost at the end of install, the setup try to start the SQL Server Service. I can press either retry or cancel. Retry simply show again this message box, cancel rollback the last step (sql engine setup).
While the setup is at this message box, i've look around my system to see what can be wrong.
When i start the service manualy, it stop immediatly. But, if i copy paste the command line "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS
into a "cmd", it told me it can not open file "mssqlsystemresource.mdf" located on "d:\windows\temp\mkmaster_result\".
My D drive is my cd-rom which i did not used at all during setup (i download SQLEXPR from MSDN). To make it run, i unmap my cdrom and I "subst d: c:\".
The next error was about the other database files, so i copy everything.
Finaly, SQL Express start on the command box.
There was no way to connect to it, I try osql, sqlcmd and even telnet. Nothing work, telnet only connect, the two other can not find the server.
I then stoped the sqlservr.exe, and i try starting the service. It fail with the exact same error.
Both system are clean from other beta (only .NET 2 and SQL Express). But i did try C# express, which is uninstalled and did not cause any other problem on install.
I've look at a lot of place on internet, no install failure where identical to my problem.
I have no PDC (i'm in a workgroup).
Both system are Windows XP French, one is Home Ed. the other is Professional Ed.
The home Ed. have MSVS .NET 2003, the Pro Ed. have MSVS 6.
So here the logs:
- # MSSQL.1\MSSQL\LOG\ERRORLOG
2005-08-20 13:05:04.54 Server Microsoft SQL Server 2005 - 9.00.1187.07 (Intel X86)
May 24 2005 18:22:46
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2005-08-20 13:05:04.54 Server (c) 2005 Microsoft Corporation.
2005-08-20 13:05:04.56 Server All rights reserved.
2005-08-20 13:05:04.56 Server Server process ID is 4084.
2005-08-20 13:05:04.56 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2005-08-20 13:05:04.56 Server This instance of SQL Server last reported using a process ID of 3720 at 20/08/2005 11:52:46 (local) 20/08/2005 15:52:46 (UTC). This is an informational message only; no user action is required.
2005-08-20 13:05:04.56 Server Registry startup parameters:
2005-08-20 13:05:04.56 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2005-08-20 13:05:04.56 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2005-08-20 13:05:04.56 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2005-08-20 13:05:04.56 Server Command Line Startup Parameters:
2005-08-20 13:05:04.56 Server -s SQLEXPRESS
2005-08-20 13:05:04.57 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2005-08-20 13:05:04.59 Server Detected 1 CPUs. This is an informational message; no user action is required.
2005-08-20 13:05:04.60 Server Error: 8316, Severity: 16, State: 1.
2005-08-20 13:05:04.60 Server Cannot open registry key 'HKLM\SYSTEM\CurrentControlSet\Services\MSSQL$SQLEXPRESS\Performance'. SQL Server performance counters are disabled.
2005-08-20 13:05:04.65 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.
2005-08-20 13:05:04.68 Server Database mirroring has been enabled on this instance of SQL Server.
2005-08-20 13:05:04.70 spid5s Starting up database 'master'.
2005-08-20 13:05:04.85 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2005-08-20 13:05:04.96 spid5s SQL Trace ID 1 was started by login "sa".
2005-08-20 13:05:04.99 spid5s Starting up database 'mssqlsystemresource'.
2005-08-20 13:05:05.03 spid5s Error: 17207, Severity: 16, State: 1.
2005-08-20 13:05:05.03 spid5s FCB::Open: Operating system error 21(Le priphrique n'est pas prêt.) occurred while creating or opening file 'D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf'. Diagnose and correct the operating system error, and retry the operation.
2005-08-20 13:05:05.04 spid5s Error: 17204, Severity: 16, State: 1.
2005-08-20 13:05:05.04 spid5s FCB::Open failed: Could not open file D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf for file number 1. OS error: 21(Le priphrique n'est pas prêt.).
2005-08-20 13:05:05.04 spid5s Error: 5120, Severity: 16, State: 101.
2005-08-20 13:05:05.04 spid5s Unable to open the physical file "D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf". Operating system error 21: "21(Le priphrique n'est pas prêt.)".
2005-08-20 13:05:05.07 spid5s Error: 17207, Severity: 16, State: 1.
2005-08-20 13:05:05.07 spid5s FileMgr::StartLogFiles: Operating system error 2(Le fichier spcifi est introuvable.) occurred while creating or opening file 'D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.ldf'. Diagnose and correct the operating system error, and retry the operation.
2005-08-20 13:05:05.09 spid5s File activation failure. The physical file name "D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.ldf" may be incorrect.
2005-08-20 13:05:05.09 spid5s Error: 945, Severity: 14, State: 2.
2005-08-20 13:05:05.09 spid5s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2005-08-20 13:05:05.10 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
-- #90\Setup Bootstrap\LOG\File\SQLSetup0010_SPITFIRE_SQL.log
Error Code: 1068
MSI (s) (B8!64) [14:21:05:562]: Product: Microsoft SQL Server 2005 Express Edition CTP -- Error 29523. 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 (1068) Le service ou le groupe de dpendance n'a pas pu dmarrer.
.
Error 29523. 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 (1068) Le service ou le groupe de dpendance n'a pas pu dmarrer.
.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Sat Aug 20 14:21:05 2005
Service MSSQL$SQLEXPRESS with parameters '-m -Q -qFrench_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Sat Aug 20 14:21:05 2005
Warning: VerQueryValue failed to get OriginalFileName for
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Bin\{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}sqlca.dll
with error
Info 1813.1813
Unable to start service (1068)
Error Code: 0x8007042c (1068)
Windows Error Text: Le service ou le groupe de dpendance n'a pas pu dmarrer.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Tue May 10 13:18:21 2005
Function Name: sqls::Service::Start
Source Line Number: 303
((Translation)
Le service ou le groupe de dpendance n'a pas pu dmarrer.
The service or the dependencies group could not start.
)
--
Events Logs: I'll copy some event that are related to the issue.
Application:
The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Administrator should deregister this SPN manually to avoid client authentication errors.
System:
Le service SQL Server (SQLEXPRESS) dpend du service Ouverture de session rseau qui n'a pas pu dmarrer en raison de l'erreur : %%0
(SQL Service Server depends on "network session opening" which could not start due to error %%0)
Cet ordinateur est configur en tant que membre d'un groupe de travail, et non en tant que membre d'un domaine. Il n'est pas ncessaire d'excuter le service Accès rseau dans cette configuration.
(This computer is setup as a workgroup computer and not as a domain member. It's useless to run Network Access in this configuration)
--
With all these informmation, i don't know where to go. The Network Session service is not start and could not be start (lsass.exe). But, it is in my Process in Task Manager. Is it started or not? But since it's a Domain tool, i don't need it.
In the Requirement, I can not see anywhere we need to be on a Domain. Plus, it's impossible to connect a Win XP Home to a Domain, Win XP Home is supported.
I think i write all information i have on this failure.
Thanks,
Robert.
rlvladbob@.hotmail.com
Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.
Paul
|||I'm having the same problem installing SQL Server 2005 Express on Windows XP. At the end of the installation, a message box appears stating:
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_sqlScript%40sqls%3a%3aService%3a%3aStart%40x42b
BUTTONS:
&Retry
Cancel
I have tried to start the service manually several different ways. I also checked the service log on credentials and group policies.
In the event viewer, these are the errors:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 07/17/2007
Time: 11:16:28 PM
Description:
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 (1067) The process terminated unexpectedly.
Any help? I've tried re-installing about 10 times.
|||Another user with the same problem. Windows application log says it can't write to the SQL ERRORLOG; changing the startup account to Local System gives error saying SQL trying to write to a non-existent drive. Anybody? I've cleaned the registry, retried, no luck.|||I also updated all my windows components, shut off my antivirus & spyware, made sure group policies & services were at default settings.
I was installing using the SQL Express default settings and even tried it from the administrator account.
Everything appeared to be installing correctly until it tried to start the service, then it failed and rolled back the installation every time.
I am not having any other problems on my computer. All the other Visual Studio 2005 Express programs installed flawlessly.
|||I also updated all my windows components, shut off my antivirus & spyware, made sure group policies & services were at default settings.
I was installing using the SQL Express default settings and even tried it from the administrator account.
Everything appeared to be installing correctly until it tried to start the service, then it failed and rolled back the installation every time.
I am not having any other problems on my computer. All the other Visual Studio 2005 Express programs installed flawlessly.
Appreciate any help.
|||
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Sep 07 11:52:17 2007
Machine : SONYDESKTOP
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\SQLSetup0003_SONYDESKTOP_SQLSupport_1.log
--
Machine : SONYDESKTOP
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\SQLSetup0003_SONYDESKTOP_SQLNCLI_1.log
--
Machine : SONYDESKTOP
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\SQLSetup0003_SONYDESKTOP_SqlWriter_1.log
--
Machine : SONYDESKTOP
Product : MSXML 6.0 Parser
Product Version : 6.10.1129.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_MSXML6_1.log
--
Machine : SONYDESKTOP
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 : SONYDESKTOP
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\SQLSetup0003_SONYDESKTOP_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 (1058) The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
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 : Fri Sep 07 11:56:47 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQL.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_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\SQLSetup0003_SONYDESKTOP_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_WI.log
I am running Windows Server 2003 R2 with SP2 installed. The server is 800 MHz, 1 GB Ram, 500 GB HDD. The preinstallation check said that it fulfilled minimum hardware requirements.
Exactly as what was stated initially in this forum, the SQL service fails to start. What's even more odd, before the installation starts, you can tell setup to not start the server automatically at the end of installation by unchecking the box for SQL server service. What makes this odd is setup actually ignores this setting and tries to start the service anyways, which forces me to hit cancel and rollback the installation.
My goal is to setup a demo of sharepoint on the server to use for a possible company intranet. It requires a database backend which normally comes with it, but sharepoint setup also crashes during installation for unknown reasons.
I would definitely like to know why none of these things work on a server OS...The server is currently acting as a DC, but I read that it doesn't matter.
Microsoft, can you please resolve this problem?! Thank you.
No comments:
Post a Comment