Auto refresh replication whenever the stores servers are started / re-started.

Auto refresh replication whenever the stores servers are started / re-started.

Problem Reported: 

when customers do the restarting of the servers, Replication doesn't work and they have to update the replication service again.




Cause:  

Replication service takes some time to reconnect back and establish a connection when started again and thus when we restart the server it takes time to create the connection.


Resolution: 

This is not an issue. This is a matter of observation. When we restart the server it takes time to create the connection.  Replication starts to work When the request reaches the head office.


    • Related Articles

    • Troubleshooting iVend Replication

      Introduction iVend Cloud is a Software as a Service offering that encompasses the full capabilities of the iVend Retail omnichannel solution suite with fully managed services delivered via a hosted infrastructure. iVend Cloud offers seamless ...
    • 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 ...
    • Customized addon events in Replication Records Stuck for Stores on HO Replication Dashboard

      Internal Purpose Environment : iVend 6.6 Problem Statement : It was noticed that iVend Enterprise replication monitor has add-on related records ,stucked for long time and need to ignore it . Symptoms : Customized Addons were applied on iVend ...
    • 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 ...