IBM BPM, V8.0.1, All platforms > Reference > Business Process Management messages > Business Monitor messages

CWMDS

CWMDS messages are data services messages.

They are divided as follows:

• Persistence messages [1000–1999]

• Repository messages [2000–2100]
• Generation [2500–3999]

• Data movement service messages [5000–5999]
• REST services messages [6000–6349]
• Fine-grained security messages [6350-6399]
• REST services security messages [6551–6600]
• Fine-grained security framework messages [6500–6699]
• Fine-grained security import/export messages [7000–7100]
• Fine-grained security messages [7700–7800]

• CWMDS1002E
  The size of one or more parameters passed exceeded the column size in the database tables 0
• CWMDS1003E
  A SQL Exception occurred 0
• CWMDS1004E
  An IllegalStateException occurred 0
• CWMDS2000E
  The following exception occurred while parsing the model mm file: 0
• CWMDS2001E
  The following model ids of two model versions are inconsistent 0 and 1.
• CWMDS2002W
  The MC '' 0'' has a different parent in the new version. Will not migrate instance data for this MC and all of its child MCs.
• CWMDS2003E
  The MC table '' 0'' under schema '' 1'' can not be queried. SQL exception occurred.
• CWMDS2004E
  The MC table '' 0'' under schema '' 1'' can not be processed completely due to database access error. Some data may have been successfully moved, but the rest of the instance records will not be attempted.
• CWMDS2005E
  Exception occurred during instance batch transfer (starting MCIID: '' 0'', source table: '' 1''). The transaction will be rolled back.
• CWMDS2006W
  The MC '' 0'' no longer exists in the new version. Will not migrate instance data for this MC and all of its child MCs.
• CWMDS2007W
  The child MC '' 0'' will not be processed for queue recovery because its parent MC '' 1'' is not processed.
• CWMDS2008E
  The XPath expression '' 0'' of the metric default value can not be evaluated successfully. The column will be set to null.
• CWMDS2009E
  The XPath expression '' 0'' of the metric default value can not be evaluated successfully. The column does not allow null value. Need to roll back the whole database transaction. Already migrated data within this transaction will be rolled back.
• CWMDS2010I
  The migration of instances (starting number '' 0'') from MC table '' 1'' has started.
• CWMDS2011I
  The migration of instances (starting number '' 0'') from MC table '' 1'' and all of the descendant instances has started.
• CWMDS2012I
  The migration of instances (starting number '' 0'') from MC table '' 1'' has completed.
• CWMDS2013I
  The migration of instances (starting number '' 0'') from MC table '' 1'' and all of its descendant instances has completed.
• CWMDS2014I
  Batch instance move is completed without any error or warning. The number of successfully moved top-level instance records is 0.
• CWMDS2015E
  Batch instance move encountered severe errors/exceptions and can not complete the migration. 0 top-level instances were successfully migrated and 1 top-level instances failed to be migrated - this number may not reflect all failed instances if any MC table in the old version could not be read. The first error/warning message is as follows: 2 See server logs for additional details.
• CWMDS2016W
  Failed to get the status of data movement service for model 0 and version 1. Therefore, DMS can not be suspended if it is running for this model version. This could result in unpredictable results when deleting migrated instance records from DMS target tables in the old version.
• CWMDS2017E
  Can not find instance 0 in table 1. This instance and all of its desendant instances will not be processed.
• CWMDS2018E
  EnableDashboards one or more of the ids/displaynames was found to exceed the maximum length limit.
• CWMDS2019E
  EnableDashboards a TOMSQLException occurred: 0
• CWMDS2020E
  EnableDashboards A SQLException occurred: 0
• CWMDS2021W
  Batch instance move completed with warning(s). 0 top-level instances were successfully migrated. The first warning message is as follows: 1. See server logs for additional details.
• CWMDS2022E
  Failed to resume data movement service for model 0 and version 1. Resume it from the administrative console.
• CWMDS2023E
  EnableDashboards A MetricDataType was found to be invalid: 0
• CWMDS2024E
  EnableDashboards A model with the same modelID and version timestamp already exists in the database. EnableDashboards stopping.
