Problem

After a server reboot, a UMRA service task is stuck displaying the "running" status, even though it is not really running.

Cause

If the server is rebooted or crashes while a task is running, the file that holds service task queue information may become corrupted.  This causes the task to display the incorrect status, and may even prevent the task from being run manually or by the scheduler.

Solution

  1. Stop the UMRA Service from the Windows services console
  2. Browse to the UMRA Service's installation directory (e.g, C:\Program Files (x86)\Tools4ever\UmraService\)
  3. Go into the Config folder
  4. Rename UmraTaskQueue.sac to UmraTaskQueue.old
  5. Start the UMRA Service