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 equal to 0 |
Description |
Invalid refreshInterval value '{0}' specified for connection '{1}'. Value must a positive number greater than 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 subscirbe for stream '{0}' |
Description |
Can not subscirbe 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 executing "sars_start |
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 creating RepClient session |
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 |
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 |
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 vaid 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 |
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 |