Re: MSDE install faile (faile to configure server)

Tech-Archive recommends: Fix windows errors by optimizing your registry



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

"Kenneth" <subscribe@xxxxxxxxxxx> wrote in message
news:1c9401c54328$ed80a0f0$a601280a@xxxxxxxxxx
> 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&#12290;
>
> 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?


.



Relevant Pages

  • Re: Upgrade from SBS2K to SBS2k3 R2
    ... and re-run setup. ... seems ok now except my POP3 connector failed to install... ... Dell server, ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharepoint
    ... Files\Microsoft Windows Small Business Server\Client Experience\Provision', ... please try to install the Intranet component follow below steps. ... Rename Program Files\Microsoft Windows Small Business Server ... Insert SBS setup CD 1, and then run setupsbs.exe to rerun the setup. ...
    (microsoft.public.windows.server.sbs)
  • Re: dell poweredge 830 RESULTS
    ... server software for his sweet new server for hishouse. ... this dell poweredge 830 had two 142GB scsi drives on a rebranded ... A little tweaking in the setup of that card gave us ... Rebooted into Sarge 3.1r2 net install. ...
    (Debian-User)
  • Re: Install Error after Node Replace Exchange 2003 Cluster
    ... I tried to install Exchange on the newly installed Node. ... I can see that the Setup Installs the System Attendant ... > server. ...
    (microsoft.public.exchange.setup)
  • SQL Server 2005 Cluster Intall FAILS
    ... I have a two node cluster, each running windows enterprise server 2003, 64-bit edition. ... I am running the setup for SQL 2005 64-bit Standard Edition. ... I created a domain account, SQLUser, and added it to the local admin group on each server. ... However, once it finishes installing database services, the install craps out, and gives the error "REMOTE SETUP FAILED". ...
    (microsoft.public.sqlserver.clustering)