Before Arcoro can read or write anything for a Sage 300 CRE company, it has to build a connection to the HH2 service and log in. That step needs a handful of settings: a service address, a sign-in name and password, and an API key and secret. If any one of these is missing or blank, Arcoro cannot finish logging in and the entire sync run stops immediately, before it touches a single employee record. Some of these settings live on the connector itself and can be corrected by an Arcoro implementation user. Others are deployment-level settings that users, and no connector screen, can see or change.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Sage 300 CRE Provider could not read the configuration setting '[configuration setting name]'. | Both read and write | The named connector configuration setting is not present on the connector, or is present but blank, at the point Arcoro builds the connection or logs in. | Sync stopped | Open the connector configuration and enter a value for the named setting. |
| Sage 300 CRE Provider could not read config setting Sage300HH2ApiKey. Try the Sync again and if this problem persists contact Arcoro support. | Both read and write | The API key deployment setting is missing or blank at login time. This setting is not part of the connector configuration and is not visible on any connector screen. | Sync stopped | Retry the sync once. If it fails again, escalate to Arcoro support. |
| Sage 300 CRE Provider could not read config setting Sage300HH2ApiSecret. Try the Sync again and if this problem persists contact Arcoro support. | Both read and write | The API secret deployment setting is missing or blank at login time. This setting is not part of the connector configuration and is not visible on any connector screen. | Sync stopped | Retry the sync once. If it fails again, escalate to Arcoro support. |
Setting Names That Can Appear in the First Message
- HH2 Service URL - connector setting. Read while Arcoro builds the connection, before login is attempted. This is the earliest of the three settings to fail if it is missing.
- UserName - connector setting. Read during login, after the API key and API secret have already been read successfully.
- Password - connector setting. Read during login, immediately after UserName, and after the API key and API secret have already been read successfully.
Confirming the Error
- Open the sync execution for the reported run in Sync History.
- Open the step for the Sage 300 CRE connector.
- These messages occur before any entity is processed, so you will not find them attached to a specific entity's Errors count the way an employee-level message would. Look instead at the overall run outcome and its Failures count.
- A non-zero Failures count for this run means the sync did not complete normally. For this family, it means the connector never finished logging in, so no entity in that step was read or written.
- Match on the fixed part of the sentence, not on the value in quotes or brackets. For the first message, match on "Sage 300 CRE Provider could not read the configuration setting" and read the quoted name that follows to know which setting is missing. For the other two, match on the full sentence including "Sage300HH2ApiKey" or "Sage300HH2ApiSecret", since those key names are fixed text, not a placeholder.
Resolving the Error
HH2 Service URL, UserName, or Password Missing
- These are connector configuration settings. The fix happens in the Sage 300 CRE connector configuration in Arcoro, not in Sage 300 CRE itself and not in HH2.
- Enter or correct the named setting on the connector so it has a non blank value.
- Re-run the sync and confirm the message no longer appears, and the run completes instead of stopping.
Sage300HH2ApiKey or Sage300HH2ApiSecret Missing
- These are deployment-level settings and are not stored on the connector.
- Retry the sync once, since the message text itself instructs this.
- If the message returns, escalate to Arcoro support with the exact message text and the sync execution details.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The message names Sage300HH2ApiKey or Sage300HH2ApiSecret. These are deployment settings and the message text itself says to contact Arcoro support if a retry does not resolve it.
- The message names HH2 Service URL, UserName, or Password, a value was entered on the connector, and the sync still fails with the same message.
- The log text does not match any message in the table above, or it reports a different setting name than the three listed here.