Hi,
First I attemtped to upgrade MSDE to sp4, and I got the error
"This product is not installed",
So I removed the installation of MSDE and just installed sp4 directly. But
when I do, I get the error
"Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (A4!4C) [12:01:18:241]: Product: Microsoft SQL Server Desktop Engine
(VLM) -- Setup failed to configure the server. Refer to the server error
logs and setup error logs for more information."
The only other line in the log that metions a failure is
Setting SqlEdition property failed
The installer then backs everthing out and removes the service. The service
was already installed and running at that point.
I am using SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to install,
Thanks,
Brian
hi Brian,
msnews.microsoft.com wrote:
> Hi,
> First I attemtped to upgrade MSDE to sp4, and I got the error
> "This product is not installed",
> So I removed the installation of MSDE and just installed sp4
> directly. But when I do, I get the error
> "Setup failed to configure the server. Refer to the server error logs
> and setup error logs for more information.
> MSI (s) (A4!4C) [12:01:18:241]: Product: Microsoft SQL Server Desktop
> Engine (VLM) -- Setup failed to configure the server. Refer to the
> server error logs and setup error logs for more information."
> The only other line in the log that metions a failure is
> Setting SqlEdition property failed
> The installer then backs everthing out and removes the service. The
> service was already installed and running at that point.
> I am using SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to install,
this usually means you did not comletely uninstall MSDE (not your fault,
just MSDE fault :D)
I succesfully cleared my registry and file system following
http://support.microsoft.com/default...b;en-us;290991 KB article
adiveces but the Windows Installer entries, that can be cleared using the
Windows Installer SDK tool Msizap.exe as per
http://support.microsoft.com/default...b;en-us;320873 (never tried)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Got it fixed.
To get it to work I did the following:
1. Intalled a default instance. I had removed it as well. That worked.
2. re-registering sqldmo.dll. I did this because DbaMgr got an automation
error when connecting to the default instance
3. Installed the named instance I wanted. This time it worked.
Notes:
The error I was getting was
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error.
Check your network documentation.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()).
Things learned along the way:
1. If the install fails, then enable verbose logging with /L*v
C:\MSDELog.log. Look in the log when its finished for what failed. When you
get the error message box, LEAVE IT THERE, and go look at the log. The last
thing it did is the last line.
2. If you get the error "Unable to configure server", then look in the file
cnfgsvr.out. It will be in C:\Program files\Microsoft SQL
Server\MSSQL$<instancename>\Inatall (assuming drive c)
3. To clean manully to get the installer to resintall completely if a
partial install is left on the system:
- Run Windows Installer SDK tool Msizap.exe as per
http://support.microsoft.com/default...b;en-us;320873
The command is MSIZAP.EXE" T {product code}. The product code can be
found in the install log (C:\MSDELog.log in the example above). The product
code for MDSE service pack 4 was
{E09B48B5-E141-427A-AB0C-D3605127224A} so I ran
MSIZAP.EXE" T {E09B48B5-E141-427A-AB0C-D3605127224A}
- Manually delete the folder C:\Program Files\Microsoft SQL Server\MSSQL
or C:\Program Files\Microsoft SQL Server\MSSQL$<instancename>. Make sure you
look at cnfgsvr.out first if you need too!
Brian
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3s9k91Fn804jU1@.individual.net...
> hi Brian,
> msnews.microsoft.com wrote:
> this usually means you did not comletely uninstall MSDE (not your fault,
> just MSDE fault :D)
> I succesfully cleared my registry and file system following
> http://support.microsoft.com/default...b;en-us;290991 KB article
> adiveces but the Windows Installer entries, that can be cleared using the
> Windows Installer SDK tool Msizap.exe as per
> http://support.microsoft.com/default...b;en-us;320873 (never
> tried)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
