Issue with Job Servers Not Processing Tasks After Environment Setup

Did you execute the step "On the Configuration Wizard's home page, select the Enable restored database option and click Next."?

Thank you for your prompt response

Yes, after installing the tools on the workstation, I launch the Configuration Wizard and select the "Enable restored database" option.

The process completes successfully, including the database recompilation and related steps.

I’ve repeated this process several times (I took snapshots of the servers beforehand).

In the restored database (from another environment), there are already three Job Servers configured that point to servers in another network.

(I plan to delete these in Designer later and replace them with three new ones.)

To proceed step by step, I’ve started the setup with the following:

- The workstation (without any Job Server)

- The database server, on which I’ve installed a Job Server and the Database Agent

If I don’t initialize the DBQueue, it appears to start on the DB server but doesn’t process anything.

Then, when I initialize the DBQueue (using the commands from the guide), all the tools start displaying the following error:

"A system update is running. Try again later."


But before initilizing DBQueue : i had these logs after installing service and configuring it with JobServiceConfigurator using private key and adding DbAgentplugin:

<w>2025-06-12 16:09:07 +02:00 - Warning: Moving private key to the key container.<x>
<w>2025-06-12 16:09:07 +02:00 - Warning: Constrain access to encrypted configuration properties on the service account.<x>
<w>2025-06-12 16:09:07 +02:00 - Warning: Starting queue "\idm-db-int-vm".<x>
<w>2025-06-12 16:16:12 +02:00 - Warning: Constrain access to encrypted configuration properties on the service account.<x>
<w>2025-06-12 16:16:13 +02:00 - Warning: Starting queue "\idm-db-int-vm".<x>



Now i have these logs :

<w>2025-06-13 10:16:08 +02:00 - Warning: jobservicedestination: Processing is disabled (queues globally switched off).<x>

You do not need to initialize the DB queue. This is not part of the documentation section. Please look at the same section of the 9.2.2 documentation guide here. https://docs.oneidentity.com/bundle/one-identity-manager_operational-guide_9.3/page/sources/config/database/confreferencedbbackup.htm 

Thank you very much for your quick response.

I’ve taken note of your recommendation.

Indeed, previously I wasn’t performing the “Initialize DBQueue” step. However, the Job Server installed on the database server still doesn’t process any tasks.

For example, when I modify a simple property of the Job Server idm-db-int-vm  (like the url) in Designer and then compile the database,
a task like the following appears in JobQueueInfo for idm-db-int-vm:

Created by QBMDBQueueProcess: fire event GetDeployTargets for object type QBMServer
12.06.2025 16:16:13
FireGenEvent

But this task is never executed, it just remains stuck with Runtime Status = True indefinitely.

And i have these logs :

Job Server Logs:

<w>2025-06-12 16:25:00 +02:00 - Warning: Starting queue "\idm-db-int-vm".<x>
<w>2025-06-12 16:26:32 +02:00 - Warning: Stopped task requests for queue "\idm-db-int-vm".<x>
<w>2025-06-12 16:26:46 +02:00 - Warning: Constrain access to encrypted configuration properties on the service account.<x>
<w>2025-06-12 16:26:46 +02:00 - Warning: Starting queue "\idm-db-int-vm".<x>

i don't know what is the meaning of this Warning : Warning: Constrain access to encrypted configuration properties on the service account.<x>

Do tools like JobQueue Info mention that processing is disabled? 

What are the following settings from the table DialogDatabase? 

Select IsDBSchedulerDisabled, IsJobServiceDisabled, SingleUserProcess, SingleUserStart, UpdatePhase  from DialogDatabase

Thank you very much for your quick response.

I ran the following command:

UPDATE DialogDatabase SET UpdatePhase = 0

After this, the error "A system update is running. Try again later" no longer appears. I also recompiled the database.

Running the query:

SELECT IsDBSchedulerDisabled, IsJobServiceDisabled, SingleUserProcess, SingleUserStart, UpdatePhase FROM DialogDatabase

 returns:

IsDBSchedulerDisabled | IsJobServiceDisabled | SingleUserProcess | SingleUserStart | UpdatePhase
0                                     |                     0              |                    0           |     NULL            | 0

I'm planning to start the process again from scratch.

Is there a complete, up-to-date article or guide that explains how to duplicate a pre-production environment (with existing Job Servers, configuration, etc.) into a test environment, using a database restore and new Job Servers?

Also, I’d like to confirm whether my current installation steps (and order) are correct:

1-Install the Workstation and restore the database

2-Install the Database Agent and the first Job Server on the DB server

3-Install additional Job Servers (I install them and configure them with private.key in new servers)

4-Delete the old Job Servers (from the previous environment) in Designer

Thank you again for your support!

The documentation link in my answer is the latest for 9.2. x branch. If you are running on 9.2, I suggest updating to 9.2.2, as there is at least one fix that may resolve your scenario where the Update Phase wasn't reset to 0.

How you deal with the Job Servers depends on your scenario. For the restore, I would use th DatabaseAgent Service commandline tool during the migration (Configuration Wizard run), check the Queues to ensure they are empty, and then deal with the Job Servers.

The documentation link in my answer is the latest for 9.2. x branch. If you are running on 9.2, I suggest updating to 9.2.2, as there is at least one fix that may resolve your scenario where the Update Phase wasn't reset to 0.

How you deal with the Job Servers depends on your scenario. For the restore, I would use th DatabaseAgent Service commandline tool during the migration (Configuration Wizard run), check the Queues to ensure they are empty, and then deal with the Job Servers.

Thank you very much for taking the time to answer. I will try to start over and use  DatabaseAgent Service commandline tool on the DB server (to install by checking database agent role during install). Then i will install the new job servers.