Event Persistence Messages

EVSECM172E0000	Invalid Event Persistence Elasticsearch URI format: {0}
Explanation	The Elasticsearch URI was specified using an invalid or unexpected format.

EVSECM172E0001	Error creating Elasticsearch transport client for URI: {0}
Explanation	There was an error creating the Elasticsearch client and connecting to the cluster using the specified URI.

EVSECM172E0002	Error creating Elasticsearch transport client for cluster name {0} and host(s) {1}
Explanation	There was an error creating the Elasticsearch client and connecting to the cluster using the specified URI.

EVSECM232E0000	Invalid Event Persistence Elasticsearch URI format: {0}
Explanation	he Elasticsearch URI was specified using an invalid or unexpected format.

EVSECM232E0001	Error creating Elasticsearch transport client for URI: {0}
Explanation	There was an error creating the Elasticsearch client and connecting to the cluster using the specified URI.

EVSECM232E0002	Error creating Elasticsearch transport client for cluster name {0} and host(s) {1}
Explanation	There was an error creating the Elasticsearch client and connecting to the cluster using the specified URI.

EVSECM564E0000	Invalid Event Persistence Elasticsearch URI format: {0}
Explanation	Invalid Event Persistence Elasticsearch URI format

EVSECM564E0001	Error creating Elasticsearch transport client version 5.6.4 for URI {0}
Explanation	Error creating Elasticsearch transport client version 5.6.4 for URI {0}
Action	Check your connection to the elasticsearch node and your transport client settings.

EVSECM564E0002	Error creating Elasticsearch transport client for cluster name {0} and host {1}
Explanation	Error creating Elasticsearch transport client for cluster name {0} and host {1}
Action	Check your connection to the elasticsearch node, transport client settings, and cluster name and host.

EVSECME0000

Error creating Elasticsearch transport client for URI: {0}

EVSECME0001

Error creating Elasticsearch transport client for cluster name {0} and host(s) {1}

EVSECME0002

Invalid Event Persistence Elasticsearch URI format: {0}

EVSEDSE0000	Cannot get EDA event type schema parser.
Explanation	Cannot get EDA event type schema parser.

EVSEDSE0001	Cannot get event type store at location: {0}
Explanation	Cannot get event type store at the given location.
Action	Please make sure that the event type store location is valid.

EVSEDSE0002

Non-default ETS locations are not currently supported in OSGi {0}

EVSEDSE0003	Timeout waiting for blueprint injection of EDA interface provider
Explanation	The timeout expired when waiting for EDA ETS/XSD services

EVSEQF232E0000	A error occurred when trying to instantiate the Elasticsearch 2.3.2 Query Session implementation class.
Explanation	The factory implementation could not create an instance of the query session class.
Action	Contact Global Support.

EVSEQF232E0001	Query implementation library found in multiple locations: {0}
Explanation	The implementation library was found in multiple locations on the server or installation directory. In this situation, the factory can not determine the proper installation directory based on the library location.
Action	Contact Global Support.

EVSEQF232E0002	Could not find query implementation library while determining installation directory.
Explanation	In Non-OSGi environments the factory loads its third party dependencies from a whitelist. It must first determine the installation directory. This is done by searching for the implementation jar in the Software_AG_Directory\common\EventPersistence folder. This error indicates that the library could not be found.
Action	Contact Global Support.

EVSEQF232E0003	The property dep.common.dir is set to a non-existent directory: {0}
Explanation	The system property dep.common.dir must be set to a valid Software_AG_Directory/common/EventPersistence directory location.
Action	Contact Global Support.

EVSEQF232E0004	The property dep.common.dir has not been set before you use this component.
Explanation	The system property dep.common.dir is required and must be set to the location of the Software_AG_Directory/common/EventPersistence directory.
Action	Contact Global Support.

EVSEQF564E0000	A error occurred when trying to instantiate the Elasticsearch 5.6.4 Query Session implementation class.
Explanation	The factory implementation could not create an instance of the query session class.
Action	Contact Global Support.

EVSEQF564E0001	Query implementation library found in multiple locations: {0}
Explanation	The implementation library was found in multiple locations on the server or installation directory. In this situation, the factory can not determine the proper installation directory based on the library location.
Action	Contact Global Support.

EVSEQF564E0002	Could not find query implementation library while determining installation directory.
Explanation	In Non-OSGi environments the factory loads its third party dependencies from a white-list. It must first determine the installation directory. This is done by searching for the implementation jar in the Software_AG_Directory/common/EventPersistence folder. This error indicates that that library could not be found.
Action	Contact Global Support.

EVSEQF564E0003	The property dep.common.dir is set to a non-existent directory: {0}
Explanation	The system property dep.common.dir must be set to a valid Software_AG_Directory/common/EventPersistence directory location.
Action	Contact Global Support.

EVSEQF564E0004	The property dep.common.dir has not been set prior to using this component.
Explanation	The system property dep.common.dir is required and must be set to the location of the Software_AG_Directory/common/EventPersistence directory.
Action	Contact Global Support.

EVSEQI172E0000	Unsupported syntax found in aggregate function clause: {0}
Explanation	The syntax of the aggregate expression is incorrect. This error should never occur because the grammar has already been validated. It's included for proper error handling.

EVSEQI172E0001	Unsupported encoding exception encountered when formatting result
Explanation	The default utf-8 encoding was not supported in this environment. The result body could not be added to the result set.

EVSEQI172E0002	An error has occurred because the response reference has not been set in response handler
Explanation	This is a programming class usage issue. This error shouldn't be experienced once the implementation is tested and verified.

EVSEQI172E0003	Unexpected statement type found when trying to determine query builder implementation
Explanation	The query builder examines the statement to determine if its an instance or aggregate query. In this case the implementation couldn't identify the statement type.

EVSEQI172E0004	Error executing full text query due to invalid query filter
Explanation	The query filter could not be transformed and used in the Elasticsearch query.

EVSEQI172E0005	An unsupported encoding exception was thrown while generating query hit.
Explanation	The default encoding of utf-8 was not available and the query hit document could not be processed.

EVSEQI172E0006	An unsupported encoding exception was thrown while generating explain message
Explanation	The default encoding of utf-8 was not available to format the explain plan message

EVSEQI172E0007	Error creating full text query for explain plan due to invalid query filter.
Explanation	The explain plan content could not be generated due to a parsing error in the filter syntax

EVSEQI172E0010	Error transforming query to native Elasticsearch request!%n{0}
Explanation	The query as specified in the Common Query Syntax could not be transformed into a native Elasticsearch query.

EVSEQI172E0011	Error executing native Elasticsearch search request!%n{0}
Explanation	An error occurred during execution of the Elastisearch query.

EVSEQI172E0012	Error transforming query to native Elastisearch request for explain plan
Explanation	The query as expressed in the Common Query Syntax could not be transformed into an Elasticsearch request when creating the explain plan.

EVSEQI172E0013	An unsupported encoding exception was thrown while generating explain message
Explanation	The default encoding of utf-8 is not availble and caused an exception when generating the explain plan text.

EVSEQI172E0014	Query session has been created with invalid context for this implementation
Explanation	The context must include all of the required parameters for this query implementation.

EVSEQI172E0015	Error creating a transport client connection to Elasticsearch cluster
Explanation	A connection to the Elasticsearch cluster could not be established.

EVSEQI172E0016	Failed to position cursor at next event in the result stream
Explanation	An exception was thrown when trying to move the cursor to the next position in the result stream.

EVSEQI172E0017	The method {0} is unsupported in this implementation of ResultStream
Explanation	The ResultStream inteface only requires that all implementations provide a next operation.

EVSEQI172E0018	Error getting result at current cursor position from handler
Explanation	An exception was thrown when attempting to get the event data from the current position in the result stream.

EVSEQI172I0008

Inbound query in common syntax form:

EVSEQI172I0009

Outbound query in native form:

EVSEQI232E0000	Unsupported syntax found in aggregate function clause: {0}
Explanation	The syntax of the aggregate expression is incorrect. This error should never occur because the grammar has already been validated. It's included for proper error handling.

EVSEQI232E0001	Unsupported encoding exception encountered when formatting result
Explanation	The default utf-8 encoding was not supported in this environment. The result body could not be added to the result set.

EVSEQI232E0002	An error has occurred because the response reference has not been set in response handler
Explanation	This is a programming class usage issue. This error shouldn't be experienced once the implementation is tested and verified.

EVSEQI232E0003	Unexpected statement type found when trying to determine query builder implementation
Explanation	The query builder examines the statement to determine if its an instance or aggregate query. In this case the implementation couldn't identify the statement type.

EVSEQI232E0004	Error executing full text query due to invalid query filter
Explanation	The query filter could not be transformed and used in the Elasticsearch query.

EVSEQI232E0005	An unsupported encoding exception was thrown while generating query hit.
Explanation	The default encoding of utf-8 was not available and the query hit document could not be processed.

EVSEQI232E0006	An unsupported encoding exception was thrown while generating explain message
Explanation	The default encoding of utf-8 was not available to format the explain plan message

EVSEQI232E0007	Error creating full text query for explain plan due to invalid query filter.
Explanation	The explain plan content could not be generated due to a parsing error in the filter syntax

EVSEQI232E0010	Error transforming query to native Elasticsearch request:%n{0}
Explanation	The query as specified in the Common Query Syntax could not be transformed into a native Elasticsearch query.

EVSEQI232E0011	Error executing native Elasticsearch search request:%n{0}
Explanation	An error occurred during execution of the Elastisearch query.

EVSEQI232E0012	Error transforming query to native Elastisearch request for explain plan
Explanation	The query as expressed in the Common Query Syntax could not be transformed into an Elasticsearch request when creating the explain plan.

EVSEQI232E0013	An unsupported encoding exception was thrown while generating explain message
Explanation	The default encoding of utf-8 is not availble and caused an exception when generating the explain plan text.

EVSEQI232E0014	Query session has been created with invalid context for this implementation
Explanation	The context must include all of the required parameters for this query implementation.

EVSEQI232E0015	Error creating a transport client connection to Elasticsearch cluster
Explanation	A connection to the Elasticsearch cluster could not be established.

EVSEQI232E0016	Failed to position cursor at next event in the result stream
Explanation	An exception was thrown when trying to move the cursor to the next position in the result stream.

EVSEQI232E0017	The method {0} is unsupported in this implementation of ResultStream
Explanation	The ResultStream inteface only requires that all implementations provide a next operation.

EVSEQI232E0018	Error getting result at current cursor position from handler
Explanation	An exception was thrown when attempting to get the event data from the current position in the result stream.

EVSEQI232I0008

Inbound query in common syntax form:

EVSEQI232I0009

Outbound query in native form:

EVSEQI564E0000	Unsupported syntax found in aggregate function clause: {0}
Explanation	Unsupported syntax found in aggregate function clause: {0}

EVSEQI564E0001	Unsupported encoding exception encountered when formatting result
Explanation	Unsupported encoding exception encountered when formatting result

EVSEQI564E0002	An error has occurred because the response reference has not been set in response handler
Explanation	An error has occurred because the response reference has not been set in response handler

EVSEQI564E0003	Unexpected statement type found when trying to determine query builder implementation
Explanation	Unexpected statement type found when trying to determine query builder implementation

EVSEQI564E0004	Error executing full text query due to invalid query filter.
Explanation	Error executing full text query due to invalid query filter.

EVSEQI564E0005	An unsupported encoding exception was thrown while generating query hit.
Explanation	An unsupported encoding exception was thrown while generating query hit.

EVSEQI564E0006	An unsupported encoding exception was thrown while generating explain message
Explanation	An unsupported encoding exception was thrown while generating explain message

EVSEQI564E0007	Error creating full text query for explain plan due to invalid query filter.
Explanation	Error creating full text query for explain plan due to invalid query filter.

EVSEQI564E0010	Error transforming query to native Elasticsearch request!%n{0}
Explanation	Error transforming query to native Elasticsearch request!%n{0}

EVSEQI564E0011	Error executing native Elasticsearch search request!%n{0}
Explanation	Error executing native Elasticsearch search request!%n{0}

