This issue occurs-
when The user is not properly associated with its security filter due to invalid information in the Essbase security file.
To check if a user is associated with an appropriate filter, follow the steps below:
1. Log into the Essbase Administration Services Console with an administrative ID.
2. Expand the Essbase Servers node to the target Essbase application.
3. Right-click on a database of the application.
4. Select User/Group Access.
5. Check the value of "Filter" column to see if a filter name appears.
If this issue is occurring, "None" is likely to be displayed in the column.
to fix follow the below steps :-
Drop the user information from Essbase security file with the following steps:
1. Launch Essbase MaxL Client.
2. Login to Essbase with the Login command.
3. Run the following statement:
Drop User "<User>@<User Directory>" From Security_File;
4. Exit the MaxL session with the Exit command.
5. Sign into Planning, connect to the relevant application and create a new security filter.
Thanks for your answer. I believe I have found this explanation yesterday, probably also yours?
Unfortunately, it does not help us.
First, under filter column ine EAS console, "Not Applicable" is displayed for each user, and not "None". I don't know if that is actually the same.
After we did all the actions you suggested, we got Java error from above during security filter refresh. Prior to that action, we cannot create security filter for non-admin users. Some generic message appears: "An error occurred while processing this page."
For Adminitrator users, security filter can be created. But if user is Administrator, I don't have to create Security Filter, neither run Security Filter Refresh - everything works.
Just additional information, prior to this restore, we haven't created Security filters at all, and everything worked fine.
I would suggest you to raise an SR with Oracle parallely till the time you find some solution.
Thanks for your reply.
Probably we'll do that. Although I would like to avoid hypercommunication with Oracle about things like "have you switched on your computer", before we got to the real issue.
True i remember we also face the same issue and we have raise the SR with Oracle long back but still i just got update no luck on SR.
We have found workaround solution.
In Workspace click Explore button. Menu changes.
Then Tools / Database Connection Manager and change all connection types from Essbase to Planning. Users now can open their reports!
Of course, this does not solve exact problem. Connection to Essbase still does not work for non-admin user. But it solves our project situation.