Hello everyone,
in my environment with Project Server 2013 / SQL Server 2012 SP1, I am experiencing a strage behaviour with OLAP cubes.
The cubes build correctly, the data is correct, but the sole cube role ProjectServerViewOlapDataRole is empty. That means nobody has access to the cubes except SSAS administrator who access to everything.
The setup is Project Server 2013 / SQL Server 2012 SP1, ASAMO/ASADOM/ASOLEDB from the 2008R2 SP2 feature pack are installed (see http://blogs.msdn.com/b/brismith/archive/2012/11/12/project-server-2013-requirements-to-build-an-olap-cube.aspx). The issue occurs on single box SP/PS/SQL, on single box with domain controller and on 1SP/PS+1SQL-system. It occurs with PWA-instances in SharePoint mode and Project Server mode. There is a PWA Admin, a Portfolio Reader/Manager, an unattended reader account with only the View OLAP permission, none of them have access to the data.
The web application the new default (claims based, underlying Windows Kerberos authentication). In the pub.MSP_Resources table of the PWA database, both WRES_ACCOUNT and WRES_CLAIMS_ACCOUNT are in the "i:0#.w|domain\user" format. WRES_AD_GUID is set for most users. Is that the reason that PWA might not find the users to add to the cube?
So, basically my question is: Does anyone else have this issue, or is your OLAP role filled correctly? In case it works for you, what are your specifications? Are you doing something different to my actions? How does the table look in your scenario?
Kind regards,
Adrian