Error 8007007F

[Gil]

Please help. Problem occurs on a Windows XP Pro box that
has absolutely all of the patches available from
Microsoft applied (for XP, Office XP, and SQL 2000
Developers Edition).

Get "Unknown error: 8007007F" when:

(1) I attempt to return all rows from any table (local or
remote server) in SQL Enterprise Manager (no problem with
Design Table in Enterprise Manager, and no problem
querying these same databases using Query Analyzer
instead of Enterprise Manager).

(2) Attempt to connect to a local or remote database
using ADO coding in VB6 (the same code works on other
XP/SQL installations). This is the killer problem - I
can't develop code for SQL if my machine won't talk to it!

I've tried ripping out SQL and reinstalling (wouldn't be
this since can't connect to remote DBs either - but I
needed to try something) and attempted to reinstall a
newly downloaded MDAC 2.7 SP1 (you can't, it sees that
it's already there and skips over it - and since
uninstall isn't available, I can't try that first).

Please help me out here. The problem must be down in the
XP/MDAC level, but I have no idea how to fix it. I setup
this PC from scratch over a month ago, and have too many
hours into installs, configurations, and patch downloads
to start AGAIN from scratch...

[Gil]

I found the answer to this problem at
http://groups.google.com/groups?
q=8007007f&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=OnSstqY%
23CHA.2040%40TK2MSFTNGP10.phx.gbl&rnum=2

-The answer posted by Ken Schaefer was right on the
money - I've just added detail and further instructions
to his answer as I went through the fix for myself...

PART A
------

-downloaded and ran Component Checker "Comcheck.exe"
(download was cc.exe, expanded into c:\comcheck\... with
over 470 files).

-find it at
http://www.microsoft.com/downloads/details.aspx?
FamilyID=8f0a8df6-4a21-4b43-bf53-
14332ef092c9&DisplayLang=en

-ran in on MDAC 2.7 SP1 (WinXP) and found oledb32.dll was
2.71.9031.4, not the expected version 2.71.9030.0...

PART B
------

-Find the correct version of oledb32.dll. I downloaded
both MDAC2.7RTM and MDAC2.7SP1 (they're both named
mdac_typ.exe).

-Extract the files from each MDAC to separate directories
without kicking off an install (example:
mdac_typ /c /t:C:\MDAC2.7SP1).

-look for mdaccxpak.cab in that directory, open it using
explorer, and extract oledb32.dll to the same directory
as the cab.

-right-click on the extracted oledb32.dll, again using
explorer, then navigate to the "version" tab to see if
it's the "expected" version (in my case, 2.71.9030.0 was
the correct one, and it came out of the MDAC 2.7 SP1
version)

PART C
------

-In Explorer, goto Tools -> Folder Options -> View, and
allow viewing of "..Protected operating system files...",
also turn on "Show hidden files and folders" (note your
original settings so you can switch back later).

-Drag c:\Windows\System32\dllcache\oledb32.dll into the
recycler (this will stop Win2k/XP system protection from
replacing the real oledb32.dll in the next step).

-Drag c:\program files\common files\system\ole
DB\oledb32.dll to the recycler as well.

-Click "Cancel" and confirm the cancel the one or two
times that the system protection asks about restoring
those versions from the WinXP install CD

-Copy the correct oledb32.dll (that you extracted in PART
B) into both c:\Windows\System32\dllcache\ and into
c:\program files\common files\system\ole DB\

-Reboot (I don't know if this is necessary, but I wanted
to make sure that nothing was "restored" while I wasn't
looking.

PART D
------

-For piece of mind, navigate to the two directories again
and check the versions of oledb32.dll (not necessary,
this is paranoia)

-Run Comcheck.exe against "2.7 SP1(WinXP)" again. You
should get "No errors or warnings detected!"

-Change the permissions back to what they were before
from the first line of PART C.

NOW, Programatic ADO connections to SQL Server work
again, The "RETURN ALL ROWS" option of the SQL Enterprise
Manager works again, and all of those other broken things
that I've seen in the newsgroups mentioned with error
8007007F should work again as well!

-The question is which patch/application install/service
pack put the incorrect version there to begin with?

-Why is this fix not in TechNet?