Replication troubleshooting checklist

(on-premises only) If replication does not seem to be working, view the appropriate _all table(s) using SQL Server tools, to determine if data is being populated. For example, a newly added item is not available from a drop-down menu in another, replicating site. View the item_all table to see if data is being populated.

(on-premises only) If replication is not working, the table typically does not contain the newly entered data records. In this case, there probably is a problem with the replication rules.

For replication problems, check these areas:

  1. (on-premises only) Configuration Manager utility: Verify, for each site and entity, that one of these cases is true:
    • A default configuration name is defined for that site on the Sites/Entities form, or
    • You have created at least one configuration name that exactly matches the site/entity ID, including case, and that uses the site/entity’s application database.
  2. Replication Rules form: Ensure that the rules are set up properly between the site where the data was added and the one where the data was supposed to appear.

    Are the proper categories being replicated?

    Use this table to see what types of results to expect on the target site for each replicated category.

    Category Expected results on target site (for forms with Site or Site Group fields)
    A/P Posted A/P vouchers, adjustments and payments from source sites are visible on view forms.

    A/P reports contain data from source sites.

    _all tables contain account, currency, item, journal, period, vendor and tax information from source sites.

    A/R Posted A/R invoices, debit memos, credit memos and payments from source sites are visible on view forms.

    A/P reports contain data from source sites.

    _all tables contain account, currency, item, journal, period, customer and tax information from source sites.

    CCI Centralized Order Entry Credit card authorization information is replicated from the source site.
    Centralized Order Entry Customer orders with lines that have a local ship site are visible.

    Transfer orders to or from the local site are visible.

    _all tables contain customer, customer order, account, currency, item, job, period, purchase order, project, transfer order and tax information from source sites.

    Customer Portal Portal users can see item pricing. B2B users can see that prices are from multiple sites.
    Dimensions View dimensions and attributes at other sites.
    ESB Data is received in other BOD-enabled application; acknowledgement data is received in SyteLine.
    EXTFIN Not typically used between SyteLine sites.
    EXTFIN Customer Not typically used between SyteLine sites.
    EXTFIN Vendor Not typically used between SyteLine sites.
    G/L Financial and G/L reports and views show data from source sites.

    _all tables contain ledger, account, currency, period, and journal information from source sites.

    Initialize _All Parameters N/A. Used only during replication setup.
    Inventory/Transfers Transfer orders to or from the local site are visible.

    _all tables contain account, currency, item, job, period, and transfer order information from source sites.

    Invoice Builder Invoices for customer order shipments and returns can be created at target sites.
    ION Not used for SyteLine.
    Journal Builder Pending journal transactions created by Journal Builder in source site appear in the local site.

    Journal Builder site can validate data from the local site.

    Ledger Consolidation Ledger records are consolidated from source sites when invoked.

    _all tables contain account, currency, and period information from source sites.

    Ledger Detail Ability to drill down into G/L records from remote sites if transaction data is also replicated.

    _all tables contain account, material transaction and voucher pre-register information from source sites.

    Manufacturer Item _all tables contain manufacturer and manufacturer item information and cross-reference information between manufacturer item and SyteLine item records from source sites.
    Multi-Site (home forms) This applies to the Multi-Site Buyer, Controller, CRM, Customer Service, Inventory Control, Production Planner, and Project Manager categories: On the various Home forms, information from source sites is visible.
    Multi-Site Customers On the Multi-Site Customers form, customer information that is defined on source sites is visible.
    Multi-Site Items On the Multi-Site Customers form, item information that is defined on source sites is visible.
    Planning Planning is invoked for source sites when specified.

    Planning views include requirements and receipts for source sites.

    PO-CO Across Sites Upon receiving a customer’s order, the demanding site automatically creates a PO and links it to the source site.
    Purchase Order Builder POs are created in the local sites with data entered at the source site through the Purchase Order Builder.

    Purchase Order Builder site can validate data from the local site.

    Service - Global Incidents Incidents and associated events, reasons and resolutions are replicated from the source site.
    Service - Global Scheduling Shared Partners Scheduled appointments for Service are replicated from the source site.
    Service - Global Service History Summarized history information about Incidents, service orders, and units are replicated from the source site.
    Service - Global Units Units and their component configuration, warranty information and owner history are replicated from the source site.
    Service - Multi-Site SRO Copy Users can trigger the copy of a service order from the source site to the target site.
    Shared Currency Currency information from source sites is visible.
    Site Admin Site and intranet information from source sites is visible.

    _all tables contain account information from source sites.

    Vendor Portal Vendor portal users can see purchase orders initiated from multiple sites.
    Voucher Builder Vouchers and adjustments are created in the local sites with data entered at the source site through the Voucher Builder.

    Vouchers are created in the local sites with data entered at the source site through the Manual Voucher Builder.

    The Voucher Builder site, or the Manual Voucher Builder site, can validate data from the local site.

    1. View the Replication Rules form in the source site (for example, if you're expecting to see CAL data in ONT, view the CAL database), and determine if there is a rule set up with Target Site set to the site where you expect to see the data, and with Category set to the category as determined above.
    2. If such a record does not exist, this means the behavior was expected. You can create a new rule if desired, and retest to verify that the data was passed over.
    3. If the record exists, check its Interval Type:
      • If the Interval Type is Transactional, there might be another problem with the replication setup. Continue through the other steps in this checklist.
      • If the Interval Type is Immediate, there might be a problem with the setup of the replication services.
      • If the Interval Type is something other than Transactional or Immediate, wait until the time specified in Start Interval At before testing again. If the interval time has passed and the change has still not occurred on the target machine, there might be a problem with the setup of the replication services.
  3. (on-premises only) Sites or Sites/Entities form: Ensure that the database name and the linked servers (for transactional replication) or user maps (for non-transactional replication) are set up correctly.
  4. Replication Management form: You must click the Regenerate Replication Triggers button on this form after any replication rules have been changed. Failure to do so will result in replication not working properly.
  5. Find Replication Setup Issues form: Use this form to find problems relating to the setup of replication from the current site to another site for a particular database table or stored procedure.

    Not all problems found by this utility are valid in all situations. For example, it checks to see if a user name is set up between the sites, which applies only if non-transactional replication is being used.

  6. (on-premises only) Replication Errors form: This form shows the data that failed to submit to a target site during non-transactional replication. Use the form to fix and resubmit data, or delete it.
  7. (on-premises only) Replication Tool: This tool on the utility server is used to troubleshoot non-transactional replication.
  8. (on-premises only) ReplicatedRows3 and ShadowValues tables: When something is to be replicated through non-transactional replication, it gets copied to the ReplicatedRows3 and ShadowValues tables. See the Infor Mongoose Replication Reference Guide for details. If the data is not there, it is likely that either your replication rules are not set properly or that you need to click the Regenerate Replication Triggers button on the Replication Management form.
  9. (on-premises only) MSMQ or Message Queuing: Turn on journaling.
  10. (on-premises only) Event Viewer: Check the event viewer in the Windows Administrative Tools on the utility server or database server. The events that are logged may give you a clue about where replication failed.
  11. UETs: If you are using user extended tables, and the UET information is not replicating properly, see the information about UETs and _all tables in the Infor Mongoose Replication Reference Guide.