Queuing has never successfully processed ANYTHING

[d f]

Hi all,
I'm trying to get project server 2007 running on a single server but
have had no luck at all getting the queue to process the jobs sitting
in the queue. I've tried the suggestions on the other posts (make sure
the db is started before queuing service) but no luck. Yesterday I
managed to connect to the server with project professional 2007 and
push the resource pool to the server successfully but when trying to
save a project to the server it seems to sit in the Waiting to Process
state under manage Queues. I've also tried changing the services
(queue, sharepoint timer etc) to log in with the system account but no
luck. Any help is MUCH appreciated

-D

 

[Marc Soester [MVP]]

Hi d f,

this issue sounds very much like your qeue service is not running. Can you
please check that the Micrososft Office Project Server Qeue service is
running. Also can you please check if you have any event error logs display
on your server.

thanks

 

[Jonathan Sofer]

On a fully functioning environment there should be two identical
Microsoft.Office.Project.Server.Queuing.exe running under the Process tab in
Task Manager. Verify that there are two, if not let us know.

 

[d f]

On a fully functioning environment there should be two identical
Microsoft.Office.Project.Server.Queuing.exe running under the Process tab in
Task Manager. Verify that there are two, if not let us know.

Hi Jonathan,
There are 2 but not identical. They are:
- Microsoft.Office.Project.Server.Queuing.exe
- Microsoft.Office.Project.Server.Eventing.exe

Thanks! -Dave

 

[Neufusion]

I had a single server setup and thought using Local System and Network
server defaults would make things easy... They don't.

I used a new box and reinstalled everything, this time following
microsoft guidelines for SharePoint administrative and service
accounts and using least-privledge accounts. I also configured
Kerberos authentication. After I was done, I nuked the test sites on
the new server and then did a backup from the original SharePoint
Server using stsadm.exe and then restored to the new site. It worked
like a charm. All of my SharePoint AND Project errors and pains went
away.

I dont have a definitive answer for you, but I think you should try
setting up SharePoint and Project Server to use service accounts
instead of Local System / Network Service.

Here's a quick rundown of my services and proceses for SharePoint and
Project Server and the service accounts running them:
Windows Task Manager:
w3wp.exe / sharepoint_apppool_mysite
w3wp.exe / sharepoint_apppool_portal
w3wp.exe / sharepoint_apppool_sspadmin
OWSTIMER.EXE / sharepoint_serverfarm_account
Microsoft.Office.Project.Server.Queuing.exe /
sharepoint_serverfarm_account
w3wp.exe / sharepoint_serverfarm_account
Microsoft.Office.Project.Server.Eventing.exe /
sharepoint_serverfarm_account
mssdmn.exe / sharepoint_serverfarm_account
mssearch.exe / sharepoint_serversearch_account
mssearch.exe / sharepoint_serversearch_account
mssdmn.exe / sharepoint_serversearch_account
Microsoft.Office.Project.Server.Eventing.exe / sharepoint_ssp_account
Microsoft.Office.Project.Server.Queuing.exe / sharepoint_ssp_account
w3wp.exe / sharepoint_ssp_account
sqlservr.exe / sqlserver_service_account

Services:
Microsoft Office Project Server Events Service / DOMAIN
\sharepoint_serverfarm_account
Microsoft Office Project Server Queue Service / DOMAIN
\sharepoint_serverfarm_account
Windows SharePoint Services Timer / DOMAIN
\sharepoint_serverfarm_account
Office SharePoint Server Search / DOMAIN
\sharepoint_serversearch_account
Windows SharePoint Services Search / DOMAIN
\sharepoint_serversearch_account
SQL Server / DOMAIN\sqlserver_service_account

If anyone reading has any comments or suggestions for MY setup, please
let me know.

Here are some links to help you in your adventures. =]
http://technet2.microsoft.com/Offic...ca37-447a-a056-1a67d93ef5401033.mspx?mfr=true
http://technet2.microsoft.com/Offic...d60d-4b85-87de-19065d9688351033.mspx?mfr=true
http://blogs.msdn.com/martinkearn/a...part-1-base-configuration-for-sharepoint.aspx
http://www.datasprings.com/Resource...stallingSharepoint2007/tabid/774/Default.aspx
http://groups.google.com/group/micr...Access+Account+&rnum=3&hl=en#a0325bac4b837c53
http://support.microsoft.com/kb/326985/#4
http://support.microsoft.com/kb/832769

 

[Jonathan Sofer]

d f,

If you only have one of each of these running then there is something
definitely wrong with the current installation. You need to see two of each
of the following:

Microsoft.Office.Project.Server.Queuing.exe
Microsoft.Office.Project.Server.Eventing.exe

I had a similar issue where I had a job stuck in the processing state and
Microsoft could not figure out how to get rid of it. They had me verify
that I had two queue.exe's running and I didn't. Microsoft recommended
deleting and re-provisioning the top level PWA site. Once I did that it
fixed the issue but obviously there were some ramifications if you do not
restore your content database which can be difficult to do correctly.

Hope this helps,

Jonathan

 

[d f]

d f,

If you only have one of each of these running then there is something
definitely wrong with the current installation. You need to see two of each
of the following:

Microsoft.Office.Project.Server.Queuing.exe
Microsoft.Office.Project.Server.Eventing.exe

I had a similar issue where I had a job stuck in the processing state and
Microsoft could not figure out how to get rid of it. They had me verify
that I had two queue.exe's running and I didn't. Microsoft recommended
deleting and re-provisioning the top level PWA site. Once I did that it
fixed the issue but obviously there were some ramifications if you do not
restore your content database which can be difficult to do correctly.

Hope this helps,

Jonathan

Good news! I changed the services to all run under the local service
account instead of the local system account and it seems to have
solved most the problems.

 

[Jonathan Sofer]

Glad to hear it. Thanks for letting us know your resolution.

Jonathan Sofer

 

[Jason Short]

HI All,

I experienced this issue myself today. I only had one of each service
running. I managed to resolve the issue simply restarting the two single
running instances and the second instance then strated a well. All the jobs
in the queue were then successfully processed