About incomplete jobs

Ordinarily, farm jobs complete successfully and corresponding records are unlocked.

For reasons described in Chapter 3, “Troubleshooting”, farm jobs may enter an Incomplete state. When this happens, locked records remain locked, and the job status information can be reviewed on the Farm Jobs form.

Depending on the type of failure, you may be able to retry the job. The job may then complete successfully, and dependent IPF records are unlocked. Or, it may be necessary to cancel the job. Again, associated locked records are then unlocked.

In general, when a job is cancelled, the corresponding server is left idle. When an idle server is made active again, the control service automatically examines the current state of the server in IIS and compares it to the defined state in the IPF Control Database. Any missing IIS sites and bindings are recreated as necessary.

Farm jobs may have a parent/child relationship. In these cases, when a child fails the parent also fails. You must correct incomplete jobs from the bottom up, meaning that Retry and Cancel options are only active in the Farm Manager when the selected job is incomplete and has no child jobs.