EVSEQI564E0012	Error transforming query to native Elastisearch request for explain plan
Explanation	Error transforming query to native Elastisearch request for explain plan

EVSEQI564E0013	An unsupported encoding exception was thrown while generating explain message
Explanation	An unsupported encoding exception was thrown while generating explain message

EVSEQI564E0014	Query session has been created with invalid context for this implementation
Explanation	Query session has been created with invalid context for this implementation

EVSEQI564E0015	Error creating a transport client connection to Elasticsearch cluster
Explanation	Error creating a transport client connection to Elasticsearch cluster

EVSEQI564E0016	Failed to position cursor at next event in the result stream
Explanation	Failed to position cursor at next event in the result stream

EVSEQI564E0017	The method {0} is unsupported in this implementation of ResultStream
Explanation	The method {0} is unsupported in this implementation of ResultStream

EVSEQI564E0018	Error getting result at current cursor position from handler
Explanation	Error getting result at current cursor position from handler

EVSEQIE0000

Query session has been created with invalid context for this implementation

EVSEQIE0001

Error creating a transport client connection to Elasticsearch cluster

EVSEQIE0002

Error transforming query into native Elasticsearch request!%c{0}

EVSEQIE0003

Error executing native Elasticsearch search request!%c{0}

EVSEQIE0004	Failed to position cursor at next event in the result stream
Explanation	There was an error when moving the cursor position forward in the stream

EVSEQIE0005	The method {0} is unsupported in this implementation of ResultStream
Explanation	The only requirement on a ResultStream implementation is that they provide a forward cursor via the next method

EVSEQIE0006	Error getting result at current cursor position from handler
Explanation	There was an error retrieving or formating the result at the cursor position

EVSEQIE0007	Unexpected statement type found when trying to determine query builder implementation
Explanation	The query transformation found an expression other than an instance, property list or aggregate query.

EVSEQIE0008	Unsupported syntax found in aggregate function clause: {0}
Explanation	When processing an aggregation other than count, sum, avg, min or max was found.

EVSEQIE0009

Unsupported encoding exception encountered when formatting result

EVSEQIE0010	An error has occurred because the response reference has not been set in response handler
Explanation	This is a fatal programming error; the Elasticsearch response reference was not set before invoking the handler methods.

EVSEQIE0011	Cursor positioning error; No pending results on result stack
Explanation	The getResult method was invoked but there is no pending result item on the cursor stack.

EVSEQIE0013	An unsupported encoding exception was thrown while generating explain message
Explanation	An error was encountered when creating a byte array with utf8 encoding

EVSEQIE0016

Error executing full text query due to invalid query filter.

EVSEQIE0017

An unsupported encoding exception was thrown while generateing query hit.

EVSEQII0014

Inbound query in common syntax form:

EVSEQII0015

Outbound query in native form:

EVSEQIW0012	Error transforming query for explain plan
Explanation	The query transformation failed during processing of the explain plan call.

EVSEREE0001	Event Routing Consumers are not supported by this Endpoint implementation
Explanation	Event Persistence components only support producers

EVSEREE0002	Synchronous Event processing is not supported by this component.
Explanation	This component only supports asynchronous processing.

EVSEREE0003	Error initializing required internal resources
Explanation	Internal resources such as the transformer or storage provider could not be initialized.

EVSEREE0004	Error transforming event instance from native format to JSON format
Explanation	An error occurred during transformation from XML to JSON

EVSEREE0005	Fatal exception thrown from storage provider during event processing
Explanation	An error occurred when trying to persist the current event

EVSEREE0006	Error creating storage type definition for event type: {0}
Explanation	The event type schema could not be transformed to the storage type definition required by the storage providers.

EVSEREE0007	Error parsing event schema with namespace {0} and event type {1}
Explanation	The EDA event type schema for the specified type could not be parsed.

EVSEREE0008	Error creating schema parser with Event Type Store location: {0}
Explanation	A reference to the EDA schema parser class or service could not be obtained.

EVSERSE0000	Port {0} should be a non-negative and non-zero integer value.
Explanation	Port should be a non-negative integer value.

EVSERSE0001	{0} must be all lower case.
Explanation	Index Name must be all lower case..

EVSERSE0003	must be a non-negative non-zero integer.
Explanation	Thread Pool Keep Alive Time must be a non-negative integer and non-zero integer.

EVSERSE0006	must be a non-negative integer.
Explanation	Thread Pool Queue size must be a non-negative integer.

EVSERSE0009	must be a non-negative and non-zero integer.
Explanation	Batch size must be a non-negative and non-zero integer.

EVSERSE0010	must be a non-negative and non-zero integer.
Explanation	Batch write time must be a non-negative and non-zero integer.

EVSERSE0011	Event Persistence does not support storage type: {0}.
Explanation	This is not supported store type for event persistence.

EVSERSE0012	Can't create service bundle for storage type: {0}.
Explanation	The service bundle could not be created!

EVSERSE0013	Pool size must be a non-negative integer.
Explanation	Core Thread Pool size must be a non-negative integer.

EVSERSE0014

Not supported storage type {0}.

EVSERSE0015	must be a non-negative and non-zero integer.
Explanation	Hdfs maximum file size must be a non-negative and non-zero integer.

EVSERSE0016	Pool Size must be a non-negative and non-zero integer.
Explanation	Maximum Thread Pool Size must be a non-negative and non-zero integer.

EVSERSE0017	Elasticsearch keystore filepath is not valid.
Explanation	Elasticsearch keystore filepath is not valid.

EVSERSE0018	Elasticsearch truststore filepath is not valid.
Explanation	Elasticsearch truststore filepath is not valid.

EVSERSE0019	Key store should not be blank
Explanation	Key store should not be blank

EVSERSE0020	Trust store should not be blank
Explanation	Trust store should not be blank

EVSERSE0025	{0} must be specified using the following format: {1}.
Explanation	URI must be specified using the given format.

EVSERSE0028	is invalid Hive Warehouse Location.
Explanation	Hive Warehouse Location is invalid, please enter a valid location name.

EVSERSI0017	Event Persistence Configuration Validation Information
Explanation	Display Label used for Event Persistence Configuraiton Validation Information UI

EVSERSI0018	Connection to Elasticsearch node succeeded:
Explanation	Successfully connected to the specified Elasticsearch cluster, index, host and port.

EVSERSI0026	Connection to HDFS succeeded.
Explanation	Connection to HDFS succeeded.

EVSERSI0029	Connection to Hive server succeeded.
Explanation	Connection to Hive server succeeded.

EVSERSW0019	Could not connect to Elasticsearch node:
Explanation	Could not connect to the specified elasticsearch cluster node, index, host and port.

EVSERSW0020	Could not connect to Hive server:
Explanation	Could not connect to the specified Hive server.

EVSERSW0021	Could not connect to HDFS:
Explanation	Could not connect to the specified HDFS database, hive warehouse location,

EVSERSW0022	Cannot get JMX MBeanServer Connector for Runtime Componenent {0}.
Explanation	Cannot get JMX MBeanServer Connector to the runtime component.

EVSERSW0023	JMX MBeanServer invocation exception to remote runtime component {0}.
Explanation	JMX MBeanServer invocation exception to remote runtime component.

EVSERSW0024	Cannot get JMX Connector for remote runtime component {0}.
Explanation	Cannot get JMX Connector for remote runtime component.

EVSERSW0025	Cannot ping single SSL enabled elasticsearch node
Explanation	Cannot ping single SSL enabled elasticsearch node

EVSESEE0000

No onfiguration passed into this service.

EVSESEE0001	Synchronous Event processing is not supported by this component.
Explanation	Synchronous Event processing is not supported by this component.

EVSESEE0002	Error initializing required internal resources
Explanation	Error initializing required internal resources

EVSESEE0003

Error stopping internal resource {0}

EVSESEE0004	Error transforming event instance from native format to JSON format
Explanation	Error transforming event instance from native format to JSON format

EVSESEE0005	Cannot transforming event {0} instance from native format to JSON format and cannot persist the event into Event Persistence error table.
Explanation	Cannot transforming event {0} instance from native format to JSON format and cannot persist the event into Event Persistence error table.

EVSESEE0006	Fatal exception thrown from storage provider during processing event {0}.
Explanation	Fatal exception thrown from storage provider during event processing.

EVSESEE0007	Error creating storage type definition for event type: {0}
Explanation	Error creating storage type definition for the given event type.

EVSESEE0008	DES Event Type {0} has not been registered in Digital Event Type TypeRepository.
Explanation	DES Event Type has not been registered in Digital Event Type TypeRepository.

EVSESEE0009	Invalid Configuration class type {0}. : Expected type: {1}.
Explanation	Invalid Configuration class type.

EVSESEE0010	'{0}' Digital Event Data Type for event field '{1}' is not supported.
Explanation	Given Digital Event Data Type is not supported.

EVSESEE0011	Error initializing required internal resources; a restart may be required
Explanation	The required resources could not be initialized. This could be due to a wiring or classpath issue.

EVSESEE0012	A fatal and unexpected exception was thrown when creating the generic storage event instance.
Explanation	A storage event implementation could not be instantiated from the DES event instance.

EVSESEE0013	Event Persistence Sender is shutting down; events can't be processed in this state.
Explanation	An event was sent for processing while the sender was in the process of stopping.
Action	No action. If store forward is enabled the event will be reprocessed; if not an error will be raised.

EVSESF232E0000	A error occurred when trying to instantiate the Elasticsearch 2.3.2 Storage Provider implementation.
Explanation	The factory could not create an instance of the storage provider implementation. This error could be related to feature provisioning or a class path issue.
Action	Contact Global Support.

EVSESF232E0001	Could not find storage provider implementation library to determine installation directory.
Explanation	In Non-OSGi environments the factory loads its third party dependencies from a whitelist. It must first determine the installation directory. This is done by searching for the implementation jar in the common Software_AG_Directory\common\EventPersistence folder. This error indicates that that library could not be found.
Action	Verify that the Digital Event Persistence libraries were selected during the installation.

EVSESF232E0002	Storage provider implementation library found in multiple locations: {0}
Explanation	The implementation library was found in multiple locations on the server or installation directory. In this situation, the factory can not determine the proper installation directory based on the library location.
Action	Check the installation directory.

EVSESF232E0003	The property dep.common.dir is set to a non-existent directory: {0}
Explanation	The system property dep.common.dir must be set to a valid Software_AG_Directory/common/EventPersistencet directory location.
Action	Contact Global Support.

EVSESF232E0004	The property dep.common.dir has not been set prior to using this component.
Explanation	The system property dep.common.dir is required and must be set to the location of the Software_AG_Directory/common/EventPersistencet directory.
Action	Contact Global Support.

EVSESF564E0000	A error occurred when trying to instantiate the Elasticsearch 5.6.4 Storage Provider implementation.
Explanation	A error occurred when trying to instantiate the Elasticsearch 5.6.4 Storage Provider implementation.
Action	Contact Global Support.

EVSESF564E0001	Could not find storage provider implementation library to determine installation directory.
Explanation	In Non-OSGi environments the factory loads its third party dependencies from a whitelist. It must first determine the installation directory. This is done by searching for the implementation jar in the Software_AG_Directory/common/EventPersistence folder. This error indicates that that library could not be found.
Action	Verify that the Digital Event Persistence libraries were selected during the installation.

EVSESF564E0002	Storage provider implementation library found in multiple locations: {0}
Explanation	The implementation library was found in multiple locations on the server or installation directory. In this situation, the factory can not determine the proper installation directory based on the library location.
Action	Check the installation directory.

EVSESF564E0003	The property dep.common.dir is set to a non-existent directory: {0}
Explanation	The system property dep.common.dir must be set to a valid Software_AG_Directory/common/EventPersistence directory location.
Action	Contact Global Support.

EVSESF564E0004	The property dep.common.dir has not been set prior to using this component.
Explanation	The system property dep.common.dir is required and must be set to the location of the Software_AG_Directory/common/EventPersistence directory.
Action	Contact Global Support.

