OLAP Cube Proble on Small Server Farm

[Jerry]

Hi,

I am unable to see project server portfolio analyzer views. My cube is
build successfully but i get the following error.
----------------------------------------------------------------------------------------------------------------------------------
Unable to access the Microsoft Office Project Portfolio Analyzer OLAP
cube.

Possible Cause : The cube has not yet been built, or it is currently
being generated, or you do not have permission to access the cube.
Safety settings on this machine prohibit accessing a data source on
another domain
-----------------------------------------------------------------------------------------------------------------------------------

Here is my configuration.
I have one machine where project server 2003 is installed.
Project server database is installed on 2nd machine that SQL Server
2005.
I have Analysis Services 2000 installed on project server 2003 machine
and i have migrated the repository from SQL server 2005 to SQL Server
2000 Analysis Services. I have one domain admin who has full rights on
both the machines and SQL Server 2005.
(Both machines are Windows Server 2003)
1. Can i run my OLAP Cubes by the architecture where my Database is on
SQL Server 2005 and My Analysis services are on SQL Server 2000.

What kind of configuration is required. Why my current configuration
is working.
Please do help me
Thanks and Regards,
JERRY

 

[Paul Conroy]

There's no need to run AS2000, as Project Server will use AS2005.

Steps to build project server 2007 on AS 2005

SQL Server 2005 SP should be installed.

Setup Requirements

A) Application Server
The Application Server must have the Analysis Services DSO (Decision Support
Object) component installed.

If you will build the cubes in Analysis Services 2000, this component can be
obtained by running the installation setup for Analysis Service, and
selecting the Client Component to be installed.

If the cubes will be built on Analysis Services 2005, you need to install
the following components:
1. Microsoft SQL Server Native Client (sqlncli.msi)
2. Microsoft SQL Server 2005 Management Objects Collection
(sqlserver2005_xmo.msi)
3. Microsoft SQL Server 2005 Backward Compatibility Components
(SQLServer2005_BC.msi)

These components can be downloaded from the Feature Pack for Microsoft SQL
Server 2005 - April 2006 release, available on:
http://www.microsoft.com/downloads/...aa-b4bd-4705-aa0a-b477ba72a9cb&DisplayLang=en

B) Analysis Services
If running Analysis Services 2000, the following setup steps are required:
1. Add the user account running the Queue service at the Application Server
to the OLAP Admin Group
2. Give administrative access to the OLAP Admin Group to the “<Installation
Directory of AS 2000>\bin†folder

If running Analysis Services 2005 (Service Pack 1 is required), you need to
setup a repository for DSO to write to. If you have migrated the Analysis
Services 2000 repository to the Analysis Services 2005 server, no additional
steps are required.

The instructions below detail how to migrate the repository or create a new
one:

1. On the server with Analysis Services 2005 installed, go to \Program
Files\Microsoft SQL Server\MSSQL.2\OLAP

2. Create a directory called ‘DSO9’
3. Share it as MSOLAPREPOSITORY$

4. Give the SQLServer2005MSOLAPUser$<MACHINENAME>MSSQLSERVER administrative
access to the share

5. Copy the file msmdrep.mdb into the DSO9 directory previously created
This file can be found in the Analysis Services 2000, and by copying it to
this directory you will be migrating it to Analysis Services 2005. If you
don’t have an Analysis Services 2000 server, you should create a new (empty)
..mdb file and add it to the DSO9 directory (you should use the name above or
edit the <DSO> section below).

6. Navigate to the \Program Files\Microsoft SQL Server\MSSQL.2\Config
directory

7. Edit msmdsrv.ini file and replace DSO section with the following (make
sure to fill out the appropriate <MACHINENAME>):

<DSO>
<RemoteRepositoryConnectionString>Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=\\<MACHINENAME>\MSOLAPRepository$\msmdrep.mdb;Persist Security
Info=False</RemoteRepositoryConnectionString>
<RepositoryConnectionString>Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\Program
Files\Microsoft SQL Server\MSSQL.2\OLAP\DSO9\msmdrep.mdb;Persist Security
Info=False</RepositoryConnectionString>
<RemoteLocksDirectory>\\<MACHINENAME>\MSOLAPRepository$</RemoteLocksDirectory>
<LocksDirectory>C:\Program Files\Microsoft SQL
Server\MSSQL.2\OLAP\DSO9</LocksDirectory>
</DSO>

Ensure that each tab is in one entire line (not wrapped) on the file.

For more information about creating a repository, read the appropriate
Analysis Services documentation:
• http://msdn2.microsoft.com/en-us/library/ms403364.aspx
• http://msdn2.microsoft.com/en-us/library/ms403370.aspx

 

[Lene]

I think that perhaps you should check that you and your users have
access to the cube.
I have seen the error several times and all I do is to add the group
projectServerUsers to the cube

You can find several directions to that issue in this group.
Just google your error

Paul Conroy skrev: