Task updates not showing for approval

[Mike]

Question if anyone has seen this. I have a project plan, where after the team
submitted their task updates, we changed the status manager on the plan.
Now, when the status manager open the plan, he gets the warning "Team members
have submitted 63 new updates". The grid shows up - but it is empty - no
task there to approve. If the previous status manager open the plan, same
thing happens - new updates, but cannot approve them. how can we get this
time to get approved on the plan?

 

[bikerjohn]

Try republishing the plan.

 

[Mike]

I did try that - no affect....same behavior after publishing of seeing the
popupbox, but not seeing the tasks to approve in the grid...

 

[bikerjohn]

I have not seen this before. The things I would look at would be,
1: The queue to make sure the plan did publish after changing the status
manager.
2: I would go to PWA, approvals and make sure no rules or filters are in
place.
3: Seach for a specific resouce name from within the approvals area.

 

[DogLBer]

I would also look at the Task Resource tab to see who is the Assignment Owner
is, it may be the original.

 

[Gary Chefetz]

Mike:

I've seen similar symptoms caused by performance issues. I'm not completely
certain whether it's happening on the client side or server side, but it
anecdotal evidence suggests to me that this may be a post Service Pack2
Problem. Have you recently installed SP2?

Try this workaround:

For half of the tasks that are affected by the updates, or at least as many
so as to bring the number of updates going to one manager under 50, have
someone else open the plan other then the current PM and set the status
manager to themselves and publish.
Next, have the original PM try to accept the remaining updates, if that
works reverse the status manager change on the remaining tasks, publish, and
accept the remaining updates.

Are your databases healthy and do you have a maintenance plan in place that
regularly updates database statistics? Is your SQL Server patched to current
service pack and CU levels? I'm not certain that these are potential causes,
but I do see a lot of people in the field who overlook of defer their SQL
maintenance and this can result in performance issues. It's certainly a
factor that you want out of the problem equation.

I've asked Microsoft for suggestions as well.