EVSESFE0000	Port {0} should be a non-negative and non-zero integer value.
Explanation	Port should be a non-negative and non-zero integer.

EVSESFE0001	must be a non-negative integer.
Explanation	Thread Pool Keep Alive Time must be a non-negative integer.

EVSESFE0002	must be a non-negative and non-zero integer.
Explanation	Batch size must be a non-negative and non-zero integer.

EVSESFE0003	must be a non-negative and non-zero integer.
Explanation	Batch write time must be a non-negative and non-zero integer.

EVSESFE0004	Event Persistence does not support storage type: {0}.
Explanation	This is not supported storage type for Event Persistence.

EVSESFE0005	must be a non-negative and non-zero integer.
Explanation	Thread Pool Queue size must be a non-negative and non-zero integer.

EVSESFE0006	must be a non-negative integer.
Explanation	Core Thread Pool size must be a non-negative integer.

EVSESFE0007	must be a non-negative and non-zero integer.
Explanation	Hdfs maximum file size must be a non-negative and non-zero integer.

EVSESFE0008	Pool Size must be a non-negative and non-zero integer.
Explanation	Maximum Thread Pool Size must be a non-negative and non-zero integer.

EVSESFE0016	{0} must be specified using the following format: {1}.
Explanation	URI must be specified using the given format.

EVSESFE0018	{0} must be all lower case.
Explanation	Index name must be in all lower case.

EVSESFE0019	Elasticsearch keystore filepath is not valid.
Explanation	Elasticsearch keystore filepath is not valid.

EVSESFE0020	Elasticsearch truststore filepath is not valid.
Explanation	Elasticsearch truststore filepath is not valid.

EVSESFE0021	is invalid Hive Warehouse Location.
Explanation	Hive Warehouse Location is invalid, please enter a valid location name.

EVSESFI0009	Connection to HDFS succeeded.
Explanation	Connection to HDFS succeeded.

EVSESFI0017	Connection to Hive server succeeded.
Explanation	Connection to Hive server succeeded.

EVSESFI0022	Connection to Elasticsearch node succeeded:
Explanation	Connection to specific Elasticsearch succeeded.

EVSESFW0010	Could not connect to Elasticsearch node:
Explanation	Could not connect to the specified elasticsearch cluster node, index, host and port.

EVSESFW0011	Could not connect to Hive server:
Explanation	Could not connect to the specified Hive server.

EVSESFW0012	Could not connect to HDFS:
Explanation	Could not connect to the specified HDFS database, hive warehouse location.

EVSESFW0013	Cannot get JMX MBeanServer Connector for Runtime Componenent {0}.
Explanation	Cannot get JMX MBeanServer Connector to the runtime component.

EVSESFW0014	JMX MBeanServer invocation exception to remote runtime component {0}.
Explanation	JMX MBeanServer invocation exception to remote runtime component.

EVSESFW0015	Cannot get JMX Connector for remote runtime component
Explanation	Cannot get JMX Connector for remote runtime component.

EVSESI172E0000	Process method called before provider has been started
Explanation	This is a programatic initialization error. The storage providers start method was not called during initialization.

EVSESI172E0001	Error initializing required internal resources
Explanation	An error occurred during initialization of the various implementation classes for this storage provider.

EVSESI172E0002	Error creating or accessing bulk indexer for event type: {0}
Explanation	A bulk indexer instance could not be accessed or created for the specified event type.

EVSESI172E0003	Error stopping resource {0} on provider shutdown
Explanation	An internal resource threw an exception while stopping the storage provider.

EVSESI172E0005	Failed to create Elasticsearch transport client connection to cluster {0}, index {1} on server {2} with user {3}.
Explanation	The client could not establish a connection to the Elasticsearch cluster.

EVSESI172E0006	Elasticsearch client manager not started for cluster {0}, index {1} on server {2} with user {3}
Explanation	An attempt to get a connection was made before the client manager was started.

EVSESI172E0007	Error stopping bulk indexer for type: {0}
Explanation	The bulk indexer instance for the specified type threw an exception on shutdown.

EVSESI172E0008	Error creating Elasticsearch bulk indexing request
Explanation	An error occurred while formatting an Elasticsearch bulk indexing request for the current event batch

EVSESI172E0009	Error executing Elasticsearch bulk indexing request
Explanation	The Elasticsearch bulk indexing request for the specified event batch could not be executed.

EVSESI172E0010	Error loading metadata for persistence error type; logging to local file
Explanation	Metadata for the persistence error type couldn't be found or created. All messages will be logged to the local log file.

EVSESI172E0011	Unable to write internal persistence error event; defaulting to log file:%n {0}
Explanation	The logger could not persist the error event data to the data store. The error will be written to the default log file.

EVSESI172E0012	Error storing internal persistence error event to Elasticsearch index.
Explanation	The persistence error event could not be stored in elasticsearch due to an exception.

EVSESI172E0013	Exception encountered during auto registration of event type: {0}
Explanation	Storage could not be allocated for the specified event type due to an Elasticsearch error.

EVSESI172E0014	Error getting Elasticsearch client for auto registration
Explanation	An exception occured when trying to access the Elasticsearch transport client

EVSESI172E0015	An event type mapping already exists for the event type: {0}
Explanation	Storage for the specified event type has already been allocated.

EVSESI172E0016	Error checking for existing type in Elasticsearch index
Explanation	An exception was thrown while checking Elasticsearch for a registered event type

EVSESI172E0017	No acknowledgment received from Elasticsearch cluster after create index operation
Explanation	The Elasticsearch node failed to acknowledge the status of the create index request.

EVSESI172E0018	No acknowledgment received from Elasticsearch cluster after type mapping operation
Explanation	The Elasticsearch node failed to acknowledge the status of the put type mapping request.

EVSESI172E0019	An Elasticsearch exception occurred while creating the type mapping
Explanation	The type mapping could not be added due to an exception thrown by the Elasticsearch client-server.

EVSESI172E0020	Failed to initialize Elasticsearch schema parser implementation
Explanation	The event type schema parser couldn't be initialized; no event type parsing is possible.

EVSESI172E0021	Error creating schema parser with Event Type Store location: {0}
Explanation	The EDA event type schema parser could not be initialized.

EVSESI172E0022	Error parsing event schema with namespace {0} and event type {1}
Explanation	The event type definiition for the given namespace and event type could not be parsed.

EVSESI172E0023	A valid namespace and event type are required to produce an Elasticsearch type mapping.
Explanation	Event type information could not be found for the specified namespace and event type.

EVSESI172E0024	The event persistence annotation is not recognized: {0}
Explanation	An annotation specified in the event type definition is not known or supported.

EVSESI172E0027	Error retrieving Elasticsearch client for metadata verification
Explanation	A connection couldn't be established while trying to load metadata from index

EVSESI172E0029	Error closing transport client connection to cluster {0}, index {1} on server {2} with user {3}
Explanation	An error occurred disconnecting from the Elasticsearch cluster

EVSESI172E0030	The event persistence annotation is not recognized: {0}
Explanation	An annotation value was specified that is not supported by event persistence

EVSESI172E0031	Error retrieving normalized type from component for event type: {0}
Explanation	An exception was thrown by the component when generating the normalized type for the event type

EVSESI172I0004	Elasticsearch transport client successfully connected to cluster {0}, index {1} on server {2} with user {3}
Explanation	The connection to the Elasticsearch cluster was successful.

EVSESI172I0028	Elasticsearch transport client successfully disconnected from cluster {0}, index {1} on server {2} with user {3}
Explanation	The component has disconnected from the Elasticsearch cluster

EVSESI172W0025	Task manager queue is full; The operation will be re-tried
Explanation	The task queue is at it's maximum size. The operation is re-tried after a slight delay.

EVSESI172W0026	Thread interrupted while waiting for task re-submission
Explanation	The task manager thread was interrupted during re-submission delay. The operation will be re-tried immediately.

EVSESI232E0000	Process method called before provider has been started
Explanation	This is a programatic initialization error. The storage providers start method was not called during initialization.

EVSESI232E0001	Error initializing required internal resources
Explanation	An error occurred during initialization of the various implementation classes for this storage provider.

EVSESI232E0002	Error creating or accessing bulk indexer for event type: {0}
Explanation	An indexer could not be created to process the specified event type. This could be due to a failure to connect to the cluster for the required metadata.
Action	Check the status and healh of the cluster.

EVSESI232E0003	Error stopping resource {0} on provider shutdown
Explanation	An internal resource threw an exception while stopping the storage provider.

EVSESI232E0005	Failed to create Elasticsearch transport client connection to cluster {0}, index {1} on server {2} with user {3}.
Explanation	The client could not establish a connection to the Elasticsearch cluster.

EVSESI232E0006	Elasticsearch client manager not started for cluster {0}, index {1} on server {2} with user {3}
Explanation	An attempt to get a connection was made before the client manager was started.

EVSESI232E0007	Error stopping bulk indexer instance for type: {0}
Explanation	The bulk indexer instance for the specified type threw an exception on shutdown.

EVSESI232E0008	Error creating Elasticsearch bulk indexing request
Explanation	An error occurred while formatting an Elasticsearch bulk indexing request for the current event batch

EVSESI232E0009	Error executing Elasticsearch bulk indexing request
Explanation	The Elasticsearch bulk indexing request for the specified event batch could not be executed.

EVSESI232E0010	Error loading metadata for persistence error type; logging to local file
Explanation	Metadata for the persistence error type couldn't be found or created. All messages will be logged to the local log file.

EVSESI232E0011	Unable to write internal persistence error event; defaulting to log file:%n {0}
Explanation	The logger could not persist the error event data to the data store. The error will be written to the default log file.

EVSESI232E0012	Error storing internal persistence error event to Elasticsearch index.
Explanation	The persistence error event could not be stored in elasticsearch due to an exception.

EVSESI232E0013	Exception encountered during auto registration of event type: {0}
Explanation	Storage could not be allocated for the specified event type due to an Elasticsearch error.

EVSESI232E0014	Error getting Elasticsearch client for auto registration
Explanation	An exception occured when trying to access the Elasticsearch transport client

EVSESI232E0015	An event type mapping already exists for the event type: {0}
Explanation	Storage for the specified event type has already been allocated.

EVSESI232E0016	Error checking for existing type in Elasticsearch index
Explanation	An exception was thrown while checking Elasticsearch for a registered event type

EVSESI232E0017	No acknowledgment received from Elasticsearch cluster after create index operation
Explanation	The Elasticsearch node failed to acknowledge the status of the create index request.

EVSESI232E0018	No acknowledgment received from Elasticsearch cluster after type mapping operation
Explanation	The Elasticsearch node failed to acknowledge the status of the put type mapping request.

EVSESI232E0019	An Elasticsearch exception occurred while creating the type mapping
Explanation	The type mapping could not be added due to an exception thrown by the Elasticsearch client-server.

EVSESI232E0020	Failed to initialize Elasticsearch schema parser implementation
Explanation	The event type definiition for the given namespace and event type could not be parsed.

EVSESI232E0021	Error creating schema parser with Event Type Store location: {0}
Explanation	The EDA event type schema parser could not be initialized.

EVSESI232E0022	Error parsing event schema with namespace {0} and event type {1}
Explanation	Event type information could not be found for the specified namespace and event type.

EVSESI232E0023	A valid namespace and event type are required to produce an Elasticsearch type mapping.
Explanation	Event type information could not be found for the specified namespace and event type.

EVSESI232E0024	The event persistence annotation is not recognized: {0}
Explanation	An annotation specified in the event type definition is not known or supported.

EVSESI232E0027	Error retrieving Elasticsearch client for metadata verification
Explanation	A connection couldn't be established while trying to load metadata from index

EVSESI232E0029	Error closing transport client connection to cluster {0}, index {1} on server {2} with user {3}
Explanation	An error occurred when diconnecting from the Elasticsearch cluster

EVSESI232E0030	The event persistence annotation is not recognized: {0}
Explanation	An annotation value was specified that is not supported by event persistence

