BOI not pushing web orders to Sage 100

We are encountering an issue where CIM Cloud web orders are successfully pushing to the ERP Driver but is failing to create a BOI session. Any suggestions on what other pieces we can troubleshoot before reinstalling the ERP Driver? 

What we have tried:

  • Re-registered .dlls
  • Confirmed the Windows user is set up with full admin rights
  • Confirmed the Sage user has all applicable rights enabled
  • Confirmed Sage is set up to allow external connections
  • Sales order object test script was run successfully on both the Windows user and another admin user
  • Tried running ERP Driver services under the other admin user (orders are still failing with the same BOI connection error)
  • Confirmed at least some syncing processes not using Sage business objects are syncing data to the site successfully (products, shipping addresses, taxing data)
  • Created a new Sage user with the same rights as the original user, and configured our sync tool to use it (to rule out corruption of the original user)
  • Looked into potential Avatax integration conflicts on BOI connections
  • Ran the Sage object interface test with the new user successfully

Web order error:

Parents
  • 0

    You ran the OI test successfully?  This ensures the Sage 100 system is working correctly for BOI.

    If this is OK, you are looking at issues where the interface is running (where the Sage 100 workstation client should be installed and run at least once), or a permission problem.

    (Of course there are issues like using mapped drive paths, which don't work for services... and things like having the machines on different networks / sub-nets, which Sage 100 does not like).

Reply
  • 0

    You ran the OI test successfully?  This ensures the Sage 100 system is working correctly for BOI.

    If this is OK, you are looking at issues where the interface is running (where the Sage 100 workstation client should be installed and run at least once), or a permission problem.

    (Of course there are issues like using mapped drive paths, which don't work for services... and things like having the machines on different networks / sub-nets, which Sage 100 does not like).

Children