4.3 Upgrade Issues

Review the following sections for troubleshooting the issues encountered after you upgrade PlateSpin Migrate:

4.3.1 Upgrade Fails: PlateSpin Installation/Upgrade File Is Improperly Quarantined by Anti-Virus Application

Issue: If an anti-virus application is installed and running on the intended PlateSpin Migrate server host, the anti-virus application might improperly quarantine the PlateSpin Server Installation/Upgrade file, which causes the installation or upgrade to fail.

Workaround: Do either of the following during the PlateSpin Migrate installation or upgrade:

  • Disable the anti-virus software.

  • Add the folder where you extract the PlateSpin Install/Upgrade file to the anti-virus application exclude list. The %TEMP% folder is the default location for extraction.

See also PlateSpin Migrate and Anti-Virus Applications in the PlateSpin Migrate 2020.2 User Guide.

4.3.2 Refresh of VMware ESXi Server Target Fails After Upgrade

Issue: When you refresh a VMware ESXi Server target after you upgrade PlateSpin Migrate, the VMware ESXi Server target might fail to refresh in the very first refresh attempt because of a timeout issue or failure to discover this target server. Consequently, you cannot migrate a workload to this target unless it is successfully refreshed.

Workaround: Refresh the VMware ESXi Server target a couple of times until it successfully refreshes.

4.3.3 After Upgrade, There Is an Extra Gray Color Workload Tag

Issue: After you upgrade the Migrate server, the Web Interface shows an extra workload tag that is assigned the color gray. This extra tag is either named as Default or named after one of the networks found in the PlateSpin Migrate Client.

For example, if the PlateSpin Migrate Client has three networks: Default, Network-test1, and Network-test2, then the extra workload tag has the name of one of these networks. (Bug 1018730)

Fix: In the Web Interface, select Settings > Workload Tags, then manually delete the extra workload tag.