Before Arcoro reads anything from Sage 100 or writes an employee back to it, the sync has to log in to the Sage 100 connector once for the whole run. That login needs two things you cannot see: a platform API key and a platform API secret that Arcoro configures behind the scenes. It also needs the username, password, and service URL that were entered when the connector was set up. If either platform value is missing, or if the login attempt itself is rejected, the sync stops right there. No entity gets a chance to read or write, because the login step has to succeed first. Every message in this article means the same thing at a high level: the connector never got past login for this run.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Sage 100 Construction Provider failed to authenticate. Please run the Sync again and if the problem persists contact Arcoro support. | Read or write | The login request to Sage 100 completed, but the result it returned was anything other than a validated success. This is not limited to a login that never got a response — a response can come back and still count as a failed login. | Sync stopped before any entity was read or written for this run. | Escalate; Verify the connector's username, password, and service URL first. |
| Sage 100 Construction Provider could not read config setting HH2ApiKey. Try the Sync again and if this problem persists contact Arcoro support. | Read or write | The platform API key value that Arcoro stores for this integration was empty or missing when the login step started, before any request was sent to Sage 100. | Sync stopped before any entity was read or written for this run. | Escalate to engineering. You cannot see or edit this setting. |
| Sage 100 Construction Provider could not read config setting HH2ApiSecret. Try the Sync again and if this problem persists contact Arcoro support. | Read or write | The platform API secret value that Arcoro stores for this integration was empty or missing when the login step started, before any request was sent to Sage 100. | Sync stopped before any entity was read or written for this run. | Escalate to engineering. You cannot see or edit this setting. |
Confirming the Error
- Open the sync execution for the reported time in the Sync History screen for the affected connector.
- Because the login step runs once for the whole connector before any entity is processed, look at the connector-level result for that execution rather than an individual entity row. A non-zero count in the Failures column, together with every entity showing zero in Added, Updated, and Unchanged, is the signature of a login-stage stop rather than a data problem in one entity.
- Open the failure detail for that step and read the logged message text.
- Match the fixed part of the sentence against the three messages in this article, ignoring only the trailing instruction to retry or contact support. "failed to authenticate" is the authentication failure. "could not read config setting HH2ApiKey" is the missing API key. "could not read config setting HH2ApiSecret" is the missing API secret.
- Rule out a connection timeout before treating this as one of the three messages above. This provider also has a distinct timeout path that rewrites the failure to a message beginning "Time Out: resource connection to HH2 can not be placed at this time." If the log shows that text instead, treat it as a connection timeout and note that separately when escalating; it is a related but different symptom from an outright login rejection.
Resolving the Error
- Confirm the connector-wide pattern from How to confirm: a non-zero Failures count with no entity activity for the run.
- All three messages already tell you to run the sync again. Ask for one re-run before escalating, so the ticket can note whether the failure reproduced.
- If the message text is the authentication failure ("failed to authenticate"), check the connector's user name, password, and service URL settings on the connector configuration page. These are the only pieces of this login that anyone outside Arcoro can see or edit.
- If the message text names either the API key or the API secret setting, skip the check above. Both of those are platform-level settings that only Arcoro can see and this must be escalated.
- Escalate with the connector name, the sync execution date and time (and its Id if the screen shows one), the exact message text from the log, and whether it reproduced on re-run.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- Always escalate the missing API key or missing API secret message.
- Escalate the authentication failure message after you have confirmed the username, password, and service URL are correct, and a re-run still fails.
- Escalate immediately, and flag it as a possible connection issue rather than a login rejection, if the log instead shows the timeout message described in How to confirm.
- Escalate without waiting for a second re-run if this is happening on every run for this connector.