<systemname>_sync_succeeded file will have incorrect node name,(ex site-LC1 instead of site-CA1)
The work around fix for customers with the issue:
? [CA] Stop all services on the CA node except for the NIC DB service. (the replication client should be off)
o You should make this the offline collector if possible
o This also assumes that the CA is currently sync?d with the DS node using the wrong subscription name.
? [CA] Run database\cmd\remove_mobilink_subscription.cmd <sitename>-LC1
or whatever the sitename value is in the syssync table
? [DS] Run database\cmd\remote_sysnc_user.cmd <sitename>-LC1
o This will clean up the ml_subscription, ml_user, and ml_sync_user table entries assocated with <sitename>-LC1 on the DS
? [CA] Update the db with the ECE2433WorkAroundFix.sql (can be found in ECE-2433)
o Installing this in the CA by copying to the database\sql\patches directory and then executing database\cmd\install_patches.cmd.
? [CA] Run database\cmd\create_mobilink_subscription <sitename>-DS1
? [CA] Start Replication Service
? [CA] Verify replication ok, and using correct name.
? [CA] Start remaining services if any.
Verify _<systemname>-sync_succeeded file has the correct name for the CA node.
Related Articles
Workflow Decision Node takes wrong path in SecurID Governance & Lifecycle 75Number of Views Group owner approval is getting assigned to wrong owner in RSA Identity Governance & Lifecycle 42Number of Views Risk-Based Authentication from Cisco ASA 9.3.1 redirects to wrong URL for RSA Authentication Manager 8.1 185Number of Views Error: 'Problem processing request: message is 'Failed to connect to the ACE/Server snoopy56 with port = 5570. Wrong ACE/S… 46Number of Views Add Authentication Source Access Rules 21Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x