Planning
your next identity automation
solution?
This article
covers a legacy Tools4ever product. If you
are evaluating NIM in the United States or
Canada,
start with the NIM guides for setup,
integrations, and automation
workflows.
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
- Stop the UMRA Service from the Windows
services console
- Browse to the UMRA Service's
installation directory
(e.g, C:\Program Files
(x86)\Tools4ever\UmraService\)
- Go into the Config folder
- Rename UmraTaskQueue.sac to
UmraTaskQueue.old
- Start the UMRA Service