×
גיל
Hi,
Trying to fix the problem in the title (old post about it at
http://www.microsoft.com/communitie...&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
) our IT team installed SP2 WITH June CU on the SERVER. Project CLIENT were
upgraded to SP2 only, NO June CU.
After upgrade, a team member reported 4 hours of actual work, in one day, on
a fixed-units task. After accepting the update, the PM saw on
Project-Proffesional that the actual was modified to 2.5556 and 1.4444 or
something similar, across two days, meaning, the issue is still here.
Questions asked:
Should the June CU be installed also on all Project Clients? Will this make
the problem go away (I am asking that because I didn't see this issue listed
on the June CU KB)?
If so, How can I obtain the special tool mentioned in Ryan and Skip W posts,
which can sync the actuals back to what is showing up in the transaction
logs?
Your suggestions are wellcome.
Gil
Trying to fix the problem in the title (old post about it at
http://www.microsoft.com/communitie...&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
) our IT team installed SP2 WITH June CU on the SERVER. Project CLIENT were
upgraded to SP2 only, NO June CU.
After upgrade, a team member reported 4 hours of actual work, in one day, on
a fixed-units task. After accepting the update, the PM saw on
Project-Proffesional that the actual was modified to 2.5556 and 1.4444 or
something similar, across two days, meaning, the issue is still here.
Questions asked:
Should the June CU be installed also on all Project Clients? Will this make
the problem go away (I am asking that because I didn't see this issue listed
on the June CU KB)?
If so, How can I obtain the special tool mentioned in Ryan and Skip W posts,
which can sync the actuals back to what is showing up in the transaction
logs?
Your suggestions are wellcome.
Gil