Project Center not showing progress

[agriffin]

Calculation is set up for Automatic.

There is one PM that can self-publish, otherwise the system is pulling in updates from the accounting system and loading them into project using the PSI on a nightly basis. These updates from the accounting system are published through the PSI.

[ssanderlin]

Originally Posted by agriffin

Calculation is set up for Automatic.

There is one PM that can self-publish, otherwise the system is pulling in updates from the accounting system and loading them into project using the PSI on a nightly basis. These updates from the accounting system are published through the PSI.

Ah... OK. That makes more sense. I assume your code is auto-approving the updates as well -- meaning there is no interaction with Project Managers at any step in this process?

[agriffin]

Correct, there is no interaction from the PM's at any step during this process.

[ssanderlin]

Originally Posted by agriffin

Correct, there is no interaction from the PM's at any step during this process.

OK. I think that you are running into a calculation issue -- meaning that for whatever reason, the project rollup calculations are not being done when you fully automate the submission, approval, and publish processes with the PSI.

If you check the either the MSP_EpmProject table or the MSP_EpmProject_UserView view in the Reporting database for a ProjectUID/ProjectName in which you are experiencing the problem, are either the ProjectRollupsAreState or ProjectCalculationsAreStale columns set to 1 (True)?

[agriffin]

There was no MSP_EpmProject_UserView table, but there was a MSP_EpmProject table. I looked in this table and both of those columns were set to 0 for project. All of the projects are set to 0 for these 2 columns.

[ssanderlin]

Originally Posted by agriffin

There was no MSP_EpmProject_UserView table, but there was a MSP_EpmProject table. I looked in this table and both of those columns were set to 0 for project. All of the projects are set to 0 for these 2 columns.

MSP_EpmProject_UserView is a View, not a Table.

OK... So, that's fine. I didn't expect them to be 1, since ProjectRollupsAreStale is supposed to only be used for master project / sub project relationships and ProjectCalculationsAreStale is supposed to be set when the Calculation is set to Manual and the Project is published -- but I figured we should check

I'd like to try one more thing... I don't think it will work, but it's worth a try. In one of the projects, uncheck the Actual Costs are always calculated by Microsoft Office Project option in Tools>Options>Calculate. Then, see if the rollups calculate correctly when the PSI publishes.

I think it's obvious that the Project rollup is not being recalculated, but I'm not sure why -- according to the documentation, this should occur.

If my above suggestion does not resolve the issue, you may want to consider using the Project Pro Object Model to open, recalculate, and save the project before you call your Publish method... I don't believe the Server-Side Scheduling Engine is exposed through any interface, so I don't think you can resolve your problem by forcing it to calculate.

[agriffin]

Unchecking the Actual Costs are always calculated by Microsoft Office Project option in Tools>Options>Calculate did not fix the problem.

[ssanderlin]

Originally Posted by agriffin

Unchecking the Actual Costs are always calculated by Microsoft Office Project option in Tools>Options>Calculate did not fix the problem.

I think we can all agree that the Project Rollup calculations are not being calculated properly, but none of us are sure why. I'm fairly confident that I've led you down all applicable paths that are low-impact.

I do know that there were some issues with PSI Publishes that were resolved in SP1 (and I believe in the Post-SP1 Hotfix Rollup), but I do not have any specific information. I also know that there are some lingering issues that do not have a public fix as of yet -- but, I do not know if this issue is one of them since I do not have access to Microsoft's internal Bug Database.

I would recommend that you proceed in this manner:

1. Deploy SP1 to Client and Server
2. Deploy Post-SP1 Rollup to Server
3. Contact PSS to obtain the Client Post-SP1 Rollup
4. Apply Post-SP1 Rollup to Client
5. Conduct further testing to determine if the issue has been resolved
   1. If so, then please let us know that you resolved your issue
   2. If not, open a ticket with PSS. They may be aware of this issue and might have a hotfix.

If you are unable to come to a resolution, I would recommend that you build an addition onto your Publishing service to leverage the Project Pro object model in order to recalculate the rollups.

Just so you know, I have also reached out to my Microsoft contacts on this issue to see if they have encountered anything similar. I cannot guarantee an affirmative response (or any response at all), but anything I recieve will surely be passed along to you.

I will be happy to continue working with you on this issue, but honestly I believe I've done all that I can do without being in physical contact with the code and your environment. Please consider deploying SP1 and the Post-SP1 Rollup for both Client and Server so that we can either identify or eliminate them as resolutions.

In any event, please continue to keep us apprised of your progress. I know we would all be very interested in any resolution you find, especially one that involves a hotfix -- or at least a ticket and/or internal resolution number so that others experiencing similar issues can reference it.

[ssanderlin]

Originally Posted by agriffin

Unchecking the Actual Costs are always calculated by Microsoft Office Project option in Tools>Options>Calculate did not fix the problem.

By the way... specifically what PSI methods are you calling to submit updates, accept updates, and publish?

[agriffin]

I installed SP1. This has not fixed the problem. It is really odd b/c it is only 1 specific project that is not getting updated on the PWA.

I am using QueueUpdateProject, QueuePublish.