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 accessing VFP data.

I have a test system setup in Reading.
SQL Server is on machine EUK01314
IIS 5 also is on machine EUK01314
Reporting services are installed on machine EUK01314
Visual Studo is on machine EUK01314
I can create reports that access SQL server data, or via ODBC, or via OLEDB
to SQL server on EUK01314.
I can use those reports from our Terminal Server, no problem.
I can create reports that access Oracle data, via ODBC, or via OLEDB to
Oracle on a server in Belgim..
I can use those reports from our Terminal Server, no problem.
I draw a total blank accessing Visual FoxPro data.
I can create reports that access VFP data, via ODBC or OLEDB.
Those reports work on EUK01314 in Visual Studio.
Those reports work on EUK01314 in IE via Report Manager.
So why on earth (or any other planet) don't they work on any other machine
?
Connection string: Driver={Microsoft Visual FoxPro
Driver};SourceType=DBC;SourceDB=\\ecengds001\connections\data\connrdp.dbc;Exclusive=No;NULL=NO;Collate=Machine;BACKGROUNDFETCH=NO;DELETED=NO
a.. An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
a.. Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection) Get Online Help
a.. ERROR [S1000] [Microsoft][ODBC Visual FoxPro Driver]Cannot open
file \\ecengds001\connections\data\connrdp.dbc. ERROR [IM006]
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed ERROR
[01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the
version of ODBC behavior that the application requested (see SQLSetEnvAttr).
Connection string: Driver={Microsoft Visual FoxPro
Driver};SourceType=DBC;SourceDB=\\ecengds001\connections\data\connrdp.dbc
a.. An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
a.. Query execution failed for data set 'DataSet1'.
(rsErrorExecutingCommand) Get Online Help
a.. ERROR [S1000] [Microsoft][ODBC Visual FoxPro Driver]Cannot open
file \\ecengds001\connections\data\service.dbf.
Connection String: Provider=VFPOLEDB.1;Data
Source=\\eukfs01\mis_deve\andersonanalysis\data\;Collating Sequence=MACHINE
a.. An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
a.. Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection) Get Online Help
a.. Invalid path or file name.
Change to use credentials when connecting to datasource. (my user ID and
password)
a.. An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
a.. Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection) Get Online Help
a.. Multiple-step OLE DB operation generated errors. Check each OLE DB
status value, if available. No work was done.
Change to also impersonate user in Windows after connection.
a.. An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
a.. Cannot impersonate user for data source 'DataSource1'.
(rsErrorImpersonatingUser) Get Online Help
a.. Specified method is not supported.
Remember, these work just fine when Report Manager is accessed from
EUK01314.
They do not work if Report Manager is accessed from another machine.
--
PAulHi PAul :-)
I think checking the Deleted box corresponds to SET DELETED ON which
evaluates to DELETED=YES in the connection string so be sure to verify that
you're getting what you want. Sorry I can't help on the ReportingSvcs stuff.
--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"PAul Maskens" <pmaskens@.mvps.org> wrote in message
news:efE5woQwEHA.3872@.TK2MSFTNGP11.phx.gbl...
> Connection string: Driver={Microsoft Visual FoxPro
> Driver};SourceType=DBC;SourceDB=\\ecengds001\connections\data\connrdp.dbc;Exclusive=No;NULL=NO;Collate=Machine;BACKGROUNDFETCH=NO;DELETED=NO|||You are using SP1, right? This looks similar to an issue that we had with
Access databases (MDBs) on remote shares. Is the FoxPro database on the same
machine as the Report Server? At one point, we were incorrectly adding an
Integrated Security property to the connection string but this should have
been fixed.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"PAul Maskens" <pmaskens@.mvps.org> wrote in message
news:efE5woQwEHA.3872@.TK2MSFTNGP11.phx.gbl...
>I have a test system setup in Reading.
> SQL Server is on machine EUK01314
> IIS 5 also is on machine EUK01314
> Reporting services are installed on machine EUK01314
> Visual Studo is on machine EUK01314
> I can create reports that access SQL server data, or via ODBC, or via
> OLEDB to SQL server on EUK01314.
> I can use those reports from our Terminal Server, no problem.
> I can create reports that access Oracle data, via ODBC, or via OLEDB to
> Oracle on a server in Belgim..
> I can use those reports from our Terminal Server, no problem.
> I draw a total blank accessing Visual FoxPro data.
> I can create reports that access VFP data, via ODBC or OLEDB.
> Those reports work on EUK01314 in Visual Studio.
> Those reports work on EUK01314 in IE via Report Manager.
> So why on earth (or any other planet) don't they work on any other machine
> ?
> Connection string: Driver={Microsoft Visual FoxPro
> Driver};SourceType=DBC;SourceDB=\\ecengds001\connections\data\connrdp.dbc;Exclusive=No;NULL=NO;Collate=Machine;BACKGROUNDFETCH=NO;DELETED=NO
> a.. An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> a.. Cannot create a connection to data source 'DataSource1'.
> (rsErrorOpeningConnection) Get Online Help
> a.. ERROR [S1000] [Microsoft][ODBC Visual FoxPro Driver]Cannot open
> file \\ecengds001\connections\data\connrdp.dbc. ERROR [IM006]
> [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed ERROR
> [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the
> version of ODBC behavior that the application requested (see
> SQLSetEnvAttr).
> Connection string: Driver={Microsoft Visual FoxPro
> Driver};SourceType=DBC;SourceDB=\\ecengds001\connections\data\connrdp.dbc
> a.. An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> a.. Query execution failed for data set 'DataSet1'.
> (rsErrorExecutingCommand) Get Online Help
> a.. ERROR [S1000] [Microsoft][ODBC Visual FoxPro Driver]Cannot open
> file \\ecengds001\connections\data\service.dbf.
> Connection String: Provider=VFPOLEDB.1;Data
> Source=\\eukfs01\mis_deve\andersonanalysis\data\;Collating
> Sequence=MACHINE
> a.. An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> a.. Cannot create a connection to data source 'DataSource1'.
> (rsErrorOpeningConnection) Get Online Help
> a.. Invalid path or file name.
> Change to use credentials when connecting to datasource. (my user ID and
> password)
> a.. An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> a.. Cannot create a connection to data source 'DataSource1'.
> (rsErrorOpeningConnection) Get Online Help
> a.. Multiple-step OLE DB operation generated errors. Check each OLE
> DB status value, if available. No work was done.
> Change to also impersonate user in Windows after connection.
> a.. An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> a.. Cannot impersonate user for data source 'DataSource1'.
> (rsErrorImpersonatingUser) Get Online Help
> a.. Specified method is not supported.
> Remember, these work just fine when Report Manager is accessed from
> EUK01314.
> They do not work if Report Manager is accessed from another machine.
> --
> PAul
>|||Thanks Brian.
Sorry for the delay, I've been away in Utrecht.
I started out with the evaluation edition, then installed the SP1 download
onto that.
I had no errors reported during the installation of SP1, so I assume it
really completed OK.
How can I find out what the connection string being used is?
I know what I typed into the Report Manager, but you're implying that
something else is actually sent.
If there's a way to debug this, I'd like to get to the bottom of it.|||Hmm. I'm not sure there is a trace for VFP. Is it OLE DB or ODBC? For SP1,
the string should be the same (we don't add the Integrated Security flag for
other providers). You can make sure SP1 was successful by looking at the
version under http://server/reportserver.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"PAul Maskens" <pmaskens@.mvps.org> wrote in message
news:OZUD5Xx0EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Thanks Brian.
> Sorry for the delay, I've been away in Utrecht.
> I started out with the evaluation edition, then installed the SP1 download
> onto that.
> I had no errors reported during the installation of SP1, so I assume it
> really completed OK.
> How can I find out what the connection string being used is?
> I know what I typed into the Report Manager, but you're implying that
> something else is actually sent.
> If there's a way to debug this, I'd like to get to the bottom of it.
>|||Sorry for the delay, I've been dragged onto a BizTalk project for a while.
Microsoft SQL Server Reporting Services Version 8.00.878.00