Fujitsu Data e-TRUST message collection
Preface
Purpose of This Manual
This document describes the messages and workaround for the most common errors that occur with Fujitsu Data e-TRUST.
If you encounter an error not described in this manual, contact your system administrator.
Readers of This Manual
This document is written for those who plan or develop applications and services using Fujitsu Data e-TRUST. The following knowledge is required to read this document:
- Basic knowledge of the Internet
- Basic knowledge of the Web API
- Basic knowledge of the database (DB)
Organization of Manuals
Please read the following manuals according to your purpose and purpose.
| manual name | Purpose and purpose |
|---|---|
| Function Manual (this document) | This document provides an overview of the Service, main functions, and information you need to understand to use the Service. |
| API Reference Manual | Provides a detailed reference for using the Web API. It is written in HTML format. |
| API Reference Manual: separate volumes | Supplements the API Reference Manual. Please check it with the API reference. |
| Message Collection | This document describes the message contents and the action to be taken when using the Web API. |
| Notes and Limitations | This document describes precautions and restrictions for using Fujitsu Data e-TRUST. |
| Release Information | Provides release information for Fujitsu Data e-TRUST. |
| Licensing Information | This document describes the license of the software used in this service. |
Organization of This Document
This manual is organized as follows.
| Chapter/Appendix | Contents |
|---|---|
| Chapter I Common Error Messages and Workarounds for Distributed Data Linkage, Consent Management, and Service Management Functions | This section describes the common error messages that are generated by the functions in Chapters 2, 3, and 6, and how to resolve them. |
| Chapter II Error Messages for the Distributed Data Linkage Function | This subsection describes the error messages that occur in the distributed data linkage function and the corrective actions to take. |
| Chapter III Error Messages for the Consent Management Function | This subsection describes the error messages that occur in the consent management function and the corrective actions to take. |
| Chapter IV Error Messages for the Trail and Audit Function | This subsection describes the error messages that occur in the trail and audit function and how to handle them. |
| Chapter V Error Messages for the Trust Seal Function | This section describes the error messages that are generated by the trust seal function and the corrective actions to take. |
| Chapter VI Error Messages for the Service Management Function | This subsection describes the error messages that occur in the management function and the corrective actions to take. |
Conventions Used in This Manual
Error messages generated by Fujitsu Data e-TRUST may have "Failed to XXX:" in the front, but this manual only describes the following error messages. We appreciate your understanding in advance.
Export Control Regulation
If this document is to be exported or provided to a third party, please review the regulations of your country of residence and the U.S. export control laws and regulations before proceeding.
Change History
| Edition Count | Date | Changes |
|---|---|---|
| v1.1 | 2024/3/22 | + Revise the technology name from “Data e-TRUST” to “Fujitsu Data e-TRUST”. |
| second edition (v 1.0) | 2023/7/10 | + Add the following new error to Section 2.3 - Error Detail Code: 40006100 + Add the following new error to Section 4.1 - Status Code: 408 |
| First edition | 2023/3/24 | New |
copyright
Copyright 2023 FUJITSU LIMITED
Chapter I: Common Error Messages and Workarounds for Distributed Data Linkage, Consent Management, and Service Management Functions
This chapter describes the error messages that are common to the functions in Chapters 2, 3, and 6, and how to handle them.
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 400 | 40001100 | Invalid Parameter. (Error: XXX). | The specified parameter is invalid. | Check the XXX in the error message and specify the correct value based on the API reference manual. |
| 2 | 403 | 40301100 | Bad Access Rights. (XXX) | Insufficient access privileges. | Check XXX in the error message and check the API reference manual to see if the role is appropriate. |
| 3 | 408 | 40801100 | Request Timeout. | A timeout error has occurred. | If the system is under load due to execution of another request, try re-execution at a time when the load is low. If this error occurs frequently, contact your system administrator. |
| 4 | 500 | 50000100 | XXX | An unexpected error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 5 | 500 | 50001100 | Internal Server Error. (XXX) | (same as above) | (same as above) |
| 6 | 500 | 50002100 | Internal SQL Error. | A SQL request error has occurred. | (same as above) |
| 7 | 500 | 50003100 | Internal Exclusive Lock Timeout Error. | An error occurred due to exclusive lock timeout. | Processing on the same table may be concentrated. Wait a while, and then retry the operation. If this error occurs frequently, contact your system administrator. |
| 8 | 500 | 50004100 | Internal DB Error. | An error occurred during DB connection processing. | Contact your system administrator. In that case, please contact us with an error message. |
| 9 | 500 | 50005100 | Internal Server Error (internal error). | An internal error has ccurred. | Contact your system administrator. In that case, please contact us with an error message. |
Chapter II: Chapter II Error Messages for the Distributed Data Linkage Function
This chapter describes the error messages that occur in the distributed data linkage function and the corrective actions to take.
II.1 Error Messages and Workarounds for Manage Table Definition API
This subsection describes the error messages and corrective actions to be taken for the table definition.
Manage table definition (create)
The main error messages that occur with Manage table definition (create) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 400 | 40003021 | Already Exist. ("XXX" is already exist.) " | Identical table name already exists. | Check the XXX in the error message and specify the correct value based on the API reference manual. |
| 2 | 400 | 40003022 | Already Exist. (XXX is already defined by others, and composition of columns are different from your request.) " | A table with the same table name but with a different column structure already exists. | Check the XXX in the error message and specify the correct value based on the API reference manual. |
Manage table definition (update)
The main error messages that occur with Manage table definition (update) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 409 | 40901100 | Cannot process due to existence of synchronizing records. | Data is in the process of being synchronized. | The target data is in the process of being synchronized. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 3 | 409 | 40901100 | Cannot process due to existence of synchronizing records. | Data is in the process of being synchronized. | The target data is in the process of being synchronized. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 4 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
II.2 Error Messages and Workarounds for Get Table Definition API
There is no main error message that occurs only with Get table definition. Refer to Chapter 1 for the contents of common error messages and actions to take.
II.3 Error Messages and Workarounds for Register Data (Single Record) API
The main error messages that occur with Register data (single record) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 400 | 40002100 | Failed to register data — Table Record Limit Exceeded. (Registered record number per table must not exceed XXX. agent _ id: XXX, table _ name: XXX | You have exceeded the maximum number of registered records per table. | Check the XXX in the error message and specify the correct value based on the API reference manual. |
| 2 | 400 | 40004100 | Already Exist. (data is already exist.) | A record with the same primary or unique key already exists. | Check the input data and API Reference Manual to ensure that the primary key or unique keyed column has an appropriate value that does not duplicate any other record. |
| 3 | 400 | 40006100 | Failed to register data: Dataowner Record Limit Exceeded. (Registered record number for one data owner per table must not exceed XXX. agent _ id: XXX, table _ name: XXX, data owner: [agent _ id: XXX, user _ id: XXX]) | You have exceeded the maximum number of registered records per data owner for a record with a data owner. | Check the XXX in the error message and specify the correct value based on the API reference manual. |
| 4 | 409 | 40901100 | Cannot process due to existence of synchronizing records. | Data is in the process of being synchronized. | The target data is in the process of being synchronized. |
| 5 | 500 | 50006100 | Exist Synchronizing Data Error. (XXX) | Data is in the process of being synchronized. | The target data is in the process of being synchronized. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 6 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
II.4 Error Messages and Workarounds for Upload Data (Multiple Records) API
The main error messages that occur with Upload data (multiple records) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 400 | 40004100 | Already Exist. (data is already exist.) | A record with the same primary or unique key already exists. | Check the input data and API Reference Manual to ensure that the primary key or unique keyed column has an appropriate value that does not duplicate any other record. |
| 2 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
II.5 Error Messages and Workarounds for Delete Data API
The main error messages that occur with Delete data and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 409 | 40901100 | Cannot process due to existence of synchronizing records. | Data is in the process of being synchronized. | The target data is in the process of being synchronized. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50006100 | Exist Synchronizing Data Error. (XXX) | (same as above) | (same as above) |
| 3 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
II.6 Error Messages and Workarounds for Get Data API
There is no main error message that occurs only with Get data. Refer to Chapter 1 for the contents of common error messages and actions to take.
II.7 Error Messages and Workarounds for Send Data API
The main error messages that occur with Send data and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 409 | 40901100 | Failed to send all records. | All data transmission failed. | Check whether the data to be sent exists, whether the sent record is not specified, whether the data conforms to the conditions of the target table definition, and then re-execute the command with the specified parameters changed. There may also be data in the synchronization process, so try again later. |
| 2 | 409 | 40901100 | Cannot process due to existence of synchronizing records. | Data is in the process of being synchronized. | The target data is in the process of being synchronized. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 3 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
II.8 Error Messages and Workarounds for Cancel Data Transmission API
The main error messages that occur with Cancel data transmission and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 409 | 40901100 | Failed to stop all records. | All data transmission cancellations could not be performed. | Check whether the data to be canceled exists, whether the data has already been sent to the specified record, whether the data conforms to the conditions of the target table definition, and then re-execute the command with the specified parameters changed. Also, there may be data in the synchronization process, so please try again after a while. |
| 2 | 409 | 40901100 | Cannot process due to existence of synchronizing records. | Data is in the process of being synchronized. | The target data is in the process of being synchronized. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 3 | 500 | 50006100 | Exist Synchronizing Data Error. (XXX) | Data is in the process of being synchronized. | The target data is in the process of being synchronized. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 4 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
II.9 Error Messages and Workarounds for Request Data Transmission API
The main error messages that occur with Request data transmission and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
II.10 Error Messages and Workarounds for Respond to Data Transmission Request API
The main error messages that occur with Respond to data transmission request and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
Chapter III Error Messages for the Consent Management Function
This chapter describes the error messages that are generated by the consent management function and the actions to be taken.
III.1 Error Messages and Workarounds for Respond to Consent Request API
The main error messages that occur with Respond to consent request and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 409 | 40901100 | Cannot process due to existence of synchronizing records. | Data is in the process of being synchronized. | The target data is in the process of being synchronized. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
| 2 | 409 | 40901100 | all agreement answers are invalid. | All specified consent responses are invalid. | You have already responded to the subject consent request with the specified information. Please review the data you need to answer. |
| 3 | 500 | 50009100 | Too Many Asynchronous Request Error. | There is a large amount of data being processed asynchronously. | The processing of data is concentrated. Please try again later. If this error occurs frequently, contact your system administrator. In that case, please contact us with an error message. |
III.2 Error Messages and Workarounds for Get Consent Data API
There is no main error message that occurs only with Get consent data. Refer to Chapter 1 for the contents of common error messages and actions to take.
Chapter IV Error Messages for the Trail and Audit Function
This chapter describes the error messages that are generated by the trail and audit function and the corrective actions to take.
IV.1 Common Error Messages and Workarounds for the Trail and Audit Function
This section describes the error messages that are common to the functions described in Chapter 4 and the corrective actions to take.
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 400 | 40021100 | Invalid Parameter. (XXX.) | The specified parameter is invalid. | Check the XXX in the error message and specify the correct value based on the API reference manual. |
| 2 | 401 | 40121100 | Unauthorized. (XXX.) | Not authenticated. or credentials have expired. | Check XXX in the error message, check the API reference manual to see if the user information is correct, and then re-access. |
| 3 | 403 | 40321100 | Bad Access Rights. (XXX.) | Insufficient access privileges. | Check XXX in the error message and check the API reference manual to see if the role is appropriate. |
| 4 | 408 | ‐ | ‐ | A timeout error has occurred. | If the system is under load due to execution of another request, try re-execution at a time when the load is low. If this error occurs frequently, contact your system administrator. |
| 5 | 500 | 50020100 | (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
| 6 | 500 | 50021100 | Internal Server Error. | An unexpected error has occurred. | Contact your system administrator. |
| 7 | 500 | 50022100 | Internal SQL Error. (XXX.) | A SQL request error has occurred. | Contact your system administrator. |
| 8 | 500 | 50024100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
| 9 | 500 | 50025100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
| 10 | 500 | 50025110 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
| 11 | 500 | 50025120 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
| 12 | 500 | 50025140 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
| 13 | 500 | 50025150 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
| 14 | 500 | 50025160 | Internal Server Error. (XXX.) | An unexpected error has occurred. | An unexpected error has occurred. |
| 15 | 500 | 50025170 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
IV.2 Error Messages and Workarounds for Register Trail API
The main error messages that occur with Register trail and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
IV.3 Error Messages and Workarounds for Get Lineage API
The main error messages that occur with Get lineage and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40421100 | Not exist. (XXX.) | The Lineage to which the specified History ID belongs cannot be found. | Check XXX in the error message and make sure there are no typographical errors. |
| 2 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
IV.4 Error Messages and Workarounds for Search Trail API
This subsection describes error messages and corrective actions to be taken for trail search.
Search trail (by header)
The main error messages that occur with Search trail (by header) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40421100 | Not exist. (XXX.) | No history matching the search criteria was found. | Check XXX in the error message and make sure there are no typographical errors. |
| 2 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
Search trail (by global data)
The main error messages that occur with Search trail (by global data) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40421100 | Not exist. (XXX.) | No history matching the search criteria was found. Check XXX in the error message and make sure there are no typographical errors. | |
| 2 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
Search trail (by local data across organizations)
The main error messages that occur with Search trail (by local data across organizations) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40422100 | cdl: EventId not exist. (XXX.) | No history with requested eventId registered. | Check that there are no errors in the input. |
| 2 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. Contact your system administrator. |
Search trail (by verification)
The main error messages that occur with Search trail (by verification) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40421100 | Not exist. (XXX.) | No history matching the search criteria was found. | Check XXX in the error message and make sure there are no typographical errors. |
| 2 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
IV.5 Error Messages and Workarounds for Delete Local Data API
The main error messages that occur with Delete local data and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40421100 | Not exist. (XXX.) | Cannot find local data to delete. | Check XXX in the error message and make sure there are no typographical errors. |
| 2 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
IV.6 Error Messages and Workarounds for Manage reference policy API
Describes reference policy management error messages and workarounds.
Manage reference policy (create)
The main error messages that occur with Manage reference policy (create) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40422100 | cdl: EventId not exist. (XXX.) | No history with requested eventId registered. | Check that there are no errors in the input. |
| 2 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
Manage reference policy (delete)
The main error messages that occur with Manage reference policy (delete) and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40421100 | Not exist. (XXX.) | Cannot find the reference policy to delete. | Check XXX in the error message and make sure there are no typographical errors. |
| 2 | 404 | 40422100 | cdl: EventId not exist. (XXX.) | No history with requested eventId registered. | Check that there are no errors in the input. |
| 3 | 500 | 50023100 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
Manage reference policy (get list)
There is no main error message that occurs only with Manage reference policy (get list) Refer to Chapter 4.1 for the contents of common error messages and actions to take.
IV.7 Error Messages and Workarounds for Verify Trail API
The main error messages that occur with Verify trail and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 404 | 40423100 | Termination History does not exist. (XXX.) | There is no end history for the specified Lineage. Check that there are no errors in the input. | |
| 2 | 500 | 50025130 | Internal Server Error. (XXX.) | An unexpected error has occurred. | Contact your system administrator. |
Chapter V Error Messages for the Trust Seal Function
This chapter describes the error messages that are generated by the trust seal function and how to resolve them.
V.1 Common Error Messages and Workarounds for the Trust Seal Function
This section describes the error messages that are common to the functions described in Chapter 5 and how to resolve them.
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 400 | 40041100 | Invalid Parameter. (XXX). | The specified parameter is invalid. | Check the XXX in the error message and specify the correct value based on the API reference manual. |
| 2 | 403 | 40341100 | Bad Access Rights. (XXX). | Insufficient access privileges. | Check XXX in the error message and check the API reference manual to see if the role is appropriate. |
| 3 | 408 | 40841100 | Request Timeout. | A timeout error has occurred. | If the system is under load due to execution of another request, try re-execution at a time when the load is low. If this error occurs frequently, contact your system administrator. |
| 4 | 500 | 50040100 | XXX | An unexpected error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 5 | 500 | 50041100 | Internal Server Error. (XXX) | An unexpected error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
V.2 Error Messages and Workarounds for Create Credential API
The main error messages that occur with Create Credential and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50042100 | Internal SQL Error. | A SQL request error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50044100 | Internal DB Error. | An error occurred during DB connection processing. | Contact your system administrator. In that case, please contact us with an error message. |
V.3 Error Messages and Workarounds for Send Credential API
The main error messages that occur with Send credential and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50042100 | Internal SQL Error. | A SQL request error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50044100 | Internal DB Error. | An error occurred during DB connection processing. | Contact your system administrator. In that case, please contact us with an error message. |
V.4 Error Messages and Workarounds for Revoke Credential API
There is no main error message that occurs only with Revoke credential. Refer to Chapter 5.1 for the contents of common error messages and actions to take.
V.5 Error Messages and Workarounds for Get Credential API
The main error messages that occur with Get credential and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50042100 | Internal SQL Error. | A SQL request error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50044100 | Internal DB Error. | An error occurred during DB connection processing. | Contact your system administrator. In that case, please contact us with an error message. |
V.6 Error Messages and Workarounds for Get Received Credential API
The main error messages that occur with Get received credential and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50042100 | Internal SQL Error. | A SQL request error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50044100 | Internal DB Error. | An error occurred during DB connection processing. | Contact your system administrator. In that case, please contact us with an error message. |
V.7 Error Messages and Workarounds for Create Trust Seal API
The main error messages that occur with Create trust seal and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50042100 | Internal SQL Error. | A SQL request error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50044100 | Internal DB Error. | An error occurred during DB connection processing. | Contact your system administrator. In that case, please contact us with an error message. |
V.8 Error Messages and Workarounds for Get Trust Seal API
The main error messages that occur with Get trust seal and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50042100 | Internal SQL Error. | A SQL request error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50044100 | Internal DB Error. | An error occurred during DB connection processing. | Contact your system administrator. In that case, please contact us with an error message. |
V.9 Error Messages and Workarounds for Verify Trust Seal API
The main error messages that occur with Verify trust seal and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 500 | 50042100 | Internal SQL Error. | A SQL request error has occurred. | Contact your system administrator. In that case, please contact us with an error message. |
| 2 | 500 | 50044100 | Internal DB Error. | An error occurred during DB connection processing. | Contact your system administrator. In that case, please contact us with an error message. |
Chapter VI Error Messages for the Service Management Function
This chapter describes the error messages that occur in the service management function and how to handle them.
VI.1 Error Messages and Workarounds for Create Agent API
The main error messages that occur with Create agent and the corrective actions to take are as follows:
| No. | status codes | error detail code | error message | error content | workaround |
|---|---|---|---|---|---|
| 1 | 400 | 40003011 | Already Exist. ("XXX" is already exist.) " | The same agent ID already exists. | Check the XXX in the error message and specify the correct value based on the API reference manual. |
VI.2 Error Messages and Workarounds for Client Notification APIs
This subsection describes the error messages and corrective actions to be taken for client notification settings.
Register client notification
There is no main error message that occurs only with Register client notification. Refer to Chapter 1 for the contents of common error messages and actions to take.
Update client notification
There is no main error message that occurs only with Update client notification. Refer to Chapter 1 for the contents of common error messages and actions to take.
Delete client notification
There is no main error message that occurs only with Delete client notification. Refer to Chapter 1 for the contents of common error messages and actions to take.
Get client notification
There is no main error message that occurs only with Get client notification. Refer to Chapter 1 for the contents of common error messages and actions to take.
VI.3 Error Messages and Workaround for Geting Client Notification Settings Information
There are no specific error messages that occur only when retrieving client notification settings information.
For common error messages and workaround, please refer to Chapter 1.
VI.4 Error Messages and Workarounds for Geting API Usage Log
There is no main error message that occurs only with Geting API usage log. Refer to Chapter 1 for the contents of common error messages and actions to take.