MID Web Server Context fails to start, after doing an instance upgrade rollbackIssue After doing an instance upgrade rollback, the MID Web Server Context fails to start. In the application node logs, the following Key Management Framework error is see (sys_id may be different): HMAC validation failed for: 388db2ba1b2211109f3f202a2d4bcb4c : com.glide.kmf.AKMFKeyRegistry$KeyRegistryException: HMAC validation failed for key: 388db2ba1b2211109f3f202a2d4bcb4c : com.glide.kmf.AKMFKeyRegistry$KeyRegistryException: HMAC validation failed for key: 388db2ba1b2211109f3f202a2d4bcb4c : com.glide.kmf.AKMFKeyRegistry.validateHmac(AKMFKeyRegistry.java:345)com.glide.kmf.KMFModuleKeyRegistry.getKeyById(KMFModuleKeyRegistry.java:158)com.glide.kmf.KMFModuleKeyRegistry.getKeyByType(KMFModuleKeyRegistry.java:85)com.glide.kmf.KMFOutputBaseBuilder.getKMFOutputObject(KMFOutputBaseBuilder.java:103)ReleaseThis affects instances that rollback an update that had upgraded from pre-San Diego, to San Diego or later. e.g. Rome to Tokyo. Then rollbacked to Rome.ResolutionSee KB1208578 HMAC validation errors after upgrading an instance from Rome to San Diego or later, and subsequently cloning it back to Rome.