Errors after upgrade

After upgrading the server to Windows 2003 Server, I
receive the following error when trying to view all table
rows - Unknown Error 8007007F. I tried reinstalling
SP3a, but that resulted in the same error. Also, the
ODBC connections from desktops to the database receive
an "ODBC failed" error.
Anyone know what may be causing these errors?Mike,
Try applying MDAC 2.8. If that fails, there is a fix for the oledb32.dll
file which you can obtain from Microsoft.
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a
database or data component will result in a '8007007f' or "The specified
procedure 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
important 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
oledb32.dll file.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> After upgrading the server to Windows 2003 Server, I
> receive the following error when trying to view all table
> rows - Unknown Error 8007007F. I tried reinstalling
> SP3a, but that resulted in the same error. Also, the
> ODBC connections from desktops to the database receive
> an "ODBC failed" error.
> Anyone know what may be causing these errors?|||Mark,
I tried the MDAC 2.8 install, but the same errors
occurred. Is the oledb32.dll file I need on the MS site
(I checked the Knowledge Base, but didn't find anything)
or on the Win 2003 CD?
Thanks for your help.

>--Original Message--
>Mike,
>Try applying MDAC 2.8. If that fails, there is a fix for
the oledb32.dll
>file which you can obtain from Microsoft.
>Symptoms:
>After upgrading from Windows 2000 to Windows 2003
attempting to access a
>database or data component will result in a '8007007f'
or "The specified
>procedure 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
>important 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
>oledb32.dll file.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mike wrote:
table[vbcol=seagreen]
>.
>|||Mike,
http://www.promiseweb.com/oledb32.zip
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mike wrote:
> Mark,
> I tried the MDAC 2.8 install, but the same errors
> occurred. Is the oledb32.dll file I need on the MS site
> (I checked the Knowledge Base, but didn't find anything)
> or on the Win 2003 CD?
> Thanks for your help.
>|||Mark,
I have encountered the same problem, but your link to the URL is no longer v
alid.
Any thoughts or help would be most appreciated.
David
"Mark Allison" wrote:

> Mike,
> http://www.promiseweb.com/oledb32.zip
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Mike wrote:
>|||Hi David,
I ran into this error, too. The link is broken.
So I just downloaded MDAC 2.8 from the Microsoft homepage and used the oledb
32.dll from within this package. Replaced the file in the dllcache and progr
am files folders, rebootet the server and everything's ok !
Hope this helps,
Torsten
"David Wilson" wrote:
[vbcol=seagreen]
> Mark,
> I have encountered the same problem, but your link to the URL is no longer
valid.
> Any thoughts or help would be most appreciated.
> David
> "Mark Allison" wrote:
>