DSP: Post upgrade - Syncs do not run due to multiple NODES (4224807)

After upgrading or reinstalling Directory Sync Pro for AD, you may notice that when attempting to run any syncs, the latest log entry remains at "User Initiated Sync" indefinitely.
You have cloned profiles and even created a new one, but this behavior still persists.

Check the NODES section of DirSync Pro. You will likely find that there are two listed (for non-clustered DS Pro servers, this is unexpected).

It is necessary to adjust the NODES accordingly:

1. You can remove the old NODE entry by selecting it on the NODES page and clicking the REMOVE button.
2. The new NODE should be activated.

• You can also run the SQL query below on the DirSyncPro database to check the status.

SELECT * FROM [DirSyncPro].[dbo].[DirSync_Nodes]

• Let's assume that your first NODE entry has a DirSync_Nodes_PK ID of 1. In that case, you should see ID 2 under the DirSync_Nodes_PK column, which should correspond to your new NODE entry.
• Ensure that it is online and activated, and also verify the Last Contact date.

3. Next, try restarting the Quest Directory Sync Windows service. You can also restart the IIS services by executing the IIS reset command or reboot the DirSync Pro server.
4. After that, please attempt the sync again.

NOTE: For clustered DS Pro nodes, please consult Binary Tree Support for a case-by-case examination and guidance.