OS: Windows 2019 and UIM 20.3.3. Wasp on OC not starting correctly.
- wasp 20.33hf1
Release : 20.3
Component : UIM OPERATOR CONSOLE - WASP & CORE
- leftover corrupt artifact in the wasp.cfg (reportscheduler webapp)
A child container failed to start error was displayed in the wasp log.
This highlighted one of the webapps, the ump_reportscheduler.
The webapps section of the wasp.cfg looked fine but we decided to delete that webapp and redeploy ump_reportscheduler v20.10 as we thought somehow it might have become corrupted.
Once deleted and then redeployed, the wasp started up fine without error and we could access the Operator Console and login.