ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

unisrvcntr not working properly


Article ID: 145297


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE


I'm trying to understand why, when the instance is in a failed-over state with the Primary Scheduler down, that restarting the Scheduler via unisrvcntr give a success message but doesn't actually start the Scheduler.  The only way I can get the Scheduler to start is via eventor.


Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)


The issue occurs sometimes when a WAAE service process is terminated abnormally.
As a workaround, the WAAE server process can be started up using "as_server -A $AUTOSERV" or "event_demon -A $AUTOSERV".