Idea ID 2785773
During an upgrade from Sentinel 18.104.22.168 the database upgrade failed, after the main Sentinel upgrade failed. After investigation, it was determined that there were some orphaned jar files from 22.214.171.124 that were causing the database upgrade to fail. Putting something in the install script to look for *RELEASE.jar that are not from the upgrade currently being attempted would prevent this issue from occurring.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.