Missing OVF context can cause multiple problems when using vSphere Replication. These problems include, but are not limited to the following:

• Upgrading vSphere Replication might fail.
• After an upgrade, the vSphere Replication appliance is corrupted.
• After an upgrade, the vSphere Replication appliance appears as a vSphere Replication server.
• Registering an upgraded vSphere Replication instance with vCenter Single Sign-On fails with error
  Bad exit code: 1.

The OVF context of the vSphere Replication appliance might be lost or corrupted due to some of the following circumstances:

• You restarted the vSphere Replication appliance by using the vSphere Web Client while the Client was connected to an ESXi host instead of a vCenter Server.
• You removed the vSphere Replication appliance from the inventory and added it back in.

Check if the vSphere Replication appliance has an OVF context

1. In the vSphere Replication appliance console, log in as the root user.
2. Open the /opt/vmware/etc/vami/ovfEnv.xml file. The file should contain the following properties:
   
   evs:GuestApi/evs:URL
evs:GuestApi/evs:Token
evs:GuestApi/evs:X509Thumbprint

evs:VCenterApi/evs:IP
evs:VCenterApi/evs:X509Thumbprint
evs:VCenterApi/evs:HttpPort
evs:VCenterApi/evs:HttpsPort
evs:VCenterApi/evs:SelfMoRef
evs:VCenterApi/evs:Address

Restore the OVF context of the vSphere Replication appliance

If the /opt/vmware/etc/vami/ovfEnv.xml file is empty or does not contain some of the properties listed above, the vSphere Replication appliance is missing an OVF context.

1. Use the vSphere Web Client to connect to the vCenter Server to which the vSphere Replication appliance is registered.
2. Right-click the vSphere Replication Management server VM (HMS VM) and power it off and on.

The OVF environment is restored and you can upgrade the vSphere Replication appliance.