Module Navigation

Troubleshooting CMiC Integration Error: Preload or Lookup Data Setup Failure

Before the CMiC connector reads or writes a single employee, it loads a set of reference lookup lists from CMiC, things like trade codes, unions, pay runs, and work locations, so it can translate values between CMiC and Arcoro. This is called preload. If preload finds a duplicate entry in one of these lookup lists, it cannot safely build that lookup, and the entire sync run is stopped immediately, before any employee data moves.

This can be referred to when you see that a sync ran, but nothing happened. It is not that individual employees failed. The sync never got far enough to look at employees at all.

Error Messages

Message textDirectionOccurs whenOutcomeFix
Failures on PreloadRead and writeOne or more of the lookup lists loaded during preload contained at least one duplicate entry. This message is raised once, after all lookup lists have finished loading, if any of them failed.The entire sync run stops. No employees, and no other entities in the same run, are processed.Do not act on this message alone. Find the duplicate detail messages logged just before it and fix the duplicate they describe in CMiC.
The CMiC Provider encountered a duplicate [lookup type] with key: '[key value]' in the Employee Read Service. Remove the duplicate and run the sync again.Read (CMiC into Arcoro)While loading a lookup list from CMiC for the employee read, the same key value appeared more than once in that list. Logged once per duplicate found.The duplicate row is skipped and that lookup list is marked as failed. Preload finishes loading the remaining lookup lists, then the whole sync run stops with the "Failures on Preload" message.In CMiC, find the record identified by the key value for the named lookup type and remove or correct the duplicate.
The CMiC Provider encountered a duplicate [lookup type] with key: '[key value]' in the Employee Write Service. Remove the duplicate and run the sync again.Write (Arcoro out to CMiC)While loading a lookup list from CMiC for the employee write, the same key value appeared more than once in that list. Logged once per duplicate found.The duplicate row is skipped and that lookup list is marked as failed. Preload finishes loading the remaining lookup lists, then the whole sync run stops with the "Failures on Preload" message.In CMiC, find the record identified by the key value for the named lookup type and remove or correct the duplicate.

Lookup Types That Can Appear in a Duplicate Message

Lookup type as it appears in the messageSideWhat the key in the message isWhere to fix it in CMiC
Trade CodeReadThe trade code by itself. Only checked when the Occupation scope is included in the sync.Not established from code. See Open questions.
SkillReadThe skill code by itself. Only checked when the Skill Level scope is included in the sync.Not established from code. See Open questions.
UnionReadThe union code by itself. Only national-level unions are checked for this list. Only checked when the Union scope is included in the sync.Not established from code. See Open questions.
Union LocalReadThe union code by itself. This is a separate list from national-level unions, so the same code appearing once in each list is not a duplicate. Only checked when the Union Local scope is included in the sync.Not established from code. See Open questions.
Pay RunReadThe pay run code by itself. Always checked, regardless of which scopes are included in the sync.Not established from code. See Open questions.
Work LocationWriteA combination of the work location name and the work location code, shown together as name and code. Always checked, regardless of which scopes are included in the sync.Not established from code. See Open questions.
Trade CodeWriteA combination of the trade code and the trade description, shown together as code and description. Always checked, regardless of which scopes are included in the sync. Unlike the read side, this list is loaded even when the Occupation scope is not included.Not established from code. See Open questions.
SkillWriteThe skill description, not the skill code. Only checked when the Skill Level scope is included in the sync.Not established from code. See Open questions.
UnionsWriteA combination of the union name and the union code, shown together as name and code. This list combines national and local unions together in a single check, unlike the read side. Checked when either the Union scope or the Union Local scope is included in the sync.Not established from code. See Open questions.
Pay RunWriteThe pay run description, not the pay run code. Always checked, regardless of which scopes are included in the sync.Not established from code. See Open questions.
BankWriteThe bank code by itself. Only checked when the Direct Deposits scope is included in the sync.Not established from code. See Open questions.

All of these comparisons are case sensitive. A code or description that differs only in upper or lower case, for example, a trade code entered as both "abc" and "ABC", is treated as two different values and will not trigger a duplicate message.

Confirming the Error

  1. Open the sync run in Sync History.
  2. Check the step-level Failures tab, not the entity row. The entity row for Employees shows Total, Added, Updated, Unchanged, Information, Warnings, and Errors, but it has no Failures column. The "Failures on Preload" message is a step-level failure, so it will not appear on the Employees entity row.
  3. In the same run, look at the log entries recorded as errors around the same time as the failure. These are the duplicate detail messages. Match on the fixed part of the sentence, "encountered a duplicate", "in the Employee Read Service", or "in the Employee Write Service", rather than on the lookup type or key value in quotes, since those change per user.
  4. If you see "Failures on Preload" but no duplicate detail messages nearby, you are likely looking in the wrong place in the log. The duplicate messages are logged as errors before the failure is raised; confirm you are viewing the full log for that run, not a filtered view.
  5. Each duplicate message names a lookup type and a key value. Use the lookup type table above to identify which side (read or write) the message came from and what the key value represents.

Resolving the Error

  1. From the duplicate message, identify the lookup type (for example, Trade Code, Skill, Union, Pay Run, Work Location, Unions, or Bank) and the key value shown in quotes.
  2. In CMiC, locate the record for that lookup type that matches the key value. Where the key is a combination of two fields, such as a name and a code, both fields must match.
  3. Remove or correct the duplicate record in CMiC so that only one active record exists with that key value.
  4. If more than one duplicate message appears in the log, repeat for each one. Preload logs one message per duplicate found, and all of them must be resolved before the sync will get past preload.
  5. Run the sync again.
  6. Confirm the fix worked by checking that the run no longer shows "Failures on Preload" at the step level, and that the Employees entity row now shows activity in Total, Added, or Updated instead of stopping at the start.

When to Escalate

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

  • You cannot find a duplicate record in CMiC matching the key value shown in the message.
  • You removed the duplicate in CMiC, but the same "Failures on Preload" failure recurs on the next run.
  • "Failures on Preload" appears in the log but no duplicate detail messages can be found anywhere in that run's log.
  • The duplicate is in a lookup type where tier 1 cannot determine where in CMiC the record is maintained.
Was this article helpful?
0 out of 0 found this helpful