Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts

Sunday, March 25, 2012

can we change from Windows authentication to SQL authentication after installing SQL Sever

I already installed SQL Server 2000 and choose Windows authentication during
the setup. Can i still change to sql authentication now? I couldnt see such
options in Enterprise Manager. Please advise! ThanksRight click on the server in Enterprise Manager. Choose properties. Choose
the Security tab.
I hope this helps!
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Matthew Louden" <mattloude@.hotmail.com> wrote in message
news:eEvUu8DxDHA.1736@.TK2MSFTNGP09.phx.gbl...
> I already installed SQL Server 2000 and choose Windows authentication
during
> the setup. Can i still change to sql authentication now? I couldnt see
such
> options in Enterprise Manager. Please advise! Thanks
>

Thursday, March 8, 2012

Can SQL Server work with a Paradox table?

I've never really setup or used MS SQL Server (just a couple hours, one
day, several months ago). I think MS SQL Server has the ability to use
"linked tables", like MS Access does. Is this correct? What I want to
do is have an MS SQL Server setup, which compatible applications can
talk with, but I want the data to come from a Paradox database. I can
use any MS SQL version, whatever would work best. I'm not sure about
the Paradox version, I know it is an old DOS version. I can't just
convert the data to another format, because Paradox still needs to use
it.

I tried using MS Access before, with ODBC drivers it *should* be able
to work with the Paradox data. However, I ended up with lots of data
corruption. I'm hoping MS SQL Server may work better, and not corrupt
the Paradox data everytime it is updated.It's been a while since I've used Paradox, but you should be able to
what you want. I would find the appropriated ODBC drive from Paradox,
rather than use the generic MS drivers. That was probably the cause of
your corruption issues in the past.

How real-time does your data access need to be? If there can be some
delay, you may consider using an import process to fetch the data from
Paradox and convert it to MSSQL; that may reduce locking issues on the
Paradox side.

HTH,
Stu|||Thanks for the reply. The data access needs to be real-time, so any
import/export or even synchronization would not work.

I'll try again, since I don't remember all of the details. I'm pretty
sure over my several attempts I tried both the MS drivers, and the BDE
drivers (Borland, but as far as I know those are the only Paradox
drivers, since Corel (current Paradox owners) haven't really updated
Paradox or done any work on it). I only tried with Access though, so
I'll see if I have better luck with MSSQL.|||For the project I worked on integrating Paradox with SQL Server, I
ended up buying a copy of Paradox to get the ODBC drivers that came
with it. It was some third-party driver (and it was years ago), but
they worked great. Of course, I wasn't doing real-time integration; it
happened every 5 minutes or so.

Not sure that helps; I tried googling for the vendor we used (I think
it was DataDirect, but not sure). All I remember was that it was
cheaper to get a single copy of Paradox than to get the server licence
from the vendor.

Stu|||Thank you, and that is exactly what I found. After reading the last
post I decided to try again. This time I found that ODBC driver that
comes with Paradox (by Intersolv) and that fixed the data corruption
which I was getting with the Microsoft driver. Great!

I just started to play around with it. Most areas seem pretty fast.
The only weird thing, which I'm hoping I can find a way around, is that
it takes about 5 seconds to enter "edit mode", for example:

1. Open Linked table in Access (opens really fast, like in Paradox)

2. Browse through records (really fast), then start to edit one of the
records

... Access hangs for about 5 seconds, then enters "edit mode"...

3. Edit the record and save it (really fast), edit aditional records
(really fast).

4. Close table, then reopen...

5. First edit has that 5 second delay again.

