Re: setup failed to configure server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Andrea Montanari (andrea.sqlDMO_at_virgilio.it)
Date: 01/04/05 

Date: Tue, 4 Jan 2005 17:49:31 +0100

hi,
"Pluno" <Pluno@discussions.microsoft.com> ha scritto nel messaggio
news:87D5C336-8824-4673-AB24-A18C9E041186@microsoft.com
> hi everyone,
>
> I'm trying to install MSDE2000 on my PC. Some seconds before the end
> of the installation I get an error message: setup failed to configure
> server. I've changed my command into setup.exe disablerollback=1
> disablenetworkprotocols=0 instancename="name" sapwd="passwd" /L*v
> C:/MSDElog.log so that I could see what's going wrong. I get this:
>
> MSI (c) (78:0C) [03:49:35:406]: Note: 1: 1708
> MSI (c) (78:0C) [03:49:35:406]: Product: Microsoft SQL Server Desktop
> Engine -- De installatie is mislukt. (it means that the
> installation has failed)
>
> MSI (c) (78:0C) [03:49:35:406]: Grabbed execution mutex.
> MSI (c) (78:0C) [03:49:35:406]: Cleaning up uninstalled install
> packages, if any exist
> MSI (c) (78:0C) [03:49:35:406]: MainEngineThread is returning 1603
> === Verbose logging stopped: 4/01/2005 3:49:35 ===
>
> I searched everywhere on the net to find a solution and I was told
> that this error means that the server is not running, but I checked
> all the services and the server one is running. The option 'File and
> print sharing' is active as well. I get this error from the very
> first attempt to install it, so I don't think that there are values
> in my registry that need to be deleted, but Im not sure about that.
> Can anybody help me to find a solution? (I'm working with windows XP
> home Edition)
>
> Thanks in advance!!!
>
> Pluno

usually the advices reported at
http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
help solving this problem 

-- 
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm        http://italy.mvps.org
DbaMgr2k ver 0.9.1  -  DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

Relevant Pages

  • Re: How to install WSS 3.0 SP2 & WSUS 3.0 on a new fresh install SBS2003
    ... Make sure you do a parallel install according to the instructions ... i need to install sql express 2008 on the server. ... You'd need a new separate instance. ...
    (microsoft.public.windows.server.sbs)
  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)