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,
Cali
tancatOracle DeveloperAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
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..
0
tancatOracle DeveloperAuthor Commented:
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!
0
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
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.
0
tancatOracle DeveloperAuthor Commented:
This is what I ended up doing - I installed MSSS Data Tools 2015, including SS Reporting Tools 13.0.1400.361, and I also looked up MSSS 2016 Feature Pack, and installed ENU\x86\ReportViewer.msi.  I tried to also install ENU\x64\SQLSysClrTypes.msi  but I have several other versions that interfered and I did not want to start uninstalling stuff.  I roughly followed the advice at this site: https://stackoverflow.com/questions/40586371/ssdt-installer-missing-prerequisite-sql-server-2016-system-clr-types.  

So far, this seems to be working correctly and I can now preview my colleague's reports and he can preview mine.

Thanks!
Cali
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.