M
milrock
Hi Everyone,
Just so you are aware...if you are using Project Server 2007 Timesheet
functionality on your own system or at a client's site, do not deploy
SP2 or the April CU.
There is a known issue with the timesheet functionality where certain
PS stored procedures will fail with no errors except in the SQL trace
logs (you may get an intermittent error in the app server application
event log saying that the Statusing Interval Submitted is Invalid).
This issue comes up periodically when users save their timesheets but
do not submit them. The next time a user accessed the saved timesheet
they will a) receive an Unknown Error Has Occurred and the dreaded Web
Part Maintenance page will appear, b) the user is given an Access
Denied error when clicking on any of the timesheets on their My
Timesheets page, even creating a new one, or c) the user is able to
submit their timesheet but their timesheet manager will get an Access
Denied error when trying to approve the timesheet. This will render
the timesheet manager unable to approve any of his resources'
timesheets.
This is a very nasty problem (even nastier than the Project Server
Timesheet functionality itself) that the April CU/SP2 has caused.
Microsoft has a hotfix, that isn't regression tested, that will
prevent future occurrences of the problem but are struggling to come
up with a fix for users that have already experienced the issue.
Their is a potential private release for this fix at the beginning of
October but will probably not be in a production deployable state
until the December Cumulative Update.
Another in a long, long line...
S
Just so you are aware...if you are using Project Server 2007 Timesheet
functionality on your own system or at a client's site, do not deploy
SP2 or the April CU.
There is a known issue with the timesheet functionality where certain
PS stored procedures will fail with no errors except in the SQL trace
logs (you may get an intermittent error in the app server application
event log saying that the Statusing Interval Submitted is Invalid).
This issue comes up periodically when users save their timesheets but
do not submit them. The next time a user accessed the saved timesheet
they will a) receive an Unknown Error Has Occurred and the dreaded Web
Part Maintenance page will appear, b) the user is given an Access
Denied error when clicking on any of the timesheets on their My
Timesheets page, even creating a new one, or c) the user is able to
submit their timesheet but their timesheet manager will get an Access
Denied error when trying to approve the timesheet. This will render
the timesheet manager unable to approve any of his resources'
timesheets.
This is a very nasty problem (even nastier than the Project Server
Timesheet functionality itself) that the April CU/SP2 has caused.
Microsoft has a hotfix, that isn't regression tested, that will
prevent future occurrences of the problem but are struggling to come
up with a fix for users that have already experienced the issue.
Their is a potential private release for this fix at the beginning of
October but will probably not be in a production deployable state
until the December Cumulative Update.
Another in a long, long line...
S