Timesheet issues

Aug 31, 2011 at 8:42 PM

We are receiving three successive 9681 events, an error and two information, recurring almost constantly. The error is as follows:


FAILED due to a SoapException: ==============================


System.Web.Services.Protocols.SoapException: ProjectServerError(s) LastError=GeneralUnhandledException Instructions: Pass this into PSClientError constructor to access all error information

at Microsoft.Office.Project.Server.WebService.Statusing.ImportTimesheet(Guid periodUID)





Exception InnerXML:

<errinfo><general><class name="An unhandled exception occurred in Statusing.ImportTimesheet."><error id="42" name="GeneralUnhandledException" uid="9118b8fd-c2c5-43fe-9097-f4f6bcf38b22" /></class></general></errinfo>



Additionally, we are experiencing the following front-end behavior:

1. User submitted a timesheet 6/19-2011-6/25/2011 with time against a task; when the time was accepted into the project plan, no Actual Work was recorded against the task. Resource had to notify Project Owner that the task was completed and what timesheet time was recorded against.

2. Same user as above unable to adjust Remaining Work on project tasks without getting a queue job failed error. Other users are able to adjust Remaining Work from his computer. Have reviewed ActiveX Controls; cleared cache; cleared browser history; removed user from AD; removed from PWA Group, put back in and saved; removed from company AD account; had user change Remaining Work from other computer without avail; included PWA in trusted sites; reviewed add-ons and verified pop-up blockers were disabled.

3. Timesheets reverting back to previous setting to require additional approver even with Fixed Approval Routing selected. During week of 8/15/2011, began seeing Set Next Approver on certain Resource Manager accounts with Resource Manager listed as next approver. Upon selecting Approve, timesheet review would result in Failed and Blocking Correlation in the queue with the following error message:

 <error id="3205" name="TimesheetInvalidApprover"

We are currently running on Service Pack 2 with Cumulative Updates through Aug 2011.


Oct 18, 2011 at 2:50 PM

This problem usually arises when the timesheet contains invalid data. You may need to delete the timesheet and recreate.