Getting error as " The selected page could not be opened because the cube could not be found. Please choose a different page ", while accessing books from URL of ProClarity Analytics server RRS feed

  • Question

  • Hi All,

    We have PAS and SSAS installed on two different server. Our requirement is that the users having rights only in PAS must be able to access the books.

    For this we have created one domain user for accessing the cube data, we have added it in cube side and in PAS as well. we have disabled the ananymous access in IIS server and just selected Basic Authentication as we are having PAS and SSAS on two different servers.

    However the users having admin rights are able to access the reports through URL but the regular users having access only in PAS are not able to access the reports.
    They are able to see the Libraries and books but when the try to access the data it giving message like "The selected page could not be opened because the cube could not be found. Please choose a different page "

    Please suggest solution for this.

    Monday, October 5, 2009 9:12 AM

All replies

  • Hi varsha,

    I'm not sure I understand correctly, but it looks like you're using basic authentication for PAS, have a distributed environment, and non-admin users connecting to PAS view do not have access to the cube data.  ProClarity will pass the credentials of the connecting user to the cube.  If the connecting user doesn't have cube access they will see the "..cube could not be found.." message.  You can control what users see which libraries and books by using publishing permissions in PAS.  The Analytics Admin Utility help file has information about this.

    Microsoft ProClarity | This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, October 12, 2009 9:40 PM
  • Hi Sean,

    Thanks for the reply.

    Actually with enabling ananymous account anyone were able to access the PAS , even thoes users who were not having access in the cubes.

    so finally we have remove the anynymous access and finally for avoiding this error we have given access to users in the cubes with dimentional security and issue has been resolved.

    Project is in the good condition now.


    Friday, October 30, 2009 8:57 AM