Module Navigation

Troubleshooting Sage 100 Integration Error: Connector Configuration Missing or Invalid

The Sage 100 connector needs three basic settings before it can talk to your HH2 service at all: the service address, the HH2 user name, and the HH2 password. These live on the Sage 100 connector configuration in Arcoro, not inside Sage 100 itself. The connector reads these values the moment a sync step starts, before it tries to log in and before it reads or writes a single employee record. If any one of them is blank, the connector cannot proceed, so the whole step stops immediately.

Error Messages

Message textDirectionOccurs whenOutcomeFix
Sage 100 Construction Provider could not read the configuration setting 'HH2 Service URL'.Read or writeThe Sage 100 connector is set up at the start of the sync step, before login and before any record is read or written.Sync stoppedEnter a value in the connector's HH2 Service URL field.
Sage 100 Construction Provider could not read the configuration setting 'UserName'.Read or writeImmediately after setup, when the connector logs in to the HH2 service.Sync stoppedEnter a value in the connector's UserName field.
Sage 100 Construction Provider could not read the configuration setting 'Password'.Read or writeImmediately after setup, when the connector logs in to the HH2 service (same login step as UserName).Sync stoppedEnter a value in the connector's Password field.

A setting that is present but only spaces is treated the same as a blank setting and produces the same message.

Confirming the Error

  1. Open the sync execution in Sync History for the connector in question.
  2. Find the step for the Sage 100 connector. This message can appear on a read step or a write step, so check whichever step says failed.
  3. Look at the Failures column for that step, not Errors or Warnings. This family of messages always reports as a Failure.
  4. A non-zero Failures count where every entity in that step shows 0 for Added, Updated, and Unchanged means the connector never connected to HH2. That combination is the defining signal for this article.
  5. Open the failure detail and read the setting name inside the single quotes. Match it against the Message text column above.

Resolving the Error

All three settings are edited in the same place: the Sage 100 connector's configuration in Arcoro.

HH2 Service URL Missing

  1. Get the correct HH2 service address for your Sage system.
  2. Open the Sage 100 connector configuration and enter that address in the HH2 Service URL field.
  3. Save the connector.
  4. Run the sync again and confirm the step now shows 0 in the Failures column.

UserName Missing

  1. Get the correct HH2 username for your Sage system.
  2. Open the Sage 100 connector configuration and enter that value in the UserName field.
  3. Save the connector.
  4. Run the sync again and confirm the step now shows 0 in the Failures column.

Password Missing

  1. Get the correct HH2 password for your Sage system.
  2. Open the Sage 100 connector configuration and enter that value in the Password field. This field is masked once saved.
  3. Save the connector.
  4. Run the sync again and confirm the step now shows 0 in the Failures column.

The HH2 API key and API secret are separate settings with your own error messages and own resolution path. If the failure message names one of those instead of HH2 Service URL, UserName, or Password, use this resource instead of this article.

When to Escalate

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

  • It does not have the correct HH2 Service URL, HH2 username, or HH2 password, and you are unsure of them.
  • The value is already filled in on the connector and saved, but the same message keeps appearing on the next sync. Escalate to implementation or engineering to check why the saved value is not being read.
  • The Failures count is non-zero, but the message text does not name HH2 Service URL, UserName, or Password. That is a different failure and outside this article.
Was this article helpful?
0 out of 0 found this helpful