Newly configured store not seen in replication monitor
Product version:
6.5 Onward
Problem Statement:
Configured new store in iVend. Now this newly configured store is not seen in the replication monitor at Enterprise.
Proposed Solution:
In the store configuration, there is option ‘Is On Premise’, please check this option, if this option is not checked than in this case this newly created store will act as the store, however it will use the DB of Enterprise so there is no physically new DB created for this store hence not seen in replication monitor.
Steps if any:
NA
Constraints/Scenarios:
NA
Related Articles
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 ...
Replication Monitor
Introduction iVend Retail has an in-built data flow mechanism from the Head Office (Enterprise) to the Stores and likewise from the sStores to the Head oOffice – this mechanism is called Replication. This data flow can contain the flow components ...
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 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 ...
Replication Monitor Error: 'System.OutOfMemoryException' was thrown
Replication Monitor Error: 'System.OutOfMemoryException' was thrown. Environment : iVend 6.6 Problem Statement : Replication monitor error in Store ."Exception of type 'System.OutOfMemoryException' was thrown." Proposed Solution/Workaround : The ...