MID Server shows invalidated status after auto-upgradeIssue After an instance upgrade, the MID Server performs an auto-upgrade. After the auto-upgrade, the MID Server does not show a status of Valid. The default keystore used by the MID Server becomes invalid. Symptoms The following conditions exist after an instance upgrade: •The MID Server performed an auto-upgrade. •The MID Server status shows as invalidated. •The MID Server log file contains the following error: Symptom StartupSequencer SEVERE *** ERROR *** Unable to load keystore: Unexpected IOException loading KeyStore, caused by: Keystore was tampered with, or password was incorrect •A rekey attempt on the MID Server fails. Release Cause The default keystore used by the MID Server becomes invalid. Resolution Complete the following steps to validate the MID Server again. 1.Go to MID Server > Servers, and select the MID Server that shows No in the Validated column. 2.Use the Related link to try to rekey the MID Server. 3.Manually remove the keystore file from the MID Server install directory: ./keystore/agent_keystore.jks 4.Restart the MID Server from the host machine where the MID Server is installed. 5.Go to MID Server > Servers and validate the MID Server through the instance. The MID Server is now up and validated.