• CWMDS2025E
  EnableDashboards The model byte array was null. EnableDashboards aborting.
• CWMDS2026E
  EnableDashboards An IOException occurred during SVG Diagram processing. EnableDashboards aborting. 0
• CWMDS2027E
  EnableDashboards A Parser Configuration Exception occurred during SVG Diagram processing. EnableDashboards aborting. 0
• CWMDS2028E
  EnableDashboards A SAX Configuration Exception occurred during SVG Diagram processing. EnableDashboards aborting. 0
• CWMDS2029E
  EnableDashboards A Transformer Exception occurred during SVG Diagram processing. EnableDashboards aborting. 0
• CWMDS2030E
  EnableDashboards A Transformer Configuration Exception occurred during SVG Diagram processing. EnableDashboards aborting. 0
• CWMDS2031E
  EnableDashboards An Unsupported Encoding Exception occurred during String processing. EnableDashboards aborting. 0
• CWMDS2032E
  EnableDashboards A Parse Exception occurred during Kpi date processing. EnableDashboards aborting. 0
• CWMDS2033E
  EnableDashboards A Service Unavailable Exception occurred when getting the connection from the WAS pool: 0
• CWMDS2034E
  EnableDashboards A Naming Exception occurred when getting the connection from the WAS pool: 0
• CWMDS2036E
  A data access exception occurred: 0
• CWMDS2037E
  Data Access An SQLException occurred: 0
• CWMDS2038E
  Failed to mark cubes as stale for model 0 and version 1.
• CWMDS2039E
  The version 0 of model 1 is not found.
• CWMDS2040E
  Failed to obtain or parse the Monitor model resource for model 0.
• CWMDS2041E
  The monitoring context 0 was not found in model 1 and version 2.
• CWMDS2042W
  Error occurred when trying to get the status of data movement service or trying to suspend it for model 0. This could result in unpredictable results when deleting the instance from the source version.
• CWMDS2043E
  Failed to commit the database transaction. The instance transfer may not be successfully committed.
• CWMDS2044E
  Instance transfer encountered severe errors/exceptions and cannot be completed. The first error/warning message is as follows. See server logs for additional details. 0
• CWMDS2045W
  Instance transfer is completed with warning(s). The first warning message is as follows. See server logs for additional details. 0
• CWMDS2046E
  An error occurred while creating KPI History entries. Contact your system administrator.
• CWMDS2047E
  The instance type must be one of the following 3 values (case-insensitive): active, completed, all.
• CWMDS2048E
  DMS is running now or is set to Pending Run Now status for model '' 0'' and version '' 1''. It is recommended that instances be moved after Data Movement Service (DMS) is completed. Try again after DMS has finished.
• CWMDS2049E
  Failed to to obtain a connection from data source 0.
• CWMDS2500E
  Register scheduler task an unknown exception occurred: 0
• CWMDS2501E
  A data access exception occurred: 0
• CWMDS2502E
  Data Access An SQLException occurred: 0
• CWMDS2503I
  The scheduler task has not started.
• CWMDS2506E
  Invalid input 0.
• CWMDS2507E
  Scheduled Service 0 for model 1 and version 2 can not be found.
• CWMDS3003E
  An IO exception occurred when loading resources 0
• CWMDS3004E
  One or more of the later versions of a model is incompatible with an earlier version. 0
• CWMDS3100E
  Failed to load properties from file : 0
• CWMDS3101E
  Some unexpected error happened : 0
• CWMDS3102E
  Error happened during MQT script generation : 0
• CWMDS3103W
  These Measures are based on Stopwatch and are not summarized:
• CWMDS3104W
  These KPIs reference a nullable time metric and are not summarized:
• CWMDS3105W
  These KPIs are based on Stopwatch and are not summarized:
• CWMDS3106E
  Could not open file: 0
• CWMDS3107E
  Option 0 not specified.
• CWMDS3108E
  Model 0 not found.
• CWMDS3109E
  Available models: 0
• CWMDS3110E
  Version 0 not found.
• CWMDS3111E
  Available versions of model 0: 1
• CWMDS3112E
  Unknown option: 0
