MSDE Setup fails...

I don't think I've ever worked so long and tried so many suggestions,
recommendations and followed KB article processes in my life with so little
success -- in fact, none -- and so intransigent a set of symptoms. I hope
that there is someone here that will be able to help me.
To set the hardware scene: I have a 3 year old Sony Vaio with P4 HT 3.2
ghz, 1GB ram, 560 GB of hard drive and a new ATI video card. It has had
lots of software installed and removed over the last couple of years. My
wife has an almost identical eMachine that is 9 months old and is still in
the exact state that it was when it came out of the box. Both run XP Pro
sp2.
The problem: I purchased a copy of Pinnacle Studio Plus vers 10 video
editing software. With it I got also their media manager which uses MSDE.
I have not been able to successfully install that software. It gets to the
exact same spot (says that it is 5 sec from finishing the MSDE setup) and
then quits with an error every time. I've tried manually installing MSDE
and the symptoms and results are exactly the same -- each and every time.
I've verified that File & print sharing are installed and enabled. I've
verified that my policy is to install unsigned drivers. I've cleaned out
the registry of failed attempt entries. I've removed all of the file
directories. I've run the MDAC repair that I found in another post here.
I've got the setup logs and the error logs, including the verbose log from
my manual attempt but it has not helped me.
Nothing has made one single iota of a difference. Kinda like trying to
teach a pig to tell time -- won't work, just irritates the pig and
frustrates you.
Now, here's the kicker: I tried the install on my wife's machine and it
went perfectly. Installed without a hitch.
The logs (setup & error) are similar, but as you might guess, differ in a
couple of key respects. I have put the successful setup log and error log
into a spreadsheet along with the unsuccessful setup log and error log.
I've matched the common entries from both on the same row and hi-lighted the
differences.
If there is someone here that can help me I can provide this file, or
anything else related that you might need, via e-mail.
Can someone give me a hand with this?
Frustrated in Seattle
I ran the verification software and it showed that I had all MDAC 2.8 sp1
components installed with no differences/issues detected.
I noticed that I don't have a service, much less one running, for MSSQL. So
I installed MS SQL Server 2005 Express. It installed perfectly and
afterwards the service was there and running. However, MSDE still wouldn't
install -- exact same behavior.
I did find another log [extension was ".out"] and it also is pointing to an
ODBC problem. Nowhere in any instructions does it say anything about
setting up any ODBC connections so I suspect this may be a red herring. But
I did put it right after this note for reference.
I clearly don't know what I'm talking about but I'm getting the sense that I
don't really need SQL Server installed because MSDE is supposed to be some
sort of "light" version for the desktop. So the fact that MSDE is not
installing may account for why there was no MSSQL service before I installed
SQL Server 2005 Express.
Btw, I've verified that File & Print sharing is enabled and that unsigned
drivers are set to install automatically -- two things that MS KB identified
as potential related issues. I've gone through and completely removed all
registry vestiges of the product and the file directories and started over
from scratch. The result was exactly the same.
The first error that it encounters is when it tries to configure the new
server it's installing and it's an unrecoverable error. I've included the
log entries for that as well.
Still looking for help. Sigh...
Howard
################################################## #######################
====SQL Server Error Log====
2006-01-26 20:40:34.31 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-01-26 20:40:34.32 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-01-26 20:40:34.32 server All rights reserved.
2006-01-26 20:40:34.32 server Server Process ID is 2460.
2006-01-26 20:40:34.32 server Logging SQL Server messages in file
'C:\Program Files\Pinnacle\MediaServer\Microsoft SQL
Server\MSSQL$PINNACLESYS\LOG\ERRORLOG'.
2006-01-26 20:40:34.34 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-01-26 20:40:34.49 server SQL Server configured for thread mode
processing.
2006-01-26 20:40:34.49 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-01-26 20:40:34.53 spid3 Warning ******************
2006-01-26 20:40:34.53 spid3 SQL Server started in single user mode. Updates
allowed to system catalogs.
2006-01-26 20:40:34.68 spid3 Starting up database 'master'.
2006-01-26 20:40:35.15 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-01-26 20:40:35.17 spid5 Starting up database 'model'.
2006-01-26 20:40:35.28 spid3 Server name is 'OFFICE\PINNACLESYS'.
2006-01-26 20:40:35.28 spid3 Skipping startup of clean database id 5
2006-01-26 20:40:35.28 spid3 Skipping startup of clean database id 6
2006-01-26 20:40:35.28 spid3 Starting up database 'msdb'.
2006-01-26 20:40:35.28 server SQL server listening on 192.168.1.100: 1465.
2006-01-26 20:40:35.28 server SQL server listening on 127.0.0.1: 1465.
2006-01-26 20:40:35.28 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-01-26 20:40:35.28 server SQL Server is ready for client connections
2006-01-26 20:40:35.78 spid5 Clearing tempdb database.
2006-01-26 20:40:36.84 spid5 Starting up database 'tempdb'.
2006-01-26 20:40:37.03 spid3 Recovery complete.
2006-01-26 20:40:37.03 spid3 SQL global counter collection task is created.
2006-01-26 20:40:37.12 spid3 Warning: override, autoexec procedures skipped.
2006-01-26 20:40:44.71 spid3 SQL Server is terminating due to 'stop' request
from Service Control Manager.
================================================== =====================
====Verbose MSDE Install Log=====
Starting custom action SkuIt
MSI (s) (A4:A4) [22:15:37:640]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (A4:A4) [22:15:37:640]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (A4:A0) [22:15:37:656]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI3F.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Howard\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Howard\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q
"SQL_Latin1_General_CP1_CI_AS""
MSI (c) (54:98) [22:16:04:703]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (A4!20) [22:16:08:500]: 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.
Action ended 22:16:08: InstallFinalize. Return value 3.
################################################## ##########################===Configure.out===Start ing Service ...SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659Connecting to Server ...driver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=
master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver specifieddriver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver speci
fieddriver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver specifiedSQL Server configuration failed.########################################### #############
####################
|||hi Howard,
Howard Woodard wrote:
> MSI (s) (A4!20) [22:16:08:500]: 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.
> Action ended 22:16:08: InstallFinalize. Return value 3.
this error is usually related to
http://support.microsoft.com/default...9&Product=sql,
but I do think you already noticed and tried it's advices...
another non indicated cause I'm aware of is related to MDAC stack
corruption, as you alredy reported, tha could be fixed as reported in
http://www.macropool.com/en/download/mdac_xp_sp2.html.. but it seems to me
you already checked that...
other causes... to the besto of my knowledge, unfortunately I can not help
further...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea. There is one more thing that you can help me with if you
would. It appears that there is some expectation that I would already have
a Microsoft Sql Server directory under the Program Files directory and
possibly even an SQLSERVER service running. Is that right? I have neither
and see no option for installing it from my XP Pro CD.
Can you confirm what I should be looking for please?
Tia,
Howard
==========================================
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:44eh20F1qf9sU1@.individual.net...
> hi Howard,
> Howard Woodard wrote:
> this error is usually related to
> http://support.microsoft.com/default...9&Product=sql,
> but I do think you already noticed and tried it's advices...
> another non indicated cause I'm aware of is related to MDAC stack
> corruption, as you alredy reported, tha could be fixed as reported in
> http://www.macropool.com/en/download/mdac_xp_sp2.html.. but it seems to me
> you already checked that...
> other causes... to the besto of my knowledge, unfortunately I can not help
> further...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Never mind. I got this figured out. MSDE installs from the XP Office CD,
not from the XP Pro CD.
I reinstalled it and then my video editing software was able to install the
instance that it needed.
Thanks for helping me.
==============================
"Howard Woodard" <woodard@.msn.com> wrote in message
news:uqrrZUGKGHA.740@.TK2MSFTNGP12.phx.gbl...
> Thanks Andrea. There is one more thing that you can help me with if you
> would. It appears that there is some expectation that I would already
> have a Microsoft Sql Server directory under the Program Files directory
> and possibly even an SQLSERVER service running. Is that right? I have
> neither and see no option for installing it from my XP Pro CD.
> Can you confirm what I should be looking for please?
> Tia,
> Howard
> ==========================================
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:44eh20F1qf9sU1@.individual.net...
>
sql