Error setting up cube report: 'Either the user, IIS APPPOOL\Classic .NET AppPool, does not have access to the Cubes database or the database does not exist.'
Last Updated August 28, 2011
Edit the web.config file in C:\Program Files\Altiris\Workflow\ProcessManager\ by changing the “Initial Catalog=ProcessManagerAnalysis” to “Initial Catalog=<Newly Created Cube database name>”
In Process Manager, setup the connection string:Navigate to Process Manager / Admin / Report / Connection Context List. On the connection context page click the Green Plus on the right side. In the Add Connection Context dialog type in the a Name and Display Name. Choose a connection string template from the Connection String dropdown and edit the string with the correct information for the new Cubes database. () Select OLAP context type from the dropdown box. My connection string that worked was "Data Source=xxxxxxxx;Initial Catalog=Cubes;Integrated Security=SSPI". Context type is OLAP.
Navigate to the Reports and click on the Add report icon; select ‘Add Cube Report’. You get the error message: 'Either the user, IIS APPPOOL\Classic .NET AppPool, does not have access to the Cubes database or the database does not exist.'
The database exists and the user, IIS APPPOOL\Classic .NET has all rights to the database.
In Process Manager when creating and connection context to an analysis database for cube reports you must ensure that whatever user the Process Manager application pool runs as has access to the database.
Using MS SQL Server Management Studio (SSMS) connect to analysis services server and right click server root node and select Properties in context menu. Than go to Security page and click Add and input “IIS APPPOOL\Classic .NET AppPool”. Click Ok to add user and click Ok to close propertirs window. After that you should be able to access the AS database.
Imported Document ID: TECH168264
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe