Replication not working: Specific Replication records are stuck from store to HO

Replication not working: Specific Replication records are stuck from store to HO

Version: 

6.5 Update 6


Issue: 

Some records from a store are stuck in the replication monitor which is never being replicated to Enterprise.


Steps: 

Restarted the server, the configuration manager and Replication service however the issue remains the same.


New records are processing fine only issue with some specific records was there.


Resolution: 

There can be multiple reasons for such cases however one of the reasons can be the wrong date on the store database server.


In this specific case, the store server had a date 2009 which was causing the issue. So once the date at the store server was corrected , stuck replication records started moving and replicated to HO successfully.


The incident for the reference: INC0012813



    • Related Articles

    • Replication stuck and Not Moving

      Problem: Replication not moving from HO to Specific Store. Symptoms: Replication Log File Not generated and Event Viewer is showing "INVALID CLASS ERROR" What need to be Check : 1. Right Click on My PC 2. Click on Manage 3. Now Go to Services and ...

    • Replication records stuck/ not moving from HO to all available stores

      Product Version 6.5 Update 5 Incident Reference: INC0011720 Problem Statement: Replication records stuck/ not moving from HO to all available stores Details: Replication records were stuck at HO and piled up for each and every store and they were not ...

    • Replication not working

      Environment: iVend 6.6 Problem Statement: Replication service not working due to controller application Error Screenshot: Solution: - This issue happened due to there’s an error showing from controller application when customer removed this ...

    • Replication not working from store server to HO server.

      Problem Reported - It was observed that Replication does not work from a particular store server to HO server. Cause: Problematic store database was corrupted. Troubleshooting Step: Check the store database health. Run the below command in the store ...

    • Replication event stuck with "source type" - "rtlStoreData" in replication monitor from HO to Store

      Product version : 6.5 Update 6 or below. Problem statement : "rtlStoreData" event stuck in Replication monitor going from HO to Store. Proposed solution/workaround: Generally, it happens after the EOD activity performed at store, the event of ...