• CWMDS5002E
  Runtime exception has occurred when writing to the data movement service log table. Stored procedure '' 0'' 1
• CWMDS5003E
  The following SQLException has occurred when invoking Stored Procedure '' 0'' for model '' 1'', version '' 2'' and Monitoring Context '' 3'': 4
• CWMDS5012E
  No DMS stored procedure is found in DMS metadata table for model 0 and version 1
• CWMDS5013E
  Failed to initialize DMSAccess.
• CWMDS5014E
  The following error has occurred when executing the stored procedure '' 0'' for model '' 1'', version '' 2'' and Monitoring Context '' 3'': 4
• CWMDS5015E
  The following SQLException has occurred when invoking Stored Procedure '' 0'' for model '' 1'' and version '' 2'': 3
• CWMDS5901E
  Failed to run the Cognos task to clear cache for model 0 and version 1. Details: 2
• CWMDS5902E
  KPI History generation failed for model 0 and version 1 due to the following error: 2
• CWMDS5903E
  KPI Prediction creation failed for model 0 and version 1 due to the following error: 2
• CWMDS5904E
  Data Movement Scheduler Service failed for model 0 and version 1 due to the following error: 2
• CWMDS5905E
  Alphablox Cube Refresh Scheduler Service failed for model 0 and version 1 due to the following error: 2
• CWMDS5909I
  Service 0 is disabled or suspended for model 1. Skip it.
• CWMDS5910I
  Service 0 for model 1 is not due yet. Next start time is 2.
• CWMDS5911E
  Service 0 for model 1 can not be invoked due to internal server error. Check log for details.
• CWMDS5912W
  Service 0 for model 1 does not have any registered version services.
• CWMDS5913W
  Model version is not started. Service 0 is not invoked for model 1 and version 2.
• CWMDS5914E
  Archive/Prune service for model 0 and version 1 failed due to the following error: 2
• CWMDS5915E
  The following exception was thrown from service SPI 0 for model 1 and version 2: 3
• CWMDS5916E
  Cognos Cache Clearing service failed for model 0 and version 1 due to the following exception: 2
• CWMDS6001E
  The search string payload is not valid. It should be a single JSON object which has the key "Search String" and a string value.
• CWMDS6002E
  The sort column array is not valid.If the sort column array is in the query string of the HTTP request, it must be a string or a JSON string array: "sortColumn" or ["sortColumn1", "sortColumn2"]. If the sort column array is in the payload of the HTTP request, it must be in the following format: "Sort":[{"SortBy":"sortColumn1","Order":"asc"},{"SortBy":"sortColumn2","Order":"desc"}].
• CWMDS6003E
  The sort order array is not valid.If the sort order array is in the query string of the HTTP request, it must be a string or a JSON string array: "asc" or ["asc", "desc"]. If the sort order array is in the payload of the HTTP request, it must be in the following format: "Sort":[{"SortBy":"sortColumn1","Order":"asc"},{"SortBy":"sortColumn2","Order":"desc"}].
• CWMDS6004E
  The "Sort" payload is not valid.It must be in the following format: "Sort":[{"SortBy":"sortColumn1","Order":"asc"},{"SortBy":"sortColumn2","Order":"desc"}].
• CWMDS6050E
  The currency code '' 0'' is not a valid code.
• CWMDS6101E
  Invalid Filter Operator 0
• CWMDS6102E
  Filter operand is null - filter requries at least one operand.
• CWMDS6103E
  Filter operators isNull and isNotNull do not require any operands.
• CWMDS6104E
  More than one filter operands are detected.
• CWMDS6105E
  Invalid Time Period 0
• CWMDS6106E
  Operator and operands can not have values if using Time Period filtering.
• CWMDS6107E
  Period Duration or Period Basis value for Repeating Time Period can not be null.
• CWMDS6108E
  The value of Period Duration for Repeating Time Period is invalid.
• CWMDS6109E
  The value of Period basis for Repeating Time Period is invalid.
• CWMDS6110E
  Rolling quantity can not be null.
• CWMDS6111E
  The Rolling Quantity is not a valid integer.
• CWMDS6112E
  Rolling duration can not be null.
