[PS2007] - Issue and Risk Cube broken after SP2

[godrid]

Hi,

After applying SP2 to the projectserver 2007, the issue and risk cube seems
to be broken. There is only Project List available as the dimension, Issue
List, Issue Category, Risk List, etc are no longer available. In additional,
Issue Count shows empty instead of a number. Has anyone seen this issue?

Regards
Godrid

 

[Gary L. Chefetz]

Too soon to tell if this is a general issue or something unique to your
situation. Let's try some soothing therapy first. First step is to force a
rebuild of the reporting database by making an administrative backup of your
custom enterprise fields and then do a restore. Step two is to run a new
cube build and see if this clears the problem. If not, post back any errors
you encounter during these actions.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[godrid]

Hi Gary,

I have tried to rebuild the reporting database but still have the same issue
with the Issue and Risk Cube. This problem occurs in my customer installation
as well as my in-house VPC after installing SP2 so it does not appears to be
a unique case.

Regards
Godrid

 

[Gary L. Chefetz]

Godrid:

If you can duplicate the problem on multiple unrelated systems, it would
seem to point to a more general issue, so let me run it up the flag pole,
and see if I get some response. I'm not seeing this on our internal systems
with SP2 and I'm away from the office this week and don't have access to my
VPC collection to try to duplicate the issue myself.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[godrid]

Hi Gary,

Thanks for your reply. I have created another instance on my VPC (SP2) using
existing database from another customer who is still on SP1 and the issue and
risk cube is working perfectly. I think it must be due to certain conditions
that the issue and risk cube breaks, I will try to test further and hopefully
could pinpoint the scenario that causes the problem.

Regards
Godrid

 

[Gary L. Chefetz]

Please post back your findings as this is very useful information for the
community and for Microsoft. Thanks.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Gan]

Hi Gary,

Finally found the problem, it got nothing to do with SP2. Those found with
this issue are new instances of project server. In order to have the issue
cube, I create a issue on one of the project workspace and then build the
cube but I did not publish the project prior to that, so in the issue cube I
only get to see project list as the only dimension. Once I publish the
project and rebuild the cube, the issue cube will have all the dimensions
(Issue List, Issue Category, etc) that I am looking for.

Sorry for the trouble. My opinion is that a publish should not be needed
before building OLAP cube if new issues are being raised in the project
workspace.

Regards
Godrid

 

[Gary L. Chefetz]

Well, this is easily explainable. The cube is built from the Reporting
database. The reporting database gets populated with project data only on a
publish action. Do you really think that any user should be able to publish
project data from directly from a Project Workspace? What if the Project
Manager doesn't agree with the issue raised? The out-of-box construct
assumes a more tightly controlled environment by default. You can certainly
loosen this up by automating publishing programmatically. I guarantee that
lots of PMs would not agree with your closing comment as most PMs are
control freaks of sorts, as it comes with the territory. Bottom line,
there's no one right answer to this problem, there's only what works for
your organization. It sounds as though you need to get your PMs to attend to
changes in the project more frequently, or you need to consider the
automation option.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com