MSDE Installation Error

Posted by Mikey Rogers on January 7, 2006, 1:37 am

Please log in for more thread options

During the MSDE 2000 installation portion, afrer you input your password the
app looks like it will install but I almost immediately get an error stating:

Microsoft SQL Server Desktop Engine
Setup failed to configure the server. Refer to the
server error logs and setup error logs for more information.

I looked for log files in the server Even Viewer and elsewhere and cannot
find anything relevent. This same error happens if I try to download and
install MSDE 2000 as a standalone but with the complex password setting in
the Command Prompt.

There are PC's on the domain that are already running SQL and connected to a
server but we just got this PC and I cannot find out how to get it installed.

Posted by Jeff on January 7, 2006, 4:40 am

Please log in for more thread options

Mikey,

If you already have an SQL Server running, you can use that for your main
database storage. I'd send you a link how to set it up, but CustomerSource
is down right now.

For this installation, make sure you have Admin rights to the machine. What
OS? You must use XP for the version on the 1.3 disk as it is MSDE with
Service Pack 4. Win9x or W2K are OK for 1.2 disk as it has MSDE with
Service Pack 3.

If you look at the disk, there is an MSDE _PKG folder and an InstallMSDE.bat
file in there to install MSDE after the fact. Oops, its only on the 1.2
disk, there is just a setup.exe on the 1.3. I need to play with that.
Here's the install line from the 1.2 version; setup /settings setup.ini
/qb+

Another thing you might try is to post the logs on the
microsoft.public.sqlserver.msde newsgroup. The gang there can usually
figure the MSDE strangeness out.
--
*
During the MSDE 2000 installation portion, afrer you input your password the
app looks like it will install but I almost immediately get an error
stating:

Microsoft SQL Server Desktop Engine
Setup failed to configure the server. Refer to the
server error logs and setup error logs for more information.

I looked for log files in the server Even Viewer and elsewhere and cannot
find anything relevent. This same error happens if I try to download and
install MSDE 2000 as a standalone but with the complex password setting in
the Command Prompt.

There are PC's on the domain that are already running SQL and connected to a
server but we just got this PC and I cannot find out how to get it
installed.

Posted by Mikey Rogers on January 7, 2006, 9:31 am

Please log in for more thread options

The workstation is running XP Pro SP 2. Thankfully, as it seems, I have both
1.2 and 1.3. Is one easier to get the MSDE installation to work over the
other? Should I just paste the command line you have typed at Run? Also, as
I stated, I was having a hard time finding a log file as the error doesn't
indicate any names of log files that I could look for. Is there a standard
log file for the installation of this app? As I said before, I couldn't find
it on the server's event viewer. Would it even be on the server or on the
workstation, itself? Thanks.

"Jeff" wrote:

> Mikey,

> If you already have an SQL Server running, you can use that for your main

> database storage. I'd send you a link how to set it up, but CustomerSource

> is down right now.

> For this installation, make sure you have Admin rights to the machine. What

> OS? You must use XP for the version on the 1.3 disk as it is MSDE with

> Service Pack 4. Win9x or W2K are OK for 1.2 disk as it has MSDE with

> Service Pack 3.

> If you look at the disk, there is an MSDE _PKG folder and an InstallMSDE.bat

> file in there to install MSDE after the fact. Oops, its only on the 1.2

> disk, there is just a setup.exe on the 1.3. I need to play with that.

> Here's the install line from the 1.2 version; setup /settings setup.ini

> /qb+

> Another thing you might try is to post the logs on the

> microsoft.public.sqlserver.msde newsgroup. The gang there can usually

> figure the MSDE strangeness out.

> --

> *

> During the MSDE 2000 installation portion, afrer you input your password the

> app looks like it will install but I almost immediately get an error

> stating:

> Microsoft SQL Server Desktop Engine

> Setup failed to configure the server. Refer to the

> server error logs and setup error logs for more information.

> I looked for log files in the server Even Viewer and elsewhere and cannot

> find anything relevent. This same error happens if I try to download and

> install MSDE 2000 as a standalone but with the complex password setting in

> the Command Prompt.

> There are PC's on the domain that are already running SQL and connected to a

> server but we just got this PC and I cannot find out how to get it

> installed.

Posted by Jeff on January 7, 2006, 7:02 pm

Please log in for more thread options

Mikey,

I don't know if either is easier than the other. You just have an easier
time to install 1.2 because of the batch file. As I said last nite, 1.3
doesn't have one and I need to play with it before trying to install that
standalone.

Will you be using this machine as a Register? If not, then there is no need
for you to install MSDE on this machine anyway. It only needs to be on the
main machine that acts as the database server and register machines for the
Terminal Offline feature to work. Here the link on how to upgrade/use the
full version of SQL http://tinyurl.com/bud2r and this describes the Terminal
Offline feature http://tinyurl.com/75cs9 You must have access to
CustomerSource to see them.

Normally on this machine. Look for a folder Program FilesMicrosoft SQL
ServerMSSQLLog the latest error is the Errorlog. then Errorlog.1, then .2
and so on.

--
*
The workstation is running XP Pro SP 2. Thankfully, as it seems, I have
both
1.2 and 1.3. Is one easier to get the MSDE installation to work over the
other? Should I just paste the command line you have typed at Run? Also,
as
I stated, I was having a hard time finding a log file as the error doesn't
indicate any names of log files that I could look for. Is there a standard
log file for the installation of this app? As I said before, I couldn't
find
it on the server's event viewer. Would it even be on the server or on the
workstation, itself? Thanks.

"Jeff" wrote:

> Mikey,

> If you already have an SQL Server running, you can use that for your main

> database storage. I'd send you a link how to set it up, but

> CustomerSource

> is down right now.

> For this installation, make sure you have Admin rights to the machine.

> What

> OS? You must use XP for the version on the 1.3 disk as it is MSDE with

> Service Pack 4. Win9x or W2K are OK for 1.2 disk as it has MSDE with

> Service Pack 3.

> If you look at the disk, there is an MSDE _PKG folder and an

> InstallMSDE.bat

> file in there to install MSDE after the fact. Oops, its only on the 1.2

> disk, there is just a setup.exe on the 1.3. I need to play with that.

> Here's the install line from the 1.2 version; setup /settings setup.ini

> /qb+

> Another thing you might try is to post the logs on the

> microsoft.public.sqlserver.msde newsgroup. The gang there can usually

> figure the MSDE strangeness out.

> --

> *

> During the MSDE 2000 installation portion, afrer you input your password

> the

> app looks like it will install but I almost immediately get an error

> stating:

> Microsoft SQL Server Desktop Engine

> Setup failed to configure the server. Refer to the

> server error logs and setup error logs for more information.

> I looked for log files in the server Even Viewer and elsewhere and cannot

> find anything relevent. This same error happens if I try to download and

> install MSDE 2000 as a standalone but with the complex password setting in

> the Command Prompt.

> There are PC's on the domain that are already running SQL and connected to

> a

> server but we just got this PC and I cannot find out how to get it

> installed.

Posted by amaDalmatian on January 9, 2006, 1:32 am

Please log in for more thread options

This usually happens when you don't have access rights to that folder.
Actually, not you, but rather the install program. So what I usually do
is to copy all the install files to a temp folder (c:temp), and give
EVERYONE full access to that folder. That will sort it out quickly.
Just remember to only give the access to that specific folder, and all
subfolders for the installs.