I'm sure it has to do with locking. In Paradox it takes less than a
second to enter edit mode (a split second), so hopefully there is a way
to get the ODBC driver to work just as fast. Not sure if it is an ODBC
thing, or Access, but I guess I could check by using some other
utilities which can use the ODBC driver (like Borland's "Database
Desktop").

I haven't brought SQL into the picture yet, but I might, for one thing
I'll only need one server license for the ODBC driver, instead of one
for each workstation if I only use Access.

Stu wrote:
> For the project I worked on integrating Paradox with SQL Server, I
> ended up buying a copy of Paradox to get the ODBC drivers that came
> with it. It was some third-party driver (and it was years ago), but
> they worked great. Of course, I wasn't doing real-time integration; it
> happened every 5 minutes or so.
> Not sure that helps; I tried googling for the vendor we used (I think
> it was DataDirect, but not sure). All I remember was that it was
> cheaper to get a single copy of Paradox than to get the server licence
> from the vendor.
> Stu

Thursday, February 16, 2012

Can replication handle existing database?

Hello:
I have the following situatioin. A few months ago, I setup a secondary SQL
server with the same schema and data as the primary. But that server was
shut down for a few months.
Currently, I am thinking to set up replication (transaction). Since the
database is rather huge, I think I will try transaction replication. Do you
think it will work so that the secondary server will be in sync with the
primary server? This is the first time I am doing it.
Thanks,
Q
If the data is now out of sync, this'll need attending to first. You could
use Redgate's DataCompare to synchronize the subscriber with the publisher
then after that do a nosync initialization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Can replication be ran on a MS sharepoint database?

Hello,

I was curious if you can have merge and/or snapshot replication setup on a MS sharepoint database? Thanks.

John

I don't think that those will work for the following reason.

At a recent MS course, we asked our instructor if it was possible to change the content database in SP central Admin to a secondary database server during a crisis. They advised that this might be a problem because the SP configuration database creates hard-coded entries referencing the database server name that it resides on. They suspsected that these entries would cause problems in the long run, if not right away.

We decided to test this out by creating a virtual environment that mimicked our production system. We then copied the database to a seperate physical machine. To try and avoid the configuration database problems, we created a new virtual site on the VM that mirrored our existing front end and pointed it to the new database to recreate the configuration database.

Everything worked okay for about 3 hours then we began to see timeouts due to maxpoolsize being reached. When we checked the event log we also found that the server was STILL trying to connect to the original database even though everything was on the new server. Eventually, it became impossible to access any of the sites in the virtual environment.

I imagine that these entries in the configuration database would cause the same problem if we were to replicate from one server to another. We're now thinking of using log shipping or clustering to try and provide the redundancy we're looking for.

|||

Jaydog,

Thanks for your reply.

John

|||Hey John,

Looks like I was premature with my first response. We tried the same thing one more time, except that we shut down the old SQL Server before clearing the old configuration database and allowing SharePoint to rebuild it. So far, it looks like everything is up and running.

We're giving it a few days to see if there are any adverse effects and then we will be trying to get merge replication up and running. I'll post again once there is more to report.|||

Jaydog,

I look forward to what you find out.

John

|||

Jaydog,

I was curious if you had an update on this?

John

|||

Jaydog,

I would also be interested in finding out how that went.

JBW

Can replication be ran on a MS sharepoint database?

Hello,

I was curious if you can have merge and/or snapshot replication setup on a MS sharepoint database? Thanks.

John

I don't think that those will work for the following reason.

At a recent MS course, we asked our instructor if it was possible to change the content database in SP central Admin to a secondary database server during a crisis. They advised that this might be a problem because the SP configuration database creates hard-coded entries referencing the database server name that it resides on. They suspsected that these entries would cause problems in the long run, if not right away.

We decided to test this out by creating a virtual environment that mimicked our production system. We then copied the database to a seperate physical machine. To try and avoid the configuration database problems, we created a new virtual site on the VM that mirrored our existing front end and pointed it to the new database to recreate the configuration database.

Everything worked okay for about 3 hours then we began to see timeouts due to maxpoolsize being reached. When we checked the event log we also found that the server was STILL trying to connect to the original database even though everything was on the new server. Eventually, it became impossible to access any of the sites in the virtual environment.

I imagine that these entries in the configuration database would cause the same problem if we were to replicate from one server to another. We're now thinking of using log shipping or clustering to try and provide the redundancy we're looking for.

|||

Jaydog,

Thanks for your reply.

John

|||Hey John,

Looks like I was premature with my first response. We tried the same thing one more time, except that we shut down the old SQL Server before clearing the old configuration database and allowing SharePoint to rebuild it. So far, it looks like everything is up and running.

We're giving it a few days to see if there are any adverse effects and then we will be trying to get merge replication up and running. I'll post again once there is more to report.
|||

Jaydog,

I look forward to what you find out.

John

|||

Jaydog,

I was curious if you had an update on this?

John

|||

Jaydog,

I would also be interested in finding out how that went.

JBW

Can replication be ran on a MS sharepoint database?

Hello,

I was curious if you can have merge and/or snapshot replication setup on a MS sharepoint database? Thanks.

John

I don't think that those will work for the following reason.

At a recent MS course, we asked our instructor if it was possible to change the content database in SP central Admin to a secondary database server during a crisis. They advised that this might be a problem because the SP configuration database creates hard-coded entries referencing the database server name that it resides on. They suspsected that these entries would cause problems in the long run, if not right away.

We decided to test this out by creating a virtual environment that mimicked our production system. We then copied the database to a seperate physical machine. To try and avoid the configuration database problems, we created a new virtual site on the VM that mirrored our existing front end and pointed it to the new database to recreate the configuration database.

Everything worked okay for about 3 hours then we began to see timeouts due to maxpoolsize being reached. When we checked the event log we also found that the server was STILL trying to connect to the original database even though everything was on the new server. Eventually, it became impossible to access any of the sites in the virtual environment.

I imagine that these entries in the configuration database would cause the same problem if we were to replicate from one server to another. We're now thinking of using log shipping or clustering to try and provide the redundancy we're looking for.

|||

Jaydog,

Thanks for your reply.

John

|||Hey John,

Looks like I was premature with my first response. We tried the same thing one more time, except that we shut down the old SQL Server before clearing the old configuration database and allowing SharePoint to rebuild it. So far, it looks like everything is up and running.

We're giving it a few days to see if there are any adverse effects and then we will be trying to get merge replication up and running. I'll post again once there is more to report.|||

Jaydog,

I look forward to what you find out.

John

|||

Jaydog,

I was curious if you had an update on this?

John

|||

Jaydog,

I would also be interested in finding out how that went.

JBW

Tuesday, February 14, 2012

Can Not View Reports (Please Help)

I am running RS on a W2K3 server. I have a report setup with a datasource to
use sql security. When I try to run the report from the server or from a
client I get a login failed for user "userid"
I am not sure what to check and have been toying with this for 3 days now. I
would appreciate any help!
Thank You.Andy,
I have nearly the exaxt same problem.
SQL Server 2000 SP3
SQL Reporting Services SP1 on the server and Report Designer client
W2K3 Server OS.
In Report Manager, I created a new role called View Reports Only which has
View Reports and View Folders permissions. I have assigned authenticated
users to have the View Reports Only role at the Home folder, which propagates
down through all folders and reports. Yet, the users get prompted with a
login / password dialogue when they try to view a report via a url link from
our intranet web page.
So far, the only way a user can run one of the reports is to be a member of
the Local Administrators group on the W2K3 server.
I have not loaded W2K3 Server SP1 yet. I wonder if any fixes for this
situation would be included with it. My company does not want to install
W2K3 Server SP1 on any of our live servers until we have time to do some
testing for any ill side affects.
I also have not loaded Reporting Services SP2 yet until I see fewer negative
posts on here about ill side affects. Unless it gurantees a fix for this
security issue.
Hopefully, someone on here can shed some light on this W2K3 security problem.
I have the exact same setup running on another server without any problems.
The only main difference is the server that behaves correctly is running W2K
Server OS, not W2K3 Server.
--
Owen B
SQL Report Writer
"Andy Jones" wrote:
> I am running RS on a W2K3 server. I have a report setup with a datasource to
> use sql security. When I try to run the report from the server or from a
> client I get a login failed for user "userid"
> I am not sure what to check and have been toying with this for 3 days now. I
> would appreciate any help!
> Thank You.
>
>|||Bump
--
Owen B
SQL Report Writer
"Owen B" wrote:
> Andy,
> I have nearly the exaxt same problem.
> SQL Server 2000 SP3
> SQL Reporting Services SP1 on the server and Report Designer client
> W2K3 Server OS.
>
> In Report Manager, I created a new role called View Reports Only which has
> View Reports and View Folders permissions. I have assigned authenticated
> users to have the View Reports Only role at the Home folder, which propagates
> down through all folders and reports. Yet, the users get prompted with a
> login / password dialogue when they try to view a report via a url link from
> our intranet web page.
> So far, the only way a user can run one of the reports is to be a member of
> the Local Administrators group on the W2K3 server.
> I have not loaded W2K3 Server SP1 yet. I wonder if any fixes for this
> situation would be included with it. My company does not want to install
> W2K3 Server SP1 on any of our live servers until we have time to do some
> testing for any ill side affects.
> I also have not loaded Reporting Services SP2 yet until I see fewer negative
> posts on here about ill side affects. Unless it gurantees a fix for this
> security issue.
> Hopefully, someone on here can shed some light on this W2K3 security problem.
> I have the exact same setup running on another server without any problems.
> The only main difference is the server that behaves correctly is running W2K
> Server OS, not W2K3 Server.
> --
> Owen B
> SQL Report Writer
>
> "Andy Jones" wrote:
> > I am running RS on a W2K3 server. I have a report setup with a datasource to
> > use sql security. When I try to run the report from the server or from a
> > client I get a login failed for user "userid"
> >
> > I am not sure what to check and have been toying with this for 3 days now. I
> > would appreciate any help!
> >
> > Thank You.
> >
> >
> >

Can not uncompress files during setup of beta 3 or sql2005eval

I have had problems during the beta 3 or sql2005eval edition self extracting setups. It gets to the evaluating configuration then gives the error "not enough drive space on C:\ to extract files". I have a 1.8 ghz processor with 512mbs of RAM and 44.3 gbs of hard drive space. I have no problems installing any of the versions at work. I have tried a couple of different suggested fixes and they did not work. Any help would be greatly appreciated!Try this advice from a former SQL Setup tester:
http://blogs.msdn.com/nikop/archive/2005/03.aspx

Sunday, February 12, 2012

Can not start Service on install

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 feel the pain of all of you. I am very suprised that no one is able to solve this problem, not even Microsoft!!

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.

Can not start Service on install

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

Can not start Service on install

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

Can not start Service on install

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 feel the pain of all of you. I am very suprised that no one is able to solve this problem, not even Microsoft!!

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.
|||

Exact same problem here, can't install because it can't start the service and then rolls back the install:

"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."

HP Desktop

Pentium 4

1.8ghz

1.2Gb ram

XP Pro 2002 SP2

Can not start Service on install

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 feel the pain of all of you. I am very suprised that no one is able to solve this problem, not even Microsoft!!

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.
|||

Exact same problem here, can't install because it can't start the service and then rolls back the install:

"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."

HP Desktop

Pentium 4

1.8ghz

1.2Gb ram

XP Pro 2002 SP2