Enterprise Manager Messed up completely

Hi. I spent half a day trying to figure this out, so i finally turn to you
guys for help.
first i had enterprise manager for 7.0
then i installed MSDE 2000 on my machine, then enterprise manager for 2000.
then i couldnt return rows for any table in enterprise manager (big
problem) - it said procedure not found or something
so i played around, and finally i replaced MSDART.DLL with a newer one, so
now i get different error message:
unknown error 8007007F.
ANYBODY know what in the world to do?
I have MDAC 2.8 installed, it doesnt want to rollback, it doesnt want to
reinstall - i tried 100 different ways.
Thanks!Hi i got solution through guessing in the registry, thanks
"Michael" <Michael@.nospamplease.com> wrote in message
news:u%23DhOP8BEHA.3360@.TK2MSFTNGP11.phx.gbl...
> Hi. I spent half a day trying to figure this out, so i finally turn to you
> guys for help.
> first i had enterprise manager for 7.0
> then i installed MSDE 2000 on my machine, then enterprise manager for
2000.
> then i couldnt return rows for any table in enterprise manager (big
> problem) - it said procedure not found or something
> so i played around, and finally i replaced MSDART.DLL with a newer one, so
> now i get different error message:
> unknown error 8007007F.
> ANYBODY know what in the world to do?
> I have MDAC 2.8 installed, it doesnt want to rollback, it doesnt want to
> reinstall - i tried 100 different ways.
> Thanks!
>|||Hi,
It must be a problem with some mismatched file version
Reinstall MDAC 2.8 from the following location and see if it helps
http://www.microsoft.com/downloads/...0fe3-c795-4b7d-
b037-185d0506396c&DisplayLang=en
If that fails, use the component checker from the following location to see
if there are any mismatched file versions. You can do that by running an
analysis against MDAC 2.8
http://www.microsoft.com/downloads/...8df6-4a21-4b43-
bf53-14332ef092c9&DisplayLang=en
Try to replace the mismatched files with the right ones from another server
and then stop and restart SQL. Pay specific attention to OLEDB32.dll.
Regards,
Gayathri Rau [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.|||I had the same problem after upgrading to Windows 2003 Server. I called Mic
rosoft and here is the fix:
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a dat
abase or data component will result in a '8007007f' or "The specified proced
ure could not be found" error.
Status:
This is a known issue with some installations of Windows 2003
Workaround:
Extract oledb32.dll from the zip file into these two directories. It's impo
rtant that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server
Cause:
This issue is caused when the Windows 2003 installer did not update the oled
b32.dll file.
You can dowload the oledb32.dll file here: [url]http://www.promiseweb.co
m/oledb32.zip[/url]
This is per Malcolm Stewart at Microsoft Developer Support
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...