Replication not working from store server to HO server.

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 server database.

DBCC checkdb


Resolution: Corrupt database was causing the replication to not workk. So need to repair the store server database along with DBA for a working replication.



    • 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 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: 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 ...
    • Replication from HO to store or from store to HO is freezed

      Environment: 6.5 updates 6 and before Problem Statement: Replication is not working between store and Enterprise Resolution: One of the basic reasons for replication not working can be the replication service not working correctly or there is SQL ...
    • Addon information was not updated for newly created store

      Environment: iVend 6.6 integrated with SAPB1 Problem Statement: Addon information was not updated for newly created store Symptoms: Not Applicable Resolution/Work Around: Issue is already fixed in the latest iVend patch (8567). As a workaround we ...