Farm job errors when adding a server

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

Job Name: InstallControlServiceOnServer

Parent Job: DeployServerToFarm

Possible Errors:

• Job left pending because no valid IPF control service is available to process this job.

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

  To resolve, start the IPF Control Service on an existing farm server. Pending jobs will then be processed. Any code path that creates a job that is not able to be processed will set the job status to Manual.

• IPF Control Service configuration file not found.

  This message is displayed: "Unable to install 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 reverts the target server to its previous state, not in a farm.

• User credentials are missing from the IPF Control Service configuration file.

  This message is displayed: "Unable to install 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 reverts the target server to its previous state, not in a farm.

• Invalid permissions on the target server.

  This message is displayed: "Unable to install IPF Control service on server '{0}': You do not have enough permissions to install 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 reverts the target server to its previous state, not in a farm.

Job Name: DeployServerToFarm

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: DeployIPFInstanceToServer

Parent Job: DeployServerToFarm or DeployIPFInstanceToFarm

Possible Errors:

• Unable to create IIS application pool.

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

  This is most likely a corrupt IPF Control Service installation on the target server. To resolve, repair with the IPF Installer and retry the job. Cancelling the job leaves the server idle. If deploying the server to a farm, the server is removed from the farm.

• Unable to create IIS site.

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

  This is most likely a corrupt IPF Control Service installation on the target server. To resolve, repair with the IPF Installer and retry the job. Cancelling the job leaves the server idle. If deploying the server to a farm, the server is removed from the farm.

• Web install missing from IPFVersion.

  This message is displayed: "Unable to deploy web application for FarmName '{0}', IPFInstanceName '{1}': Could not get web application files from the IPFVersion.zip"

  The IPFVersion metadata in the IPF Control Database is corrupt. To resolve, import a valid IPF version and retry the job. Cancelling the job leaves the server idle. If deploying the server to a farm, the server is removed from the farm.

• Unable to deploy web app.

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

  This is most likely a permission issue. Correct permissions and retry the job. Cancelling the job leaves the server idle. If deploying the server to a farm, the server is removed from the farm.

Job Name: DeployBindingToIPFInstanceServer

Parent Job: DeployIPFInstanceToServer or DeployBindingToIPFInstance

Possible Errors:

• Unable to import certificate into IIS.

  This message is displayed: "Unable to import certificate into IIS: {errmsg)"

  This is due to an invalid certificate. To resolve, re-import the certificate and retry the job. Cancelling the job leaves the server idle.

• Unable to create binding for IIS site.

  This message is displayed: "Unable to create binding of '{0}' for FarmName '{1}', IPFInstanceName '{2}': {errmsg}"

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

Job Name: DeployServerToLoadBalancer

Parent Job: DeployServerToFarm or MakeServerActive

Possible Errors:

• No active interface adapter found on the target server.

  This message is displayed: "No active interface adapter found on Server '{0}'"

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

• No host names are defined in the farm.

  This message is displayed: "No Host Names are defined for Farm '{0}'"

  To resolve, add the host name to the farm and retry the job. Cancelling the job leaves the server idle and not in a farm.

• No IP address found for host name.

  This message is displayed: "No IP addresses found for Host Names in Farm '{0}'"

  To resolve, create the DNS entry for the host name(s) in the farm and retry the job. Cancelling the job leaves the server idle and not in a farm.

• Error creating NLB cluster.

  This message is displayed: "Unable to create NLB cluster: {errmsg}"

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