Fix For the following Issue: Unable to access the Microsoft Office Project Portfolio Analyzer OLAP c

[berichards]

"Unable to access the Microsoft Office Project Portfolio Analyzer OLAP
cube.
The cube may not exist, or you may not have permissions to access the
cube."

A network engineer at my company has been working with me (DBA) on
this issue. He found that the issue is in the UsrClass.dat and
UsrClass.Log files. I am not sure what these files are used for, or
what affect they have on your system, but by performing the following
steps, we were able to fix this issue.

1. Login as the local administrator or another account.
2. Navigate to the following profile directory. (Replace berichards
with your username)
C:\Documents and Settings\berichards\Local Settings\Application Data
\Microsoft\Windows
3. Rename UsrClass.dat and UsrClass.Log to UsrClass.dat.bak and
UsrClass.Log.bak
4. Reboot your computer.
5. A new UsrClass.dat and UsrClass.Log file will be created.
You will now be able to see views in Portfolio Analyzer

Bill Richards
Senior DBA

 

[NZ Projects]

Also check out

http://support.microsoft.com/kb/822220

 

[Al Himler]

Bill,

I've been plagued with these problems. I'm trying to determine if your
suggestion would improve my situation - is it similar to yours? Here's what
we experience: If logged directly onto the Project Server box using PWA, we
can create cubes, views on cubes, and see the Portfolio Analyzer views. If
we are using a PWA browswer from our workstation on the same LAN though, then
we cannot see the Portfolio Analyzer views and get the error message that you
noted. Is that what you were experiencing and were able to fix with this
change?

Thanks,
Al

 

[Gary L. Chefetz [MVP]]

Al:

It sounds as though you haven't set roles or added users to roles for the
cube. This would explain why you can build and access from the server,
because you're logging in as an administrator that already has rights to
these objects on the same machine.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Al Himler]

Gary - I wish it were the OLAP role, but I've re-confirmed that is set up on
our the OLAP cube.

Here's a recap of my situation in the simplest form:

Environment: Project Server 2003, SQL Server 2005 - both running on the
same server

1) An OLAP Administrators Group exists on the Project Server box and my
account is part of the Group

2) A Role is set up on the OLAP database with full control and I am
included in the set of users for that role

3) There is a Project Server user and I've run PSCOMPLUS.exe; it seemed to
run successfully

4) My account on the Project Server system is set up as a Windows
Authenticated User and I'm part of the Administrators Group on Project Server

5) I am not directly connected to the network that the Project Server box
is on

6) I VPN into the network that the Project Server box is on and then Remote
Desktop into that box

7) At that point I can do full PWA functionality, create cubes, create
Portfolio Analyzer views, and see those views

I think the fact that I can do all of this while logged into the box
indicates that I have all of the permissions and groups set up correctly.

BUT...If I VPN into the network and try to use PWA across the VPN connect, I
can get all of my PWA functions except the ability to view the Portfolio
Analyzer views that I've set up.

It's like the Project Server system is treating my credentials differently
if I'm connecting through PWA from my workstation than if I'm using PWA on
the Project Server box even though I'm logging in with the same
userid/password each time.

As a further test, I asked a user who is directly on the network and is part
of all of the same groups to try to use PWA from her workstation and she gets
the same: "Unable to access the Microsoft Office Project Portfolio Analyzer
OLAP cube" error, so it doesn't seem like the VPN connection is related to
the problem.

Any thoughts on how to fix this or diagnose it better would be greatly
appreciated.

Thanks,

Al

 

[Gary L. Chefetz [MVP]]

Al:

You got a whole lot of issues here:

2003 with SQL 2005 - You have the latest SP for SQL2k5?

Using VPN, does treat your credentials differently. With SQL 2000, you
needed enterprise edtion to make this work. I must confess that I'm not
certain if that is true for 2005.

As far as the "other user" is that person also and administrator on the
Project Server box? Doesn't sound like it.


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com