Farm job errors when removing a server

These farm job errors also may occur when removing a server:

Job Name: UninstallControlServiceOnServer

Parent Job: RetractServerFromFarm

Possible Errors:

• Server is not reachable.

  This message is displayed: "Could not save Server '{0}': Server is not reachable.

  To resolve, retry the failed job when the server is available. Cancelling the job unlocks the server record and leaves it with a status of Idle and still in the farm.

• Job left pending because no other control service is available to run it.

  No message is displayed. The server remains locked due to pending job.

  To resolve, start the IPF Control Service on an existing farm server. Pending jobs will then be processed. In a single server farm, the IPF Installer must be used to install, remove, or upgrade the IPF Control Service.

  If the server no longer exists, you can cancel the pending jobs.

• IPF Control Service configuration file not found.

  This message is displayed: "Unable to delete IPF Control service on server '{0}': Configuration file not found."

  The IPF Control Service installation is corrupt on server '{0}'. To resolve, repair with the IPF Installer and retry the job. Cancelling the job unlocks the server record and leaves it with a status of Idle and still in the farm.

• User credentials missing from IPF Control Service configuration file.

  This message is displayed: "Unable to delete IPF Control service on server '{0}': Credentials missing from configuration file."

  The IPF Control Service installation is corrupt on server '{0}'. To resolve, repair with the IPF Installer and retry the job. Cancelling the job unlocks the server record and leaves it with a status of Idle and still in the farm.

• Could not remove the service.

  This message is displayed: "Unable to delete IPF Control service on server '{0}': You do not have enough permissions to uninstall services. Make sure you are part of the Administrators group."

  To resolve, grant permissions to the IPF Control Service account on the target server and retry the job. Cancelling the job unlocks the server record and leaves it with a status of Idle and still in the farm.

Job Name: RetractServerFromFarm

Possible Error:

• Child job failed.

  No message is displayed. The server remains locked.

  To resolve, examine the child job(s) for failure, to determine the appropriate action.

Job Name: MakeServerIdle

Parent Job: RetractServerFromFarm

Possible Error:

• Child job failed.

  No message is displayed. The server remains locked in a Suspending state.

  To resolve, examine the child job(s) for failure, to determine the appropriate action.

Job Name: DrainServerFromLoadBalancer

Parent Job: MakeServerIdle

Possible Error:

• Failure to drain server from NLB.

  This message is displayed: "Unable to drain server '{0}' from NLB: {errmsg}"

  To resolve, fix the NLB configuration issue and retry the job. Cancelling the job leaves the server idle and still in the farm.

Job Name: MonitorSessionsForServer

Parent Job: MakeServerIdle

Possible Error:

• Job remains running, waiting for sessions to close.

  No message is displayed.

  The server remains in a Suspending state. To resolve, you can force the server to be idle. The pending jobs are then processed.

Job Name: RetractServerFromLoadBalancer

Parent Job: MakeServerIdle

Possible Error:

• Failure to retract server from NLB.

  This message is displayed: "Unable to retract server '{0}' from NLB: {errmsg}"

  To resolve, fix the NLB configuration issue and retry the job. Cancelling the job leaves the server idle and still in the farm.

Job Name: RetractIPFInstanceFromServer

Parent Job: RetractServerFromFarm

Possible Errors:

• Unable to delete IIS site.

  This message is displayed: "Unable to delete site for FarmName '{0}', IPFInstanceName '{1}': {errmsg}"

  To resolve, fix the IIS configuration issue and retry the job. Cancelling the job leaves the server idle and not in a farm.

• Unable to delete IIS application pool.

  This message is displayed: "Unable to delete application pool for FarmName '{0}', IPFInstanceName '{1}': {errmsg}"

  To resolve, fix the IIS configuration issue and retry the job. Cancelling the job leaves the server idle and not in a farm.