Access denied error while doing DrillThrough in OLAP

  • Hi,

    While doing DrillThrough in OLAP, user getting the following error:

    16389 – The operation requested failed due to security problems – resource access error)

    16389 – Access denied to the cube

    But if we add the user to the OLAP Administrator group then user is able to do the drillthrough option.  DrillThrough are enable on the Cubes.

    Any help or suggestions will be much appreciated.

    -SN

     

     

     

     

  • When you say that drill through is enabled, have you done this in both the cube *and* the role/s? 

     

    Steve.

  • Thanks for your response Steve!

    I have enabled the drillthrough on the Cube Role and I don't know if there is any other place where I can enable this. Sorry if I have not understood your question.

    -SN

  • a) open the cube with Analysis Manager - from the menue klick extras - drillthroughoptions - klick the checkbox "drillthrough activated"

    b) rightclick the cube in Analysis Manager - choose admin roles... - rightclick the role - chose access...  - from the cards choose options and ... check "allow drillthrough"

    Ralf

  • Drillthrough is enabled on the cube but still there is access denied on the cube

    -SN

  • Hello.

    Have Your user the rights to access the cube's data source or only the OLAP Administrator Group?

    Let us know.

    Best Regards.




    Fernando Ponte
    factdata.com.br

  • could you please let us know what the user is accessing the OLAP cube with?  Excel?  i have experienced and solved some pretty funky errors generated by users accessing our OLAP solution with ancient versions of Windows and Office.  bringing the operating system and Office installations up to current service packs solved many a problem.

    seth

  • I'm having the same problem, but user was able to use drillthrough in the past.

    I am an OLAP admin and am able to access the cube just fine.

    I think sp4 was recently installed but do not know if this is the cause of the problem.

    If anyone can shed light on this it would be appreciated.

  • Hello pdelpreo.

    1) What about Setht3 questions?

    2) If you installed SP4 on server, did you perform the same on client machine (update client components)?

    Let us know.

    Regards.




    Fernando Ponte
    factdata.com.br

  • Ponte - Excel is the front-end tool, with MDX, ADOMD and ADO recordsets driving the drillthrough functionality.

    Client's OS is either windows 2K or XP.  I am running 2k sp4 and my version of excel is 2003 sp1.  User may be using XP will need to check.

    No installation of sql sp4 was done on the client machine just the olap server.  Interestingly enough like a previous poster stated adding the user to the OLAP admin group on the server will work, but obviously we can't keep it like that.

    This looks like(to me anyway) a break in the security aspect, but who knows.

     

     

  • Hello.

    Thanks for your answer.

    Just check the following.

    Have your user rights to access (perform a select) the cube's data source or only the OLAP Administrator Group?

    This may answer why they were able to drillthrough when inside Olap Admin group.

    Verify cube roles an check if everything is ok.

    Best Regards.




    Fernando Ponte
    factdata.com.br

  • Everything is ok from the OLAP cube permissions side, as well as the OLAP database side. 

    Here is some new info I found out while poking around:

    Using AS 2K from my desktop I attempted to test the role that has the ability to drillthrough into the cube.  So using the built-in cube browser with AS 2k I tried and was unable to do this...  Error was operation requested failed due to security problems - resource access error.

    I then proceeded to log directly onto the AS server via terminal services and tried to test drillthrough for the same role and it worked.

    Strange stuff.

  • Ok.

    So, I guess this is a problem related to the service pack. If you have the SP4 on server I think you may need to update the client objects too, especially Pivotable services.

    Verify if there is diffent versions of msadomd.dll (Program Files/System/Ado) and and msolap80.dll(Program Files/System/Oledb) on both server and client machine.

    Hope this help.

    Regards.




    Fernando Ponte
    factdata.com.br

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply