problem relating to SQL Server 2000 installation

Question

problem relating to SQL Server 2000 installation

Lee Wang

Newbie

Points: 2
More actions
November 3, 2004 at 3:32 am

#86784

I wanted to reinstall SQL Server 2000 yesterday after uninstalled it a few months ago. However there was always an error hint which says "Error in installing MDAC: the memory 0x000000f0 can't be read by command 0x01555led". I checked MSDN site and found that it seems due to my installation of MDAC2.8 last month.
Hope anyone may share your experience about how to uninstall MDAC2.8 or if there is any way to solve the problem. Thank you in advance.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Wesley Brown SSChampion Points: 12045 More actions · Answer 1

I don't think there is any uninstall of the MDAC. I'm not sure installing an older version would fix that ether. SQL 2000 installs on windows 2003 and that has 2.8 as the default MDAC version. I'd put in a call to MS support or reinstall the box if that was an option.

Wes

sswords SSCrazy Eights Points: 8207 More actions · Answer 2

I'm assuming that this machine is Windows 2000 or higher?

Attempting to uninstall MDAC can be problematic at best. A large part of this is due to the fact that all Microsoft OS's starting with Windows 2000 install numerous MDAC components as part of the operating system, therefore they can't be completely removed. Rolling back MDAC means that you will need to replace the upgraded components with the ones that originally shipped with the OS. If you know the folder that you originally installed MDAC 2.8 from, you could try going to a command prompt, moving to that folder and typing 'dasetup.exe /u' as the previous install should have created an uninstall folder.

There's a microsoft link that explains this somewhat here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconinstallingredistributingado.asp

If running the /u option doesn't work, you may be looking at an OS reinstall. Before doing that though you could also try using the original CD to repair your Windows installation as a last ditch effort. It goes without saying I hope, but before trying any of this back up anything on this box that you can't afford to lose to and put it someplace safe. Hope this helps some and best of luck.

My hovercraft is full of eels.

Diarmuid Hurley SSC Veteran Points: 237 More actions · Answer 3

If it is likely that it is an MDAC problem, have you tried running the "Component Checker" available from the Microsoft web site - this has sorted me out on a number of occasions.

Diarmuid

Lee Wang Newbie Points: 2 More actions · Answer 4

Yes I tried "component checker" and found that there were many error messages relating to the MDAC2.6 in my machine. However, MDAC2.7 and 2.8 all work normally. I tried to fix the problems of 2.6 with the checker, but it seems not work.

Frank Kalis SSC Guru Points: 111183 More actions · Answer 5

By any chance, see if this helps:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;842193

http://support.microsoft.com/default.aspx?scid=kb;EN-US;828396

http://support.microsoft.com/default.aspx?scid=kb;EN-US;820761

http://support.microsoft.com/default.aspx?scid=kb;EN-US;326842

If not (and you can afford it), I would follow Wesley's suggestion and reinstall the box, before you waste too much time to find out why and how.

Good luck!

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]