08-18-2011 02:52 AM
Hi, Im trying to make per-person distinctions for the rows in a the members in a dimension.
I am using the USERID identity-driven property.
it works fine when i open the OLAP CUBE in the SAS EG 4.2, but when i am trying to open it with WRS 4.2 im geting the following error:
An error occurred in processing the report element. Please refresh the page to try again. Contact your administrator if this problem persists.
[a13136480061980.9474379268020503_0_0] שגיאה בעיבוד הדוחUnable to access the OLAP server for cube HAIM_OPERATING.
What could be the reason for that behavior?
08-18-2011 09:01 AM
I am not even sure if this is a problem with member level security. Can you open cube data in WRS 4.2 which is not using member level securty or even completely different cube data?
08-22-2011 04:38 AM
It would be helpful for anyone to answer if you could provide some more information or sample on how the member level security has been applied on the cube. Applying security based on the user id can be tricky and I guess it requires that the member in the dimension has to match the user id.
If you are using the OLAP Cube Studio 4.3, you may use the new batch security tool.
08-22-2011 02:06 PM
Im using SAS BI VERSION 4.2....
First I set up member level security on a dimention ,in the managment console:
When I open the cube in the EG its works good without errors-i get the information that relevant to the user (in this case it is me) who can only see the subset of data he had been granted access to.
But when I opened the cube in the WRS I get the ERROR message: Unable to access the OLAP server for cube.
We can't figure this out, Why in the EG its works fine and in the WRS its not working ?
09-21-2011 10:07 AM
There is a documented issue with SAS Management Console that was fixed in release 9.2M3.
If you are unable to get the new SAS Management Console version, you can manually fix the MDX code to include the higher levels in the dimension.
Included is the SAS Note: http://support.sas.com/kb/36437
Also - to further troubleshoot MDX from Web Report Studio you can turn trace logging on. Included are instructions on how to do this: http://support.sas.com/kb/36728