Reporting (Publish Project) job is 'sleeping'

[Kristi]

I am using Project Server 2007 and whenever I publish a job, it sits in the
job queue with a job state of 'Waiting to be processed (sleeping)' for about
an hour. Why would it do that and how can I speed it up?
Thanks!

 

[Ben Howard]

Hi Kristi,
Presumably the job is processed eventually. Make sure the queue settings
are set back to their default and then try publishing the job again. Let me
know what happens.

 

[Marc Soester]

Kristi,

I have noticed that you will have to restart the Queue service occationally,
then the jobs are processed. I have this issue on some VPC images.
Go to Services and find the Microsoft Project Server queue service, restart
them and see if the jobs are processes.
Hope this helps

 

[Boaz Lev [MSFT]]

What priority have you given your queue job?

 

[Pradeep GanapathyRaj [MSFT]]

Kristi - there is no way to "Speed up" a Queue job ie) users cannot change
the priority of any job in the queue. If it is in the "Waiting to be
processed (sleeping)" state for a long time, there may have been some issue
with a previous job that is preventing this Publish job from going through.

One way to get out of the situation (you may have tried it):

1) Select the waiting job in the 'Manage Queue' page and 'Cancel' it.
2) Try publishing the project again

To troubleshoot the problem further, look at the event viewer log around
that time or the Project Server log files (default location:
<Drive>:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\12\LOGS). Hope that helps.

 

[Sharry Heberer [MSFT]]

Usually when a "Reporting <something>" job is having to sleep, it is because
some component referenced in that entity (that project, that resource, etc.)
is missing from the Reporting Database. We see this most often when a
Custom Field definition has not been transferred into the Reporting
Database. For consistency purposes, the Reporting Database cannot handle
values for metadata it knows nothing about.

What I suggest is trying another publish on an offending project, waiting
for it to go to sleep, then looking in the project server logs on the
application server. Once the Reporting job finds that it needs to sleep, it
will tell you exactly what field is missing in the logs at the time the
error occurs. At that point, you can simply cause an edit to happen on the
offending field (something as simple as editing the name of the custom
field), so that Reporting will be forced to try and sync that field again.
Once the field is properly synced, the sleeping job should go through just
fine (i.e. it will "wake up" in about 5 minutes and try again and succeed
this time).

HTH,
Sharry