EVSESI232E0031	Error retrieving normalized type from component for event type: {0}
Explanation	An exception was thrown by the component when generating the normalized type for the event type

EVSESI232E0032	Error generating cache key for bulk indexer instance
Explanation	There was an error generating the cache key for the specified elasticsearch resource; verify variable values.

EVSESI232E0033	Error creating and starting bulk indexer for event type: {0}
Explanation	The bulk indexer for the stated type could not be created or started

EVSESI232E0034	Validation of dynamic service configuration against provided values failed
Explanation	A dynamic service configuration was provided but the variables are not present in the event.

EVSESI232E0035	Validation of dynamic service configuration failed. Event can not be persisted: Header: {0} Body: {1}
Explanation	The values required for using a dynamic configuration were not supplied in the event being processed.

EVSESI232E0036	Error initialising internal resources for provider; operation will be re-tried. Exception repeated {0} times
Explanation	Internal initialisation failed. The operation will be retried until successful or the component is restarted.

EVSESI232E0037	Error creating bulk indexer for event type {0}; operation will be re-tried; Exception repeated {1} times
Explanation	An indexer could not be created to process the specified event type. This could be due to a failure to connect to the cluster for the required metadata.

EVSESI232E0038	Error creating Elasticsearch bulk indexing request; operation will be re-tried; Exception repeated {0} times.
Explanation	There was an error while creating the indexing request most likely due to a connectivity issue between the client and the server.
Action	Check the status and health of the cluster.

EVSESI232E0039	Error executing Elasticsearch bulk indexing request; operation will be re-tried; Exception repeated {0} times.
Explanation	There was an error while creating the indexing request most likely due to a connectivity issue between the client and the server.
Action	Check the status and health of the cluster.

EVSESI232E0040	An exception occurred while checking the cluster for the specified destination index: {0}
Explanation	When the provider invoked the index exists call to Elasticsearch, the API threw an exception.
Action	Check the status of the Elasticsearch cluster.

EVSESI232E0041	An Elasticsearch exception occurred while creating the specified destination index: {0}
Explanation	When the provider invoked the create index call to Elasticsearch, the API threw an exception.
Action	Check the status of the Elasticsearch cluster

EVSESI232E0042	An error occurred while attempting to determine if auto-registration is required for type: {0} in index: {1}
Explanation	The service could not access or process the Elasticsearch type mapping in the given index.
Action	Check the health of the Elasticsearch cluster.

EVSESI232E0043	Error creating or accessing indexer for event type: {0}
Explanation	An indexer could not be created to process the specified event type. This could be due to a failure to connect to the cluster for the required metadata.
Action	Check the status and healh of the cluster.

EVSESI232E0044	Error creating Elasticsearch client for bulk indexing operation.
Explanation	A connection to the Elasticsearc cluster could not be obtained.
Action	Check the status and health of the Elasticsearch cluster

EVSESI232E0045	Error creating Elasticsearch bulk indexing request.
Explanation	An error occurred when creating the bulk indexing request.
Action	Check the state and health of the Elasticsearch cluster.

EVSESI232E0046	Error executing Elasticsearch bulk indexing request.
Explanation	An error occurred when executing the indexing operation.
Action	Check the status and health of the Elasticsearch cluster.

EVSESI232E0047	Error creating Elasticsearch client; operation will be re-tried; Exception repeated {1} times.
Explanation	An error occurred when trying to connect to the Elasticsearch cluster.
Action	Check the state and health of the Elasticsearch cluster.

EVSESI232E0048	Error creating bulk indexer for event type {0}; operation will be re-tried.
Explanation	An indexer could not be created to process the specified event type. This could be due to a failure to connect to the cluster for the required metadata.
Action	Check the status and healh of the cluster.

EVSESI232E0049	Error creating Elasticsearch client; operation will be re-tried.
Explanation	An error occurred when trying to connect to the Elasticsearch cluster.
Action	Check the state and health of the Elasticsearch cluster.

EVSESI232E0050	Error creating Elasticsearch bulk indexing request; operation will be re-tried.
Explanation	There was an error while creating the indexing request most likely due to a connectivity issue between the client and the server.
Action	Check the status and health of the cluster.

EVSESI232E0051	Error executing Elasticsearch bulk indexing request; operation will be re-tried.
Explanation	There was an error while creating the indexing request most likely due to a connectivity issue between the client and the server.
Action	Check the status and health of the cluster.

EVSESI232E0052	Error storing event of type: {0}
Explanation	The indexer could not persist the event of the specified event type. This could be due to a failure to connect to the cluster or an issue with the cluster health.
Action	Check the status and healh of the cluster.

EVSESI232E0053	Error creating or accessing indexer for event type: {0}; operation will be re-tried.
Explanation	An indexer could not be created to process the specified event type. This could be due to a failure to connect to the cluster for the required metadata.
Action	Check the status and healh of the cluster.

EVSESI232E0054	Error storing event of type: {0}; operation will be re-tried.
Explanation	The indexer could not persist the event of the specified event type. This could be due to a failure to connect to the cluster or an issue with the cluster health.
Action	Check the status and healh of the cluster.

EVSESI232E0055	Error creating Elasticsearch client for indexing request.
Explanation	A connection to the Elasticsearc cluster could not be obtained.
Action	Check the status and health of the Elasticsearch cluster.

EVSESI232E0056	Error preparing indexing request or processing response - id: {0} document type: {1}
Explanation	An error occurred when creating or processing the index request required to persist the event. This could be due to an issue with the cluster.
Action	Check the status and health of the cluster.

EVSESI232I0004	Elasticsearch transport client successfully connected to cluster {0}, index {1} on server {2} with user {3}
Explanation	The connection to the Elasticsearch cluster was successful.

EVSESI232I0028	Elasticsearch transport client successfully disconnected from cluster {0}, index {1} on server {2} with user {3}
Explanation	The component has disconnected from the Elasticsearch cluster

EVSESI232W0025	Task manager queue is full; The operation will be re-tried
Explanation	The task queue is at it's maximum size. The operation is re-tried after a slight delay.

EVSESI232W0026	Thread interrupted while waiting for task re-submission
Explanation	The task manager thread was interrupted during re-submission delay. The operation will be re-tried immediately.

EVSESI564E0000	Process method called before provider has been started
Explanation	Process method called before provider has been started

EVSESI564E0001	Error initializing required internal resources
Explanation	An error occurred during initialization of the various implementation classes for this storage provider.

EVSESI564E0002	Error creating or accessing bulk indexer for event type: {0}
Explanation	A bulk indexer instance could not be accessed or created for the specified event type.

EVSESI564E0003	Error stopping resource {0} on provider shutdown
Explanation	Error stopping resource {0} on provider shutdown

EVSESI564E0005	Failed to create Elasticsearch transport client connection to cluster {0}, index {1} on server {2} with user {3}.
Explanation	Failed to create Elasticsearch transport client connection to cluster {0}, index {1} on server {2} with user {3}.

EVSESI564E0006	Error creating Elasticsearch client for bulk indexing operation.
Explanation	A connection to the Elasticsearc cluster could not be obtained.
Action	Check the status and health of the Elasticsearch cluster.

EVSESI564E0007	Error stopping bulk indexer for type: {0}
Explanation	Error stopping bulk indexer for type: {0}

EVSESI564E0008	Error creating Elasticsearch bulk indexing request.
Explanation	An error occurred when creating the bulk indexing request.
Action	Check the state and health of the Elasticsearch cluster.

EVSESI564E0009	Error executing Elasticsearch bulk indexing request.
Explanation	An error occurred when executing the indexing operation.
Action	Check the status and health of the Elasticsearch cluster.

EVSESI564E0010	Error creating Elasticsearch client; operation will be re-tried; Exception repeated {1} times.
Explanation	An error occurred when trying to connect to the Elasticsearch cluster.
Action	Check the state and health of the Elasticsearch cluster.

EVSESI564E0011	Unable to write internal persistence error event; defaulting to log file:%n {0}
Explanation	Unable to write internal persistence error event; defaulting to log file:%n {0}

EVSESI564E0012	Error storing internal persistence error event to Elasticsearch index
Explanation	Error storing internal persistence error event to Elasticsearch index

EVSESI564E0013	Exception encountered during auto registration of event type: {0}
Explanation	Exception encountered during auto registration of event type: {0}

EVSESI564E0014	Error creating bulk indexer for event type {0}; operation will be re-tried.
Explanation	An indexer could not be created to process the specified event type. This could be due to a failure to connect to the cluster for the required metadata.
Action	Check the status and healh of the cluster.

EVSESI564E0015	Error creating Elasticsearch client; operation will be re-tried.
Explanation	An error occurred when trying to connect to the Elasticsearch cluster.
Action	Check the state and health of the Elasticsearch cluster.

EVSESI564E0016	Error creating Elasticsearch bulk indexing request; operation will be re-tried.
Explanation	There was an error while creating the indexing request most likely due to a connectivity issue between the client and the server.
Action	Check the status and health of the cluster.

EVSESI564E0017	No acknowledgment received from Elasticsearch cluster after create index operation
Explanation	No acknowledgment received from Elasticsearch cluster after create index operation

EVSESI564E0018	No acknowledgment received from Elasticsearch cluster after type mapping operation
Explanation	No acknowledgment received from Elasticsearch cluster after type mapping operation

EVSESI564E0019	An Elasticsearch exception occurred while creating the type mapping
Explanation	An Elasticsearch exception occurred while creating the type mapping

EVSESI564E0020	Error executing Elasticsearch bulk indexing request; operation will be re-tried.
Explanation	There was an error while executing the indexing request most likely due to a connectivity issue between the client and the server.
Action	Check the status and health of the cluster.

EVSESI564E0021	Error creating or accessing indexer for event type: {0}
Explanation	An indexer could not be created to process the specified event type. This could be due to a failure to connect to the cluster for the required metadata.
Action	Check the status and healh of the cluster.

EVSESI564E0022	Error storing event of type: {0}
Explanation	The indexer could not persist the event of the specified event type. This could be due to a failure to connect to the cluster or an issue with the cluster health.
Action	Check the status and healh of the cluster.

EVSESI564E0023	Error creating or accessing indexer for event type: {0}; operation will be re-tried.
Explanation	An indexer could not be created to process the specified event type. This could be due to a failure to connect to the cluster for the required metadata.
Action	Check the status and healh of the cluster.

EVSESI564E0024	Error storing event of type: {0}; operation will be re-tried.
Explanation	The indexer could not persist the event of the specified event type. This could be due to a failure to connect to the cluster or an issue with the cluster health.
Action	Check the status and healh of the cluster.

EVSESI564E0027	Error retrieving Elasticsearch client for metadata verification
Explanation	Error retrieving Elasticsearch client for metadata verification

EVSESI564E0029	Error closing transport client connection to cluster {0}, index {1} on server {2} with user {3}
Explanation	Error closing transport client connection to cluster {0}, index {1} on server {2} with user {3}

EVSESI564E0030	The event persistence annotation is not recognized: {0}
Explanation	The event persistence annotation is not recognized: {0}

EVSESI564E0031	Error retrieving normalized type from component for event type: {0}
Explanation	Error retrieving normalized type from component for event type: {0}

EVSESI564E0032	Error generating cache key for resource
Explanation	Error generating cache key for resource

EVSESI564E0033	Error creating bulk indexer for event type: {0}
Explanation	Error creating bulk indexer for event type: {0}

EVSESI564E0034	Error creating Elasticsearch client for indexing request.
Explanation	A connection to the Elasticsearc cluster could not be obtained.
Action	Check the status and health of the Elasticsearch cluster.

EVSESI564E0035	Validation of dynamic service configuration failed. Event can not be persisted%nHeader: %s%nBody: %s
Explanation	Validation of dynamic service configuration failed. Event can not be persisted%nHeader: %s%nBody: %s

EVSESI564E0036	Error initialising internal resources for provider; operation will be re-tried. Exception repeated {0} times
Explanation	Error initialising internal resources for provider; operation will be re-tried. Exception repeated {0} times

