Subject. Impossible to reinstall and configure SQL Server
Windwizard
Enterprise Manager on my server.
It wasn't possible co connect to the SQL Server from the console. It seemed
that all ODBC drivers were gone.
However, I was able to connect to the server via network.
Trying to get rid of this problem I uninstalled SQL Server and now I'm
trying to install it back.
I can not. In the very end of installation I get the following message.
<Setup failed to configure the server. Refer to the server error logs and
C:\windows\sqlstp.log for more information.>
In the end of sqlstp.log I found the following lines.
---
Starting Service ...
Cyrillic_General_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=RUWS4003;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=RUWS4003;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=RUWS4003;UID=sa;PWD=;database=master
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
SQL Server configuration failed.
---
I tried to install the newest MDAC2.8 but it didn't help.
Configuration
Windows 2003 Server,
SQL Server 2000 Standart Edition.
I don't want to reinstall the server completely so I would appreciate any
idea and it's extremely urgent.
Warren Read
entries in the registry behind.
After I uninstall, I follow the following routine:
1) reboot.
2) delete the folder where your previous installation of SQL Server was.
3) open regedit.exe, search for Keys:
a) SQLServer (no space between 'SQL' and 'Server')
b) SQL Server (one single space between 'SQL' and 'Server')
**** NOTE ! --- Don't delete registry entries that SQL Server didn't
install...For example, Visual Studio 7.0 adds a couple of references to SQL
Server. Also, ODBCAD32.EXE adds references to DSN's and installed drivers,
so don't remove those entries from the registry.
You should examine the registry entries before deleting them...use common
sense.
4) Reboot again.
Once this is done, your machine should be clean of your previous install of
SQL Server.
I hope this helps.
~Warren
Mark Hurd
<snip>
We're seeing the same scenario with Win2k SP2 and MSDE2000A.
It seems we've lost the ODBC driver registry entries. The files ODBC.INI and
ODBCINST.INI seem to have valid contents, but the corresponding registry
entries are missing.
We're intending to apply the registry entries from a working system, but
we'd like to know what happened and if future driver installations &
upgrades will take automatically...
--
Regards,
Mark Hurd, B.Sc.(Ma.) (Hons.)
Lori McDonald
I rebooted.
Then I manually cleaned out my registry and deleted my program files
Then I imported the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC from a machine where it
was working.
I rebooted again and then did the install and it worked!!
Thank you!
Mark Hurd
> "Mark Hurd" wrote:
> > Windwizard wrote:
> > <snip>
> > > It seemed that all ODBC drivers were gone.
> for me.
>
> I rebooted.
>
> Then I manually cleaned out my registry and deleted my program files
>
> Then I imported the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC from a machine where
> it was working.
>
> I rebooted again and then did the install and it worked!!
>
> Thank you!
Yes, we can also confirm this gets MSDE installed.
Still looking for the reason why the ODBC registry keys were empty...
Addcom
Hi
Just give this a try
Go to AddRemove program and check if the SQL progroam or MSDE is still
installed.
If it is then uninstall.
Go to ptrogram Files\Microsoft Server SQL ir the location where the server
program are installed. Delete the folder.
I experience this before if you install MSDE2000 and something goes wrong or
stop the install in the middle then you get the problem you described,...
I think it is to do with the master.mdb being corrupt
have go and lets know
"Mark Hurd" <mark...@ozemail.com.au> wrote in message
news:ea6sDn3V...@tk2msftngp13.phx.gbl...