3.6 Troubleshooting Specific Issues

This section includes some of the issues you might encounter while performing a Forge upgrade. The issues and actions you can take to correct or work around them include the following:

Importing Forge Server contracts fails

Explanation: The following message is displayed:
Step 2 of 2: Importing Forge Server Contracts

The task failed. "C:\bin\PlateSpin.ForgeUpgrade\11.0.0.5180\PlateSpin.ForgeUpgrade\ForgeUpgrade.zip" Could not be found.
Possible Cause: Exported data is not in the location it should be.
Action: If you are using the /outfolder parameter, make sure that it points to the folder where the backup output is located.

If you are not using the /outfolder parameter, make sure that the backup output is in the same folder as the executable.

The task "Back up contracts" failed. Could not find a part of the <some_path>\GetForgeVmInfo_Result.xml path

Possible Cause: This could be an indication that you are attempting to run the Forge Upgrade utility from a network path. In the ForgeUpgrade.log file, you might see this manifest as:
Type: System.IO.DirectoryNotFoundException

Please stop all jobs or wait for them to complete before running the upgrade

Error Display: You might see the following message:
There are jobs running. Please stop all jobs or wait for them to complete before running the upgrade.
Explanation: The PlateSpin Server is busy with running operations.
Action: Pause all replications and wait for all operations to complete, or abort the running operations.

"Validate user input" failed. Unable to connect to the Forge Server.

Explanation: During the validation phase of the Backup or Restore, the authentication is failing although the password you entered is correct.
Possible Cause: This is a symptom of having a firewall on the Forge Server, which is preventing access.
Action: Try one of the following:
  • Modify the firewall settings to enable file sharing on the Forge Host for the network on which the administrative computer resides, then try again.

  • Temporarily disable the firewall, then try again.

  • Run the tool from a machine within the same subnet as the PlateSpin Server.

"Validate user input" failed. Failed to log in. Please check your credentials and try again

Error Display: You might see the following message:
Step 3 of 5: Validating Parameters
The task "Validate user input" failed. Failed to login. Please
check your credentials and try again.
Logs: You might see an exception like this in the stack trace of the main log file:
Message: Multiple connections to a server or shared resource by
the same user, using more than one user name, are not allowed.
Disconnect all previous connections to the server or shared
resource and try again
Other Symptoms: If you run the net use command on the administrative computer, you might see a message formatted like this:
Disconnected        \\<psserver>\d$       Microsoft Windows Network

Where <psserver> represents the value specified for the psserver parameter. For example:

Disconnected        \\10.99.160.72\d$     Microsoft Windows Network
Possible Cause: A net use connection already exists, probably because you attempted to run the utility previously.
Action: Run the net use <connection> command where <connection> contains relevant content. For example:

net use \\10.99.160.72\d$ /d

"Validate user input" failed. Unable to connect to the PlateSpin Server at <IP_address>

Error Display: You might see a message like this:
The task "Validate user input" failed. Unable to connect to the
PlateSpin server at '10.99.160.72'.
Verify that the address is correct 
Possible Cause: A domain user is being used to connect to the PlateSpin Server.
Action: Enter the PlateSpin Server credentials of either a non-Domain user or a Domain Administrator.

"Validate user input" failed. Unable to connect to the Forge ESX Server at <IP_address>

Error Display: You might see a message like this:
The task "Validate user input" failed. Unable to connect to the
Forge ESX server at '10.99.163.112'.
Please ensure that the address, username, and password are correct
and retry 
Possible Cause: Credentials for forgeuser (or equivalent) are invalid.
Action: Enter the valid ESX Server credentials.

"Validate user input" failed. The administrator user does not have access to the PlateSpin Server

Error Display: You might see the following message:
The task "Validate user input" failed. The user 'administrator'
does not have access to the PlateSpin server at '10.99.160.72'.
Verify that the username and password are correct
Explanation: You entered the wrong password for the administrator.
Action: Enter the correct password.

"Validate user input" failed. The password file does not exist

Error Display: You might see the following message:
The task "Validate user input" failed. An exception occurred while
reading the password file.  Error:  {0}
Explanation: A password file either does not exist or cannot be read.
Action: Check all of the password files.

Authentication for user root failed

Error Display: You might see the following message:
The task Back up Forge failover VMs failed. Authentication for
user "root" failed with result: FAILED
Explanation: You entered the wrong password for the superuser or root user.
Action: Enter the correct password for the root user.

Backup or Restore using USB drive fails with error about read-only device

Context: The USB drive is relatively new, but was used in previous backup/restore operations.
Possible Cause: USB drive mount status can change to read-only midway through the backup process. This might occur if the USB drive goes bad.
Action: Try the operation again or try a new USB device.

Backup to the USB storage fails because it cannot detect the attached USB devices

Explanation: Backup fails with an error stating that USB devices not detected. You are prompted to attach the USB devices.
Possible Cause: USB device detection on ESX (in general) is unreliable.
Action: Try these steps:
  1. Shut down the administrative computer.

  2. Attach the USB devices.

  3. Power on the administrative machine.

Error when using external shared storage such as a NAS

Explanation: The upgrade utility displays errors that indicate it is not able to import the VMs. For example:
Step 6 of 7: Register VMs on shared storage -
    23 Apr 2014 10:00:14,560 WARN  - Failed to register VM <vm_name>.vmx on NAS datastore <nas_name>|
23 Apr 2014 10:00:14,968 WARN  - Failed to process VM <vm_name>.vmx. Exception: System.ApplicationException: Could not find virtual machine <vm_name>.vmx
Possible Cause: The shared storage was not added prior to the restore.
Action: Follow these steps to import the VMs:
  1. Launch the restore process again.

  2. Repeat the restore process, using the same options as during your previous attempt, until the following is displayed:

     Step 5 of 5: Confirming that failover VMs should be restored
        Proceed with restore Forge failover VMs from external USB
    storage? If so, please attach it now and answer "yes" to
    continue. If you answer "no" then USB restore will be skipped.
    [y|n]
    
  3. Enter n to skip the USB restore.

    The Restore process resumes, displaying text like this:

    Step 1 of 1: Register VMs on shared storage -
    INFO - Successfully registered VM <vm_name>.vmx on NAS
    datastore <nas_name>
    The task Restore previously backed up Forge failover VMs
    completed successfully.
    

    and then this:

    Starting task Restore Forge failover VMs.
    Step 1 of 3: Update contracts
    Step 2 of 3: Importing Forge Server Contracts \-/
    Step 3 of 3: Refreshing Forge ESX Server container
    The task Restore Forge failover VMs completed successfully.
    
    Restore Summary:
    The task "Validate user input" completed successfully.
            Step Setting Default Values completed successfully.
            Step Getting Required Passwords completed successfully.
            Step Validating Parameters completed successfully.
            Step Confirming restore completed successfully.
            Step Confirming that failover VMs should be restored completed successfully.
    The task Restore previously backed up Forge failover VMs  completed successfully.
            Step Register VMs on shared storage completed successfully.
    The task Restore Forge failover VMs completed successfully.
            Step Update contracts completed successfully.
            Step Importing Forge Server Contracts completed successfully.
            Step Refreshing Forge ESX Server container completed successfully.
    
  4. Check the imported VMs.

    1. From the vSphere client, select each of the imported VMs:

    2. Select the Summary tab.

    3. (Conditional) If a VM is tagged with a message like this:

      msg.uuid.altered: This virtual machine might have been moved or copied
      

      Select I Moved it to preserve the UUID for the VM.

      For more information, see the VMware Knowledge Base article: Changing or keeping a UUID for a moved virtual machine.