Hello Ryan,
I was interested in your comment "In P2K3, there is a design flaw that does
not keep proteted actuals in the MSP_WEB tables in synch with the MSP tables
even if you have your server set up to ensure that the two are in synch.
(This issue can be caused by ODBC errors, DCOM errors, etc) MS support is
working on a hot-fix for this."
Can you expand on this in more detail please ? We haven't come across this
issue (and we have been operating with Project Server 2003 using managed
time periods for several months now) so I am curious as to whether this
"design flaw" is specific to a particular setup or whether it is indeed a
design flaw. If it is, as you suggest, a design flaw, presumably there is
some information about this on MSDN or an article about this ??? Can you
provide a reference or URL ?
Are there circumstances in which this flaw manifests itself ?
I also haven't seen any other reference to this in the NG - and this can't
be the first time this issue has cropped up if it is indeed a flaw !
Many Thanks
Gary
Ryan said:
Eric:
If you are using P2K or P2K3 these views can become out of sync for a
number of reasons. One of which is a design flaw(allowing the PM to change
%, actual work, remaining work in the client and then publishing) in the
server product that in 2K allowed for the MSP and MSP_WEB tables to become
out of synch with no method of synching from MSP_WEB which has all of your
actual information to the MSP tables. Since the Analyzer view feeds from the
MSP tables, you will see the incorrect values.
In P2K3, there is a design flaw that does not keep proteted actuals in the
MSP_WEB tables in synch with the MSP tables even if you have your server set
up to ensure that the two are in synch. (This issue can be caused by ODBC
errors, DCOM errors, etc) MS support is working on a hot-fix for this.
Sorry I can't provide the magic bullet to fix your problem, but sometimes
it helps to know why it's happening.