Queue Problems - Waiting to be Processed

[Project Server Slave]

Hello,

I'm working with a single server installation of Project Server 2007
SP1 and SQL Server 2005. Each day the queue seems to get hung up, and
there is no solution other then to restart the queue service to get
things processed.

It seems to happen most often with the Archive job type, such as
archive resources. It will get stuck on this job and everything above
it will remain in the waiting to be processed job state.

I've tried retrying the job, I've tried canceling the jobs and letting
them go again the next day. If its a save or publish job, I have the
project manager open the project, save and publish and then close, but
nothing seems to help.

The only thing I can do to get it unstuck, is to restart the project
queue service and then it just gets stuck again the next day. The
queue settings are all set as default, and this box is not used for
anything else. There are only 3 or 4 people using this so it has
extremely low usage.

Any ideas? Thanks.

 

[ProjmanZA]

Hello,

I'm working with a single server installation of Project Server 2007
SP1 and SQL Server 2005.  Each day the queue seems to get hung up, and
there is no solution other then to restart the queue service to get
things processed.

It seems to happen most often with the Archive job type, such as
archive resources. It will get stuck on this job and everything above
it will remain in the waiting to be processed job state.

I've tried retrying the job, I've tried canceling the jobs and letting
them go again the next day. If its a save or publish job, I have the
project manager open the project, save and publish and then close, but
nothing seems to help.

The only thing I can do to get it unstuck, is to restart the project
queue service and then it just gets stuck again the next day.  The
queue settings are all set as default, and this box is not used for
anything else.  There are only 3 or 4 people using this so it has
extremely low usage.

Any ideas?  Thanks.

Hey there ,

You do not mention that you have SQL sp1/2 installed. If you dont that
is most proberbly the cause of the problem. If you do have it do you
have all the other hotfixes installed? if you dont the latest
Infrastructure Update from MS has all the hotfixes in a signle
package.

Hope it helps

 

[Project Server Slave]

We do have SP 2 for SQL Server installed. I didn't want to install
the Infrastructure update yet, but I suppose that's an option. This
is a smaller company, with no easy way to make an image of the box
before installing. I suppose I could backup the databases and
reinstall the application if something goes wrong.

Short of installing an update, this problem has not occurred at the
many different clients sites I've installed this at. So what do you
think could be the issue? I should not ever have to restart the Queue
service.

 

[Project Server Slave]

Anyone have any idea's? Still having the same issues.

 

[Gary L. Chefetz [MVP]]

Robert:

I can't tell you the cause, but I can tell you that some systems behave this
way. I suspect it's a data issue, but nobody has studied these cases enough
to make this determination. Meanwhile, this might help:

http://www.projectserverexperts.com... restart the queue service automatically.aspx

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


Anyone have any idea's? Still having the same issues.

 

[Project Server Slave]

Gary,

I had thought about doing this, but was hoping to find a way to
resolve the issue. I'll probably have to go this route, thanks for
the advice.