D&B Connector API Error Codes

Different types of API errors such as request errors, mapping errors, configuration errors, and so on occur at different stages of functioning of the D&B connector.

Reltio Errors

The following errors may occur when the connector works with Reltio API.


Error Code	Message	Occurs When	Response
REL0001	Reltio API error ({0})	The connector fails to invoke the Reltio API. {0} is the Reltio error message.	Depends on Reltio API error.
REL0003	Reltio authorization error	Expired or invalid token.	Obtain the correct token and re-invoke the call.
REL0004	Reltio permission error. User has missing role(s) {0}	A User does not have appropriate Reltio roles to use the connector. {0} is required roles separated by comma. Currently only the `ROLE_DNB_CONNECTOR` role is required.	Obtain the correct roles and re-invoke the call.
REL0005	Cannot handle error response from Reltio API request	Connector invokes Reltio API, but receives a response as non-json string.	Contact Reltio Support.
REL0006	Cannot handle error response from Reltio Authentication API request	Connector invokes Reltio Authentication API, but receives a response as non-json string.	Contact Reltio Support.
REL0007	Cannot write entity to Data Tenant {0}	Connector invokes Reltio API, but the user account has no permissions or has temporary problems.	Obtain the required role and re-invoke the call.

D&B Errors

The following errors may occur when the connector works with D&B API.


Error Code	Message	Occurs When	Response
DNB0001	DnB API error ({0})	The connector fails to invoke the D&B API. {0} is the D&B error message	Depends on D&B API error.
DNB0002	DnB API authorization error	A user specifies invalid D&B credentials or expired/invalid token.	Obtain the correct token and re-invoke the call.
DNB0003	Cannot handle error response from DnB API request	Connector invokes D&B API, but receives a response as non-json string.	Contact Reltio Support.
DNB0004	DNB STP service is not available in this request	STP service is currently unavailable or not reachable.	Check Network Connectivity: Ensure that your network connection is stable and that you can reach the STP server. Verify Server Status: Check if the STP server is up and running. There might be scheduled maintenance or unexpected downtime. Review Logs: Look for any related error messages or logs that might provide more context about the failure. Retry the Request: Sometimes the issue might be transient, and retrying the request might resolve it.
DNB0005	Failed to read STP directory	Unable to read the directory contents on the STP server	Verify Directory Path: Ensure that the directory path in STP server is "/gets" and accessible. Check Permissions: Verify that the user has the necessary permissions to read the directory on the STP server. Review Logs: Examine logs for any additional details that might indicate the cause of the failure.
DNB0006	Failed to initialize SFTP client	This error indicates a failure during the initialization of the SFTP client.	Review Initialization Code: Check the code responsible for initializing the SFTP client for any issues or misconfigurations. Check Library Dependencies: Ensure that all required libraries and dependencies for the SFTP client are correctly installed and up-to-date. Inspect Logs: Look at the logs for any error messages that provide more context about the initialization failure.
DNB0007	Failed to connect using provided server details	This error occurs during the first step of the SSH connection, which involves creating a connection using the username, host, and port.	Verify Server Details: Ensure that the username, host, and port are correct. Check Network Access: Make sure that your network allows outbound connections to the specified host and port. Test Connectivity: Use a tool like telnet or nc to test connectivity to the STP server on the specified port.
DNB0008	Authentication failed using provided credentials	This error occurs during the second step of the SSH connection, which involves verifying the password.	Verify Credentials: Double-check the username and password for correctness. Update Credentials: If there has been a recent password change, ensure that the updated credentials are being used. Direct Link Check: Manually verify the credentials by attempting to log in to the STP server using an SSH client.

Request Errors

The following errors may occur when a user specifies incorrect data in the request.


