3xxxx codes
Last updated
Last updated
Description | These error codes are related to the logic of the component for off-chain storage. They always come with the subcode, error-specific details are provided within the subcodes |
What to do | Check details of the subcode |
Message | object with docType: |
Description | The creation of a new document failed because a document with the same type and the document id already exists |
What to do | If you're trying to create an asset, try again, if error persists, contact CoreLedger and provide |
Message | mongo write operations response with error code: |
Description | The requested operation failed because of the internal error of the 3rd party component |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | mongo operations response with error code: |
Description | The requested operation failed because of the internal error of the 3rd party component |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | Document with type: |
Description | The requested document is not found |
What to do | If you expect this document to be written to the off-chain storage of the TEOS Platform, contact CoreLedger and provide |
Message | Document unexpected error |
Description | Some unexpected error happened, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | Object with docType: |
Description | The request for deleting the asset document can't be completed because asset is already written to the blockchain. Most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message |
|
Description | While searching for assets it is necessary to specify the type of the search. These are supported types: "fullRecords", "records" and "ids", most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | refId or refType missing |
Description | The amendment request doesn't have all necessary info about original asset record. Most likely you've managed to find a bug |
What to do | Check that you provide correct |
Message | Amendment referenced parent not found with docId: |
Description | The amendment request is for the original asset record which was not found |
What to do | Provide correct |
Message | Amendment author |
Description | Issuer address of the amendment must be the same as the issuer of the original asset record. |
What to do | Make sure that the amendment request is created using the same wallet and try again, if error persists, contact CoreLedger and provide |
Message | Amendment referenced tenant not match amendment tenant: |
Description | Tenant of the amendment must be the same as the tenant of the original asset record |
What to do | Make sure that the amendment request is created from the same tenant where the original asset record was created and try again, if error persists, contact CoreLedger and provide |
Message | Amendment referenced tenant not match amendment blockchain: |
Description | Blockchain of the amendment must be the same as the blockchain of the original asset record |
What to do | Make sure that the amendment request is created from the same tenant where the original asset record was created and try again, if error persists, contact CoreLedger and provide |
Message | Object with docType: |
Description | There was a try to set block reference for the asset where block reference is already set. Most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | Documents are already linked ({UniqueAssetIds}) |
Description | There was a try to link assets and some of them are already linked |
What to do | Make sure that you only link assets which are not yet linked |
Message | Documents are not linked ({UniqueAssetIds}) |
Description | There was a try to unlink assets and some of them are not linked |
What to do | Make sure that you only unlink assets which are linked |
Message | Cannot remove property ({schemaNames}) because it was already updated. |
Description | In a same amendment a value for a property was set and then there was a try to remove this property. These actions are mutually exclusive. |
What to do | Choose what to do: either update or delete the same property, but not both |
Message | Cannot remove language ({language}). The current document already contains some data in this language. |
Description | In a same amendment a value for a property was set in a certain language and then there was a try to remove the whole translation to that language. These actions are mutually exclusive. |
What to do | Choose what to do: either update some properties in a certain language or delete the whole translation in that language, but not both |
Message | Cannot update property ({fullSchemaPath}) because it was removed. |
Description | A property was removed in an amendment. Then there was a try to update a property in the same amendment. These actions are mutually exclusive. |
What to do | Choose what to do: either update or delete the same property, but not both |
Message | Cannot write or translate in the language ({language}) that was removed. |
Description | In an amendment a translation in a certain language was removed. Then there was a try to update a property in that language. These actions are mutually exclusive. |
What to do | Choose what to do: either update some properties in a certain language or delete the whole translation in that language, but not both |
Message | Parameter docType can not be null |
Description | Some unexpected error happened when processing your request, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Description | These error codes are related to the logic of the component which writes to the blockchain. They always come with the subcode, error-specific details are provided within the subcodes |
What to do | Check details of the subcode |
Message | Error code |
Description | Some unexpected error happened when processing your request, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | Error message has wrong format or count of passed parameters do not match. Error message: |
Description | Some unexpected error happened when processing your request, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | Error validating request. |
Description | Some validation of the request body has failed |
What to do | If you use TxServer directly, check that your request meets the requirements of the api and try again.
If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Provider |
Description | The provider associated with the transaction could not be found |
What to do | If you use TxServer directly, make sure that the request contains correct |
Message | Provider |
Description | The provider which is used in the request data is not active anymore and relation between the wallet and this provider can't be established |
What to do | If you use TxServer directly, make sure that the request contains correct |
Message | Provider |
Description | Some unexpected error happened when processing your request, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | No configured address |
Description | No configured contract address with requested technology found for provider |
What to do | If you use TxServer directly, make sure that the request contains correct contract address and technology and try again. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Address |
Description | Some unexpected error happened when processing your request, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | More than one active address |
Description | Some unexpected error happened when processing your request, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | Provider address nonce |
Description | Error occurred during validating nonce of the transaction being posted |
What to do | If you use TxServer directly, make sure that the request contains correct nonce and try again, if error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Source address |
Description | No address address with technology technology associated with device was found during validation of a signed transaction. |
What to do | If you use TxServer directly, check that you are using correct device and correct signer address (wallet), and that the address is added to the device. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Source address |
Description | No active address with technology associated with device was found during validation of a signed transaction. |
What to do | If you use TxServer directly, check that you are using correct device and correct signer address (wallet), and that the address is added to the device. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | No active assignments between client device and source address |
Description | No active address address with technology technology associated with to any device was found during posting a transaction. |
What to do | If you use TxServer directly, check that you are using correct device and correct signer address (wallet), and that the address is added to the device. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Signature missing |
Description | Posted transaction doesn't have required parameter "Signature". |
What to do | If you use TxServer directly, check that you sign the posted transaction with correct provider certificate and try again. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Signature does not match request data. |
Description | Posted transaction has invalid parameter "Signature". |
What to do | If you use TxServer directly, check that you sign the posted transaction with correct provider certificate and try again. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Device |
Description | Device which is used in the request is not found in TEOS Platform |
What to do | If you use TxServer directly, make sure that you're using the device id which was registered and connected to TxServer and try again, if error persists, contact CoreLedger and provide |
Message | Device |
Description | Device which is used in the request is not active anymore in TEOS Platform |
What to do | If you use TxServer directly, make sure that you're using the device id which was registered and connected to TxServer and try again, if error persists, contact CoreLedger and provide |
Message | No configured address |
Description | This error may happen when configuring association between provider and device addresses. |
What to do | If you use TxServer directly, check that you are using correct device and correct signer address (wallet), and that the address is added to the device. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Access token does not reference to device id. |
Description | Access token used in the request data is not related to the device id in the request data |
What to do | If you use TxServer directly, make sure that you're using correct access token of the authenticated user and that you're using the device id which was registered and connected to TxServer and try again, if error persists, contact CoreLedger and provide |
Message | Could not revoke access token. |
Description | Some unexpected error happened when processing your request, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | No configured provider |
Description | There is no any transaction provider associated with the pair address and deviceId in the request data |
What to do | If you use TxServer directly, add transaction provider to the |
Message | Blockchain technology |
Description | Technology used in the request data is not valid |
What to do | If you use TxServer directly, provide correct |
Message | Contract definition for contract |
Description | Contract definition for contract and technology not found. |
What to do | If you use TxServer directly, check that you are using correct contract address and blockchain technology. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Address registration grant |
Description | This error may happen when configuring association between provider and device addresses. |
What to do | If you use TxServer directly, generate new address registration grant and try again, if error persists, contact CoreLedger and provide |
Message | Address registration grant |
Description | This error may happen when configuring association between provider and device addresses. |
What to do | If you use TxServer directly, generate new address registration grant and try again, if error persists, contact CoreLedger and provide |
Message | Address registration grant |
Description | This error may happen when configuring association between provider and device addresses. |
What to do | If you use TxServer directly, generate new address registration grant and try again, if error persists, contact CoreLedger and provide |
Message | Address registration grant |
Description | This error may happen when configuring association between provider and device addresses, when the access registration grant was requested for a blockchain technology other then in the request. |
What to do | If you use TxServer directly, check that you are using correct value for blockchain technology. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Transaction |
Description | Transaction with specified id was not found |
What to do | Provide correct transactionId in the request data and try again |
Message | Transaction |
Description | Transaction with specified id has invalid state |
What to do | Revoke this transaction and create a new transaction. If you observe this problem with several transactions, contact CoreLedger and provide |
Message | Transaction |
Description | This error may happen, when you try to get a transaction from a device, that does not have an associated address, used as transaction signer address. |
What to do | If you use TxServer directly, check that the signer address is added to the device. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Transaction signature for transaction |
Description | This error may happen, when you try to submit a signed transaction from a device, that does not have an associated address, used as transaction signer address. |
What to do | If you use TxServer directly, check that the signer address is added to the device. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Transaction signature for transaction |
Description | This error may happen, when trying to perform an operation on the transaction, which is invalid for current transaction state. |
What to do | If you use TxServer directly, check the logic of your application. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message |
|
Description | Some error happened when processing your request in the Blockchain |
What to do | Revoke this transaction and create a new transaction. If you observe this problem with several transactions, contact CoreLedger and provide |
Message | Address |
Description | This error may happen when adding an address to a device. |
What to do | If you use TxServer directly, check that the address provided in the request has a correct format. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Duplicate nonce used for transaction. |
Description | This error may happen when several transactions with the same signer address are being submitted simultaneously. |
What to do | If you use TxServer directly, try to increase nonce value (+1), sign the transaction and submit again. In general, you should avoid submitting transactions from the same signer address simultaneously. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Insufficient funds for transaction. |
Description | Address does not have enough ether to complete transaction processing |
What to do | Top up the address balance or change gas parameters: decrease gas price and gas limit (it may help to decrease the price of this specific transaction) |
Message | Duplicate transaction. |
Description | This error may happen when the same transactions with identical parameters is being submitted several times. |
What to do | If you use TxServer directly, change the parameters of the transaction (nonce, gas price) and submit the transaction again. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Transaction will probably run into error. |
Description | This warning may occur when testing transaction against the current state of blockchain without actually submitting it. |
What to do | Check the parameters of the transaction and correct if necessary before submission. After the transaction is submitted, make sure that it reaches the state "Confirmed". If not - create another transaction. |
Message | No address data submitted. |
Description |
|
What to do | If you use TxServer directly, provide at least one address in the request data. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message |
|
Description | Error occurred during validating signed Ethereum transaction |
What to do | Contact CoreLedger and provide |
Message | Transaction data invalid. RLP data must contain 9 values. |
Description | Error occurred during validating signed Ethereum transaction |
What to do | If you use TxServer directly, check that parameters of the transaction signed and submitted by device correspond to the parameters of the transaction posted by provider. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Target address does not match. |
Description | Error occurred during validating signed Ethereum transaction. |
What to do | If you use TxServer directly, check that parameters of the transaction signed and submitted by device correspond to the parameters of the transaction posted by provider. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Amount does not match. |
Description | Error occurred during validating signed Ethereum transaction. |
What to do | If you use TxServer directly, check that parameters of the transaction signed and submitted by device correspond to the parameters of the transaction posted by provider. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Message | Transaction data does not match. |
Description | Error occurred during validating signed Ethereum transaction. |
What to do | If you use TxServer directly, check that parameters of the transaction signed and submitted by device correspond to the parameters of the transaction posted by provider. If error persists, contact CoreLedger and provide If you receive this error when calling TEOS API, try again, if error persists, contact CoreLedger and provide |
Description | This error code indicates, that a problem has occurred while processing the request in the backbone components of TEOS Platform Such errors always come with the subcode, error-specific details are provided within the subcodes |
What to do | check the subcode and its details |
Message | The length of array ( |
Description | The length of an array, provided as a blockchain transaction parameter, exceeds the allowed length |
What to do | Split the array into the parts, that fit the limitation, and send several transactions |
Message | Warp simulation error occured. |
Description | This error is returned, when some problem was found during warp execution simulation. For the details check the error subcode |
What to do | Check the error details and respective suggestions |
Message | There is no |
Description | Exchange with the selected warp can't be executed because the address offering desired asset doesn't have enough amount of sparks |
What to do | Select another warp or change the offered amount and try again |
Message | Asset Mismatch |
Description | Warp consists of a chain of supplies. Each next supply should have the desiredAssetId same as the previous supply's offeredAssetId, e.g. (desired1-offered2)->(desired2-offered3), where offered2 equals to desired2. The error will be returned if a warp with supply ids, breaking this rule, is executed/simulated |
What to do | Make sure that the warp supplies make a chain or select another warp and try again |
Message | One of supplies in the WARP failed |
Description | Exchange with the selected warp can't be executed because of the problems with one of the supplies |
What to do | Select another warp and try again. |
Message | One of supplies does not exist |
Description | Exchange with the selected warp can't be executed because one of the supplies does not exist anymore |
What to do | Select another warp and try again |
Message | Sender is blocked by compliance |
Description | There is a controller, preventing warp execution, if the sender (last supply owner) is blacklisted |
What to do | Select another warp and try again |
Message | Receiver is blocked by compliance |
Description | Exchange with the selected warp can't be executed because one of the receivers of the assets is not allowed to receive desired asset |
What to do | Select another warp or provide another address as a transaction signer and try again |
Message | Cannot estimate gas cost |
Description | Unexpected error during warp execution gas cost estimation |
What to do | Select another warp and try again |
Message | Supply |
Description | Exchange with the selected warp can't be executed because one of the supplies does not exist |
What to do | Select another warp and try again |
Message | Supply |
Description | Exchange with the selected warp can't be executed because one of the supplies was already consumed |
What to do | Select another warp and try again |
Message | Supply |
Description | Exchange with the selected warp can't be executed because one of the supplies has expired |
What to do | Select another warp and try again |
Message | Supply |
Description | The specified supply can not be executed, because its owner does not have enough sparks to the execution moment |
What to do | Select another warp and try again |
Message | Supply |
Description | Exchange with the selected warp can't be executed because the supply must be consumed fully ("take all" was set) but calculated output amount is less, than available in the supply |
What to do | Select another warp and try again |
Message | Some special rules were applied to supply |
Description | The warp can not be executed, as the were some special rules in supply container contract, preventing the execution |
What to do | Select another warp and try again |
Message | Supply |
Description | The transfer within the selected warp can't be executed because of compliance restrictions (e.g. asset controller doesn't allow this transfer) |
What to do | Select another warp and try again |
Message | Supply |
Description | The owner address of the supply is not allowed to give the sparks away |
What to do | Select another warp and try again |
Message | Supply |
Description | The desired address in the supply is not allowed to receive sparks |
What to do | Select another warp and try again |
Message | Provided ExternalReference |
Description | The external reference, provided for the supply is already used for another supply |
What to do | Retry the supply creation with another external reference |
Message | Balance of the address |
Description | The balance of the target address exceeds the limit for donation, request can't be completed |
What to do | Try again when |
Message | Only issuer or administrator can change this controller. The address |
Description | Controller can't be changed by the address which is used for signing transaction. Current address is not the issuer or administrator of the controller |
What to do | Use the address of controller issuer or administrator to change the controller |
Message | BlacklistReason not in the right format. The BlacklistReason value should be between 1 and 255 |
Description | Incorrect format of the blacklistReason |
What to do | Provide blacklistReason in the correct format and try again |
Message | The provided contract address does not implement the required controller interface |
Description | When adding an external controller, it must implement the required interface. The contract at the provided address does not implement the interface |
What to do | Contact CoreLedger team to find the decision to the problem |
Message | Address |
Description | The address from which transfer is initiated doesn't have enough sparks of the asset |
What to do | Provide another |
Message | AssetId |
Description | The request can't be executed because of the compliance restrictions (asset controller doesn't allow transfers to the target address) |
What to do | Provide another |
Message | AssetId |
Description | Some unexpected error happened, most likely you've managed to find a bug. |
What to do | Check the unique asset Id and its ledger part. Try again, if the error persists, contact CoreLedger and provide |
Message | AssetId |
Description | The address from which transfer is initiated doesn't have enough sparks of the asset |
What to do | Provide another |
Message | Supply |
Description | Supply can't be created because signing address doesn't have enough sparks of the offered asset |
What to do | Provide less value for the |
Message | Supply |
Description | Supply can't be created because the type is invalid. Some unexpected error happened, most likely you've managed to find a bug |
What to do | Try again, if error persists, contact CoreLedger and provide |
Message | Supply |
Description | Supply can't be created because of compliance restrictions (e.g. asset controller doesn't allow the transfer of the desired asset to the signing address or the transfer of the offered asset from the owner address) |
What to do | Provide another |
Message | Supply |
Description | There is not enough service asset sparks on the signing address to pay a fee for the supply creation |
What to do | Use another |
Message | Supply |
Description | Supply can't be created with the amount = 0 |
What to do | Set the amount bigger than 0 and try again |
Message | Supply |
Description | Supply can't be created with the exchange rate = 0 |
What to do | Set the exchange rate bigger than 0 and try again |
Message | Supply |
Description | The supply expiration date can not be set in the past |
What to do | Change the expiration date of the supply and try again |
Message | Schema names array |
Description | Asset object misses the display names for the sections path of custom definition items. |
What to do |
Message | Amendment with docId: |
Description | There was a try to change asset general properties which are not allowed to be amended |
What to do |
Provide value for SectionsPathNames structured in the way which will match the SectionsPath for custom definition items. For example, if SectionsPath is defined as [General][Issuer], then SectionsPathNames must have structure [DisplayNameForGeneral][DisplayNameForIssuer].
Make sure that your amendment request does not contain of the asset and try again