Standard manager fails to start

A concurrent program that had its basepath defined wrong when it was registered was submitted. which caused the standard manager to crash. and since the concurrent program was in the standard manager queue, the manager would crash as soon as the concurrent managers are restarted since the program is executed as soon as the concurrent managers are online. None of the log files reported any error except in the manager log of the deactivated processes ( of the standard manager) in the front end. all of the deactivated processes log's contained the request ID of the concurrent program.

The solution was to remove the concurrent program from the queue and correct the basepath of the concurrent program under the system administrator -> applications -> register to the correct custom top path as in the OS level and restart the concurrent managers.