EVSESI564E0037	Error creating bulk indexer for event type {0}; operation will be re-tried; Exception repeated {1} times
Explanation	Error creating bulk indexer for event type {0}; operation will be re-tried; Exception repeated {1} times

EVSESI564E0038	Error creating Elasticsearch bulk indexing request; operation will be re-tried; Exception repeated {1} times
Explanation	Error creating Elasticsearch bulk indexing request; operation will be re-tried; Exception repeated {1} times

EVSESI564E0039	Error executing Elasticsearch bulk indexing request; operation will be re-tried; Exception repeated {1} times
Explanation	Error executing Elasticsearch bulk indexing request; operation will be re-tried; Exception repeated {1} times

EVSESI564E0040	An exception occurred while checking the cluster for the specified destination index: {0}
Explanation	An exception occurred while checking the cluster for the specified destination index: {0}

EVSESI564E0041	An Elasticsearch exception occurred while creating the specified destination index: {0}
Explanation	An Elasticsearch exception occurred while creating the specified destination index: {0}

EVSESI564E0042	An error occurred while attempting to determine if auto-registration is required for type: {0} in index: {1}
Explanation	An error occurred while attempting to determine if auto-registration is required for type: {0} in index: {1}

EVSESI564E0043	Error preparing indexing request or processing response - id: {0} document type: {1}
Explanation	An error occurred when creating or processing the index request required to persist the event. This could be due to an issue with the cluster.
Action	Check the status and health of the cluster.

EVSESI564I0004	Elasticsearch transport client successfully connected to cluster {0}, index {1} on server {2} with user {3}
Explanation	Elasticsearch transport client successfully connected to cluster {0}, index {1} on server {2} with user {3}

EVSESI564I0028	Elasticsearch transport client successfully disconnected from cluster {0}, index {1} on server {2} with user {3}
Explanation	Elasticsearch transport client successfully disconnected from cluster {0}, index {1} on server {2} with user {3}

EVSESI564W0025	Task manager queue is full; The operation will be re-tried
Explanation	Task manager queue is full; The operation will be re-tried

EVSESI564W0026	Thread interrupted while waiting for task re-submission
Explanation	Thread interrupted while waiting for task re-submission

EVSEUPE0004	The destination file does not exist, failed creating configuration directory: ''{0}''.
Explanation	The destination file does not exist, failed creating Digital event Persistence configuration directory.

EVSEUPE0008	Problem occurred during unmarshalling file: ''{0}''. Aborting migration of this file.
Explanation	Problem occurred during unmarshalling given file. Aborting migration of this file.

EVSEUPE0010	The destination file exists: ''{0}''. Migrating from source to destination.
Explanation	The destination file exists. Migrating from source to destination.

EVSEUPE0011	Problem occurred during marshalling file: ''{0}''. Aborting migration of this file.
Explanation	Problem occurred during marshalling given file. Aborting migration of this file.

EVSEUPE0012	Not supported Digital Event Persistence Service Type: {0}
Explanation	Not supported Digital Event Persistence Service Type.

EVSEUPI0000	Migrating Digital Event Persistence service configurations.
Explanation	Migrating Digital Event Persistence service configurations.

EVSEUPI0001	The source directory exists: ''{0}''.
Explanation	The given source directory exists.

EVSEUPI0002	The source directory does not exist: ''{0}''. Nothing to migrate.
Explanation	The source directory does not exist. Nothing to migrate.

EVSEUPI0003	The destination directory exists: ''{0}''. Migrating from source to it.
Explanation	The given destination directory exists. Migrating from source to it.

EVSEUPI0005	No Digital Event Persistence Service json files found under source directory: ''{0}''.
Explanation	No Digital Event Persistence Service json files found under source directory.

EVSEUPI0006	Migrating Digital Event Persistence service: ''{0}''
Explanation	Migrating Digital Event Persistence service.

EVSEUPI0007	Migrating file: ''{0}''.
Explanation	Migrating given file.

EVSEUPI0009	The destination file exists: ''{0}''. Migrating from source to destination.
Explanation	The destination file exists. Migrating from source to destination.

EVSEVCE0000	No transformer found for type: {0}
Explanation	No transformer of the required type, for example XML could be found.

EVSEVEE0000

Elasticsearch transport client successfully connected to cluser {0}, index {1} on server {2}, port {3} with user {4}

EVSEVEE0001

Failed creating Elasticsearch transport client to connect to cluser {0}, index {1} on server {2}, port {3} with user {4}

EVSEVEE0002

Elasticsearch transport client is not started to connect to cluser {0}, index {1} on server {2}, port {3} with user {4}.

EVSEVEE0003

Error retrieving Elasticsearch client from pool

EVSEVEE0004

Error checking for existing type in Elasticsearch index

EVSEVEE0005

Exception encountered auto registration of event type: {0}

EVSEVEE0006

Event Routing Consumers are not supported by this Endpoint implementation

EVSEVEE0007

Synchronous Event processing is not supported by this component.

EVSEVEE0008

Error transforming event instance from native format to JSON format

EVSEVEE0009

Error initializing required internal resources

EVSEVEE0010

Error retrieving Elasticsearch client from pool during bulk indexing task

EVSEVEE0011

Error creating Elasticsearch bulk indexing request

EVSEVEE0012

Error executing Elasticsearch bulk indexing request

EVSEVEE0013

Unable to write internal persistence error event defaulting to log file:%s {0}

EVSEVEE0014

Error storing internal persistence error event to Elastisearch

EVSEVEE0015

Error loading metadata for persistence error type; logging to local file

EVSEVEE0017

Elasticsearch transport client not started for cluster {0}, index {1} on server {2} with user {3}.

EVSEVEE0019

Elasticsearch transport client successfully connected to cluster {0}, index {1} on server {2} with user {3}

EVSEVEE0020

Failed to create Elasticsearch transport client connection to cluster {0}, index {1} on server {2} with user {3}

EVSEVEE0021	Not Compliant JMX MBean, cannot create MBean {0}.
Explanation	Failed to create Elasticsearch JMX MBean

EVSEVEE0023	An internal error occurred during schema processing operations
Explanation	This error is most likely due to incorrect wiring of the ETS/XSD services

EVSEVEI0022

EVSEVEW0016	Task manager queue is full; The operation will be re-tried
Explanation	The work queue has reached its maximum size.

EVSEVEW0018

Thread interrupted while waiting for task re-submission

EVSEVHE0000	Hive table could not be found or created for Event Type {0}
Explanation	Hive table could not be found or created in event store instance

EVSEVHE0001	Error loading Hive table from event store instance
Explanation	Error loading Hive table from event store instance

EVSEVHE0002	Failed to generate HDFS URI ({0})
Explanation	Failed to generate HDFS URI based on the configuration parameters.
Action	Inspect configuration parameters defined in Command Central's UI.

EVSEVHE0003	Failed to generate Hive URI ({0})
Explanation	Failed to generate Hive URI based on the configuration parameters set.
Action	Inspect the configuration parameters defined in Command Central's UI.

EVSEVHE0004	Error creating HDFS Producer for Event Type: {0}
Explanation	Error creating HDFS Producer

EVSEVHE0005	Event could not be processed by HDFS producer
Explanation	Event could not be processed by HDFS producer

EVSEVHE0006	Unable to create or locate Hive persistence errors table; defaulting to log file
Explanation	Unable to create or locate Hive persistence errors table

EVSEVHE0007	Unable to write internal persistence error event; defaulting to log file
Explanation	Unable to write internal persistence error event

EVSEVHE0008	Synchronous Event processing is not supported by this component.
Explanation	Event Persistence components only support asynchronous event processing.

EVSEVHE0009	Consumers are not supported by the HDFS Endpoint
Explanation	The EVP HDFS Component only supports producers for event persistence

EVSEVHE0010	Error encountered during batch processing.
Explanation	An errror occured during batch processing. Possible network connection failure.
Action	Check your network connection.

EVSEVHE0011	Ping Hive Server {0} failed.
Explanation	Hive Server is not available.

EVSEVHE0012	Ping NameNode {0} failed.
Explanation	Cannot access the NameNode.

EVSEVHE0013	Not Compliant JMX MBean, cannot create MBean {0}.
Explanation	Not Compliant JMX MBean.

EVSEVHE0015	An internal error occurred during schema processing operations
Explanation	This error is most likely due to incorrect wiring of the ETS/XSD services

EVSEVHE0016	Error transforming event instance from native format to JSON format
Explanation	The XML event could not be transformed to JSON possibly due to invalid content

EVSEVHI0014	Successfully created Hadoop Connectivity JMX MBean {0}.
Explanation	Hadoop Connectivity JMX MBean created.

EVSEVJE0002

JDBC Database Type not supported: {0}

EVSEVJE0003	Error Starting JDBC Component ({0})
Explanation	The EVP JDBC Component could not be started

EVSEVJE0004	Error Stopping JDBC Component ({0})
Explanation	An internal error occurred when stopping the JDBC Component

EVSEVJE0005	Error creating JDBC Producer for event type: {0}
Explanation	The EVP JDBC Endpoint could not create a Producer for the given event type.

EVSEVJE0006	Consumers are not supported by the JDBC Endpoint
Explanation	The EVP JDBC Component only supports producers for event persistence

EVSEVJE0007	No metadata found for event type: {0}
Explanation	No JDBC metadata was found for the given event type.

EVSEVJE0008	Database exception while searching for event metadata!
Explanation	The metadata lookup failed with a database exception.

EVSEVJE0009	Unable to write internal persistence error event defaulting to log file %n%n{0}
Explanation	The PersistenceError event could not be written to the store.

EVSEVJE0011	Unexpected error during database rollback operation
Explanation	The database system reported an exception while performing the rollback

EVSEVJE0012	Error encountered during batch processing! Number of batched events: {0}
Explanation	An error was reported while writing the events to the persistence store.

EVSEVJE0013	Event could not be processed by producer
Explanation	An error occurred during event processing by this producer.

EVSEVJE0014	Synchronous Event processing is not supported by this component.
Explanation	Event Persistence components only support asynchronous event processing.

EVSEVJI0000

JDBC Connection Pool {0}{1} started with initial size of {2} and max size of {3}

EVSEVJI0001

JDBC Connection Pool closed

EVSEVJW0010	No metadata found for persistence error logger; defaulting to local log files!
Explanation	The metadata for the internal persistence error event type was not found in the store.

EVSEVPE0000	Error Connecting ParStream Server for host: {0}, port: {1} and user: {2}.
Explanation	Error Connecting to ParStream Streaming Server.
Action	Please make sure that the database server is up and running.

EVSEVPE0001

No metadata found for event type: {0}

EVSEVPE0002	AutoRegistration failed for Event Type with NameSpace {0} : EventType {1}
Explanation	Check Database status and connection

EVSEVPE0003	Database exception while searching for event metadata!
Explanation	Database exception while searching for event metadata!

EVSEVPE0004	Synchronous Event processing is not supported by this component.
Explanation	Synchronous Event processing is not supported by this component.

EVSEVPE0005	Error Starting ParStream Streaming Component for host: {0} and port: {1}
Explanation	Error Starting ParStream Streaming Component for host: {0} and port: {1}

EVSEVPE0006	Error Stopping ParStream Component for host: {0} and port: {1}
Explanation	Error Stopping ParStream Component

EVSEVPE0007	Unexpected error during database rollback operation
Explanation	Unexpected error during database rollback operation

EVSEVPE0008	Error encountered during batch processing! Number of batched events: {0}
Explanation	Error encountered during batch processing!

EVSEVPE0009	Unable to write internal persistence error event, defaulting to log file %n%n{0}
Explanation	Unable to write internal persistence error event defaulting to log file.

EVSEVPE0010	Cannot get metadata information for event namespace {0} and type {1}.
Explanation	Cannot get metadata information for the event type.

EVSEVPE0011	Error creating ParStream Producer for event type: {0}
Explanation	Error creating ParStream Producer for event type.

EVSEVPW0000	No metadata found for persistence error logger; defaulting to local log files!
Explanation	No metadata found for persistence error logger; defaulting to local log files!

