Module Navigation

Troubleshooting Sage 100 Integration Error: Target System Rejected the Write

Arcoro sent a brand new employee to Sage 100 and asked HH2 to create it. HH2 did not hand back a new employee record for that request. Arcoro cannot tell from that response whether the problem is bad data on the employee or a problem on HH2's side, so it logs a single generic message and stops working on that one employee. Every other employee in the sync keeps going. Nothing else about this employee synced up to this point, since the create call is the very first thing Arcoro sends to Sage 100 for a brand new employee.

Error Messages

Message textDirectionOccurs whenOutcomeFix
HH2 failed to create this employee. This could be a problem with the data or an issue with HH2's service. Try the Sync again and if the problem persists contact support.Arcoro to Sage 100 (write)The employee is new to Sage 100 (no matching Sage 100 record was found), the create request to HH2 did not come back with a new employee record, and the sync is running in a mode that actually persists data.Record skipped. Sync continues with the next employee.Re-run the sync; if it fails again, escalate with the captured evidence.

Errors That Came From the Destination System

Before this message is ever logged, Arcoro already writes a separate error line for that same employee containing the raw text that HH2 sent back for the failed create request. That raw text is passthrough: it is Sage 100's own wording, not Arcoro's, and it was copied into the log as-is.That is expected. It is HH2's own error text, not an Arcoro message.

  1. Arcoro messages read as complete, deliberate sentences, they consistently name HH2 or Sage 100 or the specific field in question, and they end with guidance such as asking you to try again or to contact support. They come from a fixed, small set of English sentences written by Arcoro's own engineering team.
  2. Passthrough text from the destination does not follow that shape. It can look like a raw code, a short fragment, or web-service style wording, and it will not match anything documented in this knowledge base no matter how carefully you search it.
  3. One destination-originated message is rewritten by Arcoro before logging: a connection timeout to HH2 is turned into the sentence "Time Out: resource connection to HH2 can not be placed at this time. Please try your sync again later. If error continues, please contact Customer Support." If you see this exact sentence, recognise it as a timeout. It also stops the entire sync run, not just the one employee, so treat it differently from a single employee's error, see How to confirm below.
  4. If you find a message you cannot match to anything in this knowledge base and it does not read like a full Arcoro sentence, treat it as passthrough text from Sage 100 or HH2. Capture the exact text and escalate.

Confirming the Error

  1. Open the sync execution for the Sage 100 connector in the Sync History screen.
  2. Open the step for the Sage 100 connector and find the employee's entity row.
  3. Check the Failures column at the step or sync level first. A non-zero Failures count means the entire run stopped, which is a different problem than a single employee's error, see the timeout sentence above. If Failures is zero, continue.
  4. Check the Errors column for the employee's row. A non-zero count here means this employee, and possibly others, had a record-level problem, but the run itself kept going.
  5. Open the errors list for that employee and look for the exact sentence "HH2 failed to create this employee." Match on that fixed part of the sentence, since it never changes.
  6. If you also see a separate error line above or near it with different wording, that is the raw text HH2 returned for the failed create request. Capture it too, see Errors that came from the destination system above.
  7. Confirm the employee has no existing Sage 100 record. This message only occurs when Arcoro is trying to create a brand new employee, not when it is updating one that already exists.

Resolving the Error

  1. Re-run the sync for this connector. The message itself states the problem may be transient, so a re-run is the first and simplest step.
  2. If the re-run succeeds, no further action is needed.
  3. If the re-run fails again with the same message, escalate. Before escalating, capture:
    • The connector name.
    • The sync execution (date and time, or execution identifier).
    • The employee identifier and name.
    • The exact message text from the employee's errors list, including any separate raw text line from HH2.
    • Whether the failure reproduced on the re-run.

When to Escalate

If any of the following occur, you may need to reach out to Arcoro support for additional assistance.

  • The same employee fails with this message on a second, clean re-run.
  • The errors list contains destination text you cannot match to any Arcoro message or any article in this knowledge base.
  • Multiple employees fail with this same message in the same sync execution.
  • You see that the employee was partially created in Sage 100.
Was this article helpful?
0 out of 0 found this helpful