Queue and Event service not starting correctly after server reboot

[Dyn]

Hi Everyone,

Our Test environment is deployed with one application server and one
database server.

The database server is scheduled to be restarted every sunday at 4:00, then
the application server reboot at 5:00 every sundays as well.
After the application server restart, I checked the task manager and only 1
process each for queue and event service is running. (Only one SSP for this
Project Server 2007 and WSS 3.0 deployment)

Could anyone please tell me what I need to do so that the Queue and Event
service will start correctly after these server restart?

 

[paul conroy]

you should only be expecting one process, but multiple threads, depending on
usage.

 

[Dyn]

Hi Paul,

Thank you for your response. I have one SSP, and I believe that I should be
expecting 2 processes for the queue and event in task manager. Since the
process is spawned every instance of SSP.

By the way, all of my scheduled queues (OLAP cube build) is stuck with the
status "Waiting to be Processed" every application server reboot.

It would only process when I perform either a Service Restart for the Queue
and Event Service or when I manually execute a new job.

Do you have any idea what might be causing this?

 

[paul conroy]

Are you running the latest SP and hotfixes (SP1, Dec CU) ? There were some
memory leaks in the queue at RTM.

What's the oldest job on the queue which is still waiting to be processed?

 

[Dyn]

Hi Paul,

Yes, we are up to date with hotfixes even for the SQL database server.

As of now there are no queues waiting to be processed for all sites. All of
the "Waiting to be Processed" queues completes successfully after I perform a
restart of the queue and event service.

Im quite sure that its got something to do with the service not starting
correctly after server reboot because of the missing processes.

Do you know of any workaround for this issue, which doesn't involve creating
a batch file for a service restart of the Queue and Event Service?

Thank you in advance.

 

[Gary L. Chefetz]

Dyn:

The classic cause of this is that the SQL Server isn't ready when Project
Server attempts to start the queue service. It seems unlikely that your SQL
server is taking more than an hour to recycle, but I suppose it could be
possible. Have you monitored the restarts? Are the date/time settings on
both servers pulling from a DC to keep them in synch? Then again, there are
a minority of systems out there that exhibit this behavior and, to my
knowledge, no one has pinpointed the cause. In this case you might want to
setup another automated job to restart the queue service say 20 minutes
after the restart. See:

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

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Dyn]

Hi Gary,

Thank you for your reply, yes i have also thought the same that it shouldn't
take the database server an hour to actually accept connections again. I was
hoping that I wont have to resolve to the creation of a batch file for this
issue. Will the Recovery Tab under the properties of the service work? If i
turn on the restart service after first failure?

But the services are actually started, it just doesn't seem to recognize my
SSP, thats why it doesn't spawn a service. And the weird thing is when I
manually execute a job that is not a scheduled job, the queue actually
processes all of the "Waiting to be Processed" jobs correctly afterwards.

 

[cv]

Had same issue myself with the services not starting correctly after the Dec
CU, not sure if exactly the same as yours but changing timeout in the
registry solved for me.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

Add ServicesPipeTimeout as REG_DWORD = 600000
Change WaitToKillServiceTimeout = 120000

Then restart.

 

[Dyn]

Hi cv,

Thank you for this, I will try this out.
But is it 600,000? or just 60,000? Ive just checked our servers and these
two fields are already defined in the registry with only the exception that
for ServicePipeTimeout its defined as 60,000 instead of 600,000.

 

[Gary L. Chefetz]

Dyn:

Do you have the latest SQL Server SP3 installed? It might not help to run a
repair on your Project Server installation but it won't hurt it.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[cv]

ya sorry 60000 not 600000.

ServicesPipeTimeout was not already there for me so just change WaitToKill