D
David F-H
MS Project Server 2007 (SP1 + IU updates + Aug cum hotfixes)
MS SQL 2005
We are having some problems with the "View Availability" view not matching
what is in our published project plans. Eg. A resource is clearly allocated
in a given week for a project (and confirmed in Resource USage view in PP, as
well as "View Assignments" in PWA), but shows zeroes in the same week /
project under "View Availability". We had hoped that applying the IU updates
and cumulative August hotfixes may have fixed this, but it hasn't (at least
not for existing problem tasks).
I thought perhaps that a full rebuild of the Reporting database may fix this
(as I assume that "View Availability" derives its info from here), and have
found how to do this at Projectserverblogs.com (from Sharry Herberer MSFT).
My questions then are :
1) Firstly, do you know what could be causing the problem?
2) Would rebuilding the Reporting DB in Proj Server fix this and/or be a
useful exercise regardless? (it has never been rebuilt since original
install prior to SP1 and hotfixes).
3) I initiated a restore on our test server (by backup / restore custom
fields as suggested in blog). This spawned hundreds of jobs just for a small
test DB, so am worried about potential for errors, as the error messages are
not that informative, and how to go about fixing if there is a corruption in
the db ?
4) I believe that once initiated, that the job queue should prevent
inconsistencies due to people publishing jobs at the same time (although I
would do it late at night) ?
Any advice welcome.
MS SQL 2005
We are having some problems with the "View Availability" view not matching
what is in our published project plans. Eg. A resource is clearly allocated
in a given week for a project (and confirmed in Resource USage view in PP, as
well as "View Assignments" in PWA), but shows zeroes in the same week /
project under "View Availability". We had hoped that applying the IU updates
and cumulative August hotfixes may have fixed this, but it hasn't (at least
not for existing problem tasks).
I thought perhaps that a full rebuild of the Reporting database may fix this
(as I assume that "View Availability" derives its info from here), and have
found how to do this at Projectserverblogs.com (from Sharry Herberer MSFT).
My questions then are :
1) Firstly, do you know what could be causing the problem?
2) Would rebuilding the Reporting DB in Proj Server fix this and/or be a
useful exercise regardless? (it has never been rebuilt since original
install prior to SP1 and hotfixes).
3) I initiated a restore on our test server (by backup / restore custom
fields as suggested in blog). This spawned hundreds of jobs just for a small
test DB, so am worried about potential for errors, as the error messages are
not that informative, and how to go about fixing if there is a corruption in
the db ?
4) I believe that once initiated, that the job queue should prevent
inconsistencies due to people publishing jobs at the same time (although I
would do it late at night) ?
Any advice welcome.