Module Navigation

Troubleshooting Sage 300 Integration Error: Target System Rejected the Write

When Arcoro syncs a brand new employee to Sage 300 CRE, it sends that employee to Sage 300 CRE's HH2 web service to be created for the first time. If HH2 turns down that request, Arcoro cannot get an employee record back, so it cannot continue building that employee, and this message is logged against that one employee. Every other employee in the same sync keeps processing normally. Because the create itself is what failed, nothing was actually added to Sage 300 CRE for that employee, not even a partial record.

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.WriteArcoro sends a brand new employee to HH2 to be created for the first time, and HH2 responds by rejecting that request, rather than a connection or authorization failure. Never occurs on an update to an employee that already exists in Sage 300 CRE, and never occurs on a run that is not actually persisting changes.Record skipped (this employee only); the sync continues to the next employeeRetry the sync. If it fails again, read the raw HH2 response text logged for the same employee and route to the matching sibling article below.

Finding the Real Cause

  1. Open the sync log for the run and find the affected employee by identifier. This message is always attached to a long, generic system sentence that begins "Error: Failure to connect/sync due to bad data and/or connection...". Ignore that opening boilerplate. The part that identifies this specific problem is the shorter sentence that follows it, starting with "HH2 failed to create this employee". Match on that fixed sentence.
  2. On the same employee, in the same run, look for a separate Error entry logged earlier than the one in step 1. Arcoro logs the exact text HH2 sent back as its own line before it logs the generic message above. That earlier line is raw passthrough text from HH2, not Arcoro wording. You can tell it apart because it will not read like an Arcoro sentence: no "this could be a problem with the data" phrasing, no mention of contacting support. It may be short, technical, reference a field or code directly, or simply read as an HTTP status description such as "400 BadRequest Response With No Body" if HH2 did not send back any usable detail.
  3. Use that raw text to route the ticket to the sibling article most likely to hold the real answer:
    • References an employee code, number, or a required demographic field: see the identity and demographics article.
    • References a duplicate or an employee that already exists: see the duplicate record article.
    • References a hire date, termination date, or employment status: see the employment status article.
    • References a pay rate, pay group, or pay frequency: see the compensation article.
    • References tax, filing status, or an exemption count: see the tax setup article.
    • References a bank account or routing number: see the direct deposit and banking article.
    • References a deduction, benefit, or fringe code: see the deduction, benefit, and fringe article.
    • References a union, classification, workers comp, or occupation code: see the union and classification article.
  4. If there is no separate raw-text line at all for this employee, or the sync stopped entirely instead of moving on to the next employee, this is probably not this article's message. A connection or authorization problem on the same create call ends the whole run instead of producing this message. Check the connector auth and connector configuration articles in that case.
  5. Confirm this really is a first-time create. Arcoro only reaches this code path when it could not match the employee to an existing Sage 300 CRE record and tried to add a new one.

Confirming the Error

  1. Open the Sync History screen for the run in question.
  2. Find the People/Employees write step and check its Failures column. A number greater than zero means at least one employee ended the run in an error state, but it does not by itself confirm this exact message; you still need to open the step detail.
  3. Open the Employees step detail and locate the affected employee by identifier.
  4. Confirm the logged message ends in the fixed sentence "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." A message that is similar but not an exact match is a different problem and belongs in a different article.
  5. Check the Added column for the same step. Because the create failed, this employee will not be counted in Added for this run; it is only reflected in Errors and Failures.

Resolving the Error

  1. Confirm the sync run actually persists changes rather than only previewing them. This message, and any create at all, cannot happen on a run that does not persist changes.
  2. Retry the sync. Because a failed create leaves nothing behind in Sage 300 CRE for this employee, a second attempt is safe to run without any cleanup first.
  3. One retry, two at most, is a reasonable ceiling before treating this as unresolved by retrying alone.
  4. If it fails again, read the raw HH2 response text on the same employee as described in "Finding the real cause", and act on whatever the matching article recommends.
  5. To confirm the fix worked, run the sync again and check that the same employee identifier now appears in the Added column for the Employees step, with no error logged against it.

When to Escalate

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

  • The raw HH2 text found in Finding the real cause does not clearly match any of the sibling causes listed above.
  • The same employee fails again after you have corrected the suspected data issue and the sync has been retried.
  • The employee still does not exist in Sage 300 CRE after a supposed fix.
  • Before escalating, capture: the employee identifier from the sync log, the exact raw HH2 error text found in the same run, whether any other message is logged against the same employee in the same run, and whether the failure reproduces on a second sync attempt.
Was this article helpful?
0 out of 0 found this helpful