Miscellaneous Error Messages
| Code | 130001 |
| Severity | Critical |
| Message | RowDefinition({0}): empty column name |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 130002 |
| Severity | Critical |
| Message | RowDefinition({0}): unknown type '{1}' |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 130003 |
| Severity | Critical |
| Message | RowDefinition({0}): unexpected '{1}' in place of literal KEY |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 130004 |
| Severity | Critical |
| Message | RowDefinition({0}): unexpected character '{1}' |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 130005 |
| Severity | Critical |
| Message | RowDefinition({0})::pack(): internal error, {1} values passed, {2} expected. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 131000 |
| Severity | Critical |
| Message | {0}({1})::initInputs() cannot find input stream {2} |
| Description | Probably the name of an input stream is mistyped. Check and correct the model. |
| Code | 131004 |
| Severity | Critical |
| Message | {0}({1})::init() Configuration file contains a cycle of streams involving this stream. |
| Description | In CCL Prime the streams may not be connected in a loop. Check and correct the model. |
| Code | 131005 |
| Severity | Critical |
| Message | Stream({0})::initStream() -- thread start failed when starting data retention |
| Description | The limit of threads per process is probably exhausted. Consult your system administrator. |
| Code | 131006 |
| Severity | Debug |
| Message | {0}({1})::handleEvent() -- exit requested, no more feeders. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 131007 |
| Severity | Debug |
| Message | {0}({1})::handleEvent() -- exit requested {2} feeders still running. |
| Description | The exit request is propagated through the model from the source streams to the derived streams. Each stream must collect the exit requests from all inputs before shutting down. This message provides the information on the progress of shutdown. |
| Code | 131008 |
| Severity | Info |
| Message | {0}({1})::run() -- starting event queue Stream. |
| Description | Information about the internal stages of initialization. |
| Code | 131009 |
| Severity | Info |
| Message | {0}({1})::run() -- starting thread with thread id {2} |
| Description | Information about the internal stages of initialization. |
| Code | 131010 |
| Severity | Debug |
| Message | {0}({1})::run() -- sending completion notification to {2} |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 131011 |
| Severity | Debug |
| Message | {0}({1})::dumpXML() -- writing out records. |
| Description | If the stream has tile attribute "ofile", its contents gets automatically dumped into an XML file when the model exits. |
| Code | 131012 |
| Severity | Error |
| Message | {0}({1}): Divide-by-zero.{2} |
| Description | An illegal calculation has happened in the model. Check the model logic and received data. |
| Code | 131013 |
| Severity | Error |
| Message | {0}({1}): Floating-point exception.{2} |
| Description | An illegal calculation has happened in the model. Check the model logic and received data. |
| Code | 131014 |
| Severity | Critical |
| Message | {0}({1}): Illegal record operation {2} in 0x{3} |
| Description | An illegal calculation has happened in the model. Check the model logic and received data. |
| Code | 131015 |
| Severity | Info |
| Message | {0}({1})::regenerate() -- regenerating stream. |
| Description | When the model starts, it regenerates the contents of the streams to a consistent state, based on the contents of the persistent stores. After a dynamic modification, the affected streams are also regenerated. |
| Code | 131016 |
| Severity | Info |
| Message | {0}({1})::regenerate() -- done regenerating stream. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 131017 |
| Severity | Info |
| Message | {0}({1})::stats: msec {2} qsize {3} rtrans {4} ttrans {5} rops {6} tops {7} streamsize {8} cpu {9}% |
| Description | The periodic statistics about the stream, a subset of those provided by sp_monitor. The Sybase Event Stream Processor must be started with option -t to enable the monitoring of statistics. The values: msec - time since the last report, in milliseconds; qsize - current queue size; rtrans - number of transactions processed since the last update; ttrans - total number of transactions processed; rops - number of rows processed since the last update; ttrans - tops number of rows processed; streamsize - current number of rows in stream's store; cpu - CPU usage since the last report, percent. |
| Code | 131018 |
| Severity | Info |
| Message | {0}({1})::signature is {2} |
| Description | It is an informational message. The signature is like a checksum of the stream's schema. The signature is checked when loading data from the persistent stores to make sure that the schema did not change. |
| Code | 131019 |
| Severity | Debug |
| Message | {0}({1})::Inject orphaned records, opCode: {2}, record: {3} |
| Description | The orphaned records are the source stream records that have been written into the LogStore but not checkpointed yet. On the Sybase Event Stream Processor restart, it is played back to restore the state. |
| Code | 131020 |
| Severity | Debug |
| Message | {0}({1})::Registered a cluster export stream, total export streams: {2} |
| Description | Another node of the cluster has subscribed to this stream. |
| Code | 131021 |
| Severity | Debug |
| Message | {0}({1})::Unregistered a cluster export stream, total export streams: {2} |
| Description | Another node of the cluster has unsubscribed from this stream. |
| Code | 131022 |
| Severity | Critical |
| Message | {0}({1}):: stream references a store <{2}> that is not in the running module. |
| Description | A cluster node must be self-contained, with all streams and stores wrapped inside this node's Module. Check and correct the model. |
| Code | 131023 |
| Severity | Debug |
| Message | {0}({1}):: exit posted to all subscribers. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 131024 |
| Severity | Critical |
| Message | {0}({1})::{2} received invalid opcode: {3} on record, exiting. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 131025 |
| Severity | Critical |
| Message | {0}({1})::initMetadata() both expiryTime and expiryField must be specified in config file. |
| Description | The expiry-related attributes must be either both present or absent. Check and correct the model. |
| Code | 131026 |
| Severity | Critical |
| Message | {0}({1})::initMetadata() expiryField must be valid column name |
| Description | The attribute "expiryField" must identify an integer column in the data. Check and correct the model. |
| Code | 131027 |
| Severity | Critical |
| Message | {0}({1})::initMetadata() expiryField must be an integer column |
| Description | The attribute "expiryField" must identify an integer column in the data. Check and correct the model. |
| Code | 131030 |
| Severity | Critical |
| Message | {0}({1})::initMetadata() expiryTimeField must be valid column name |
| Description | The attribute "expiryTimeField" must identify a date column in the data. Check and correct the model. |
| Code | 131031 |
| Severity | Critical |
| Message | {0}({1})::initMetadata() expiryTimeField's type must be "date" |
| Description | The attribute "expiryTimeField" must identify a date column in the data. Check and correct the model. |
| Code | 131032 |
| Severity | Info |
| Message | {0}({1})::pushToHotSpare() _gatewayClient is NULL, creating new object. |
| Description | In a Hot Spare cluster configuration, the connection to the secondary Sybase Event Stream Processor is created when the first data record comes in. The connection is also re-established if it was lost. |
| Code | 131033 |
| Severity | Warning |
| Message | {0}({1})::pushToHotSpare() _gatewayClient unable to open connection, disabling redundancy. |
| Description | If a Hot Spare cluster configuration can not establish connection to the secondary Sybase Event Stream Processor, it reverts to running in the non-redundant configuration. Check whether the secondary Sybase Event Stream Processor is running. |
| Code | 131034 |
| Severity | Warning |
| Message | {0}({1})::pushToHotSpare() _gatewayClient authentication failed, disabling redundancy. |
| Description | If a Hot Spare cluster configuration can not establish connection to the secondary Sybase Event Stream Processor, it reverts to running in the non-redundant configuration. Check the credentials specified with the command-line option -a or -K. |
| Code | 131035 |
| Severity | Warning |
| Message | {0}({1})::pushToHotSpare() _gatewayClient send message failed, disabling redundancy. |
| Description | If a Hot Spare cluster configuration can not establish connection to the secondary Sybase Event Stream Processor, it reverts to running in the non-redundant configuration. Check whether the secondary Sybase Event Stream Processor is running. |
| Code | 131036 |
| Severity | Critical |
| Message | {0}({1})::Bad access control specification: '{2}' is not a pair of strings separated by ':'. |
| Description | The attribute "restrictAccess" has been misformatted. It must contain a space-separated list of colon-separated pairs. Check the model and correct it. |
| Code | 131037 |
| Severity | Critical |
| Message | {0}({1})::Bad access control specification: unknown access control type in pair '{2}'. |
| Description | The attribute "restrictAccess" has been misformatted. It must contain a space-separated list of colon-separated pairs. Check the model and correct it. |
| Code | 131038 |
| Severity | Warning |
| Message | Stream(): error occurred in computation of row. |
| Description | An illegal calculation has happened in the model. Check the model logic and received data. |
| Code | 131039 |
| Severity | Info |
| Message | {0}({1}): Collecting statistics (this could take awhile). |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 131040 |
| Severity | Info |
| Message | {0}({1}): Memory usage: {2} bytes in {3} records. |
| Description | Statistics about the amount of memory used by the stream. This does not include any internal indexing overhead. This information can be used to plan the LogStore sizes for the future runs of the Sybase Event Stream Processor. |
| Code | 131041 |
| Severity | Critical |
| Message | {0}({1}):: can not find store {2} |
| Description | The store name specified for this stream is not present in the model. Check and correct the model. |
| Code | 131042 |
| Severity | Critical |
| Message | {0}({1})::initMetadata() expiryTime value '{2}' is not a valid integer >=0. |
| Description | The attribute "expiryTime" must specify the expiry step in seconds. Check and correct the model. |
| Code | 131043 |
| Severity | Critical |
| Message | {0}({1})::initMetadata() expiryMaxValue '{2}' is not a valid integer >=0. |
| Description | The attribute "expiryMaxValue" specifies the maximum number of expiry steps that can be done on a record. Check and correct the model. |
| Code | 131044 |
| Severity | Critical |
| Message | {0}({1})::wipeout() -- started wiping out the old contents. |
| Description | After a dynamic modification, if the data in the stream is about to be regenerated, the old data must be wiped out first. |
| Code | 131045 |
| Severity | Critical |
| Message | {0}({1})::wipeout() -- completed. |
| Description | After a dynamic modification, if the data in the stream is about to be regenerated, the old data must be wiped out first. |
| Code | 131046 |
| Severity | Critical |
| Message | {0}({1}): received an unexpected input regeneration report. |
| Description | The regeneration may happen only at certain moments in the life of the stream: either when the model gets started or after a dynamic modification. A regeneration request at any other time means that something went wrong in the Sybase Event Stream Processor. Contact the Sybase support. |
| Code | 131047 |
| Severity | Critical |
| Message | {0}({1}): regeneration completed |
| Description | Information about the internal stages of initialization. |
| Code | 131048 |
| Severity | Critical |
| Message | {0}({1}): Join/Flex do not currently support Input Windows. |
| Description | JoinStreams and FlexStreams do not support InputWindows. A FlexStream may use eventCaches instead, achieving higher efficiency as well. A ComputeStream with an InputWindow may be added before either FlexStream or JoinStream. Check and correct the model. |
| Code | 131049 |
| Severity | Critical |
| Message | {0}({1}): specifying an input stream for an Input Window of a source stream is not allowed. |
| Description | Since the Source Stream receives data directly from the outside sources, its InputWindow may act only on this data. Check and correct the model. |
| Code | 131050 |
| Severity | Critical |
| Message | {0}({1}): a Source Stream can only have one Input Window. |
| Description | Since the Source Stream receives data directly from the outside sources, its InputWindow may act only on this data. Check and correct the model. |
| Code | 131051 |
| Severity | Critical |
| Message | {0}({1}): an Input Window on a derived stream must have a stream attribute set to one of its input streams. |
| Description | An InputWindow is associated with one input stream, no more than one InputWindow per input stream. The "stream" attribute of the InputWindow must identify this stream. Check and correct the model. |
| Code | 131052 |
| Severity | Critical |
| Message | {0}({1}): multiple Input Windows on a derived stream for the same input stream is illegal. |
| Description | An InputWindow is associated with one input stream, no more than one InputWindow per input stream. The "stream" attribute of the InputWindow must identify this stream. Check and correct the model. |
| Code | 131053 |
| Severity | Critical |
| Message | {0}({1}): the stream attribute of an Input Window does not match any input streams. |
| Description | An InputWindow is associated with one input stream, no more than one InputWindow per input stream. The "stream" attribute of the InputWindow must identify this stream. Check and correct the model. |
| Code | 131054 |
| Severity | Critical |
| Message | {0}({1}): for logstores, only SourceStreams and CopyStreams may specify Input Windows. |
| Description | The LogStore consistency relies on the input being injected only in the source streams or copy streams of a cluster. Since the InputWindows produce the deletion records in place, it may not be used on the streams with data in LogStores, unless these streams mare one of these cases. Check and correct the model. |
| Code | 131055 |
| Severity | Critical |
| Message | {0}({1}): dynamic modification of Streams with Input Window is not permitted in 'noregen' mode. |
| Description | The option "noregen" bypasses the regeneration after the dynamic modification. It expects that the user knows that this would not introduce a major discrepancy in the data or accept such a discrepancy, as a tradeoff for a faster modification. The InputWindows have major issues if the data is not properly regenerated, so any streams with InputWindows may not be modified in the "noregen" mode. Retry the modification without the option "noregen" (or with the explicit option "regen"). |
| Code | 131056 |
| Severity | Critical |
| Message | {0}({1}): Insert-only streams (SourceStream) may not specify an Input Window. |
| Description | Since the InputWindows generate the delete records, any stream with them is no longer insert-only. However for the InputWindows to work correctly, the data coming into them must be insert-only. Check and correct the model. |
| Code | 131057 |
| Severity | Info |
| Message | {0}({1}): will be recompiled, because InsertOnly state change has propagated. |
| Description | Informational message. On a dynamic modification, changing the InsertOnly state of one stream may propagate to the streams derived from it. The streams that have InsertOnly state changed must be recompiled, even though they had no explicit changes in them. This is detected and handled automatically. |
| Code | 131058 |
| Severity | Critical |
| Message | {0}({1}): InsertOnly state change has propagated, not allowed without 'regen' option. |
| Description | The option "noregen" bypasses the regeneration after the dynamic modification. It expects that the user knows that this would not introduce a major discrepancy in the data or accepts such a discrepancy, as a tradeoff for a faster modification. The InsertOnly mode change without regeneration may cause major issues in the stream's logic, so this combination is not allowed. Retry the modification without the option "noregen" (or with the explicit option "regen"). |
| Code | 131059 |
| Severity | Critical |
| Message | {0}({1}): attribute "{2}" value is incompatible in the old and new configuration. |
| Description | See the Administrator's Guide for the information on the Dynamic Services. The incompatible modifications require the whole stream ot be destroyed and re-created with the same name but possibly a different schema. Since it may be too disruptive, by default (or with option "compat") such dynamic modifications are not allowed, to prevent an accidental disruption. This message identifies the incompatible changes in the model. If the resulting modification gets refused, either correct the new model to prevent the incompatible changes or do the modification with the option "nocompat". |
| Code | 131060 |
| Severity | Critical |
| Message | {0}({1}): input stream count can not be changed, is: {2}, requested: {3} |
| Description | Obsolete. |
| Code | 131061 |
| Severity | Warning |
| Message | {0}({1}): Previous incarnation {2}({3}) had an incompatible rowdef, data will be discarded. |
| Description | A source stream, unlike the derived streams, can not have its data regenerated. If a source stream is modified while keeping its schema the same, or if a conversion model is provided to convert the data, the data may be moved from the old model. But otherwise on an incompatible modification, the data can not be moved and is discarded. |
| Code | 131062 |
| Severity | Info |
| Message | {0}({1}): moving the data from the previous incarnation. |
| Description | If a source stream is modified in an incompatible way while keeping its schema the same, the data will be moved from the old model. |
| Code | 131063 |
| Severity | Critical |
| Message | {0}({1}): the data move has failed, discarding data. |
| Description | If a source stream is modified in an incompatible way while keeping its schema the same, the data will be moved from the old model. However the new model may specify a different primary key. If the old data do not fit the new unique key, the move is abandoned and data discarded. |
| Code | 131064 |
| Severity | Critical |
| Message | {0}({1}): can not set {2}({3}) as data source, row definitions or keys differ. |
| Description | When using a conversion model, at the points where the data enters and leaves the conversion model, the stream schema must be the same to transfer the data between the models. Check and correct the conversion model. |
| Code | 131065 |
| Severity | Critical |
| Message | {0}({1}): a non-source stream can not source data from {2}({3}). |
| Description | A conversion model may receive its data only in its source streams. It may provide data only for the source streams of the new model. Check and correct the conversion model. |
| Code | 131066 |
| Severity | Info |
| Message | {0}({1}): sourcing the data from {2}({3}). |
| Description | A conversion model has been specified, and this message informs of the connection points between the models. |
| Code | 131067 |
| Severity | Info |
| Message | {0}({1}): added breakpoint {2} |
| Description | Informational message about a breakpoint being added. |
| Code | 131068 |
| Severity | Info |
| Message | {0}({1}): deleted breakpoint {2} |
| Description | It is informational message about a breakpoint being deleted. |
| Code | 131069 |
| Severity | Info |
| Message | {0}({1}): triggered breakpoint {2} |
| Description | It is informational message about a breakpoint being triggered. The model is paused. |
| Code | 131070 |
| Severity | Info |
| Message | {0}({1}): triggered a break on exception. |
| Description | It is informational message about an exception in a stream triggering the model pause. |
| Code | 131071 |
| Severity | Warning |
| Message | {0}({1})::expiryTimeField is null; defaulting to the current time for this record. |
| Description | The attribute "expiryTimeField" may be used to specify the column in a row that carries the information about the logical last modification time of the row. The expiry is counted started from that time instead of the real time when the row was last updated in the stream. If the value in this column is NULL, the logic reverts to using the real time. If this is not intended, check the input data and the model for the reasons why that NULL appeared. |
| Code | 131072 |
| Severity | Critical |
| Message | {0}({1}): {2} {3} is invalid: {4} |
| Description | The Connection could not be created. The most likely reason is the shared library for this connection type can not be loaded. Examine the preceding messages for the possible reasons that led to it. Check your configuration. |
| Code | 131073 |
| Severity | Info |
| Message | {0}({1})::processService(): received START_SYNC when not empty |
| Description | It is an informational message. A connector or other source started the resynchronization of the stream contents, replacing the whole old contents with the new ones. |
| Code | 131074 |
| Severity | Info |
| Message | {0}({1})::processService(): END_SYNC {2} records of {3} differ, posting diffs to sync stream. |
| Description | It is an informational message. A connector or other source completed the resynchronization of the stream contents, replacing the whole old contents with the new one. The stream compares the new contents with the old one, and passes through only the differences. The message provides the summary of the differences. |
| Code | 131075 |
| Severity | Debug |
| Message | {0}({1})::processService(): record diff: opCode: {2}, record: {3} |
| Description | Debugging message. Provides information about the ongoing stream resynchronization. |
| Code | 131076 |
| Severity | Error |
| Message | {0}({1}): Error in running initializers; see next message for details |
| Description | The initialization of the global or local variables has failed. The model does not start. |
| Code | 131077 |
| Severity | Debug |
| Message | {0}({1}):: waiting for connectors to finish before exiting. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 131078 |
| Severity | Critical |
| Message | {0}({1}): illegal stream; no keys defined. |
| Description | A stream must have at least one key field defined. Check and correct the model. |
| Code | 131079 |
| Severity | Info |
| Message | {0}({1})::dynamic changes with InConnection running are treated as incompatible |
| Description | If a source stream has a running InConnection, changing it in place is unsafe. Instead the stream will be re-created from scratch and the input connection will be restarted. |
| Code | 131080 |
| Severity | Info |
| Message | {0}({1})::dynamic changes in 'noregen' mode with local variables are treated as incompatible |
| Description | The option "noregen" bypasses the regeneration after the dynamic modification. It expects that the user knows this would not introduce a major discrepancy in the data or accepts such a discrepancy, as a tradeoff for a faster modification. This cannot be safely applied to the streams with local variables, so any changes to these streams are treated as incompatible, effectively preventing them from being done in the "noregen" mode. |
| Code | 131081 |
| Severity | Critical |
| Message | {0}({1}): illegal stream; duplicate column '{2}'. |
| Description | The column names in a stream must be unique. Check and correct the model. |
| Code | 131082 |
| Severity | Error |
| Message | {0}({1}): Invalid function arguments.{2} |
| Description | Function was invoked with invalid argumements in the model. Check the model logic and received data. |
| Code | 131083 |
| Severity | Error |
| Message | {0}({1}): Overflow.{2} |
| Description | Arithmetic overflow in computation of invoked function. Received data is inappropriate for computation. |
| Code | 131084 |
| Severity | Debug |
| Message | {0}({1}):: waiting for distributed subscribers to disconnect before exiting. |
| Description | In a clustered model, all the nodes wait for the other nodes to process the exit instructions and disconnect. This makes sure that all data has been processed by the whole model. |
| Code | 132000 |
| Severity | Error |
| Message | StreamExport({0}):: dropped a subscriber (via processed message). |
| Description | Informational message that a client subscribed to this stream has disconnected. |
| Code | 132001 |
| Severity | Warning |
| Message | StreamExport::Got a {START,END,RECORD} or BASE data for an unknown client. |
| Description | A self-testing assertion in the Sybase Event Stream Processor has failed. However this is a minor point. |
| Code | 132002 |
| Severity | Warning |
| Message | StreamExport::Got an unknown message type. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 132003 |
| Severity | Info |
| Message | StreamExport({0})::put() message queue at 99% of limit. |
| Description | If any of this stream's subscribers is slow, that subscriber's gateway queue will fill and then the export queue of this stream will start filling, until it becomes full. Check the clients and sp_monitor data to locate the slow client. |
| Code | 132004 |
| Severity | Info |
| Message | StreamExport({0})::put() max(size(all seen blocks)) now: {1} |
| Description | Information about the biggest transaction size produced by this stream. |
| Code | 132005 |
| Severity | Info |
| Message | StreamExport({0})::put() message queue dropped below 51% of limit. |
| Description | If any of this stream's subscribers is slow, that subscriber's gateway queue will fill and then the export queue of this stream will start filling, until it becomes full. This message means that the client continued consuming the data, and the operation is returning to normal. |
| Code | 134000 |
| Severity | Critical |
| Message | {0}({1})::UnionStream requires at least one input stream. |
| Description | The UnionStream needs one or more input streams. Check and correct the model. |
| Code | 134001 |
| Severity | Critical |
| Message | {0}({1})::All inputs must have matching fields and field types. |
| Description | A UnionStream merges the records with the same schema from multiple streams, including the exact same primary key. It can not handle the records with different schemas. Check and correct the model. |
| Code | 134002 |
| Severity | Critical |
| Message | {0}({1})::All inputs must have the same number of key columns as the UnionStream. |
| Description | A UnionStream merges the records with the same schema from multiple streams, including the exact same primary key. It can not handle the records with different schemas. Check and correct the model. |
| Code | 134003 |
| Severity | Critical |
| Message | {0}({1})::The key columns of the inputs must match that of the UnionStream. |
| Description | A UnionStream merges the records with the same schema from multiple streams, including the exact same primary key. It can not handle the records with different schemas. Check and correct the model. |
| Code | 135000 |
| Severity | Critical |
| Message | Platform()::main() -- fatal error in thread {0}; aborting. |
| Description | Some major crash has happened in the Sybase Event Stream Processor. Ideally, this should never happen. If it happens, collect the log file, the core dump and the Sybase Event Stream Processor binaries and contact the Sybase support. If you can provide a way to reproduce this crash, preferably with a smaller model and data set, it would be very helpful and lead to a quicker fix. |
| Code | 135001 |
| Severity | Critical |
| Message | Platform::main() Could not initialize SSL layer. |
| Description | The SSL can not be initialized. Probably there is some issue with the SSL key files specified in the option -e. Check whether the path exists and whether the permissions are correct. If the path is relative, check that the Sybase Event Stream Processor's current directory is what you think it is. |
| Code | 135002 |
| Severity | Alert |
| Message | Platform::main() Could not find the specified project ccx file '{0}'. |
| Description | The project ccx file specified in the option -f can not be read. Check whether the path exists and whether the permissions are correct. If the path is relative, check that the Sybase Event Stream Processor's current directory is what you think it is. |
| Code | 135003 |
| Severity | Critical |
| Message | Platform::main() Project ccx file '{0}' is not a regular file. |
| Description | The project ccx file specified in the option -f must be a regular file, not a pipe or device or directory. |
| Code | 135004 |
| Severity | Info |
| Message | Platform()::main() -- loading project ccx file '{0}'. |
| Description | Information about the internal stages of initialization. |
| Code | 135005 |
| Severity | Warning |
| Message | Platform()::asap_badrec_init() -- could not open bad records file'{0}' for writing. |
| Description | The bad records file specified in the option -B can not be opened for writing. Check whether the path exists and whether the permissions are correct. If the path is relative, check that the Sybase Event Stream Processor's current directory is what you think it is. |
| Code | 135006 |
| Severity | Critical |
| Message | Platform::main() -- port {0} for SQL interface is outside valid range 0<= p < 2^16. |
| Description | The TCP protocol allows 16 bits for the port number. Check and correct the argument to the option -q. |
| Code | 135007 |
| Severity | Critical |
| Message | Platform::main() -- port {0} for Command and Control interface is outside valid range 0<= p < 2^16. |
| Description | The TCP protocol allows 16 bits for the port number. Check and correct the argument to the option -c. |
| Code | 135008 |
| Severity | Info |
| Message | Platform::main() -- now running as daemon, old pid: {0}, current pid: {1} |
| Description | Informational message that the daemonization succeeded. |
| Code | 135009 |
| Severity | Critical |
| Message | Platform::main() -- Error parsing project ccx file '{0}': the ccx file does not match the schema. Please see the preceding messages. |
| Description | The XML parser has found a syntax error in the project ccx file. The detailed information about the kind and location of the error should be reported in the preceding messages. Check and correct the model. |
| Code | 135010 |
| Severity | Critical |
| Message | Platform::main() -- Configuration file '{0}' is invalid, see the preceding messages for details. |
| Description | The exact error should be described in the preceding messages. |
| Code | 135011 |
| Severity | Critical |
| Message | Platform::main() -- -a <user>:<pass> specified, but {0} is NULL. |
| Description | The user name and password for the intra-cluster authentication mus not be empty. |
| Code | 135012 |
| Severity | Critical |
| Message | Platform::main() -- -K <user>:<privateKeyFile> specified, but {0} is NULL. |
| Description | The user name and key file name for the intra-cluster authentication must not be empty. |
| Code | 135013 |
| Severity | Critical |
| Message | Platform::main() -- spcrypt::getPrivateRSALoginMsg() failed, status={0}, errmsg={1} |
| Description | Obsolete. |
| Code | 135014 |
| Severity | Critical |
| Message | Platform::main() -- -H <host>:<port> (-H {0}) is invalid, check format. |
| Description | The format of the clustering option argument is invalid. |
| Code | 135015 |
| Severity | Critical |
| Message | Platform::main() -- -H <host>:<port> specified, but instance not HAC enabled, must specify -a, or -k/-K |
| Description | The option -H is used to enable the secondary Sybase Event Stream Processor in the Hot Spare cluster configuration to connect to the primary Sybase Event Stream Processor. However the user id and the password or key is also required to log in to the primary Sybase Event Stream Processor. Add the login information to the command line. |
| Code | 135016 |
| Severity | Critical |
| Message | Platform::main() -- HA/Cluster authentication options -a, -K and -G are mutually exclusive. |
| Description | Only one intra-cluster authentication method may be specified. It must match the method used by the other node(s) of the cluster. |
| Code | 135017 |
| Severity | Critical |
| Message | Platform::main() -- {0} |
| Description | The license file can not be read. Check that the ESP_HOME environment variable is properly set and exported, and the the file $ESP_HOME/etc/license.key is installed. |
| Code | 135018 |
| Severity | Critical |
| Message | Platform::main() -- {0} |
| Description | Information about the license expiration time. |
| Code | 135019 |
| Severity | Critical |
| Message | Platform::main() -- {0} |
| Description | The trial license has expired. Purchase a commercial license. |
| Code | 135020 |
| Severity | Critical |
| Message | Platform::main() -- the directory <{0}> must exist and have read/execute permissions. |
| Description | The RSA key directory can not be read. Check whether the path exists and whether the permissions are correct. If the path is relative, check that the Sybase Event Stream Processor's current directory is what you think it is. |
| Code | 135021 |
| Severity | Alert |
| Message | Platform::main() -- REVISION <{0}>, start timestamp (gmt): {1} |
| Description | Information about the Sybase Event Stream Processor build id. |
| Code | 135022 |
| Severity | Critical |
| Message | Platform::main() -- file <{0}> does not exist or is not readable. |
| Description | The Sybase Event Stream Processor has experienced an error when trying to read or write a file. Check whether the path exists and if the permissions are correct. If the path is relative, make sure that the Sybase Event Stream Processor's current directory is correct. |
| Code | 135023 |
| Severity | Critical |
| Message | Platform::main() -- file <{0}> does not exist or is not executable. |
| Description | The Sybase Event Stream Processor has experienced an error when trying to read or write a file. Check whether the path exists and if the permissions are correct. If the path is relative, make sure that the Sybase Event Stream Processor's current directory is correct. |
| Code | 135024 |
| Severity | Critical |
| Message | Platform::main() -- environment variable <{0}> is not set. |
| Description | Check that this environment variable is set and exported. |
| Code | 135025 |
| Severity | Critical |
| Message | Platform::main() -- general problem starting process <{0}> |
| Description | An auxiliary process can not be started. There may be multiple reasons for this. Check that the ESP_HOME environment variable is properly set and exported, and the the binary is present and has correct permissions. Also the system limit for the number of processes may be reached, consult your systems administrator. |
| Code | 135026 |
| Severity | Critical |
| Message | Platform::main() -- problem parsing argument list for sslwrap: <{0}> |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 135027 |
| Severity | Critical |
| Message | Platform::main() -- Badly formatted authentication database argument. |
| Description | The testing user database specified with option -A is misformatted. Check and correct your command line. |
| Code | 135028 |
| Severity | Info |
| Message | Platform::main() -- Authentication database from the command line will be used. |
| Description | The testing user database was specified specified on the command line with option -A. It will be used instead of the normal PAM authentication. |
| Code | 135029 |
| Severity | Info |
| Message | Platform::main() -- Stopping the Command Server, ignore the Socket Error messages. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 135030 |
| Severity | Info |
| Message | Platform::main() -- Waiting for the Command Server completion signal. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 135031 |
| Severity | Info |
| Message | Platform::main() -- Waiting for the Command Server thread to exit. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 135032 |
| Severity | Info |
| Message | Platform::main() -- Destroying the Command Server. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 135033 |
| Severity | Critical |
| Message | Platform::main() -- Authentication mechanism '-V {0}' is invalid. |
| Description | The option -V takes one of the arguments: none, pam, rsa, gssapi. Check your command line. |
| Code | 135034 |
| Severity | Critical |
| Message | Platform::main() -- Warning: invalid gateway port specified with '-g {0}'. |
| Description | The gateway port number must be a positive 16-bit number. |
| Code | 135035 |
| Severity | Critical |
| Message | Platform::main() -- Could not initialize Java VM: {0} |
| Description | The Java VM could not be initialized, the Sybase Event Stream Processor will try to proceed as is. Any functions using Java will be disabled or may crash. Java could be disabled by the option "-DJ". |
| Code | 135036 |
| Severity | Alert |
| Message | Platform::main() -- Starting initialization sequence. |
| Description | Information about the internal stages of initialization. |
| Code | 135037 |
| Severity | Info |
| Message | Platform::main() -- Stopping the Sybase Event Stream Processor Monitor. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 135038 |
| Severity | Critical |
| Message | Platform::main() -- authentication [{0}] mismatch with HA/Cluster authentication [{1}] |
| Description | The same authentication method must be used both between the cluster nodes and for the client connections. Check the command line options related to authentication. |
| Code | 135039 |
| Severity | Critical |
| Message | Platform::main() -- for rsa authentication both "-V rsa" and "-k <path to rsa keys>" must be specified |
| Description | The RSA authentication method requires the authentication keys. |
| Code | 135040 |
| Severity | Critical |
| Message | Platform::main() -- "-k <path to rsa keys>" may only be used when "-V rsa" is specified |
| Description | The RSA authentication keys can not be used with any other authentication method. |
| Code | 135041 |
| Severity | Critical |
| Message | Platform::main() -- the file <{0}> must exist and have read permissions. |
| Description | The Sybase Event Stream Processor has experienced an error when trying to read or write a file. Check whether the path exists and if the permissions are correct. If the path is relative, make sure that the Sybase Event Stream Processor's current directory is correct. |
| Code | 135042 |
| Severity | Critical |
| Message | Platform::main() -- limiting virtual memory to {0} megabytes. |
| Description | Information that the command line option -m was used to set the limit on the memory usage. |
| Code | 135043 |
| Severity | Critical |
| Message | Platform::main() -- port {0} for Gateway interface is outside valid range 0<= p < 2^16. |
| Description | The TCP protocol allows 16 bits for the port number. Check and correct the argument to the option -g. |
| Code | 135044 |
| Severity | Critical |
| Message | Platform::main() -- port {0} may not be used for both Command and for Gateway interface. |
| Description | The XMLRPC and gateway services may not share the same port. Check that the options -c and -g specify different values. |
| Code | 135045 |
| Severity | Critical |
| Message | Platform::main() -- port {0} may not be used for both Command and for SQL interface. |
| Description | The XMLRPC and ODBC services may not share the same port. Check that the options -c and -q specify different values. |
| Code | 135046 |
| Severity | Critical |
| Message | Platform::main() -- port {0} may not be used for both Gateway and for SQL interface. |
| Description | The gateway and ODBC services may not share the same port. Check that the options -g and -q specify different values. |
| Code | 135047 |
| Severity | Critical |
| Message | Platform::main() -- Sybase Event Stream Processor authentication is via <{0}>. |
| Description | Information about the selected authentication mode. |
| Code | 135048 |
| Severity | Critical |
| Message | Platform::main() -- Sybase Event Stream Processor is running without any authentication. |
| Description | Information about the selected no-authentication mode. |
| Code | 135049 |
| Severity | Critical |
| Message | Platform::main() -- Sybase Event Stream Processor parameter name is empty (value='{0}'). |
| Description | Empty name given for Sybase Event Stream Processor parameter. Correct syntax is: -p <param1_name>=<param1_value> -p <param2_name>=<param2_value> ... -p <paramN_name>=<paramN_value> |
| Code | 135050 |
| Severity | Critical |
| Message | Platform::main() -- Duplicate Sybase Event Stream Processor parameter value. Parameter '{0}' has already been set to '{1}'. |
| Description | Attempt to set the same Sybase Event Stream Processor parameter more than once. Correct syntax is: -p <param1_name>=<param1_value> -p <param2_name>=<param2_value> ... -p <paramN_name>=<paramN_value> |
| Code | 136000 |
| Severity | Debug |
| Message | {0}({1})::initialize() -- initializing. |
| Description | Information about the internal stages of initialization. |
| Code | 136001 |
| Severity | Debug |
| Message | {0}({1})::~{2}() -- disposing. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 136002 |
| Severity | Info |
| Message | {0}({1})::getIndex() -- setting up index '{2}'. |
| Description | Information about the internal stages of initialization. |
| Code | 136100 |
| Severity | Error |
| Message | Platform(): Attempt to assign to parameter {0} with value "{1}" failed: {2} |
| Description | Obsolete. |
| Code | 136101 |
| Severity | Error |
| Message | Platform(): Invalid type "{0}" specified for parameter {1}. |
| Description | MSG_PARAMETER_BAD_TYPE |
| Code | 136102 |
| Severity | Error |
| Message | Platform(): Default value '{0}' specified for parameter {1} could not be converted to type {2}: {3}. |
| Description | MSG_PARAMETER_BAD_DEFAULT |
| Code | 136103 |
| Severity | Error |
| Message | Platform(): Value '{0}' specified for parameter {1} could not be converted to {2}{3}. |
| Description | MSG_PARAMETER_BAD_VALUE |
| Code | 136200 |
| Severity | Warning |
| Message | CleanerMgr(schedule): cleaning scheduled for log: {0} |
| Description | An informational message that the specified LogStore was detected to be running short on free space and was scheduled for cleaning. |
| Code | 136201 |
| Severity | Info |
| Message | CleanerMgr(run): START cleaning dirty logstores ({0} secs - since last cleaning). |
| Description | Information that the store cleaning cycle has started. |
| Code | 136202 |
| Severity | Info |
| Message | CleanerMgr(run): END cleaning dirty logstores ({0} secs - to clean). |
| Description | Information that the store cleaning cycle has completed. |
| Code | 137000 |
| Severity | Info |
| Message | ExternalFeed(execute): [copystream:{0}] attempting connection to stream {1}({2}), from host {3} on port {4} |
| Description | Information about the intra-cluster connection to be established. |
| Code | 137002 |
| Severity | Warning |
| Message | ExternalFeed(loginXMLRPC): [copystream:{0}] fault authenticating, exception: {1} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137003 |
| Severity | Critical |
| Message | ExternalFeed(loginXMLRPC): [copystream:{0}] failed to authenticate, errno: {1} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137004 |
| Severity | Critical |
| Message | ExternalFeed(getGatewayPortXMLRPC): [copystream:{0}] fault obtaining gateway port, exception: {1} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137005 |
| Severity | Critical |
| Message | ExternalFeed(getGatewayPortXMLRPC): [copystream:{0}] failed to obtain gateway port, errno: {1} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137006 |
| Severity | Critical |
| Message | ExternalFeed(getStreamHandleXMLRPC): [copystream:{0}] fault obtaining stream handle({1}), exception: {2} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137007 |
| Severity | Critical |
| Message | ExternalFeed(getStreamHandleXMLRPC): [copystream:{0}] failed obtain stream handle({1}), errno: {2} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137008 |
| Severity | Info |
| Message | ExternalFeed(getData): [copystream:{0}] received an exit from feeding stream {1} |
| Description | Information the the feeding node of the cluster is exiting and sent an exit notification. |
| Code | 137011 |
| Severity | Critical |
| Message | ExternalFeed::({0}): [copystream:{1}] failure to authenticate, errno: {2} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137012 |
| Severity | Critical |
| Message | ExternalFeed::({0}): [copystream:{1}] general gateway exception: {2} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137013 |
| Severity | Critical |
| Message | ExternalFeed({0}): [copystream:{1}] failure to subscribe, errno: {2} |
| Description | The connection attempt to another node of the cluster has failed. Check the authentication information provided on the command line. If the model uses the "restrictAccess" attribute, check that it sets the correct permissions for the intra-cluster user id. |
| Code | 137014 |
| Severity | Info |
| Message | ExternalFeed(subscribeAndForward): [copystream:{0}] closing subscribe socket and exiting. |
| Description | Information that this cluster node is exiting and closing the connection to the other parts of the cluster. |
| Code | 137015 |
| Severity | Info |
| Message | ExternalFeed(execute): [copystream:{0}] from stream: {1}, main thread exiting. |
| Description | Information that this cluster node is exiting and closing the connection to the other parts of the cluster. |
| Code | 138000 |
| Severity | Critical |
| Message | Node(module:{0})::matches() actual host/port <{1}/{2}>, and node specified host/port <{3}/{4}> differ. |
| Description | The port specified for this cluster node in the model (as identified by the options -C and -M) and the port specified on the command line with option -c on the command line differ. They must be the same. |
| Code | 138001 |
| Severity | Critical |
| Message | Node(module:{0})::initialize(): module could not be found. |
| Description | The module specified with option -M is not present in the model. |
| Code | 138002 |
| Severity | Critical |
| Message | Cluster({0})::verify(): could not find module <{1}> |
| Description | The module specified with option -M is not present in the model. |
| Code | 138003 |
| Severity | Critical |
| Message | Node(module:{0})::Node(): bad canonical hostname<{1}> for node. |
| Description | The symbolic host name set on the machine does not match the host name set for this module in the model. Make sure that they are the same. |
| Code | 138004 |
| Severity | Critical |
| Message | Node(module:{0})::matches(): canonical hostname of localhost resolved to <{1}> |
| Description | An attempt to resolve the host name of this machine to the canonical name has failed. Check your DNS and the host name setting. |
| Code | 138005 |
| Severity | Info |
| Message | Node(module:{0}):: host:({1}:{2}) matches our running instance. |
| Description | Information that the host name has been found to match the cluster configuration. |
| Code | 138006 |
| Severity | Info |
| Message | Node::initialize() host:({0}:{1}) has no module, assuming cold spare. |
| Description | The cluster configuration for this node does not specify a module. The Sybase Event Stream Processor will be started in cold spare mode, waiting for the cluster manager command to replace a failed node. |
| Code | 138007 |
| Severity | Info |
| Message | Node(module:{0})::matches(): found matching module names, useConfigTopology false, skipping host/port verification. |
| Description | The command line option -T specifies that the cluster topology from the model file should not be used. Instead the cluster manager will provide the actual topology. |
| Code | 138008 |
| Severity | Critical |
| Message | Node(module:{0})::matches(): can not write ephemeral port to file '{1}': {2} |
| Description | The clustered model was configured with the test feature that allows to run all the cluster modules on the same physical machine, with a dynamic allocation of the control port numbers. |
| Code | 139000 |
| Severity | Info |
| Message | {0}({1})::run() -- starting event queue Stream. |
| Description | Information about the internal stages of initialization. |
| Code | 139001 |
| Severity | Info |
| Message | {0}({1})::initExternalStream() istream<{2}> found in module<{3}>, running on host<{4}:{5}({6})>. |
| Description | Information about the internal stages of initialization. |
| Code | 139002 |
| Severity | Critical |
| Message | {0}({1})::initExternalStream() istream<{2}> could not be found in any module, exiting. |
| Description | The source for the CopyStream is not present in the model. Check and correct the model. |
| Code | 139003 |
| Severity | Info |
| Message | {0}({1})::initExternalStream() istream<{2}> in module<{3}> awaiting cluster topology from c&c call. |
| Description | The Sybase Event Stream Processor was started with option -T and there is no information on the location of the other nodes in the cluster. Need to wait for the cluster manager to provide this information. |
| Code | 139004 |
| Severity | Info |
| Message | {0}({1})::migrateModuleLocation() istream<{2}> in module<{3}> moved to ({4}:{5}) |
| Description | The cluster manager has provided the information about the location of a cluster module. |