Sage 300 CRE syncs do not talk to your ERP directly. Arcoro sends every request through HH2, a hosted service that sits between Arcoro and Sage 300 CRE. Before any employee or time data can move, Arcoro has to log in to HH2 using the credentials on the connector, and every request after that has to actually reach HH2 and get a response back. This article covers the two ways that first step can fail: HH2 does not accept the credentials, or HH2 never responds in time.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Sage300 CRE Provider failed to authenticate. Please run the Sync again and if the problem persists contact Arcoro support. | Both read and write | HH2 responded to the login request, but it did not return a validated result. This covers wrong username or password, a locked account, invalid API credentials, an invalid HH2 service URL, or HH2 returning no result at all. The message text is the same for all of these; the log does not say which one. | Sync stopped | Verify the username and password on the connector, then confirm those credentials still work directly in Sage 300 CRE or with their HH2 login. |
| Arcoro Integration Service is unable to establish a successful connection to HH2's service. Wait a few minutes and try the sync again. If the error continues, please contact Arcoro Customer Support. | Both read and write | A request to HH2 did not get a response before Arcoro's own request timeout elapsed. This is not a rejection from HH2; HH2 simply did not answer in time. | Sync stopped | Wait a few minutes and re-run the sync once. If it keeps happening, escalate; this is an HH2 connectivity issue, not something fixable in the connector setup. |
Confirming the Error
- Open the sync run in Sync History for the affected connector.
- Both of these messages stop the entire run, so look at the run-level result rather than a single entity row. A non-zero Failures count for this family means the whole sync ended early. No entities after the point of failure will show meaningful Added, Updated, or Unchanged counts.
- Match the log text on the fixed part of the sentence, not on any values in quotes: "failed to authenticate" for the authentication message, or "unable to establish a successful connection to HH2's service" for the timeout message.
- The authentication message appears in the log on its own, without any extra boilerplate text in front of it.
- The timeout message is different: it is always preceded by a separate generic sentence that starts "Error: Failure to connect/sync due to bad data and/or connection." That generic sentence and the HH2 timeout sentence are both Arcoro-authored and both belong to this same failure. Do not treat the generic sentence as a second, unrelated error.
- If the log text does not match either sentence above and instead reads like a raw technical response from HH2 (for example a "Bad Request" body or a server error description), that is passthrough text from HH2 itself, not one of the two messages in this article. See When to escalate.
Resolving the Error
Sage300 CRE Provider Failed to Authenticate
- Re-confirm the username and password configured on the Sage 300 CRE connector are current and have not been changed or expired on the HH2 or Sage 300 CRE side.
- Re-run the sync once after confirming credentials.
- If it fails again with the same message, escalate; the connector's HH2 API credentials or the HH2 service URL may need review.
- To confirm a fix worked, re-run the sync and check that the run no longer stops at authentication and that entity rows show normal Added, Updated, or Unchanged counts.
Arcoro Integration Service Is Unable to Establish a Successful Connection to HH2’s Service
- Wait a few minutes, as the message states, then re-run the sync. One retry after a short wait is reasonable.
- If the same message appears again on that retry, do not keep retrying repeatedly. Escalate; this points to HH2 not responding.
- To confirm a fix worked, re-run the sync and check that the run completes past authentication and the entity rows show normal Added, Updated, or Unchanged counts.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- Either message repeats after you confirmed credentials (for the authentication message) or waited and retried once (for the timeout message).
- The log text does not match the fixed wording in the table above and instead looks like raw text passed through from HH2, such as a technical response body or server error description.
- Capture before escalating: which of the two messages appeared, the date and time it started, and whether it happens on every run or only intermittently.