Error Messages Relating to External Adapters
Code | 400001 |
Severity | Error |
Message | Authentication method: {0} not implemented |
Description | Authentication method: {0} need to be implemented. |
Code | 400002 |
Severity | Error |
Message | Adapter controller error: Not enough parameters |
Description | Adapter controller needs 3 parameters: Config file, Schema file and command (start/stop or status ) |
Code | 400003 |
Severity | Error |
Message | Unknown command: {0} |
Description | Valid commands are start, stop and status. {0} is wrong command. |
Code | 400004 |
Severity | Error |
Message | Exception in adapter controller: |
Description | Exception in adapter controller, See additional message and stack trace. |
Code | 400005 |
Severity | Error |
Message | Cannot run service on port :{0} |
Description | Service cannot be run on port {0}, port might already be in use. |
Code | 400006 |
Severity | Error |
Message | Failed to accept client Connection |
Description | Failed to accept client Connection. See additional exception details. |
Code | 400007 |
Severity | Error |
Message | Cannot send message: {0} |
Description | Message cannot be sent. See additional errors for reason. |
Code | 400008 |
Severity | Error |
Message | Cannot queue up record |
Description | Record cannot be placed to queue. See additional error details. |
Code | 400009 |
Severity | Error |
Message | Model Generator error: Not enough parameters |
Description | Model generator needs 2 parameters: Fix Dictionary directory path and template directory |
Code | 400010 |
Severity | Error |
Message | Cannot send data to client : {0} |
Description | Cannot send data to client for client socket {0}. See additional exception details for cause. |
Code | 400011 |
Severity | Error |
Message | Failed to read request from client : {0} |
Description | Request cannot be read from client socket {0}. See additional exception details for cause. |
Code | 400012 |
Severity | Error |
Message | Cannot write HTTP response |
Description | See additional exception details. |
Code | 400013 |
Severity | Error |
Message | Failed to connect to {0}:{1} |
Description | Connection to {0}:{1} failed. See additional exception details for cause. |
Code | 400014 |
Severity | Critical |
Message | Could not login as {0} |
Description | Login with username {0} failed. |
Code | 400015 |
Severity | Error |
Message | Failed Request:{0} |
Description | See additional exception details. |
Code | 400016 |
Severity | Error |
Message | Failed to get dictionary |
Description | See additional exception details. |
Code | 400017 |
Severity | Error |
Message | Failed to get the response statuses |
Description | See additional exception details. |
Code | 400018 |
Severity | Error |
Message | Error dispatching message |
Description | Message cannot be dispatched. See additional error details for reason. |
Code | 400019 |
Severity | Error |
Message | Message dispatcher interrupted |
Description | This is mainly caused by InterruptedException. See additional error details for reason. |
Code | 400020 |
Severity | Error |
Message | Cannot set value {0} to field {1} |
Description | Value of field {1} cannot be set to {0}. See additional error details for reason. |
Code | 400021 |
Severity | Error |
Message | Data dictionary timed out. |
Description | Data dictionary timed out. Please check configuration parameters. |
Code | 400022 |
Severity | Error |
Message | Cannot load Data dictionary. |
Description | See additional exception details. |
Code | 400023 |
Severity | Error |
Message | Error getting Data dictionary. |
Description | Error getting Data dictionary. See additional exception details. |
Code | 400024 |
Severity | Error |
Message | Wrong number of columns ({0}) in stream '{1}', {2} expected. |
Description | Stream '{1}' must contain {2} no. of columns. |
Code | 400025 |
Severity | Error |
Message | fail to create subscriber ''{0}''. |
Description | fail to create subscriber ''{0}''. |
Code | 400026 |
Severity | Error |
Message | Failed to get project ''{0}'' |
Description | Failed to get project ''{0}'' |
Code | 400027 |
Severity | Error |
Message | Failed to create a publisher |
Description | Failed to create a publisher |
Code | 400028 |
Severity | Error |
Message | Stream ''{0}'' has not been registered yet |
Description | Stream ''{0}'' has not been registered yet |
Code | 400029 |
Severity | Error |
Message | COMMAND: {0} |
Description | COMMAND: {0} |
Code | 400030 |
Severity | Error |
Message | WARNING: Argument delimiter is not specified for connection {0}. Using default of ''##''. |
Description | WARNING: Argument delimiter is not specified for connection {0}. Using default of ''##''. |
Code | 400031 |
Severity | Error |
Message | WARNING: Invalid refresh interval value ''{0}'' specified for connection {1}. Using default of 0. |
Description | WARNING: Invalid refresh interval value ''{0}'' specified for connection {1}. Using default of 0. |
Code | 400032 |
Severity | Error |
Message | WARNING: Both hot spare port and hostname must be specified to use the the hot spare configuration. Ignoring hot spare values for connection |
Description | WARNING: Both hot spare port and hostname must be specified to use the the hot spare configuration. Ignoring hot spare values for connection |
Code | 400033 |
Severity | Error |
Message | Invalid port value ''{0}'' specified for connection ''{1}''. Value must a positive number greater than 0 and less than 65535 |
Description | Invalid port value ''{0}'' specified for connection ''{1}''. Value must a positive number greater than 0 and less than 65535 |
Code | 400034 |
Severity | Error |
Message | Invalid port value ''{0}'' specified for connection ''{1}''. Value must a positive number greater than 0 and less than 65535 |
Description | Invalid port value ''{0}'' specified for connection ''{1}''. Value must a positive number greater than 0 and less than 65535 |
Code | 400035 |
Severity | Error |
Message | Invalid refreshInterval value ''{0}'' specified for connection ''{1}''. Value must a positive number greater than or equal to 0 |
Description | Invalid refreshInterval value ''{0}'' specified for connection ''{1}''. Value must a positive number greater than or equal to 0 |
Code | 400036 |
Severity | Error |
Message | connection to esp has not been setup yet |
Description | connection to esp has not been setup yet |
Code | 400037 |
Severity | Error |
Message | Unsupported datatype: |
Description | Unsupported datatype: |
Code | 400038 |
Severity | Error |
Message | Stream ''{0}'' does not exist in StreamObserverManager |
Description | Stream ''{0}'' does not exist in StreamObserverManager |
Code | 400039 |
Severity | Error |
Message | Can not subscribe for stream ''{0}'' |
Description | Can not subscribe for stream ''{0}'' |
Code | 400040 |
Severity | Error |
Message | can not find streamName for event |
Description | can not find streamName for event |
Code | 400041 |
Severity | Error |
Message | data lost |
Description | data lost |
Code | 400042 |
Severity | Error |
Message | fatal error |
Description | fatal error |
Code | 400043 |
Severity | Error |
Message | platformStream not set |
Description | platformStream not set |
Code | 400044 |
Severity | Warning |
Message | tableName not specified, setting to streamName: {0} |
Description | tableName not specified, setting to streamName: {0} |
Code | 400045 |
Severity | Error |
Message | Error connecting to TDS listener. Adapter might not have started properly. Please make sure the TDS port is not used by other process. |
Description | Please check stacktrace below for more information |
Code | 400046 |
Severity | Error |
Message | RuntimeParams is null |
Description | RuntimeParams is null |
Code | 400047 |
Severity | Error |
Message | Error parsing {0} |
Description | Error parsing {0} |
Code | 400048 |
Severity | Error |
Message | Error occurred establishing connection to ESP |
Description | Please check stacktrace below for more information |
Code | 400049 |
Severity | Error |
Message | SQL Execution Error |
Description | Please check stacktrace below for more information |
Code | 400050 |
Severity | Error |
Message | SQL Parser Unsupported Statement |
Description | Please check stacktrace below for more information |
Code | 400051 |
Severity | Error |
Message | SQL Parse Error |
Description | Please check stacktrace below for more information |
Code | 400052 |
Severity | Error |
Message | Problem in handleLanguage for command: {0} |
Description | Please check stacktrace below for more information |
Code | 400053 |
Severity | Error |
Message | Problem in handleBulk |
Description | Please check stacktrace below for more information |
Code | 400054 |
Severity | Error |
Message | Error in error response to RPC |
Description | Please check stacktrace below for more information |
Code | 400055 |
Severity | Error |
Message | Unexpected error in capability print out |
Description | Please check stacktrace below for more information |
Code | 400056 |
Severity | Error |
Message | Error in handleAttention() |
Description | Please check stacktrace below for more information |
Code | 400057 |
Severity | Error |
Message | Error in getJConnectVersion() |
Description | Please check stacktrace below for more information |
Code | 400058 |
Severity | Warning |
Message | dbName is null |
Description | dbName expected with "USE dbName" syntax |
Code | 400059 |
Severity | Warning |
Message | Column name {0} does not exist in Stream. Skipping |
Description | Column name {0} does not exist in Stream. Skipping |
Code | 400060 |
Severity | Error |
Message | Error parsing {0} value for column {1} |
Description | Error parsing {0} value for column {1} |
Code | 400061 |
Severity | Error |
Message | Could not parse Platform HotSpare Port parameter |
Description | Please check stacktrace below for more information |
Code | 400062 |
Severity | Error |
Message | Could not parse Platform Command Port parameter |
Description | Please check stacktrace below for more information |
Code | 400063 |
Severity | Error |
Message | Could not parse Platform Ssl parameter |
Description | Please check stacktrace below for more information |
Code | 400064 |
Severity | Error |
Message | Could not parse Platform Sql Port parameter |
Description | Please check stacktrace below for more information |
Code | 400065 |
Severity | Error |
Message | Could not parse TDS Listener Port parameter |
Description | Please check stacktrace below for more information |
Code | 400066 |
Severity | Error |
Message | Could not parse TDS SSL Listener Port parameter |
Description | Please check stacktrace below for more information |
Code | 400067 |
Severity | Error |
Message | Could not parse Batch Size parameter |
Description | Please check stacktrace below for more information |
Code | 400068 |
Severity | Error |
Message | Runtime Params Error |
Description | Please check stacktrace below for more information |
Code | 400069 |
Severity | Error |
Message | Error executing Stop |
Description | Please check stacktrace below for more information |
Code | 400070 |
Severity | Warning |
Message | Discover::New DataType found- {0} -Defaulting to string |
Description | Discover::New DataType found- {0} -Defaulting to string |
Code | 400071 |
Severity | Error |
Message | No subscriptions found for {0} |
Description | No subscriptions found for {0} |
Code | 400072 |
Severity | Error |
Message | Incorrect Replication Server connection user/password specified |
Description | Incorrect Replication Server connection user/password specified, login denied |
Code | 400073 |
Severity | Error |
Message | Error initializing SSL |
Description | Please check stacktrace below for more information |
Code | 400074 |
Severity | Error |
Message | Incorrect Adapter admin user/password specified |
Description | Incorrect Adapter admin user/password specified, login denied |
Code | 400075 |
Severity | Error |
Message | ''Max Rows (internal)'' property on ''{0}'' has an invalid value. |
Description | ''Max Rows (internal)'' property on ''{0}'' has value ''{1}'', which is not a valid value. Must be a positive integer. |
Code | 400076 |
Severity | Error |
Message | ''Max Rows (internal)'' property on ''{0}'' has multiple different definitions |
Description | ''Max Rows (internal)'' property on ''{0}'' has multiple different definitions, using ''{1}'', ignoring ''{2}''. |
Code | 400077 |
Severity | Error |
Message | Error decrypting password |
Description | Please check stacktrace below for more information |
Code | 400078 |
Severity | Error |
Message | Error parsing adapter configuration |
Description | Please check stacktrace below for more information |
Code | 400079 |
Severity | Error |
Message | Error executing RFC {0} |
Description | Please check stacktrace below for more information |
Code | 400080 |
Severity | Error |
Message | Error publishing to ESP, data row is skipped |
Description | Please check stacktrace below for more information |
Code | 400081 |
Severity | Error |
Message | Error mapping ESP data to RFC parameters |
Description | Please check stacktrace below for more information |
Code | 400082 |
Severity | Error |
Message | Batched data rows will be removed |
Description | Batched data rows will be removed |
Code | 400083 |
Severity | Error |
Message | Null parameter list for field {0} |
Description | Null parameter list for field {0} |
Code | 400084 |
Severity | Error |
Message | Parameter {0} is not a structure |
Description | Parameter {0} is not a structure |
Code | 400085 |
Severity | Error |
Message | Error converting data for field {0} |
Description | Please check stacktrace below for more information |
Code | 400086 |
Severity | Error |
Message | Field {0} is not defined in table {1} |
Description | Field {0} is not defined in table {1} |
Code | 400087 |
Severity | Error |
Message | Attribute sourceType not defined for input parameter {0} |
Description | Attribute sourceType not defined for input parameter {0} |
Code | 400088 |
Severity | Error |
Message | Field {0} is not defined in previous RFC |
Description | Field {0} is not defined in previous RFC |
Code | 400089 |
Severity | Error |
Message | Variable {0} is not defined under <variables> |
Description | Variable {0} is not defined under <variables> |
Code | 400090 |
Severity | Error |
Message | Field {0} is not defined |
Description | Field {0} is not defined |
Code | 400091 |
Severity | Error |
Message | Error processing field {0} |
Description | Please check stacktrace below for more information |
Code | 400092 |
Severity | Error |
Message | Error initializing adapter |
Description | Please check stacktrace below for more information |
Code | 400093 |
Severity | Error |
Message | Mapping for {0} does not have espField |
Description | Mapping for {0} does not have espField |
Code | 400094 |
Severity | Error |
Message | No mapping defined for {0} |
Description | No mapping defined for {0} |
Code | 400095 |
Severity | Error |
Message | RFC {0} inactive or not defined in SAP system |
Description | RFC {0} inactive or not defined in SAP system |
Code | 400096 |
Severity | Error |
Message | espField {0} specified in mapping {1} not defined in ESP schema |
Description | espField {0} specified in mapping {1} not defined in ESP schema |
Code | 400097 |
Severity | Error |
Message | Field {0} is not defined in BW query output |
Description | Field {0} is not defined in BW query output |
Code | 400100 |
Severity | Critical |
Message | Cannot create default SP publication |
Description | SP Publication creation failed. |
Code | 400101 |
Severity | Critical |
Message | Error while sending heartbeat |
Description | See Additional exception details. |
Code | 400102 |
Severity | Critical |
Message | Error:Cannot publish record to stream '{0}' |
Description | Publishing to Stream {0} failed. |
Code | 400103 |
Severity | Critical |
Message | Error:Cannot issue commit to publisher |
Description | Please check stacktrace below for more information |
Code | 400200 |
Severity | Critical |
Message | Exception in subscriber initialisation |
Description | Exception in subscriber initialisation |
Code | 400201 |
Severity | Critical |
Message | Exception in subscriber addObserver |
Description | Exception in subscriber addObserver |
Code | 400203 |
Severity | Critical |
Message | Exception in subscriber addObserver |
Description | Exception in subscriber addObserver |
Code | 400204 |
Severity | Error |
Message | Unsupported datatype:{0} |
Description | {0} is not supported datatypes. Please see documentation for supported datatypes for adapter in subject. |
Code | 400205 |
Severity | Error |
Message | Cannot start AEP subscription. |
Description | See additional exception details for more info. |
Code | 400205 |
Severity | Error |
Message | Cannot subscribe client {0} to stream {1} |
Description | See additional exception details for more info. |
Code | 400206 |
Severity | Error |
Message | Symbol=[{0}] : An error occurred creating subscription: {1} |
Description | Error while creating MAMA subscription. See error details. |
Code | 400207 |
Severity | Error |
Message | Duplicate subscription key: {0} |
Description | Already subscribed with the key {0}. |
Code | 400208 |
Severity | Warning |
Message | Message received on unknown subscription: {0} |
Description | Message received on unknown subscription: {0} |
Code | 400209 |
Severity | Warning |
Message | Message received on destroyed subscription : {0} |
Description | Message received on destroyed subscription : {0} |
Code | 400300 |
Severity | Error |
Message | Error: invalid configuration file. Adapter can not be started. |
Description | Invalid configuration file provided. Adapter can not be started. |
Code | 400301 |
Severity | Error |
Message | XML file {0} not found |
Description | XML file {0} not found. Please check the path carefully. |
Code | 400302 |
Severity | Error |
Message | Schema file {0} not found |
Description | Schema file {0} not found. Please check the path carefully. |
Code | 400303 |
Severity | Error |
Message | Bad XML in file {0} |
Description | {0} file has invalid XML content. Update the file to have valid XML. |
Code | 400304 |
Severity | Error |
Message | Cannot open file {0}, {1} |
Description | Error opening file:{0}, {1} |
Code | 400305 |
Severity | Error |
Message | Cannot write message to file {0} |
Description | See if the user has sufficient rights for the file {0}. |
Code | 400306 |
Severity | Error |
Message | Could not load properties file {0} |
Description | Error loading properties file {0} |
Code | 400307 |
Severity | Error |
Message | Could not parse properties file {0} |
Description | Error parsing properties file {0} |
Code | 400308 |
Severity | Error |
Message | Kerberos KDC not set |
Description | Please set Kerberos KDC in configuration file. |
Code | 400309 |
Severity | Error |
Message | Kerberos realm not set |
Description | Please set Kerberos realm in configuration file. |
Code | 400310 |
Severity | Error |
Message | Kerberos service principal not set |
Description | Please set Kerberos service principal in configuration file. |
Code | 400311 |
Severity | Error |
Message | Cannot create resume status file in directory {0}. The resume mode will be disabled. |
Description | Please check if the user has sufficient rights for the directory {0}. |
Code | 400312 |
Severity | Error |
Message | Error reading file: {0} |
Description | No additional information available. |
Code | 400313 |
Severity | Error |
Message | Cannot write resume status file {0}. |
Description | Please check if the user has sufficient rights for the file {0}. |
Code | 400314 |
Severity | Error |
Message | Validate XML file {0} fail. Please check if it obeys the constraints of schemas definition file {1}. |
Description | Validate XML file {0} fail. Please check if it obeys the constraints of schemas definition file {1}. |
Code | 400401 |
Severity | Error |
Message | FIX Message has no MsgType field: {0} |
Description | Please add MsgType field. FIX Message: {0} |
Code | 400402 |
Severity | Error |
Message | Invalid message : {0} |
Description | Please correct syntax. message : {0} |
Code | 400403 |
Severity | Error |
Message | Unknown message type : {0} |
Description | Message type {0} is invalid. Use correct message type. |
Code | 400404 |
Severity | Error |
Message | Cannot translate message to records: {0} |
Description | See additional details for error. |
Code | 400405 |
Severity | Error |
Message | Bad message format. |
Description | Bad message format. |
Code | 400406 |
Severity | Error |
Message | Bad request {0} from client {1} : no stream specified |
Description | Stream is not specified in the request : {0}, from client {1} |
Code | 400407 |
Severity | Error |
Message | Bad request {0} from client {1} : no such stream {2} |
Description | Stream {2} present in request {0} does not exist. |
Code | 400408 |
Severity | Error |
Message | Client:{0} already subscribed to Stream:{1} |
Description | Client:{0} already subscribed to Stream:{1} |
Code | 400409 |
Severity | Error |
Message | Bad request: {0} from client {1} stream {2} contains no column {3} |
Description | Stream {2} does not contain column {3} |
Code | 400410 |
Severity | Error |
Message | Bad request {0} from client {1}: column {2} in stream {3} is not of string type. |
Description | Column {2} in stream {3} is not of string type. |
Code | 400411 |
Severity | Error |
Message | Bad request {0} from client {1} |
Description | Correct the request content |
Code | 400412 |
Severity | Error |
Message | Bad HTTP Request : {0} |
Description | Correct the HTTP request content |
Code | 400413 |
Severity | Error |
Message | Discarded message {0} : has wrong size, expected {1} |
Description | IDC message has wrong size. Message has been discarded. |
Code | 400414 |
Severity | Error |
Message | Discarded message {0} :stray <EOT> |
Description | Stray <EOT> found in message. Message discarded |
Code | 400415 |
Severity | Error |
Message | Discarded stray byte <{0}> |
Description | Stray byte <{0}> found in message. Byte discarded |
Code | 400416 |
Severity | Error |
Message | Bad message token {0} |
Description | Found bad token during parsing IDC message. |
Code | 400417 |
Severity | Error |
Message | Bad message tag: {0} |
Description | Found bad message tag {0} while parsing IDC message. |
Code | 400418 |
Severity | Error |
Message | No such stream: {0} |
Description | Stream {0} does not exist. |
Code | 400419 |
Severity | Error |
Message | Stream {0} does not contain required column {1} |
Description | Stream {0} should contain required column {1} |
Code | 400420 |
Severity | Error |
Message | Stream {0}, coulmn {1} is not of type String |
Description | Change Stream definition {0}, column {1} must be of type String. |
Code | 400421 |
Severity | Error |
Message | Column {0}, is not Key column in stream {1}. |
Description | Change Stream {1} definition, column {0} must be key column. |
Code | 400422 |
Severity | Error |
Message | At least one of the columns '{0}', '{1}', '{2}' is required in stream {3} |
Description | Change Stream definition {3}, include at least one of the column. |
Code | 400422 |
Severity | Error |
Message | coulmn {0} in Stream {1} is not of type Long |
Description | Change Stream definition {1}, column {0} must be of type Long. |
Code | 400423 |
Severity | Error |
Message | Invalid watchlist operation: UPDATE |
Description | Only 'INSERT' and 'delete' operations permitted. |
Code | 400424 |
Severity | Error |
Message | Stream {0} is both inbound and outbound. |
Description | Some adapters are only inbound or outbound. Streams for them must be either inbound or outbound. |
Code | 400425 |
Severity | Error |
Message | coulmn {0} in Stream {1} is not of type Integer |
Description | Change Stream definition {1}, column {0} required to be of type Integer. |
Code | 400426 |
Severity | Error |
Message | No target stream in record {0} |
Description | No target stream in record |
Code | 400427 |
Severity | Error |
Message | Name of GD key column in Log Window {0} has not been specified. |
Description | Name of GD key column in Log Window {0} has not been specified. |
Code | 400428 |
Severity | Error |
Message | Name of GD opcode column in Log Window {0} has not been specified. |
Description | Name of GD opcode column in Log Window {0} has not been specified. |
Code | 400429 |
Severity | Error |
Message | Name of Control Window for Log Window {0} has not been specified. |
Description | Name of Control Window for Log Window {0} has not been specified. |
Code | 400430 |
Severity | Error |
Message | Control Window specified is same for {0} and {1} Log Windows. |
Description | Each Log Window should have its own Control Window. |
Code | 400431 |
Severity | Error |
Message | Control Window {0} specified for Log Window {1} does not exists. |
Description | Control Window {0} specified for Log Window {1} does not exists. |
Code | 400432 |
Severity | Error |
Message | GD key column {0} specified for Log Window {1} does not exists. |
Description | GD key column {0} specified for Log Window {1} does not exists. |
Code | 400433 |
Severity | Error |
Message | GD opcode column {0} specified for Log Window {1} does not exists. |
Description | GD opcode column {0} specified for Log Window {1} does not exists. |
Code | 400434 |
Severity | Error |
Message | GD Batch Size for Log Window {0} has not been specified. |
Description | GD Batch Size for Log Window {0} has not been specified. |
Code | 400435 |
Severity | Error |
Message | GD Purge Interval for Log Window {0} has not been specified. |
Description | GD Purge Interval for Log Window {0} has not been specified. |
Code | 400500 |
Severity | Error |
Message | Adapter needs a valid license to start |
Description | Adapter needs a valid license to start |
Code | 400501 |
Severity | Error |
Message | License file checked in |
Description | The license file has been successfully checked in |
Code | 400502 |
Severity | Error |
Message | Failed to create license manager |
Description | The license manager could not be created |
Code | 400503 |
Severity | Error |
Message | Failed to get license type from license manager |
Description | The license type was unable to be obtained from the license manager. Please ensure this is set in the properties file. |
Code | 400504 |
Severity | Error |
Message | Failed to checkout license |
Description | The license checkout failed. Please ensure you have a valid license and it is setup properly |
Code | 400505 |
Severity | Error |
Message | {0} adapter checked out license successfully |
Description | {0} adapter checked out license successfully |
Code | 400506 |
Severity | Error |
Message | {0} adapter has expired license |
Description | {0} adapter has an expired license. Please obtain a new license. |
Code | 400507 |
Severity | Error |
Message | {0} adapter is in install grace period |
Description | {0} adapter is in install grace period. Please obtain a valid license. |
Code | 400508 |
Severity | Error |
Message | {0} adapter is in runtime grace period |
Description | {0} adapter is in runtime grace period. Please obtain a valid license. |
Code | 400509 |
Severity | Error |
Message | {0} adapter is in support grace period |
Description | {0} adapter is in support grace period. Please obtain a valid license. |
Code | 400510 |
Severity | Error |
Message | Failed to check in license |
Description | The license file could not be checked in. |
Code | 400511 |
Severity | Error |
Message | License expired, please check server log file |
Description | License expired, please check server log file |
Code | 400800 |
Severity | Error |
Message | The command parameters are invalid. |
Description | The command parameters are invalid. |
Code | 400801 |
Severity | Error |
Message | The configuration file does not exist: {0} |
Description | The configuration file does not exist: {0} |
Code | 400802 |
Severity | Error |
Message | The control command is not supported: {0} |
Description | The control command is not supported: {0} |
Code | 400803 |
Severity | Error |
Message | The configuration file is invalid: {0} |
Description | The configuration file is invalid: {0} |
Code | 400804 |
Severity | Error |
Message | Schema discovery is not supported. |
Description | Schema discovery is not supported. |
Code | 400805 |
Severity | Error |
Message | Schema discovery failed. |
Description | Schema discovery failed. |
Code | 400806 |
Severity | Error |
Message | Modules list in configuration file is invalid: {0} |
Description | Modules list in configuration file is invalid: {0} |
Code | 400807 |
Severity | Error |
Message | Multiple transporters cannot be specified in the same configuration file. |
Description | Multiple transporters cannot be specified in the same configuration file. |
Code | 400808 |
Severity | Error |
Message | The Next property of module {0} is set to an invalid instance name {1} |
Description | The Next property of module {0} is set to an invalid instance name {1} |
Code | 400809 |
Severity | Error |
Message | The module {0} is invalid: its classpath cannot be found. |
Description | The module {0} is invalid: its classpath cannot be found. |
Code | 400810 |
Severity | Error |
Message | The output data type of module {0} does not match the input data type of module {1}, they cannot be connected. |
Description | The output data type of module {0} does not match the input data type of module {1}, they cannot be connected. |
Code | 400811 |
Severity | Error |
Message | Failed to connect to the ESP project. |
Description | Failed to connect to the ESP project. |
Code | 400812 |
Severity | Error |
Message | Key not found. |
Description | Key not found. |
Code | 400813 |
Severity | Error |
Message | Invalid authentication configuration. |
Description | Invalid authentication configuration. |
Code | 400814 |
Severity | Error |
Message | EspPublisher parameters are missing |
Description | EspPublisher parameters are missing |
Code | 400815 |
Severity | Error |
Message | Failed to get publisher |
Description | Failed to get publisher |
Code | 400816 |
Severity | Error |
Message | Adapter Row has an unsupported Block Flag {0} |
Description | Adapter Row has an unsupported Block Flag {0} |
Code | 400817 |
Severity | Error |
Message | EspSubscriber parameters are missing |
Description | EspSubscriber parameters are missing |
Code | 400818 |
Severity | Error |
Message | Error sending rows |
Description | Error sending rows |
Code | 400819 |
Severity | Error |
Message | User Error: No such row {0} |
Description | User Error: No such row {0} |
Code | 400820 |
Severity | Error |
Message | Fatal Error: Wrong observer was created |
Description | Fatal Error: Wrong observer was created |
Code | 400821 |
Severity | Error |
Message | The module type of module instance {0} is not supported. |
Description | The module type of module instance {0} is not supported. |
Code | 400822 |
Severity | Error |
Message | Failed to create publisher |
Description | Failed to create publisher |
Code | 400823 |
Severity | Error |
Message | Fail to connect publisher |
Description | Fail to connect publisher |
Code | 400824 |
Severity | Error |
Message | Error: {0} runnable interface is null |
Description | Error: {0} runnable interface is null |
Code | 400825 |
Severity | Error |
Message | Fatal Error: No input queue was found |
Description | Fatal Error: No input queue was found |
Code | 400826 |
Severity | Error |
Message | Guaranteed Delivery mode of the module EspSubscriber is disabled because some parameters are missing. These parameters should be configured if parameter GDMode is set to true: GDKeyColumnName, GDOpodeColumnName, GDControlStream, GDBatchSize, GDPurgeInterval. |
Description | Guaranteed Delivery mode of the module EspSubscriber is disabled because some parameters are missing. These parameters should be configured if parameter GDMode is set to true: GDKeyColumnName, GDOpodeColumnName, GDControlStream, GDBatchSize, GDPurgeInterval. |
Code | 400827 |
Severity | Error |
Message | Invalid authentication configuration. These parameters should be configured if parameter AuthType is set to user_password: User, Password |
Description | Invalid authentication configuration. These parameters should be configured if parameter AuthType is set to user_password: User, Password |
Code | 400828 |
Severity | Error |
Message | Invalid authentication configuration. These parameters should be configured if parameter AuthType is set to server_rsa: User, RSAKeyStore, RSAKeyStorePassword |
Description | Invalid authentication configuration. These parameters should be configured if parameter AuthType is set to server_rsa: User, RSAKeyStore, RSAKeyStorePassword |
Code | 400829 |
Severity | Error |
Message | Invalid authentication configuration. These parameters should be configured if parameter AuthType is set to kerberos: User, KerberosKDC, KerberosRealm, KerberosService, KerberosTicketCache |
Description | Invalid authentication configuration. These parameters should be configured if parameter AuthType is set to kerberos: User, KerberosKDC, KerberosRealm, KerberosService, KerberosTicketCache |
Code | 400830 |
Severity | Error |
Message | Invalid authentication configuration. AuthType is not supported: {0}. These auth types are supported: user_password, server_rsa, kerberos |
Description | Invalid authentication configuration. AuthType is not supported: {0}. These auth types are supported: user_password, server_rsa, kerberos |
Code | 400831 |
Severity | Error |
Message | Invalid authentication configuration. These parameters should be configured if parameter encrypted is set to true: User, EncryptionAlgorithm, RSAKeyStore, RSAKeyStorePassword |
Description | Invalid authentication configuration. These parameters should be configured if parameter encrypted is set to true: User, EncryptionAlgorithm, RSAKeyStore, RSAKeyStorePassword |
Code | 400832 |
Severity | Error |
Message | Invalid authentication configuration. These parameters should be configured if parameter AuthType is set to rsa or project_rsa: User, RSAKeyFile |
Description | Invalid authentication configuration. These parameters should be configured if parameter AuthType is set to rsa or project_rsa: User, RSAKeyFile |
Code | 400833 |
Severity | Error |
Message | Invalid stream name: {0} |
Description | Invalid stream name: {0} |
Code | 400834 |
Severity | Error |
Message | Failed to get stream schema. |
Description | Failed to get stream schema. |
Code | 400835 |
Severity | Error |
Message | Failed to load module {0}. Please check if its class {1} is in the classpath. |
Description | Failed to load module {0}. Please check if its class {1} is in the classpath. |
Code | 400836 |
Severity | Error |
Message | Can not initialize I18N: |
Description | Can not initialize I18N: |
Code | 400837 |
Severity | Error |
Message | Can not localized message: |
Description | Can not localized message: |
Code | 400838 |
Severity | Error |
Message | Invalid error key provided. |
Description | Invalid error key provided. |
Code | 400839 |
Severity | Error |
Message | Can not get localized message: |
Description | Can not get localized message: |
Code | 400840 |
Severity | Error |
Message | Invalid error codes definition. |
Description | Invalid error codes definition. |
Code | 400841 |
Severity | Error |
Message | Fail to initialize the publisher processor. |
Description | Fail to initialize the publisher processor. |
Code | 400842 |
Severity | Error |
Message | The stream name is not configured. |
Description | The stream name is not configured. |
Code | 400843 |
Severity | Error |
Message | Fail to connect to ESP server. |
Description | Fail to connect to ESP server. |
Code | 400844 |
Severity | Error |
Message | The ESP subscriber is not configured. |
Description | The ESP subscriber is not configured. |
Code | 400845 |
Severity | Error |
Message | The column mapping configured in stream {0} is wrong: {1} |
Description | The column mapping configured in stream {0} is wrong: {1} |
Code | 400846 |
Severity | Error |
Message | And invalid column is configured in the column mapping of {0}:{1} |
Description | And invalid column is configured in the column mapping of {0}:{1} |
Code | 400847 |
Severity | Error |
Message | The column mappings configured have confliction! {0} [{1}] |
Description | The column mappings configured have confliction! {0} [{1}] |
Code | 400848 |
Severity | Error |
Message | The column mapping configured does not match the schema of stream {0}. |
Description | The column mapping configured does not match the schema of stream {0}. |
Code | 400849 |
Severity | Error |
Message | Error to create {0}. |
Description | Error to create {0}. |
Code | 400850 |
Severity | Error |
Message | The ESP project to be connected is invalid! {0} |
Description | The ESP project to be connected is invalid! {0} |
Code | 400851 |
Severity | Error |
Message | The module {0} is invalid: its parameters node {1} cannot be found. |
Description | The module {0} is invalid: its parameters node {1} cannot be found. |
Code | 400852 |
Severity | Error |
Message | Fail to stop the running adapter. The running adapter is started by another user and current user has no privillege to stop it. |
Description | Fail to stop the running adapter. The running adapter is started by another user and current user has no privillege to stop it. |
Code | 401001 |
Severity | Error |
Message | File {0} doesn't exist. |
Description | File {0} doesn't exist. |
Code | 401002 |
Severity | Error |
Message | Path {0} doesn't exist. |
Description | Path {0} doesn't exist. |
Code | 401003 |
Severity | Error |
Message | File {0} can't be read. |
Description | File {0} can't be read. |
Code | 401004 |
Severity | Error |
Message | File {0} can't be written. |
Description | File {0} can't be written. |
Code | 401005 |
Severity | Error |
Message | {0} is a path, file expected. |
Description | {0} is a path, file expected. |
Code | 401006 |
Severity | Error |
Message | Failed to access file {0}. |
Description | Failed to access file {0}. |
Code | 401007 |
Severity | Error |
Message | Failed to create path {0}. |
Description | Failed to create path {0}. |
Code | 401008 |
Severity | Warning |
Message | Invalid input buffer size, will use default. |
Description | Invalid input buffer size, will use default. |
Code | 401009 |
Severity | Error |
Message | Error accessing file {0}. |
Description | Error accessing file {0}. |
Code | 401010 |
Severity | Error |
Message | Wrong file transporter {0} parameter: {1}. |
Description | Wrong file transporter {0} parameter: {1}. |
Code | 401101 |
Severity | Error |
Message | Ftp cannot connect. |
Description | Ftp cannot connect. |
Code | 401102 |
Severity | Error |
Message | Syntax error in parameters or arguments. |
Description | Syntax error in parameters or arguments. |
Code | 401103 |
Severity | Error |
Message | Invalid username or password. |
Description | Invalid username or password. |
Code | 401104 |
Severity | Error |
Message | FTP server refused connection. |
Description | FTP server refused connection. |
Code | 401105 |
Severity | Error |
Message | Cannot find this file. |
Description | Cannot find this file. |
Code | 401106 |
Severity | Error |
Message | Create directory faild. |
Description | Create directory faild. |
Code | 401107 |
Severity | Error |
Message | No permission to upload file. |
Description | No permission to upload file. |
Code | 401301 |
Severity | Alert |
Message | JMS Transporter create factory failed. |
Description | JMS Transporter create factory failed. |
Code | 401302 |
Severity | Alert |
Message | JMS Transporter failed to connect with JMS server. |
Description | JMS Transporter failed to connect with JMS server. |
Code | 401302 |
Severity | Error |
Message | Get DB connection failed. |
Description | Get DB connection failed. |
Code | 401303 |
Severity | Error |
Message | Please add query or table parameter. |
Description | Please add query or table parameter. |
Code | 401303 |
Severity | Error |
Message | JMS Transporter failed to close the conneciton. |
Description | JMS Transporter failed to close the conneciton. |
Code | 401304 |
Severity | Error |
Message | Parse date failed. |
Description | Parse date failed. |
Code | 401304 |
Severity | Error |
Message | JMS_Transporter failed to receive message. |
Description | JMS_Transporter failed to receive message. |
Code | 401304 |
Severity | Error |
Message | JMS Transporter failed to send message. |
Description | JMS Transporter failed to send message. |
Code | 401305 |
Severity | Error |
Message | Parse big date failed. |
Description | Parse big date failed. |
Code | 401305 |
Severity | Error |
Message | ClientID and SubscribeName are necessary for persistent subscription. |
Description | ClientID and SubscribeName are necessary for persistent subscription. |
Code | 401306 |
Severity | Error |
Message | JMS Transporter is expected a TextMessage, received {0}. |
Description | JMS Transporter is expected a TextMessage, received {0}. |
Code | 401307 |
Severity | Error |
Message | JMS Transporter is expecting an ObjectMessage, received {0}. |
Description | JMS Transporter is expecting an ObjectMessage, received {0}. |
Code | 401308 |
Severity | Error |
Message | This JMS Transporter does not support discovery. |
Description | Only JMS Transporter with message type of TEXT can support discovery. |
Code | 401309 |
Severity | Error |
Message | JMS Connection is not initialzied yet. |
Description | JMS Connection is not initialzied yet. |
Code | 401310 |
Severity | Error |
Message | JMS Transporter failed to browser message |
Description | JMS Transporter failed to browser message |
Code | 402001 |
Severity | Error |
Message | CSV line contains too few fields. |
Description | CSV line contains too few fields. |
Code | 402001 |
Severity | Error |
Message | XMLLIST Formatter received a null data. |
Description | XMLLIST Formatter received a null data. |
Code | 402002 |
Severity | Error |
Message | CSV line contains {0} fields, expected {1}. |
Description | CSV line contains {0} fields, expected {1}. |
Code | 402002 |
Severity | Warning |
Message | XMLLIST Formatter met an unsupported data type: {0}. |
Description | XMLLIST Formatter met an unsupported data type: {0}. |
Code | 402003 |
Severity | Error |
Message | CSV Formatter received a null data. |
Description | CSV Formatter received a null data. |
Code | 402004 |
Severity | Warning |
Message | CSV Formatter met an unsupported data type: {0}. |
Description | CSV Formatter met an unsupported data type: {0}. |
Code | 402101 |
Severity | Alert |
Message | XMLLIST Formatter met an invalid line: {0} |
Description | XMLLIST Formatter met an invalid line: {0} |
Code | 402260 |
Severity | Error |
Message | The XPATH expression {0} is invalid. |
Description | The XPATH expression shall follow XPATH specification. |
Code | 402260 |
Severity | Error |
Message | The number of mapping columns in adapter configuration are not matched with ESP side. |
Description | The number of mapping columns in adapter configuration shall be equal with the column number of ESP side. |
Code | 402261 |
Severity | Error |
Message | XML Formatter met an unsupported data type: {0}. |
Description | The ESP SDK data type may not be included in this formatter implementation. |
Code | 402262 |
Severity | Error |
Message | The XML element for column {0} is NULL. |
Description | This may be due to invalid XPath expression. If the XPath expression begins with the last XML element appearing in the 'XmlElemMappingRowPattern', please add the forward slash '/' before it. |
Code | 402263 |
Severity | Error |
Message | Schema compilation errors. |
Description | Schema compilation errors. |
Code | 402264 |
Severity | Error |
Message | No Schemas to process. |
Description | No Schemas to process. |
Code | 402265 |
Severity | Error |
Message | Could not find a global element with name {0} in your .xsd file. |
Description | Could not find the global element with name in your .xsd file. |
Code | 402266 |
Severity | Error |
Message | It is not simple type. |
Description | It is not simple type. |
Code | 402267 |
Severity | Error |
Message | It is union type. |
Description | It is union type. |
Code | 402268 |
Severity | Error |
Message | Could not find valid XML element in the xpath expression {0} |
Description | Could not find valid XML element in the xpath expression. |
Code | 402269 |
Severity | Error |
Message | This shall be an element node to create the element(attribute). |
Description | This shall be an element node to create the element(attribute). |
Code | 402269 |
Severity | Error |
Message | The node has no wildcard attribture. |
Description | The node has no wildcard attribture. |
Code | 402269 |
Severity | Error |
Message | The node has no wildcard element. |
Description | The node has no wildcard element. |
Code | 402269 |
Severity | Error |
Message | Only support to replace the wildcard with the element(attribute) from the same namespace with the node. |
Description | Only support to replace the wildcard with the element(attribute) from the same namespace with the node. |
Code | 402270 |
Severity | Error |
Message | XML document Formatter received a null data. |
Description | XML document Formatter received a null data. |
Code | 402291 |
Severity | Error |
Message | The max column index(value:{0}) for the output row exceeds the max column index(value:{1}) for the input row |
Description | The probable reason is that the value of colsmapping for publisher is not set properly |
Code | 402302 |
Severity | Error |
Message | The stream name {0} column mapping configured invalid. |
Description | The stream name {0} column mapping configured invalid. |
Code | 402303 |
Severity | Error |
Message | Can not get value from JSON path. |
Description | Can not get value from JSON path. |
Code | 402304 |
Severity | Error |
Message | ESP data convert exception. |
Description | ESP data convert exception. |
Code | 402305 |
Severity | Error |
Message | Invalid rootpath, please check the JSON rootpath. |
Description | Invalid rootpath, please check the JSON rootpath. |
Code | 402306 |
Severity | Error |
Message | JSON Formatter received a null data. |
Description | JSON Formatter received a null data. |
Code | 402501 |
Severity | Error |
Message | Please config the host. |
Description | Please config the host. |
Code | 402502 |
Severity | Error |
Message | Please config the port. |
Description | Please config the port. |
Code | 402503 |
Severity | Error |
Message | Please config the blocksize. |
Description | Please config the blocksize. |
Code | 402601 |
Severity | Error |
Message | Encrypted password need {0} parameter. |
Description | Encrypted password need {0} parameter. |