Problem | Bus names must be unique within the administrative domain. |
User response | Specify a unique bus name that is not already in existence within the administrative domain. |
Problem | The specified bus name could not be located within the administrative domain. |
User response | Make sure that the bus name specified is a valid bus name for an existing bus. |
Problem | Only one instance of a bus should exist with the name specified, yet more than one instance has been located. |
User response | Make sure that bus names are unique within the administrative domain. |
Problem | An attempt has been made to add a server to a bus of which it is already a member. |
User response | Do not attempt to add a bus member if the server in question is already a member. |
Problem | The messaging engine specified already exists on the server. |
User response | Ensure that the messaging engine details are not identical to that of another messaging engine on the server. |
Problem | An exception was generated attempting to create a bus member with the configuration data provided. |
User response | Ensure that all configuration data for the bus member is valid. |
Problem | An Incorrect destination type has been specified. |
User response | Make sure the destination type specified is a valid destination type. |
Problem | The parameters supplied do not provide a valid bus member configuration. |
User response | To correctly identify a bus member, specify node name and server name, or cluster name, or WebSphere MQ server name. |
Problem | The details specified do not represent a valid scope specification. |
User response | Make sure that valid node name, server name and cluster name details are used to represent the scope. |
Problem | The destination specified already exists on the bus. |
User response | Ensure that destinations on a bus have unique names. |
Problem | An attempt has been made to create an alias destination without sufficient configuration detail. |
User response | Make sure that an Alias parameter is specified when creating an alias destination. |
Problem | An attempt has been made to create an foreign destination without sufficient configuration detail. |
User response | Make sure that a foreign parameter is specified when creating an foreign destination. |
Problem | The operation could not be invoked because the given messaging engine does not exist for the given bus at the specified scope. |
User response | Ensure that a correct messaging engine name and scope are specified. |
Problem | Multiple messaging engines have been found matching the configuration data provided. |
User response | Ensure that messaging engines are unique within an administrative domain. |
Problem | An attempt has been made to locate a SIB JDBC provider within the scope provider, but none was found. |
User response | Ensure that there is a SIB JDBC provider available within the administrative domain. |
Problem | An exception occurred creating a data source with the configuration data provided. |
User response | Make sure that the configuration data provided to create a data source is valid. |
Problem | An exception occurred creating a resource property set with the configuration data provided. |
User response | Make sure that the configuration data provided to create a resource property set is valid. |
Problem | An exception occurred dealing with a bus member which is not a member of the specified bus. |
User response | Ensure that the bus member supplied is a member of the specified bus. |
Problem | An exception occurred creating a messaging engine with the configuration data provided. |
User response | Make sure that the configuration data provided to create a messaging engine is valid. |
Problem | An exception occurred creating a data store with the configuration data provided. |
User response | Make sure that the configuration data provided to create a data store is valid. |
Problem | The specified bus contained illegal characters. Bus names cannot contain any of the following characters \/,#$@:;"*?<>|=+&%' or start with _ or . or contain ]]> . |
User response | Ensure that a valid bus name is being specified upon bus creation. |
Problem | An exception has occurred attempting to delete a bus with the name specified. |
User response | Ensure that a valid bus name is being specified upon bus deletion. |
Problem | The bus member specified could not be located within the administrative domain. |
User response | Ensure that a valid bus member is being located. |
Problem | Only one instance of a bus member should exist within the scope specified, yet more than one instance has been located. |
User response | Ensure that bus members have unique configuration data within an administrative domain. |
Problem | A messaging engine already exists with the configuration data supplied. |
User response | Ensure that unique configuration data is supplied when creating a messaging engine. |
Problem | An exception has occurred attempting to delete a destination with the name specified. |
User response | Ensure that a valid destination name is being specified upon destination deletion. |
Problem | An exception occurred attempting to locate the specified destination. |
User response | Ensure that the destination being located exists within the administrative domain. |
Problem | Only one instance of a destination should exist within the scope specified, yet more than one instance has been located. |
User response | Ensure that destinations have unique configuration data within an administrative domain. |
Problem | An exception occurred due to multiple buses having identical UUIDs. |
User response | Ensure that each bus in an administrative domain has a unique UUID. |
Problem | The UUID specified does not belong to a bus in the administrative domain. |
User response | Ensure that the UUID specified belongs to a valid bus. |
Problem | A suitable messaging engine name could not be created. |
User response | Try specifying different configuration data when creating the messaging engine. |
Problem | An exception occurred due to multiple destinations having identical UUIDs. |
User response | Ensure that each destination in an administrative domain has a unique UUID. |
Problem | An exception occurred retrieving the SIB Services for the messaging server. |
User response | Ensure that a SIB Service exists for the messaging server. |
Problem | The named destination could not be located on the named bus within the administrative domain. |
User response | Make sure that the named destination exists on the named bus. |
Problem | Either the specified parameter was not supplied, or no value was supplied for it. |
User response | Run the command again, this time supplying the missing parameter value. |
Problem | The value supplied for the specified parameter of the specified command was not valid. |
User response | Run the command again, this time supply a valid value. |
Problem | Either the specified parameter was not supplied for the specified step, or no value was supplied for it. |
User response | Supply the missing parameter value for the specified step. |
Problem | An internal error occurred while trying to determine values for "reliability" and "maxReliability". |
User response | Report this problem to your system administrator. |
Problem | The value supplied for "reliability" should be less than or equal to the value supplied for "maxReliability". |
User response | Report this problem to your system administrator. |
Problem | The value supplied for the specified parameter was not recognized. |
User response | Run the command again, this time supplying a valid value. |
Problem | The destination name supplied to the createSIBDestination command is not valid. |
User response | Supply a valid destination name. |
Problem | The value supplied for the specified parameter was not valid. |
User response | Run the command again, this time supply a valid value. |
Problem | The node, server and/or cluster parameters should not be specified when type is "WebServices". |
User response | Run the command again, this time supply a valid combination of parameters. |
Problem | An internal error occurred while validating reliability and maxReliability. |
User response | Report this problem to your system administrator. |
Problem | A reply destination can not be specified with out a reply destination name. The reply destination object will be removed |
User response | If a reply destination is required specify at least the reply destination name. |
Problem | An attempt has been made to add an MQ server to a bus of which it is already a member. |
User response | Do not attempt to add an WebSphere MQ server to a bus of which it is already a member. |
Problem | An exception occurred creating a WebSphere MQ server Bus Member with the configuration data provided. |
User response | Make sure that the configuration data provided to create a WebSphere MQ server Bus Member is valid. |
Problem | When added to a bus, a WebSphere MQ server should have one bus member target. None was found. |
User response | Report this problem to your system administrator. |
Problem | When added to a bus, a WebSphere MQ server should have one bus member target. More than one was found. |
User response | Report this problem to your system administrator. |
Problem | The supplied parameter was not valid when adding a Server or a Cluster to a bus. |
User response | Remove the parameter from the addSIBusMember command and retry. |
Problem | The supplied parameter was not valid when creating a Destination. The parameter supplied is only valid when specifying a WebSphere MQ Server name. |
User response | Remove the parameter from the createSIBDestination command and retry. |
Problem | The supplied parameter was not valid when creating a Destination. The parameter supplied is only valid when not specifying a WebSphere MQ Server name. |
User response | Remove the parameter from the createSIBDestination command and retry. |
Problem | When creating a destination the WebSphere MQ Server name was specified with a destination type which was not QUEUE. |
User response | Change the destination type to be QUEUE and retry the command. |
Problem | When creating a destination on a WebSphere MQ Server the wmqQueueName parameter must be specified. |
User response | Change the destination type to be QUEUE and retry the command. |
Problem | -fileStore and -dataStore are mutually exclusive, likewise parameters relating to both types are not allowed in the same command |
User response | Either remove parameters relating to file store or data store |
Problem | When the size of the permanent file store has been set to unlimited, a maximum permanent size can not be set |
User response | Remove the maximum permanent file store size parameter or change the unlimited permanent file store size to false then retry. |
Problem | An exception occurred creating a file store with the configuration data provided. |
User response | Make sure that the configuration data provided to create a file store is valid. |
Problem | This scenario shouldnt occur. |
User response | Unexpected error has occured. |
Problem | A file store parameter has been specified for a data store or vise versa. |
User response | Check parameters are correct for this message store type |
Problem | Certain default parameters dont apply with clusters, therefore must be specified |
User response | Check parameters are correct for this message store type |
Problem | A value for parameter {1} is required to create {0} |
User response | Check parameters are correct for this message store type |
Problem | The permanent file store size must be greater than the file store log size |
User response | Increase the permanent store size or decrease the log size |
Problem | The log size specified is lower than the minimum log size |
User response | Increase the size of the log file |
Problem | The maximum permanent store size specified is lower than the maximum permanent store size minimum value |
User response | Increase the size of the maximum permanent store size, or make it unlimited |
Problem | Maximum store size can not be less than minimum store size |
User response | either lower the minimum store size, increase the size of the maximum store size or make it unlimited |
Problem | The busSecurity parameter being specified and scriptCompatibility set to 6 is invalid. The busSecurity parameter is only valid with scriptCompatibility set to 6.1 |
User response | Either set the scriptCompatibility to 6.1 or use the secure parameter. |
Problem | The secure parameter being specified and scriptCompatibility set to 6.1 is invalid. The secure parameter is only valid with scriptCompatibility set to 6 |
User response | Either set the scriptCompatibility to 6 or use the busSecurity parameter. |
Problem | The busSecurity parameter has been specified to be enabled, but administrative security is not enabled. |
User response | Either enable administrative security in the Admin Console, or set the busSecurity to be false. |
Problem | The permitted transport chain with the specified name was not found on the bus |
User response | Check that the transport chain name should exist in the Admin console. Check that the case of the name is correct and try the command again. |
Problem | The supplied parameter permittedChains has an invalid value so the command was rejected |
User response | Set the permittedChains to an allowable value of either ALL, SSL_ENABLED or LISTED |
Problem | The permittedChains parameter being specified with the secure parameter is invalid. |
User response | Use the busSecurity parameter instead of the secure parameter. |
Problem | The filestore option is only valid for messaging engines created on version 6.1 or later nodes. |
User response | Select a datastore, or choose a node which is of version 6.1 or later. |
Problem | An attempt was made to add a transport chain as a permitted transport to the bus. This failed as the transport chain is already a permitted transport for the bus. |
User response | Add a transport chain with a different name. |
Problem | An attempt was made to remove a permitted transport from a bus. The permitted transport chain specified is not a permitted transport for the bus specified. |
User response | If the permitted transport does exist on the bus, check the name and correct and reissue the command. |
Problem | The value supplied for the parameter scriptCompatibility was not valid. |
User response | Run the command again, this time supply a valid value which is either 6 or 6.1. |
Problem | The specified destination could not be found on the specified bus. |
User response | Ensure that the destination being located exists within the administrative domain. |
Problem | When mediating a destination whose message point is on WebSphere MQ, the pre-mediation point MQ queue name must not be the same as the message point's MQ queue name. |
User response | Choose a different WebSphere MQ destination from which the mediation is to get messages from |
Problem | The busSecurity parameter being specified with the secure parameter is invalid. |
User response | Remove either the busSecurity or the secure parameter from the modifySIBus command. |
Problem | The parameter supplied can only be used when the destination type is Queue, Port or WebService. |
User response | Run the command again without using the previously stated parameter. |
Problem | The range of allowable values for the port parameter range between 0 and 65535. |
User response | Run the command again specifying a valid port value. |
Problem | The maximum length for a WebSphere MQ queue manager or queue sharing group is 48 characters. |
User response | Run the command again specifying a valid WebSphere MQ queue manager or queue sharing group value. |
Problem | The WebSphere MQ queue manager or queue sharing group allowable characters range a-z, A-Z, 0-9, ., /, % and _. |
User response | Run the command again specifying a valid WebSphere MQ queue manager or queue sharing group value. |
Problem | The maximum length for a WebSphere MQ channel is 20 characters. |
User response | Run the command again specifying a valid WebSphere MQ channel value. |
Problem | The WebSphere MQ queue channel allowable characters range a-z, A-Z, 0-9, ., /, % and _. |
User response | Run the command again specifying a valid WebSphere MQ channel value. |
Problem | The details specified do not represent a valid scope specification. |
User response | Make sure that valid node and server name details are used to represent the scope. |
Problem | The details specified do not represent a valid scope specification. |
User response | Make sure that valid cluster name details are used to represent the scope. |
Problem | The parameter "topicAccessCheckRequired" supplied can only be used when the destination type is TopicSpace. |
User response | Run the command again and remove the parameter specified. |
Problem | When the size of the temporary file store has been set to unlimited, a maximum temporary size can not be set. |
User response | Remove the maximum temporary file store size parameter or change the unlimited temporary file store size to false then retry. |
Problem | The temporary file store size must be greater than the temporary store log size. |
User response | Increase the temporary store size or decrease the log size. |
Problem | The maximum temporary store size specified is lower than the maximum temporary store size minimum value. |
User response | Increase the size of the maximum temporary store size, or make it unlimited. |
Problem | Maximum temporary store size can not be less than minimum temporary store size. |
User response | either lower the minimum temporary store size, increase the size of the maximum temporary store size or make it unlimited. |
Problem | The maximum length for a WebSphere MQ reply to queue is 48 characters. |
User response | Run the command again specifying an allowable WebSphere MQ reply to queue value. |
Problem | The WebSphere MQ reply to queue allowable characters range a-z, A-Z, 0-9, ., /, % and _. |
User response | Run the command again specifying an allowable WebSphere MQ reply to queue value. |
Problem | The deleteSIBDestination command takes either the "aliasBus" or the "foreignBus" parameters. The command had both parameters supplied. |
User response | If there are multiple destinations with the same name, then the aliasBus, foreignBus parameters can be used to identify an Alias, or a Foreign destination to delete. Only one of aliasBus or foreignBus parameters can be supplied. |
Problem | The named Alias destination could not be located on the named bus within the administrative domain. |
User response | Make sure that the named Alias destination exists on the named bus with the named alias bus. |
Problem | The named Foreign destination could not be located on the named bus within the administrative domain. |
User response | Make sure that the named Foreign destination exists on the named bus with the named foreign bus. |
Problem | The support for a file store is only available on WebSphere Application Server version 6.1 or later. Either the -fileStore option was specified or another one that implied it. |
User response | Run the command again, this time specifying a data store. |
Problem | The maintain strict message order support is only available on WebSphere Application Server version 6.1 or later. |
User response | Run the command again, this time either not specifying strict message ordering, or specifying a server of version 6.1 or later. |
Problem | The operation could not be invoked because the specified server or cluster is not a member of the given bus. |
User response | Ensure that a server or cluster is specified which is a member of the given bus. |
Problem | The operation could not be invoked because no messaging engines exist for the given bus at the specified scope. |
User response | Ensure that there is a messaging engine at the specified scope for the given bus. |
Problem | The operation could not be invoked because the messaging engine with the given UUID does not exist at the specified scope. |
User response | Ensure that there is a messaging engine at the specified scope. |
Problem | The server could not be added to the bus because the server resides on a pre-6.1 node, and bus security settings are not compatible with pre-6.1 nodes. The permitted transport chains setting must not be "LISTED" or "SSL_ENABLED". The group "Server" must not be in the bus connector role. |
User response | Disable security on the named bus, or modify the bus security settings so that it is compatible with pre-6.1 nodes, or upgrade the named server so that it resides on a 6.1 node. |
Problem | The cluster could not be added to the bus because at least one of its member servers resides on a pre-6.1 node, and bus security settings are not compatible with pre-6.1 nodes. The permitted transport chains setting must not be "LISTED" or "SSL_ENABLED". The group "Server" must not be in the bus connector role. |
User response | Disable security on the named bus, or modify the bus security settings so that it is compatible with pre-6.1 nodes, or upgrade the pre-6.1 servers on the named cluster so that they reside on 6.1 nodes. |
Problem | Enabling bus security and/or changing the named bus security attribute to the indicated value when the bus contains one or more pre-6.1 bus members is not allowed because the value is not compatible with pre-6.1 nodes. The permitted transport chains setting must not be "LISTED" or "SSL_ENABLED". |
User response | Disable security on the named bus, or modify the named security setting to a value that does not conflict with pre-6.1 bus members, or remove all pre-6.1 bus members from the bus. |
Problem | The named bus contains one or more pre-6.1 bus members. Having the named group in the bus connector role is not compatible with pre-6.1 bus members. The group "Server" must not be in the bus connector role. |
User response | Disable security on the named bus, or remove the named group from the bus connector role, or remove all pre-6.1 bus members from the bus. |
Problem | The given destination is specified more than once in the nameList. |
User response | Make sure that the destinations specified in the nameList are unique. |
Problem | At unsuccessful attempt was made to locate a JMS JCA resource adapter installed at the specified scope. |
User response | Ensure that a JMS JCA resource adapter exists within the specified scope. |
Problem | An incorrect type has been found for the connection factory. |
User response | Ensure that the connection factory type is either Queue, Topic or All. |
Problem | The command was run but no result object was returned. |
User response | Ensure that the correct configuration information has been passed to the command being run. |
Problem | The target object specified is not of type QueueConnectionFactory, TopicConnectionFactory or ConnectionFactory. |
User response | Ensure that a valid connection factory interface is specified to the target object. |
Problem | The interface of the target object is not of type Queue. |
User response | Ensure that the target object is of type Queue. |
Problem | The interface of the target object is not of type Topic. |
User response | Ensure that the target object is of type Topic. |
Problem | The name provided for the SIB JMS connection factory does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | The name provided for the SIB JMS connection factory does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | The name provided for the SIB JMS queue does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | The name provided for the SIB JMS queue does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | The name provided for the SIB JMS Topic does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | The name provided for the SIB JMS topic does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | An illegal value has been provided for the JMS Queue property specified. |
User response | Ensure that the value specified is legal for the given property. |
Problem | An illegal value has been provided for the JMS Topic property specified. |
User response | Ensure that the value specified is legal for the given property. |
Problem | An internal exception was thrown creating an instance of a JMS Queue. |
User response | Ensure that a valid queue name has been specified upon creation of the Queue object. |
Problem | An internal exception was thrown creating an instance of a JMS Topic. |
User response | Ensure that a valid queue name has been specified upon creation of the Topic object. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The named ActivationSpec already exists on the specified resource adapter. |
User response | Ensure that ActivationSpec objects are unique within a given scope. |
Problem | The create command ran but no result object was returned. |
User response | Ensure that the correct configuration information has been passed to the create command being run. |
Problem | It is likely that Incorrect or null parameters were passed to the modify command. |
User response | Ensure that all parameters passed to the modify command are valid. |
Problem | It is likely that Incorrect or null parameters were passed to the command. |
User response | Ensure that all parameters are valid, and that a JMS JCA resource adapter is installed at the specified scope. |
Problem | The list command failed either because null parameters were given, or no result was returned. |
User response | Ensure that all parameters passed to the command are valid, and not null. |
Problem | The target object specified is not of the correct type. |
User response | Ensure that the target object is of type JMS ActivationSpec. |
Problem | The name provided for the SIB JMS ActivationSpec does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | The name provided for the SIB JMS ActivationSpec does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | The user has entered a value for the read ahead property which is not valid |
User response | Check the documentation for a valid value |
Problem | The user has entered a value for the destination type property which is not valid |
User response | Check the documentation for a valid value |
Problem | The user has entered a value for the target type property which is not valid |
User response | Check the documentation for a valid value |
Problem | The user has entered a value for the target significance property which is not valid |
User response | Check the documentation for a valid value |
Problem | The mediation specified already exists within the administrative domain. |
User response | Ensure that all mediations are uniquely identified within an administrative domain. |
Problem | The mediation specified could not be found within the administrative domain. |
User response | Ensure that the mediation specified to the command exists. |
Problem | A mediation cannot be deleted whilst it is being used to mediate a destination. |
User response | Ensure that a mediation is not be used before trying to delete it. |
Problem | The destination specified could not be found within the administrative domain. |
User response | Ensure that the destination specified exists. |
Problem | The destination specified is already mediated, and no destination may be mediated twice. |
User response | Ensure that the destination specified is not already mediated before trying to mediate it. |
Problem | Null parameters have been supplied to the command. |
User response | Ensure that either "node" and "server" parameters, or "cluster" parameter is supplied to the command. |
Problem | The bus member specified could not be located in the administrative domain. |
User response | Ensure that the bus member specified exists before trying to use it. |
Problem | An inconsistent configuration has been detected. |
User response | Run cross document validation to check the destination configuration. |
Problem | It is not possible to un-mediate a destination which is not already mediated. |
User response | Ensure that the destination is mediated before attempting to un-mediate it. |
Problem | The name provided for the mediation does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | The name provided for the mediation does not adhere to naming restrictions. |
User response | Ensure that the name does not begin with an underscore, and is not empty or null. |
Problem | Invalid parameters have been supplied to the command. When specifying "wmqServer" an execution point must be specified where the mediation will run. |
User response | Ensure that "wmqServer" is supplied with either "node" and "server" parameters, or "cluster" parameter. |
Problem | The supplied parameter was not valid when mediating a destination and a WebSphere MQ Server name was not specified. |
User response | Remove the parameter from the mediateSIBDestination command and retry. |
Problem | When specifying a WebSphere MQ Server name a WebSphere MQ Queue name must be supplied. |
User response | Add the "wmqQueueName" parameter to the mediateSIBDestination command and retry. |
Problem | When mediating a destination using a WebSphere MQ server it must have been added to the bus, but no bus member was found. |
User response | Ensure that the WebSphere MQ Server has been added to the bus specified and retry the command |
Problem | The node parameter specifies a pre version 6.1 node which cannot host a mediation execution point for a WebSphere MQ mediated destination. |
User response | Select a node which is of version 6.1 or later. |
Problem | External mediation support is only valid for destinations localized to WebSphere MQ. |
User response | Either specify a false value for the "externallyMediated" parameter or add a "wmqServer" parameter. |
Problem | Externally mediating destinations are only supported for destinations that are localized in WebSphere MQ. |
User response | Remove the "node" or "server" or "cluster" parameter that was specified. |
Problem | Externally mediating destinations are only supported for destinations that are localized in WebSphere MQ. |
User response | Set the "externallyMediated" parameter to false or mediate a destination that is assigned to WebSphere MQ. |
Problem | The configuration archive does not contain any cells. |
User response | Make sure that the configuration archive contains a cell. |
Problem | The deployment manager configuration does not contain any cells. |
User response | Make sure that the deployment manager configuration contains a cell. |
Problem | A bus of the same name already exists in the deployment manager configuration. As a result the bus on this node will not be added to the deployment manager configuration. However the node will still be federated. |
User response | Ensure that the named bus does not exist in the deployment manager configuration before running addNode. If there is a conflict in the names, the bus on the node being federated will not be included. As a result the bus on the deployment manager must be configured to have the required resources needed. Either that, or the bus should be either renamed or deleted. |
Problem | The configuration does not contain any cells. |
User response | Make sure that the configuration contains a cell. |
Problem | No cells were found in the deployment manager configuration. |
User response | Ensure that the deployment manager configuration contains a cell definition. |
Problem | Internal error. Method invoked requires a deployment manager configuration session parameter. |
User response | Please contact your system administrator to resolve this problem. |
Problem | Internal error. Method invoked requires a cell object, |
User response | Please contact your system administrator to resolve this problem. |
Problem | Internal error. Method invoked requires a bus object. |
User response | Please contact your system administrator to resolve this problem. |
Problem | Internal error. Method invoked requires destination object. |
User response | Please contact your system administrator to resolve this problem. |
Problem | Internal error. The specified command did not return a result. |
User response | Please contact your system administrator to resolve this problem. |
Problem | Internal error. The application server template ID is null. |
User response | Please contact your system administrator to resolve this problem. |
Problem | The specified WebSphere MQ Server name could not be located within the administrative domain. |
User response | Make sure that the WebSphere MQ Server name specified is a valid name for an existing WebSphere MQ Server. |
Problem | Only one instance of a WebSphere MQ Server should exist with the name specified, yet more than one instance has been found. |
User response | Make sure that WebSphere MQ Server names are unique within the administrative domain. |
Problem | A WebSphere MQ Server name must be unique. A WebSphere MQ Server with the supplied name already exists. |
User response | Make sure that WebSphere MQ Server names are unique within the administrative domain. |
Problem | The specified WebSphere MQ Server Proxy name could not be located within the Bus administrative domain. |
User response | Make sure that the WebSphere MQ Server Proxy name specified is a valid name for an existing WebSphere MQ Server Proxy. Check that the bus name specified is the correct bus for the WebSphere MQ Server Proxy |
Problem | Only one instance of a WebSphere MQ Server Proxy should exist with the name specified, yet more than one instance has been located. |
User response | Make sure that WebSphere MQ Server Proxy names are unique within the administrative domain. |
Problem | Only custom JMS providers can be deleted. |
User response | Select another JMS provider to delete. |
Problem | A Foreign Bus name was supplied to the command which could not be resolved on the Bus provided. |
User response | Ensure that the Foreign Bus supplied to the command exists in the configuration. |
Problem | When the routingType parameter = Indirect, a valid nextHopBus parameter must be supplied. |
User response | Ensure that the nextHopBus parameter and value is supplied to the command. |
Problem | When the routingType parameter = Direct, a valid type parameter must be specified |
User response | Ensure that the type parameter for the command is either "SIBus" or "MQ" |
Problem | The routingType of either "Direct" or "Indirect" is required for this command. |
User response | Ensure that the routingType parameter for the command is either "Direct" or "Indirect" |
Problem | The foreign bus specified to the command does not have a virtual link child object. |
User response | Ensure that the foreign bus specified has a virtual link child object. |
Problem | The foreign bus specified contains a SIBVirtualGatewayLink, not the required SIBVirtualMQLink. |
User response | Ensure that the foreign bus specified has a SIBVirtualMQLink child object. |
Problem | The value of the default priority attribute must be between 0 and 9 inclusive. |
User response | Ensure that a valid value is specified for the default priority attribute. |
Problem | The value supplied for "reliability" should be less than or equal to the value supplied for "maxReliability". |
User response | Report this problem to your system administrator. |
Problem | The type of either "MQ" or "SIBus" is required for this command. |
User response | Ensure that the type parameter for the command is either "MQ" or "SIBus" |
Problem | The type parameter is only permitted if the routingType parameter is also supplied. |
User response | Make sure that the routingType parameter is supplied if the type parameter is supplied. |
Problem | When creating a foreign bus, its name cannot be the same as the local bus on which it is being created. The name should be the unique name of the foreign bus being connected to. |
User response | Make sure that the name parameter supplied is different to the bus parameter. |
Problem | The bus name that was supplied to the command could not be resolved to a Bus object. |
User response | Ensure that you used the correct spelling for the name, and that a Bus with that name exists in the configuration. |
Problem | A messaging engine name was supplied to the command which could not be resolved on the bus name supplied. |
User response | Ensure that both the messaging engine and bus name supplied to the command exist in the configuration. |
Problem | An invalid value was supplied for the parameter specified above. |
User response | See the command help for a list of valid parameter values. |
Problem | An internal error has occured. See linked exception for details. |
User response | Ensure that a valid MQLink name was specified to the command. |
Problem | The foreign bus name supplied to the command is not the name of a foreign bus configured on the bus. |
User response | Ensure that both the foreign bus and bus name supplied to the command exist in the configuration. |
Problem | The engine UUID specified above could not be found on any of the existing Bus Member Targets. |
User response | Ensure that the correct messaging engine was supplied to the command. |
Problem | An MQLink with the name supplied could not be found on the messaging engine supplied. |
User response | Ensure that both the messaging engine and MQLink named on the command exist in the configuration. |
Problem | An internal error has occured. See linked exception for details. |
User response | Ensure that a valid SIBLink name was specified to the command. |
Problem | The foreign bus specified to the command does not have a child SIBVirtualGatewayLink object. |
User response | Ensure that the foreign bus specified has a SIBVirtualGatewayLink child object. |
Problem | The foreign bus specified contains a SIBVirtualMQLink, not the required SIBVirtualGatewayLink. |
User response | Ensure that the foreign bus specified has a SIBVirtualGatewayLink child object. |
Problem | A SIBLink name was supplied to the command which could not be resolved on the messaging engine name supplied. |
User response | Ensure that both the messaging engine and SIBLink name supplied to the command exist in the configuration. |
Problem | SIBLinks and MQLinks objects share a namespace within a Messaging Engine, and require unique names. |
User response | If you want to use the supplied name, ensure that neither an MQLink nor SIBLink already exists with that name. Otherwise, specify a different name. |
Problem | The details specified do not represent a valid scope specification. |
User response | Make sure that valid node name, server name and cluster name details are used to represent the scope. |
Problem | The foreign bus specified already contains a reference to a SIBLink. |
User response | Ensure that a foreign bus is specified that doesn't reference a pre-existing SIBLink. |
Problem | The foreign bus specified already contains a reference to a MQLink. |
User response | Ensure that a foreign bus is specified that doesn't reference a pre-existing MQLink. |
Problem | This message is displayed when an AdminTask command is attempted on a process that is not connected to a server that has a running config service. |
User response | Reissue the command on a process that is connected to a server that has a running config service - for example a deployment manager, managed server or unmanaged server. |