Avatar of tancat
Flag for United States of America asked on

Problem previewing reports in VS 2015/2017 using SSRS and Oracle 12c

I have been tasked with creating some reports out of VS and SSRS from an Oracle 12c database.  I am an Oracle developer but I don't know much about VS or SSRS.  I have both VS 2015 (14.0.25431.01 Update 3) and 2017 (15.7.5) installed and I have installed ODTwithODAC for 12c.  I have also installed SSDT for both VS 2015 and VS 2017.  

Using VS 2017, i have created a new project but I am unable to create a shared data source.  As soon as I select Oracle Database in the Type drop-down, the Edit button next to the connection string becomes grayed out.  

Using VS 2015, I have cloned an existing project that works fine for my colleague.  However, when I first tried to load the project I received a message that the version of the report server project is not supported and the project must be upgraded.  If I say no, then the project won't load.  If I say yes, the project loads and everything seems to be ok. However, when I try to Preview an existing report from the project, I receive the following error:
"An error has occurred during local report processing.  An error has occurred during report processing.  An attempt has been been made to use a data extension 'ORACLE' that is either not registered for this report server or is not supported in this edition of Reporting Services."  There is nothing in the Error List when this happens.  

The only difference between my colleague's setup and mine is that he has SQL Server Reporting Services 14.0.806.134 and I have 14.0.1012.227.  However, I cannot find his specific version online anywhere to download it.  

I am able to query the database if I go to the Dataset under Report Data, right-click and select Query and Run the query - no errors and data are returned.

Any ideas on how to resolve either of these problems?  I was told that we have to use VS 2015 because we get an error with SSDT for 2017.  Well, I'm getting an error with 2015 so neither one seems to be better than the other.  

Is any additional information needed to solve this?

Thank you,
Microsoft Server OSMicrosoft SQL ServerOracle DatabaseSSRSMicrosoft Visual Studio

Avatar of undefined
Last Comment

8/22/2022 - Mon
Raja Jegan R

Just a thought, kindly try applying the latest Service packs for SQL Server involving both Database and SSRS engines in the currently working one to see whether it still works..
Ideally it should work and once verified, then install the latest Service packs in the machine where it is not working so that now both are in the same version.

Also try using VS2017 across both the servers to verify whether it the project is able to work evenly across both machines.
We would also need to take care of Oracle Driver versions to be installed evenly across both servers/machines to check it out once..

Apologies for the late response; I had to go out of town unexpectedly this weekend.

My colleague and I are at this point only working on our computers, not on the server.  If I've checked out the code and want to preview it in VS, that is on my computer, correct, not the server?  We are not using SQL Server, only Oracle.  

We don't want to change my colleague's setup at all since it is the only one working.  As far as I know, the only difference between the oracle client and ODAC versions, the SSDT versions, and the VS versions is the SQL Server Reporting Services version (which I think is part of the SSDT package but I could be wrong about that).  

At one point I did update to the latest of everything with ODAC, SSDT, and VS, but I still received the same error so I went back to my previous setup since it matches my colleague the closest.  

Thank you!
Raja Jegan R

No issues, if I understand correctly you are using SSRS reports to fetch data from Oracle database..
May I know where is ur ReportServer and ReportServertempdb databases located, ideally it would be in a SQL Server instance and kindly share those details along with SP and version information.
And your colleague is having latest SP for SQL Server 2014 installed out whereas yours appears to be RTM version and hence try to apply the latest SP for SQL Server 2014 and see whether it helps or not.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.