CWMLC
CWMLC messages are lifecycle messages.
They are divided as follows:
- Common [0001-0100]
- Lifecycle services [0101-0200]
- Lifecycle services startup [0201-0250]
- Lifecycle application install [0251-0300]
- Lifecycle client install [0451-0500]
- Lifecycle integration restart scan task [0626-0650]
- Monitor model integration [0651-0700]
- Monitor model integration recovery handling [0701-0750]
- Monitor model integration queue recovery shutdown [0751-0800]
- Monitor model integration general [0801-0850]
- Monitor model integration manager [0851-0900]
- Managed deployment manager [2000-2100]
- CWMLC0001E
Unable to access database. Cause: [0]. - CWMLC0002E
Unable to disconnect from database. Cause: [0]. - CWMLC0003E
Model [0] not found. - CWMLC0004E
Model [0] version [1] not found. - CWMLC0005E
Model [0] version [1] step [2] not found. - CWMLC0006E
Model [0] already exists. - CWMLC0007E
Model [0] version [1] already exists. - CWMLC0008E
Model [0] version [1] step [2] already exists. - CWMLC0009E
Unable to obtain LifecycleServices reference. - CWMLC0010E
Illegal argument [0]. - CWMLC0011W
Unable to remove CEI configuration for model [0] version [1]. Cause: [2]. - CWMLC0012E
Unexpected exception [0]. - CWMLC0013E
Unable to rollback database changes. Cause: [0]. - CWMLC0014E
The JSON import file is malformatted or is not valid. Detailed message: [0] - CWMLC0015E
The display name of this monitor model, [0], is already in use by model [1] version [2]. - CWMLC0016E
One or more parameters are not valid. Detailed message: [0] - CWMLC0101I
Stop request processed for model [0] version [1]. - CWMLC0102I
Event queue drained notification received for model [0] version [1]. - CWMLC0103I
Clear KPI cache completed. - CWMLC0104I
Model [0] version [1] KPI cache refresh interval set to [2]. - CWMLC0105E
AppManagement MBean instance not found. Cause: [0]. - CWMLC0106E
LifecycleServices MBean notification failed. Cause: [0]. - CWMLC0107E
Model [0] version [1] integration not valid. Cause: [2]. - CWMLC0108I
Task [0] enqueued for model [1] version [2]. Delay: [3]. Retry: [4]. - CWMLC0109I
Task [0] started. - CWMLC0110I
Task [0] enqueued. - CWMLC0111I
Model [0] version [1] step [2] completed. - CWMLC0112E
Model [0] version [1] step [2] not allowed. Reason: [3]. - CWMLC0113E
Model [0] version [1] step [2] failed. Cause: [3]. - CWMLC0114W
Administrative security must be enabled before connecting to a secure remote application server. - CWMLC0115E
Unable to establish secure CEI server connection when administrative security is not enabled. - CWMLC0116W
Unable to remove Alphablox cubes for model [0] version [1] during purge. Cause: [2]. - CWMLC0117W
Unable to drop schema for model [0] version [1] during purge. Cause: [2]. - CWMLC0118W
Unable to remove Alphablox cubes (union cubes) for model [0] during purge. Cause: [1]. - CWMLC0119W
Unable to drop schema (union views) for model [0] during purge. Cause: [1]. - CWMLC0120W
Model [0] version [1] must be restarted for changes to take effect. - CWMLC0121I
[0] provisional repository record(s) deleted. - CWMLC0122I
Model [0] version [1] repository record updated. - CWMLC0123I
[0] repository record(s) updated. - CWMLC0124I
Model [0] version [1] Alphablox cubes start completed. - CWMLC0125I
Model [0] version [1] Alphablox cubes stop completed. - CWMLC0126I
Model [0] version [1] start completed. - CWMLC0127I
Model [0] version [1] stop completed. - CWMLC0128E
Model [0] version [1] Alphablox cubes start not allowed. Reason: [2]. - CWMLC0129E
Model [0] version [1] start failed. Cause: [2]. - CWMLC0130E
Model [0] version [1] Alphablox cubes start failed. Cause: [2]. - CWMLC0131E
Model [0] version [1] Alphablox cubes stop not allowed. Reason: [2]. - CWMLC0132E
Model [0] version [1] start not allowed. - CWMLC0133E
Model [0] version [1] stop not allowed. - CWMLC0134E
Model [0] version [1] stop failed. Cause: [2]. - CWMLC0135E
Model [0] version [1] Alphablox cubes stop failed. Cause: [2]. - CWMLC0136W
Model [0] version [1] REST install notification failed. Cause: [2]. - CWMLC0137W
Model [0] REST uninstall notification failed. Cause: [1]. - CWMLC0139I
Creating work queues. - CWMLC0140I
Work queues created. - CWMLC0141E
Unable to create work queues with work manager [0]. Cause: [1]. - CWMLC0142W
Model [0] version [1] scheduler install notification failed. Cause: [2]. - CWMLC0143W
Model [0] version [1] scheduler uninstall notification failed. Cause: [2]. - CWMLC0144I
0 = 1 - CWMLC0157E
Work queue unavailable. - CWMLC0160E
Cannot connect to the remote Alphablox server with host name [0], RMI port [1] and user name [2] for model [3] version [4]. Verify that the Alphablox server is running. If the Alphablox server is in a cluster, use the host name and RMI port for one of the cluster members. Otherwise use the host name and RMI port for the standalone server. - CWMLC0161E
AlphabloxConfig MBean instance not found. Cause: [0]. - CWMLC0162E
Unable to establish secure Alphablox server connection when administrative security is not enabled. - CWMLC0163W
Model [0] version [1] cannot be started because the database schema has not been created. - CWMLC0164W
Model [0] version [1] cannot be started because the CEI configuration has not been completed. - CWMLC0165W
Model [0] version [1] cannot be started because the current state is not Active. - CWMLC0166E
Cannot connect to the remote CEI server with host name [0], RMI port [1], and user name [2] for model [3] version [4]. Verify that the CEI server is running. If the CEI server is in a different network deployment cell, use the host name and RMI port for the deployment manager. Otherwise, use the host name and RMI port for the standalone server. - CWMLC0167I
To complete the CEI configuration, use the Monitor Models Change CEI Configuration page and the Change CEI Distribution Mode page in the administrative console, or use the configureCEIDistribution() MBean method. - CWMLC0168I
To create the Alphablox cubes, use the Monitor Models Manage Alphablox Cubes page in the administrative console or use the createAlphabloxCubes() MBean method. - CWMLC0169I
Verify that the CEI server is running. Verify that the CEI server supports the target distribution mode. - CWMLC0170I
Model [0] version [1] step [2] set to "not complete". - CWMLC0171W
Unable to reload the CEI configuration for model [0] version [1]. Cause: [2]. - CWMLC0172W
Unable to unregister WPS transfer targets for model [0] version [1]. Cause: [2]. - CWMLC0173W
Unable to remove Cognos cubes for model [0] version [1] during purge. Cause: [2]. - CWMLC0174W
Unable to remove Cognos cubes for model [0] during purge. Cause: [1]. - CWMLC0175E
Model [0] version [1] step [2] not allowed for state [3]. Reason: [4]. - CWMLC0201I
LifecycleServices initialization processing terminated. Reason: [0]. - CWMLC0202I
LifecycleServices initialization processing completed. - CWMLC0203I
LifecycleServices startup processing completed. - CWMLC0204I
LifecycleServices stop processing completed. - CWMLC0205I
LifecycleServices destroy processing completed. - CWMLC0206E
LifecycleServices startup processing failed. - CWMLC0207I
[0] MBean activated. - CWMLC0208I
[0] MBean deactivated. - CWMLC0209E
Unable to activate [0] MBean. - CWMLC0210E
Unable to deactivate [0] MBean. - CWMLC0251I
Model [0] version [1] installation started. - CWMLC0252E
Model [0] version [1] could not be installed. Cause: [2]. - CWMLC0253I
Model [0] version [1] registration complete. - CWMLC0254E
Model [0] version [1] registration failed. Cause: [2]. - CWMLC0255I
[0] extracted from Monitor EAR file. - CWMLC0256I
Model [0] CEI server configuration updated. - CWMLC0257W
Model [0] CEI server configuration ignored. Reason: [1]. - CWMLC0258I
Model [0] version [1] Alphablox server configuration updated. - CWMLC0259W
Model [0] version [1] Alphablox server configuration ignored. Reason: [2]. - CWMLC0260E
Monitor SIBus [0] not defined. - CWMLC0261E
Model [0] version [1] registration failed -- multiple versions not supported on development server. - CWMLC0262W
Model [0] cannot have multiple versions on this server due to publishing settings. - CWMLC0263E
Unable to access application [0] monResources.xml from Monitor EAR file. - CWMLC0264E
Monitor EAR file installation/uninstallation not supported with wsadmin -conntype NONE. - CWMLC0265E
Monitor EAR file installation/uninstallation requires Monitor enabled profile. - CWMLC0266W
Model [0] version [1] processing strategy forced to 6.0.2 emulation due to event queue recovery. - CWMLC0267W
Model [0] version [1] CEI distribution mode forced to inactive due to event queue recovery and reason [2]. - CWMLC0268W
Model [0] version [1] added to the root resource group and may not be visible by its intended dashboard users -- use the Monitor data security panel to assign permission. - CWMLC0269E
Model [0] version [1] registration failed -- database schema [2] already in use by model [3]. - CWMLC0270E
Model [0] version [1] registration failed -- Monitor EAR file generator version [2] used and [3] or later required. - CWMLC0271E
Monitor EAR file installation requires that the data services scheduler be deployed and running. - CWMLC0272E
Model [0] version [1] in the Monitor EAR file does not match model [2] version [3] for the installed application [4]. Install a new version of the model instead of updating the installed application. - CWMLC0273E
Model [0] has an inconsistent state in the Monitor database. The integration state was 1, but it will be reset to 2. The flow was: 3 - CWMLC0274E
An error occurred while trying to determine the state of an MM. This will be retried shortly. The condition was caused by: 0. - CWMLC0275E
An error occurred while changing the distribution state of an MM [0]. This will be retried shortly. The condition was caused by: 2. The flow was: 1 - CWMLC0276I
Lifecycle was able to reestablish the status of the MMs. - CWMLC0451E
The response to the Create schema question must be Yes or No. "0" is not valid. - CWMLC0452E
The response to the Enable DMS question must be Yes or No. "0" is not valid. - CWMLC0453E
The response to the CEI server location question must be Local or Remote. "0" is not valid. - CWMLC0454E
The response to the CEI security question must be Enabled or Disabled. "0" is not valid. - CWMLC0455E
The response to the CEI distribution mode question must be Active, ActiveBypass, ActiveScalable or Inactive. "0" is not valid. - CWMLC0456E
The CEI server location is remote, so hostname and RMI port are required. - CWMLC0457E
The CEI server security is enabled, so user ID and password are required. - CWMLC0458E
The CEI server location is remote, so Event group profile list name and a scope of cell, node, server or cluster are required. - CWMLC0459E
For Event group profile list name and the scope (cell, node, server or cluster), either both must be specified or both must be blank. - CWMLC0460E
For server scope "0", cell and node are required. - CWMLC0461E
For node scope "0", cell is required. - CWMLC0462E
For cluster scope "0", cell is required. - CWMLC0463I
The Monitor EAR file contains no DMS scripts. - CWMLC0464E
The response to the Delete schema question must be Yes or No. "0" is not valid. - CWMLC0465E
The response to the Create Alphablox cubes question must be Yes or No. "0" is not valid. - CWMLC0466E
The response to the Alphablox server location question must be Local or Remote. "0" is not valid. - CWMLC0467E
The response to the Alphablox security question must be Enabled or Disabled. "0" is not valid. - CWMLC0468E
The Alphablox server location is remote, so hostname and RMI port are required. - CWMLC0469E
The Alphablox server security is enabled, so user ID and password are required. - CWMLC0470E
The CEI server location is remote, so RMI port number "0" must be an integer greater than zero. - CWMLC0471E
The Alphablox server location is remote, so RMI port number "0" must be an integer greater than zero. - CWMLC0472E
The response to the Processing strategy question must be SerialST, SerialMT or ParallelMT. "0" is not valid. - CWMLC0473E
The response to the Event reordering question must be Yes or No. "0" is not valid. - CWMLC0474E
The response to the KPI merge question must be Yes or No. "0" is not valid. - CWMLC0475E
The Processing strategy is SerialST, so Enable event reordering must be No. - CWMLC0476E
The Monitor model does not support multithreading, so Processing strategy must be SerialST. - CWMLC0477E
The Monitor model does not support event reordering, so Enable event reordering must be No. - CWMLC0482E
The response to the Start Alphablox cubes question must be Yes or No. "0" is not valid. - CWMLC0483E
The response to the Business Situations merge question must be Yes or No. "0" is not valid. - CWMLC0484E
The response to the processing mode question must be "sync" or "async". "0" is not valid. - CWMLC0485E
"0" is not a valid event source ID. - CWMLC0486E
The following exception occurred while confirming that event source "0" exists : 1 - CWMLC0487E
The selected event consumption mode "0" is not valid. - CWMLC0488E
This model version only supports CEI. - CWMLC0489E
This model must have at least one event source association when event consumption mode is set to "CreateNewInstances". - CWMLC0490E
Errors were discovered in one or more of the event sources assigned to this model. The model can not be deployed in an active state with invalid event sources. - CWMLC0551I
Model [0] version [1] cube [2] created. - CWMLC0552I
Model [0] version [1] cube [2] deleted. - CWMLC0553E
Model [0] version [1] cube [2] create failed. Cause: [3]. - CWMLC0554E
Model [0] version [1] cube [2] start failed. Cause: [3]. - CWMLC0555E
Model [0] version [1] cube [2] delete failed. Cause: [3]. - CWMLC0556E
Model [0] version [1] cube [2] stop failed. Cause: [3]. - CWMLC0557I
Model [0] version [1] cube [2] started. - CWMLC0558I
Model [0] version [1] cube [2] stopped. - CWMLC0626I
An interrupted model integration has been found. The integration sequence will be restarted. modelID: ''0'' - CWMLC0627E
Runtime exception has occurred. The repository database scan cannot continue. An attempt to restart the repository scan will be made after a delay of 0 1 - CWMLC0628E
Runtime exception has occurred. The repository database scan cannot continue. 0 - CWMLC0651E
Runtime exception has occurred. Integration work flow will stop. An attempt to restart the work flow will be made after a delay of: 0 modelID: ''1'' 2 - CWMLC0652E
Runtime exception has occurred. Integration work flow will stop. modelID: ''0'' 1 - CWMLC0701I
CEI Server RE-BOOT REQUIRED. Integration work-flow will pause until CEI server reboot signal is received. modelID: ''0'' - CWMLC0702I
***** ''RECOVERY HANDLING'' integration sequence is COMPLETE. modelID: ''0'' - CWMLC0703E
Runtime exception has occurred while trying to restart the ''RECOVERY HANDLING'' integration for modelID: ''0'' 1 - CWMLC0704I
CEI Server AUTOMATICALLY RE-BOOTED. Integration work-flow will continue. modelID: ''0'' - CWMLC0751I
***** ''QUEUE RECOVERY SHUTDOWN'' integration sequence is COMPLETE. modelID: ''0'' - CWMLC0752E
Runtime exception has occurred while trying to restart the integration for modelID: ''0'' 1 - CWMLC0753E
Another attempt to restart the integration will be tried after the following delay period: 0 modelID: ''1'' 2 - CWMLC0801I
CEI Server RE-BOOT REQUIRED. Integration work-flow will pause until CEI server reboot signal is received. modelID: ''0'' - CWMLC0802E
Runtime exception has occurred while trying to restart modelID: ''0'' 1 - CWMLC0803I
CEI Server AUTOMATICALLY RE-BOOTED. Integration work-flow will continue. modelID: ''0'' - CWMLC0804I
***** ''GENERAL'' integration sequence is COMPLETE. modelID: ''0'' - CWMLC0851W
Runtime exception has occurred. The ''CEI Server Rebooted'' event cannot be processed at this time. It must be submitted again at a later time. modelID: ''0'' 1 - CWMLC0852E
Runtime exception has occurred. The ''Queue Drained'' event could not be delivered. modelID: ''0'' versionDate: 1 2 - CWMLC0853I
A ''GENERAL'' integration RESTART request is being enqueued onto the lifecycle batch queue. modelID: ''0'' - CWMLC0854I
A ''QUEUE_RECOVERY_SHUTDOWN'' integration RESTART request is being enqueued onto lifecycle batch queue. modelID: ''0'' - CWMLC0855I
A ''RECOVERY_HANDLING'' integration RESTART request is being enqueued onto lifecycle batch queue. modelID: ''0'' - CWMLC0856W
OM integration type is not supported. It was not determined to be of type ''0'', ''1'' or ''2''. The integration RESTART request is being discarded. modelID: ''3'' - CWMLC0857I
Model [0] version [1] event queue recovery for version [2] completed. - CWMLC0858I
Model [0] version [1] event queue recovery for version [2] completed with warnings. Cause: [3]. - CWMLC0859E
The resource group could not be created because it already exists. - CWMLC0861E
The response to the Profile Migration question must be Yes or No. "0" is not valid. - CWMLC0862E
The response to the Process Center Server question must be Yes or No. "0" is not valid. - CWMLC0863E
The response to the MC Instance Migration question must be Yes or No. "0" is not valid. - CWMLC0864E
The response to the Generate Dashboard question must be Yes or No. "0" is not valid. - CWMLC0865E
The response to the Dashboard User question must be entered. - CWMLC0866E
The response to the Dashboard Name question must be entered. - CWMLC0867E
The Dashboard name must not contain a @, \, /, *, ?, ", <, >, or |. - CWMLC2001E
The resource for the model [0] is currently locked. - CWMLC2002E
The EAR file for the model [0] failed to build. - CWMLC2003I
The EAR file [0] was built successfully. - CWMLC2004I
The EAR file for model [0] has started building. - CWMLC2005E
Error reported while building model [0] : 1 - CWMLC2006W
Warning reported while building model [0] : 1 - CWMLC2007I
Information message reported while building model [0] : 1 - CWMLC2008W
Unable to remove unneeded directory or file : 0 - CWMLC2009E
Error reported while undeploying model [0] : 1 - CWMLC2010E
Error reported while cleaning up model [0] : 1 - CWMLC3000E
The 0 host cannot be reached. - CWMLC3001E
The 0 host cannot be resolved. - CWMLC3002E
The SOAP connection to 0 was not successful. Caused by : 1 - CWMLC3003E
The MBean for the Dynamic Event Framework cannot be found on 0. - CWMLC3004E
A CEI configuration was not found on remote host 0 at scope location 1. - CWMLC3005E
The following product installations cannot be found on 0 in node 1: 2: - CWMLC3006E
The 0 data source cannot be found on 1. - CWMLC3007E
The 0 validation step failed because of 1. - CWMLC3008I
The required BundleDetection MBean is not active on 0 in node 1. Checking the metadata to confirm that the event source is valid for the local Business Monitor server... - CWMLC3009W
The 0 application metadata cannot be modified. - CWMLC3010W
The required 0 resource bundle on 1 is not active because it is in the following state: 2 - CWMLC3011E
An SSL connection to 0 cannot be established. - CWMLC3012W
The JDBC data source on 0 with a JNDI name of ''1'' contains a 2 parameter value ''3'' that does not match the value ''4'' found in the local JDBC data source with a JNDI name of ''5''.
Parent topic: Messages