Project Cube Build Service Analysis Services server lock time out
Published: June 10, 2010
Applies to: Project Server 2010 | Project Server 2013
Element ID / Rule Name: Project_Cube_Build_Service_OLAP_Processing_Failure
Summary: After the Microsoft Project Server cube structures are built, the Microsoft SQL Server Analysis Services (SSAS) server processes the cubes in order to obtain the data from its data source, which is the associated Project Server Reporting database. This processing also obtains any customized data that was added to the cubes.
Cause: Several things could cause the SQL Server Analysis Services database processing to fail. The most common case is that the Analysis Services server does not have access to the data in the Project Server Reporting database. This could be the case if the computer that is running SQL Server and that is hosting the Reporting database and the Analysis Services server are on separate computers and the SQL Server Analysis Services is not running under an account that has at least read access to the Reporting database. This might also occur if there is a custom extension to the cubes that attempts to read data from a source without having sufficient permission.
Possible resolutions include the following:
Use the ULS logs to verify that the processing failure is caused by permission problems.
Resolve permission problems:
In the computer where the Analysis Services server is running, ensure that the account that is used by the computer that is running SQL Server Analysis Services is a Windows domain account instead of in a service account, such as Local System.
Ensure that this account has read access to the Project Server Reporting database from the site on which you want to build cubes. Note that, if there are multiple sites building cubes on the same Analysis Services server, the Windows domain account that is used by the SQL Server Analysis Services should have read access to all corresponding Project Server Reporting databases.
If processing fails but the credentials are configured properly, go directly to the Analysis Services server and manually attempt to process the database. This action will provide you with detailed information about where the failure is occurring.