Issue with replication

Issue with replication

Product version:

6.6

Problem  Statement:

The replication service is not working, the service is updated and starts without problems but the logs do not move.


Proposed Solution:-

Steps  to perform to resolve the issue

1) Stop the Replication Service

2) Clear the Temp folder where iVend Replication Service is configured

3) Restart the affected machine once.

4) Restart the SQL Server once.

5) Update the Replication Service

6) Start the Replication Service

7) validate the  connection but it is good between  is good between store and HO

8)Restart the IIS




    • Related Articles

    • 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 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 Issue - Connection Status Color is Black

      Version 6.6 Issue The customer has a problem with the connection status color of the stores. Replication connection status at the replication dashboard from stores to HO appears in Green but from HO to stores the status color is in Black. Below are ...
    • Urgent Issue !! Replication issue on the HO

      Product version: iVend 6.6 latest patch Problem statement: The Replication service of 3 stores is disconnected from Enterprise to stores and vice versa.The Replication service was fine and running.There was no error in the application Log and we also ...
    • Replication issue with special price list

      Environment:  iVend 6.6 8567 Problem statement:  Price changes made on the enterprise were not reflected on the offline POS after replication queue was cleared. We then changed product description and that was successful, and the price change we made ...