Is this an installation problem??

I am using the Server Installation strategy, the install is complete (I
think), I have deployed my reports but when I try to view any report I am
getting this error. I have already installed the Oracle Client software
(9.2), and the data source is deployed. Any else get this error before?
HELP!!
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'entpar1- SCARDBA'.
(rsErrorOpeningConnection) Get Online Help
System.Data.OracleClient requires Oracle client software version 8.1.7 or
greater.Did you get a solution? We're having the same problem since we've installed
the oracle db on the reporting services server.
Regards
Antoon
"OriginalStealth" wrote:
> I am using the Server Installation strategy, the install is complete (I
> think), I have deployed my reports but when I try to view any report I am
> getting this error. I have already installed the Oracle Client software
> (9.2), and the data source is deployed. Any else get this error before?
> HELP!!
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Cannot create a connection to data source 'entpar1- SCARDBA'.
> (rsErrorOpeningConnection) Get Online Help
> System.Data.OracleClient requires Oracle client software version 8.1.7 or
> greater.
>

Is there necessary remove named instance alias after...

Hi,
I was told by someone that after install clustering SQL Server 2000 named
instance, it must remove that before installation made the alias. Is that
necessary? What if I leave the alias named instance in the server?
Thanks!
-Chen
Hi Chen,
I hope I'm understanding your question correctly.
It seems that you have installed a SQL 2000 Named Instance on a Windows
2003 Cluster. This requires an alias using Named Pipes for setup to run
properly.
Your question appears to be, do you have to remove it?
Technically, no, you don't have to remove the alias. However, cluster, sql
agent, and other local applications will continue to connect to SQL using
Named Pipes. There isn't an issue with this, but if you have an
application that specifically needs to use TCP, you will want to remove the
alias, or at least change it to TCP.
Hope that helps!
Donna Lambert
Microsoft PSS
SQL Server Support