PS2007: Timephased baseline work (BCWS) gets zeroed out randomly

[PedroJose]

Hi all,

I have started to see this problem and it is causing major headaches. Here
is the scenario:
A project plan has baseline work saved. The BCWS is calculated correctly
based on the status date set. The flags that I have setup to track variance
work correctly. The plan is publsihed and it shows fine in PWA with all
correct values. ALL is OK.

The next day, I open the plan using project pro and all the values for BCWS
are zero even though the baseline values are fine (at least look as being
fine). If I go to the top level of the project and try to update the
baseline from the subtasks, all baseline values get zeroed out as well (so i
hit the undo button...). If i then go to PWA and save and publish the same
plan without having changed anything at all (using edit project properties)
and check in the project. I then go back to project pro and open the same
project plan, and it is all fine!!!!!

This is random in that it doesn't happen all the time, or with all plans...
some are fine sometimes, but others are not.....

NOT GOOD!!

any ideas??

we installed some hotfixes about two weeks ago..... maybe that caused this???

Thanks.

 

[ProjmanZA]

Hi all,

I have started to see this problem and it is causing major headaches.  Here
is the scenario:
A project plan has baseline work saved.  The BCWS is calculated correctly
based on the status date set.  The flags that I have setup to track variance
work correctly.  The plan is publsihed and it shows fine in PWA with all
correct values.  ALL is OK.  

The next day, I open the plan using project pro and all the values for BCWS
are zero even though the baseline values are fine (at least look as being
fine).  If I go to the top level of the project and try to update the
baseline from the subtasks, all baseline values get zeroed out as well (so i
hit the undo button...).  If i then go to PWA and save and publish the same
plan without having changed anything at all (using edit project properties)
and check in the project.  I then go back to project pro and open the same
project plan, and it is all fine!!!!!

This is random in that it doesn't happen all the time, or with all plans....
some are fine sometimes, but others are not.....

NOT GOOD!!

any ideas??

we installed some hotfixes about two weeks ago..... maybe that caused this???

Thanks.

PD ,

Did you status date change by any chance ? the EV is dependant on the
status date you set manually , by default. If you open it the next day
the status date could still be on the previous date.

Andre

 

[PedroJose]

The status date may or may not change, but changing the status date is not
the problem (I fully understand the use of the status date). With the same
status date, the BCWS is zero (again, randomly). If I close the project
without saving any changes, go to edit properties in PWA and save/publish,
and then go an open the same project plan from project pro, all is fine
(status date has not changed).....

any ideas??

 

[PedroJose]

All,

We applied the following hotfixes about 3 weeks ago which is whnen this sems
to have started happening:

http://support.microsoft.com/kb/952289/en-us

http://support.microsoft.com/kb/941426/en-us

http://support.microsoft.com/kb/952000/en-us

http://support.microsoft.com/kb/950284/en-us

http://support.microsoft.com/kb/950816/en-us

http://support.microsoft.com/kb/951169/en-us

 

[Gary L. Chefetz [MVP]]

PedroJose:

What order did you apply them? These are all cumulative updates, so you
should have installed only the latest one for each Project and Project
Server. Installing them out of date order could mess things up if the system
let you do that.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[PedroJose]

Gary, they were installed in numerical order, smallest first:

1. http://support.microsoft.com/kb/941426/en-us
2. http://support.microsoft.com/kb/950284/en-us
3. http://support.microsoft.com/kb/950816/en-us
4. http://support.microsoft.com/kb/951169/en-us
5. http://support.microsoft.com/kb/952000/en-us
6. http://support.microsoft.com/kb/952289/en-us

There is NO documentation saying that these should be applied in any
order...

If in fact these were not applied correctly, is there a way to uninstall
them and re-apply them??

Thanks!!!

 

[Gary L. Chefetz [MVP]]

PedroJose:

Unfortunately, these cannot be uninstalled. Theoretically, they should
detect the existence of prior updates, but I've never hammered the system
enough to find out if this is true or not. That's a lot of scenario testing!
In the future, understand that all hot fixes that are released to the public
are cumulative, so if you have a choice of several, if you install the
latest, you get everything that preceded it. There are rare exceptions to
this rule, but they usually come in the form of one-off fixes for specific
customers, not in generally released updates. Also, you should only apply
hot fixes to your system that were released after your current service pack
level. The hot fix packages eventually become the next service pack, but not
until Microsoft code locks and regression tests them. The order you followed
should not be a problem. I'll report your problem and see if I can stir up
some more information. It sound like this may be a data display problem
rather than a data loss problem, and I'm fresh out of suggestions for you.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[PedroJose]

Many thanks Gary. I agree that it seems a data dispaly problem as the data
in the server is actually intact and good!! (which is why if i save and
publish from the server, it all goes back to normal). Is there a way to
refresh data from project pro?? i.e. hit a button to extract the data as it
sits in the server....??

seems like that is what my workaround is doing (i.e. going to pwa and save
and publish from there and then open in pro)

thx!