EVSHQF530E0000	A error occurred when trying to instantiate the Hive CDH5.3.0 Query Session implementation class.
Explanation	The factory implementation could not create an instance of the query session class.
Action	Contact Global Support.

EVSHQF530E0001	Query implementation library found in multiple locations: {0}
Explanation	The implementation library was found in multiple locations on the server or installation directory. In this situation, the factory cannot determine the proper installation directory based on the library location.
Action	Contact Global Support.

EVSHQF530E0002	Could not find query implementation library while determining installation directory.
Explanation	In Non-OSGi environments the factory loads its third-party dependencies from a whitelist. It must first determine the installation directory. This is done by searching for the implementation jar in the Software_AG_Directory/common/EventPersistence folder. This error indicates that that library could not be found.
Action	Contact Global Support.

EVSHQF530E0003	The property dep.common.dir is set to a non-existent directory: {0}
Explanation	The system property dep.common.dir must be set to a valid Software_AG_Directory/common/EventPersistence directory location.
Action	Contact Global Support.

EVSHQF530E0004	The property dep.common.dir has not been set prior to using this component.
Explanation	The system property dep.common.dir is required and must be set to the location of the Software_AG_Directory/common/EventPersistence directory.
Action	Contact Global Support.

EVSHQI530E0000	Hive query execution failed with unexpected exception
Explanation	An unexpected exception occurred during the execution of the Hive query

EVSHQI530E0001	Error transforming common query for explain plan
Explanation	An error occurred when transforming the common query to native format for the explain plan

EVSHQI530E0002	An unsupported encoding exception was thrown while generating explain message
Explanation	The default encoding of utf-8 is required when creating the explain plan

EVSHQI530E0003	Failed to close hive JDBC result set
Explanation	An exception was thrown during the close method on the JDBC result set

EVSHQI530E0004	Failed to close hive JDBC statement
Explanation	An exception was thrown when closing the JDBC statement

EVSHQI530E0007	The context did not contain the required parameters
Explanation	The context parameters for the specified session were invalid.

EVSHQI530E0008	Error creating Hive SQL query in the current session.
Explanation	Could not create a JDBC connection and or Hive Query using the current session.

EVSHQI530E0009	Full text query not supported by this implementation.
Explanation	This query implementation does not support full text queries.

EVSHQI530E0010	Error closing current Hive JDBC connection.
Explanation	An exception was thrown when the close method of the connection was invoked.

EVSHQI530E0011	Error initializing Hive JDBC connection.
Explanation	An error occurred when creating the Hive JDBC connection

EVSHQI530E0012	Error setting default database in Hive JDBC connection.
Explanation	An exception was thrown when issuing the use database statement

EVSHQI530E0013	Error closing active Hive JDBC statement.
Explanation	An exception was thrown during the close invocation on the current JDBC statement.

EVSHQI530E0014	Failed to position cursor at next event in the result stream
Explanation	An error occurred when advancing the cursor in the result set.

EVSHQI530E0015	The method {0} is unsupported in this implementation of ResultStream
Explanation	Implementors of the result stream must implement the next method; the other positional methods are optional.

EVSHQI530E0016	Error getting result at current cursor position from handler
Explanation	An error occurred when retrieving the event data from the current cursor position.

EVSHQI530E0017	Error closing Hive JDBC result set on close of result stream.
Explanation	The JDBC result set could not be closed when closing the result stream.

EVSHQI530E0018	Property '{0}' in group by expression must appear in select expression
Explanation	A property specified in the group by clause is not present in the select list

EVSHQI530E0019	Property '{0}' in select expression must appear in group by expression
Explanation	A property in the select expression is not present in the group by clause

EVSHQI530E0020	Property '{0}' in order by expression must appear in select and group by expression
Explanation	A property specified in the order by expression is not present in the select expression

EVSHQI530I0005	Inbound query in common syntax form:
Explanation	Label for the explan plain

EVSHQI530I0006	Outbound query in native form:
Explanation	Explain plan label

EVSHQIE0000	Unsupported date time format in string literal: {0}.
Explanation	Unsupported date time format in string literal

EVSHQIE0001	Hive query execution failed.
Explanation	Hive query execution failed.

EVSHQIE0002	Failed to close result set.
Explanation	Failed to close result set.

EVSHQIE0003	Failed to close statement.
Explanation	Failed to close statement.

EVSHQIE0004	HiveQuerySession initialize JDBC Connection failed.
Explanation	HiveQuerySession initialize JDBC Connection failed.

EVSHQIE0005	Close Connection failed.
Explanation	Close Connection failed.

EVSHQIE0007	Result cannot be formated to JSON. format
Explanation	Result cannot be formated to JSON format.

EVSHQIE0008	Failed get next result.
Explanation	Failed get next result.

EVSHQIE0009	Cannot create connection statement.
Explanation	Cannot create connection statement.

EVSHQIE0010

Failed to create {0}

EVSHQIE0011	Property ''{0}'' in group by expression must appear in select expression
Explanation	Group by property is required to appear in select expression

EVSHQIE0012	Property ''{0}'' in select expression must appear in group by expression
Explanation	Property in select expression must appear in the group by expression

EVSHQIE0013	Property ''{0}'' in order by expression must appear in select and group by expression
Explanation	Property in order by expression must be included in the group by and select expression

EVSHQIE0014	Full text query not supported by this implementation
Explanation	This query implementation does provide full text search capabilities

EVSHQIE0015

Error transforming query for explain plan

EVSHQIE0016

An unsupported encoding exception was thrown while generating explain message

EVSHQII0006	Method: {0} is not supported.
Explanation	Method is not supported.

EVSHQII0017

Inbound query in common syntax form:

EVSHQII0018

Outbound query in native form:

EVSHSF530E0000	A error occurred when trying to instantiate the HDFS 5.3.0 Storage Provider implementation.
Explanation	The factory could not create an instance of the storage provider implementation. This error could be related to feature provisioning or a class path issue.
Action	Contact Global Support.

EVSHSF530E0001	Could not find storage provider implementation library to determine installation directory.
Explanation	In Non-OSGi environments the factory loads its third party dependencies from a white-list. It must first determine the installation directory. This is done by searching for the implementation jar in the common Event Persistence folder. This error indicates that that library could not be found.
Action	Verify that the Digital Event Persistence libraries were selected during the installation.

EVSHSF530E0002	Storage provider implementation library found in multiple locations: {0}
Explanation	The implementation library was found in multiple locations on the server or installation directory. In this situation, the factory can not determine the proper installation directory based on the library location.
Action	Check the installation directory.

EVSHSF530E0003	The property dep.common.dir is set to a non-existent directory: {0}
Explanation	The system property dep.common.dir must be set to a valid Software_AG_Directory/common/EventPersistence directory location.
Action	Contact Global Support.

EVSHSF530E0004	The property dep.common.dir has not been set prior to using this component.
Explanation	The system property dep.common.dir is required and must be set to the location of the Software_AG_Directory/common/EventPersistence directory.
Action	Contact Global Support.

EVSHSI530E0000	Process method called before storage provider was started
Explanation	The storage provider was not initialized and a call was made to process an event.

EVSHSI530E0001	Error initializing required internal resources for provider
Explanation	The required internal resources for the storage provider couldn't be initialized.

EVSHSI530E0002	Error creating or accessing HDFS processor for event type: {0}
Explanation	An HDFS processor for the given event type could not be accessed or instantiated.

EVSHSI530E0003	Error stopping resource {0} on storage provider shutdown
Explanation	An exception was through when stopping an internal resource on provider shutdown.

EVSHSI530E0004	Error closing HDFS Writer instance on processor shutdown
Explanation	The HDFS writer and stream threw an exception on close.

EVSHSI530E0005	Unexpected error encountered during batch processing.
Explanation	There was an HDFS or Hive error encounted during the processing of an event batch.

EVSHSI530E0006	Error processing batch during execution of auto-write task.
Explanation	An unexpected exception was thrown during batch processing.

EVSHSI530E0007	Error processing batch during execution of on-demand task
Explanation	An expected exception was thrown during batch processing

EVSHSI530E0008	Error starting HDFS processor resource for event type: {0}
Explanation	An error was thrown when initializing and starting the HDFS processor.

EVSHSI530E0009	Error stopping HDFS processor for event type: {0}
Explanation	An unexpected error occurred during the shutdown of the HDFS processor

EVSHSI530E0010	Error creating HDFS processor for event type: {0}
Explanation	An internal error occurred during the creation of the HDFS processor

EVSHSI530E0011	Unsupported encoding error converting text event to byte stream
Explanation	The event instance was formatted in an encoding other than the default of utf-8

EVSHSI530E0012	Error streaming event data to HDFS output stream
Explanation	An error occurred while writing the event data to the HDFS file system.

EVSHSI530E0013	Error flushing and closing the HDFS file stream
Explanation	The HDFS I/O stream could not be flushed and closed.

EVSHSI530E0014	Error closing HDFS file system reference
Explanation	The HDFS file system reference throw an unexpected exception during the close method call

EVSHSI530E0015	Error creating HDFS file system reference
Explanation	An unexpected exception was thrown when closing the HDFS file system.

EVSHSI530E0016	Hive table could not be found or created for event type: {0}
Explanation	The Hive table does not exist and or could not be created by the Hive metadata manager

EVSHSI530E0017	Error loading Hive table data or performing auto registration for event type: {0}
Explanation	An error accessing the Hive metadata or creating the Hive metadata for the specified event type occurred.

EVSHSI530E0018	Unable to create or find Hive persistence error table; defaulting to log file:%n {0}
Explanation	The Hive metadata table for the event persistence error type could not be found or created. Errors will be logged to the error log.

EVSHSI530E0019	Error retrieving root schema tree element children from parser
Explanation	The child nodes of the schema element tree root could not be accessed.

EVSHSI530E0020	Error parsing schema for event type: {0} in namespace {1}
Explanation	The event type definition for the given event type and namespace could not be parsed by the schema parser.

EVSHSI530E0021	Generated Hive event table name exceeds 255 character size limit: {0}
Explanation	Table names in Hive are limitted to 255 characters; The unique table name generated for the event type and namespace exceeded this limit.

EVSHSI530E0022	Error creating Hive database table field definitions
Explanation	An expected error occurred when parsing the schema tree and creating the database table and field definitions

EVSHSI530E0023	Error creating Hive database table structure definition
Explanation	An unexpected error occurred when generating the Hive table structure

EVSHSI530E0024	Error creating Hive database table definition
Explanation	An unexpected error occurred when generating the Hive metadata table definition.

EVSHSI530E0025	Error filtering non-mappable nodes from root schema element tree
Explanation	There are certain binary type properties supported in events; these are filtered out of the stored event. An unexpected error occurred when trying to filter these nodes.

EVSHSI530E0027	Ping to Apache Hive Server {0} failed.
Explanation	Could not ping an active hive server for metadata operations

EVSHSI530E0028	Ping to Apache Hadoop Name Node {0} failed.
Explanation	Failed to connect to primary name node for file system access.

EVSHSI530E0031	Error disconnecting from Apache Hive database: {0} at host: {1} port: {2} and user: {3}
Explanation	An error occurred when disconnecting from the hive database

EVSHSI530E0034	Error retrieving normalized type from component for event type: {0}
Explanation	An exception was thrown by the component when generating the normalized type for the event type

EVSHSI530E0035	An exception was thrown whilst stopping an HDFS error event writer: {0}
Explanation	During shutdown of the HDFS error logger an exception was thrown when closing the writer for the given target and event type.

EVSHSI530E0036	Validation of dynamic service configuration against provided values failed
Explanation	A dynamic service configuration was provided but the variables are not present in the event.

EVSHSI530E0037	Unexpected exception encountered during batch processing; operation will be re-tried. Exception repeated {0} times.
Explanation	An exception occurred while writing the events to the HDFS file system. The operation will be re-tried until successful.
Action	Check the status of the HDFS cluster.

EVSHSI530E0038	Unexpected exception on HDFS file system close call during hard reset
Explanation	An exception was thrown when closing the file system reference after write exception.

