Explanation | Bus names must be unique within the administrative domain. |
Action | Specify a name for this bus that is not already in use within the administrative domain. |
Explanation | The specified bus name could not be located within the administrative domain. |
Action | Make sure that the bus name specified is a valid bus name for an existing bus. |
Explanation | Only one instance of a bus should exist with the name specified, yet more than one instance has been located. |
Action | Make sure that bus names are unique within the administrative domain. |
Explanation | An attempt has been made to add a server to a bus of which it is already a member. |
Action | Do not attempt to add a bus member if the server in question is already a member. |
Explanation | The messaging engine specified already exists on the server. |
Action | Make sure that the messaging engine details are not identical to that of another messaging engine on the server. |
Explanation | An exception was generated attempting to create a bus member with the configuration data provided. |
Action | Make sure that all configuration data for the bus member is valid. |
Explanation | An incorrect destination type has been specified. |
Action | Make sure that the destination type specified is valid. |
Explanation | The parameters supplied do not provide a valid bus member configuration. |
Action | To correctly identify a bus member, specify node name and server name, or cluster name, or WebSphere MQ server name. |
Explanation | The details specified do not represent a valid scope specification. |
Action | Make sure that valid node name, server name and cluster name details are used to represent the scope. |
Explanation | The destination specified already exists on the bus. |
Action | Make sure that destinations on the bus have unique names. |
Explanation | An attempt has been made to create an alias destination without sufficient configuration detail. |
Action | Make sure that an alias parameter is specified when creating the alias destination. |
Explanation | An attempt has been made to create an foreign destination without sufficient configuration detail. |
Action | Make sure that a foreign parameter is specified when creating the foreign destination. |
Explanation | The operation could not be invoked because the given messaging engine does not exist for the given bus at the specified scope. |
Action | Make sure that a correct messaging engine name and scope are specified. |
Explanation | Multiple messaging engines have been found matching the configuration data provided. |
Action | Make sure that messaging engines are unique within the administrative domain. |
Explanation | An attempt has been made to locate a SIB JDBC provider within the scope provider, but none was found. |
Action | Make sure that there is a SIB JDBC provider available within the administrative domain. |
Explanation | An exception occurred creating a data source with the configuration data provided. |
Action | Make sure that the configuration data provided to create a data source is valid. |
Explanation | An exception occurred creating a resource property set with the configuration data provided. |
Action | Make sure that the configuration data provided to create a resource property set is valid. |
Explanation | The specified bus member is not a member of this bus. |
Action | Make sure that the specified bus member is a member of this bus. |
Explanation | An exception occurred creating a messaging engine with the configuration data provided. |
Action | Make sure that the configuration data provided to create a messaging engine is valid. |
Explanation | An exception occurred creating a data store with the configuration data provided. |
Action | Make sure that the configuration data provided to create a data store is valid. |
Explanation | Bus names cannot contain any of the following characters \/,#$@:;"*?<>|=+&%' or start with _ or . or contain ]]> . |
Action | Make sure that a valid bus name is specified for the bus that is to be created. |
Explanation | An exception has occurred attempting to delete a bus with the name specified. |
Action | Make sure that a valid bus name is specified for the bus that is to be deleted. |
Explanation | The bus member specified could not be located within the administrative domain. |
Action | Make sure that a valid bus member is being located. |
Explanation | Only one instance of a bus member should exist within the scope specified, yet more than one instance has been located. |
Action | Make sure that bus members have unique configuration data within an administrative domain. |
Explanation | A messaging engine already exists with the configuration data supplied. |
Action | Make sure that unique configuration data is specified for the messaging engine that is to be created. |
Explanation | The destination with the name specified cannot be deleted. |
Action | Make sure that a valid destination name is specified for the destination that is to be deleted. |
Explanation | An exception occurred attempting to locate the specified destination. |
Action | Make sure that the destination being located exists within the administrative domain. |
Explanation | Only one instance of a destination should exist within the scope specified, yet more than one instance has been located. |
Action | Make sure that destinations have unique configuration data within an administrative domain. |
Explanation | An exception occurred due to multiple buses having identical UUIDs. |
Action | Make sure that each bus in an administrative domain has a unique UUID. |
Explanation | The UUID specified does not belong to a bus in the administrative domain. |
Action | Make sure that the UUID specified belongs to a valid bus. |
Explanation | A suitable messaging engine name could not be created. |
Action | Try specifying different configuration data when creating the messaging engine. |
Explanation | More than one destination within the administrative domain has the same UUID. |
Action | Make sure that each destination within the administrative domain has a unique UUID. |
Explanation | No SIB services were found for this messaging server. |
Action | Make sure that a SIB service exists for this messaging server. |
Explanation | The named destination could not be located on the named bus within the administrative domain. |
Action | Make sure that the named destination exists on the named bus. |
Explanation | Either the specified parameter was not supplied, or no value was supplied for it. |
Action | Run the command again, supplying the missing parameter value. |
Explanation | The value supplied for the specified parameter of the specified command is not valid. |
Action | Run the command again, supplying a valid value. |
Explanation | Either the specified parameter was not supplied for the specified step, or no value was supplied for it. |
Action | Run the command again, supplying the missing parameter value for the specified step. |
Explanation | An internal error occurred while trying to determine values for the reliability and maxReliability parameters. |
Action | Report this problem to your system administrator. |
Explanation | The value supplied for the reliability parameter should be less than or equal to the value supplied for the maxReliability parameter. |
Action | Run the command again, supplying a value for the reliability parameter that is less than or equal to the value supplied for the maxReliability parameter. |
Explanation | The value supplied for the specified parameter was not recognized. |
Action | Run the command again, supplying a valid value. |
Explanation | The destination name supplied to the createSIBDestination command is not valid. |
Action | Run the command again, supplying a valid destination name. |
Explanation | The value supplied for the specified parameter is not valid. |
Action | Run the command again, supplying a valid value. |
Explanation | The node, server and cluster parameters should not be specified when the type is WebServices. |
Action | Run the command again, supplying a valid combination of parameters. |
Explanation | An internal error occurred while validating the reliability and maxReliability parameters. |
Action | Report this problem to your system administrator. |
Explanation | A reply destination cannot be specified without a reply destination name. The reply destination object will be removed. |
Action | If a reply destination is required specify at least the reply destination name. |
Explanation | An attempt has been made to add an MQ server to a bus of which it is already a member. |
Action | Do not try to add an WebSphere MQ server to a bus of which it is already a member. |
Explanation | An exception occurred creating a WebSphere MQ server bus member with the configuration data provided. |
Action | Make sure that the configuration data provided to create a WebSphere MQ server bus member is valid. |
Explanation | When added to a bus, a WebSphere MQ server should have one bus member target. None was found. |
Action | Report this problem to your system administrator. |
Explanation | When added to a bus, a WebSphere MQ server should have one bus member target. More than one was found. |
Action | Report this problem to your system administrator. |
Explanation | The supplied parameter is not valid when adding a server or a cluster to a bus. |
Action | Remove the parameter from the addSIBusMember command then retry the command. |
Explanation | The supplied parameter is not valid when creating a destination. The parameter supplied is only valid when specifying a WebSphere MQ server name. |
Action | Remove the parameter from the createSIBDestination command then retry the command. |
Explanation | The supplied parameter is not valid when creating a destination. The parameter supplied is only valid when not specifying a WebSphere MQ server name. |
Action | Remove the parameter from the createSIBDestination command then retry the command. |
Explanation | When creating a destination the WebSphere MQ server name was specified with a destination type other than QUEUE. |
Action | Change the destination type to be QUEUE then retry the command. |
Explanation | When creating a destination on a WebSphere MQ server the wmqQueueName parameter must be specified. |
Action | Change the destination type to be QUEUE then retry the command. |
Explanation | The message store type can be either a file store or a data store, but not both. Therefore parameters relating to both types are not allowed in the same command. |
Action | Either remove parameters relating to file store, or to data store. |
Explanation | When the size of the permanent file store has been set to unlimited, a maximum permanent size cannot be set. |
Action | Remove the maximum permanent file store size parameter or change the unlimited permanent file store size to false then retry. |
Explanation | A file store could not be created with the configuration data provided. |
Action | Make sure that the configuration data provided to create a file store is valid. |
Explanation | There is an unexpected problem with the system. |
Action | Check the log files for information about the problem. |
Explanation | A file store parameter has been specified for a data store, or a data store parameter has been specified for a file store. |
Action | Check that the parameters are correct for this message store type. |
Explanation | Certain default parameters do not apply with clusters, therefore valid values must be specified. |
Action | Check that parameters are correct for this message store type on a cluster. |
Explanation | A value for the specified parameter is required to create a message store of this type. |
Action | Check that the parameters are correct for this message store type. |
Explanation | The permanent file store size must be greater than the file store log size. |
Action | Increase the permanent store size or decrease the log size. |
Explanation | The log size specified is lower than the minimum log size. |
Action | Increase the size of the log file. |
Explanation | The maximum permanent store size specified is lower than the maximum permanent store size minimum value. |
Action | Increase the size of the maximum permanent store size, or make it unlimited. |
Explanation | Maximum store size cannot be less than minimum store size. |
Action | Either lower the minimum store size, or increase the maximum store size, or make the maximum store size unlimited. |
Explanation | The busSecurity parameter is not compatible with WebSphere Application Server Version 6.0. The busSecurity parameter is only valid for Version 6.1 and later. |
Action | Either set the scriptCompatibility to 6.1, or use the secure parameter with scriptCompatibility set to 6. |
Explanation | The secure parameter is not compatible with WebSphere Application Server Version 6.1. The secure parameter is only valid for Version 6.0. |
Action | Either set the scriptCompatibility to 6, or use the busSecurity parameter with scriptCompatibility set to 6.1. |
Explanation | You cannot set the busSecurity parameter to true unless you also enable administrative security. |
Action | Either use the administrative console to enable administrative security, or set the busSecurity parameter to false. |
Explanation | The permitted transport chain with the specified name was not found on the bus. |
Action | Use the administrative console to check that the transport chain name exists and that the case of the name is correct, then reissue the command. |
Explanation | The supplied parameter permittedChains has a value that is not valid, so the command was rejected. |
Action | Set the permittedChains to an allowable value of ALL, SSL_ENABLED or LISTED. |
Explanation | You cannot specify the permittedChains parameter with the secure parameter. |
Action | Use the busSecurity parameter instead of the secure parameter. |
Explanation | You can only use a file store with a messaging engine on a WebSphere Application Server Version 6.1 or later node. |
Action | Select a data store, or choose a node that is of Version 6.1 or later. |
Explanation | An attempt was made to add a transport chain as a permitted transport to the bus. This was unsuccessful because the transport chain is already a permitted transport for the bus. |
Action | Add a transport chain with a different name. |
Explanation | An attempt was made to remove a permitted transport from a bus. However the specified permitted transport chain is not a permitted transport for the specified bus. |
Action | If the permitted transport exists on the bus, check and correct the name then reissue the command. |
Explanation | The value supplied for the parameter scriptCompatibility is not valid. |
Action | Run the command again, supplying a value that is either 6 (for compatability with WebSphere Application Server Version 6.0) or 6.1 (for compatability with Version 6.1). |
Explanation | The specified destination could not be found on the specified bus. |
Action | Make sure that the destination being located exists within the administrative domain. |
Explanation | When mediating a destination that has a message point on WebSphere MQ, the pre-mediation point MQ queue name must not be the same as the message point MQ queue name. |
Action | Choose a different WebSphere MQ destination from which the mediation is to get messages. |
Explanation | You cannot specify the busSecurity parameter with the secure parameter. |
Action | Remove either the busSecurity or the secure parameter from the modifySIBus command. |
Explanation | The parameter supplied can only be used when the destination type is Queue, Port or WebService. |
Action | Run the command again without using the previously stated parameter. |
Explanation | Allowable values for the port parameter range between 0 and 65535. |
Action | Run the command again specifying a valid port value. |
Explanation | The maximum length for a WebSphere MQ queue manager or queue sharing group is 48 characters. |
Action | Run the command again specifying a valid WebSphere MQ queue manager or queue sharing group value. |
Explanation | The WebSphere MQ queue manager or queue sharing group allowable characters range a-z, A-Z, 0-9, ., /, % and _. |
Action | Run the command again specifying a valid WebSphere MQ queue manager or queue sharing group value. |
Explanation | The maximum length for a WebSphere MQ channel is 20 characters. |
Action | Run the command again specifying a valid WebSphere MQ channel value. |
Explanation | The WebSphere MQ queue channel allowable characters range a-z, A-Z, 0-9, ., /, % and _. |
Action | Run the command again specifying a valid WebSphere MQ channel value. |
Explanation | The details specified do not represent a valid scope specification. |
Action | Make sure that valid node and server name details are used to represent the scope. |
Explanation | The details specified do not represent a valid scope specification. |
Action | Make sure that valid cluster name details are used to represent the scope. |
Explanation | The topicAccessCheckRequired parameter can only be used when the destination type is TopicSpace. |
Action | Remove the parameter specified, then reissue the command. |
Explanation | When the size of the temporary file store has been set to unlimited, a maximum temporary size cannot be set. |
Action | Remove the maximum temporary file store size parameter or change the unlimited temporary file store size to false then retry. |
Explanation | The temporary file store size must be greater than the temporary store log size. |
Action | Increase the temporary store size or decrease the log size. |
Explanation | The maximum temporary store size specified is lower than the maximum temporary store size minimum value. |
Action | Increase the size of the maximum temporary store size, or make it unlimited. |
Explanation | An attempt is being made to configure a maximum temporary store size with a value that is less than the minimum temporary store size. |
Action | Either lower the minimum temporary store size, increase the maximum temporary store size, or make the maximum temporary store size unlimited. |
Explanation | The maximum length for a WebSphere MQ reply to queue is 48 characters. |
Action | Run the command again specifying an allowable WebSphere MQ reply to queue value. |
Explanation | The WebSphere MQ reply to queue allowable characters range a-z, A-Z, 0-9, ., /, % and _. |
Action | Run the command again specifying an allowable WebSphere MQ reply to queue value. |
Explanation | The deleteSIBDestination command takes either the aliasBus or the foreignBus parameter. The command had both parameters supplied. |
Action | If there are multiple destinations with the same name, then the aliasBus or foreignBus parameter can be used to identify either an Alias or a Foreign destination to delete. Only one of the aliasBus or foreignBus parameters can be supplied. |
Explanation | The named alias destination could not be located on the named bus within the administrative domain. |
Action | Make sure that the named alias destination exists on the named bus with the named alias bus. |
Explanation | The named foreign destination could not be located on the named bus within the administrative domain. |
Action | Make sure that the named foreign destination exists on the named bus with the named foreign bus. |
Explanation | 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 option was set that implied that a file store is to be used. |
Action | Run the command again, this time specifying a data store. |
Explanation | The option to maintain strict message order is only available on WebSphere Application Server Version 6.1 or later. |
Action | Run the command again. Only specify strict message ordering if you also specify a server of Version 6.1 or later. |
Explanation | The operation could not be invoked because the specified server or cluster is not a member of the given bus. |
Action | Make sure that a server or cluster is specified that is a member of the given bus. |
Explanation | The operation could not be invoked because no messaging engines exist at the specified scope for the given bus. |
Action | Make sure that there is a messaging engine at the specified scope for the given bus. |
Explanation | The operation could not be invoked because the messaging engine with the given UUID does not exist at the specified scope. |
Action | Make sure that there is a messaging engine at the specified scope. |
Explanation | The server could not be added to the bus because the server resides on a WebSphere Application Server Version 6.0 node, and bus security settings are not compatible with pre-Version 6.1 nodes. The permitted transport chains setting must not be LISTED or SSL_ENABLED. The Server group must not be in the bus connector role. |
Action | Disable security on the named bus, or modify the bus security settings so that bus security is compatible with pre-Version 6.1 nodes, or upgrade the named server so that it resides on a Version 6.1 node. |
Explanation | The cluster could not be added to the bus because at least one of its member servers resides on a WebSphere Application Server Version 6.0 node, and bus security settings are not compatible with pre-Version 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. |
Action | Disable security on the named bus, or modify the bus security settings so that bus security is compatible with pre-Version 6.1 nodes, or upgrade the pre-Version 6.1 servers on the named cluster so that they reside on Version 6.1 nodes. |
Explanation | Enabling bus security, or changing the named bus security attribute to the indicated value when the bus contains one or more WebSphere Application Server Version 6.0 bus members, is not allowed because the value is not compatible with pre-Version 6.1 bus members. The permitted transport chains setting must not be LISTED or SSL_ENABLED. |
Action | Disable security on the named bus, or modify the named security setting to a value that does not conflict with pre-Version 6.1 bus members, or remove all pre-Version 6.1 bus members from the bus. |
Explanation | The named bus contains one or more WebSphere Application Server Version 6.0 bus members. Having the named group in the bus connector role is not compatible with pre-Version 6.1 bus members. The Server group must not be in the bus connector role. |
Action | Disable security on the named bus, or remove the named group from the bus connector role, or remove all pre-Version 6.1 bus members from the bus. |
Explanation | The assistanceEnabled and policyName parameters are valid only when you add a server cluster as a bus member. |
Action | Either do not use the assistanceEnabled and policyName parameters, or add a server cluster as a bus member. |
Explanation | Valid policy names are HA, SCALABILITY, SCALABILITY_HA, or CUSTOM. |
Action | Either specify a valid policy name, or do not use messaging engine policy assistance (set the assistanceEnabled parameter to false). |
Explanation | To use messagine engine policy assistance, set the assistanceEnabled parameter to true and specify a policyName parameter. |
Action | Either set the assistanceEnabled parameter to true and specify a valid policyName parameter, or do not use messaging engine policy assistance (set the assistanceEnabled parameter to false). |
Explanation | The failover, failback, preferredServersOnly, and preferredServerList parameters are valid only when assistanceEnabled is true and policyName is CUSTOM. |
Action | Either set the assistanceEnabled parameter to true and the policyName parameter to CUSTOM, or or do not use these parameters. |
Explanation | You specified a server in the preferred servers list when that server is not a member of the current cluster. |
Action | Ensure that the servers specified for the preferredServerList parameter are members of the current cluster. |
Explanation | To modify messagine engine policy assistance for a cluster, specify either the assistanceEnabled or the policyName parameter. |
Action | Specify the assistanceEnabled parameter, the policyName parameter, or both. |
Explanation | To use messagine engine policy assistance, set the assistanceEnabled parameter to true and specify a valid policyName parameter. Valid policy names are HA, SCALABILITY, SCALABILITY_HA, or CUSTOM. |
Action | Either specify a valid policy name, or do not use messaging engine policy assistance (set the assistanceEnabled parameter to false). |
Explanation | To disable messaging engine policy assistance, set the assistanceEnabled parameter to false and do not specify a policyName parameter. |
Action | Either set the assistanceEnabled parameter to false and do not specify a policyName parameter, or set the assistanceEnabled parameter to true and specify a valid policyName parameter. |
Explanation | The failover parameter is set to false but either the preferredServersOnly parameter is set to false or the preferredServerList parameter does not specify one server. |
Action | Either ensure that the preferredServersOnly parameter is set to true and the preferredServerList parameter specifies one server, or set the failover parameter to true. |
Explanation | The failover parameter is set to false, but the failback parameter is set to true. |
Action | Either set the failback parameter to false, or set the failover parameter to true. |
Explanation | The failover parameter is set to true and the preferredServersOnly parameter is set to true, but the the preferredServerList parameter does not specify at least two servers (one to run on, and one to fail over to). |
Action | Either ensure that the preferredServerList parameter specifies at least two servers, or set the preferredServersOnly parameter to false. |
Explanation | You specified a new policyName parameter when the assistanceEnabled parameter is set to false. |
Action | Ensure that the assistanceEnabled parameter is set to true, then specify a valid policyName parameter. |
Explanation | You attempted to create a core group policy for a messaging engine when the messaging engine is not associated with a server cluster that is a member of a bus. |
Action | Ensure that the name parameter is the name of a messaging engine that is associated with a server cluster that is a member of a bus. |
Explanation | To create a core group policy for a messaging engine, the server cluster that the messaging engine is associated with must have messaging engine policy assistance enabled and the CUSTOM policy specified. |
Action | Either specify a messaging engine that is associated with a server cluster that has messaging engine policy assistance enabled and the CUSTOM policy specified, or use modifySIBusMemberPolicy to modify the server cluster so that messaging engine policy assistance is enabled and the CUSTOM policy is specified. |
Explanation | To correct a core group policy for a messaging engine, the server cluster that the messaging engine is associated with must have messaging engine policy assistance enabled and the HA, SCALABILITY, or SCALABILITY_HA policy specified. |
Action | Either specify a messaging engine that is associated with a server cluster that has messaging engine policy assistance enabled and a valid policy type specified, or use modifySIBusMemberPolicy to modify the server cluster so that assistanceEnabled is true and policyName is set to a valid policy type. |
Explanation | The bus name that was supplied to the command could not be resolved to a Bus object. |
Action | Ensure that you used the correct spelling for the name, and that a Bus with that name exists in the configuration. |
Explanation | The node and server names that were supplied to the command could not be used to resolve a Server object. |
Action | Ensure that you used the correct spelling for the node and server names, and that the Server exists in the configuration. |
Explanation | The old bus and server names that were supplied to the command could not be used to resolve a messaging engine object. |
Action | Ensure that you used the correct spelling for the old bus and server names, and that the server is a member of the old bus. |
Explanation | The cluster name that were supplied to the command could not be used to resolve a Cluster object. |
Action | Ensure that you used the correct spelling for the cluster name, and that the Cluster exists in the configuration. |
Explanation | The node and server supplied to the command do not correspond to a member of the cluster supplied. |
Action | Ensure that you used the correct spelling for the node, server and cluster name, and that the server is a member of the cluster. |
Explanation | To migrate a server messaging engine to a cluster, the cluster cannot be a member of the same bus already. |
Action | Ensure that the cluster is not a member of the same bus to which the server belongs. |
Explanation | The node and server supplied to the command do not correspond to a member of the bus supplied. |
Action | Ensure that you used the correct spelling for the node, server and bus name, and that the server is a member of the bus. |
Explanation | A suitable messaging engine name could not be created. |
Action | Try specifying different configuration data when creating the messaging engine. |
Explanation | The parameters supplied do not provide a valid bus member configuration. |
Action | To correctly identify a bus member, specify node name and server name, or cluster name. |
Explanation | An exception occurred retrieving the SIB Services for the messaging server. |
Action | Ensure that a SIB Service exists for the messaging server. |
Explanation | The details specified do not represent a valid scope specification. |
Action | Make sure that valid node name, server name and cluster name details are used to represent the scope. |
Explanation | The supplied parameter bootstrapPolicy has a value that is not valid, so the command was rejected. |
Action | Set the bootstrapPolicy to an allowable value of MEMBERS_ONLY, SIBSERVICE_ENABLED, MEMBERS_AND_NOMINATED. |
Explanation | The bootstrap member policies of MEMBERS_ONLY and MEMBERS_AND_NOMINATED are not supported by pre-7.0 nodes, as a result they cannot be specified for a bus that contains pre-7.0 bus members. |
Action | Specify a setting that is supported by a bus with pre-7.0 members, or remove all pre7.0 bus members from the bus. |
Explanation | The server could not be added to the bus because the server resides on a pre-7.0 WebSphere Application Server Version node, and the bootstrap policy setting is not compatible with pre-Version 7.0 nodes. The bootstrap policy setting must not be MEMBERS_ONLY, or MEMBERS_AND_NOMINATED. |
Action | Change the bootstrap policy to be SIBSERVICE_ENABLED, or upgrade the named server so that it resides on a Version 7.0 node. |
Explanation | The cluster could not be added to the bus because the cluster has members that reside on a pre-7.0 WebSphere Application Server Version node, and the bootstrap policy setting is not compatible with pre-Version 7.0 nodes. The bootstrap policy setting must not be MEMBERS_ONLY, or MEMBERS_AND_NOMINATED. |
Action | Change the bootstrap policy to be SIBSERVICE_ENABLED, or upgrade the named cluster so that all servers in the cluster reside on a Version 7.0 node. |
Explanation | The server could not be added to the bus because the bus has been configured to use the server identity for mediations, but the server resides on a pre-7.0 WebSphere Application Server Version node. The useServerIdForMediations is not compatible with pre-Version 7.0 nodes. |
Action | Change the bus to use an authentication alias for mediations instead of the server identity. |
Explanation | The cluster could not be added to the bus because the bus has been configured to use the server identity for mediations, but the cluster contains members that reside on pre-7.0 WebSphere Application Server Version node. The useServerIdForMediations is not compatible with pre-Version 7.0 nodes. |
Action | Change the bus to use an authentication alias for mediations instead of the server identity. |
Explanation | The bus contains servers or clusters that run on pre-Version 7.0 nodes. The userServerIdForMediations option does not support pre-Version 7.0 nodes so the command could not complete. |
Action | Upgrade the pre-Version 7.0 nodes. |
Explanation | The supplied initial JVM heap size value is not in the acceptable range. |
Action | Change the supplied initial JVM heap size value to one that is in the acceptable range. |
Explanation | The supplied maximum JVM heap size value is not in the acceptable range. |
Action | Change the supplied maximum JVM heap size value to one that is in the acceptable range. |
Explanation | The given destination is specified more than once in the nameList. |
Action | Make sure that the destinations specified in the nameList are unique. |
Explanation | The supplied initial JVM heap size value is bigger than the supplied maximum JVM heap size value. |
Action | Change the supplied initial and maximum JVM heap size values so that the initial JVM heap size value is not be bigger than the maximum JVM heap size value. |
Explanation | The auditAllowed parameter can only be used when the destination type is TopicSpace. |
Action | Remove the parameter specified, then reissue the command. |
Explanation | Specifying queue points is only permitted when the alias directly targets a Queue destination. |
Action | Do not supply the "queuePoints" parameter, or supply it and target a Queue destination. |
Explanation | Specifying queue points is only permitted when the alias directly targets a Queue destination in the same bus as the alias definition (the 'bus' parameter). |
Action | Do not supply the "queuePoints" parameter, or supply it and target a Queue destination in the same bus as the alias definition. |
Explanation | Specifying queue points is only permitted when the alias directly targets a Queue destination localized to a bus member with multiple messaging engines. |
Action | Do not supply the "queuePoints" parameter, or supply it and target a Queue destination localized to a bus member with multiple messaging engines. |
Explanation | Each queue point must be a SIBQueueLocalizationPoint belonging to the target queue. |
Action | Identify any non valid queue point(s) and correct the list. |
Explanation | Specifying mediation points is only permitted when the alias directly targets a Queue destination. |
Action | Do not supply the "mediationPoints" parameter, or supply it and target a Queue destination. |
Explanation | Specifying mediation points is only permitted when the alias directly targets a Queue destination in the same bus as the alias definition (the 'bus' parameter). |
Action | Do not supply the "mediationPoints" parameter, or supplpy it and target a Queue destination in the same bus as the alias definition. |
Explanation | Specifying mediation points is only permitted when the alias directly targets a Queue destination localized to a bus member with multiple messaging engines. |
Action | Do not supply the "mediationPoints" parameter, or supply it and target a Queue destination localized to a bus member with multiple messaging engines. |
Explanation | Each mediation point must be a SIBMediationPoint belonging to the target queue. |
Action | Identify any non valid mediation point(s) and correct the list. |
Explanation | It is not valid to supply either queuePoints or mediationPoints when the destination type is not set to ALIAS. |
Action | Only supply "queuePoints" or "mediationPoints" when the destination type is set to ALIAS. |
Explanation | It is not valid to supply a target destination for an Alias destination that is localized on an MQ Server. |
Action | Supply a target destination that is not localized on an MQ Server. |
Explanation | It is not valid to clear this option (setting it false) unless queuePoints contains at least one queue point |
Action | Either set useAllQueuePoints true, or set queuePoints to contain at least one queue point |
Explanation | It is not valid to clear this option (setting it false) unless mediationPoints contains at least one mediation point |
Action | Either set useAllQueuePoints true, or set mediationPoints to contain at least one mediation point |
Explanation | Multiple server bus members for each service integration bus are not allowed for base profiles. |
Action | Review the proposed service integration bus configuration requirements and either adopt a single server bus member for each service integration bus deployment or use multiple server bus members for each service integration bus in a non-base profile. |
Explanation | An unsuccessful attempt was made to locate a JMS JCA resource adapter installed at the specified scope. |
Action | Make sure that a JMS JCA resource adapter exists within the specified scope. |
Explanation | An incorrect type has been found for the connection factory. |
Action | Make sure that the connection factory type is either Queue, Topic or All. |
Explanation | The command was run but no result object was returned. |
Action | Make sure that the correct configuration information has been passed to the command being run. |
Explanation | The target object specified is not of type QueueConnectionFactory, TopicConnectionFactory or ConnectionFactory. |
Action | Make sure that a valid connection factory interface is specified to the target object. |
Explanation | The interface of the target object is not of type Queue. |
Action | Make sure that the target object is of type Queue. |
Explanation | The interface of the target object is not of type Topic. |
Action | Make sure that the target object is of type Topic. |
Explanation | The name provided for the SIB JMS connection factory does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | The name provided for the SIB JMS connection factory does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | The name provided for the SIB JMS queue does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | The name provided for the SIB JMS queue does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | The name provided for the SIB JMS Topic does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | The name provided for the SIB JMS topic does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | The value provided for the specified JMS Queue property is not valid. |
Action | Make sure that the value specified is allowed for the given property. |
Explanation | The value provided for the specified JMS Topic property is not valid. |
Action | Make sure that the value specified is allowed for the given property. |
Explanation | An instance of a JMS Queue with the specified queue name could not be created. |
Action | Make sure that a valid queue name has been specified upon creation of the Queue object. |
Explanation | An instance of a JMS topic with the specified topic name could not be created. |
Action | Make sure that a valid topic name has been specified upon creation of the Topic object. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The named ActivationSpec already exists on the specified resource adapter. |
Action | Make sure that ActivationSpec objects are unique within a given scope. |
Explanation | The create command ran but no result object was returned. |
Action | Make sure that the correct configuration information has been passed to the create command being run. |
Explanation | It is likely that incorrect or null parameters were passed to the modify command. |
Action | Make sure that all parameters passed to the modify command are valid. |
Explanation | It is likely that incorrect or null parameters were passed to the command. |
Action | Make sure that all parameters are valid, and that a JMS JCA resource adapter is installed at the specified scope. |
Explanation | The list command was unsuccessful either because null parameters were given, or no result was returned. |
Action | Make sure that all parameters passed to the command are valid, and not null. |
Explanation | The target object specified is not of the correct type. |
Action | Make sure that the target object is of type JMS ActivationSpec. |
Explanation | The name provided for the SIB JMS ActivationSpec does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | The name provided for the SIB JMS ActivationSpec does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | A value that is not valid has been entered for the read ahead property. |
Action | Check the documentation for a valid value for this property. |
Explanation | A value that is not valid has been entered for the destination type property. |
Action | Check the documentation for a valid value for this property. |
Explanation | A value that is not valid has been entered for the target type property. |
Action | Check the documentation for a valid value for this property. |
Explanation | A value that is not valid has been entered for the target significance property. |
Action | Check the documentation for a valid value for this property. |
Explanation | A value that is not valid has been entered for this property. Valid values are GuaranteedByUser and NotGuaranteedByUser. |
Action | Make sure that a valid value is entered for the property. |
Explanation | A value that is not valid has been entered for this property. Valid values are true and false. |
Action | Make sure that a valid value is entered for the property. |
Explanation | A value that is not valid has been entered for the retry interval property. |
Action | Check the documentation for a valid value for this property. |
Explanation | Valid values are zero which indicates that MDB endpoints will not be automatically stopped. Or one or more, which indicates the number of failing sequential messages that will cause the MDB endpoint to be stopped. |
Action | Specify a value of zero or more. |
Explanation | Valid values are zero or more, which indicate the period of time in milliseconds that passes before a failing message is retried before its maximum failed delivery limit is reached |
Action | Specify a value of zero or more. |
Explanation | The message delay is only used when sequential message failures are being monitored and the MDB endpoint can be automatically stopped. |
Action | Specify a value of zero for the failingMessageDelay or a positive value for autoStopSequentialMessageFailure. |
Explanation | The mediation specified already exists within the administrative domain. |
Action | Make sure that all mediations are uniquely identified within an administrative domain. |
Explanation | The mediation specified could not be found within the administrative domain. |
Action | Make sure that the mediation specified to the command exists. |
Explanation | A mediation cannot be deleted whilst it is being used to mediate a destination. |
Action | Make sure that a mediation is not being used before trying to delete it. |
Explanation | The destination specified could not be found within the administrative domain. |
Action | Make sure that the specified destination exists. |
Explanation | The destination specified is already mediated, and a destination cannot be mediated twice. |
Action | Make sure that the specified destination is not already mediated before trying to mediate it. |
Explanation | Null parameters have been supplied to the command. |
Action | Make sure that either the node and server parameters, or the cluster parameter, is supplied to the command. |
Explanation | The bus member specified could not be located in the administrative domain. |
Action | Make sure that the bus member specified exists before trying to use it. |
Explanation | An inconsistent configuration has been detected. |
Action | Run cross document validation to check the destination configuration. |
Explanation | You cannot un-mediate a destination which is not already mediated. |
Action | Make sure that the destination is mediated before attempting to un-mediate it. |
Explanation | The name provided for the mediation does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | The name provided for the mediation does not adhere to naming restrictions. |
Action | Make sure that the name does not begin with an underscore, and is not empty or null. |
Explanation | Invalid parameters have been supplied to the command. When specifying the wmqServer parameter, you must specify execution point where the mediation will run. |
Action | Make sure that the wmqServer parameter is supplied with either the node and server parameters, or the cluster parameter. |
Explanation | The supplied parameter is not valid when mediating a destination and a WebSphere MQ server name was not specified. |
Action | Remove the parameter from the mediateSIBDestination command then retry. |
Explanation | When specifying a WebSphere MQ server name a WebSphere MQ Queue name must be supplied. |
Action | Add the wmqQueueName parameter to the mediateSIBDestination command then retry. |
Explanation | When mediating a destination using a WebSphere MQ server it must have been added to the bus, but no bus member was found. |
Action | Make sure that the WebSphere MQ server has been added to the bus specified then retry the command. |
Explanation | The node parameter specifies a WebSphere Application Server Version 6.0 node. This node cannot host a mediation execution point for a WebSphere MQ mediated destination. |
Action | Select a node that is of Version 6.1 or later. |
Explanation | External mediation support is only valid for destinations localized to WebSphere MQ. |
Action | Either specify a false value for the externallyMediated parameter or add a wmqServer parameter. |
Explanation | Externally mediating destinations are only supported for destinations that are localized in WebSphere MQ. |
Action | Remove the node, server or cluster parameter that was specified. |
Explanation | Externally mediating destinations are only supported for destinations that are localized in WebSphere MQ. |
Action | Set the externallyMediated parameter to false, or mediate a destination that is assigned to WebSphere MQ. |
Explanation | The configuration archive does not contain any cells. |
Action | Make sure that the configuration archive contains a cell. |
Explanation | The deployment manager configuration does not contain any cells. |
Action | Make sure that the deployment manager configuration contains a cell. |
Explanation | 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. |
Action | Make sure that the named bus does not exist in the deployment manager configuration before running the addNode command. If there is a conflict in the names, the bus on the node being federated is not 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 renamed or deleted. |
Explanation | The configuration does not contain any cells. |
Action | Make sure that the configuration contains a cell. |
Explanation | No cells were found in the deployment manager configuration. |
Action | Make sure that the deployment manager configuration contains a cell definition. |
Explanation | Internal error. Method invoked requires a deployment manager configuration session parameter. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. Method invoked requires a cell object. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. Method invoked requires a bus object. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. Method invoked requires destination object. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. The specified command did not return a result. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. The application server template ID is null. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | The specified WebSphere MQ server name could not be located within the administrative domain. |
Action | Make sure that the WebSphere MQ server name specified is a valid name for an existing WebSphere MQ server. |
Explanation | Only one instance of a WebSphere MQ server should exist with the name specified, yet more than one instance has been found. |
Action | Make sure that WebSphere MQ server names are unique within the administrative domain. |
Explanation | A WebSphere MQ server name must be unique. A WebSphere MQ server with the supplied name already exists. |
Action | Make sure that WebSphere MQ server names are unique within the administrative domain. |
Explanation | The specified WebSphere MQ server proxy name could not be located within the bus administrative domain. |
Action | 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. |
Explanation | Only one instance of a WebSphere MQ server proxy should exist with the name specified, yet more than one instance has been located. |
Action | Make sure that WebSphere MQ server proxy names are unique within the administrative domain. |
Explanation | Only custom JMS providers can be deleted. |
Action | Select a different JMS provider to delete. |
Explanation | A WebSphere MQ server must be supplied as the target object |
Action | Set a WebSphere MQ server as the target object. |
Explanation | A WebSphere MQ server SVRCONN channel must have a name. |
Action | Set the WebSphere MQ server SVRCONN channel name using the "name" parameter. |
Explanation | The parameters "sslEndpoint", "sslChain", "sslCRL", "sslReset" and "sslPeer" are not valid when the "sslType" parameter is set to "NONE". |
Action | Specify a different sslType or do not use the illegal parameters. |
Explanation | The parameters "sslEndpoint" and "sslChain" are not valid when the "sslType" parameter is set to "CENTRAL". |
Action | Specify a different sslType or do not use the illegal parameters. |
Explanation | The "sslChain" parameter is not valid when the "sslType" parameter is set to "SPECIFIC". |
Action | Specify a different sslType or do not use the illegal parameters. |
Explanation | The "sslChain" parameter is not valid when the "sslType" parameter is set to "CHAIN". |
Action | Specify a different sslType or do not use the illegal parameters. |
Explanation | Valid values for the sslType parameter are "NONE", "CENTRAL", "SPECIFIC" and "CHAIN". |
Action | Set the sslType parameter to be either "NONE", "CENTRAL", "SPECIFIC" or "CHAIN" |
Explanation | The "sendExitInit" parameter can only be supplied if the "sendExit" parameter is supplied. |
Action | Supply the "sendExit" parameter or do not suplly the "sendExitInit" parameter. |
Explanation | The "receiveExitInit" parameter can only be supplied if the "receiveExit" parameter is supplied. |
Action | Supply the "receiveExit" parameter or do not suplly the "receiveExitInit" parameter. |
Explanation | The "securityExitInit" parameter can only be supplied if the "securityExit" parameter is supplied. |
Action | Supply the "securityExit" parameter or do not suplly the "securityExitInit" parameter. |
Explanation | A WebSphere MQ server endpoint must have a host. |
Action | Set the WebSphere MQ server endpoint host using the "host" parameter. |
Explanation | A WebSphere MQ server endpoint must have a port. |
Action | Set the WebSphere MQ server endpoint port using the "port" parameter. |
Explanation | A valid value must be supplied for the endpoint port. |
Action | Set the WebSphere MQ server endpoint with a valid port number. |
Explanation | A WebSphere MQ server endpoint must be supplied as the target object |
Action | Set a WebSphere MQ server endpoint as the target object. |
Explanation | At least one of the endpoint attributes must be modified |
Action | Supply either a host, port or both parameters. |
Explanation | A WebSphere MQ server server connection channel must be supplied as the target object |
Action | Set a WebSphere MQ server server connection channel as the target object. |
Explanation | A foreign bus name was supplied to the command that could not be resolved on the specified bus. |
Action | Make sure that the foreign bus supplied to the command exists in the configuration. |
Explanation | When the routingType parameter is set to Indirect, a valid nextHopBus parameter must be supplied. |
Action | Make sure that the nextHopBus parameter and value is supplied to the command. |
Explanation | When the routingType parameter = Direct, a valid type parameter must be specified. |
Action | Make sure that the type parameter for the command is either SIBus or MQ. |
Explanation | The routingType of either Direct or Indirect is required for this command. |
Action | Make sure that the routingType parameter for the command is either Direct or Indirect. |
Explanation | The foreign bus specified to the command does not have a virtual link child object. |
Action | Make sure that the foreign bus specified has a virtual link child object. |
Explanation | The foreign bus specified contains a SIBVirtualGatewayLink, not the required SIBVirtualMQLink. |
Action | Make sure that the foreign bus specified has a SIBVirtualMQLink child object. |
Explanation | The value of the default priority attribute must be between 0 and 9 inclusive. |
Action | Make sure that a valid value is specified for the default priority attribute. |
Explanation | The value supplied for the reliability parameter should be less than or equal to the value supplied for the maxReliability parameter. |
Action | Report this problem to your system administrator. |
Explanation | The type of either MQ or SIBus is required for this command. |
Action | Make sure that the type parameter for the command is either MQ or SIBus. |
Explanation | The type parameter is only permitted if the routingType parameter is also supplied. |
Action | Make sure that the routingType parameter is supplied if the type parameter is supplied. |
Explanation | 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 to which you are connecting. |
Action | Make sure that the name parameter supplied is different to the bus parameter. |
Explanation | An incorrect value has been supplied. Valid values are BEST_EFFORT_NONPERSISTENT, EXPRESS_NONPERSISTENT, RELIABLE_NONPERSISTENT, RELIABLE_PERSISTENT or ASSURED_PERSISTENT. These values are case sensitive. |
Action | Make sure the a valid value is supplied to the command. |
Explanation | The bus name that was supplied to the command could not be resolved to a Bus object. |
Action | Make sure that you used the correct spelling for the name, and that a Bus with that name exists in the configuration. |
Explanation | A messaging engine name was supplied to the command that could not be resolved on the bus name supplied. |
Action | Make sure that both the messaging engine and bus name supplied to the command exist in the configuration. |
Explanation | A value that is not valid was supplied for the parameter specified above. |
Action | See the command help for a list of valid parameter values. |
Explanation | An internal error has occurred. See linked exception for details. |
Action | Make sure that a valid MQLink name was specified to the command. |
Explanation | The foreign bus name supplied to the command is not the name of a foreign bus configured on the bus. |
Action | Make sure that both the foreign bus and bus name supplied to the command exist in the configuration. |
Explanation | The messaging engine UUID specified above could not be found on any of the existing bus member targets. |
Action | Make sure that the correct messaging engine was supplied to the command. |
Explanation | An MQLink with the name supplied could not be found on the messaging engine supplied. |
Action | Make sure that both the messaging engine and MQLink named on the command exist in the configuration. |
Explanation | This command requires a valid SIB MQLink object to be passed in as the target object. |
Action | Ensure that the target object of the command is a SIB MQLink object. |
Explanation | An internal error has occurred. See the linked exception for details. |
Action | Make sure that a valid SIBLink name was specified to the command. |
Explanation | The foreign bus specified to the command does not have a SIBVirtualGatewayLink child object. |
Action | Make sure that the foreign bus specified has a SIBVirtualGatewayLink child object. |
Explanation | The foreign bus specified contains a SIBVirtualMQLink, not the required SIBVirtualGatewayLink. |
Action | Make sure that the foreign bus specified has a SIBVirtualGatewayLink child object. |
Explanation | A SIBLink name was supplied to the command that could not be resolved on the messaging engine name supplied. |
Action | Make sure that both the messaging engine and SIBLink names supplied to the command exist in the configuration. |
Explanation | SIBLink and MQLink objects share a namespace within a messaging engine, and require unique names. |
Action | 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. |
Explanation | The details specified do not represent a valid scope specification. |
Action | Make sure that valid node name, server name and cluster name details are used to represent the scope. |
Explanation | The preferLocal attribute can only be set to false when a cluster running the messaging engine contains only v7.0 servers. |
Action | Ensure that the messaging engine hosting the link is running in a cluster containing only v7.0 servers before setting the preferLocal attribute to false. |
Explanation | The preferLocal attribute can only be set to true when the server running the messaging engine is v7.0. |
Action | Ensure that the messaging engine hosting the link is running on a v7.0 server before setting the preferLocal attribute to true. |
Explanation | The foreign bus specified already contains a reference to a SIBLink. |
Action | Ensure that a foreign bus is specified that doesn't reference a pre-existing SIBLink. |
Explanation | The foreign bus specified already contains a reference to a MQLink. |
Action | Ensure that a foreign bus is specified that doesn't reference a pre-existing MQLink. |
Explanation | An AdminTask command is trying to work with a process that is not connected to a server that has a running configuration service. |
Action | Reissue the command on a process that is connected to a server that has a running configuration service. For example a deployment manager, managed server or unmanaged server. |
Explanation | An AdminTask command is specifying both a target object and one of the parameters that is used to specify the target. |
Action | Reissue the command either specifying the target object directly, or specifying the target object using the target parameters. |
Explanation | An AdminTask command is invoked without specifying either a target object or the parameters that are used to specify the target. |
Action | Reissue the command either specifying the target object directly, or specifying the target object using the target parameters. |
Explanation | The command should specify a specific server or a cluster. To specify a server a valid node name and server name must be provided. To specify a cluster just the cluster name should be provided. |
Action | Rerun the command specifying either a node and server name, or a cluster name. |
Explanation | The specified cluster does not exist. |
Action | Rerun the command specifying the name of a cluster that exists. |
Explanation | The specified server does not exist. |
Action | Rerun the command specifying the name of a server and node that exists. |
Explanation | The specified cluster is not a bootstrap member, so cannot be removed from the list of bootstrap members. |
Action | Rerun the command specifying the name of a cluster that is a bootstrap member. |
Explanation | The specified server is not a bootstrap member, so cannot be removed from the list of bootstrap members. |
Action | Rerun the command specifying the name of a server and node that is a bootstrap member. |
Explanation | In order for clusters to be bootstrap members all the servers in the cluster must be on a node whose version is at least 7.0.0.0. |
Action | This can be resolved either by upgrading all the nodes, or by choosing a different cluster. |
Explanation | A cluster cannot be both a bus member and a bootstrap member. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | In order for a server to be a bootstrap member the node it is defined to needs to have a version that is at least 7.0.0.0. |
Action | This can be resolved either by upgrading the nodes, or by choosing a server on a different node. |
Explanation | A server cannot be both a bus member and a bootstrap member. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |