<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
Recovering an enVision Database Number of Views Lsdata Utility Instructions for RSA enVision Number of Views How to shutdown the cluster in an Envision Environment Number of Views Webserver failed to start - Lockbox fingerprint has changed Number of Views To resolve 'Failed to read nst file' issue Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Download OTP Token Seed Files from myRSA Installing a new license on RSA Authentication Manager RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
