Upgrade via kit or autopatch fails with "the following process must be stopped before upgrade"
search cancel

Upgrade via kit or autopatch fails with "the following process must be stopped before upgrade"

book

Article ID: 452255

calendar_today

Updated On:

Products

Automic Dollar Universe

Issue/Introduction

The autopatch (or the upgrade via the kit) may fail with this kind of errors:

The following process must be stopped before upgrade :

uxjob######:PROCESS_ID

When launching the setup on Windows, a popup error message will appear as below so it's simple to detect which process must be killed

But when this is done via Autopatch, no warning is being generated to the end user and the error can only be found after the whole Autopatch procedure has failed and the cause can be found in the maintenance.log, example here:


The following process must be stopped before upgrade :
uxjobstatus.exe:15204
uxjobstatus.exe:26484
uxjobstatus.exe:67616
uxjobstatus.exe:59264
...
Installation will be ABORTED
8-14-2026_09:48:16 : Leaving PrintMessage
8-14-2026_09:48:16 : Installation aborted !
...

_____________ ERROR ____________________________

"############################################################"
"Release 7.01.21 installation failed."
"(product restored to previous configuration)"
"############################################################"

It was observed that there were multiple jobs running that have the Auto-retry feature enabled at the Uproc level to restart automatically in case the jobs fail.

Environment

Dollar Universe Application Server 6.x or 7.x being upgraded

Cause

Very long running jobs with Auto-retry feature enabled would have the uxjobstatus, uxjobretry and uxjobend processes automatically started after the jobs were cancelled in Job Runs. In case the end user would not kill them all completely, the upgrade will fail in case any of the processes are detected.

Resolution

  1. Stop all Running jobs and the launcher to prevent new jobs from starting while the upgrade will be running.
  2. Make sure no more uxjob* processes are running on the system , as after you kill the uxjobstatus some uxjobretry and uxjobend processes can start again.
  3. Launch again the autopatch or the upgrade of the node using the installation kit, in this case if the situation would occur again you would have a popup window indicating the processes that have to be cancelled for the upgrade to be able to start as described above:

    The following process must be stopped before upgrade :

    uxjob######:PROCESS_ID