Job servers keep in "Update Running" state, and software version keep in "-1"

Did you check the database journal for errors?

Is the DB Queue processor running? If not check these steps here to get it working https://support.oneidentity.com/technical-documents/identity-manager/8.0/installation-guide/27#TOPIC-864264 

Hi Marcus, 

Database journal showed some warning that the database "STOP because too many Slots are dead." and "Dead slot resetted".

I ran the queries following the steps in the provided url to create new service broker ID and initializing DBQueue Processor, and restarted services, there are some tasks appears in the DBQueue and gone from time to time, so I think the DB Queue processor is running. But still the Job queue is not processed and the job server state is still "Update running".

Anymore things I can do?

Hi Marcus, 

Database journal showed some warning that the database "STOP because too many Slots are dead." and "Dead slot resetted".

I ran the queries following the steps in the provided url to create new service broker ID and initializing DBQueue Processor, and restarted services, there are some tasks appears in the DBQueue and gone from time to time, so I think the DB Queue processor is running. But still the Job queue is not processed and the job server state is still "Update running".

Anymore things I can do?

If the DB Queue is now running and no new errors are showing in the Database Journal, then please check the Job Queue if there are update processes for the Job Servers. If not then try to set the flag IsInSoftwareUpdate in table QBMServer to 0 for the job servers.

There are some processes of "fire event Checkversion for object type QBMServer", "fire event DeployTargetChanged for object type QBMServer" " fire event GetConfig for object type QBMServer", are any of them related to update processes? 

I tried to set the flag IsInSoftwareUpdate in table QBMServer to 0, but it automatically changed back to 1.

If the job queue processes are triggered for orphaned job servers before migration, can they be forcibly terminated?

Yes, these are related to the update process.

You can remove the processes for the orphaned job servers by selecting them in Job Queue Info and pressing CTRL+D

And, is one (and only one) of your new job servers marked as "Update Server" in the list fo server functions?

I found an old post about how to kill running job queues, it can be done by pressing Ctrl-D, so I did it to the orphaned processes, and then the job server update process can be initialized, and the job servers are updated now.