|
| Hi,
I have developed various datamarts with the MS Analysis Services
platform, to which I tried to restrict the access using Analysis
Services dimension level security model.
Unfortunately, it didn=B4t work, so I looked for a solution in Internet
and I have found the following page, which describes exactly what
happens to me.
http://support.microsoft.com/defaul...kb;en-us;816480
The page explains that it is a bug of the software and it was first
solved with SP4. However I have the SP4 installed both on SQL Server
and Analysis Services and the problem still ocurres. Moreover it fails
only with one dimension - I use the same type of restriction with other
dimensions and it works fine.
The only difference between the correct dimensions, and the one that
fails, is that the latter has more than 64.000 members on the leaf
level, thus it needed to be grouped.
I would like to comment other thing. I am not trying to use any
user-defined function in the MDX expression. I just check the members
that should be visible to particular user. However, I obtain the same
error message that the one listed on the FIX page.
The scenario is as follows. I tried to concede the access permission to
the first level member (there are two - one should be visible, the
other not). When I save the changes I receive the error message of the
FIX I've already mentioned where the MDX expresion is like:
[dimension].[firstlevel].&[1]
This expression is created by An. Manager when I check the proper
checkbox on the Basic tab. I changed the expression to
[dimension].levels(1).&[1]
The error I obtain in this case is the same, but, what's even more
weird, the MDX expression in the error message does NOT change and it
still is:
[dimension].[firstlevel].&[1]
I have checked this MDX expression with the MDX Sample Application and
it works fine.
Did any one of you have a similar problem? What did you do to solve it?
Thanks in advance.
Best regards,
Ewa
|
|