none
Reporting (Timesheet Project Aggregation) tasks "waiting to be processed" forever... RRS feed

  • Question

  • Project Server 2010 /SP2/SEM

    A few days ago, a job of the type Reporting (Timesheet Project Aggregation) in the queue got "stuck" (by which I mean it shows  processing but at 0%) and some, but not all, subsequent Reporting (Timesheet Project Aggregation) jobs now automatically go to "waiting to be processed" and nothing happens.  I tried canceling the original job (shows up as number one if you select "show related jobs") and it cancels all the "waiting to be processed" jobs, but that number 1 job doesn't change.

    The timesheet line information that we use for reporting does seem to be hitting the database,  and the users aren't seeing any errors in their timesheets, but the queue is becoming more and more junked up with these things every day.

    Also, there are jobs of this type that are completing without a problem.  It doesn't seem to be tied to a specific project they are putting hours against or any other type of pattern that I can detect.

    This screenshot only shows some of the jobs, there are a whole lot more in there.

    Has anyone seen anything like this before?  There is woefully little information out there about particular queue job types and what they mean, and google has not been forthcoming.  I'd appreciate any ideas!


    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/


    • Edited by ElliJ Monday, April 21, 2014 3:38 PM Added Screenshot
    Monday, April 21, 2014 3:24 PM

Answers

  • Hi Elli

    Are you performing Reporting database refresh? I see the jobs are in "Timesheet' Queue, are you able to process other timesheet jobs?

    Did you check restarting SharePoint Timer Service and Project Server Queue service?

    ==Anil==

    Monday, April 21, 2014 6:13 PM

All replies

  • Hi Elli

    Are you performing Reporting database refresh? I see the jobs are in "Timesheet' Queue, are you able to process other timesheet jobs?

    Did you check restarting SharePoint Timer Service and Project Server Queue service?

    ==Anil==

    Monday, April 21, 2014 6:13 PM
  • Yeah, we just rebooted the whole system and it all went along nicely.  I feel silly for even asking now - when in doubt, reboot, right?

    Thanks!


    Elli J Project Solutions Specialist Blog: http://projectserverpants.wordpress.com/

    Monday, April 21, 2014 7:24 PM