4.3 Errors Occurred During Forge VM Configuration

A FAILURE error occurred on running Forge Appliance Configurator

Source: When you run the Forge Appliance Configurator, you might not see SUCCESS.
Troubleshoot: Check the log file found at the location mentioned in the error message. For example:

D:\Program Files\PlateSpin Forge Server\ForgeApplianceConfigurator\ForgeApplianceConfigurator.log

Explanation: The possible causes for this problem could be any of the following:
Possible Cause: The Forge VM disk is not PLATESPINFORGE01.
Action: Delete the Forge VM, then deploy the OVF Template, according to the instructions in Deploying the OVF Template, where the name of the imported VM is PLATESPINFORGE01.
Possible Cause: The Forge VM name is not PlateSpin Forge Management VM.
Action: Rename the Forge VM to PlateSpin Forge Management VM. In the vSphere client, locate the Forge Management VM, right-click the VM, then rename it to PlateSpin Forge Management VM.
Possible Cause: The Forge ESXi Hypervisor has the Evaluation License.
Action: Follow the instructions in Section 3.3, Licensing the ESXi 5.5 Hypervisor, and then re-run the Forge Appliance Configurator.
Possible Cause: The Forge Appliance Configurator log reports an Installing self-signed SSL certificate event before the exception error. Check the Event Log if the Forge VM’s IIS Admin Service failed to manually or automatically start up because of an Invalid Signature error.
Action: We are not sure why this happens, but here are the possible solutions (so far):

  • Delete the Forge VM, then deploy the OVF Template, according to the instructions in Deploying the OVF Template, where the name of the imported VM is PLATESPINFORGE01.

  • The checksums of the copied VM folder might not match. Re-copy the VM folder and repeat Deploying the OVF Template.