• CWMDS6113E
  Invalid Rolling Period Duration 0
• CWMDS6114E
  At least one of Start Date and End Date for Fixed Time Period must have a value.
• CWMDS6115E
  Start Date is not in the valid format. XPath format is required.
• CWMDS6116E
  End Date is not in the valid format. XPath format is required.
• CWMDS6117E
  Metric is not Date or DateTime data type. The time period filter is invalid.
• CWMDS6118E
  Filter metric ID is null
• CWMDS6119E
  The following metric ID is not valid 0
• CWMDS6120E
  Time Period cannot be null.
• CWMDS6121E
  IO exception occurred when trying to serialize a JSON object.
• CWMDS6122E
  The following monitor object was not found type= 0, version= 1, ID= 2
• CWMDS6123E
  The following monitor object was not found type= 0, ID= 1
• CWMDS6124W
  The following monitor objects were not found type= 0, version= 1, parent ID= 2
• CWMDS6125W
  The following monitor objects were not found type= 0, parent ID= 1
• CWMDS6126E
  IO exception occurred when trying to parse a serialized JSON payload.
• CWMDS6127E
  Unsupported URI: 0
• CWMDS6128E
  The metric data type is not STRING. Metric value list can only be provided for STRING type metrics.
• CWMDS6129E
  Unable to load visual diagram.
• CWMDS6130E
  A maximum of one year of KPI History records can be created.
• CWMDS6131E
  The requested page 0 does not exist.
• CWMDS6132E
  One of the filter values cannot be processed. Filter values must be strings, numbers or Boolean values.
• CWMDS6133E
  The metric ID array, currency code array and/or decimal place array provided in the REST payload do not have the same size.
• CWMDS6134E
  REST found a null metric ID or a null decimal place in the metric ID array or decimal array provided in the REST payload.
• CWMDS6135E
  The KPI icon jar is not found.
• CWMDS6136E
  The requested icon image is not found.
• CWMDS6137E
  The REST Gateway application 'REST Services Gateway' is not found.
• CWMDS6138E
  The sort column array is not valid.If the sort column array is in the query string of the HTTP request, it must be a string or a JSON string array: "sortColumn" or ["sortColumn1", "sortColumn2"]. If the sort column array is in the payload of the HTTP request, it must be in the following format: "Sort":[{"SortBy":"sortColumn1","Order":"asc"},{"SortBy":"sortColumn2","Order":"desc"}].
• CWMDS6139E
  The sort order array is not valid.If the sort order array is in the query string of the HTTP request, it must be a string or a JSON string array: "asc" or ["asc", "desc"]. If the sort order array is in the payload of the HTTP request, it must be in the following format: "Sort":[{"SortBy":"sortColumn1","Order":"asc"},{"SortBy":"sortColumn2","Order":"desc"}].
• CWMDS6150E
  Invalid XPath value 0
• CWMDS6151E
  Invalid Metric filter value " 0" or Metric data type " 1".
• CWMDS6152E
  The alias for the CEI Server Source cannot be blank.
• CWMDS6153E
  The alias 0 already exists as a CEI Server Source.
• CWMDS6250E
  The XML payload within the HTTP request is not a valid XML.
• CWMDS6300E
  The JSON payload within the HTTP request is not in a valid format.
• CWMDS6301E
  IOException occured when serializing the JSON output of the HTTP request.
• CWMDS6302E
  Unexpected system error. Possible causes include database unavailable, network error, incorrect or insufficient credentials to connect to the database.
• CWMDS6303E
  A database exception occurred. Check the SQL Exception.
• CWMDS6304E
  Error getting user credentials from WebSphere VMM.
• CWMDS6351E
  The JSON payload is not in a valid format.
• CWMDS6364E
  The following exception was caught when getting the KPI icon paths: 0
• CWMDS6366E
  The following KPI attribute was submitted with an invalid format attribute 0, value submitted 1, type required 2
• CWMDS6367E
  An error occurred while creating KPI History entries. Contact your system administrator.
• CWMDS6370E
  The following KPI prediction model was not found: ID= 0, version= 1
