NUMSPME0001 | Unexpected exception encountered. |
Explanation |
An unexpected exception occurred. |
Action |
Check the detailed error message. Contact Software AG Global Support for further assistance. |
NUMSPME0002 | An error occurred while identifying the inventory components of Universal Messaging. |
Explanation |
Unexpected exception occurred while identifying the inventory components of Universal Messaging. |
Action |
Please contact webMethods Administrator. |
NUMSPME0003 | An error occurred while retrieving the interfaces configured for Universal Messaging. |
Explanation |
Unable to read the adapters.nst file. |
Action |
Please contact webMethods Administrator. |
NUMSPME0005 | Invalid configuration instance. {0} entered. |
Explanation |
Format of the port configuration is wrong. |
Action |
Contact your webMethods product administrator and re-configure the port settings. |
NUMSPME0006 | Invalid configuration object. {0} expected. |
Explanation |
Format of the port configuration is wrong. |
Action |
Contact your webMethods product administrator and re-configure the port settings. |
NUMSPME0007 | Invalid input for the port alias. |
Explanation |
The input for the port alias is not valid. |
Action |
Input a valid port alias or keep the port alias field empty. |
NUMSPME0008 | SSL configuration cannot be set for a non-SSL port. |
Explanation |
SSL configuration can be set only for the SSL ports. |
Action |
Remove the SSL configuration from the non-SSL port and try again. |
NUMSPME0009 | The configuration instance ID argument is missing. |
Explanation |
The configuration instance ID is required to load the port configuration. |
Action |
Specify the configuration instance ID. |
NUMSPME0010 | No port matches the provided configuration instance ID. |
Explanation |
The provided configuration instance ID is incorrect. |
Action |
Verify the configuration instance ID provided for configuration update. |
NUMSPME0011 | Protocol entered for the interface is incorrect. |
Explanation |
The protocol can only be NSP, NHP, NSPS, or NHPS. |
Action |
Verify the protocol value entered for the port. |
NUMSPME0012 | Unable to connect to the UM realm server. |
Class | E |
Explanation |
Unable to connect to the UM realm server. None of the interfaces can connect to the realm server. |
Action |
Verify if at least one interface is available for the relam server. |
NUMSPME0013 | At least one port must be specified. |
Explanation |
Port configuration is not specified in the port settings input. |
Action |
Add the port configuration to the port settings input. |
NUMSPME0014 | Error occurred while saving the port configurations. |
Explanation |
Unable to save the port configurations. |
Action |
See the detailed error message and verify the cause of failure. |
NUMSPME0015 | Only one set of port settings is allowed. |
Explanation |
More than one set of port settings are passed in the input. |
Action |
Configure only one set of port setting. |
NUMSPME0016 | Universal Messaging port number must not be changed. |
Explanation |
Attempted to change the Universal Messaging port number. |
Action |
Do not modify the port number. |
NUMSPME0017 | Universal Messaging Server port type must be STANDARD. |
Explanation |
Universal Messaging Server port type is not STANDARD. |
Action |
Set the Universal Messaging Server port type as STANDARD. |
NUMSPME0018 | Universal Messaging Server protocol must be NSP, NHP, NHPS, or NSPS. |
Explanation |
Universal Messaging Server protocol is not valid. |
Action |
Set NSP, NHP, NSPS, or NHPS as the Universal Messaging port protocol. |
NUMSPME0019 | Do not modify the BindAddress. |
Explanation |
Attempted to modify the BindAddress. |
Action |
Do not modify the BindAddress in the input. |
NUMSPME0020 | Invalid argument provided. |
Explanation |
Invalid value provided for argument. Port cannot be configured. |
Action |
Verify and provide correct value for all the arguments. Refer to the Universal Messaging documentaion for more information about argument values. |
NUMSPME0021 | IPAccess is not supported by Universal Messaging. |
Explanation |
IPAccess is set, but Universal Messaging does not support IPAccess. |
Action |
Do not set the IPAccess. |
NUMSPME0022 | KeepAliveTimeout is not supported by Universal Messaging. |
Explanation |
KeepAliveTimeout is set, but Universal Messaging does not support KeepAliveTimeout. |
Action |
Do not set the KeepAliveTimeout. |
NUMSPME0023 | ThreadPool is not supported by Universal Messaging. |
Explanation |
ThreadPool is set, but Universal Messaging does not support ThreadPool. |
Action |
Do not set the ThreadPool. |
NUMSPME0024 | URLAccess is not supported by Universal Messaging. |
Explanation |
URLAccess is set, but Universal Messaging does not support URLAccess. |
Action |
Do not set the URLAccess. |
NUMSPME0025 | Keystore definition must not be null. |
Explanation |
Keystore definition for SSL in the port configuration input is set to Null. |
Action |
Set a valid value for the keystore definition. |
NUMSPME0026 | Truststore definition must not be null. |
Explanation |
Truststore definition for SSL in the port configuration input is set to Null. |
Action |
Set a valid value for the truststore definition. |
NUMSPME0027 | Cannot delete this interface. At least one interface is required for a Universal Messaging server. |
Explanation |
At least one interface must exist for a Universal Messaging server. |
Action |
Make sure you retain at least one interface for a Universal Messaging server. |
NUMSPME0028 | Unexpected error occurred while fetching the monitoring data. |
Explanation |
An internal error occurred while fetching the monitoring data. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0029 | The primary port cannot be stopped. |
Explanation |
The primary port of a ream server cannot be stopped. |
Action |
Do not attempt to stop the primary port of a ream server. |
NUMSPME0030 | Keystore definition type can only be JKS. |
Explanation |
Keystore definition type can only be JKS. |
Action |
Specify JKS in the keystore type. |
NUMSPME0031 | Truststore definition type can only be JKS. |
Explanation |
Truststore definition type can only be JKS. |
Action |
Specify JKS for the Truststore type. |
NUMSPME0032 | Client Authentication cannot be set to REQUEST_CERTIFICATE. |
Explanation |
Only values supported for client authentication is REQUIRE_CERTIFICATE or NONE. |
Action |
Use either REQUIRE_CERTIFICATE or NONE. |
NUMSPME0033 | Universal Messaging instance management operation failed. |
Explanation |
An error occurred during the instance management operation. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0034 | Universal Messaging instance creation operation failed for the instance with name {0}. |
Explanation |
An error occurred while creating the Universal Messaging instance. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0035 | Universal Messaging instance deletion operation failed for the instance with name {0}. |
Explanation |
An error occurred while deleting the Universal Messaging instance. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0036 | Universal Messaging instance management read operation failed for the runtime component {0}. |
Explanation |
An error occurred while reading the Universal Messaging instance. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0037 | Universal Messaging instance management does not support the operation called on the runtime component {0}. |
Explanation |
The specified operation is not supported by Universal Messaging instance management. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0038 | Universal Messaging instance management operation was called with an invalid server name for the runtime component {0}. |
Explanation |
Universal Messaging instance name specified for the operation is invalid or empty. |
Action |
Provide a valid Universal Messaging instance name. |
NUMSPME0039 | Universal Messaging instance management operation was called with an empty server name for product-id {0}. |
Explanation |
Universal Messaging instance name specified for the operation is invalid or empty. |
Action |
Provide a valid Universal Messaging instance name. |
NUMSPME0040 | Universal Messaging instance management operation was called with an empty port for product-id {0}. |
Explanation |
The port specified for the Universal Messaging instance management operation is invalid or empty. |
Action |
Provide a valid port number for the Universal Messaging instance. |
NUMSPME0041 | Universal Messaging instance name, {0}, already exists. |
Explanation |
The Universal Messaging instance name specified already exists. |
Action |
Choose a Universal Messaging instance name, which is not already present. |
NUMSPME0042 | Universal Messaging instance management operation was called with the wrong product id, {0}. |
Explanation |
An error occurred during the instance management operation. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0043 | Universal Messaging user repository file does not exist. |
Explanation |
The new repository file for the Universal Messaging users does not exist on the file system. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0044 | Universal Messaging cluster update operation failed for the instance with name {0}. |
Explanation |
An error occurred while updating the cluster details of the Universal Messaging instance. |
Action |
Check the detailed error message. Contact Software AG Global Support for further assistance. |
NUMSPME0045 | Universal Messaging cluster management operation failed. |
Explanation |
An error occurred during the cluster management operation. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0046 | Universal Messaging cluster get operation failed for the instance with name {0}. |
Explanation |
An error occurred while getting the cluster details of the Universal Messaging instance. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0047 | The configuration instance ID argument is missing. |
Explanation |
The configuration instance ID is required to load the cluster configuration. |
Action |
Specify the configuration instance ID. |
NUMSPME0049 | Universal Messaging cluster operation failed. Minimum of two Universal Messaging server instances are required in the cluster. |
Explanation |
Minimum of two Universal Messaging server instances are required in the cluster. |
Action |
Make sure the cluster has a minimum of two Universal Messaging server instances. Contact Software AG Global Support for further assistance. |
NUMSPME0050 | Cannot update the {0} site information for {1} Universal Messaging server instance in {2} cluster. |
Explanation |
Failed to add or delete the site information to a server node in the cluster. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0051 | Cannot update {0} prime site for {1} cluster. The specified prime site does not belong to the cluster. |
Explanation |
Failed to update the prime site of the cluster. Only a site defined in the cluster can be specified as the prime site. |
Action |
Specify one of the sites defined in the cluster as the prime site. Contact Software AG Global Support for further assistance. |
NUMSPME0052 | Cannot create the {0} site information for {1} Universal Messaging server instance in {2} cluster. |
Explanation |
Failed to create the site for the server node in the cluster. |
Action |
Check the detailed error message. Contact Software AG Global Support for further assistance. |
NUMSPME0053 | Universal Messaging cluster create operation failed. |
Explanation |
An error occurred while creating the Universal Messaging cluster. |
Action |
Check the detailed error message. Contact Software AG Global Support for further assistance. |
NUMSPME0054 | Universal Messaging cluster delete operation failed for the cluster with name {0}. |
Explanation |
An error occurred while deleting the Universal Messaging cluster. |
Action |
Check the detailed error message. Contact Software AG Global Support for further assistance. |
NUMSPME0055 | Universal Messaging cluster create operation failed because the cluster name is not provided. |
Explanation |
To create a Universal Messaging cluster, you must provide a cluster name. |
Action |
Specify the cluster name in the input for Universal Messaging cluster creation. |
NUMSPME0056 | Universal Messaging server instance {0} is either offline or not reachable. |
Explanation |
For performing cluster management operations, all the nodes of the cluster must be online. |
Action |
Make sure that the Universal Messaging server instance is online. Contact Software AG Global Support for further assistance. |
NUMSPME0057 | The cluster update operation failed because there is a mismatch in the cluster name. Actual cluster name is {0} where as the cluster name input is {1}. |
Explanation |
There is a mismatch between the cluster name specified in the input and the name of the existing cluster. |
Action |
Input the correct cluster name. Contact Software AG Global Support for further assistance. |
NUMSPME0058 | The license file you have provided is invalid. Provide a valid license file. |
Explanation |
Invalid license file provided. |
Action |
Provide a valid Software AG license file. Please contact Software AG Global Support for further assistance. |
NUMSPME0060 | Unable to configure the Universal Messaging server properties. |
Explanation |
An error occurred while configuring server properties. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0061 | Unable to load the Universal Messaging server configuration properties. Provide a valid configuration instance ID. |
Explanation |
Configuration instance ID is invalid or not provided. |
Action |
Provide a valid configuration instance ID. |
NUMSPME0062 | Parameter validation failed. Unable to update the Universal Messaging server configuration parameters. |
Explanation |
Incorrect configuration parameter values provided. |
Action |
See the Universal Messaging documentation for information about valid configuration parameter values. |
NUMSPME0063 | Unable to update Universal Messaging server configuration parameters. |
Explanation |
An error occurred when updating the Universal Messaging server configuration properties. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0064 | The Universal Messaging server configuration parameter provided is null or does not exist within the group. |
Explanation |
The Universal Messaging server parameter is null or does not exist. |
Action |
See the Command Central Help and Universal Messaging documentation for information about valid parameters and values. |
NUMSPME0065 | Cannot create the {0} site information for {1} Universal Messaging server instance in {2} cluster within the event time interval. |
Explanation |
Failed to create the site information for the server node in the cluster, in the time interval. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0066 | An error occurred while initializing the Universal Messaging Context. |
Explanation |
An error occurred while initializing the Universal Messaging Context for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0067 | An error occurred while initializing the Universal Messaging Context for Universal Messaging server {0}. |
Explanation |
An error occurred while initializing the Universal Messaging Context for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0068 | An error occurred while retrieving the JNDI connection factory entries. |
Explanation |
An error occurred while retrieving the JNDI connection factory entries from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the JNDI connection factories are present on the server. |
NUMSPME0069 | An error occurred while retrieving the JNDI connection factory entries for the Universal Messaging server {0}. |
Explanation |
An error occurred while retrieving the JNDI connection factory entries from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the JNDI connection factories are present on the server. |
NUMSPME0070 | An error occurred while retrieving JNDI connection factory {0} for Universal Messaging server {1}. |
Explanation |
An error occurred while retrieving the JNDI connection factory entry from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the JNDI connection factory is present on the server. |
NUMSPME0071 | An error occurred while deleting the JNDI connection factory. |
Explanation |
An error occurred while deleting the JNDI connection factory from the Universal Messaging server. |
Action |
Ensure that the JNDI connection factory is present on the server. |
NUMSPME0072 | An error occurred while deleting the JNDI connection factory {0} for Universal Messaging server {1}. |
Explanation |
An error occurred while deleting the JNDI connection factory from the Universal Messaging server. |
Action |
Ensure that the JNDI connection factory is present on the server. |
NUMSPME0073 | An error occurred while binding the JNDI connection factory. |
Explanation |
An error occurred while binding the JNDI connection factory for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0074 | An error occurred while binding the JNDI connection factory {0} for Universal Messaging server {1}. |
Explanation |
An error occurred while binding the JNDI connection factory for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0075 | An error occurred while updating the JNDI connection factory. |
Explanation |
An error occurred while updating the JNDI connection factory for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the JNDI connection factory is present on the server. |
NUMSPME0076 | An error occurred while updating the JNDI connection factory {0} for Universal Messaging server {1}. |
Explanation |
An error occurred while updating the JNDI connection factory for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the JNDI connection factory is present on the server. |
NUMSPME0077 | An error occurred while loading the JNDI connection factory type for Universal Messaging server {0}. |
Explanation |
An error occurred while loading the JNDI connection factory type for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0078 | An error occurred while creating the JNDI connection factory type {0} for Universal Messaging server {1}. |
Explanation |
An error occurred while creating the JNDI connection factory type for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0079 | An error occurred while binding the JNDI destination. |
Explanation |
An error occurred while binding the JNDI destination on the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0080 | An error occurred while binding the JNDI destination {0} on Universal Messaging server {1}. |
Explanation |
An error occurred while binding the JNDI destination on the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0081 | An error occurred while retrieving the JNDI destination. |
Explanation |
An error occurred while retrieving the JNDI destination from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and JNDI destinations are present on the server. |
NUMSPME0082 | An error occurred while retrieving the JNDI destination from Universal Messaging server {0}. |
Explanation |
An error occurred while retrieving the JNDI destination from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and JNDI destinations are present on the server. |
NUMSPME0083 | An error occurred while retrieving the JNDI destination {0} from Universal Messaging server {1}. |
Explanation |
An error occurred while retrieving the JNDI destination from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and JNDI destinations are present on the server. |
NUMSPME0084 | An error occurred while deleting the JNDI destination. |
Explanation |
An error occurred while deleting the JNDI destination from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the JNDI destinations are present on the server. |
NUMSPME0085 | An error occurred while deleting the JNDI destination {0} from Universal Messaging server {1}. |
Explanation |
An error occurred while deleting the JNDI destination from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the JNDI destinations are present on the server. |
NUMSPME0086 | An error occurred while loading the JNDI destination type for Universal Messaging server {0}. |
Explanation |
An error occurred while loading the JNDI destination type for Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0087 | An error occurred while creating the JNDI destination {0} for Universal Messaging server {1}. |
Explanation |
An error occurred while creating the JNDI destination on the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0088 | Updating a JNDI destination type is not supported. |
Explanation |
Update operation for a JNDI destination type is not supported for Universal Messaging server. |
Action |
No action required. |
NUMSPME0089 | The Universal Messaging server is unavailable, check the status of the Universal Messaging server. |
Explanation |
The Universal Messaging server might not be running. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0090 | An error occurred while retrieving the Universal Messaging session. |
Explanation |
An error occurred while retrieving the Universal Messaging session. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0091 | An error occurred while retrieving the session for Universal Messaging server {0}. |
Explanation |
An error occurred while retrieving the session for Universal Messaging server {0}. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0092 | JNDI connection factory name is either empty or contains invalid characaters. |
Explanation |
JNDI connection factory name is either empty or contains invalid characaters. |
Action |
Provide a valid JNDI connection factory name. |
NUMSPME0093 | Updating JNDI connection factory name is not supported. |
Explanation |
Update operation for JNDI connection factory name is not supported for the Universal Messaging server. |
Action |
No action required. |
NUMSPME0094 | Updating JNDI connection factory {0} name is not supported. |
Explanation |
Update operation for JNDI connection factory name is not supported for the Universal Messaging server. |
Action |
No action required. |
NUMSPME0095 | Invalid JNDI connection factory type. Allowed types are Connection Factory, Topic Connection Factory, Queue Connection Factory, and XA Connection Factory. |
Explanation |
Invalid JNDI connection factory type. Allowed types are Connection Factory, Topic Connection Factory, Queue Connection Factory, and XA Connection Factory. |
Action |
Provide a valid JNDI connection factory type. |
NUMSPME0096 | JNDI connection factory URL is either empty or invalid. |
Explanation |
JNDI connection factory URL is either empty or invalid. |
Action |
Provide a valid JNDI connection factory URL. |
NUMSPME0097 | Invalid value provided for JNDI connection factory shared durable property. Allowed values are true and false. |
Explanation |
Invalid value provided for JNDI connection factory shared durable property. Allowed values are true and false. |
Action |
Provide true to enable and false to disable shared durable for the JNDI connection factory. |
NUMSPME0098 | JNDI destination name is either empty or contains invalid characters. |
Explanation |
JNDI destination name is either empty or contains invalid characters. |
Action |
Provide a valid JNDI destination name. |
NUMSPME0099 | Invalid JNDI destination type. Allowed types are Topic and Queue. |
Explanation |
Invalid JNDI destination type. Allowed types are Topic and Queue. |
Action |
Provide a valid JNDI destination type. |
NUMSPME0100 | JNDI store name is either empty or contains invalid characaters. |
Explanation |
JNDI store name is either empty or contains invalid characaters. |
Action |
Provide a valid JNDI store name. |
NUMSPME0101 | Invalid value provided for the JNDI destination auto-create option. Allowed values are true and false |
Explanation |
Invalid value provided for the JNDI destination auto-create option. Allowed values are true and false. |
Action |
Provide true to enable and false to disable auto-creation of JNDI destinations. |
NUMSPME0102 | An error occurred while creating a channel on the Universal Messaging server. |
Explanation |
An error occurred while creating a channel on the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0103 | An error occured while creating channel {0} on Universal Messaging server {1}. |
Explanation |
An error occured while creating a channel on the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0104 | An error occured while creating a queue on the Universal Messaging server. |
Explanation |
An error occured while creating a queue on the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0105 | An error occured while creating queue {0} on Universal Messaging server {1}. |
Explanation |
An error occured while creating a queue on the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0106 | The JNDI connection factory already exists on the Universal Messaging server. |
Explanation |
The JNDI connection factory already exists on the Universal Messaging server. |
Action |
Provide a different name for the JNDI connection factory. |
NUMSPME0107 | JNDI connection factory {0} already exists on Universal Messaging server {1}. |
Explanation |
JNDI connection factory already exists on the Universal Messaging server. |
Action |
Provide a different name for the JNDI connection factory. |
NUMSPME0108 | The JNDI destination already exists on the Universal Messaging server. |
Explanation |
The JNDI destination already exists on the Universal Messaging server. |
Action |
Provide a different name for the JNDI destination. |
NUMSPME0109 | JNDI destination {0} already exists on Universal Messaging server {1}. |
Explanation |
JNDI destination already exists on Universal Messaging server. |
Action |
Provide a different name for the JNDI destination. |
NUMSPME0110 | Unable to load Universal Messaging server configuration properties user interface. |
Explanation |
An error occurred while reading or writing configuration properties. |
Action |
Contact Software AG Global Support for further assistance. |
NUMSPME0111 | Unable to establish connection with the Universal Messaging server. |
Explanation |
An error occurred while retrieving the session from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0112 | Unable to retrieve the session attribute object associated with with Universal Messaging server session. |
Explanation |
An exception occurred while retrieving the session attribute. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0113 | Unable to find the Universal Messaging channel on this Universal Messaging sever. |
Explanation |
An error occurred while retrieving the Universal Messaging channel on the Universal Messaging realm server connected to this session, or a joined realm. |
Action |
Please check if the channel exists on this Universal Messaging sever. |
NUMSPME0114 | Unable to retrieve the named object on this channel. |
Explanation |
An error occurred while retrieving the named object details from this channel on the Universal Messaging server. |
Action |
Please check if the namd object exists on this channel. |
NUMSPME0115 | Unable to delete the named object on this channel. |
Explanation |
An error occurred while deleting the named object from this channel on the Universal Messaging server. |
Action |
Please check if the named object exists on this channel. |
NUMSPME0116 | Missing argument: {0}. |
Explanation |
Arguments not provided. Please provide both the channel and durable subscriber names to view details or delete a durable subscriber. |
Action |
Provide valid arguments for durable subscriber or channel. |
NUMSPME0117 | Unable to connect to the Universal Messaging server. |
Explanation |
An error occurred while retrieving the session from the Universal Messaging server. |
Action |
Please check if the Universal Messaging server is running. |
NUMSPME0118 | Unable to retrieve the channel/queue {0} from Universal Messaging server {1}. |
Explanation |
An error occurred while retrieving the channel/queue from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the specified channel/queue exists on the server. |
NUMSPME0119 | Unable to establish connection with the Universal Messaging server {0}. |
Explanation |
An error occurred while connecting to the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server exists and is running. |
NUMSPME0120 | An error occurred while loading channel configuration for the Universal Messaging server {0}. |
Explanation |
An error occurred while loading channel configuration for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0121 | Unable to retrieve the channel list for the Universal Messaging server {0}. |
Explanation |
An error occured while retrieving the list of channels for the Universal Messaging server. |
Action |
Check if the Universal Messaging server is running and if the channels are configured. |
NUMSPME0122 | Unable to retrieve the details of channel {0} in Universal Messaging server {1}. |
Explanation |
An error occured while retrieving the channel details for the Universal Messaging server. |
Action |
Check if the Universal Messaging server is running and if the channel exists on the server. |
NUMSPME0123 | Unable to connect to the Universal Messaging server {0}. |
Explanation |
An error occurred while connecting to the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server exists and is running. |
NUMSPME0124 | An error occurred while loading the queues for the Universal Messaging server {0}. |
Explanation |
An error occurred while loading the queues for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server exists and is running. |
NUMSPME0125 | Unable to retrieve the queue list for the Universal Messaging server {0}. |
Explanation |
An error occured while retrieving the queue list for the Universal Messaging server. |
Action |
Please check if the Universal Messaging server is running and has queues configured. |
NUMSPME0126 | Unable to retrieve the details of the queue {0} in Universal Messaging server {1}. |
Explanation |
An error occured while retrieving the queue details from the Universal Messaging server. |
Action |
Please check if Universal Messaging server is running and the queue exists on the server. |
NUMSPME0127 | Universal Messaging instance management operation failed, exit code - {0}, full command - {1}, standard output - {2} |
Explanation |
The Universal Messaging instance management operation failed due to an error. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error, resolve the error and retry. |
NUMSPME0128 | Unable to create or update the channel as the channel name is not provided or is invalid. |
Explanation |
Cannot create or update the channel with an empty or invalid name. |
Action |
Provide a valid channel name. |
NUMSPME0129 | Unable to create or update the channel as the channel TTL value provided is invalid. |
Explanation |
Cannot create or update a channel as the TTL is negative. |
Action |
Provide a TTL value between 0 to 2147483647. |
NUMSPME0130 | Unable to create or update the channel as the provided channel capacity value is invalid. |
Explanation |
Cannot create or update a channel as the provided value for the channel capacity is in negative. |
Action |
Provide a capacity value between 0 to 2147483647. |
NUMSPME0131 | Unable to create or update the channel as the channel type provided is invalid. |
Explanation |
Cannot create or update a channel because the channel type provided is invalid. |
Action |
Provide a valid channel type. |
NUMSPME0132 | Unable to create or update the channel as the channel engine provided is invalid |
Explanation |
Cannot create or update the channel because the channel engine type provided is invalid. |
Action |
Provide a valid channel engine type. |
NUMSPME0133 | Unable to create or update the channel as the publish key name provided is invalid. |
Explanation |
Cannot create or update a channel becaue the publish key name provided is invalid . |
Action |
Provide a valid channel publish key name. |
NUMSPME0134 | Unable to create or update the channel as the key depth value provided is invalid. |
Explanation |
Cannot create or update a channel bacause the key depth value provided is invalid. |
Action |
Provide a valid channel key depth. |
NUMSPME0135 | Unable to create or update the channel as the priority value provided is invalid. |
Explanation |
Cannot create or update a channel because the priority value provided is invalid. |
Action |
Provide a value between 0 to 9. |
NUMSPME0136 | Unable to create or update the channel as the selected stamp dictionary is invalid. |
Explanation |
Cannot create /update a channel with an invalid stamping dictionary |
Action |
Select a valid stamp dictionary. |
NUMSPME0137 | Unable to create the channel {0} on Universal Messaging server {1}. |
Explanation |
An error occured while creating the channel on the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0138 | Unable to create/update the channel attributes as the provided parameters are invalid. |
Explanation |
An error occured while creating/updating the channel attributes as the provided input parameters are invalid. |
Action |
Ensure that the provided input channel parameter values are valid. |
NUMSPME0139 | Unable to create/update the channel as the dead event store provided is invalid. |
Explanation |
An error occured while creating/updating the channel as the provided dead event store does not exist on the Universal Messaging server. |
Action |
Ensure that the dead event store channel or queue provided exists on the server. |
NUMSPME0140 | Unable to create the channel as channel {0} already exists on server {1}. |
Explanation |
Channel already exists on the server. |
Action |
Create a channel with a different name. |
NUMSPME0141 | Unable to delete the channel or queue {0} on Universal Messaging server {1}. |
Explanation |
An error occured while deleting the channel or queue on the Universal Messaging server. |
Action |
Check if the Universal Messaging server is running. |
NUMSPME0142 | Unable to update the channel or queue {0} on Universal Messaging server {1}. |
Explanation |
An error occured while updating the channel or queue on the Universal Messaging server. |
Action |
Check if the Universal Messaging server is running. |
NUMSPME0143 | Cannot update the channel or queue {0} on Universal Messaging server {1} because of invalid input parameters. |
Explanation |
An error occured while updating the channel or queue for the Universal Messaging server because of invalid input parameters. |
Action |
Ensure that the input parameters are valid and correct. |
NUMSPME0144 | Unable to update the channel or queue {0} on Universal Messaging server {1}. |
Explanation |
Update failed because an error occurred while copying the new configuration over the existing channel or queue configuration. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0145 | Unable to create or update the channel or queue {0} on Universal Messaging server {1}. |
Explanation |
An error occured while creating or updating the channel or queue on Universal Messaging server because of invalid input storage parameters. |
Action |
Ensure that the input storage parameters are valid and correct. |
NUMSPME0146 | Unable to create queue {0} on Universal Messaging server {1}. |
Explanation |
An error occured while creating the queue on Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0147 | Unable to create or update the queue. |
Explanation |
Cannot create or update the queue because of empty or invalid name. |
Action |
Ensure that you provide a valid name. |
NUMSPME0148 | Unable to create or update the queue bacause the TTL value is invalid. |
Explanation |
Cannot create or update a queue as the TTL value is negative. |
Action |
PLease provide a TTL between 0 to 2147483647 (exclusive) |
NUMSPME0149 | Unable to create or update the queue as the channel capacity value is invalid. |
Explanation |
Cannot create or update a queue as the capacity is negative. |
Action |
Enter a capacity value between 0 to 2147483647. |
NUMSPME0150 | Unable to create or update the channel because the queue type is invalid. |
Explanation |
Cannot create or update a queue with an invalid type. |
Action |
Provide a valid queue type. |
NUMSPME0151 | Unable to create or update the channel because the priority value is invalid. |
Explanation |
Cannot create or update a channel with an invalid event priority. |
Action |
Provide a priority value between 0 to 9 (lowest to highest) . |
NUMSPME0152 | Unable to create or update the channel as the stamping dictionary value provided is invalid. |
Explanation |
Cannot create or update a channel with an invalid stamping dictionary. |
Action |
Provide a valid stamping dictionary value. |
NUMSPME0153 | Unable to create the queue attributes as the provided parameters are invalid. |
Explanation |
An error occured while creating the queue attributes as the input parameters are invalid. |
Action |
Provide valid queue parameters. |
NUMSPME0154 | Unable to create the channel attributes as the dead event store is invalid. |
Explanation |
An error occured while creating the channel attributes as the provided dead event store does not exist on the Universal messaging server. |
Action |
Ensure that the dead event store channel or queue exists on the server. |
NUMSPME0155 | Unable to create the queue as queue {0} already exists on server {1}. |
Explanation |
Queue exists on the server. |
Action |
Create a queue with a different name. |
NUMSPME0156 | Missing argument: {0}. |
Explanation |
Arguments not provided. Provide the channel name to view status of a channel. |
Action |
Provide a valid channel name. |
NUMSPME0157 | Unable to retrieve the status of channel {0} in Universal Messaging server {1}. |
Explanation |
An error occured while retrieving the channel details from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the channel exists on the server. |
NUMSPME0158 | Arguments not provided. |
Explanation |
Arguments not provided. Provide the queue name to view status of a queue. |
Action |
Provide queue name as the argument. |
NUMSPME0159 | Unable to retrieve the status of queue {0} for Universal Messaging server {1}. |
Explanation |
An error occured while retrieving the queue status from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running and the queue exists on the server. |
NUMSPME0160 | Unable to retrieve ACLs for channel {0}. |
Explanation |
An error occurred while retrieving ACLs for channel {0}. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error resolve the error and retry. |
NUMSPME0161 | Unable to add ACLs for channel {0}. |
Explanation |
An error occurred while adding ACLs to a channel. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0162 | Unable to update ACLs for channel {0}. |
Explanation |
An error occurred while updating ACLs for channel {0}. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0163 | Unable to create an ACL entry with subject {0} for channel {1}. |
Explanation |
An error occurred when creating an ACL entry object for the channel. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0164 | Unable to retrieve ACLs for queue {0}. |
Explanation |
An error occurred when retrieving ACLs for the queue. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0165 | Unable to add ACLs for queue {0}. |
Explanation |
Adding ACLs to a queue failed due to an error. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0166 | Unable to update ACLs for queue {0}. |
Explanation |
An error occurred when updating ACLs for a queue. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0167 | Unable to create the ACL entry with name {0} for queue {1}. |
Explanation |
An error occurred in creating ACL entry object with name {0} for queue {1}. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0168 | Unable to create the ACL entry with subject {0} for channel {1}. |
Explanation |
Invalid group name provided for ACL entry object with subject {0} for channel {1}. |
Action |
Provide a valid group name. |
NUMSPME0169 | Unable to create the ACL entry with name {0} for queue {1}. |
Explanation |
Invalid group name provided for ACL entry with name {0}, for queue {1}. |
Action |
Provide a valid group name. |
NUMSPME0170 | Unable to create a join from {0} to {1} because the operation is unsupported. |
Explanation |
An error occurred while creating the join. |
Action |
Ensure that the source node is a valid channel. For archived join, ensure that the destination node is a queue. |
NUMSPME0171 | Unable to create a join from {0} to {1}. |
Explanation |
An error occurred while creating the join. |
Action |
Ensure that the source is a valid channel and the Universal Messaging server is running. |
NUMSPME0172 | Unable to delete the join from {0} to {1} as this operation is unsupported. |
Explanation |
An error occurred while deleting the join. |
Action |
Ensure that the source node is a valid channel. |
NUMSPME0173 | Unable to delete the join from {0} to {1}. |
Explanation |
An error occurred while deleting the join. |
Action |
Ensure that the source is a valid channel and the Universal Messaging server is running. |
NUMSPME0174 | Unable to delete the join from {0} to {1} as this is not a source node. |
Explanation |
An error occurred while deleting the join. |
Action |
Delete the join from the source node. A join cannot be deleted from a destination node. |
NUMSPME0175 | Unable to create the cluster. |
Explanation |
Unable to create the cluster because the Universal Messaging server instance is already part or another cluster or the server instance already exists in the cluster or a local store is configured in one of the server instances that you are adding to the cluster. |
Action |
Ensure that the Universal Messaging server instance added to the cluster complies to the restrictions provided in the error message explanation. |
NUMSPME0176 | Unable to create the cluster. |
Explanation |
Session error. |
Action |
Check the detailed error message in the Command Central and Universal Messaging logs. Resolve the error and retry. |
NUMSPME0177 | Unable to create the cluster. |
Explanation |
Request timed out. |
Action |
Retry creating the cluster. |
NUMSPME0178 | Unable to create the cluster. |
Explanation |
Error in the response received from the realm server. |
Action |
Check for the detailed error message in the Universal Messaging logs. Resolve the error and retry. |
NUMSPME0179 | Unable to create the cluster. |
Explanation |
The Universal Messaging server instance is currently unreachable. |
Action |
Check for the detailed error message in the Universal Messaging logs. Resolve the error and retry. |
NUMSPME0180 | Unable to create the cluster. |
Explanation |
Conflicting realm names provided. |
Action |
Ensure that you provide the correct realm names to create the cluster. |
NUMSPME0181 | Unable to create the cluster. |
Explanation |
The Universal Messaging server instance could not be found. |
Action |
Check for detailed error messages in the Command Central and Universal Messaging logs. Contact Software AG Global Support for further assistance. |
NUMSPME0182 | Unable to create the cluster. |
Explanation |
You do not have the required administration rights for the realm. |
Action |
Ensure that you have the relevant administration rights for the realm. |
NUMSPME0183 | Channel created successfully but cannot create a join from {0} to {1} because the operation is not supported. |
Explanation |
An error occurred while creating the join. |
Action |
Ensure that the source is a valid channel. For archived join, ensure that the destination node is a queue. |
NUMSPME0184 | Channel created successfully but cannot create a join from {0} to {1}. |
Explanation |
An error occurred while creating the join. |
Action |
Ensure that the source is a valid channel and the Universal Messaging server is running. |
NUMSPME0185 | Unable to create a join from {0} to {1} because the operation is not suppported. The other channel properties are sucessfully updated. |
Explanation |
An error occurred while creating the join. |
Action |
Ensure that the source is a valid channel. For archived join, ensure that the destination node is a queue. |
NUMSPME0186 | Unable to create a join from {0} to {1}. The other channel properties are sucessfully updated. |
Explanation |
An error occurred while creating the join. |
Action |
Ensure that the source is a valid channel and the Universal Messaging server is running. |
NUMSPME0187 | Unable to delete the join from {0} to {1} as the operation is not supported. Other channel properties are updated. |
Explanation |
An error occurred while deleting the join. |
Action |
Ensure that the source node is a valid channel. |
NUMSPME0188 | Unable to delete the join from {0} to {1}. Other channel properties are updated. |
Explanation |
An error occurred while deleting the join. |
Action |
Ensure that the source is a valid channel and the Universal Messaging server is running. |
NUMSPME0189 | Cannot delete the join from {0} to {1} because {0} is not the source node. Other channel properties are updated. |
Explanation |
An error occurred while deleting the join. |
Action |
Delete the join from the source node. A join cannot be deleted from a destination node. |
NUMSPME0190 | Unable to create or update the channel as the protobuf descriptor file does not exist. |
Explanation |
Cannot create or update a channel with an invalid protobuf descriptor file. |
Action |
Ensure that the protobuf descriptor file exists in the provided path. |
NUMSPME0191 | Unable to create or update the channel as the protobuf descriptor file provided is invalid. |
Explanation |
An error occured while creating or updating the channel because the protobuf descriptor file provided is invalid. |
Action |
Provide a valid protobuf descriptor file. |
NUMSPME0192 | Unable to create or update the queue as the protobuf descriptor file does not exist. |
Explanation |
Cannot create or update a queue with an invalid protobuf descriptor file. |
Action |
Ensure that the protobuf descriptor file exists in the provided path. |
NUMSPME0193 | Unable to create or update the queue as the protobuf descriptor provided is invalid. |
Explanation |
An error occured while creating or updating the queue because the protobuf descriptor file provided is invalid. |
Action |
Provide a valid protobuf descriptor file. |
NUMSPME0194 | Unable to edit the name of the channel. |
Explanation |
You cannot edit the name of a channel, operation not supported. |
Action |
Delete and recreate the channel. |
NUMSPME0195 | Unable to edit the name of the queue. |
Explanation |
You cannot edit the name of a queue, operation not supported. |
Action |
Delete and recreate the queue. |
NUMSPME0196 | Unable to retrieve the channel or queue {0} from Universal Messaging server {1}. |
Explanation |
An error occurred while retrieving the channel or queue from the Universal Messaging server as the node addition has failed. |
Action |
Ensure that the Universal Messaging server instances are not clustered. |
NUMSPME0197 | An error occurred while creating the join. |
Explanation |
Cannot create the join between {0} and {1} because remote node {1} is not a valid node. |
Action |
Ensure that the remote node is a valid channel or queue and the Universal Messaging server is running. |
NUMSPME0198 | Cannot edit a channel join. Operation not supported. |
Explanation |
Channel joins can only be created and deleted. Editing is not supported. |
Action |
Delete and recreate the join with the new join attributes. |
NUMSPME0199 | Missing argument: {0}. |
Explanation |
Arguments not provided. Please provide both the channel and durable subscriber names to delete a durable subscriber. |
Action |
Provide valid arguments for durable subscriber or channel. |
NUMSPME0200 | An error occurred while creating file {0} for the Universal Messaging server instance {1}. |
Explanation |
An error occurred while creating the file for Universal Messaging instance {1}. |
Action |
Check the Platform Manager logs for more information about the error. |
NUMSPME0201 | Invalid cluster configuration. Cluster name not provided for Universal Messaging server instance {0}. |
Explanation |
Invalid cluster configuration provided. Cluster name not provided for Universal Messaging server instance {0}. |
Action |
Provide a valid cluster name in the cluster configuration. |
NUMSPME0202 | Invalid cluster configuration. Servers element is required and is not provided for the Universal Messaging server instance {0}. |
Explanation |
Invalid cluster configuration. Servers element is required in the cluster configuration and is not provided for the Universal Messaging server instance {0}. |
Action |
Provide valid cluster configuration with the necessary servers element. |
NUMSPME0203 | Invalid cluster configuration. Server name is required and is not provided for the Universal Messaging server instance {0}. |
Explanation |
Invalid cluster configuration. Server name is required and is not provided for the Universal Messaging server instance {0}. |
Action |
Provide a valid server name in the cluster configuration. |
NUMSPME0204 | Invalid cluster configuration. Server URL {0} is not provided or is invalid for Universal Messaging server name {1} for server instance {2}. |
Explanation |
Invalid cluster configuration. Server URL {0} is not provided or is invalid for Universal Messaging server name {1} for server instance {2}. |
Action |
Provide a valid server URL in the cluster configuration. |
NUMSPME0205 | Unable to establish connection with the Universal Messaging server {0}. |
Explanation |
An error occurred while connecting to the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server exists and is running. |
NUMSPME0206 | An error occurred while loading the realm ACL configuration for the Universal Messaging server {0}. |
Explanation |
An error occurred while loading the realm ACL configuration for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0207 | Unable to retrieve the realm ACLs for Universal Messaging server {0}. |
Explanation |
An error occurred while retrieving the realm ACLs for {0}. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0208 | Unable to update realm ACLs for Universal Messaging server {0}. |
Explanation |
An error occurred while updating ACLs for Universal Messaging server {0}. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0209 | Unable to create an ACL entry with subject {0} for Universal Messaging server {1}. |
Explanation |
An error occurred when creating an ACL entry for the realm. |
Action |
Check the Platform Manager and Universal Messaging logs to find the error; resolve the error and retry. |
NUMSPME0210 | Unable to create the ACL entry with subject {0} for Universal Messaging server {1}. |
Explanation |
Invalid group name provided for ACL entry object with subject {0} for realm {1}. |
Action |
Provide an existing group name. |
NUMSPME0211 | Purge operation not supported on the durable subscriber of type {0}. |
Explanation |
Purge operation is not allowed for this durable subscriber type. |
Action |
Purge events on a different durable type. |
NUMSPME0212 | Unable to establish connection to the Universal Messaging server. |
Explanation |
An error occurred while retrieving the session from the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0213 | An error occurred while trying to view events on the durable subscriber. |
Explanation |
An error occurred while trying to view events on the durable subscriber. |
Action |
Ensure that the channel and durable type exists, and the Universal Messaging server is running. |
NUMSPME0214 | An error occured while purging events on the durable subscriber. |
Explanation |
An error occured while purging events on the durable subscriber. |
Action |
Ensure that the channel and durable type exists, and the Universal Messaging server is running. |
NUMSPME0215 | An error occurred while parsing the event header. |
Explanation |
An error occurred while parsing the event header. |
Action |
Ensure that the header does not contain corrupted information. |
NUMSPME0217 | Invalid arguments provided. |
Explanation |
Invalid arguments provided. |
Action |
Ensure that you provide valid arguments and try again. |
NUMSPME0227 | Creation of realm ACLs for Universal Messaging server is not supported. |
Explanation |
Create operation for realm ACLs is not supported for a Universal Messaging server. |
NUMSPME0228 | Deletion of realm ACLs for Universal Messaging server is not supported. |
Explanation |
Delete operation for realm ACLs is not supported for Universal Messaging server. |
NUMSPME0229 | Universal Messaging cluster update operation failed for the instance with name {0}. |
Explanation |
An error occurred while updating the cluster details of the Universal Messaging instance. |
Action |
Ensure that all the cluster nodes are online and the cluster has the quorum. |
NUMSPME0239 | XA Connection Factory does not support round robin URL. |
Action |
Change the connection factory type or the URL. |
NUMSPME0240 | Unable to load the groups configuration instance for the Universal Messaging instance {0}. |
Explanation |
An error occurred when loading the group configuration for the Universal Messaging server instance. |
Action |
Specify a valid group name. |
NUMSPME0241 | Unable to retrieve groups for Universal Messaging instance {0}. |
Explanation |
Cannot retrieve groups for the Universal Messaging instance. There are no groups present for the Universal Messaging instance. |
Action |
Groups don't exist for this Universal Messaging instance. You need to create a group for the Universal Messaging instance before you retrieve the group. |
NUMSPME0242 | Unable to add entry with the subject or group {0} for the Universal Messaging instance {1}. |
Explanation |
Invalid subject or group name provided. |
Action |
Provide a valid existing subject and group name. |
NUMSPME0243 | Unable to create group {0} for the Universal Messaging instance {1}. |
Explanation |
An error occured while creating a group for the Universal Messaging instance. |
Action |
Ensure that you have sufficient privileges to add new groups to the Universal Messaging instance. |
NUMSPME0244 | Unable to delete group {0} for the Universal Messaging instance {1}. |
Explanation |
An error occured while deleting a group for the Universal Messaging instance. |
Action |
Ensure that you have sufficient privileges to delete groups in the Universal Messaging instance. |
NUMSPME0245 | Unable to update group {0} for the Universal Messaging instance {1}. |
Explanation |
An error occured while updating a group for the Universal Messaging server. |
Action |
Ensure that you have sufficient privileges to update groups in the Universal Messaging instance. |
NUMSPME0246 | Unable to add an entry with subject {0} for the group {1} for Universal Messaging instance {2}. |
Explanation |
An error occured when adding a subject to the group for the Universal Messaging instance. |
Action |
Ensure that you have sufficient privileges to update groups in the Universal Messaging instance. |
NUMSPME0247 | Unable to connect to the Universal Messaging instance {0}. |
Explanation |
An error occurred while connecting to the Universal Messaging server. |
Action |
Ensure that the Universal Messaging instance is online. |
NUMSPME0248 | Unable to create the group as the group name is not provided or is invalid. |
Explanation |
Cannot create or update group with an empty or invalid name. |
Action |
Provide a valid group name. |
NUMSPME0249 | Unable to create zone {0} with Universal Messaging server {1}. |
Explanation |
An error occurred while creating a zone with the Universal Messaging server. |
Action |
Check the detailed error message. Resolve any errors, and then retry. |
NUMSPME0250 | Unable to create or update the channel as the read buffer size value provided is invalid. |
Explanation |
Cannot create or update a channel because the read buffer size value provided is invalid. |
Action |
Provide a read buffer size value between 0 to 2147483647. |
NUMSPME0251 | Unable to create or update the channel as the events per spindle value provided is invalid. |
Explanation |
Cannot create or update a channel because the events per spindle value provided is invalid. |
Action |
Provide a value between 0 to 2147483647. |
NUMSPME0252 | Unable to create or update the channel as the sync batch property values provided are invalid. |
Explanation |
Cannot create or update a channel because the sync batch property values provided are invalid. |
Action |
Provide a sync batch property value between 0 to 2147483647. |
NUMSPME0253 | Unable to create or update the queue as the read buffer size value provided is invalid. |
Explanation |
Cannot create or update a queue because the read buffer size value provided is invalid. |
Action |
Provide a read buffer size value between 0 to 2147483647. |
NUMSPME0254 | Unable to create or update the queue as the events per spindle value provided is invalid. |
Explanation |
Cannot create or update a queue because the events per spindle value provided is invalid. |
Action |
Provide a events per spindle value between 0 to 2147483647. |
NUMSPME0255 | Unable to create or update the queue as the sync batch property values provided are invalid. |
Explanation |
Cannot create or update a queue because the sync batch property values provided are invalid. |
Action |
Provide a sync batch property value between 0 to 2147483647. |
NUMSPME0256 | Unable to update zone {0} with Universal Messaging server {1}. |
Explanation |
An error occurred while updating a zone with the Universal Messaging server. |
Action |
Check the detailed error message in the Universal Messaging server logs. |
NUMSPME0257 | Unable to remove link from Universal Messaging server {0} to Universal Messaging server {1}. |
Explanation |
An error occurred while removing links between Universal Messaging servers in the zone. |
Action |
Check for the detailed error message in the Universal Messaging logs. Resolve the error and retry. |
NUMSPME0258 | Failed to remove cluster link from cluster {0} to cluster {1}. |
Explanation |
An error occurred while removing links between clusters in the zone. |
Action |
Ensure the clusters are available and connected. |
NUMSPME0259 | Unable to retrieve zone details for Universal Messaging server {0}. |
Explanation |
An error occurred while retrieving the zone members list for the Universal Messaging server. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0260 | The Universal Messaging server instance is currently not accessible . |
Explanation |
Check for the detailed error messages in the Universal Messaging logs. Resolve the error and retry. |
Action |
Ensure that the Universal Messaging server is running. |
NUMSPME0261 | An error occurred while creating a zone. |
Explanation |
Zone members are incompatible, clustered and non-clustered Universal Messaging server instances cannot be in the same zone. |
Action |
Ensure that the clustered and non-clustered Universal Messaging server instances are not added to the same zone. Clustered and non-clustered Universal Messaging server instances need to be grouped in separate zones. |
NUMSPME0262 | Unable to create a link to the Universal Messaging server {0} from Universal Messaging server {1}. |
Explanation |
An error occurred while linking the Universal Messaging servers. Rolling back the created links. |
Action |
Ensure that all the Universal Messaging servers that are being linked are running. |
NUMSPME0263 | Unable to rollback the added Universal Messaging server instance links. |
Explanation |
An error occurred when rolling back the Universal Messaging instance links added to the zone. |
Action |
Check the detailed error message. |
NUMSPME0264 | Unable to delete zone {0} with Universal Messaging server {1}. |
Explanation |
An error occurred while deleting a zone with the Universal Messaging server. |
Action |
Check the detailed error message. |
NUMSPME0265 | Unable to create or update the cluster as the server URL provided is invalid. |
Explanation |
The URL provided for the Universal Messaging server instance is invalid. |
Action |
Please provide a valid URL for the Universal Messaging server instance. |
NUMSPME0266 | Cannot disable this interface. At least one interface needs to be enabled. |
Explanation |
At least one interface should be enabled for a Universal Messaging server. |
Action |
Ensure that you enable at least one interface for a Universal Messaging server. |
NUMSPME0267 | The specified prime site is invalid, the prime site specified does not belong to the cluster. |
Explanation |
The specified prime site is invalid. |
Action |
Specify one of the sites defined in the cluster as the prime site. |
NUMSPME0268 | Unable to create zone as the zone name is not provided or is invalid. |
Explanation |
Cannot create or update zone with an empty or invalid name. |
Action |
Provide a valid zone name. |
NUMSPME0269 | Unable to add Universal Messaging server {0} to the zone. It is already part of zone {1}. |
Explanation |
Unable to add Universal Messaging server to the zone as it is already a part of a different zone. |
Action |
Provide a different Universal Messaging server or remove the server from the other zone. |
NUMSPME0270 | Unable to create or update the zone as the server URL provided is invalid. |
Explanation |
The URL provided for the Universal Messaging server instance is invalid. |
Action |
Please provide a valid URL for the Universal Messaging server instance. |
NUMSPME0271 | Unable to create/update the zone as it should contain at least one cluster. |
Explanation |
The zone create/update cannot be performed because a zone should contain at least one cluster. |
Action |
Ensure that at least one cluster is part of the zone. |
NUMSPME0272 | Unable to retrieve the configured user repository file path for instance {0}. |
Explanation |
Unable to retrieve the configured user repository file path for instance {0}. |
Action |
Verify if the user repository file is configured for the instance {0}. |
NUMSPME0273 | Unable to create/update the zone as it should contain at least one realm. |
Explanation |
The zone create/update cannot be performed because a zone should contain at least one realm. |
Action |
Ensure that at least one realm is part of the zone. |
NUMSPME0274 | Universal Messaging instance management update operation has failed for instance {0}. |
Explanation |
Universal Messaging instance management update operation has failed. |
Action |
Please confirm that the Universal Messaging instance is stopped. |
NUMSPME0275 | Cannot create a clustered store on a non-clustered realm. |
Explanation |
Cannot create a clustered store on a non-clustered realm. |
Action |
Create a cluster and recreate the store, or change the store to local. |
NUMSPMI0048 | The Universal Messaging server instance {0} is not a part of any cluster. |
Explanation |
This Universal Messaging sever instance is not a part of any cluster. |
Action |
No action required. |
NUMSPMW0004 | Unable to connect to the Command Central interface of the Universal Messaging server {0}. |
Explanation |
Interface factory could not connect to any interface. |
Action |
Please contact webMethods Administrator. |