EVSHSI530E0039	Error initialising internal resources for provider; operation will be re-tried. Exception repeated {0} times
Explanation	Internal initialisation failed. The operation will be retried until successful or the component is restarted.

EVSHSI530E0040	Error creating processor for event type {0}; operation will be re-tried; Exception repeated {1} times.
Explanation	A processor could not be created to process the specified event type. This could be due to a failure to connect to Hive for the required metadata.
Action	Check the health of the Hive server and HDFS cluster.

EVSHSI530E0041	Validation of dynamic service configuration failed. Event can not be persisted: Header: {0} Body: {1}
Explanation	The values required for using a dynamic configuration were not supplied in the event being processed.

EVSHSI530E0042	Error create Hive MetaData table for performing auto registration for type: {0}
Explanation	Create Hive MetaData Table error.

EVSHSI530E0043	Error streaming event data to HDFS file system in table directory: {0}
Explanation	An error occurred when writing to the event types data file in HDFS.
Action	Check the status of the Hadoop HDFS file system.

EVSHSI530E0044	Error creating processor for event type {0}; operation will be re-tried.
Explanation	A processor could not be created to process the specified event type. This could be due to a failure to connect to Hive for the required metadata.
Action	Check the health of the Hive server and HDFS cluster.

EVSHSI530E0045	Unexpected exception was encountered during batch processing; operation will be re-tried.
Explanation	An exception occurred while writing the events to the HDFS file system. The operation will be re-tried until successful.
Action	Check the status of the HDFS cluster.

EVSHSI530E0046	Error storing event of type {0}
Explanation	The event could not be wrtten to the HDFS file system.
Action	Check the health of the HDFS cluster.

EVSHSI530E0047	Error storing event of type {0}; operation will be re-tried.
Explanation	The event could not be wrtten to the HDFS file system. The cluster could be down or unreachable. The operation will be retried until successful or until the service is shut down.
Action	Check the health of the HDFS cluster.

EVSHSI530I0026	Successfully created JMX MBean for Hadoop Connectivity: {0}
Explanation	The monitoring MBean was successfully created

EVSHSI530I0029	Connected to Apache Hive database: {0} at host: {1} port: {2} and user: {3}
Explanation	Info message on connection to hive database

EVSHSI530I0030	Disconnected from Apache Hive database: {0} at host: {1} port: {2} and user: {3}
Explanation	Info message on database disconnect

EVSHSI530I0032	Connected to Apache HDFS File System specified by URI: {0}
Explanation	Info message logged on connect to HDFS file system

EVSHSI530I0033	Disconnected from Apache HDFS File System specified by URI: {0}
Explanation	Info message logged on disconnect from HDFS file system

EVSJCOE0000	An invalid column index was passed into the accessor method: {0}
Explanation	Column indices range from 1 to n. The client has passed an index into the accessor methods that is outside this range.

EVSJCOE0001	An invalid column label was passed into the accessor method: {0}
Explanation	The client has passed a column label into the accessor method that does not exist in this result set.

EVSJCOE0002	The specified feature is not supported by this driver or data source: {0}
Explanation	The invoked method is not supported by the driver or data source. Only a subset of the JDBC API are required to be supported.

EVSJCOE0003	Column data at index or specified label is not integral: (0}
Explanation	A numeric column accessor method was called but the value is not a numeric.

EVSJCOE0004	Column data at index or for specified label is not a floating point number: {0}
Explanation	A decimal column accessor method was called but the value is not a floating point number.

EVSJDRE0000	No driver or data source implementation found for scheme: {0}
Explanation	The driver implementation is dynamically loaded based on the scheme in the database URL. This message indicates that there is no implementation class for the specified schema.

EVSJDRE0001	The specified feature is not supported by this driver or data source: {0}
Explanation	The invoked method is not supported by the driver or data source. Only a subset of the JDBC API are required to be supported.

EVSJDRE0002	Error loading dynamic library white list from resource:
Explanation	The resource containing a white list of dynamically loaded run-time libraries could not be loaded.

EVSJDRE0003	Error creating class loader and loading white listed run-time libraries
Explanation	There as an error when creating the classloader and loading the classes contained in the white listed libraries.

EVSJDRE0004	Error creating instance of the driver or data source implementation class:
Explanation	The driver implementation class could not be instantiated using the custom class loader and dynamically loaded library classes.

EVSJDRE0005	The driver or data source installation directory is a required property but has not been set.
Explanation	The driver dynamically loads the implementation and run-time libraries based on the database URL. For this to function correctly the location of the driver installation must be provide.

EVSJDRE0006	The databaseURL property has not been set for this data source
Explanation	An attempt was made to retrieve a connection from the data source without setting the database location.

EVSJDRE0007	No parameters found in JDBC URL query string: {0}
Explanation	The JDBC URL contains a query string marker "?" but has no parameters.
Action	Correct the JDBC URL and ensure that the required parameters are specified correctly.

EVSJDRE0008	The specified query parameter has no associated value: {0}
Explanation	The JDBC URL contains a query string that includes one or more parameters with no associated values.
Action	Correct the JDBC URL and ensure that all query parameters have valid values.

EVSJDRE0009	The installDir property is set to a non-existent directory location.
Explanation	The installDir property points to a directory that does not exist.
Action	Verify the location of the JDBC driver installation and update the client settings.

EVSJDRE0010	The installDir directory location points to an invalid driver distribution.
Explanation	The installDir property points to a directory that does not contain the driver distribution.
Action	Verify the location of the JDBC driver installation and update the client settings.

EVSJDRE0011	Error loading dynamic library white list from resource: {0}
Explanation	The resource containing a white list of dynamically loaded run-time libraries could not be loaded.

EVSJDRE0012	Error creating instance of the driver or data source implementation class: {0}
Explanation	The driver implementation class could not be instantiated using the custom class loader and dynamically loaded library classes.

EVSJDRE0013	The installDir property is set to a non-existent directory location: {0}
Explanation	The installDir property points to a directory that does not exist.
Action	Verify the location of the JDBC driver installation and update the client settings.

EVSJDRE0014	The installDir directory location points to an invalid driver distribution: {0}
Explanation	The installDir property points to a directory that does not contain the driver distribution.
Action	Verify the location of the JDBC driver installation and update the client settings.

EVSJEDI232E0000	The specified feature is not supported by this driver or data source: {0}
Explanation	The invoked method is not supported by the driver or data source. Only a subset of the JDBC API are required to be supported.

EVSJEDI232E0001	This connection implementation provides no wrapper interfaces
Explanation	The connection implementation does not support the unwrap feature declared in the Wrapper interface.

EVSJEDI232E0002	The required properties for this data source have not be set prior to creating the connection
Explanation	Prior to creating a connection through the data source the various setter methods should be invoked to initialize the data source.

EVSJEDI232E0003	An error occurred when creating a connection to the Elasticsearch cluster.
Explanation	The transport client could not be created during construction of the connection.
Action	Check the database URL and verify that the cluster is available

EVSJEDI232E0004	Error converting Elasticsearch mapping metadata to JSON format
Explanation	The Elasticsearch metadata response could not be marshalled into JSON format.

EVSJEDI232E0005	An invalid column index was passed into the accessor method: {0}
Explanation	Column indices range from 1 to n. The client has passed an index into the accessor methods that is outside this range.

EVSJEDI232E0006	Column data at index or specified label is not integral: {0}
Explanation	A numeric column accessor method was called but the value is not a numeric.

EVSJEDI232E0007	Column data at index or for specified label is not a floating point number: {0}
Explanation	A decimal column accessor method was called but the value is not a floating point number.

EVSJEDI232E0008	An invalid column label was passed into the accessor method: {0}
Explanation	The client has passed a column label into the accessor method that does not exist in this result set.

EVSJEDI232E0009	Column data at index or for specified label is not a valid timestamp: {0}
Explanation	A timestamp column accessor method was called but the value is not a valid timestamp

EVSJEDI232E0010	Column data at index or for specified label is not a valid date: {0}
Explanation	A date column accessor method was called but the value is not a valid date

EVSJEDI232E0011	Column data at index or for specified label is not a valid time field: {0}
Explanation	A time column accessor method was called but the value is not a valid time field

EVSJEDI232E0012	No corresponding index exists for the specified catalog: {0}
Explanation	There is a one to one relationship between the SQL catalog and Elasticsearch index in the persistence framework. A method taking a catalog parameter was called but no such index exists in the Elasticsearch cluster.

EVSJEDI232E0013	This driver or data source only supports SQL queries
Explanation	The JDBC driver for Event Persistence is provided for basic queries against non-SQL data stores.

EVSJEDI232E0014	The specified column name "{0}" does not exist in table; available columns are: {1}
Explanation	The SQL query specified an invalid column name in the column list, where clause, order by clause, or group by clause.
Action	Correct the SQL query statement.

EVSJEDI232E0015	Error transforming SQL query into a native Elasticsearch request%n{0}
Explanation	The SQL query could not be turned into an Elasticsearch search request.
Action	Verify the syntax of the issued query and revise as needed.

EVSJEDI232E0016	Error executing native Elasticsearch search request%n{0}
Explanation	An error occurred while executing the native Elasticsearch search request.
Action	Check that the cluster is available and in good health.

EVSJEDI232E0017	The index represented by the specified catalog does not exist: {0}
Explanation	An SQL query was issued but there is no corresponding index on the cluster
Action	Check your query and the available indices on the cluster.

EVSJEDI232E0018	The type represented by the specified table does not exist: {0}
Explanation	An SQL query was issued but there is no corresponding type available in the index.
Action	Check your query and the available indices on the cluster.

EVSJEDI232E0019	Unexpected statement type found while trying to determine the appropriate query builder implementation
Explanation	Different builder classes are used to transform the SQL query into various Elasticsearch search requests. The implementation is selected based on the presence of aggregate functions or column list expressions. In this case, neither was found.
Action	Check your SQL query syntax.

EVSJEDI232E0020	Error incrementing result cursor or accessing query result data
Explanation	The result cursor could not be advanced to the next position.
Action	This can occur if the cluster goes down and the client tries to access the next batch. Check the cluster health.

EVSJEDI232E0021	Error setting fetch direction on forward only result set.
Explanation	This jdbc driver provides foward only result sets. A client attempted to set a fetch direction other than forward.
Action	Correct the client logic.

EVSJEDI232E0022	An error has occurred because the response reference has not been set in response handler
Explanation	This is a programming error in the implementation logic; the response must be set before using the handler.
Action	Correct the programming error.

EVSJEDI232E0023	No matching parameter marker found for given index: {0}
Explanation	The client invoked a set method on the prepared statement for which there was no marker. For example, setting parameter 2 on a statement with only one marker.
Action	Correct the program logic.

EVSJEDI232E0024	No corresponding value found for the marker at parameter index: {0}
Explanation	A parameter marker was specified in the query but no value was set prior to executing the statement.
Action	Correct the program logic by invoking the appropriare set method on the prepared statement.

EVSJEDI232E0025	The position {0} declared in the order by clause does not match a valid column or alias defined in the select statements column or aggregate list
Explanation	The order by clause specifies an integer position that does not match a value in the select expressions column list.
Action	Review the statement and correct the column list expression or the order by clause.

EVSJEDI232E0026	No column matching the specified label was found in this result set: {0}
Explanation	The findColumn method was invoked with a non-existent column label.
Action	Specify a correct column label when invoking the method.

EVSJEDI232E0027	Column type at index or for the specified label is not a JDBC timestamp: {0}
Explanation	A getTimestamp, getTime or getDate accessor method was called for an incorrect column type. These methods are only valid for JDBC timestamp columns.
Action	Update the program logic to use the appropriate accessor method.

EVSJEDI232E0028	The specified database URL is not in a valid format for this driver or datasource: {0}
Explanation	The JDBC URL contains an invalid format for the given driver or data source.
Action	Consult the JDBC Driver documentation for the appropriate URL format.

EVSJEDI564E0000	The specified feature is not supported by this driver or data source: {0}
Explanation	The invoked method is not supported by the driver or data source. Only a subset of the JDBC API are required to be supported.

