Errors with SP4 upgrade... Please Help

I am having problems accessing DTS after install SP4 and was wondering
if someone could offer some advice.

I installed SP4 and got the following error after it competed.

Unable to write to response file 'U:\WINDOWS\setup.iss' during
recording. Please ensure enough space is available on target drive.

I got the error 3 times (3 pop-ups).

After the install I could not access DTS. I was getting 2 error
pop-ups.
1. 'rebbrui.rll is missing'
2. Snap-In failed to initialize: Meta Data Services

I read the groups and tried several things.

I tried to reinstall MDAC and it did not help.

I tried to register several dlls and it did not help.

I found this post and it seemed to help.
Repair Script:
http://www.experts-exchange.com/Dat...Q_21445589.html

I was then able to access DTS using the profile (which is an
administrator) which
I used to install SP4 and run the above repair script. However, no
other profile can open or run DTS.

I tried running the repair script under the other profiles and it did
not help.

I was receiving 2 errors for the other profiles. I only documented one
and I am no longer getting the other. Now it just goes to a white
screen and hangs.

1st error:
DTS Designer Error
The specified module could not be found.

2nd error:
???

I tried reinstalling client tools and SP4 and it did not help. Now I
get one additional error.

Before I can expand the server node in enterprise manager I get the
following error.
Snap-in failed to initialize
Name: Meta Data Services
CLSID: {1DBA4DD4-EB97-4FD2-AB80-9D0D4BA74034}

Does anyone have a suggestion on how I might fix this?

I am running SQL Server 2000 Enterprise on Windows 2000 Server with 4
GB RAM.

I did notices that someone has set the /3GB switch. I know this is not
supported on this OS but it was not causing major problems before the
upgrade. Could it be the culprit?Finally got this fixed. It was a real pain!

The registry on this server looked all hacked up to me. It looks like
many of the keys referenced U:/ instead of C:/

Some of the necessary dlls were pointing to U: also.

I had to manually uninstall SQL Server. Then reinstall. Then uninstall
via add remove programs. Then I did another uninstall/reinstall
(because i got a few errors).

I reinstalled, upgraded to sp4, stopped the service, swapped my master,
msdb, tempdb with the originals and everything is working great.

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:
>> 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,
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.
>|||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 oledb32.dll from within this package. Replaced the file in the dllcache and program files folders, rebootet the server and everything's ok !
Hope this helps,
Torsten
"David Wilson" wrote:
> 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:
> > 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.
> > >
> > >
> >

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:
>

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[vbcol=seagreen]
>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
>.
>
|||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 valid.
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 oledb32.dll from within this package. Replaced the file in the dllcache and program 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: