Troubleshooting Guide for Reltio Enrichment with D&B
Learn about some Reltio Enrichment with D&B error scenarios and how to resolve them.
This topic provides troubleshooting information about Reltio Enrichment with D&B.
Error: Tenant is not registered tenant
Resolution:
Use the Status endpoint to ensure your tenant is registered in the Reltio Enrichment with D&B.
This error explains the number of values with different crosswalks. The modification of a survivorship strategy impacts the multiple values with different crosswalks.
Error: 3 Matches Found
Resolution
In the Potential Match screen, no potential match is displayed. Also, the number of matches can be arbitrary.
- Make sure whether the DTSS subscription exists.
- In the Data Tenant (DT), make sure that the streaming is enabled. Enable the streaming if it is not enabled already.
streamingEnabled: true
streamingAPIEnabled: true
- In the DTSS subscription, make sure whether the parameter
hiddenDt
is not set to true. WhenhiddenDT
is set to true, it hides DT from the UI and disables sending match requests to DTSS from the user interface.
Error: REL0001: Reltio API error: 403, Access is denied
The Reltio Enrichment with D&B processes requests in Reltio with a service user account. When you encounter this error, it means that the service user account provisioned for your Reltio Enrichment with D&B doesn't have the correct roles and access. This error indicates that the service user account has no access to the Data Tenant.
Resolution:
To resolve this error, Contact a supportive person.
Error: 1 Match Found
Ensure whether the match has confidence code
(CC
) as 9 or 10. Also, ensure if it is not automatically merged to the Customer Tenant (CT) and is still in the Potential Matches view.
Resolution:
- Make sure whether the DTSS subscription exists.
- In the DT, make sure whether streaming is enabled . If not, enable streaming.
streamingEnabled: true
streamingAPIEnabled: true
- By default, the connector sets the
auto-merge
flag, only if the single entity in the response has CC 9 or CC 10. - The Connector sets the
auto-merge
flag, only for the entities that are displayed with the status asActive
.
Buttons do not work and there is an unknown failure or you do not have permissions
Resolution:
- Logging details in
LogDNA
will be available in thednb-connector-prod
project. There is a separate stackdriver for HIPAA . - Ensure that the user has a
ROLE_DNB_CONNECTOR
role.
Error: Address not found or Address is incomplete
Click Get match. The error message is displayed.
Ensure if the Address Type
and primary flags are set or they have no ISO3166-2. Also, ensure if the Reltio entity does not include the appropriate address.
Resolution:
- Ensure that an address exists for the record which you are trying to enrich.
- Make sure whether your L3 configuration and mappings are compatible. L3 describes the address as a reference. The mappings in the Reltio Enrichment with D&B also expect addresses as reference. Also, the Reltio Enrichment with D&B expect addresses as a nested attribute.
Error: DnB API (Invalid Territory provided in the request)
On DnB Direct+ API, click Get Match.
Example: Reltio source attribute staff:
Resolution:
- The
StateProvince
attribute value must be of two characters for US/CA in your L3 configuration. - Update the mapping to use
lookupCode
instead of the value.
Error: Family tree size is too long, please contact the engineering team
The get family tree on Direct 2.0 displays this error.
Resolution:
To know more information, Contact a supportive person.
In Direct 2.0
mapping the nested level is limited and this error indicates the hierarchy of entities is too deep. You can try this request once again after you get a solution.
When you do not have auto-merge even for potential matches with confidence code (CC) as 9 or 10
Resolution:
Ensure whether your auto-merge conditions are met. Check the following conditions:
- The potential match entity status is Active.
- The potential match entity with confidence codes 9 and 10 is single.
DTSS service provides the Auto-merge and potential matches feature. Ensure you have correctly configured DTSS service and correct subscription (For example in app-account360
repository):
- Streaming enabled in the physical config for DT and for CT.
"streamingConfig": { "streamingEnabled": true, "streamingAPIEnabled": true - REALTIME subscription for DT and for CT.
"dtSyncType": "REALTIME", "ctSyncType": "REALTIME", - The DTSS adds a non-empty messaging destination for DT and CT, if the two previous conditions are satisfied.Note: You cannot add the non-empty messaging destination for DT and CT manually.
Error: Not a Match button is not working for DT potential matches
Resolution:
READ
and UPDATE
permissions as shown as below: Error: No match found for input criteria
TheDirect+
batch returns this error even when the on-demand works for you. It updates the entity with a new DUNS number when your current DUNS is obsolete. Resolution:
There is a separate match or enrichment request. There are different APIs. The second batch in D&B Direct+ API is part of the Identify API which indicates that the DnB will start matching and extracting the details when it is able to find the best candidate.
The D&B specific is matched by obsolete DUNS and is not able to find any candidates. The enrichment will return the new DUNS number with details. This is confusing when you work in (on-demand) enrichment. Also, the batch returns Nothing found error.
For example, DUNS number is 001905269
:
The D&B Direct+ match creates the request without a DUNS number.
Result
The result displays nothing found
error. See the match data criteria as follows:
Result (with the new DUNS)
Error: Batch or Batch+: MAP0012: first tag must be start array
This error indicates that the connector is unable to parse the export file. Export file must be in JSON format and the first tag must be an open array tag. The reason for such an issue is unsupported by the connector compression. In the export status, check for attribute file compression. The connector process exports files with the ZIP extension; files with GZIP can not be processed.
Resolution:
Set the default compression algorithm in the tenant physical configuration to ZIP
, Contact a supportive person.
Error: Many errors in "log: 4, Too many simultaneous connections (max=5)"
This error is related to a tenant’s physical configuration. The connector uses a lot of connections requests in parallel because of no batch request for Reltio API call connections. These requests may reach a tenant’s limit.Resolution:
Update a tenant’s physical configuration to allow for additional simultaneous connections, Contact a supportive person.
Match quality attributes missing on some entities
This error indicates that some data has changed on an entity. A few other consequences can happen when the connector updates the entities in Reltio. The connector's operations related to match quality attributes are described as follows:- Get match (on demand): The connector posts entities to DT with a crosswalk based on entity
uri: DUNSNumber+entityUri(goldenId)
.After merging in CT, the entities have the DT crosswalk and values from matching responses.
- Batch+: The connector directly updates an entity in CT with match quality attributes when an entity does not have a DUNS number. Crosswalk values are DUNS Number.Note: When the entity already has the DUNS number, D&B does not provide match quality attributes.
- On-demand enrichment: The connector updates entity on CT directly without match quality attributes in the D&B response. Crosswalk values are DUNS numbers.
Conclusions:
- The Get Match (on demand) and
Batch+
enrichment for entities without DUNS will provide match quality attributes match that are involved in the operations. You must have an active mapping with match quality attributes included. The corresponding mappings were introduced in2020.02.Batch+
on entities with DUNS number would not provide match quality attributes due to lack of information in sources. - Enrichment (on demand) does not provide match quality. Moreover it erases match quality attributes and the data provided from the crosswalk value =
DUNSNumber
) assigned byBatch+
. This is caused because of the entity updates from the same crosswalks. - Presence of the Match quality attributes and irrelevant CC values.
Profiles with different DUNS and same crosswalk merged
When two profiles share the same crosswalk even if the DUNS numbers are different, the D&B connector merges the profiles. The D&B code is 40003: DUNS Number has been transferred
.
Conclusions:
By design, the connector merges the profiles by crosswalks. After the transfer, the entity has 2 DUNS numbers.
When you know the customer tenant and want to find the respective data tenant
Use get profile by a tenant name endpoint. It will return the customer tenant, profile name, and the data tenant (if the data tenant exists).
Background jobs (monitoring, batch) do not work
- Find the Job ID. For more information, see Get Jobs List.
- Work with batch, scheduled, and monitoring background job types.
- See the Status field in response to find the status or the reason of the error.
Scheduled jobs will produce more jobs to execute the required operations. After you have the list, you can get the job status. For more information, see Get Job Status.
. - You can work with all types of jobs. The job status contains the problem description.
Error 800 for Type XXX is forbidden
- REL0001: Reltio API error: 800,Type configuration/entityTypes/Organization is forbidden. Required privileges: READ,Security error.
- Required privileges: READ,Security error. Type configuration/entityTypes/Organization is forbidden. Required privileges: READ.
The errors mentioned above indicate that service user dnb.connector or dnb.connector.hipaa does not have the required privileges. Mostly, the metadata security is activated on your tenant.
You can find the details in LogDNA:
When there is a URI mismatch
Before updating the target entity with D&B attributes and DUNS number, the connector verifies that the incoming DUNS does not exist in the tenant and is not assigned to another record with a different URI. The URI mismatch error protects against unauthorized entity matches. Do the following to solve this error:
- mergeOrgsWithSameDUNS - enable this parameter to skip the URI mismatch and the entities with the same DUNS number in the crosswalk will be merged automatically.
- mergeOrgsWithSameDUNSByPotentialMatches - enable this parameter to mark the operation as successful, and view the potential matches of entities.
To activate the mergeOrgsWithSameDUNSByPotentialMatches parameter:
-
Check if you have an automatic match rule by the DUNS number in the entity on your Tenant.
-
Set the mergeOrgsWithSameDUNS parameter
=false
to ensure the URI mismatch check is active. -
Set the mergeOrgsWithSameDUNSByPotentialMatches parameter
=true
to enable this parameter.
Scenarios | Parameter | Description | Sample responses |
---|---|---|---|
Scenario 1 |
mergeOrgsWithSameDUNS=false mergeOrgsWithSameDUNSByPotentialMatches=false |
|
|
Scenario 2 |
mergeOrgsWithSameDUNS=true mergeOrgsWithSameDUNSByPotentialMatches=false |
|
|
Scenario 3 |
mergeOrgsWithSameDUNS=true mergeOrgsWithSameDUNSByPotentialMatches=true |
|
|
Scenario 4 |
mergeOrgsWithSameDUNS=false mergeOrgsWithSameDUNSByPotentialMatches=true |
|
|
Errors: D&B STP
Here's a list of STP errors and how to troubleshoot them:
Error Code | Cause | Steps to Troubleshoot |
---|---|---|
DNB0001 | Incompatible data type or unacceptable data type sent in the request. |
|
DNB0004 | The STP service is unavailable or not reachable. |
|
DNB0005 | Cannot read the directory contents on the STP server. |
|
DNB0006 | Failure during the initialization of the SFTP client. |
|
DNB0007 | Failed to connect during the first step of the SSH connection (username, host, and port). |
|
DNB0008 | Authentication failed during the second step of the SSH connection (password verification). |
|
DNB0009 | Error during the process of reading a file from the STP server due to network issues, file corruption, or insufficient permissions. |
|
DNB0010 | Error when attempting to open a file on the STP server. Possible causes include incorrect paths or permission issues. |
|
DNB0011 | Failure during the initialization of the SFTP session due to invalid server details, SSH key issues, or network problems. |
|
REQ0021 | The background monitoring job is started without providing S3 or STP parameters. |
|
BCH0039 | Monitoring registration details are empty or null due to an internal D&B error. |
|