EVSJEDI564E0001	No corresponding index exists for the specified catalog: {0}
Explanation	There is a one to one relationship between the SQL catalog and Elasticsearch index in the persistence framework. A method taking a catalog parameter was called but no such index exists in the Elasticsearch cluster.

EVSJEDI564E0002	The required properties for this data source have not be set prior to creating the connection
Explanation	Prior to creating a connection through the data source the various setter methods should be invoked to initialize the data source.

EVSJEDI564E0003	An error occurred when creating a connection to the Elasticsearch cluster.
Explanation	The transport client could not be created during construction of the connection.
Action	Check the database URL and verify that the cluster is available.

EVSJEDI564E0004	Error converting Elasticsearch mapping metadata to JSON format
Explanation	The Elasticsearch metadata response could not be marshalled into JSON format.

EVSJEDI564E0005	An invalid column index was passed into the accessor method: {0}
Explanation	Column indices range from 1 to n. The client has passed an index into the accessor methods that is outside this range.

EVSJEDI564E0006	Column data at index or specified label is not integral: {0}
Explanation	A numeric column accessor method was called but the value is not a numeric.

EVSJEDI564E0007	Column data at index or for specified label is not a floating point number: {0}
Explanation	A decimal column accessor method was called but the value is not a floating point number.

EVSJEDI564E0008	An invalid column label was passed into the accessor method: {0}
Explanation	The client has passed a column label into the accessor method that does not exist in this result set.

EVSJEDI564E0009	Column data at index or for specified label is not a valid timestamp: {0}
Explanation	A timestamp column accessor method was called but the value is not a valid timestamp

EVSJEDI564E0010	The specified column name "{0}" does not exist in table; available columns are: {1}
Explanation	The SQL query specifies an invalid column name in the column list, where clause, order by clause, or group by clause.
Action	Correct the SQL query statement.

EVSJEDI564E0011	No corresponding value found for the marker at parameter index: {0}
Explanation	A parameter marker was specified in the query but no value was set prior to executing the statement.
Action	Correct the program logic by invoking the appropriare set method on the prepared statement.

EVSJEDI564E0012	Error transforming SQL query into a native Elasticsearch request%n{0}
Explanation	The SQL query could not be turned into an Elasticsearch search request.
Action	Verify the syntax of the issued query and revise as needed.

EVSJEDI564E0013	Error executing native Elasticsearch search request%n{0}
Explanation	An error occurred while executing the native Elasticsearch search request.
Action	Make sure that the cluster is available and in good health.

EVSJEDI564E0014	The index represented by the specified catalog does not exist: {0}
Explanation	An SQL query was issued but there is no corresponding index on the cluster.
Action	Check your query and the available indices on the cluster.

EVSJEDI564E0015	The type represented by the specified table does not exist: {0}
Explanation	An SQL query was issued but there is no corresponding type available in the index.
Action	Check your query and the available indices on the cluster.

EVSJEDI564E0016	Error incrementing result cursor or accessing query result data.
Explanation	The result cursor could not be advanced to the next position. This issue can occur if the cluster goes down and the client tries to access the next batch.
Action	Check the cluster health.

EVSJEDI564E0017	Error setting fetch direction on forward only result set.
Explanation	This jdbc driver provides foward only result sets. A client attempted to set a fetch direction other than forward.
Action	Correct the client logic.

EVSJEDI564E0018	An error occurred because the response reference has not been set in response handler.
Explanation	This is a programming error in the implementation logic; the response must be set before using the handler.
Action	Correct the programming error.

EVSJEDI564E0019	No matching parameter marker found for the given index: {0}
Explanation	The client invoked a set method on the prepared statement for which there was no marker. For example, setting parameter 2 on a statement with only one marker.
Action	Correct the program logic.

EVSJEDI564E0020	The position {0} declared in the order by clause does not match a valid column or alias defined in the select statements column or aggregate list.
Explanation	The order by clause specifies an integer position that does not match a value in the select expressions column list.
Action	Review the statement and correct the column list expression or the order by clause.

EVSJEDI564E0021	No column matching the specified label was found in this result set: {0}
Explanation	The findColumn method was invoked with a non-existent column label.
Action	Specify a correct column label when invoking the method.

EVSJEDI564E0022	Column type at index or for the specified label is not a JDBC timestamp: {0}
Explanation	A getTimestamp, getTime or getDate accessor method was called for an incorrect column type. These methods are only valid for JDBC timestamp columns.
Action	Update the program logic to use the appropriate accessor method.

EVSJEDI564E0023	The specified database URL is not in a valid format for this driver or datasource: {0}
Explanation	The JDBC URL contains an invalid format for the given driver or data source.
Action	Consult the JDBC Driver documentation for the appropriate URL format.

EVSJHDI530E0000	The specified feature is not supported by this driver or data source: {0}
Explanation	The invoked method is not supported by the driver or data source. Only a subset of the JDBC API are required to be supported.

EVSJHDI530E0001	The required properties for this data source have not be set prior to creating the connection
Explanation	Prior to creating a connection through the data source the various setter methods should be invoked to initialize the data source.

EVSJQIE0000	Unsupported format in aggregation function: {0}.
Explanation	Unsupported format in aggregation function.

EVSJQIE0001	Unsupported date time format in string literal: {0}.
Explanation	Data and time format is invalid.

EVSJQIE0002	Query execution failed.
Explanation	Query execution failed.

EVSJQIE0003	Failed close query result.
Explanation	Failed close query result.

EVSJQIE0004	Failed to close query statement.
Explanation	Failed to close query statement.

EVSJQIE0005	Failed to close query connection.
Explanation	Failed to close query connection.

EVSJQIE0006	Failed to close qeury result.
Explanation	Failed to close query result.

EVSJQIE0007	Failed to format the result to JSON.
Explanation	Failed to format the result to JSON.

EVSJQIE0008	Unsupported feature: {0}.
Explanation	Feature is not supported.

EVSJQIE0009	Failed to get next query result.
Explanation	Failed to get next query result.

EVSJQIE0010	Full text query not supported by this implementation
Explanation	This query implementation does provide full text search capabilities

EVSJQIE0011

Error transforming query for explain plan

EVSJQIE0012

An unsupported encoding exception was thrown while generating explain message

EVSJQII0013

Inbound query in common syntax form:

EVSJQII0014

Outbound query in native form:

EVSJQPE0000

Test Message

EVSJUTE0000	Invalid JDBC scheme: {0}
Explanation	Invalid JDBC scheme.

EVSPAIE0000	Failed to execute operations: {0}
Explanation	Failed to execute operations: {0}

EVSPAIE0001	ParStream Admin Session has not been started.
Explanation	ParStream Admin Session has not been started.

EVSPAIE0002	Failed to close JDBC connection statement.
Explanation	Failed to close JDBC connection statement.

EVSPAIE0003	Event type {0} with Namespace {1} has already registered.
Explanation	Event type {0} with Namespace {1} has already registered.

EVSPAIE0004	Not supported operation: {0}.
Explanation	Not supported operation: {0}.

EVSPAIE0005	Not Supported Encoding {0}.
Explanation	Not Supported Encoding {0}.

EVSPQIE0000	Metadata manager error encountered during create session call
Explanation	Metadata manager couldn't be created; possibly due to invalid event type store location

EVSPQIE0001	Error encountered when initializing metadata manager
Explanation	Metadata manager couldn't be created; possibly due to invalid event type store location

EVSPQIE0002	Unsupported date time format in string literal: {0}
Explanation	Date and time format is invalid - See java.sql.Timestamp format

EVSPQIE0003	Unsupported syntax in aggregate function clause: {0}
Explanation	Unsupported syntax in aggregation function clause avg, min, max, sum or count

EVSPQIE0004	Error creating the connection to the ParStream database
Explanation	There was an error connecting to the ParStream server(s)

EVSPQIE0005	An open query exists for this session
Explanation	There is already a pending or active query for this session; execute or close the query

EVSPQIE0006	Error closing the connection to the ParStream database
Explanation	There was an error closing the connection to the database

EVSPQIE0007	An open result stream exists for this query
Explanation	There is an active result stream; process the results or close the result stream

EVSPQIE0008	There was an error executing the current query
Explanation	This could be due to a syntax error in the query or the ParStream database may be unavailable

EVSPQIE0009	Unexpected exception when closing the query
Explanation	An error was encountered when closing the query session

EVSPQIE0010	Failed to position cursor at next event in the result stream
Explanation	There was an error when moving the cursor position forward in the stream

EVSPQIE0011	The method {0} is unsupported in this implementation of ResultStream
Explanation	The only requirement on a ResultStream implementation is that they provide a forward cursor via the next method

EVSPQIE0012	Failed to format the query result into a JSON document
Explanation	There was an error when creating the JSON result from the database query

EVSPQIE0013	Unexpected exception encountered when closing result stream
Explanation	There was an error closing the result stream; this could be caused by a network or database issue

EVSPQIE0014	Full text query not supported by this implementation
Explanation	This query implementation does provide full text search capabilities

EVSQUAE0000	No provider registered for scheme: {0}
Explanation	No provider registered for scheme.

EVSQUAE0001	EventStoreUser is not set.
Explanation	EventStoreUser is not set.

EVSQUAE0002	Where clause contains no valid expression
Explanation	A where clause was added to the builder that contains no expression.

EVSQUAE0003	Group by clause contains no valid properties
Explanation	A group by was added to the builder but contains no event properties.

EVSQUAE0004	Order by clause contains no valid properties
Explanation	An order by clause was added to the builder but contains no properties

EVSQUAE0005	An internal error occurred while loading OSGi classes and creating service tracker instance.
Explanation	An internal error occurred while loading OSGi classes and creating service tracker instance.
Action	Contact Global Support.

EVSQUAE0006	An internal error occurred while performing the OSGi service lookup.
Explanation	The OSGi service look-up could not be performed.
Action	Check the run-time status of the installed query factory bundles.

EVSQUAE0007	No registered query factory found for scheme: {0}
Explanation	As EVP query factory implementation bundles are initialized they register themselves in OSGi. This indicates that there is no registered query session factory for the given URI scheme

EVSQUAE0008	An internal error occurred when closing the OSGi service tracker.
Explanation	The close method of the OSGi service tracker class could not be found or invoked.
Action	Check the run-time status of the installed product.

EVSQUAE0009	Error creating query session factory instance for scheme: {0}
Explanation	The implementation class for the storage provider could not be instantiated.

EVSSAPE0000	No registered storage provider factory found for store type: {0} and version: {1}
Explanation	As EVP storage implementation bundles are initialized they register their factories with the api. This indicates that there is no registered factory for the data store type and version.

EVSSAPE0001	Error creating storage factory instance for store type: {0} and version: {1}
Explanation	The implementation class for the storage provider could not be instantiated.

EVSSAPE0002	Found variable {0} but no associated value was provided in the event
Explanation	The service has been configured with variables but no value was included in the emitted event.

EVSSAPE0003	Dynamic Service Configuration validation failed; no values found in map for the following variables: {0}
Explanation	A variable was defined in the service configuration but no value was found in the event header.

EVSSAPE0004	Error compiling regular expression for variable substitution on variable: {0}
Explanation	The regular expression for substitution of the stated variable failed.

EVSSAPE0005	An internal error occurred while loading OSGi classes and creating service tracker instance.
Explanation	The required OSGi classes needed for service look-ups could not be found or loaded. There is a problem with the component or common run-time OSGi environment.
Action	Contact Global Support.

EVSSAPE0006	An internal error occurred while performing the OSGi service look-up.
Explanation	The OSGi service look-up could not be performed.
Action	Check the run-time status of the installed product.

EVSSAPE0007	An internal error occurred when closing the OSGi service tracker.
Explanation	The close method of the OSGi service tracker class could not be found or invoked.
Action	Check the run-time status of the installed product.

EVSUTLE0000	Invalid JDBC scheme: {0}
Explanation	Invalid JDBC scheme.

EVSUTLE0001	Invalid or unexpected Event Store URI format: {0}
Explanation	Invalid or unexpected Event Store URI format.