A.3 Errors Occurred During Forge Management 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 Management VM disk is not PLATESPINFORGE01.
Action: Delete the Forge Management VM, then deploy the OVF Template, according to the instructions in Section 5.3.4, Deploying the Forge Management VM from an OVF File, where the name of the imported VM is PLATESPINFORGE01.
Possible Cause: The Forge Management VM name is not PlateSpin Forge Management VM.
Action: Rename the Forge Management VM to PlateSpin Forge Management VM, according to the instructions in Section 5.3.5, Renaming the Forge Management VM.
Possible Cause: The Forge ESXi Hypervisor has the Evaluation License.
Action: Follow the instructions in Section 5.6, Licensing the VMware ESXi 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 Management VM’s IIS Admin Service failed to manually or automatically start up because of an Invalid Signature error.
Action: Two possible reasons for this issue and actions to take are: