Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 17 Oracle Analytics Lounge
- 218 Oracle Analytics News
- 44 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 81 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Report cannot be rendered because of an error, please contact administrator error seen without any c
Summary
Report cannot be rendered because of an error, please contact administrator error seen without any cause
Content
This issue was seen in BIP report in Oracle Business Intelligence 11.1.1.9.0. I did see other threads with the issue of report not rendering but each one of them had a certain cause associated with them. There was a reason there as to what was causing the issue. My problem is that there is no reason provided telling me what is causing this issue.
Issue:
The BIP reports normally run fine without an issue. But at certain times without any changes, it shows an error "The report cannot be rendered because of an error, please contact an administrator." There is no mention of any cause for the error at all.
Workaround:
I did find a workaround to this problem. The report works fine if I go to the datamodel of the report and save the datamodel. I don't even need to make any change. Just open the datamodel and save it. Doing this will fix the issue and report will work fine. But the problem is the issue comes back again and again.
Does anyone have any idea regarding why this is coming up and what needs to be done to make sure this problem is fixed permanently?
Answers
-
Hi Ashish,
As of my Analysis this is the error occurring only in this version.In order to resolve this issue,just go through the below solutions:
> Logout and restart the BI Server an Login again
> Check the server log file if there is any error details resides or not.
> Validate the .xdo file whether it's rendering precisely, especially if you are working on template based reports check the URL attribute is missed or not. If it does just add the .rtf file to it which was created by you.
Thanks,
Pavan kumar
0 -
Hi Pavan,
Sorry for the late response. The main issue regarding the problem is that it doesn't happen always. The report is working fine without any issue for a month or two and suddenly one day i get the error.
I don't even have to open a .xdo report for this error to come up. This happens in the .xdmz file itself as well. I'm working on a query doing some changes. I go to the data tab to view some sample data and save it. And right there this error comes up. I save the data model and go back to the data tab again, it works fine. I'm sorry I don't have the screenshot of this error popping up on the xdmz file itself, but it has happened.
The places where I've faced this error
1. Opening xdo report
2. Opening xdmz file containing the query
3. Trying to schedule the xdo report
0 -
Issue is with one single report or group of reports ?
0 -
Hi Ashish,
It seems to be the error exists within the Query itself.
1. Please check the query precisely and if you had used any LOV's and Parameters find out are they properly invoke the parameters created because i have faced this issue and after precise diagnosis, resolved this issue.
2. One more cause is, if the query not modelled properly, even you can't save the data model too,even if you had you can't find the data in the data tab also...because it will get a query conflict.
3. I'm not sure either you build a query manual or used an interface based (query builder)...just check it.
0 -
Verify the bipublisher.log file during the time frame of the error message and at-least you will get an idea.
0 -
This might be issue with parameter values passing to query , sometimes values are passing with correct data types or with incompatible selection , please run same query same parameter values in toad or sqlplus or sql develoer check
0 -
I have the same issue but in the logs it says null pointer error....see to be related to parametrized LOVs execution.
But some times the same report runs without error....no changes made just works.
We are running OBIEE 12c (12.2.1.0.0)
0 -
Have you been able to resolve this issue? I seem to have it with one of our reports intermittently too.
0 -
expand error detail tab when you see error in report page and post here , Thanks
0 -
Found this today:
There is patch
Patch 21975380: PREVENTIVE FIX: ADD CHECKS FOR NULL IN SELECTPARAMETERDEFINITION">
Patch 21975380: PREVENTIVE FIX: ADD CHECKS FOR NULL IN SELECTPARAMETERDEFINITION
0