• CWMDS6371E
  The following parameter is missing from the HTTP request: 0
• CWMDS6372W
  The request referenced metrics that are not visible to the user. The metrics will be removed from the request.
• CWMDS6373E
  KPI 0 is not visible to the user.
• CWMDS6374E
  KPI 0 contains an aggregated metric that is hidden from the user.
• CWMDS6375E
  KPI 0 contains a metric filter that references a hidden metric.
• CWMDS6376E
  KPI 0 contains a time period metric that is hidden from the user.
• CWMDS6377E
  Calculated KPI 0 references a KPI that is hidden from the user.
• CWMDS6554E
  SQL injection check failed. The following reserved SQL keyword was found in the request: 0
• CWMDS6555E
  REST can not find the SQL injection keyword property file. SQL injection check will fail for every REST request.
• CWMDS6556E
  SQL injection check failed. The HTTP request contains "||" character which is not allowed.
• CWMDS6557E
  Failed to obtain database connection.
• CWMDS6650E
  Security provider 0 implements the wrong interface.
• CWMDS6651E
  Security provider 0 cannot be instantiated.
• CWMDS6652E
  The security provider cannot be found for model 0.
• CWMDS6653E
  User information could not be obtained from WebSphere Application Server security.
• CWMDS6654E
  User group information could not be obtained from WebSphere Application Server security.
• CWMDS6655E
  Security filters could not be obtained for model 0 and monitoring context 1 for user 2.
• CWMDS6656E
  Object security could not be obtained for 0 of model 1 and monitoring context 2 for user 3.
• CWMDS6657E
  Object security could not be obtained for 0 of model 1 for user 2.
• CWMDS6658E
  The user-distinguished name could not be obtained for user ID 0.
• CWMDS6659E
  An exception occurred while parsing the serialized security rules JSON string 0.
• CWMDS6660E
  An exception occurred while serializing the security rules JSON object 0.
• CWMDS6661E
  The whole security filters defined for model 0 could not be obtained.
• CWMDS6662E
  The whole object security rules defined for model 0 could not be obtained.
• CWMDS6800E
  IO Exception occurred when trying to serialize a JSON object.
• CWMDS6801E
  IO Exception occurred when trying to parse a serialized JSON payload.
• CWMDS6803E
  The following error occurred while processing the REST request: 0
• CWMDS6815E
  The following error occurred when trying to obtain the CEI emitter. Ensure CEI is enabled and active: 0
• CWMDS6816E
  The input (XML or Atom) cannot be null.
• CWMDS6817E
  The input content type is invalid. It should be either "text/xml" or "application/atom+xml".
• CWMDS6818E
  The Monitor emitter cannot be obtained. Will retry in 15 seconds...
• CWMDS6819E
  Event validation failed when processing the ATOM feed. Exception: 0 First failed entry in the ATOM feed: 1
• CWMDS6820E
  Event validation failed when processing the XML. Exception: 0 Failed XML: 1
• CWMDS6821E
  XML Header Removal failed when processing the XML. Exception: 0 Failed XML: 1
• CWMDS6822E
  XML Header removal failed when processing the ATOM feed. Exception: 0 First failed entry in the ATOM feed: 1
• CWMDS6823E
  ATOM parsing failed when processing the ATOM feed. Exception: 0
• CWMDS6840E
  The payload content type is not valid. It must be of type 'application/atom+xml' or 'text/xml'.
• CWMDS6841E
  The error message is null. It is not possible to return the error that occurred. See system logs.
• CWMDS6846E
  IOException occurred when serializing the JSON output of the HTTP request.
• CWMDS6847E
  Unsupported URI: 0
• CWMDS6900E
  The following JMS exception occurred when retrieving the message: 0
• CWMDS6901E
  The JMS message must be a text message.
• CWMDS6902E
  The following exception occurred when processing the XML and sending CBE: 0
• CWMDS7000E
  An error occurred because no export file was specified.
• CWMDS7001E
  An error occurred because no model ID was specified.
• CWMDS7002I
  The export completed successfully. 0 Security Filters were exported.
• CWMDS7003E
  An error occurred. No Security Filters were exported.
