The new world of Project Server 2007 and the architectural changes are catching a few of our customers out - and I thought I'd share a few tips and tricks for keeping the queue flowing - and some tips for getting things moving again if they appear to have stopped.
First I will point to a great TechNet article on the Queue and as you will all have read this then my explanations will make more sense :).
Under Server Settings in Project Web Access the Manage Queue option allows you to see what is happening in the project and timesheet queues - if you don't have admin access then the Personal Settings will give you a glimpse of your queue jobs. The latter option may not however give you the complete picture and allow you to see what might be ahead or you. It is like being stuck on the highway and not being able to see around the corner to where the flashing lights are...
So lets start with some definitions:-
Waiting to be processed - means exactly what it says. Once I get to the front of the queue then I am ready to go. But there may be other active jobs ahead that will stop my job starting even if I am first in line. The queue is clever enough that it will hold jobs back if their processing would interfere with other running jobs. An example might be a publish job that will need to wait for a cube build to finish.
Processing - means that I made it to the front of the queue, was allocated a thread and am working away! One thing I have noticed is that the % complete indicator doesn't always make you think that "processing" is happening - but generally it is. Looking in the ULS logs, event logs or at general server activity (particularly the Microsoft.Office.Project.Server.Queuing.exe process should help if you have continued doubts that processing is moving along.
Skipped for optimization - is the queue's way of telling you that it is not going to do the same thing twice. Some queue jobs have a payload (such as saving a project) and others are merely instructions (such as publish a project). If several of the same instruction are in the queue, then only one needs to be actioned. An example might be working on a project and publishing a few times during a period of time. If the queue was busy all of these jobs might be sitting waiting for a while - and then rather than doing each in turn it just needs to do one. It is just an instruction to publish the content of the saved project. This would not happen with a queue job that had a payload as each of these contains real data that needs to be applied - rather than just an instruction to do something with data somewhere else.
Getting Queued - appears to be one of the more confusing messages. I mentioned above that some jobs, such as save project from Project Professional, have a payload. This payload goes into the queue as a group of related messages, which then get processed once they reach the front of the queue. Getting queued means that these messages are going into the queue. It is possible that the Getting Queued message appears for some time because a very large project is coming in across a very slow link. One other potential problem that can break things is if this flow in of messages does not complete. Perhaps the Project Manager saving the project shuts down Project before it completes - or perhaps goes out of wireless range midway through the process. Either way the Getting Queued could sit there for some time. To fix this up find the person who has this project in mid-save and get them to reconnect and complete the job. As a last resort you can cancel the Getting Queued - but YOU WILL LOSE DATA! Any changes the Project Manager made will not get saved. To protect you from inadvertently canceling one of these jobs we add a check box under Advanced options labeled "Cancel jobs getting enqueued" which will need to be checked before these jobs can be canceled.
Failed and Not Blocking correlation - is a failure that is isolated and not stopping any other jobs from processing. The term correlation is used to group related queue jobs together. There should be an associated error message and entries in the log to help explain the problem.
Failed and Blocking correlation - means that something bad happened that is also blocking other things in the related group. If a save fails then a publish could not continue would be one example.
Success - is the one message we like to see! It can also be useful to sometimes show the Success messages (by default they are not shown in the Manage Queue display) as it is a way of seeing if the queue is working at all. Adding the completion state of Success through the options on the manage queue page is how this is done.
Canceled - means what it says. It could have been canceled by a user, but it is also possible for jobs to be canceled by the server. One example would be a failure early on in a save from Project Professional. A job would have been added to the queue for the save - but reconnection may lead to cancellation of this job and the addition of another save job - it really depends hoe far the save got before the problem. I simulate bad things like this by pulling my network cable out just after hitting save - just to see what happens!
I will follow up with another posting on the queue with some further tips on troubleshooting -but my parting gift is a guide to what the dialogs at the bottom of Project Professional 2007 mean during a save.
Technorati Tags: Project Server 2007
The timesheet of the resource did not reflect in the work plan. What can cause such issues? This is what I suggested –
Can you cancel the jobs running for the affected work plan? Then, please try to republish the affected work-plans:
Open the offended plan in MS Project Client as usual
Choose File > Save for Sharing; Do not change the plan name. The operation saves the plan locally.
Choose File > Save As. Click "Save" to save the plan back to Project Server
Notice the plan name is already populated and non-editable.
Verify the save operation is finished by checking the "Active Cache Status"
When the save is done, Save the plan, wait the save is completed and Publish it as usual.
However when he tries to cancel the jobs in the manage queue page he sees an error – Root element is missing.
HOWEVER; THIS ARTICLE IS AMAZING.
During last one week, many of the jobs have started failing. The job usually process successfully but sometimes fails randomly with state ‘Failed But Not Blocking Correlation’.
Whenever the job fails, it exactly fails at following percentage:
OLAP Cube Build --> 50%
Project Checkin --> 12%
Project Publish --> 96%
Project Publish Notifications --> 0%
WSS Workspace Create --> 0%
Can you please inform me that what can be the reason of failing these jobs?
Our PS2007 environment has a job (AD Sync) that is not completing and it taking up 100% of the CPU (Queue service & SQL Server).
This job has been running for over two days now. We have tried rebooting the server as well as cancelling the job but it is not fixing the issue. After a rebootm the CPU returns to 100% once the job is picked up again.
This environment has been running for many years and we have not ezperienced this issue before.
Is there any way to remove this job from the Queue that is not completing?
Any suggestions on how to resolve this issue?
We are running PS 2007 v12.0.6422
Sorry didn't know how to start out a new Comment.
Can someone tell me where all i can look for MS Project 2007 Log files.
We have custom apps with SAP pulling data from project.
PWA > Applied Task and Errors shows - Shoes alot of errors that was showing missing data from a few days ago.
1- First question is how do you re-process this type of file/task that was not published.
2- Second where can i find the different Log Files?
I have looked at the following places:
A- C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Logs
B- Event Viewer > Windows Logs > (Applicaton)-&-( System ) Logs
I look at/inside C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Logs
but I dont' see anything todo with MS Project - for ULS Logs either.
Just want to know where all someone can look for log files.
The forums social.technet.microsoft.com/.../project or a support incident might be better for questions that don't relate to a blog post. You have the right places for the log files. USL logs (A) would be the most likely place to find problems - but until I know the errors I can't give much guidance on how to resubmit. I'd ask the people that set up the interface to SAP.
Archive Global Project,Archive Custom fields,Archive System setting, Archive Security category timesheet queue jobs are getting queued and the job status is in Waiting to be precessed.
Could any one please let us know why this is getting stuck in the queue, its happening daily.
However is tried cancelling the job, however its getting stuck everyday.
Please let us know the solution to this issue.
Thanks in advance
Hi Veeru, I'd suggest you review the queue history - if the queue is generally working then there may be an old failed job blocking this one.
Nice blog :) .
I ma facing issue freqentaly in all project as "Your queue job UpdateProjectSitePath failed. Please contact your administrator for assistance" and error code is WSSWebDoesNotExist
when try to give permsiion to any body on project.
Kindly provide appropriate solution.
When you update users Hasan, then it will sync the user to the project site. It sounds here like the site no longer exists – but is still referenced in the page showing Project Sites under Server Settings in PWA. Removing the site from that list may solve this issue.
This happens in my environment every 25 days or so...Any hint for solving this...
TimeCreated : 4/8/2014 5:53:50 AM
Id : 7754
LevelDisplayName : Critical
Message : Standard Information:PSI Entry Point:
Project User: xxxxx\xxxxxxxxxx
Correlation Id: 4bfa3fad-b1f4-4810-8535-0de6a21207bd
PWA Site URL: http://msproj2010/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)
Queue unable to interact with SQL. Queue type (Project Queue
, Timesheet Queue etc): ProjectQ Exception: Microsoft.Office
extAvailableGroup failed ---> System.Data.SqlClient.SqlExcep
tion: An invalid application lock resource was passed to xp_
on exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBeh
avior, SqlCommand cmdHandler, SqlDataReader dataStream, Bulk
CopySimpleResultSet bulkCopyHandler, TdsParserStateObject st