Application Unresponsive After Failed Upgrade
Troubleshooting
Problem
The application becomes broken or unresponsive after an upgrade fails and rolls back.
Cause
If an error occurs during an upgrade, the installer rolls back and reinstalls the previous version of the application. For security reasons, the installer does not store passwords for any previously configured custom accounts, so it cannot automatically restore permissions during rollback.
If custom accounts were used for the Web Server or Scheduler API, they must be reconfigured manually.
Solution
Reconfigure the custom accounts for both the Web Server and the Scheduler API:
- Open IIS.
- Select Application Pools.
- Right‑click WebServer.SEI and choose Advanced Settings.
- Scroll to the Identity section.
- Click the ellipsis button on the right.
- Select Custom Account.
- Click Set and enter the custom account’s username and password.
- Confirm by clicking Ok on each window.
- Repeat the same steps for Scheduler.SEI.