• CWMDS7004I
  Details
• CWMDS7005I
  Check the WebSphere Application Server trace file for errors.
• CWMDS7006E
  Invalid arguments
• CWMDS7007I
  Usage
• CWMDS7009I
  Example
• CWMDS7010I
  0 Security Filters were imported.
• CWMDS7011E
  Not all Security Filters were imported.
• CWMDS7012E
  An error occurred: No Security Filters were deleted.
• CWMDS7013E
  Model ID 0 does not exist.
• CWMDS7014E
  MCID 0 does not exist for Model ID 1.
• CWMDS7015E
  0: 1 can not be found. The security filter was not imported.
• CWMDS7016E
  0: 1 can not be found.
• CWMDS7017I
  0 Security Filters were successfully deleted.
• CWMDS7018E
  An error occurred: No Object Security Rules were exported.
• CWMDS7019E
  An error occurred: No Object Security Rules were deleted.
• CWMDS7020I
  Object Security Rules were successfully deleted
• CWMDS7021E
  Errors occurred: Not all Object Security Rules were imported.
• CWMDS7022E
  The file to be imported has format errors. No Security Filters were imported.
• CWMDS7023W
  Details
• CWMDS7024W
  Warnings have been returned by Object Security deletion.
• CWMDS7025W
  Warnings have been returned by Object Security import.
• CWMDS7026E
  Filter Metric ID 0 does not exist for Monitoring Context: 1. The security filter was not imported.
• CWMDS7029E
  The filter value case sensitive operator 0 is not supported. The security filter for 1 was not imported.
• CWMDS7030E
  The JSON input file is not properly formatted.
• CWMDS7031E
  SecurityFilterArray must be the first object in the input JSON.
• CWMDS7032E
  Incomplete Fine Grained Security Filter. The security filter for 0 was not imported.
• CWMDS7033E
  Incomplete Fine Grained Security FilterSet. The security filter for 0 was not imported.
• CWMDS7034E
  The Fine Grained Security Object contains the unsupported object: 0 The security filter for 1 was not imported.
• CWMDS7035E
  The parameter "-includegroups" can only be used if a user ID/DN or a group ID/DN has been specified.
• CWMDS7036E
  Only one User or Group may be specified for each Fine Grained Security Filter. The security filter for 0 was not imported.
• CWMDS7037E
  User ID '' 0'' can not be resolved.
• CWMDS7038E
  User DN '' 0'' can not be found.
• CWMDS7039E
  Group ID '' 0'' can not be resolved.
• CWMDS7040E
  Group DN '' 0'' can not be found.
• CWMDS7041I
  The import completed successfully.
• CWMDS7042W
  Some exported Object Security rules were found to be referencing invalid objects. These objects may have been deleted from the system. Delete the Object Security rules related to these invalid objects using Object Security delete command.
• CWMDS7043I
  The export completed successfully.
• CWMDS7044E
  Monitoring Context 0 was not found for Monitoring Model 1.
• CWMDS7045E
  The metric filter type " 0" is not supported by Fine Grained Security. The following filter was not imported: 1
• CWMDS7046E
  The filter operator " 0" is not supported for Boolean metric filter types. The following filter was not imported: 1
• CWMDS7047E
  The filter operator " 0" is not supported for string metric filter types. The following filter was not imported: 1
• CWMDS7048E
  The filter operator " 0" is not supported for integer and decimal metric filter types. The following filter was not imported: 1
• CWMDS7049E
  The filter value 0 is not supported for Boolean metric types. The value must be true() or false(). The following filter was not imported: 1
• CWMDS7050E
  The model must be included if the mc is specified.
• CWMDS7051E
  A userid, userdn, groupid or groupdn must be included when using the includegroups option.
• CWMDS7052E
  The fine grained security substitution attribute 0 could not be resolved.
• CWMDS7500E
  The JSON input is missing the item '' 0''
• CWMDS7501E
  An invalid object type '' 0'' exists in the command.
• CWMDS7502E
  The following SQL exception occurred during an export of Object Security Rules: 0
• CWMDS7503E
  The following I/O exception occurred during serialization of the JSON output: 0
