-
Notifications
You must be signed in to change notification settings - Fork 17
9.6 Error Codes
Rathna edited this page Oct 7, 2024
·
1 revision
| Error Code | Description |
|---|---|
| 0 | Replication of the API was successful |
| 1 | The API-Specification is not supported by the APIM-CLI |
| 2 | Error in parsing input parameters |
| 5 | There is a missing parameter |
| 6 | There is an invalid parameter |
| 7 | The API already exists for another organization |
| 8 | Backend API definition is not available |
| 10 | No change between desired and actual API has been detected |
| 12 | Export failed Export-Folder already exists |
| 13 | Creating of a new API fails, when flag updateOnly is set |
| 15 | A breaking change detected, but no force flag was given |
| 17 | An action failed due to a missing Admin-Account |
| 20 | Cannot parse a HTTP-Response for REST-API-Call |
| 25 | Cannot send a HTTP-Request |
| 30 | Cannot read or parse JSON-Payload |
| 35 | Cannot create API-Proxy (FE-API) |
| 40 | Cannot import Swagger-Definition -> Can't create BE-API |
| 45 | Can't update API-Proxy (FE-API) |
| 47 | Can't update Quota-Configuration |
| 50 | Can't update the API-Status |
| 51 | Unknown user given |
| 52 | Error changing password of user |
| 53 | Query-String routing option in API-Manager is not enabled |
| 54 | The given API-Config needs a query string, as API-Manager has it enabled |
| 55 | Can't upgrade API-Access |
| 56 | API is unknown / not found, etc |
| 57 | Unknown organization given. Please check the API-Config-File |
| 58 | Unknown application given. Please check the API-Config-File |
| 59 | An error happens while managing organization permissions |
| 60 | Generic API-Manager communication error |
| 61 | At least one configured organization is invalid. Check the log file for more information |
| 62 | At least one configured application is invalid. Check the log file for more information |
| 63 | Unknown remote host given |
| 64 | No API Specification configured |
| 65 | Can't read the given API-Definition |
| 66 | Can't read the given WSDL-File |
| 67 | Login to API-Manager failed |
| 68 | A unique remote host based on the given filter could not be found |
| 69 | Unexpected API-Manager communication error |
| 70 | Can't read the API Config-File |
| 71 | The given Quota-Configuration is invalid |
| 72 | The given operationId cannot be found |
| 73 | Invalid profile reference is used. For instance using a CORS-Profile in an InboundProfile |
| 75 | Unsupported feature |
| 76 | The given backend basepath is not a valid URL |
| 80 | If the Desired & Actual API can't be compared for any reason |
| 81 | The password for the keystore is wrong |
| 85 | A custom policy-name is unknown (Request-, Routing, ...) |
| 87 | It wasn't possible to setup the V-Host for the FE-API |
| 88 | Cannot create HTTP client |
| 89 | The given application name is not unique. More than one application has been found |
| 90 | API could not be approved |
| 91 | API could not be deleted |
| 92 | Organization could not be deleted |
| 93 | Error granting access to an API |
| 94 | Error exporting API-Date file |
| 95 | Error creating/updating an application |
| 96 | API could not be changed to publish state |
| 97 | API could not be changed to unpublish state |
| 99 | An unexpected error occurred |
| 100 | There was an unexpected error checking the expiration date of certificates |
| 101 | Certificates found that will expire within the given number of days |
| 102 | Error granting application access to API |
| 103 | Error revoking application access to API |
| 104 | The given security profile is invalid |