Replication Error : CreateSendDumpDataJob : error: Cannot find column ProcessDate

Replication Error : CreateSendDumpDataJob : error: Cannot find column ProcessDate

Version:

 6.6


Issue: 

Error message in replication dashboard, Replication Error : "CreateSendDumpDataJob : error: Cannot find column ProcessDate" Message, below is the screenshot for the same:



And replication was not moving from either way for this store.


Solution:

 It is a Dated version issue. This issue was resolved after applying the latest patch 7702.


    • 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 ...
    • Unable to Update Customer master from iVend

      *********This KB article is for internal use only********* Environment: Ivend 6.6 Problem statement: Unable to Update Customer master from iVend Symptoms: While updating customer master from iVend below ivend to SAP integration error occurred: ...
    • While sending the test email it thrown error as "The SMTP server requires a secure connection"

      Environment: iVend Version 6.6 Problem Statement: While sending the test email it thrown error as “The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.0 authentication required”. Error ...
    • SALES REPLICATION ERROR

      Environment: IVend 6.6 with SAP B1 Problem statement: After Applying patch 7723 for version 6.6 sales are not replicating. Did the test by modifying an article and after replicating but the sales did not. Below troubleshooting steps followed: 1.- ...