Common questions and answers on AS 2K5 permissions for EPM 2007 (thank you David & Steven):
Getting Cube to Build
1. Which application account is responsible for building the cube? Is this the SSP account? The SharePoint Timer Service account?
2. What are the database permissions needed for this account? DataReader on ReportServer? DataReader and DataWriter on OLAPdb?
DataReader on ReportServer, DataReader and DataWriter on OLAPdb (if using SQL as Analysis repository)
3. What are the system permissions needed for this account on the Project Server machines? On the SQL Server machine? On the Analysis Services machine?
Simple user on PS machine. Have not tested on separate SQL/AS machine, but for AS, it needs to be an AS Admin. In some cases I had to put it as a local admin on the SQL server.
4. Do you have a list of common error messages with their solutions?
Allowing Users to View the Cube
1. What permissions need to be setup for users to view the cube? I think part of this stems from the new Analysis Services 2005 security model.
Normally, the right security is added automatically to a defaut AS role during the cube build.
The user added to this role have the Data analysis Project server right. Typically in the Portfolio group
How do you fiind out what the SSP Account is?
I run Project Server 2007 and SQL + AS on two separate servers. DSO and client objects and BC kit are installed properly on the PS server, the AS repository have been installed as a database. I am using a single service account which is db_owner of all the DBs, including the AS Repository, and which is also member of the local group Administrators on each server.
The cube builds correctly, even when started from a client. I can see that the roles' memberships are also correct. I am able to create Data Analysis views while being on the PS machine directly, but not when I am on a client machine. On the Design View page, I get a red message saying that the server (SQL AS, that is) is not a valid Analysis Services server.
There is nothing in the application logs.
There is no firewall or router between the server and the client that could block ports.
Any idea what to look for?
Hi Jess G
We had the same issue and solved it with a good client's IT Pro and found the solution in KB 927159 (http://support.microsoft.com/kb/927159) as well: it's necessary to install Analysis Services 9.0 OLE DB Provider on each client as well running AS on SQL 2005.