MSDE install faile (faile to configure server)

pls help
I installed an instance of MSDE to a Win2000 Prof PC. It
worked (disablednetworkprotocal). Then I uninstalled and
reinstall. At the point the set up configures the SQL
Server (very final stage), it failed.


In the cnfgsv.out log file,
If network protocal is disabled, the error is:

Starting Service ...
Chinese_PRC_Stroke_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MMA0WS232
\SIS;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Cannot
find SQL Server。

If network protocal is enabled (also added TCP/IP in the
SQL Client Tool) and rebooted, the error is
Starting Service ...
Chinese_PRC_Stroke_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MMA0WS232
\SIS;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
General Network Error. Check your network documentation


Please help. I have no idea why the installation worked
the first time, but not after. Is it because I installed
with disablednetworkprotocal and made some error to the
system?

 

hi Kenneth

you have to clean up precedent removed installations... please have a look
at
http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

 

Acutally, I have seen the same answer before. I will try
when the users PC is available. But why some PCs don't
have this problem after removal of MSDE?

 

hi Kenneth,

on WinXP RTM and sp1,
http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
reports that this problem may occur if the new MSDE instance name is the
same as the previously removed MSDE instance name, and the data files of the
previous MSDE instance still exist in the Data folder.
on WinXP sp it seems not to be related to this issue, but I do not have
further info and/or workaround, and I'm sill collecting info about it to as
I'm not able to reproduce it to contact Microsoft for support...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply

 

Kenneth,

Try using a setup.ini that looks like the following and then tweak the
settings on the protocols and login modes back to where you want them.
These setting generally work.
Make sure you've removed the node for the instance name from the registry
and your folder is gone before trying to install. If you have databases to
preserve in the folder move them somewhere else and then bring them back for
attachment.

[Options]
Disablenetworkprotocols=1
InstanceName=MyOwnNameWhatever
Sapwd=Kermit
Securitymode=SQL
UID=sa

Usually this sort of setup is fairly foolproof regardless of the
circumstances. It is always a good idea to reboot before you retry the
setup and start fresh. I have had the setup fail exactly as you describe
above many times and this specific setting is the best way around it.

This may help as well, but I like to keep the same directory all the time
for standardization purposes so I don't care for this particular solution:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql

Also, I can never get by without a link to how to setup the ini file either.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp

Jamie