• CWMDS7504E
  The following SQL exception occurred during deletion of Object Security Rules: 0
• CWMDS7505E
  For Metric, Measure and Dimension object types, the object ID and monitoring context ID must both be present or both be absent. It is incorrect to specify only one of them.
• CWMDS7506E
  The monitoring context ID is not a valid parameter for KPI and AlertTemplate object types.
• CWMDS7507E
  The monitoring context ID and the object ID are invalid parameters if the object type is not specified.
• CWMDS7508E
  The following parameter has an incorrect value: 0
• CWMDS7509E
  The command cannot include both a user and a group.
• CWMDS7510E
  The Object Security JSON definition file contains an invalid value and cannot be imported: JSON key '' 0'', value '' 1''
• CWMDS7511E
  An error occurred during an attempt to obtain the Action Manager Repository Manager.
• CWMDS7512W
  There were no Object Security rules found that fell into the criteria of the request. No Object Security rules were deleted.
• CWMDS7513E
  The parameter "-includegroups" can only be used if a user ID/DN or a group ID/DN has been specified.
• CWMDS7514E
  The following exception occurred during the export of Object Security rules: 0
• CWMDS7515E
  The JSON file is missing the required element "ObjectSecurityArray". No Object Security rules were imported.
• CWMDS7516E
  The "ObjectSecurityArray" array is empty. No Object Security rules were imported.
• CWMDS7517W
  Could not find any of the following elements in the JSON file for model 0: "MetricRules", "DimensionRules", "MeasureRules", "KPIRules" and "AlertRules". No Object Security rules were imported for this model.
• CWMDS7518E
  Error occurred when importing the following Object Security rule: model= 0, monitoring context= 1, metric= 2, group/user= 3. Error details: 4
• CWMDS7519E
  Error occurred when importing the following Object Security rule: model= 0, monitoring context= 1, measure= 2, group/user= 3. Error details: 4
• CWMDS7520E
  Error occurred when importing the following Object Security rule: model= 0, monitoring context= 1, dimension= 2, group/user= 3. Error details: 4
• CWMDS7521E
  Error occurred when importing the following Object Security rule: model= 0, alert= 1, group/user= 2. Error details: 3
• CWMDS7522E
  Error occurred when importing the following Object Security rule: model= 0, KPI= 1, group/user= 2. Error details: 3
• CWMDS7523I
  0 Object Security rules were successfully added or updated.
• CWMDS7524E
  The JSON file is missing required element "HiddenFrom" and "VisibleTo" for the following object: model= 0, object type= 1.
• CWMDS7525E
  Could not find any valid user/group in the JSON file for the following metric(s): model= 0, monitoring context= 1, metric IDs= 2
• CWMDS7526E
  Could not find any valid user/group in the JSON file for the following measure(s): model= 0, monitoring context= 1, measure IDs= 2
• CWMDS7527E
  Could not find any valid user/group in the JSON file for the following dimension(s): model= 0, monitoring context= 1, dimension IDs= 2
• CWMDS7528E
  Could not find any valid user/group in the JSON file for the following dynamic alert(s): model= 0, dynamic alert IDs= 1
• CWMDS7529E
  Could not find any valid user/group in the JSON file for the following KPI(s): model= 0, KPI IDs= 1
• CWMDS7530W
  Model '' 0'' is invalid.
• CWMDS7531W
  Monitoring context '' 0'' is invalid.
• CWMDS7532W
  The following metric is invalid: model= 0, monitoring context= 1, metric= 2
• CWMDS7533W
  The following measure is invalid: model= 0, monitoring context= 1, measure= 2
• CWMDS7534W
  The following dimension is invalid: model= 0, monitoring context= 1, dimension= 2
• CWMDS7535W
  The following dynamic alert is invalid: model= 0, monitoring context= 1, dynamic alert= 1
• CWMDS7536W
  The following KPI is invalid: model= 0, monitoring context= 1, KPI= 1
• CWMDS7537W
  User 0 is invalid.
• CWMDS7538W
  Group 0 is invalid.
• CWMDS7700E
  The UserDN and groupDN lists cannot both be null or empty.

Messages