BIP1000-1999: Runtime components - Configuration Manager
- BIP1001
- Message associated with number <insert_0> was not found: data supplied <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A message number was used for which no associated message text could be found.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1002
- Unexpected exception in ConfigurationManager class <insert_1> method; exception text: <insert_0>, <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the ConfigurationManager class <insert_1> method while the Configuration Manager was being started or stopped. The exception text is: <insert_0>, <insert_2>.
- Response
- Retry the operation. If the exception still occurs, contact your IBM support center.
- BIP1003
- The Configuration Manager is available for use.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager has started successfully.
- Response
- No user action required.
- BIP1004
- The Configuration Manager is not available for use.
- Severity
- 30 : Severe error
- Explanation
- A problem has been encountered while trying to start the Configuration Manager. The problem is not expected to be transient.
- Response
- Stop the Configuration Manager using the mqsistop command. Look at previous error messages for the Configuration Manager in the event log. Determine and correct the cause of the problem before attempting to start the Configuration Manager again. If the problem persists contact your IBM support center.
- BIP1005
- The Configuration Manager is no longer available for use.
- Severity
- 20 : Error
- Explanation
- The Configuration Manager has encountered a situation where it is unable to continue processing. However, the situation is expected to be transient and the Configuration Manager will automatically attempt to restart after a short delay.
- Response
- Look at previous error messages for the Configuration Manager in the event log. Determine and correct the cause of the problem if necessary.
- BIP1006
- The Configuration Manager is no longer available for use.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager has encountered a situation where it is unable to continue. The problem is not expected to be transient.
- Response
- Stop the Configuration Manager using the mqsistop command. Look at previous error messages for the Configuration Manager in the event log. Determine and correct the cause of the problem before attempting to start the Configuration Manager again.
- BIP1007
- The Configuration Manager is not available for use.
- Severity
- 20 : Error
- Explanation
- A problem has been encountered while trying to start the Configuration Manager. However the problem is expected to be transient and the Configuration Manager will automatically attempt to restart after a short delay.
- Response
- Look at previous error messages for the Configuration Manager in the event log. Determine and correct the cause of the problem if necessary. If the problem persists contact your IBM support center.
- BIP1008
- Unable to locate file <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A file required by the Configuration Manager could not be found. This may be the result of an inconsistent installation of the Configuration Manager.
- Response
- Ensure that the file exists in the WebSphere Message Brokers directory. Check that the file permissions are such that the file is readable. Retry the operation. If this is still not successful, contact your IBM support center.
- BIP1009
- Trace level not restored due to invalid trace level <insert_0> in repository.
- Severity
- 10 : Warning
- Explanation
- An invalid trace level <insert_0> was found in the configuration repository while attempting to restore the trace level to a previously saved level. The Configuration Manager will continue but trace will not be active.
- Response
- If you need to run with Configuration Manager trace active, use the mqsichangetrace command utility to set the desired trace level. If this problem persists contact your IBM support center.
- BIP1010
- Trace level not preserved due to invalid trace level <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An invalid trace level <insert_0> was encountered while attempting to save the trace level in the configuration repository. The Configuration Manager will continue, but the trace level has not been saved so a subsequent restart may not trace at the correct level.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1011
- Trace level <insert_0> successfully restored.
- Severity
- 0 : Information
- Explanation
- A trace level of <insert_0> has been restored from the configuration repository. The Configuration Manager is now running with trace active at level <insert_0>.
- Response
- No user action required.
- BIP1012
- Unexpected exception creating or deleting Configuration Manager in ConfigurationData class <insert_0> method; exception text: <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the ConfigurationData class <insert_0> method while the Configuration Manager was being created or deleted. The exception text is: <insert_1>.
- Response
- Retry the operation. If the exception still occurs, contact your IBM support center.
- BIP1013
- Unexpected exception in Configuration Manager PersistentTrace class <insert_1> method; exception text: <insert_0>, <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- While restoring or preserving the trace level in the configuration repository, an exception was caught by the PersistentTrace class <insert_1> method. The exception text is: <insert_0>, <insert_2>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1015
- External exception.
- Severity
- 20 : Error
- Explanation
- The Configuration Manager attempted to use the services of an external component, but the component failed with the following error: <insert_0>
- Response
- Contact your IBM support center.
- BIP1016
- Failed to initiate deploy.
- Severity
- 30 : Severe error
- Explanation
- The requested deploy operation failed to initiate.
- Response
- Check there are no existing deploy requests still outstanding then reissue the command.
- BIP1017
- A backup archive called <insert_0> was created successfully.
- Severity
- 0 : Information
- BIP1018
- Unexpected exception in utility <insert_0>; method <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the <insert_0> utility in method <insert_1>. The exception text is: <insert_2>. The current operation will end.
- Response
- For XML parser errors check the XML is well-formed and the correct encoding is specified.
Retry the operation if possible. If the exception still occurs, contact your IBM support center.
- BIP1019
- Message flow <insert_0> could not be found.
- Severity
- 20 : Error
- Explanation
- The utility was asked to start or stop a named message flow <insert_0>, but this is not deployed to execution group <insert_1> on broker <insert_2>.
- Response
- Check that the (case-sensitive) message flow name has been entered correctly. Use the Broker Administration perspective of the Message Brokers Toolkit or the Config Manager Proxy to ensure that the message flow has been deployed successfully.
- BIP1020
- Message flow <insert_0> could not be started.
- Severity
- 20 : Error
- Explanation
- The utility was asked to start message flow <insert_0> running in execution group <insert_1> on broker <insert_2>, but the action did not complete successfully.
- Response
- Ensure that the broker <insert_2> and the Configuration Manager are running and that the current user has the authority defined in the Configuration Manager to control message flows on that execution group. If you suspect that the run state is not being reported correctly, try redeploying the topology using the 'complete' option. If the problem persists, contact your IBM support representative.
- BIP1021
- Message flow <insert_0> could not be stopped.
- Severity
- 20 : Error
- Explanation
- The utility was asked to stop message flow <insert_0> running in execution group <insert_1> on broker <insert_2>, but the action did not complete successfully.
- Response
- Ensure that the broker <insert_2> and the Configuration Manager are running and that the current user has the authority defined in the Configuration Manager to control message flows on that execution group. If you suspect that the run state is not being reported correctly, try redeploying the topology using the 'complete' option. If the problem persists, contact your IBM support representative.
- BIP1022
- At least one message flow could not be started.
- Severity
- 20 : Error
- Explanation
- The following message flows were not reported as running by the time a timeout occurred: <insert_0>. The following message flows were reported as running: <insert_1>.
- Response
- Ensure that the broker <insert_2> and the Configuration Manager are running and that the current user has the authority defined in the Configuration Manager to control message flows on that execution group and broker. If you suspect that the run state is not being reported correctly, try redeploying the topology using the 'complete' option. If the problem persists, contact your IBM support representative.
- BIP1023
- At least one message flow could not be stopped.
- Severity
- 20 : Error
- Explanation
- The following message flows were not reported as stopped by the time a timeout occurred: <insert_1>. The following message flows were reported as having stopped successfully: <insert_0>.
- Response
- Ensure that the broker <insert_2> and the Configuration Manager are running and that the current user has the authority defined in the Configuration Manager to control message flows on that execution group and broker. If you suspect that the run state is not being reported correctly, try redeploying the topology using the 'complete' option. If the problem persists, contact your IBM support representative.
- BIP1024
- Starts message flows.
- Severity
- 0 : Information
- Explanation
- Syntax:
vmsgflow (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b brokerName [-e executionGroupName [-m flowName]] [-w timeoutValue] [-v traceFileName]
- Response
- Command Options:
'-n cfgParameterFileName' File containing Configuration Manager connection parameters (.configmgr)
'-i ipAddress' IP address or host name of the Configuration Manager
'-p port' port number of the Configuration Manager
'-q qMgr' queue manager of the Configuration Manager
'-b brokerName' name of the broker on which to start message flows
'-e executionGroupName' name of the execution group on which to start message flows. If this is not specified, all message flows on the broker will be started.
'-m flowName' name of the message flow to start. If this is not specified, all message flows on the execution group will be started.
'-w timeoutValue' time to wait (in seconds) for message flows to start (Default=60)
'-v traceFileName' send verbose internal trace to the specified file.
- BIP1025
- Stops message flows.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsistopmsgflow (-n cfgFileName | (-i ipAddress -p port -q qMgr)) -b brokerName [-e egName [-m flowName]] [-w timeout] [-v traceFileName]
- Response
- Command Options:
'-n cfgFileName' Configuration Manager connection file (.configmgr)
'-i ipAddress' IP address or host name of the Configuration Manager
'-p port' port number of the Configuration Manager
'-q qMgr' queue manager of the Configuration Manager
'-b brokerName' name of the broker on which to stop message flows
'-e egName' name of the execution group on which to stop message flows. If this is not specified, all message flows on the broker will be stopped.
'-m flowName' name of the message flow to stop. If this is not specified, all message flows on the execution group or broker will be stopped.
'-w timeout' time to wait (in seconds) for message flows to stop (default=60)
'-v traceFileName' send verbose internal trace to the specified file
- BIP1026
- Deploying configuration information to broker <insert_0>...
- Severity
- 0 : Information
- BIP1027
- Submitting request to the Configuration Manager to start <insert_0>...
- Severity
- 0 : Information
- BIP1028
- Submitting request to the Configuration Manager to stop <insert_0>...
- Severity
- 0 : Information
- BIP1029
- Waiting up to <insert_1> second(s) for broker <insert_0> to update its configuration...
- Severity
- 0 : Information
- BIP1030
- Message flow <insert_0> is reported as started.
- Severity
- 0 : Information
- BIP1031
- Message flow <insert_0> is reported as stopped.
- Severity
- 0 : Information
- BIP1032
- Deploys pub/sub topology, topics or BAR file configuration data to the specified broker(s).
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsideploy.bat (-connection cfgParameterFileName | (-i ipAddress -p port -q qMgr)) ((-b brokerName [([-e executionGroupName ((-bar BARFileName [-complete]) | -rm deployedObjects)]) | -cancel]) | (-topology [-complete]) | (-topics [-complete]) | -cancel) [-w timeoutValue] [-v traceFileName]
- Response
- Command Options:
'-connection cfgParameterFileName' Configuration Manager connection parameters (.configmgr)
'-i ipAddress' ip address of Configuration Manager.
'-p port' port number of Configuration Manager.
'-q queueManager' queue manager of Configuration Manager.
'-b brokerName' name of broker to deploy to.
'-e executionGroupName' name of execution group to deploy to.
'-bar BARFileName' deploy the specified Broker Archive file.
'-rm deployedObjects' colon separated list of deployed objects to remove from the execution group.
'-cancel' tells the Configuration Manager to stop waiting for broker responses to currently outstanding deploy requests, across the domain or on the specified broker. Use this flag with caution; any subsequent responses to cancelled deploys will be ignored by the Configuration Manager, meaning that the status reported by the Configuration Manager may be incorrect.
'-topology' deploy pub/sub neighbor configuration to all brokers.
'-topics' deploy topics hierarchy to all brokers.
'-complete' clear existing data before deployment (vs. deploy incremental changes).
'-w timeoutValue' value in seconds to wait for responses.
'-v traceFileName' send verbose internal trace to the specified file.
- BIP1033
- Invalid parameters.
- Severity
- 20 : Error
- Explanation
- The specified flags are invalid or cannot be used together: <insert_0>.
- Response
- Reissue the command specifying valid options and flags.
- BIP1034
- Properties file could not be read
- Severity
- 20 : Error
- Explanation
- A Configuration Manager Proxy application was asked to read connection parameters from the properties file <insert_0> but this could not be found or was found to be invalid.
- Response
- Reissue the command specifying a valid path and file name. If such a file is not available, Use the Message Brokers Toolkit to generate one, or supply the Configuration Manager connection parameters individually.
- BIP1035
- Property missing from properties file.
- Severity
- 30 : Severe error
- Explanation
- Property <insert_0> was not found in the properties file <insert_1>.
- Response
- Reissue the command making sure a valid <insert_1> properties file is in the current directory.
- BIP1036
- Configuration Manager port is not a number.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager port value (<insert_0>) is not valid port number. This must be an integer value.
- Response
- Retry the command specifying a valid port number in the configuration or properties file.
- BIP1037
- Broker not found.
- Severity
- 30 : Severe error
- Explanation
- Broker <insert_0> was not found in the Configuration Manager repository.
- Response
- Reissue the command specifying an existing broker.
- BIP1038
- Execution group not found.
- Severity
- 30 : Severe error
- Explanation
- Either the execution group <insert_0> was not found in the Configuration Manager repository for broker <insert_1>, or you do not have the required permissions to view it.
- Response
- Reissue the command specifying a valid execution group to which you have access.
- BIP1039
- Deploying BAR file <insert_2> to broker <insert_0> (execution group <insert_1>) ...
- Severity
- 0 : Information
- BIP1040
- Waiting <insert_0> second(s) for reply to deploy request for deploy Id <insert_1> ...
- Severity
- 0 : Information
- BIP1041
- Configuration Manager connection parameters could not be found
- Severity
- 20 : Error
- Explanation
- A Configuration Manager Proxy application could not connect to a Configuration Manager because no connection parameters were provided. Furthermore, no default connection parameters could be determined.
- Response
- Reissue the command, specifying a valid set of Configuration Manager connection parameters.
- BIP1042
- Timeout waiting for reply to deploy request (deploy id <insert_0>).
- Severity
- 0 : Information
- BIP1043
- No previous deploy request files found to resolve (file extension <insert_0>).
- Severity
- 0 : Information
- BIP1044
- Connecting to the Configuration Manager's queue manager...
- Severity
- 0 : Information
- BIP1045
- Connecting to the Configuration Manager...
- Severity
- 0 : Information
- BIP1046
- Unable to connect with the Configuration Manager (<insert_0>).
- Severity
- 20 : Error
- Explanation
- The utility encountered a problem while attempting to connect to the Configuration Manager's queue manager to put a message to its request queue.
- Response
- Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the Configuration Manager's queue manager is running and that the current user is able to put messages to its SYSTEM.BROKER.CONFIG.QUEUE. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate.
- BIP1047
- The operation could not be completed by the Configuration Manager.
- Severity
- 20 : Error
- Explanation
- The utility did not receive an expected message from the Configuration Manager within a reasonable amount of time. The cause is described as: <insert_0>
- Response
- Ensure that the Configuration Manager is running and that the correct connection parameters have been supplied to the utility. Use the -w flag to increase the amount of time to wait for responses.
- BIP1055
- Deploying pub/sub neighbors (topology) configuration...
- Severity
- 0 : Information
- BIP1056
- Cancelling all outstanding deploy requests ...
- Severity
- 0 : Information
- BIP1057
- Deploying topics hierarchy...
- Severity
- 0 : Information
- BIP1058
- The Configuration Manager supplied the following message(s):
- Severity
- 0 : Information
- BIP1059
- Please use the Event Log Viewer to view the output of previous deploys.
- Severity
- 0 : Information
- Explanation
- The -r flag has been removed from the mqsideploy utility.
- Response
- Consult the Configuration Manager's event log in order to view the results of previous deployment. This can be done using the Event Log Viewer of the Message Brokers Toolkit or programmatically using the LogProxy class in the Config Manager Proxy. Increasing the value of the timeout period (-w) on the deployment will allow the utility to wait for a longer period of time for broker responses.
- BIP1062
- Removing the following objects from execution group <insert_1>:
<insert_0>
- Severity
- 0 : Information
- BIP1063
- Objects with the following name(s) could not be found on <insert_1>:
<insert_0>
- Severity
- 10 : Warning
- BIP1064
- Removing message set <insert_0> from execution group <insert_1> ...
- Severity
- 0 : Information
- BIP1065
- The CLASSPATH is incorrectly configured
- Severity
- 30 : Severe error
- Explanation
- The utility was unable to start because a required set of Java classes could not be loaded from the CLASSPATH (<insert_0>).
- Response
- Add <insert_1> (from the installed product's classes directory) to the CLASSPATH environment variable and reissue the command.
- BIP1070
- The file <insert_0> cannot be found or is not a valid Configuration Manager archive.
- Severity
- 30 : Severe error
- Explanation
- Reissue the command specifying a valid path and file name for the archive.
- BIP1071
- The specified archive <insert_0> already exists.
- Severity
- 30 : Severe error
- Explanation
- Reissue the command specifying a different archive name for the backup.
- BIP1072
- The internal repository for Configuration Manager <insert_0> cannot be accessed.
- Severity
- 30 : Severe error
- Explanation
- Make sure the Configuration Manager is not running then reissue the command.
- BIP1073
- Creates a backup archive of the specified Configuration Manager's repository.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsibackupconfigmgr configMgrName -d archiveDirectory [-a archiveName] [-w workPath]
- Response
- Command Options:
'configMgrName' name of Configuration Manager to backup.
'-d archiveDirectory' name of the directory the backup archive will be written to.
'-a archiveName' name of the archive
'-w workPath' work path for the Configuration Manager repository
- BIP1074
- Source and target directories are the same!
- Severity
- 30 : Severe error
- Explanation
- The Configuration data repository directory <insert_0> is the same as the backup directory.
- Response
- Reissue the command specifying a different backup directory.
- BIP1075
- Creating backup archive for Configuration Manager <insert_0> in directory <insert_1> ...
- Severity
- 0 : Information
- BIP1076
- Failed to backup the Configuration Manager <insert_0>
- Severity
- 30 : Severe error
- Explanation
- At least one file in the Configuration Manager's repository could not be backed up.
- Response
- Check user access to the backup or restore directory and reissue the command. If this problem persists contact your IBM support center.
- BIP1077
- Failed to find a valid Configuration data respository for <insert_0>
- Severity
- 30 : Severe error
- Explanation
- The Configuration data repository for Configuration Manager <insert_0> is either missing or invalid.
- Response
- Reissue the command specifying a valid Configuration Manager.
- BIP1078
- Restores a configuration data backup archive for the specified Configuration Manager.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsirestoreconfigmgr configMgrName -d archiveDirectory -a archiveName [-w workPath]
- Response
- Command Options:
'configMgrName' name of the Configuration Manager that will have its repository overwritten
'-d archiveDirectory' name of the directory the archive will be read from
'-a archiveName' name of the archive to restore
'-w workPath' work path for the Configuration Manager repository
- BIP1079
- Replacing repository for <insert_0> with archive <insert_1>...
- Severity
- 0 : Information
- BIP1080
- The Configuration Manager is not running.
- Severity
- 0 : Information
- Explanation
- The <insert_0> command attempted to contact the Configuration Manager, but failed because the Configuration Manager is not currently running.
- Response
- Ensure that the Configuration Manager has been started using the &v command.
- BIP1081
- The Configuration Manager encountered an unexpected error.
- Severity
- 0 : Information
- Explanation
- An unexpected exception was returned whilst communicating with the Configuration Manager.
- Response
- Check the previous entries in the error log to determine the cause of the problem.
- BIP1082
- The mqsideploy utility is deploying a BAR file using a v5.x Configuration Manager. If the BAR file contains JAR files or XSL Stylesheets, they will not be deployed. Also, if any files in the BAR file contain embedded keywords, this information will not be extracted.
- Severity
- 0 : Information
- Explanation
- If you wish to deploy JAR files or XSL Stylesheets, or if you wish to reveal embedded version information, reissue the command specifying the location of a higher version Configuration Manager.
- BIP1083
- The Configuration Manager <insert_0> received a CMP request from user <insert_1> (Proxy session ID=<insert_2>, type=<insert_3>).
- Severity
- 0 : Information
- Explanation
- No user action is required.
- BIP1084
- The Configuration Manager <insert_0> responded to the CMP request from user <insert_1> (Proxy session ID=<insert_2>, <insert_3> request elements successful).
- Severity
- 0 : Information
- Explanation
- No user action is required.
- BIP1085
- The Configuration Manager <insert_0> published changes to <insert_1> with UUID <insert_2> to CMP with session ID <insert_3>.
- Severity
- 0 : Information
- Explanation
- No user action is required.
- BIP1086
- The Configuration Manager <insert_0> sent a deploy message to broker <insert_1> (<insert_2>).
- Severity
- 0 : Information
- Explanation
- No user action is required.
- BIP1087
- The Configuration Manager <insert_0> received a deploy response from broker <insert_1> (<insert_2>).
- Severity
- 0 : Information
- Explanation
- No user action is required.
- BIP1088
- The Configuration Manager <insert_0> received a publication from broker <insert_1> (<insert_2>).
- Severity
- 0 : Information
- Explanation
- No user action is required.
- BIP1089
- Ignoring the following name(s) as they are ambiguous on <insert_1>:
<insert_0>
- Severity
- 10 : Warning
- BIP1090
- Cancelling outstanding deploys on broker <insert_0>...
- Severity
- 0 : Information
- BIP1092
- Broker <insert_0> successfully processed the deployment request.
- Severity
- 0 : Information
- BIP1093
- Broker <insert_0> reported the following error(s):
- Severity
- 20 : Error
- BIP1094
- Deployment to broker <insert_0> was not required because its configuration was already up-to-date.
- Severity
- 0 : Information
- BIP1095
- The Configuration Manager has not yet responded to the deployment request.
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager did not respond to the deployment request within a reasonable amount of time. The request is queued for processing and will be completed when the Configuration Manager is able to do so.
- Response
- Ensure that the Configuration Manager is running. It is not usually necessary to repeat the deployment action once the Configuration manager is started. Increasing the value of the timeout period (-w) will allow the utility to wait for a longer period of time for Configuration Manager responses.
- BIP1096
- No broker responses have been received yet.
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager initiated the deployment but no broker responses were received within a reasonable amount of time. The request is queued for processing at the broker(s) and will be completed when it is possible to do so.
- Response
- Ensure that the affected set of brokers is running. It is not usually necessary to repeat the deployment action once the set of brokers is started. Increasing the value of the timeout period (-w) will allow the utility to wait for a longer period of time for broker responses.
- BIP1097
- Some, but not all broker responses have been received yet.
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager initiated the deployment but at least one broker did not respond to the request within a reasonable amount of time. The request is queued for processing at the affected broker(s) and will be completed when it is possible to do so. At this time, no brokers have rejected the deployment.
- Response
- Following this message is the set of broker responses received by the Configuration Manager. Ensure that the affected set of brokers is running. It is not usually necessary to repeat the deployment action once the set of brokers is started. Increasing the value of the timeout period (-w) will allow the utility to wait for a longer period of time for broker responses.
- BIP1098
- At least one failure response has been received.
- Severity
- 20 : Error
- Explanation
- The deployment request was sent to the Configuration Manager but at least one component rejected the deployment.
- Response
- Following this message is the set of responses for each component. Review the errors to discover the cause of the problem.
- BIP1099
- Deployment completed successfully.
- Severity
- 0 : Information
- Explanation
- All brokers affected by the deployment request have successfully processed the message and have updated their configurations accordingly.
- BIP1100
- Broker <insert_0> had not responded before the timeout occurred.
- Severity
- 20 : Error
- BIP1101
- Unknown WebSphere MQ queue manager name <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- When connecting to the WebSphere MQ queue manager during Configuration Manager startup, the name supplied is not that of a queue manager known to WebSphere MQ.
- Response
- The most likely situation is that the queue manager specified on the mqsicreateconfigmgr command -q option has been deleted. You must delete the Configuration Manager using the mqsideleteconfigmgr command, then recreate it using mqsicreateconfigmgr, ensuring that the -q option is specified correctly. To preserve your configuration data in the configuration repository and message repository, do not specify the -n and -m flags on the mqsideleteconfigmgr command. Note also that WebSphere MQ queue manager names are case-sensitive. For more information on this error see the WebSphere MQ Application Programming Reference manual, code 2058.
- BIP1102
- The WebSphere MQ queue manager <insert_0> is not currently available.
- Severity
- 30 : Severe error
- Explanation
- When connecting to the WebSphere MQ queue manager during Configuration Manager startup, queue manager <insert_0> is not up and running. This is expected to be a transient situation and the Configuration Manager will restart after a short interval.
- Response
- Start the WebSphere MQ queue manager and its associated listener. For more information on this error see the WebSphere MQ Application Programming Reference manual, codes 2059, 2161, and 2162.
- BIP1103
- WebSphere MQ queue manager <insert_0> no longer available.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager's connections to WebSphere MQ queue manager <insert_0>, and its associated listener, have been lost. This is expected to be a transient situation and the Configuration Manager will stop then restart after a short interval.
- Response
- Restart the WebSphere MQ queue manager. For more information on this error see the WebSphere MQ Application Programming Reference manual, codes 2009, 2161, and 2162.
- BIP1104
- An authorization error occurred when the Configuration Manager accessed WebSphere MQ object <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- WebSphere MQ has raised an authorization exception while connecting to the WebSphere MQ queue manager, or opening one of the WebSphere MQ queues used by the Configuration Manager. The name of the WebSphere MQ object in question is <insert_0>.
- Response
- Check that the user name passed as the ServiceUserId argument to the mqsicreateconfigmgr utility program is authorized to connect to WebSphere MQ and access the necessary queues. See the WebSphere MQ Message Brokers online documentation, section 'Setting Up Security' for guidance. You may also find help in the WebSphere MQ Application Programming Reference manual, codes 2035 and 2063.
- BIP1105
- Unknown WebSphere MQ queue name <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- When opening the WebSphere MQ queues used by the Configuration Manager, the name supplied is not that of a queue known to WebSphere MQ queue manager.
- Response
- Check that the WebSphere MQ queue manager you specified has a definition for queue <insert_0>. Check that you are using the correct queue manager, as the mqsicreateconfigmgr command creates the required WebSphere MQ queues automatically. Note that WebSphere MQ queue names are case-sensitive. For more information on this error see the WebSphere MQ Application Programming Reference manual, code 2085.
- BIP1106
- WebSphere MQ error detected, reason code <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error has occurred while making a WebSphere MQ call from the Configuration Manager. The WebSphere MQ reason code is <insert_0>. The Configuration Manager will continue processing if it is possible to do so.
- Response
- For more information on this error see the WebSphere MQ Messages manual or WebSphere MQ Online Help, code <insert_0>.
- BIP1107
- Unexpected exception in Configuration Manager MQProcessor class <insert_1> method; exception text: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager MQProcessor class <insert_1> method. The exception text is: <insert_0>. The Configuration Manager will continue processing if it is safe to do so.
- Response
- Retry the operation if possible. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1109
- WebSphere MQ error writing to dead letter queue, reason code <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred while the Configuration Manager was putting a message on the dead letter queue. The WebSphere MQ reason code is <insert_0>. A previous message will indicate the reason why the message was put to the dead letter queue in the first place.
- Response
- For more information on this error see the WebSphere MQ Application Programming Reference manual, code <insert_0>.
- BIP1110
- Unrecognized WebSphere MQ message received by the Configuration Manager on input queue <insert_1>; reason code <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A message was received by the Configuration Manager on input queue <insert_1>, but the message could not be processed. The WebSphere MQ ReasonCode is <insert_0>. The message has been written to the WebSphere MQ dead letter queue.
- Response
- Look at the message on the dead-letter queue to establish which application sent the message and what is wrong with it. For more information on this error see the WebSphere MQ Application Programming Reference manual, code <insert_0>.
- BIP1111
- java.lang.OutOfMemoryError in Configuration Manager MQProcessor class <insert_0> method.
- Severity
- 20 : Error
- Explanation
- A java.lang.OutOfMemoryError was caught by the Configuration Manager MQProcessor class <insert_0> method. This means the Java Virtual Machine has exhausted its available memory heap.
- Response
- Stop the Configuration Manager using the mqsistop command. Increase the maximum size of the Java Virtual Machine memory heap using the mqsichangeconfigmgr command, specifying the -j option. Refer to the WebSphere Message Brokers online documentation for guidance. Then restart the Configuration Manager and retry the operation. Repeat if necessary until the error no longer occurs.
- BIP1112
- Unexpected exception in Configuration Manager RegistrationHandler class <insert_1> method; exception text: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager RegistrationHandler class <insert_1> method. The exception text is: <insert_0>. The Configuration Manager will continue processing if it is safe to do so.
- Response
- Retry the operation if possible. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1113
- The utility could not open file <insert_0> for writing trace output.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to open the file <insert_0> so that internal utility trace could be written there, but this was not successful.
- Response
- If the file already exists, ensure that it is not locked or in use by another application, and that the current user can write to it. If the file does not exist, ensure that the current user has the authority to write to the specified directory. Try specifying a different filename. If the problem persists, please contact your IBM support center.
- BIP1121
- Creates an execution group.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsicreateexecutiongroup (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b brokerName -e executionGroupName [-l] [-w timeoutValue] [-v traceFileName]
- Response
- Command Options:
'-n cfgParameterFileName' Configuration Manager connection parameters (.configmgr)
'-i ipAddress' IP address or host name of the Configuration Manager
'-p port' port number of the Configuration Manager
'-q qMgr' queue manager of the Configuration Manager
'-b brokerName' name of the broker on which to create the execution group
'-e executionGroupName' name of the new execution group
'-l' creates a 64-bit execution-group.
'-w timeoutValue' time to wait (in seconds) for the execution group to be created (default=60)
'-v traceFileName' send verbose internal trace to the specified file.
- BIP1122
- Deletes an execution group.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsideleteexecutiongroup (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b brokerName -e executionGroupName [-w timeoutValue] [-v traceFileName]
- Response
- Command Options:
'-n cfgParameterFileName' Configuration Manager connection parameters (.configmgr)
'-i ipAddress' IP address or host name of the Configuration Manager
'-p port' port number of the Configuration Manager
'-q qMgr' queue manager of the Configuration Manager
'-b brokerName' name of the broker on which the execution group resides
'-e executionGroupName' name of the execution group to delete
'-w timeoutValue' time to wait (in seconds) for the execution group to be deleted (default=60)
'-v traceFileName' send verbose internal trace to the specified file.
- BIP1123
- The execution group already exists.
- Severity
- 20 : Error
- Explanation
- The utility was asked to create execution group <insert_1> on broker <insert_0>, but it already exists.
- Response
- Check that the names of the execution group and broker are correct and reissue the command.
- BIP1124
- Creating execution group <insert_1> on broker <insert_0>...
- Severity
- 0 : Information
- BIP1125
- The execution group could not be created.
- Severity
- 20 : Error
- Explanation
- The utility was asked to create execution group <insert_1> on broker <insert_0>, but it was not completed successfully by the Configuration Manager. The Configuration Manager reported the following error(s): <insert_2>
- Response
- Determine the cause of the problem by reviewing the error messages. If the problem persists, contact your IBM support representative.
- BIP1126
- The execution group was created successfully.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager will ask the broker to initialize the execution group when a resource is deployed to it.
- BIP1127
- This command will implicitly remove all resource(s) deployed to the execution group: <insert_0>
- Severity
- 0 : Information
- BIP1128
- Deleting the execution group <insert_0> from the Configuration Manager's repository...
- Severity
- 0 : Information
- BIP1129
- The execution group could not be deleted.
- Severity
- 20 : Error
- Explanation
- The utility was asked to delete execution group <insert_1> on broker <insert_0>, but it was not completed successfully by the Configuration Manager. The Configuration Manager reported the following error(s): <insert_2>
- Response
- Determine the cause of the problem by reviewing the error messages. If the problem persists, contact your IBM support representative.
- BIP1130
- Deleting the execution group from the Configuration Manager's repository and from broker <insert_0>...
- Severity
- 0 : Information
- BIP1131
- The execution group was deleted successfully from the Configuration Manager's repository. It was not necessary to deploy these changes to broker <insert_0>.
- Severity
- 0 : Information
- Explanation
- The new configuration was not deployed because the execution group had never been initialized on the broker.
- BIP1132
- Access denied
- Severity
- 20 : Error
- Explanation
- You do not have the appropriate level of authority defined in the Configuration Manager's access control table in order to complete the specified operation. (<insert_0>)
- Response
- Consult your domain administrator.
- BIP1151
- Unprocessable request received by the Configuration Manager; server type <insert_1> invalid for resource type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A request was received by the Configuration Manager, but the URI identifies a target server type (<insert_1>) which is not valid for resource type <insert_0>.
- Response
- If the request did not originate from the Message Brokers Toolkit, correct the application issuing the request. Otherwise retry the operation from the Message Brokers Toolkit. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request, and contact your IBM support center.
- BIP1152
- Internal error in the Configuration Manager; resource type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A request was received by the Configuration Manager but an internal inconsistency has been detected within the Configuration manager code. The target resource type is <insert_0>.
- Response
- This is an internal error. Turn on Configuration Manager tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP1153
- Unprocessable request received by the Configuration Manager; URI is <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A request was received by the Configuration Manager, but the URI contains two items of metadata following the first '?'. A maximum of one item of metadata may be specified on a URI, and so a URI may only contain zero or one '?' characters. The URI in question is <insert_0>.
- Response
- If the request did not originate from the Message Brokers Toolkit, correct the application issuing the request. Otherwise retry the operation from the Message Brokers Toolkit. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request, and contact your IBM support center.
- BIP1154
- Unprocessable request received by the Configuration Manager; <insert_1> operation not permitted for resource type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A request was received by the Configuration Manager, but a <insert_1> operation is never permitted for target resource type <insert_0>.
- Response
- If the request did not originate from the Message Brokers Toolkit, correct the application issuing the request. Otherwise retry the operation from the Message Brokers Toolkit. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request, and contact your IBM support center.
- BIP1155
- Internal error in the Configuration Manager; resource type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A request was received by the Configuration Manager but the URI identifies a target resource type <insert_0> for which no corresponding RoleManager object type can be found.
- Response
- This is an internal error. Turn on Configuration Manager tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP1156
- Internal error within the Configuration Manager; server type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A request was received by the Configuration Manager but the URI identifies a target server type (<insert_0>) for which no corresponding RoleManager server type can be found.
- Response
- This is an internal error. Turn on Configuration Manager tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP1157
- The properties for the target resource cannot be located.
- Severity
- 30 : Severe error
- Explanation
- The resource has been located in the repository, but no associated properties XML can be found. This means no label and icon information is available for the resource.
- Response
- This is an internal error. Turn on Configuration Manager tracing to capture details of the exception. Retry the operation and contact your IBM support center.
- BIP1158
- Unprocessable request received by the Configuration Manager; resource type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A request was received by the Configuration Manager but the URI identifies target resource type <insert_0> for which the Configuration Manager is not configured.
- Response
- If the request did not originate from the Message Brokers Toolkit, correct the application issuing the request. Otherwise retry the operation from the Message Brokers Toolkit. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request, and contact your IBM support center.
- BIP1159
- Broker <insert_0> has a blank queue manager name.
- Severity
- 20 : Error
- Explanation
- An attempt was made to create or modify a broker with no associated WebSphere MQ queue manager name. This is a mandatory property. The broker name is <insert_0>.
- Response
- Provide a queue manager name for the broker and retry the operation. If the problem persists, contact your IBM support center.
- BIP1160
- Duplicate name <insert_1> for <insert_0> within configuration repository.
- Severity
- 20 : Error
- Explanation
- An error occurred when attempting to save <insert_0> <insert_1> to the configuration repository because another <insert_0> already exists with the same name.
- Response
- Rename the <insert_0> and retry the operation.
- BIP1161
- Unable to locate WebSphere MQ Java classes.
- Severity
- 30 : Severe error
- Explanation
- When connecting to the WebSphere MQ queue manager at Configuration Manager startup, the WebSphere MQ Java classes could not be located.
- Response
- Ensure that the required level of WebSphere MQ Java classes are installed and have been correctly added to the CLASSPATH. Different versions of WebSphere MQ Java classes require different entries in the CLASSPATH (in particular version 5.21 of MA88 requires connector.jar to be identified in the CLASSPATH). You should consult the documentation provided with your version of WebSphere MQ Java classes for information on what is required in the CLASSPATH for that version. You may need a restart of your machine in order that any alterations to the CLASSPATH are picked up by the Service Control Manager which is used in starting the Configuration Manager. Ensure that the userid under which the Configuration Manager is running has the correct authorities (on some platforms this means adding your user id to the mqm and Administrators groups). Ensure that WebSphere MQ classes for Java libraries (for example on Windows mqjbnd04.dll) are available via the PATH. Ensure that WebSphere MQ classes for Java jar files (for example com.ibm.mq.jar) are available via the CLASSPATH.
- BIP1162
- Unprocessable registration request received by the Configuration Manager.
- Severity
- 30 : Severe error
- Explanation
- A request was received by the Configuration Manager to register for updates to the resource <insert_0> , but an exception was thrown while processing this request (<insert_1>).
- Response
- Restart the connection to the Configuration Manager and retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request and contact your IBM support center.
- BIP1163
- Unprocessable request received by the Configuration Manager.
- Severity
- 30 : Severe error
- Explanation
- A serialized request was received by the Configuration Manager, but the message was not in a recognized object format. The request was serialized as a <insert_0>.
- Response
- Correct the application that issued the request so that it serializes using the correct object type and format. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request and contact your IBM support center.
- BIP1164
- Unprocessable request received by the Configuration Manager.
- Severity
- 30 : Severe error
- Explanation
- A serialized request was received by the Configuration Manager, but the message was malformed. The following exception was thrown: <insert_0>.
- Response
- Correct the application that issued the request so that it serializes using the correct format. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request and contact your IBM support center.
- BIP1165
- Unexpected exception creating or deleting security ACL Information in ConfigurationACLGroup class <insert_0> method; exception text: <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the ConfigurationACLGroup class <insert_0> method while the ACL security information was being created or deleted. The exception text is: <insert_1>.
- Response
- Retry the operation. If the exception still occurs, contact your IBM support center.
- BIP1170
- Failed to restore the repository for the Configuration Manager <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- At least one file in the Configuration Manager's repository could not be restored. The restore operation was rolled back and the Configuration Manager is in the state it was in before the restore command was issued.
- Response
- Check that the Configuration Manager is not running, and that the file specified is a valid Configuration Manager archive. Check that the current user has authority to read the archive and write to the directory described by the work path. If this problem persists contact your IBM support center.
- BIP1171
- Verifying the restored repository...
- Severity
- 0 : Information
- BIP1172
- The database is invalid (<insert_0>)
- Severity
- 30 : Severe error
- BIP1173
- The Configuration Manager could not initialize because a required service is not available.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager was unable to initialize because either the machine does not have a local IP address or an MD5 cryptography service is not available.
- Response
- Ensure that the machine has a local IP address and that cryptography services are enabled, then retry the operation. If the exception still occurs, contact your IBM support center.
- BIP1201
- Unknown or unsupported database of type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- While attempting to determine the type of database being used for the configuration repository, the database type <insert_0> was returned. This is an unknown or unsupported database.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1202
- Unexpected exception in the Configuration Manager DBManager class <insert_1> method; exception text: <insert_0>, <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager DBManager class <insert_1> method. The database operation did not complete successfully. The exception text is: <insert_0>, <insert_2>.
- Response
- The exception text may indicate that a Java class could not be found; check that the system CLASSPATH variable contains the correct classes. If the problem persists please contact your IBM support center.
- BIP1203
- Unknown database column type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- While attempting to construct the database tables for the configuration repository, a column type of <insert_0> was found. This is an unknown column type. The database tables have not been constructed successfully.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1204
- Unable to locate required <insert_0> <insert_1> in directory <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- While attempting to prime the database tables for the configuration repository, a file or directory was either not found or could not be read. This may be the result of an inconsistent installation. The database tables have not been primed successfully.
- Response
- Ensure that the file or directory exists in the WebSphere Message Brokers <insert_2> directory. Check that the permissions are such that the file or directory is readable. Retry the mqsicreateconfigmgr command. If this is still not successful, contact your IBM support center.
- BIP1205
- Unexpected exception accessing configuration repository; exception text: <insert_1>.
- Severity
- 20 : Error
- Explanation
- While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager. The database operation did not complete successfully. If this message was issued by the Configuration Manager, then it will continue if it is safe to do so. The exception text is: <insert_1>.
- Response
- If this problem persists contact your IBM support center.
- BIP1206
- Database not running; exception text: <insert_0>.
- Severity
- 20 : Error
- Explanation
- While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager. This was because the database is not up and running. The database operation did not complete successfully. If this message was issued by the Configuration Manager, then it will continue if it is safe to do so. The exception text is: <insert_0>.
- Response
- If this problem persists contact your IBM support center.
- BIP1207
- Database <insert_0> not found; exception text: <insert_1>.
- Severity
- 20 : Error
- Explanation
- While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager. This was because the database name <insert_0> is not recognized and the database cannot be found. The database operation did not complete successfully. The exception text is: <insert_1>.
- Response
- If this problem persists contact your IBM support center.
- BIP1208
- Database product name cannot be found: object <insert_0> is null.
- Severity
- 30 : Severe error
- Explanation
- A problem was encountered while attempting to get information from the configuration repository database manager. The <insert_0> object is null.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1209
- The userid and/or password are not authorized for connection to the configuration repository <insert_0>.
- Severity
- 20 : Error
- Explanation
- When starting or creating or deleting the Configuration Manager, the configuration repository database <insert_0> could not be opened because the userid and/or password is not authorized.
- Response
- This error is most probably a result of either incorrect userid and password being provided for the -u and -p options on the mqsicreateconfigmgr command, or the userid not having been assigned access rights to the configuration repository database by the database management system. First check that the access rights have been correctly configured. Then, if necessary, delete your Configuration Manager (using the mqsideleteconfigmgr command) and then re-create your Configuration Manager (using the mqsicreateconfigmgr command) with the correct options. To preserve your configuration data in the configuration repository and message repository, do not specify the -n and -m flags on the mqsideleteconfigmgr command.
- BIP1210
- Missing or blank configuration repository JDBC driver name.
- Severity
- 30 : Severe error
- Explanation
- The configuration repository JDBC driver name supplied to the Configuration Manager is either blank or is missing. This is a mandatory property of the Configuration Manager.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1211
- Missing or blank configuration repository JDBC connection name.
- Severity
- 30 : Severe error
- Explanation
- The configuration repository JDBC connection name supplied to the Configuration Manager is either blank or is missing. This is a mandatory property of the Configuration Manager.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1213
- User <insert_0> is not allowed to unlock resource locked by user <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An attempt has been made to unlock a resource in the configuration repository, but the principal supplied with the unlock request (<insert_0>) does not match the principal associated with the locked resource (<insert_1>).
- Response
- The resource was locked by a different user. You cannot unlock a resource for which you do not own the lock.
- BIP1214
- Cannot unlock resource with lock token <insert_0> as the resource is not locked.
- Severity
- 30 : Severe error
- Explanation
- An attempt has been made to unlock a resource in the configuration repository, but the lock token supplied with the unlock request (<insert_0>) does not exist in the configuration repository, implying that the resource is not locked.
- Response
- The resource has already been unlocked. You can not unlock a resource for which no lock exists.
- BIP1215
- Invalid configuration repository table name <insert_0> detected by Configuration Manager DBManager class <insert_1> method.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager DBManager class <insert_1> method has detected an unknown table name <insert_0> when processing a request against the configuration repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1216
- Can not update resource <insert_0> which is not locked.
- Severity
- 30 : Severe error
- Explanation
- An attempt has been made to update an existing resource <insert_0> in the configuration repository but the resource has not been locked.
- Response
- You must first lock a resource before you update it.
- BIP1217
- Referenced <insert_1> not found, (UUID <insert_0>).
- Severity
- 20 : Error
- Explanation
- A referenced <insert_1> has not been found in the configuration repository.
- Response
- It is possible the parent of the <insert_1> written to the repository but the <insert_1> itself has not. Alternatively, the referenced <insert_1> may have been deleted. If this problem persists contact your IBM support center.
- BIP1221
- Found invalid Configuration Manager Database for migration!
- Severity
- 20 : Error
- Explanation
- The Configuration Manager Database specified for migration did not contain a complete set of valid tables. A new empty internal respository has been created instead.
- Response
- It is possible the wrong database has been specified for migration. If this is the case, please delete and recreate the Configuration Manager specifying the correct database. If no migration is needed no further action is required.
- BIP1222
- Using internal Configuration respository
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager is connecting to its internal repository.
- Response
- No action.
- BIP1223
- Attempting to open and migrate DB2 database <insert_0>...
- Severity
- 0 : Information
- BIP1224
- Migrating from DB2 Database: <insert_0>
- Severity
- 0 : Information
- Explanation
- Migrating from DB2 Database <insert_0> to the Configuration internal repository.
- Response
- No action.
- BIP1225
- Database migration failed
- Severity
- 30 : Severe error
- Explanation
- Migration from DB2 Database <insert_0> to the Configuration internal repository failed.
- Response
- See previous messages for details. Contact your IBM support center if the problem persists.
- BIP1226
- Configuration data already migrated
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager internal repository indicates data migration has already taken place.
- Response
- No action.
- BIP1227
- Failed to find internal respository!
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager failed to find its internal repository. A new, empty one has been created. This is a non-destructive action.
- Response
- Stop the Configuration Manager and restore the repository from a previous backup. Contact your IBM support center if the problem persists.
- BIP1228
- The Configuration Manager repository has been successfully created.
- Severity
- 0 : Information
- BIP1229
- Failed to migrate table: <insert_1>
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager failed to read UUID <insert_0> from table <insert_1> while migrating configuration data.
- Response
- This is an internal error. Contact your IBM support center if the problem persists.
- BIP1230
- The Configuration Manager's repository is not available for use.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager was not able to gain exclusive access to its internal repository. Either another process already has exclusive access to the repository (for example, if another instance of the Configuration Manager is running), or the user ID under which the Configuration Manager was started does not have the required authority to access the repository.
- Response
- Ensure that the Configuration Manager is not already running, and that no other process is running that may have acquired exclusive access to the repository. Also, ensure that the Configuration Manager's user ID has the required authority to access the database; the user at least needs to be a member of the mqm and mqbrkrs groups, and on Windows the user also needs to be in the Administrators group.
- BIP1301
- Invalid call to Configuration Manager PrincipalsManager class <insert_0> method.
- Severity
- 30 : Severe error
- Explanation
- An invalid method call was made to the Configuration Manager PrincipalsManager class <insert_0> method.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1302
- Unexpected exception in Configuration Manager PrincipalsManager class makeTXDoc method; exception text: UnsupportedEncodingException, character set <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager PrincipalsManager class makeTXDoc method when constructing an XML document. The exception text is: UnsupportedEncodingException, character set <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1303
- Unexpected exception in Configuration Manager PrincipalsManager class <insert_0> method; exception text: <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager PrincipalsManager class <insert_0> method. The exception text is: <insert_1>.
- Response
- Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1304
- Error accessing User Name Server from Configuration Manager PrincipalsManager class <insert_0> method; exception text: <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager PrincipalsManager class <insert_0> method whilst getting information from the User Name Server UGRegistry client. The exception text is: <insert_1>.
- Response
- Check preceding log entries for related errors and retry the operation. If the exception still occurs, restart the Configuration Manager, then retry the operation again. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1305
- Invalid call to Configuration Manager PrincipalsManager class <insert_0> method; Section parameter value <insert_1> encountered.
- Severity
- 30 : Severe error
- Explanation
- An attempt was made by the Configuration Manager to call the PrincipalsManager class <insert_0> method using value <insert_1> for the Section parameter. Only a value of SHARED is supported.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1306
- Invalid call to Configuration Manager PrincipalsManager class <insert_0> method; Container parameter value <insert_1> encountered.
- Severity
- 30 : Severe error
- Explanation
- An attempt was made by the Configuration Manager to call the PrincipalsManager class <insert_0> method using value <insert_1> for the Container parameter. Only values of USER, GROUP and PUBLICGROUP are supported.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1350
- The current operation has timed out.
- Severity
- 20 : Error
- Explanation
- One or more requests have been sent to the Configuration Manager to process the current operation, but no reply has been received for the last request sent.
- Response
- Either your request has queued up behind a long-running request by another user, or the Configuration Manager has stopped. Check that it is up and running then retry the operation. Because the link to the Configuration Manager is via WebSphere MQ, it is important to note that the original operation may have fully completed, or have partly completed, even though no reply was received in the allotted time. The results of the retried operation should indicate this, and will determine subsequent actions.
- BIP1351
- WebSphere MQ queue manager <insert_0> unknown on host system <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- When connecting to the WebSphere MQ queue manager, the name supplied is not that of a queue manager known to WebSphere MQ on host system <insert_1>. The Message Brokers Toolkit is unable to communicate with the Configuration Manager.
- Response
- Check that the queue manager name entered in the Message Brokers Toolkit File->Connection dialog box has been correctly specified, and that a WebSphere MQ queue manager with the required name exists on the specified host system. Note that WebSphere MQ queue manager names are case-sensitive. For more information on this error see the WebSphere MQ Application Programming Reference manual, code 2058.
- BIP1352
- WebSphere MQ queue manager <insert_0> on host system <insert_1> not available.
- Severity
- 30 : Severe error
- Explanation
- When connecting to the WebSphere MQ queue manager, queue manager <insert_0> is not up and running and listening for input on host system <insert_1>. The Message Brokers Toolkit is unable to communicate with the Configuration Manager.
- Response
- Check that the queue manager name entered in the Message Brokers Toolkit File->Connection dialog box has been correctly specified. Start the WebSphere MQ queue manager if it is not running. Ensure that the WebSphere MQ listener is running and listening on the correct port, that only one listener is listening on that port. Ensure that WebSphere MQ server connection channel SYSTEM.BKR.CONFIG is defined to the queue manager. For more information on this error see the WebSphere MQ Application Programming Reference manual, codes 2059, 2161, 2162, and 2009.
- BIP1353
- WebSphere MQ queue manager <insert_0> no longer available.
- Severity
- 30 : Severe error
- Explanation
- The Message Brokers Toolkit's connection to WebSphere MQ queue manager <insert_0> has been lost. The Message Brokers Toolkit is unable to communicate with the Configuration Manager.
- Response
- Restart the WebSphere MQ queue manager and the WebSphere MQ listener. If necessary also restart the Configuration Manager. For more information on this error see the WebSphere MQ Application Programming Reference manual, codes 2009, 2161 and 2162.
- BIP1355
- Unknown WebSphere MQ queue name <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- When opening the WebSphere MQ queues used by the Message Brokers Toolkit, the name supplied is not that of a queue known to the WebSphere MQ queue manager. The Message Brokers Toolkit is unable to communicate with the Configuration Manager.
- Response
- Check that the queue manager name entered in the Message Brokers Toolkit File->Connection dialog box has been correctly specified. Also check that it is associated with the Configuration Manager, and that it has a definition for queue <insert_0>. Note that WebSphere MQ queue and queue manager names are case-sensitive. For more information on this error see the WebSphere MQ Application Programming Reference manual, code 2085.
- BIP1356
- WebSphere MQ error detected, reason code <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An error has occurred while making a WebSphere MQ call from the Message Brokers Toolkit. The WebSphere MQ reason code is <insert_0>.
- Response
- For more information on this error see the WebSphere MQ Application Programming Reference manual, code <insert_0>.
- BIP1357
- Unrecognized reply received from the Configuration Manager.
- Severity
- 20 : Error
- Explanation
- A request has been sent to the Configuration Manager to process the current operation, but the reply received back is not one recognized by the Message Brokers Toolkit.
- Response
- The most likely cause is that another WebSphere MQ application is erroneously processing messages on SYSTEM.BROKER.CONFIG.QUEUE. Check that the Configuration Manager is up and running and is the only WebSphere MQ application processing messages on the queue. If no other application can be identified and the problem persists, contact your IBM support center.
- BIP1358
- Unexpected exception in Message Brokers Toolkit <insert_1> class <insert_2> method; exception text: <insert_0>, <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the <insert_1> class <insert_2> method when the Message Brokers Toolkit was communicating with the Configuration Manager. The exception text is: <insert_0>, <insert_3>.
- Response
- Retry the operation. If the exception still occurs, restart the Message Brokers Toolkit, then retry the operation again. If the exception still occurs, turn on Message Brokers Toolkit tracing to capture details of the exception, and contact your IBM support center.
- BIP1359
- The connection to WebSphere MQ queue manager <insert_0> has been lost.
- Severity
- 30 : Severe error
- Explanation
- When communicating with WebSphere MQ, queue manager <insert_0> is no longer up and running and listening for input. The Message Brokers Toolkit is unable to communicate with the Configuration Manager.
- Response
- Restart the WebSphere MQ queue manager if it is not running. Ensure that the WebSphere MQ listener is running and listening on the correct port, that only one listener is listening on that port. For more information on this error see the WebSphere MQ Application Programming Reference manual, codes 2161, 2162, and 2009.
- BIP1360
- Configuration Manager is not at the required software level.
- Severity
- 20 : Error
- Explanation
- A request was sent to the Configuration Manager to process the current operation, but the reply received back indicates that the Configuration Manager is not at a sufficient level to recognize requests of that command level.
- Response
- The Message Brokers Toolkit or Config Manager Proxy application has been upgraded to the latest product level, but a similar upgrade has not been made to the Configuration Manager. This is an incompatible combination of software; either upgrade the Configuration Manager to the same level as the Message Brokers Toolkit and Config Manager Proxy, or connect to a different Configuration Manager.
- BIP1361
- Unable to locate WebSphere MQ Java classes.
- Severity
- 30 : Severe error
- Explanation
- When connecting to the WebSphere MQ queue manager at Configuration Manager startup, the WebSphere MQ Java classes could not be located. All Message Brokers Toolkit and Config Manager Proxy applications will be unable to communicate with the Configuration Manager.
- Response
- Ensure that the required level of WebSphere MQ Java classes are installed and have been correctly added to the classpath. You must also ensure that the userid under which you are running has permission to access the directory where the WebSphere MQ Java classes are installed (on some platforms this may mean adding your user id to the Administrators group).
- BIP1362
- Unable to locate WebSphere security exit class.
- Severity
- 30 : Severe error
- Explanation
- When a Message Brokers Toolkit or Config Manager Proxy application attempted to connect to the WebSphere queue manager, the WebSphere security exit class <insert_0> could not be located. The application is unable to communicate with the Configuration Manager with the desired level of security.
- Response
- Ensure that the WebSphere security exit class <insert_0> exists in the specified location, and that the current user has authority to load it.
- BIP1363
- A problem was encountered while configuring WebSphere MQ security exit class <insert_1>; exception text: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Message Brokers Toolkit or Config Manager Proxy application could not configure user-supplied class <insert_1> for use as a WebSphere MQ security exit. The exception text is: <insert_0>. The Message Brokers Toolkit is unable to communicate with the Configuration Manager with the desired level of security.
- Response
- Check that the CLASSPATH system environment variable contains the jar files for any classes that are used by the security exit. Ensure that the security exit implements the WebSphere MQ MQSecurityExit interface and is correctly coded. For a complete description of how to implement a WebSphere MQ security exit for the WebSphere MQ Java Client please refer to WebSphere MQ documentation.
- BIP1401
- Invalid call to Configuration Manager MRMManager class <insert_0> method.
- Severity
- 30 : Severe error
- Explanation
- An invalid method call was made to the Configuration Manager MRMManager class <insert_0> method.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1402
- Unexpected exception in Configuration Manager MRMManager class <insert_1> method; exception text: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager MRMManager class <insert_1> method. The exception text is: <insert_0>.
- Response
- Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1403
- Missing or blank message repository database name.
- Severity
- 30 : Severe error
- Explanation
- The message repository database name supplied to the Configuration Manager is either blank or missing. This is a mandatory property of the Configuration Manager. The most likely cause of this is manual editing of the registry entries created by the mqsicreateconfigmgr command.
- Response
- Delete the Configuration Manager using the mqsideleteconfigmgr command, without specifying the -n or -m options. Then recreate the Configuration Manager using the mqsicreateconfigmgr command, specifying the correct database name on the -m option. See the WebSphere Message Brokers online documentation for guidance. If the problem persists, contact your IBM support center.
- BIP1404
- Update or create message repository resource <insert_1> of type <insert_0> in server <insert_2> failed: empty hashtable.
- Severity
- 30 : Severe error
- Explanation
- An empty hashtable was supplied when updating or creating resource <insert_1> of type <insert_0> in server <insert_2> within the message repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1405
- Update or create message repository resource <insert_1> of type <insert_0> in server <insert_2> failed: no XML document.
- Severity
- 30 : Severe error
- Explanation
- No XML document was supplied when updating or creating resource <insert_1> of type <insert_0> in server <insert_2> within the message repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1406
- Unable to lock message repository resource <insert_1> of type <insert_0> in server <insert_2>: no ActiveLock object.
- Severity
- 30 : Severe error
- Explanation
- No ActiveLock object was supplied when writing resource <insert_1> of type <insert_0> in server <insert_2> within the message repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1407
- Update or create resource <insert_1> of type <insert_0> in server <insert_2> failed: empty hashtable.
- Severity
- 30 : Severe error
- Explanation
- An empty hashtable was supplied when updating or creating the properties for resource <insert_1> of type <insert_0> in server <insert_2> within the message repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1408
- Update or create resource <insert_1> of type <insert_0> in server <insert_2> failed: no XML document.
- Severity
- 30 : Severe error
- Explanation
- No XML document was supplied when updating or creating the properties for resource <insert_1> of type <insert_0> in server <insert_2> within the message repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1409
- Unable to unlock resource <insert_1> of type <insert_0> in server <insert_2>: no ActiveLock object.
- Severity
- 30 : Severe error
- Explanation
- No ActiveLock object was supplied when writing resource <insert_1> of type <insert_0> in server <insert_2> within the message repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1410
- Update or create resource <insert_1> of type <insert_0> in server <insert_2> failed: no ActiveLock object.
- Severity
- 30 : Severe error
- Explanation
- No ActiveLock object was supplied when updating or creating resource <insert_1> of type <insert_0> in server <insert_2> within the message repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1411
- Unable to save NNSY resource to the configuration database.
- Severity
- 30 : Severe error
- Explanation
- Changes to NNSY resources cannot be performed using the Message Brokers Toolkit.
- Response
- The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates to a NNSY resource, you will need to use the NNSY Formatter GUI instead.
- BIP1412
- Unable to save the properties for the NNSY resource to the configuration database.
- Severity
- 30 : Severe error
- Explanation
- Changes to NNSY resources cannot be performed using the Message Brokers Toolkit.
- Response
- The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates to a NNSY resource, you will need to use the NNSY Formatter GUI instead.
- BIP1413
- Unable to lock a NNSY resource.
- Severity
- 30 : Severe error
- Explanation
- Changes to NNSY resources cannot be performed using the Message Brokers Toolkit, and so it is not possible to put a lock on a NNSY resource.
- Response
- The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates to a NNSY resource, you will need to use the NNSY Formatter GUI instead.
- BIP1414
- Unable to unlock a NNSY resource.
- Severity
- 30 : Severe error
- Explanation
- Changes to NNSY resources cannot be performed using the Message Brokers Toolkit, and so it is not possible to release a lock on a NNSY resource.
- Response
- The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates to a NNSY resource, you will need to use the NNSY Formatter GUI instead.
- BIP1415
- Unable to delete a NNSY resource.
- Severity
- 30 : Severe error
- Explanation
- Changes to NNSY resources cannot be performed using the Message Brokers Toolkit, and so it is not possible to delete a NNSY resource.
- Response
- The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates to a NNSY resource, you will need to use the NNSY Formatter GUI instead.
- BIP1449
- Configuration Manager cannot locate one or more Java classes; exception text: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- There was an error establishing the correct Java environment for accessing the message repository.
- Response
- This normally indicates an inconsistent installation of the Configuration Manager. Check that Configuration Manager has been installed correctly and that no jar files have been deleted. If the problem persists contact your IBM support center.
- BIP1450
- Error loading library imbMRMInterface; error text: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager was unsuccessful when loading the imbMRMInterface library. Any error text follows: <insert_0>.
- Response
- This normally indicates an inconsistent installation of the Configuration Manager. Check that the Configuration Manager has been installed correctly and that PATH includes the directory containing the Configuration Manager libraries and executables. If the problem persists contact your IBM support center.
- BIP1461
- Invalid call to Configuration Manager CacheManager class <insert_0> method.
- Severity
- 30 : Severe error
- Explanation
- An invalid method call was made to the Configuration Manager CacheManager class <insert_0> method.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1462
- Unexpected exception in Configuration Manager CacheManager class <insert_1> method; exception text: <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager CacheManager class <insert_1> method. The exception text is: <insert_0>.
- Response
- Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1502
- Unexpected exception in Configuration Manager BrokerManager class <insert_0> method; exception text: <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager BrokerManager class <insert_0> method. The exception text is: <insert_1>. The current operation will terminate.
- Response
- Retry the operation if possible. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception and contact your IBM support center.
- BIP1503
- Unable to find required execution group document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When deploying configuration data, the document for execution group <insert_0> could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing deploy document is of type <insert_1>.
- Response
- The execution group document <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1504
- Unknown deploy type or action type <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager BrokerManager class received a request to perform the action <insert_0>. This action is not recognized.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1505
- Subscription can not be deleted.
- Severity
- 20 : Error
- Explanation
- An attempt was made to delete a subscription, but the subscription in question was created by a WebSphere Message Brokers component for its own internal use. Such subscriptions can not be deleted.
- Response
- Retry the operation on a different subscription.
- BIP1506
- Queue manager <insert_2> cannot be associated with broker <insert_0>; it may still be in use by another broker <insert_1> which is pending deletion.
- Severity
- 20 : Error
- Explanation
- Broker <insert_1> has been removed from the domain of active brokers, although it may still be using its queue manager. It is not possible to associate another broker with the queue manager until the Configuration Manager can confirm that the first broker has tidied up its resources.
- Response
- After successfully removing a broker from the domain, you must initiate a deploy of the topology in order to instruct the broker component to stop and tidy up its resources. This can be done using the Message Brokers Toolkit, mqsideploy utility or the Configuration Manager Proxy API. Once the deploy is successful, you must delete the broker component using the mqsideletebroker command. Only then can you associate a new broker with the queue manager.
If the runtime broker component has already been deleted and is therefore unable to cleanly tidy up its resources, you must purge any remaining references to the broker and its queue manager from the Configuration Manager's repository. To do this, either (a) make the queue manager or its SYSTEM.BROKER.ADMIN.QUEUE inaccessible to the Configuration Manager and initiate a topology deploy, or (b) use the Configuration Manager Proxy API TopologyProxy.removeDeletedBroker().
- BIP1507
- Cannot find root element <insert_0> in XML document.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager could not find a root element named <insert_0> in the XML document it was attempting to parse.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1508
- Unexpected root element <insert_0> in XML document: root element <insert_1> expected.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager found an unexpected root element named <insert_0> while parsing an XML document looking for root element <insert_1>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1509
- The deployment action was not required.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager was asked to initiate a deployment operation, but this was not performed because the deployed configuration has not changed.
- Response
- No user action required.
- BIP1510
- Deployment failed; a deployment is already in progress to broker <insert_0>
- Severity
- 20 : Error
- Explanation
- The Configuration Manager was asked to deploy to broker <insert_0>, but this could not be attempted because it has not yet received a response to a previous deployment request submitted to that broker. To ensure that the deployed configuration is consistent with the reported configuration, the more recent deployment request has been discarded.
Note that if you are attempting to deploy the publish/subscribe topology or topic hierarchy, no brokers in the domain will have received the new deployment message. There can be no outstanding deploys in the domain before deployment of such a configuration can occur.
- Response
- Wait for the outstanding deploy to complete before retrying the operation. The Event Log Editor or Configuration Manager Proxy may be used to check that all responses to the outstanding deploy have been received and processed. If the outstanding deploy does not fully complete in a suitable period of time, check that all brokers exist and are running, all WebSphere MQ queue managers are running, and that all channels between queue managers are started. Also check that deploy messages have been correctly delivered to the target brokers, and have not been put to the dead letter queue. Correct any problems you find. If it still does not complete, then cancel the deploy operation; either (a) right-click the broker in the Message Brokers Toolkit and select the 'Cancel Deployment' option, or (b) use mqsideploy with the -c option, or (c) use the BrokerProxy.cancelDeployment() method in a Configuration Manager Proxy application. Note that cancelling the deployment operation does not stop the deployment message from being processed by the broker; it simply forces the Configuration Manager to remove any outstanding deployment locks that may be associated with the broker. If a broker subsequently processes a deployment message that has been cancelled using this technique, the deployed configuration may become inconsistent with the reported configuration.
- BIP1511
- Queue manager <insert_2> cannot be associated with broker <insert_0>; it is already associated with broker <insert_1>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to associate broker <insert_0> with WebSphere MQ queue manager <insert_2>, but broker <insert_1> already has this association. A WebSphere MQ queue manager can only have one broker associated with it.
- Response
- Change the queue manager for one of the brokers. If this problem occurs after you have deleted broker <insert_1> then tried to recreate it, you must first initiate a deploy operation to automatically delete the configuration from the real broker. It is only after all types of configuration data (message flows, message sets, topology, topics) have been successfully deleted from the real broker that the broker document is finally deleted from the configuration repository. Until that time the queue manager can not be associated with another broker. Once this has been done, you must also physically delete and recreate the real broker using the mqsideletebroker and mqsicreatebroker commands.
- BIP1512
- No Topology document found.
- Severity
- 30 : Severe error
- Explanation
- When attempting to deploy configuration data, the Topology document could not be found in the configuration repository.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1513
- Unprocessable response received by Configuration Manager on input queue <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A message was received by the Configuration Manager on input queue <insert_0>, but the message was not a response to an outstanding broker request. This message has erroneously appeared on queue <insert_0>.
- Response
- The message has been written to the WebSphere MQ dead letter queue. Look at the message on the dead letter queue to establish which application sent the message. If the message was a reply from a broker to which a deploy was subsequently cancelled, then it can be safely ignored. Otherwise correct the application.
- BIP1514
- Unprocessable publication received by Configuration Manager on input queue <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A publication was received by the Configuration Manager on input queue <insert_0>, but the publication matches no topic to which the Configuration Manager has subscribed. The publication has been written to the WebSphere MQ dead letter queue.
- Response
- Look at the message on the dead letter queue to establish the application that created the subscription, and why it was published on the <insert_0> queue. Correct the application.
- BIP1515
- Unable to find deploying broker data: UUID of broker is <insert_0>
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager received a response message from a broker that matches an outstanding broker request, but can find no record in the configuration repository of the broker in question. The UUID of the broker is <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1516
- Unable to process XML document in message from broker <insert_1>: no <insert_0> element could be found.
- Severity
- 30 : Severe error
- Explanation
- While processing a message received from broker <insert_1>, the XML document it contained was found to be invalid. An element in the following list was expected but could not be found: <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1517
- Cannot find entry in section <insert_0> of configuration repository: UUID of entry <insert_1>; table <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- A configuration repository entry could not be found. The UUID of the entry is <insert_1>, the configuration repository table name is <insert_2> and section is <insert_0>. The configuration repository may be in an inconsistent state.
- Response
- This situation should not arise under normal circumstances. Retry the operation and if the problem persists contact your IBM support center.
- BIP1518
- Unexpected exception in Configuration Manager BrokerManager class purgeLogEntries method; exception text: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An exception was caught by the Configuration Manager BrokerManager class purgeLogEntries method. The CLOG table in the configuration repository was not cleared correctly. The exception text is: <insert_0>.
- Response
- This will not affect the operation of the Configuration Manager and you may continue to use it. However, this is an internal error and you should contact your IBM support center if the problem persists.
- BIP1519
- Invalid topic tree found deploying topics.
- Severity
- 20 : Error
- Explanation
- When deploying topic data, the document for topic <insert_0> could not be found in the configuration repository. The parent topic that references <insert_0> is <insert_1>.
- Response
- The topic document for <insert_0> has either been deleted or has not been saved to the Configuration Manager. Correct the problem and retry the deploy operation.
- BIP1520
- The Configuration Manager has initiated a deployment operation.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager received a request to deploy configuration data and has consequently asked the following brokers to change their configuration: <insert_0> <insert_1>
- Response
- The receipt of this message does not necessarily mean that deployment was successful; view the Event Log Editor in the Message Brokers Toolkit to check the outcome of the deployment. If you are deploying programmatically using the Config Manager Proxy, check the returned DeployResult object or LogProxy. There will be a separate set of log messages for each broker.
- BIP1521
- Start message flow operation successfully initiated for broker <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager has processed the start message flow request and initiated a start message flow operation for the target message flows.
- BIP1522
- Stop message flow operation successfully initiated for broker <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager has processed the stop message flow request and initiated a stop message flow operation for the target message flows.
- BIP1523
- Stop trace operation successfully initiated for broker <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager has processed the stop trace request and initiated a stop trace operation for the target resources.
- BIP1524
- Start trace operation successfully initiated for broker <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager has processed the start trace request and initiated a start trace operation for the target resources.
- BIP1525
- Delete subscription operation successfully initiated on broker <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager has processed the delete subscription request and initiated a delete operation for the target subscription.
- Response
- Consult the Event Log Editor in the Message Brokers Toolkit, or the LogProxy object in a Config Manager Proxy application, to check the outcome of the operation.
- BIP1526
- Operation not initiated.
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager attempted to process the request but no suitable resource was found.
- Response
- Check that the correct resources still exist. If the problem persists please contact your IBM support center.
- BIP1527
- Duplicate name <insert_1> deploying <insert_0> data.
- Severity
- 20 : Error
- Explanation
- When deploying <insert_0> data, two <insert_0>s with the same name were found in the configuration repository. The <insert_0> name is <insert_1>. Names must be unique.
- Response
- Rename one of the <insert_0>s with name <insert_1>, then retry the deploy operation.
- BIP1528
- java.lang.OutOfMemoryError in Configuration Manager BrokerManager class <insert_0> method.
- Severity
- 20 : Error
- Explanation
- A java.lang.OutOfMemoryError was caught by the Configuration Manager BrokerManager class <insert_0> method. This means the Java Virtual Machine has exhausted its available memory heap.
- Response
- Stop the Configuration Manager using the mqsistop command. Increase the maximum size of the Java Virtual Machine memory heap using the mqsichangeconfigmgr command, specifying the -j option. Refer to the WebSphere Message Brokers online documentation for guidance. Then restart the Configuration Manager and retry the operation. Repeat if necessary until the error no longer occurs.
- BIP1530
- Unable to process XML document for broker <insert_1>. Attribute <insert_0> not found for element <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- While processing a message received from broker <insert_1>, the XML document it contained was found to be invalid. An attribute named <insert_0> could not be found for element <insert_2>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1531
- Deploy configuration failed. Message set with UUID <insert_0> returned an empty hashtable.
- Severity
- 30 : Severe error
- Explanation
- When attempting to deploy configuration data, a request to the message repository to generate the message dictionary for a message set returned an empty hashtable. The UUID of the message set in question is <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1532
- Deploy configuration failed processing broker data: UUID of resource is <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An empty hash table was supplied when adding broker data to the 'DPLING' section of the configuration repository. The UUID of the resource in question is <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1533
- Unable to deploy configuration data: unknown WebSphere MQ queue manager <insert_1> associated with broker <insert_0>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to deploy configuration data to one or more brokers. The WebSphere MQ queue manager <insert_1> associated with broker <insert_0> is not known to the Configuration Manager's WebSphere MQ queue manager. The deploy operation was not performed.
- Response
- Check that the name of the queue manager is spelled correctly. Note that WebSphere MQ queue manager names are case-sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue manager <insert_1>, or a transmission queue called <insert_1>, is defined to the Configuration Manager's queue manager. For more information on this error see the WebSphere MQ Application Programming Reference manual, code <insert_2>.
- BIP1534
- Unable to perform requested operation for broker <insert_0>: broker does not exist on queue manager <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to perform an operation against resources on broker <insert_0>, but the broker does not exist on queue manager <insert_1>. The operation was not performed.
- Response
- This normally means that the broker has been prematurely deleted using the mqsideletebroker command. Delete the broker from the configuration using the Message Brokers Toolkit or Config Manager Proxy, then redeploy the topology to remove all traces of the broker from the configuration repository.
- BIP1535
- Operation not initiated: broker <insert_0> does not exist on queue manager <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to process the request, but broker <insert_0> does not exist on queue manager <insert_1>. The operation was not initiated.
- Response
- This normally means that the broker has been prematurely deleted using the mqsideletebroker command. Delete the broker from the configuration using the Message Brokers Toolkit or Config Manager Proxy, then redeploy the topology to remove all traces of the broker from the configuration repository.
- BIP1536
- The Configuration Manager was unable to register for internal subscriptions with broker <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker <insert_0> was not successful. This means that Message Brokers Toolkit and Config Manager Proxy applications may not show the correct status of the resources assigned to broker <insert_0>.
- Response
- Look in the system log for messages that indicate the cause of this problem. Correct the cause and redeploy to this broker. If this problem persists, contact your IBM support center.
- BIP1537
- Unable to remove configuration data from broker <insert_0>: broker no longer exists on queue manager <insert_1>.
- Severity
- 10 : Warning
- Explanation
- Broker <insert_0> was deleted using the Message Brokers Toolkit or Config Manager Proxy, and a deploy operation subsequently attempted to remove all configuration data. However the broker was found to no longer exist on queue manager <insert_1>.
- Response
- No action is required. This message normally means that the broker been deleted using the mqsideletebroker command.
- BIP1538
- Unable to deploy configuration data to broker <insert_0> on queue manager <insert_1>; WebSphere MQ reason code <insert_2>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to deploy configuration data to broker <insert_0> on queue manager <insert_1>, but WebSphere MQ could not deliver the deploy request to the broker. The WebSphere MQ ReasonCode is <insert_2>. No configuration data was deployed.
- Response
- For more information on this error refer to the WebSphere MQ Application Programming Reference manual, code <insert_2>. Correct the problem and retry the deploy operation.
- BIP1539
- Unable to deploy configuration data to broker <insert_0>: broker does not exist on queue manager <insert_1>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to deploy configuration data to broker <insert_0>, but WebSphere MQ could not deliver the deploy request to the broker. The broker was found not to exist on queue manager <insert_1>. No configuration data was deployed.
- Response
- Either the wrong WebSphere MQ queue manager has been specified for the broker, or the broker has not been created using the mqsicreatebroker command, or the broker has been prematurely deleted using the mqsideletebroker command. Note that WebSphere MQ queue manager names are case-sensitive. Depending on the cause, either correct the queue manager name and redeploy, or create the broker using the mqsicreatebroker command and redeploy. Alternatively, delete the broker from the Configuration Manager using the Message Brokers Toolkit or Config Manager Proxy, and redeploy to remove all traces of the broker from the configuration repository.
- BIP1540
- Broker <insert_0> has been removed from the configuration repository.
- Severity
- 0 : Information
- Explanation
- Broker <insert_0> was deleted using the Message Brokers Toolkit or a Configuration Manager Proxy application, and a deploy operation subsequently attempted to remove all configuration data. Either the deploy operation succeeded, or the broker was found to no longer exist on the target queue manager, as indicated by earlier messages. In either case, the Configuration Manager has removed all trace of the broker from the configuration repository.
- Response
- No user action required.
- BIP1541
- Unable to perform requested operation for broker <insert_0> on queue manager <insert_1>; WebSphere MQ reason code <insert_2>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to perform an operation against resources on broker <insert_0> on queue manager <insert_1>, but WebSphere MQ could not deliver the operation request to the broker. The WebSphere MQ ReasonCode is <insert_2>. No operation was performed.
- Response
- For more information on this error refer to the WebSphere MQ Application Programming Reference manual, code <insert_2>. Correct the problem and retry the operation.
- BIP1542
- Unable to deploy configuration data.
- Severity
- 20 : Error
- Explanation
- An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is busy processing another deploy request. Your deploy operation was not performed.
- Response
- This is a transient situation. Wait for the Configuration Manager to complete its processing then retry the operation.
- BIP1543
- Deploy of configuration data to broker <insert_0> not performed.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to perform a delta deploy of configuration data to broker <insert_0>, but no changes have been made to the configuration for broker <insert_0> since the last deploy. The deploy operation for broker <insert_0> was not performed.
- Response
- No user action required.
- BIP1544
- The NNSY Message Set cannot be deployed.
- Severity
- 20 : Error
- Explanation
- An attempt was made to deploy broker <insert_0>, but the broker has the NNSY Message Set assigned to it.
- Response
- The NNSY Message Set is provided to allow users to view NNSY Formatter message/format definitions within the Message Brokers Toolkit. It is not necessary to deploy this message set to a broker. You must unassign the NNSY Message Set from the broker, and retry the operation.
- BIP1545
- Unable to find required broker document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When deploying configuration data, the document for broker <insert_0> could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing deploy document is of type <insert_1>.
- Response
- The broker document <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1546
- Unable to find required broker document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When deploying configuration data, the document for broker <insert_0> could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing collective document is of type <insert_1>.
- Response
- The broker document <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1547
- Unable to find required mrm dictionary document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When deploying configuration data, the document for MRM dictionary <insert_0> could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing broker document is of type <insert_1>.
- Response
- The MRM dictionary document <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1548
- Unable to find required collective document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When deploying configuration data, the document for collective <insert_0> could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing Topology document is of type <insert_1>.
- Response
- The collective document <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1549
- Unable to find required execution group document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When deploying configuration data, the document for execution group <insert_0> could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing broker document is of type <insert_1>.
- Response
- The execution group document <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1550
- Unable to find required message flow document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When deploying configuration data, the document for message flow <insert_0> could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing execution group document is of type <insert_1>.
- Response
- The message flow document <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1551
- Unable to find required message set document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When deploying configuration data, the document for message set <insert_0> could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing broker document is of type <insert_1>.
- Response
- The message set document <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1552
- Deploy configuration failed processing execution group data: UUID of resource is <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An empty hash table was supplied when adding execution group data to the 'DPLING' section of the configuration repository. The UUID of the resource in question is <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1557
- Deploy configuration failed processing topic data: UUID of resource is <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An empty hash table was supplied when adding topic data to the 'DPLING' section of the configuration repository. The UUID of the resource in question is <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1558
- Deploy configuration failed processing neighbor data: UUID of resource is <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An empty hash table was supplied when adding neighbor data to the 'DPLING' section of the configuration repository. The UUID of the resource in question is <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1559
- Deploy configuration failed processing outstanding reply data: UUID of resource is <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An empty hash table was supplied when adding outstanding reply data to the 'DPLING' section of the configuration repository. The UUID of the resource in question is <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1560
- Deploy configuration failed processing data of an unknown type: UUID of resource is <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- An empty hash table was supplied when adding data of an unknown type to the 'DPLING' section of the configuration repository. The UUID of the resource in question is <insert_0>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1561
- Deploy of configuration data to execution group <insert_0> not performed.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to perform a delta deploy of configuration data to execution group <insert_0>, but no changes have been made to the configuration for execution group <insert_0> since the last deploy. The deploy operation for execution group <insert_0> was not performed.
- Response
- No user action required.
- BIP1562
- Deploy of configuration data bar file failed.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to perform a bar file deploy. An unexpected IOException exception <insert_0> occurred while parsing the bar file. The deploy operation was not performed.
- Response
- Correct the problem and retry the deploy operation.
- BIP1563
- Deploy of configuration data bar file failed.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to perform a bar file deploy. An unexpected SAXException exception <insert_0> occurred while parsing the bar file. The deploy operation was not performed.
- Response
- Correct the problem and retry the deploy operation.
- BIP1564
- Unable to serialize the parser tree.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to serialize the parser tree built from a bar file deploy. An unexpected IOException exception <insert_0> occurred in class <insert_1>. The deploy operation was not performed.
- Response
- Correct the problem and retry the deploy operation.
- BIP1565
- Deploy of configuration data bar file failed.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to perform a bar file deploy. An unexpected IOException exception <insert_0> occurred in class <insert_1> while uncompressing the bar file. The deploy operation was not performed.
- Response
- Investigate the problem and retry the deploy operation.
- BIP1566
- Deploy of configuration data bar file failed.
- Severity
- 10 : Warning
- Explanation
- An attempt was made to perform a bar file deploy. An unexpected exception <insert_0> occurred in class <insert_1> while extracting file <insert_2> from the bar file. The deploy operation was not performed.
- Response
- Investigate the problem and retry the deploy operation.
- BIP1567
- Delete subscription operation successful.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager detected the subscription has already been deleted or never existed.
- Response
- No user action required.
- BIP1568
- The Configuration Manager has cancelled deployment to broker <insert_0>.
- Severity
- 0 : Information
- Explanation
- A request to cancel deployment was issued against broker <insert_0>. This was completed successfully, and consequently the Configuration Manager has discarded any outstanding deployment records for that broker.
Furthermore, the Configuration Manager was able to remove the deployment message from the broker's input queue before it was processed.
It is now possible to send new deployment requests to that broker.
- Response
- No further action is required.
- BIP1569
- The Configuration Manager has removed any deployment lock associated with broker <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A request to cancel deployment was issued against broker <insert_0>. This was completed successfully, and consequently the Configuration Manager has discarded any outstanding deployment lock for that broker. It is now possible to send new deployment requests to that broker.
However, the Configuration Manager was unable to ensure that the original deployment message cannot be processed by the broker. If the broker has (or will) process this message and update its configuration as a result, the Configuration Manager will no longer be able to update its records to match and the broker will become out of sync with the Configuration Manager.
- Response
- If the broker is permanently unavailable, no further action is required.
If the broker may be only temporarily unavailable, you must take steps to remove the deployment message from the broker's input queue. Ensure that the broker is stopped and on the broker machine issue (for example) 'amqsget SYSTEM.BROKER.ADMIN.QUEUE [qmgr]' where [qmgr] is the name of the queue manager on which the broker is running.
If you suspect that the broker has already processed the deployment message that has been cancelled, you must redeploy the affected resources in order to resynchronize the Configuration Manager's records with the broker.
In order to prevent the situation reoccurring, ONLY cancel deployment when there is no possibility that the broker can ever process the submitted deployment request.
- BIP1570
- The Configuration Manager has removed all deployment locks.
- Severity
- 10 : Warning
- Explanation
- A request to cancel deployment was issued against all brokers in the domain. This was completed successfully, and consequently the Configuration Manager has discarded all outstanding deployment locks that currently exist. It is now possible to send new deployment requests to all brokers in the domain.
However, the Configuration Manager was unable to ensure that any outstanding deployment messages cannot be processed by the affected brokers. If these brokers have (or will) process these messages and update their configurations as a result, the Configuration Manager will not be able to update its records to match and the brokers will become out of sync with the Configuration Manager.
- Response
- If the brokers that had outstanding deploys are permanently unavailable, no further action is required.
If the brokers that had outstanding deploys may be only temporarily unavailable, you must take steps to remove the deployment messages from the brokers' input queues. Ensure that the brokers are stopped and on the broker machines issue (for example) 'amqsget SYSTEM.BROKER.ADMIN.QUEUE [qmgr]' where [qmgr] is the name of the queue manager on which each broker is running.
If you suspect that one or more brokers have already processed a deployment message that has been cancelled, you should redeploy the affected resources in order to resynchronize the Configuration Manager's records with the broker(s).
In order to prevent the situation reoccurring, ONLY cancel deployment when there is no possibility that a broker can ever process the submitted deployment request.
- BIP1571
- Unable to find a required broker document in the configuration repository.
- Severity
- 20 : Error
- Explanation
- When attempting to deploy a broker archive file, the broker with unique identifier (UUID) <insert_0> could not be found in the Configuration Manager's repository. Either a Configuration Manager Proxy application has recently modified the broker's UUID, or the Configuration Manager's repository has become corrupted. The deployment request was not completed successfully.
- Response
- If a Configuration Manager Proxy application has recently modified the UUID of the broker, discard all existing AdministeredObject handles to the broker or execution group, and reacquire them from the TopologyProxy before attempting to deploy. If the Configuration Manager repository has become corrupted, restore the repository from backups using the mqsirestoreconfigmgr command.
- BIP1702
- Unexpected exception in Configuration Manager RoleManager class <insert_1> method; exception text: <insert_0>, <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager RoleManager class <insert_1> method. The exception text is: <insert_0>, <insert_2>.
- Response
- Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1703
- Access rights for user <insert_0> cannot be validated: parameter <insert_1> has an unrecognized value (<insert_2>).
- Severity
- 30 : Severe error
- Explanation
- The <insert_1> parameter passed to the Configuration Manager RoleManager class validateUser method has an unrecognized value (<insert_2>).
- Response
- This is an internal error. Contact your IBM support center.
- BIP1705
- Access rights to the <insert_0> server not set up successfully by Configuration Manager RoleManager class <insert_1> method.
- Severity
- 30 : Severe error
- Explanation
- A problem was encountered by the Configuration Manager RoleManager class <insert_1> method while attempting to set up the access rights for the various groups.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1706
- The access rights for a user cannot be validated.
- Severity
- 30 : Severe error
- Explanation
- The user parameter passed to RoleManager.validateUser() method is null and, therefore, cannot be recognized.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1707
- Unknown user encountered within the Configuration Manager.
- Severity
- 20 : Error
- Explanation
- An unknown user exception was caught by the Configuration Manager RoleManager class when calling the UGRegistry class. The user has not been given access to the resource.
- Response
- Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1708
- Unexpected exception in the Configuration Manager RoleManager class <insert_0> method; exception text: <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager RoleManager class <insert_0> method when calling the UGRegistry class. The exception text is: <insert_1>.
- Response
- Look at previous error messages for the Configuration Manager in the event log. Determine and correct the cause of the problem before attempting the operation again. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1711
- The <insert_0> is not viewable by user <insert_2>
- Severity
- 10 : Warning
- Explanation
- An attempt was made to view or manipulate the <insert_0> with UUID <insert_1>, but the user who initiated this operation does not have the required authority to do so.
- Response
- Ask the domain's administrator to grant your user ID the necessary authority to perform the requested action.
- BIP1712
- <insert_0> not found
- Severity
- 10 : Warning
- Explanation
- An attempt was made to view or modify the <insert_0> with UUID <insert_1>, but it does not exist in the Configuration Manager's repository.
- Response
- If you are trying to manipulate an object immediately after submitting a request to create it, it is likely that there was a problem creating the object. An example of this is if you attempt to create a default execution group without first ensuring that the parent broker was created successfully; this error suggests that there was a problem creating the broker.
Check the Configuration Manager's logs to see why the <insert_0> could not be found. If the object has previously been available, the receipt of this error may indicate corruption in the Configuration Manager's repository; if this is the case, you may need to use mqsirestoreconfigmgr to restore the Configuration Manager's repository, or if this is not possible, contact your IBM support center for advice.
- BIP1751
- Unexpected error deploying the broker topology: record for broker <insert_1> (UUID=<insert_2>) with neighbor broker <insert_3> (UUID=<insert_4>) missing from CNEIGHBOURS table section <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- When deploying the broker topology, a record was found to be missing from the configuration repository CNEIGHBOURS table (<insert_0> section). The record in question was for broker <insert_1> (UUID=<insert_2>) with neighbor broker <insert_3> (UUID=<insert_4>).
- Response
- This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1752
- Unexpected error deploying configuration data: record for <insert_2> (UUID=<insert_3>) missing from table <insert_0>, section <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- When deploying configuration data, a record was found to be missing from the configuration repository <insert_0> table (<insert_1> section). The record in question was for <insert_2> (UUID=<insert_3>).
- Response
- This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1753
- Invalid XML document found when deploying; missing <insert_0> tag.
- Severity
- 30 : Severe error
- Explanation
- When deploying configuration data, an XML document for <insert_2> <insert_1> (UUID=<insert_3>) was retrieved from the configuration repository, but the XML document did not contain the expected <insert_0> tag as the document element.
- Response
- Identify the application that created the document. If this is not the Message Brokers Toolkit, correct the application. Otherwise this is an internal error; turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1754
- Invalid XML document for topic <insert_0> found when deploying topics.
- Severity
- 30 : Severe error
- Explanation
- When deploying topics data, an XML document for topic <insert_0> was retrieved from the configuration repository, but was found to be invalid. No UserRef or GroupRef element was found within one or more TopicPolicy elements.
- Response
- Identify the application that created the document. If this is not the Message Brokers Toolkit, correct the application. Otherwise this is an internal error; turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1755
- Invalid message flow type <insert_0> when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, the document for message flow type <insert_0> was retrieved from the configuration repository, but was found to be invalid for use as a top-level message flow type. It contains at least one Input Terminal or Output Terminal, which is not permitted. The cause is the direct assignment to an execution group of either one of the IBM primitive message flow types, or a user defined message flow type containing an Input Terminal or an Output Terminal.
- Response
- Make sure that the only message flow types you assign to an execution group are those that do not contain Input Terminals or Output Terminals. If <insert_0> is user defined, either remove any Input Terminals and Output Terminals, or create a new top-level message flow type that embeds <insert_0>. Then retry the deploy operation.
- BIP1756
- Invalid top-level message flow type <insert_0> when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, the document for message flow type <insert_0> was retrieved from the configuration repository, but was found to be invalid for use as a top-level message flow type. It does not contain a reference to at least one other message flow type. The cause is the deployment to an execution group of either one of the IBM primitive message flow types, or an empty user-defined message flow type.
- Response
- Make sure that the only message flow types you assign to an execution group are those that reference other message flow types. If <insert_0> is user-defined, modify the message flow type and retry the deploy operation.
- BIP1757
- Invalid run-time message flow type <insert_0> when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, an XML document for message flow type <insert_0>, (UUID=<insert_1>) was retrieved from the configuration repository, but was found to be invalid for use as a run-time message processing node. It contains element <insert_2> which is not a permitted element in a message flow type corresponding to a run-time message processing node.
- Response
- Establish the author of the message flow type. If the author is not IBM, contact the author to get the message flow type corrected. If the author is IBM, this is an internal error; turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1758
- Invalid message flow type found when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, an attempt was made by a message flow type to override the value of a nonexistent property of run-time message flow type <insert_1>. The property in question is <insert_0>. The message flow type in error is the one that embeds <insert_1>, and may be identified from label <insert_2>.
- Response
- This is probably caused by a message flow type that corresponds to a run-time node having been replaced by a later version with different property names. Update the message flow type in error to use the correct property name. However if the problem persists, turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1759
- Invalid XML document found when deploying; missing <insert_2> element.
- Severity
- 30 : Severe error
- Explanation
- When deploying configuration data, an XML document for <insert_5>, <insert_3>, (UUID=<insert_4>) was retrieved from the configuration repository, but was found to be invalid. The <insert_0> element, identified by label <insert_1>, did not contain an <insert_2> element.
- Response
- Identify the application that created the document. If this is not the Message Brokers Toolkit, correct the application. Otherwise this is an internal error; turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1760
- Invalid message flow type found when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When resolving the connections between nodes in a message flow, a connection was found that could not be resolved to Output Terminal <insert_0> in message flow type <insert_2>. The message flow type in error is the one that embeds <insert_2>, and may be identified from label <insert_1>.
- Response
- The most likely cause is that <insert_0> has been modified to remove Output Terminal <insert_0>, but the message flow type embedding <insert_2> was not modified to remove the connection to Output Terminal <insert_0>. Ensure that all message flow types in the message flow are consistent, and retry the deploy operation.
- BIP1762
- Invalid message flow type found when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When resolving the connections between nodes in a message flow, a connection was found that could not be resolved to Input Terminal <insert_0> in message flow type <insert_2>. The message flow type in error is the one that embeds <insert_2>, and may be identified from label <insert_1>.
- Response
- The most likely cause is that <insert_0> has been modified to remove Input Terminal <insert_0>, but the message flow type embedding <insert_2> was not modified to remove the connection to Input Terminal <insert_0>. Ensure that all message flow types in the message flow are consistent, and retry the deploy operation.
- BIP1764
- Invalid message flow <insert_0> when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, the document for message flow <insert_0> could not be found in the configuration repository.
- Response
- The message flow type document referenced by <insert_0> is not available. This is an internal error. Contact your IBM support center.
- BIP1765
- Unexpected error processing a broker message: record for <insert_2> (UUID=<insert_3>) missing from <insert_0> table, section <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- When processing a response message from a broker, a record was found to be missing from the configuration repository <insert_0> table, (<insert_1> section). The record in question was for <insert_2> (UUID=<insert_3>).
- Response
- This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1767
- Unexpected exception in Configuration Manager ResolveXML class <insert_0> method; exception text <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An exception was caught by the Configuration Manager ResolveXML class <insert_0> method. The exception text is: <insert_1>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP1768
- Invalid message flow type found when deploying message flows: badly formed <insert_0> attribute value.
- Severity
- 30 : Severe error
- Explanation
- When deploying message flow data and resolving the connections between nodes, a Connection element was found that had a badly formed <insert_0> attribute value. The 'UUID' and 'terminal name' components of the value should be separated by a '.' character but there was no such character present.
- Response
- This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1769
- Invalid message flow type <insert_0> deploying message flows; Input Terminal wired directly to Output Terminal.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, the document for message flow type <insert_0> was retrieved from the configuration repository, but was found to be invalid. It contains an Input Terminal and an Output Terminal connected together, which is not permitted.
- Response
- Remove the connection between the Input Terminal and the Output Terminal. Alternatively, if 'passthru' behavior is required, insert a Check node with all checks set to 'no', connect the Input Terminal to the Check node 'in' terminal, and connect the Check node 'match' terminal to the Output Terminal. Modify <insert_0> and retry the deploy operation.
- BIP1770
- Invalid XML document for <insert_2> <insert_1> (UUID=<insert_3>) when processing a broker message: missing <insert_0> tag.
- Severity
- 30 : Severe error
- Explanation
- When processing a response message received from a broker, an XML document for <insert_2> <insert_1> (UUID=<insert_3>) was retrieved by the Configuration Manager from the configuration repository, but the XML document did not contain the expected <insert_0> tag as the document element.
- Response
- This is an internal error; turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
- BIP1771
- Invalid run-time message flow type <insert_0> when deploying message flows; no InTerminal or OutTerminal.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, an XML document for message flow type <insert_0> (UUID=<insert_1>) was retrieved from the configuration repository, but was found to be invalid for use as a run-time message processing node. It does not contain an InTerminal or an OutTerminal.
- Response
- Establish the author of the message flow type. If the author is not IBM, contact the author to get the message flow type corrected. If the author is IBM, this is an internal error; turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1772
- Invalid run-time message flow type <insert_0> when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, an XML document for message flow type <insert_0>, (UUID=<insert_1>), was retrieved from the configuration repository, but was found to be invalid for use as a run-time message processing node. The value of the MessageProcessingNodeType element 'isPrimitive' attribute is not 'true'. Note that this error can occur if a user-defined message flow type is entirely empty or only contains InTerminals or OutTerminals.
- Response
- Establish the author of the message flow type. If the author is not IBM, contact the author to get the message flow type corrected. If the author is IBM, this is an internal error; turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support center.
- BIP1773
- Invalid recursive use of message flow type <insert_0> (label <insert_1>) when deploying message flows.
- Severity
- 20 : Error
- Explanation
- When deploying message flow data, message flow type <insert_0> was found to be used recursively. This is not permitted. The instance of this message flow type causing the problem is <insert_1>.
- Response
- Correct the message flow and retry the deploy operation.
- BIP1775
- Invalid AccessControlEntry permission <insert_0> for object type <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The Configuration Manager has been asked to create an Access Contol Entry with a permission of <insert_0> for an object of type <insert_1>. This permission is invalid for this type.
- Response
- Retry the command with a valid permission for the given object type.
- BIP1776
- Unexpected exception in the Configuration Manager ACLGroupEntry class <insert_1> method; exception text: <insert_0>, <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager ACLGroupEntry class <insert_1> method. The database operation did not complete successfully. The exception text is: <insert_0>, <insert_2>.
- Response
- The exception text may indicate that the DB2 JDBC Driver could be found; check that the system CLASSPATH variable contains access to the DB2 runtime classes. If the DB2 classes are present in the CLASSPATH or if the exception text indicates a different problem, please contact your IBM support center.
- BIP1777
- Possible database corruption found in the Configuration Manager database table <insert_0>
- Severity
- 30 : Severe error
- Explanation
- While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager ACLGroupEntry class <insert_1> method. Possible database corruption was encountered. The database operation did not complete successfully.
- Response
- The exception text may indicate that the DB2 JDBC Driver could be found; check that the system CLASSPATH variable contains access to the DB2 runtime classes. If the DB2 classes are present in the CLASSPATH or if the exception text indicates a different problem, please contact your IBM support center.
- BIP1778
- <insert_0> - <insert_1> - <insert_2> - <insert_3> - <insert_4>
- Severity
- 0 : Information
- BIP1779
- Unable to validate specified user or group <insert_0>.
- Severity
- 20 : Error
- Explanation
- An unknown user or group exception was caught while attempting this operation. The user or group <insert_0> has not been given access to the resource.
- Response
- Ensure that the user or group exists and is trusted by the calling domain or machine. Retry the operation. If the exception still occurs, contact your IBM support center.
- BIP1780
- Unable to validate specified user <insert_0>.
- Severity
- 20 : Error
- Explanation
- User <insert_0> does not have the required authority to complete the requested operation on the resource of type <insert_1> with UUID <insert_2>.
- Response
- Ensure that the user exists and has the necessary permissions to access the requested resource. Restart the Configuration Manager and retry the operation. If the exception still occurs, contact your IBM support center.