Project 2007 Plan not showing actuals received from PWA

D

Dots

I have several users who, after they approve task updates, do not see the
actual hours just approved. If we do a Task Usage view, the actual hours
columns are blank. What is causing this and how do I correct it. We are
using Project Pro SP1 2007 and MOSS/Project server 2007. PLEASE HELP!
Thanks.c
 
M

Marc Soester [MVP]

Dots, the first thing I would do is check the Queue. If a user has updated
their task and submitted it and the PM has approved it and republishes the
project again, the project schedule should be up to date. A reason why this
doesnt happen is if the job is still in the queue.
go to server settings > Manage Queue and see if there are any jobs pending.
If so try to restart the jobs and if this fails I would restart the queue
service which often fixes the queue been hung.
Hope this helps
 
D

Dots

Marc,
That is the strange thing here. The queue showed all updates as successful,
nothing hanging in the queue. I even tried to set publish to No, republish
and then set to Yes and republish again. The hours from the import are
reflecting Mon and Tues, but not Wed thru Friday. This is happening on 2
project plans that I know of.
 
J

James Fraser

I have several users who, after they approve task updates, do not see the
actual hours just approved.  If we do a Task Usage view, the actual hours
columns are blank.  What is causing this and how do I correct it.  Weare
using Project Pro SP1 2007 and MOSS/Project server 2007.   PLEASE HELP! 
Thanks.c

You may be encountering a bug. The fixes below are listed as part of
the "August Cumulative Update" at
http://support.microsoft.com/kb/956061

Excerpted fixes that may help you (there are another ~30 fixes listed
above that I'm not including here.):
• After a resource updates a task, the updated actual billable work is
not displayed in the cube report.
• The work that is accepted on the Task Updates page may not appear in
the project when the update is applied.
• When all plans are successfully published, actual work information
is missing in the reporting database.
• In PWA, you lock a task on the Close Tasks to Update page. However,
you can still add that task by using the Add Tasks feature on the My
Tasks page and submit actual work.
• When resources submit actual work to their project managers, the
first day of the timephased actual work is moved into a different
week.
• After you apply hotfix 941426, the actual work that was accepted by
the project manager is not updated into the project plan.
• When you post actual work for a single resource for a task that has
more than 5 resource assignments, the update to Project Server fails.
Additionally, the Unified Logging Service (ULS) throws the following
exception:
Exception occurred in method Statusing.UpdateStatus
System.ArgumentException: These columns don't currently have unique
values.
• A project manager accepts the actual work. However, the actual work
is not updated into the project plan.


Despite the name, this update was very recently released. Proceed
cautiously and with lots of testing.


James Fraser
 
D

Dots

James,
So this update is after the
infrastructureupdateformicrosoftofficeproject2007-kb951547-fullfile-x86.exe
update? I did apply this 951547 and all seemed fine up until last week or
so. ??
 
J

James Fraser

James,
So this update is after the
infrastructureupdateformicrosoftofficeproject2007-kb951547-fullfile-x86.exe
update?  I did apply this 951547 and all seemed fine up until last weekor
so.  ??

Yes, this update is after the infrastructure update and the recommend
(maybe require?) SP1 and the infrastructure update to be applied
first. I don't know that your problem is fixed by this update, but
some of the fixes seems to match your problem very closely.


James Fraser
 
D

Dots

Thanks James. I currently have a call into Microsoft to discuss. Apparently
you cannot download the update except by contacting MS directly. I also want
to discuss with them why this issue has not appeared until recently...

Dots
 
D

Dale Howard [MVP]

Dots --

Forgive me for "jumping into" this thread. I hope you will share the
results of your call to Microsoft with us. The problem you are describing
was a pre-Service Pack 1 bug in Project Server 2007. The bug is supposed to
be fixed by SP1. I can't imagine why you are seeing this bug again,
especially since you seem to be current on the latest updates to the tool.
So, please let us know what you find. This information could be very
valuable to everyone in this group. Thanks in advance!
 
G

Gary L. Chefetz

Dale:

There were actually some new bugs that caused similar behavior that were
introduced in patches after SP1. I think that the IU/CU combination is a
good idea for most systems. Reports are now coming in from the field.

--
----------
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
 
M

Marc Soester [MVP]

Interesting, sounds like MS re-introduced an old bug :) Lets hope SP2 comes
along soon so that you dont need to install x amount sepereate packages.
Dots, as Dale suggested it would be great if you could let us know what MS
comes back with
Thanks
--
Marc Soester [MVP]
National Manager: EPM
http://marcsoester.blogspot.com
 
B

B Weed

My installation has been seeing this issue pre SP1 and post SP1 and I
have been feeding Microsoft example after example of this happening.
Since March, they have said that the August CU was the one that would
address the issue and we got it and the Infrastructure Update
installed on Sept 13. So far, we are seeing postive results. The one
negative is that the time that is missing doesn't resolve with a
publish following the updates. For us, it's been a manual process of
"Cleaning Up" projects that have encountered the issue. We are also
not seeing the issue after the update of Actuals not coming into the
plans in sync with the way they have been entered in timesheets.

There is a ApplyMissedWork tool and a ReApplyActualWork tool that you
may also want to request from Microsoft that does try to address the
missed time.

I definitely will yield to the experts here on whether or not these
are good ideas.
 
D

Dots

All,
I will discuss both the Tools and the Aug hotfix with my contact and let you
know results. Thanks for the tips here, I appreciate it much!

D.
 
M

MikeRMT

This thread seems to match what I am experiencing at the moment, has anyone
anything new to add to it? Is the august update still the best fix?

Thanks

Mike
 
D

Dots

I installed the august hotfix without issue and ALL of my actual hours are
now working properly.
 
S

Sinister

I'm having the same issue. The project manager accepts updates entered by
users under their My Tasks section. After the updates have been accepted and
the qeue shows that it was successful he will then go into Project Central
only to find that no Actual Hours are listed.

Here's something that might shed some light on the matter. I can select the
project and click on the "Edit Project Properties" link I'll get a message
saying that the project has unpublished data. Once I click on the "Save and
Publish" button the message goes away and now the actual hours appear in
Project Central. It's nice to know that this fixes the issue, but I can't go
into 50 schedules everyday and publish them individually.

We applied the December cummulative update. That should have included the
August update correct? Would it hurt to apply the August update even after
we've already applied the December cummulative update?

Thanks in advance
 
G

Gary L. Chefetz

S

Sinister

So the PM accepts the updates in PWA and then has to go through each one of
those schedules individually and publish them? I thought that's what you are
doing by accepting the updates through PWA.

And do you know if it's okay to apply the August hotfixes if you've already
applied the December Cumulative?
 
G

Gary L. Chefetz

When you accept updates, it updates the project plan. At that point the
system expects that the PM has other updates to do. What about tasks that
were supposed to be done, but didn't get worked on. Is it your
organization's practice to leave those tasks scheduled in the past?
Typically, a planner has quite a bit of work to do to bring a plan up to
date after applying updates. You could automate a publish job on your
projects every night, but you're certainly not approaching best practices
here.

It continues to be my opinion that you should install updates to Project
Server when they become available.

--
----------
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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top