We have an SSRS report that has suddenly stopped pulling back any data. It was working fine last week, but today it pulls back nothing. The only thing that has changed is we upgraded to Oracle version 19c.
Is there any known issues with Oracle 19c and SSRS?
I can connect to the data sources in the report successfully, but it just won't pull back data when I run the report.
Related
I am looking for some direction on how to solve this SSRS problem. Basically, I am migrating a 2012 sql server to a 2016 server. I am on the last leg which was to ensure the SSRS reports being sent out match the old prod reports.
Two of the three reports being sent out are inaccurate. One report shows up completely missing all numerical data, aside from the layout of the report. The second report has all the data in the correct locations, however it is doubling the data in one of its 3 columns. They are connected to an internal data source.
I transferred these reports by downloading (rdl) them from the Old Prod SSRS and simply uploading them to the new Prod SSRS. I have tried tinkering with the report builder/visual studio but I'm not sure what to look for.
Can you please point me in the right direction of where to look or if there is an easier way to migrate said reports?
I have created an SSRS Report which loads all the columns as expected in my local preview when viewed in Visual Studio. But after deploying to Report Server, it shows 0 in columns that have numeric data. These columns are of Varchar, Big Int data types. Columns that have DateTime, string type show correct data.
I tried below without any success.
Redeploying the report multiple times.
Removing and re-adding columns.
Removing .data files every time I change something.
My SSRS Version is 15.0.19049.0. Can someone please help me understand what might be causing this weird issue and how to resolve it?
Something really strange is happening with SSRS. I have a report which is powered by a stored proc which uses a lot of TSQL and CTE's to set variables ect... I know that there's no problem with the procedure as it runs in SQL and also runs within Visual Studio and returns a full data set. The issue I'm having is on deployment, I can't seem to get the report to return data when running it from the reporting server. The headers of the table and parameter are displayed but just no data.
I've tried the following:
- Deleting the .DATA file
- Clearing cache
- Checking for data source errors
- Checked the report server error log
- Rebuilt RDL and created a different report with the code
I'm clueless on this one, it's something I've never seen before.
Please help.
Much appreciated,
Thank you
Ri
I just created a new table and filled it with data. When I run a simple select query, I can see all the data.
But when I try to build a report in Crystal with this table, I get no data. It doesn't matter if I have other tables included or not, so it isn't a linking issue.
If I right click a field and choose "browse data", I get nothing, which tells me that somehow Crystal can't read the data at all.
I created the table with the same user name/password that I used when connecting to the database from Crystal Reports.
Any ideas?
(If it matters, I'm using Oracle 10g Release 1 and Crystal Reports XI Release 2. We use a direct Oracle connection, not an ODBC.)
I found the problem. I hadn't yet committed the data on the database.
This taught me something about Oracle. I rarely use the "commit" command - but when I have created tables and filled them with data it's been via a "select" statement. Those tables have always worked. This time I did it via the insert all command. I needed to commit for that to work!
I can run all my reports from report studio just fine. So its not a question of query or data or even report specs.
When i call them from URL i am getting no data in the report. There obviously should be data.
We had just upgraded from 8.2 to 8.3 and it is not all the reports... only a select few.
This is serious problem since our users can no longer run these reports.
please help.
-k
This was worked around by recreating the reports from scratch in 8.3 by copying over all the contents using the clipboard and saving it over the old one. There must be something wrong with our reports and the cognos upgrade engine.
This fixes 90% of our reports. we still have some that do not behave correctly.