Error Code	Message	Occurs When	Response
REQ0001	{0}	User does not specify the required headers or query parameters. {0} is error message.	Fix request parameters depending on the error and re-invoke the call.
REQ0002	DUNS number is absent	User calls the connector for enrichment, but the organization has a missed DUNS Number attribute which is required for the D&B call.	Invoke the get match operation or merge the best suited potential matched organization if it was already invoked, for the DUNS Number to appear. After merging, re-invoke the call for enrichment.
REQ0003	Attribute `Address.ISO3166-2` is absent	User invokes the `get match` call but the `filter.json` mapping result does not have the `CountryISOAlpha2Code` field. It means that Address does not have the attribute `ISO3166-2`.	Specify the correct `ISO3166-2` value or perform cleansing of address, and the `ISO3166-2` value gets automatically updated. Re-invoke the call after updating the value.
REQ0004	Organization mapping from Get D&B Match response failed	User invokes the `get match` call but the mapping `match.json` is incorrect.	Check if the `match.json` file is correct or contact support for help.
REQ0005	Reltio organization has no crosswalks section	User invokes an `enrichment` call but the organization does not have the `crosswalk` field. This is a rare scenario.	Check if the organization has the `crosswalks` field.
REQ0006	The `entityUri` parameter should be in `entities/<entityId>` format	User invokes the `get match` or `enrichment` call but the request parameter `entityUri` has incorrect format.	Specify the correct `entityUri`and re-invoke the call.
REQ0007	Input parameters validation error: {0}	User specified incorrect request parameters. {0} is error message.	Fix request parameters depending on the error and re-invoke the call. The current D&B connector endpoints do not use Hibernate validations to validate the request headers. This error is for future use.
REQ0008	Entity has no name	User invokes the get match call but the `filter.json` mapping result does not have the `SubjectName` field. It means that Address does not have the attribute name.	Specify the organization name and re-invoke the call.
REQ0009	Reltio entity doesn't contain appropriate address	User invokes the `get match` call but the `filter.json` mapping result does not have the `StreetAddressLine-1` field. It means that Organization does not have an appropriate Address. By default, this address should have the type `Shipping` or `Billing` and `Primary` flag set to `true`. It can be customized in mapping for each customer.	Ensure that all the conditions are valid for a given organization address (depending on mapping) and re-invoke the call, or you may check if the connector is using the correct address model.
REQ0021	Background monitoring job must have S3 or STP credentials	This error occurs when the background monitoring job is started without providing S3 or STP parameters.	Provide Credentials: Depending on the registration destination type, supply the necessary S3 or STP credentials. Check Job Configuration: Ensure that the background monitoring job is correctly configured with the required credentials for accessing D&B Seed and Notification files.

Configuration Errors

The following errors may occur when the connector works with the configuration files.


Error Code	Message	Occurs When	Response
CFG0001	Tenant is not registered	Specified tenant is not presented in any configuration profile.	Use the Connector Configuration Service to register tenant and then re-invoke the call.
CFG0002	Profile has missed files	Specified tenant is registered in configuration profile which has missed the required files for correct connector to work. For example, one of the mapping files.	Use Connector Configuration Service to check the state of all required connector files and then re-invoke the call.

Mapping Errors

The following errors may occur when the connector performs mapping from one structure to another one.


Error Code	Message	Occurs When	Response
MAP0001	Internal mapping error	User invokes the `get match` call.	Contact Reltio Support.
MAP0002	Internal mapping error	User invokes the `get match` call.	Contact Reltio Support.
MAP0003	Internal mapping error	User invokes the `get match` call.	Contact Reltio Support.
MAP0004	Internal mapping error	User invokes the `enrichment` call.	Contact Reltio Support.
MAP0005	Internal mapping error	User invokes the `enrichment` call.	Contact Reltio Support.
MAP0006	Internal mapping error	User invokes the `get match` call.	Contact Reltio Support.
MAP0007	Internal mapping error	User invokes the `get match` call. Mapping `filter.json` is incorrect.	Review `filter.json` mapping
MAP0008	Internal mapping error	User invokes the `get match` call. Mapping `match.json` is incorrect.	Review `match.json` mapping
MAP0009	Internal mapping error	User invokes the `enrichment` call. Mapping `enrichment.json` is incorrect.	Review `enrichment.json` mapping
MAP0010	Internal mapping error	User invokes the `linkage` call. Mapping `batch.json` is incorrect.	Review `batch.json` mapping
MAP0011	Internal mapping error	User invokes the `enrichment` call. Mapping `update_status.json` is incorrect.	Review `update_status.json` mapping

Accelerate the Value of Data