Categories
- All Categories
- 87 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14.1K Oracle Analytics Forums
- 5.3K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 49 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations Gallery
- 2 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
Issue when entering OTBI
Customer user is trying to enter OTBI using Tools > Reports and Analytics. However, when it hits at Browse Catalog button, following error is throwed:
This is happening in Chrome, Edge and Firefox browsers. Cookies and cache were cleared but got same results.
What could it be?
Answers
-
Is this issue specific to any user or with all the users ?
Also please provide the error message in English language.
Thanks,
Praveen
0 -
Praveen, The "error" part of the message is already in english "This file requires drag and drop framwork" - the first bit just says "an unexpected condition has occurred (internal diagnostic message: Error:..."
Assume this is a reference to the application development framework user experience component.
Sorry i could only find the documentation for middleware 11g R1
1 -
Andres, The "Browse Catalog" button in Tools work area "Reports and Analytics" is pretty much just a link to anlaytics OTBI. So what happens if you go direct in your browser to OTBI instead of using this button. This will help debug if the issue is with the application page in the work area or in OBI.
So in your browser after you have signed into oracle fusion cloud applications as before, but before you selected a work area, just edit the uniform resource locator in your browser to replace everything after the domain ...oracle.com/analytics/ Do you get to the starting page in OTBI as setup in your user preferences in My Account?
0 -
@Nathan CCC Thank you for your help. The thing is that, right now, the error is no further happening. However, it affected all users no matter if they enter through Reports and Analytics or {url}/analytics.
The workaround we applied was entering through {url}/xmlpserver/servlet/home. Browsing using incognito/private mode worked too. We thought it could be a technical issue at that moment, but still don't understand what happened.
If you have any more information, please, let us know. Thanks again.
0