"Unable to access MS Office Project Portfolio Analyzer Olap Cube"

[mcarson]

Hello,

I can see a lot of people have posted this but I think I'm a little different.

I'm running in a single server setup. Project Server, IIS, SQL, SharePoint
and Analysis Service are running from one machine. The OS is Server2003.

I'm able to build an OLAP cube successfully but can't access it via PWA from
a Client PC (Windows XP Pro SP2). I can see with PWA from the Project
Server. I've tested this on the AD also and this will not come up either.

I've modified all kinds of permissions (as suggested in other threads) but
this makes no difference. If I log into the Proj. Server as a user, it works
fine, but if I attempt to do this from our client, it won't work.
Even logged into the client as Domain Admin will not work.

I've run out of ideas. Please help.

-M. Carson

 

[Sameer]

let me share a work around for OLAP's

Create a group in AD, lets call it OLAP View, add all the users to this
group who should access the cube.

In the machine running Project server, go to computer management -- Manage
users and groups-- groups-- OLAP Admins -- add the OLAP View group to it.

Hope this helps

 

[mcarson]

The users are already members of the local OLAP Administrators group on the
Project Server.
I've also added the domain user accounts to the Manage Roles in Analysis
Manager. Nothing has changed.

 

[Rolly Perreaux]

Hello,

I can see a lot of people have posted this but I think I'm a little different.

I'm running in a single server setup. Project Server, IIS, SQL, SharePoint
and Analysis Service are running from one machine. The OS is Server2003.

I'm able to build an OLAP cube successfully but can't access it via PWA from
a Client PC (Windows XP Pro SP2). I can see with PWA from the Project
Server. I've tested this on the AD also and this will not come up either.

I've modified all kinds of permissions (as suggested in other threads) but
this makes no difference. If I log into the Proj. Server as a user, it works
fine, but if I attempt to do this from our client, it won't work.
Even logged into the client as Domain Admin will not work.

I've run out of ideas. Please help.

-M. Carson

Once Project Server has built the OLAP cube, you will need to add User
Roles to the OLAP cube. These User Roles include users and/or groups the
permission to read the data in the OLAP cube, which you'll need in order
to view Portfolio Analyzer Views.

1. Click Start, point to Programs, point to Microsoft SQL Server, point
to Analysis Services, and then click Analysis Manager.
2. In Analysis Manager, expand the console tree, expand to the name of
the cube, right-click Database Roles and click Manage Roles.
3. In the Database Role Manager window, click New.
4. In the Create a Database Role window, complete the configuration by
using the information in the following table and then click OK.

Role name: Type the name of the Role (Portfolio)
Membership: Click Add and select users and/or groups.
Best Practice is to use Groups as it will be easy to
manage later
Cubes: Click the Cubes tab and select the following Cube
names:
MSP_ASSN_FACT
MSP_PORTFOLIO_ANALYZER
MSP_RES_AVAIL_FACT
5. In the Database Role Manager - Contoso window, click Close.
6. Close Analysis Manager.

Good Luck


--
Rolly Perreaux, PMP
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com

 

[mcarson]

I have already followed these steps previously. What I'm running into is an
issue accessing the cube from clients. If I log into the Proj. Server as the
user, I can access the cube with no problems. But when I log into the client
as the user, I'm getting the message about being Unable to Connect.
Its as though the data isn't being transferred to the client.

Again: From the Prj. Server is working perfectly, from the client, not
working.

thanks.

 

[Rolly Perreaux]

I have already followed these steps previously. What I'm running into is an
issue accessing the cube from clients. If I log into the Proj. Server as the
user, I can access the cube with no problems. But when I log into the client
as the user, I'm getting the message about being Unable to Connect.
Its as though the data isn't being transferred to the client.

Again: From the Prj. Server is working perfectly, from the client, not
working.

thanks.

Did you migrate the repository to a SQL database? If not then you will
need to add READ permissions for your Portfolio Analyzer viewers to the
msmdrep.mdb in the following location:

C:\Program Files\Microsoft Analysis Services\Bin

Good Luck
Let us know what happens

--
Rolly Perreaux, PMP
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com

 

[mcarson]

Hi

I changed perms onthe msmdrep.mdb file and this made no difference. I also
created a new database in SQL and migrated the AS repository to it. No
difference there either. :0(

 

[mcarson]

Any more suggestions? This is why I'm so stuck with this.

 

[Rolly Perreaux]

Any more suggestions? This is why I'm so stuck with this.

OK let's review

1. Cube is created
2. Can access the cube via PWA only logged in to the Project
Server/SQL/AS/WSS server
3. Cannot access the cube via PWA on remote machines
4. Migrated the repository to a SQL database

Did you add the Roles and Permissions for the Repository?
This may sound obvious, but is the Project Server/SQL/AS/WSS server
joined to the domain or is it stand-alone?

Try doing this
Add one of your Active directory users in the local Users Group for the
Project Server/SQL/AS/WSS server and then test accessing the Cube
remotely

Let us know...


--
Rolly Perreaux, PMP
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com

 

[mcarson]

Hi Rolly,

I've added perms to the new repository. The Proj Server is on our 'testing'
domain along with our AD server and 2 client PCs.
I've added the domain users into the local Users group but no change.

My head hurts... :0}

 

[Rolly Perreaux]

Hi Rolly,

I've added perms to the new repository. The Proj Server is on our 'testing'
domain along with our AD server and 2 client PCs.
I've added the domain users into the local Users group but no change.

My head hurts... :0}

Mine too :-S

....and you what's worse?
You know it's gonna be a silly little thing we forgot

Sorry :-(


--
Rolly Perreaux, PMP
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com

 

[Gary L. Chefetz [MVP]]

Mcarson:

Rolly has done an excellent job of walking you through the troubleshooting
process, so I'm not sure that I can do any better, but something you said in
your first post troubles me: "Even logged into the client as Domain Admin
will not work." This makes me think that the failure is happening at the
domain level. I'm curious whether you see any telling events in the Server
Security Event Log when you attempt to logon or in the Server Application
Event log. Is there anything showing up in either of these? Could there be
security policies set in AD preventing data access?

 

[mcarson]

I don't believe so. This is still a testing environment, so there has not
been any policy changes made that might effect this. This is a basic server
install. If I log into the Proj Server computer as domain admin, everything
works correctly. If I log into the Client PC as domain admin, it doesn't
work.
I'm wondering if there is an issue with IIS or SharePoint.
I have found an article relating to an HTTP connection to Analysis Services
(279489). I have tried these steps to no success either.
I have tried removing the Proj. Server from the domain and readding it to no
avail either.

 

[Gary L. Chefetz [MVP]]

I'm surprised you don't see errors. You're absolutely certain that you
applied SP3a to both SQL Server and Analysis Services as two separate
installations?

 

[mcarson]

I installed SQL and then installed Analysis Services. I then installed SP3
for SQL and SP3 for A.S.

I have tried the "connecting to A.S. through HTTP" and this doesn't work for
me. When I try to bring up msolap.asp, it says that it cannot be found.

 

[mcarson]

How about another wrench into the equation.
I just created a new OLAP cube from the client PC.
I cannot access this new cube, but I am able to create one.