Managing jobs (events) in the Project Server Queue
When project and timesheet information is published to Microsoft Office Project Server 2007, it is processed by the Project Server Queue. You can change how queued jobs (or events) are scheduled, view the jobs in the queue, and restart specific jobs in the queue.
The Project Server Queue contains two separate queues:
-
Project Queue This is used for project messages that are related to saving, publishing, reporting, and cube building. Its tables and stored procedures are stored in the Office Project Server 2007 Working database.
-
Timesheet Queue This is used for timesheet messages that are related to saving and submitting a timesheet. Its tables and stored procedures are stored in the Office Project Server 2007 Published database.
What do you want to do?
Change the job queue settings
-
On the Quick Launch, click Server Settings.
-
On the Server Settings page, click Queue Settings.
-
In the Queue Type list, select Project or Timesheet to indicate which queue you want to change.
Clicking Save at the end of this procedure will save the settings for the queue type that you selected. To modify and save the settings for the other queue type, you have to repeat this procedure.
-
In the Maximum Number of Job Processor Threads section, type the maximum number of queued jobs that can be processed by the server at one time.
Tip: If you type -1, the maximum number of threads (up to 20) will be processed by the server.
-
In the Polling Interval (in milliseconds) section, type the number of milliseconds that the Project Server Queue should wait before polling the project or timesheet database for new jobs.
-
In the Sub-job retry Interval (in milliseconds) section, type the number of milliseconds that the Project Server Queue should wait before retrying the job if the original attempt or attempts failed.
-
In the Sub-job retry limit section, type the number of times that the Project Server Queue should continue to poll the database if the original attempt or attempts failed.
-
In the SQL retry interval (in milliseconds) section, type the number of milliseconds that should elapse between each attempt to process a job.
-
In the SQL retry limit section, type the maximum number of times that the Project Server Queue should try to process a job.
-
Click Save.
Set up the job queue grid
-
On the Quick Launch, click Server Settings.
-
On the Server Settings page, click Manage Queue.
-
In the Filter Type section, in the Filter Type list, select the type of job that you want to display in the Jobs Grid.
-
In the Job/Job Group IDs section, type the Job ID number or a Job Group ID. This section appears only if you selected By ID from the Filter Type list.
Job Group IDs associate related jobs. For example, if a user publishes a project, that job automatically contains other associated jobs that are related to notifications, reporting, and so on.
Tip: To determine which Job or Job Group ID to use, copy the ID from the Jobs Grid. Before doing this, insert the Job ID and JobGroup ID columns in the Jobs Grid by using the Available Columns table in the Columns section.
-
In the Job History section, select the time period of historical data and the maximum number of jobs that you want to view in the Jobs Grid.
-
In the Job Types section, select the type of job information that you want to display in the Jobs Grid.
-
In the Job Completion States section, select the type of job status information that you want to display in the Jobs Grid.
-
In the Projects section, select the projects that you want to monitor in the Jobs Grid.
This section appears only if you selected By Project from the Filter Type list.
-
In the Columns section, select the columns that you want to display in the Jobs Grid.
-
In the Advanced Options section, specify if you want to cancel the related sub-jobs when you select a job, and then click Cancel Job.
-
Cancel jobs getting enqueued Select this option if you want to cancel only the jobs that are entering the jobs queue.
-
Cancel subsequent jobs in the correlation Select this option if you want to cancel the selected job or jobs, as well as any related sub-jobs. This will minimize potential synchronization problems with the task and with resource information that may be associated with the project or timesheet.
-
-
In the Jobs Grid section, select a job from the list and then click Related Tasks to review jobs that are related to the same project (if your administrator has installed the Infrastructure Update for Microsoft Office Servers). This can help you see why a job is not queued and not running, as it may be blocked by a previous job against the same object.
To remove the Related Tasks sub-filter, click All Tasks.
Notes:
-
To learn more about a failed job, click the hyperlink error message in the Error column of the Jobs Grid.
-
Team members can also view jobs in the queue. Team members can click Personal Settings on the Quick Launch and then click My Queued Jobs. On the My Queued Jobs page, team members can see only their own jobs within the queue. Team members should also be reminded that changes to pages within Microsoft Office Project Web Access may not happen immediately if there are currently many jobs in the Project Server Queue. They can press F5 to refresh a page until they see their changes.
-
You can also use event handlers to view the status or performance of queued jobs and other processes. On the Quick Launch, click Server Settings, and then click Server-Side Event Handler Configuration.
-
Cancel or retry jobs in the queue
-
Select the job in the Jobs Grid, and then click Cancel Job. You can also click Retry Job for the selected job if the status information in the Job State column indicates that there was a problem with processing the job.
Note: You cannot retry jobs that have a Job State of Failed And Blocking Correlation.
-
Click Refresh Status to update the Jobs Grid to reflect the changes that you made.
Why can't I perform some actions in Project Web Access?
Depending on the permissions settings you used to log on to Project Web Access, you may not be able to see or use certain features. Also, what you see on some pages may differ from what is documented if your server administrator customized Project Web Access and did not customize the Help to match.
No comments:
Post a Comment