MID Server not starting after failed auto-upgrade - Failed to clean the DB Cached files during MID startupIssue MID Server not starting after failed auto-upgrade. The log will contain errors like the ones shown below. In the Agent Log:(807) Wrapper-Stopper Setting mid status to Down(807) Wrapper-Stopper Instance.updateAgentRecordStopped(), OperationalState=UPGRADING(230) Wrapper-Stopper SEVERE *** ERROR *** (63068)FileDBProviderImpl - Failed to clean the DB Cached files during MID startupIn the Wrapper log:INFO | jvm 1 | com.snc.dist.mid_upgrade.UpgradeMain runINFO | jvm 1 | SEVERE: com.snc.dist.mid_upgrade.UpgradeException: java.io.FileNotFoundException: Drive Letter:\Mid Server_Folder\agent\bin\mid.bat (Access is denied) The (Access is denied) message is misleading, the actual reason it's failing is that the files have already been deleted.ReleaseAnyCauseFor an undetermined reason(s), something interrupts the Auto-Upgrade process and leaves the Mid-Server in an invaded state. When the Auto-Update process resumes, it's unable to successfully perform many of the tasks it's programmed too because they were already completed by the previous attempt and the logs will contain errors like those shown here and, in the Description, above. ileDBProviderImpl - Failed to clean the DB Cached files during MID startup FileNotFoundException: Drive Letter:\Mid Server_Folder\agent\bin\mid.bat (Access is denied) ResolutionYou must perform a manual upgrade. KB0713557 How to manually restore a MID Server after a failed upgrade - Support and Troubleshooting (servicenow.com)