S
Scott Robertson
Hi,
Im having quite a bit of 'fun' latelly with our Project Server 2003
SP2a and Project Professional 2003 SP2 Enterprise installation.
I have a Microsoft Support call open for some of the issues, but any
help or advice that could be offered would be greatly appreciated.
The big 2 issues I have are:
1. Our method of timesheet complaince follows the publicised method re
MVP's, i.e.
http://www.projectserverexperts.com/Shared Documents/Determinetimesheetcompliance.htm
Recently we have run timesheet complaince reports on the whole company,
the first a fortnight ago and again at the end of last week.
The one at the end of last week shows gaps in returning hours that were
not present the first time we ran the report and are easily
attributable to one plan (we had a deadline and most of us swamped onto
that project during the first 2 weeks of the year).
To complicate matters further I can return a pivot table for the
affected resources for this time and see their recorded actuals (which
I know are in this project). I can also go into the plan itself
(through project and see sensible looking actuals).
2. A hanging or crashing administrative plan. Basically, its a huge
plan where we capture all our overheads, it went through a stage of not
updating actuals in the spooler. After about a week of this it crashed,
I luckily (after about a week of tinkering with it) managed to save an
offline mpp of it, backed the spooler up to xls and reimported and
manually rekeyed all the spooler data (Prestore.exe didnt seem to fix
the issue). This has improved the situation greatly but the plan still
shows signs of instability... I'd like to make it stable!
Again any help or assistance would be greatly appreciated.
Scott
Im having quite a bit of 'fun' latelly with our Project Server 2003
SP2a and Project Professional 2003 SP2 Enterprise installation.
I have a Microsoft Support call open for some of the issues, but any
help or advice that could be offered would be greatly appreciated.
The big 2 issues I have are:
1. Our method of timesheet complaince follows the publicised method re
MVP's, i.e.
http://www.projectserverexperts.com/Shared Documents/Determinetimesheetcompliance.htm
Recently we have run timesheet complaince reports on the whole company,
the first a fortnight ago and again at the end of last week.
The one at the end of last week shows gaps in returning hours that were
not present the first time we ran the report and are easily
attributable to one plan (we had a deadline and most of us swamped onto
that project during the first 2 weeks of the year).
To complicate matters further I can return a pivot table for the
affected resources for this time and see their recorded actuals (which
I know are in this project). I can also go into the plan itself
(through project and see sensible looking actuals).
2. A hanging or crashing administrative plan. Basically, its a huge
plan where we capture all our overheads, it went through a stage of not
updating actuals in the spooler. After about a week of this it crashed,
I luckily (after about a week of tinkering with it) managed to save an
offline mpp of it, backed the spooler up to xls and reimported and
manually rekeyed all the spooler data (Prestore.exe didnt seem to fix
the issue). This has improved the situation greatly but the plan still
shows signs of instability... I'd like to make it stable!
Again any help or assistance would be greatly appreciated.
Scott