RE: Fail to install MSDE (log attached)

From: Rob Beene [MSFT] (rbeene_at_online.microsoft.com)
Date: 02/22/04 

Date: Sun, 22 Feb 2004 05:21:23 GMT

Hey Greg,

Thank you for the attached file. I'm sorry to hear you are having so much
trouble getting MSDE installed. To expidite the resolution, maybe consider
calling Microsoft Technical Support. The reason I say that is regretably,
the attached file by itelf isn't enough to determine why MSDE isn't
working. Also, I'm not sure if you included what command you are using for
installing MSDE?

The attached file you included shows the following reason for why the
installation failed:

Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (C8!B4): Product: Microsoft SQL Server Desktop Engine -- Setup
failed to configure the server. Refer to the server error logs and setup
error logs for more information.

Basically, what this means is that during the configuration phase of setup,
the server encountered an error. That error was written to the cnfgsvr.out
file located in the install directory where you are installing MSDE. That
file will contain the exact error for setup failing. In addition to this
file, we would also like to have the SQL Server Error logs which are in the
LOG folder where you are installing MSDE to.

Unfortunately, without this information, we will not be able to determine
exactly why the installation is failing. However, common reasons that the
configuration of the server fails are:

1. During setup, sql server is started so we can run scripts to configure
the databases. When we run those scripts the server is often started
either allowing only one connection or limited connections, there are
applications such as backupexec or web pages that are taking the
connections before setup can and therefore setup's attempt to login fails.
To resolve this, make sure all applications that are using this server are
not running including services.

OR

2. On Windows 2003, the network protocols are disabled by default. If you
don't specify DISABLENETWORKPROTOCOLS=1 in the setup command, setup may try
to use either TCP/IP or Named Pipes to connect to the server and can't
since they are not enabled. You can enable the protocols by running the
client configuration utility by going to the windows start menu and click
RUN, then run: cliconfg.exe

When the screen comes up, click to enable the approprate protocols.

OR

3. By default, MSDE only enables Windows Authentication. If your user
account is not in the Administrators group on the machine you are trying to
install MSDE to, you may not have the appropriate permissions in order for
setup to connect to SQL Server.

In general though, when installing MSDE on Windows 2003, you would do the
following:

1. Download the SP3 version of MSDE from
http://www.microsoft.com/sql/downloads/2000/sp3.asp. The file is
sql2kdesksp3.exe and is approximately 70 MB.
2. Extract the file. By default it will want to put it in C:\SQL2kSP3.
3. Once extracted, use a command prompt and navigate to
c:\sql2ksp3\msde\x86\setup
4. Run the following command. The following command assumes you want to
install a named instance. If you want MSDE to use the default instance,
elimante the argument INSTANCENAME=nameyouspecifyhere. Replace
nameyouspecifyhere with the actual name you want to use for the instance
such as DotNet. Also change sapwdyouspecify with the actual password you
want to give the sa account.

setup.exe INSTANCENAME=nameyouspecifyhere
DISABLENETWORKPROTOCOLS=1SAPWD=sapwdyouspecify L*v c:\MSDESetup.LOG

Sincerely,

Rob Beene, MCSD, MCDBA
Microsoft SQL Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.

Relevant Pages

  • Re: Inherited botched w2k3 SBS install, is this recoverable?
    ... continue installing rest of the SBS Components. ... Server Setup. ... Microsoft Windows Small Business Server Setup, ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: 2 Applications With MSDE
    ... > Since MSDE SP2 it just doesn't work anymore. ... I do not know what kind of service pack level hase been applied to Veritas ... upgrade tha instance yourself downloading and installing the sp3 from ... it is not mandatory that all MSDE/SQL Server ...
    (microsoft.public.sqlserver.msde)
  • Re: SBS Setup Error
    ... Installing over the top of an existing installation, may or may not resolve a poorly installed setup. ... Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2 ... I have reinstalled the SBS server over the top of the old version. ...
    (microsoft.public.windows.server.sbs)
  • MSDE Exorcism
    ... Got some problems installing the MSDE I downloaded it from ... and ran the setup with the following command: ... It installs, however, the server is never visible by the SQL Server ... Service Manager (although I can type it in manually, ...
    (microsoft.public.sqlserver.msde)
  • Re: MSDE installation fails
    ... Whether installing Veritas Backup Exec, Microsoft SUSW, or any other ... program that needs to add an instance of MSDE it bombs. ... SQL Server does not exist or access denied. ...
    (microsoft.public.windows.server.sbs)