Previous Topic: MSMC1000-1025Next Topic: SCS Address Space Abend Completion Codes


MSMC2100-2604

MSMC2100E

Specified User ID is not authorized to create configuration

Reason:

The specified user does not have the user level authority required to create configurations. User ID: user_identification.

The ID of the user that is not authorized is user_identification.

Action:

  1. Verify with the CA CSM administrator that the User ID has the required CA CSM authority.
  2. Verify with the CA CSM administrator that the User ID has the required system level authority.
  3. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2101E

Specified User ID is not authorized to delete configuration

Reason:

The specified user does not have the user level authority required to delete the target configuration. User ID: user_identification.

The ID of the user that is not authorized is user_identification.

Action:

  1. Verify with the CA CSM administrator that the User ID has the required CA CSM authority.
  2. Verify with the CA CSM administrator that the User ID has the required system level authority.
  3. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2102E

Specified User ID is not authorized to view configuration

Reason:

The specified user does not have the user level authority required to view the target configuration. User ID: user_identification.

The ID of the user that is not authorized is user_identification.

Action:

  1. Verify with the CA CSM administrator that the User ID has the required CA CSM authority.
  2. Verify with the CA CSM administrator that the User ID has the required system level authority.
  3. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2103E

The lock for the configuration is a valid lock and cannot be reset

Reason:

The reset status command determined that the lock is valid and cannot be reset because another user is already using the lock.

Action:

Wait for the other user to finish their work with the configuration. Then, retry your action.

MSMC2150E

JAXB initialization of new instance failed

Reason:

Initialization of the XML to Java object translation infrastructure required to process the configuration metadata has failed.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2151E

Unmarshal of Configuration Unit XML from string failed

Reason:

Processing of the current configuration metadata has failed. Problems were encountered when attempting to convert the configuration metadata from XML string elements into Java objects.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2152E

Unmarshal of Configuration Unit from XML file failed

Reason:

Processing of the current configuration metadata has failed. Problems were encountered when attempting to convert the configuration metadata from an XML file into Java objects.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2153E

Marshal of Configuration Unit to XML string failed

Reason:

Processing of the current configuration metadata has failed. Problems were encountered when attempting to convert the configuration metadata from Java objects back into XML string elements.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2154E

Marshal of Configuration Unit to XML file failed

Reason:

Processing of the current configuration metadata has failed. Problems were encountered when attempting to convert the configuration metadata from Java objects back into an XML file.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2155E

Unmarshal of Configuration Unit from XML node failed

Reason:

Processing of the current configuration metadata has failed. Problems were encountered when attempting to convert the configuration metadata from an XML node into Java objects.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2200E

Numeric expression evaluation error

Reason:

The CA CSM configuration wizard encountered an exception while processing a numeric expression required to calculate a variable value.

Action:

  1. Attempt to inspect the description text of the problem variable and its dependencies, if any, within the CA CSM configuration wizard. If possible, verify that dependent variables contain proper values.
  2. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2201E

String expression evaluation error

Reason:

The CA CSM configuration wizard encountered an exception while processing a string expression required to calculate a variable value.

Action:

  1. Attempt to inspect the description text of the problem variable and its dependencies, if any, within the CA CSM configuration wizard. If possible, verify that dependent variables contain proper values.
  2. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2202E

NumberFormatException conversion error

Reason:

An exception was encountered when trying to convert a nonnumeric string value to a number.

Action:

  1. Attempt to inspect the description text of the problem variable and its dependencies within the CA CSM configuration wizard, if this error is associated with user data input. If possible, verify that dependent variables contain proper values.
  2. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2203E

ArithmeticException numeric operation error

Reason:

An exception was encountered when attempting to perform an arithmetic operation with two or more parameters.

Action:

  1. Attempt to inspect the description text of the problem variable and its dependencies within the CA CSM configuration wizard, if this error is associated with user data input. If possible, verify that dependent variables contain proper values.
  2. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2204E

Unknown numeric expression error

Reason:

An invalid expression operand was encountered when processing an expression involving numeric data.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2205E

Invalid string expression type encountered

Reason:

An invalid expression operand was encountered when processing an expression involving string data.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2206E

A nonnumeric value is being used in a numeric compare operation

Reason:

A numeric variable used within a compare operation appears to contain a nonnumeric value.

Action:

  1. Attempt to determine the variable that is the cause of the error. If possible, verify that the content of the variable is correct for its type.
  2. Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2207E

Number format exception during include condition comparison

Reason:

The configuration metadata for this product has encountered a syntax error when executing the compare operation for an include condition.

One or more of the following values being compared are not numbers:

referenced_variable_name

Specifies the name of the referenced variable as found within the configuration metadata.

referenced_variable_current_value

Specifies the current value of the referenced variable. This value is expected to be numeric.

referenced_variable_comparison_value

Specifies the value the referenced variable is being compared to. This value is expected to be numeric.

Action:

  1. Determine which variable is causing the error.
  2. Verify that the content of the variable is correct for its type.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2250E

Unknown configuration validation error

Reason:

A configuration validation request was sent to the SCS address space. An error was encountered but no further error data is available from the SCS address space.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2251E

A configuration metadata validation error has occurred

Reason:

An error was encountered during the configuration metadata validation process. Validation errors: error_name.

The ID of the user that is not authorized is user_identification.

Action:

  1. Inspect the error dialog message for mention of validation error message data files.
  2. If there are validation error message data files, take steps to preserve them.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2252E

Failed to open and/or read a schema validation file

Reason:

An error was encountered during the configuration metadata validation process when trying to open a required schema file. File name:file_name.

The ID of the user that is not authorized is user_identification.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2253E

Failed to open and/or read a transformation file

Reason:

An error was encountered during the configuration metadata validation process when trying to open a required metadata transformation file. File name: file_name.

The ID of the user that is not authorized is user_identification.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2254E

Failed to process a required transformation file

Reason:

An error was encountered during the configuration metadata validation process when trying to process the contents of a required transformation file. File name: file_name.

The ID of the user that is not authorized is user_identification.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2255E

Failed to create an empty Document Object Model document

Reason:

An error was encountered during the configuration metadata validation process when trying to initialize an empty Documents Object Model.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2256E

Failed to marshal the configuration metadata into a DOM document

Reason:

An error was encountered during the configuration metadata validation process when trying to convert the configuration metadata into a Document Object Model object.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2257E

XPath failed to find ID attributes within the configuration

Reason:

An error was encountered during the configuration metadata validation process. The XPath process failed to locate ID attributes within the target configuration.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2258E

Performing symbolic resolution on the configuration failed

Reason:

An error was encountered during the configuration metadata validation process when attempting to perform symbolic resolution.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2259E

Processing configuration include conditions failed

Reason:

An error was encountered during the configuration metadata validation process while processing include conditions for the target configuration.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2260E

Processing metadata into a readable document failed

Reason:

An error was encountered during the configuration metadata validation process when trying to process the metadata into a readable document.

Action:

Search problem reporting data bases for a fix for the problem. If unable to resolve the problem, save and report this message to CA Support.

MSMC2261E

Parse error in the schema used to validate a configuration

Reason:

An error was encountered during the configuration metadata validation process. A schema parsing error was encountered.

Action:

  1. Inspect the error dialog message for mention of validation error message data files. If there are validation error message data files, take steps to preserve them.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2262E

Transformation error encountered during symbol resolution

Reason:

An error was encountered during the configuration metadata validation process. A transformation error occurred during the symbol resolution phase.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2263E

The transformation/validation of the configuration failed

Reason:

An error was encountered during the transformation and validation configuration meta data.

Action:

  1. Inspect the error dialog message for further information related to the error. If there are validation error message data files, take steps to preserve them.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2264E

Saving of validation error data failed

Reason:

An error was encountered while attempting to validate the configuration metadata. An attempt to save validation error data to files has failed.

Action:

  1. Inspect the error dialog message. If there are validation error message data files, take steps to preserve them for CA Support.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2265E

Validation of the configuration failed, parse error

Reason:

An error was encountered during the configuration metadata validation process. An XML parsing error was encountered.

Action:

  1. Inspect the error dialog message. If there are validation error message data files, take steps to preserve them for CA Support.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2266E

Failed to marshal the configuration into a DOM document

Reason:

An error was encountered during the configuration metadata validation process. Marshaling of the configuration into the Document Object Model failed.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2267E

Reversing repeatable resources on the configuration failed

Reason:

An error was encountered during the configuration metadata validation process. The process of reversing repeatable resources for the configuration has failed.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2268E

Processing of repeatable resources has failed

Reason:

An error was encountered during the configuration metadata validation process. Transforming of the repeatable resources failed.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2269E

Processing repeatable processes and operations has failed

Reason:

An error was encountered during the configuration metadata validation process. Transforming the repeatable processes and operations failed.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2270E

Processing of target resolution has failed

Reason:

An error was encountered during the configuration metadata validation process. Processing of the target resolution failed.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2271E

Failed to marshal the configuration metadata into a DOM document

Reason:

An error occurred while attempting to load XML data into a Document Object Model object for use during the processing of default set by metadata.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2272E

XPath failed when searching for the defaultSetBy attributes

Reason:

An XPath XML parsing error occurred while attempting to locate the default set by elements within the target configuration metadata.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2273E

XPath id() function errors with defaultSetBy attribute

Reason:

An XPath XML parsing error occurred while attempting to process the id() function associated with a default set by element within the target configuration metadata.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2274E

Failed to marshal instance display data into a DOM document

Reason:

An error occurred while attempting to load instance display XML data into a Document Object Model object for use in processing of the configuration metadata.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2275E

XPath processing for instance display data ids has failed

Reason:

An XPath XML parsing error occurred while attempting to process the id() function associated with an instance display data within the target configuration metadata.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2276E

Parsing for reference variable of DefaultSetBy failed

Reason:

An error occurred while attempting to locate a reference variable associated with a default set by element within the target configuration metadata.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2277E

Tracking ID cannot be composed of symbol data content

Reason:

An error occurred while attempting to process configurable resources. A tracking identifier has been incorrectly defined. FMID: FMID tracking_identifier tracking ID: incorrect_tracking_identifier.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2278E

A stack overflow error has been detected

Reason:

The CA CSM UI Application Server has run out of stack space while processing the configuration meta data. The java parameter -Xss512m may need to be added to the STDENV file or the value needs to be increased.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2279E

An error occurred while attempting to fetch the configuration unit template

Reason:

The fetch of the deployments configuration unit template for the current configuration has failed. Configuration of the product cannot continue.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2280E

Thread interrupted exception processing configuration metadata

Reason:

The CA CSM UI Application Server was unable to acquire a lock necessary to process the configuration metadata.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2281E

Parse error in the configuration metadata

Reason:

An error was encountered during the configuration metadata validation process. A parsing error was encountered against the configuration.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2282E

Marshal or Unmarshal of Configuration Unit to XML string failed

Reason:

Processing of the current configuration metadata has failed. Problems were encountered when attempting to convert the configuration metadata from Java objects back into XML string elements.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2283E

An infinite loop was detected during symbol resolution of the Configuration Unit

Reason:

Processing of the current configuration metadata has failed. Problems were encountered when performing symbol resolution.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2350E

Request event message XML is missing or invalid

Reason:

The required XML data contained within an SCS address space request event message is missing or was found to be invalid.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2351E

RegisterEvents message for SCS address space failed

Reason:

Registration for notification of SCS address space target server response event messages has failed. The client is not notified when event response messages become available.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2352E

CreateEvent message for SCS address space failed

Reason:

The creation of the event record content for a request message targeting an SCS address space failed. The client is unable to communicate with the target address space.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2353E

SendEvent message to SCS address space failed

Reason:

A request event record message targeting an SCS address space could not be delivered. The request message was created, however, the send event failed.

Action:

Attempt to retry the operation that caused the failure. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2354E

Event message response from the SCS address space timed out

Reason:

A network communications timeout occurred while waiting for the response message from the SCS address space. The receive attempt may have been retried one or more times depending on the SCS address space communications settings within the CA CSM registry.

Action:

  1. Verify the current state of network activity, a severely overloaded network can result in this error.
  2. Verify that the SCS address space is available and responding with acceptable performance.
  3. Attempt to retry the operation that caused the failure.
  4. Consider increasing the defined TCP Connection Timeout and Retry values within the CA CSM system registry, Network Locations tab for the computer hosting the SCS address space.
  5. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2355E

Event message request/response correlation IDs mismatch

Reason:

The unique request/response message identifiers used to verify that message traffic integrity are out of sync. The SCS address space response message received does not belong to the current request message. The expected identifier correlation_identifier, the received identifier retrieved_correlation_identifier.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2356E

SCS address space event message character encoding error

Reason:

A code page character encoding error was encountered during the creation of the SCS address space request message or during the parsing of the SCS address space response message.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2357E

SCS address space event message invalid parameter error

Reason:

An error was encountered with one of the API required parameters during the creation of an SCS address space request message or during the parsing of an SCS address space response message.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2358E

SCS address space event message unknown exception error

Reason:

An uncategorized exception or error was encountered during the creation of an SCS address space request message or during the parsing of an SCS address space response message.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2359E

SCS address space message contains an unexpected event type received: event_type_name

Reason:

An unexpected result message was received as a result of a SCS address space request message sent to create an Instance Container required for configuration processing. Event type received: event_type_name.

The message type number that was received in error is message_type_number.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2360E

SCS address space target server communications error

Reason:

An unexpected or uncategorized communications error was encountered when communicating with the target SCS address space.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2361E

The connection object must be initialized

Reason:

An attempt was made to communication with at target SCS address space prior to initializing a connection object. A connection to the SCS address space must be established before proceeding.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2362E

Null or empty SCS address space hostname string specified

Reason:

An invalid host name was specified when attempting to connect to the target system SCS address space. The host name specified in the CA CSM system registry for this SCS address space is a null value or an empty string. Host name defined: host_name.

The actual host name value encountered is host_name.

Action:

  1. Verify that the SCS address space properties are properly defined for the target computer within the Network Locations tab within the CA CSM system registry.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2363E

Invalid SCS address space port number specified

Reason:

The port number configured for access to the target server SCS address space appears to be invalid. Port number specified: port_number.

The actual port number value encountered is port_number.

Action:

  1. Verify that the SCS address space properties are properly defined for the target system within the Network Locations tab within the CA CSM system registry.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2364E

Null returned From CommunicationsSection Open() API

Reason:

Attempting to initiate communications to the target server SCS address space has failed. The communications API Open() has returned a null value.

Action:

  1. Verify that the SCS address space properties are properly defined within the Network Locations tab for the target computer within the CA CSM system registry.
  2. Verify that the computer hosting the SCS address space is available, online, and can be connected to from the computer hosting the CA CSM client software.
  3. Verify that the SCS address space being targeted has been started and is available for use.
  4. Contact your network administrator to verify that there are no connectivity issues between the CA CSM client software hosting computer and the SCS address space hosting computer.
  5. Attempt to retry the operation which caused the failure.
  6. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2365E

Missing or invalid SCS address space message event type

Reason:

A missing or invalid SCS address space event message type has been specified. The current SCS address space request cannot continue.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2366E

The event message priority value is missing or invalid

Reason:

The target server SCS address space request event message contains a priority property that is not invalid. Value: priority_value_name.

The actual priority value encountered is priority_value_name.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2367E

The event message name is missing or invalid

Reason:

The required event name property contained within a target server SCS address space request event message is missing or invalid. Event name encountered: event_name.

The event name encountered is event_name.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2368E

The event message User ID is missing or invalid

Reason:

The required user ID property contained within a target server SCS address space request event message is missing or invalid User_identification: user_identification.

The user ID encountered is user_identification.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2369E

The event message event source name is missing or invalid

Reason:

The required event source name property contained within a target server SCS address space request event message is missing or invalid. Event source name: event_source_name.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2370E

The event message event-specific data is missing or invalid

Reason:

The required event-specific data property contained within a target server SCS address space request event message is missing or invalid. Event-specific data encountered: event_specific_data_text.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2371E

The event message correlation ID is missing or invalid

Reason:

The required message correlation ID property contained within a target server SCS address space request event message is missing or invalid. The correlation ID encountered: identification_name.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2372E

Invalid response event received from SCS address space

Reason:

An invalid response event message was received from the SCS address space target server. The event data was missing or has been corrupted.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2373E

Invalid or null request event data

Reason:

The request event data contained within a target server SCS address space request event message is missing or invalid.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2374E

Unmarshal of response ICRequest attribute failed

Reason:

The parsing of the target server SCS address space response message failed due to an invalid or missing ICRequest attribute.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2375E

Unmarshal of response ICRequest element failed

Reason:

The parsing of the target server SCS address space response message failed due to an invalid or missing ICRequest element.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2376E

XMLOperations - JAXB subsystem initialization failed

Reason:

Attempting to create a new instance of the JAXB XML to Java object conversion infrastructure required to facilitate communications to the SCS address space has failed.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2377E

JAXB exception encountered creating XML request message

Reason:

A Java to XML conversion exception was encountered when attempting to create a target system SCS address space request message.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2378E

Exception encountered creating XML request message

Reason:

An unknown or uncategorized exception was encountered during the Java to XML conversion when attempting to create a target system SCS address space request message.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2379E

JAXB exception encountered parsing XML response message

Reason:

An XML to Java conversion exception was encountered when attempting to parse a message received from the target system SCS address space. Exception message encountered: JAXB specific_exception. String being parsed: XML string_name.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2380E

A null response buffer was encountered during XML doc parsing

Reason:

An XML parsing API received an empty response buffer.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2381E

No event-specific data was found within the event message

Reason:

The required event specific data property contained within a target server SCS address space response event message is missing or invalid.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2382E

Unmarshal of XML response message failed

Reason:

The extraction of data from a target server SCS address space response message failed for an undetermined reason.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2383E

SCS address space XML response message contains a DBError

Reason:

The response message received from the target server SCS address space contains error data identifying a database error that occurred during the SCS address space processing of the request message.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator for possible resolutions.
  3. Consult with the system database administrator for possible resolutions.
  4. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2384E

SCS address space XML response message contains an XMLError

Reason:

The response message received from the target server SCS address space contains error data identifying an XML processing error that occurred during the SCS address space processing of the request message.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2385E

SCS address space XML response message contains a SAFError

Reason:

The response message received from the target server SCS address space contains error data identifying a Security Access Facility error that occurred during the SCS address space processing of the request message.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2386E

SCS address space XML response message contains a DYNError

Reason:

The response message received from the target server SCS address space contains error data identifying a dynamic allocation error that occurred during the SCS address space processing of the request message.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2387E

SCS address space XML message contains a FileAccessError

Reason:

The response message received from the target server SCS address space contains error data identifying a file access error that occurred during the SCS address space processing of the request message.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2388E

SCS address space response contains a SYSVIEWAPIError

Reason:

The response message received from the target server SCS address space contains error data identifying a Sysview API error that occurred during the SCS address space processing of the request message.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2389E

SCS address space XML response message contains an unknown error

Reason:

The response message received from the target server SCS address space contains error data identifying an unknown error that occurred during the SCS address space processing of the request message.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2390E

SCS address space XML response error, no event data found

Reason:

The response message received from the target server SCS address space appears to be corrupted. The message does not contain the required response event data.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2391E

SCS address space message missing error description data

Reason:

The response message returned from the SCS address space is missing expected error description data.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2392E

Event data from the SCS address space message is missing

Reason:

The response message received from the target server SCS address space does not contain the required event data.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2393E

Unknown SCS address space target system name specified

Reason:

The specified SCS address space target_system_name cannot be resolved to a TCP/IP address.

target_system_name specifies the name of the target server computer that cannot be resolved to a TCP/IP address.

Action:

  1. Verify that the SCS address space properties are properly defined within the Network Locations tab within the CA CSM system registry.
  2. Verify the computer hosting the SCS address space is available, online, and can be connected to from the computer hosting the CA CSM client software.
  3. Verify the SCS address space being targeted has been started and is available for use.
  4. Contact your network administrator to verify that there are no connectivity issues between the CA CSM client software hosting computer and the SCS address space hosting computer.
  5. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2394E

An unknown IOException communication error occurred

Reason:

An unknown IOException error occurred during a send/receive of a message to the SCS address space target_system_name. See the error log for details. target_system_name specifies the name of the host computer being communicated with when the error occurred.

Action:

  1. Verify that the computer hosting the SCS address space is available, online, and can be connected to from the computer hosting the CA CSM client software.
  2. Verify that the SCS address space being targeted has been started and is available for use.
  3. Contact your network administrator to verify that there are no connectivity issues between the CA CSM client software hosting computer and the SCS address space hosting computer.
  4. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2395E

SCS address space CommunicationsException error detected

Reason:

An SCS address space target system CommunicationsException was detected. SCS address space target system name: target_system_name.

target_system_name specifies the name of the host computer being communicated with when the error occurred.

Action:

  1. Verify that the computer hosting the SCS address space is available, online, and can be connected to from the computer hosting the CA CSM client software.
  2. Verify that the SCS address space being targeted has been started and is available for use.
  3. Contact your network administrator to verify that there are no connectivity issues between the CA CSM client software hosting computer and the SCS address space hosting computer.
  4. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2396E

SCS address space communications timeout exception

Reason:

A transmission timeout error occurred while waiting to receive a response message from SCS address space target system name: target_system_name. Wait time out: wait_timeout seconds, number of times retried: retry_count.

This error is typically seen when network traffic is more congested than normal or an SCS address space process takes longer to complete than expected.

Action:

  1. Verify the current state of network activity. A severely overloaded network can result in this error.
  2. Verify that the SCS address space is available and responding with acceptable performance.
  3. Consider increasing the defined TCP Connection Timeout and Retry values within the CA CSM system registry Network Locations tab for the computer hosting the SCS address space.
  4. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2398E

SCS address space target server definition not found

Reason:

The target system hosting the address space targeted by the specified configuration is not defined within the CA CSM system registry. System name: system_name.

system_name specifies the name of the host computer whose configuration data is missing.

Action:

  1. Verify that the name of the target system is correct.
  2. Verify within the CA CSM system registry, Network Locations, that the SCS address space definitions are correct for the expected target system.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2450E

File name missing for target resource

Reason:

A resource file request was made to the target system SCS address space however, the required file name for the resource is missing.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2453E

Unable to load configurable resources from XML

Reason:

An error has occurred during the processing of configurable resources within the configuration metadata.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2454E

SIA file transfer error. File segments out of order

Reason:

During the execution of the CA CSM configuration wizard, a metadata driven resource file transfer was initiated. An error was encountered due to attempting to process segments of file data in an incorrect sequence. Segment number expected: segment_number. Segment received: segment_number_received.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2455E

Hash value verification error during SIA file transfer

Reason:

During the execution of the CA CSM configuration wizard, a metadata driven resource file transfer was initiated.

An error was encountered when comparing a client side calculated message digest hash value, of the file content, with the value calculated by the server and sent to the client.

Data stored in the configuration metadata for the current resource is considered suspect.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2456E

SIA file transfer, Invalid file hash algorithm received

Reason:

During the execution of the CA CSM configuration wizard, a metadata driven resource file transfer was initiated.

The target system SCS address space subsystem has specified an invalid message digest hash algorithm.

Data stored in the configuration metadata for the current resource is considered suspect.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2457E

SIA file transfer, hash value encoding error encountered

Reason:

During the execution of the CA CSM configuration wizard, a metadata driven resource file transfer was initiated.

An unsupported encoding exception was encountered when attempting to calculate the message digest hash value for the received resource data.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2458E

SIA file transfer error encountered

Reason:

During the execution of the CA CSM configuration wizard, a metadata driven resource file transfer was initiated. An unexpected error occurred during the transfer attempt of file_name.

file_name indicates the name of the transferred file.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Verify that the file name being referenced exists.
  3. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  4. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2459E

SCS address space version incompatible

Reason:

The version (address_space_version) of the SCS address space does not support the current metadata packaged with the product you are configuring.

Action:

  1. On the target system, verify that the SCS address space is started.
  2. In the CA CSM system registry, navigate to the Network Locations subtab for this system and click Status to verify the version of the SCS address space.
  3. Consult the product information to verify that you are running the correct SCS address space version for the version of the product that you are configuring.
  4. Contact your CA CSM system administrator to verify that the SCS address space is running with correct release level libraries.
  5. Contact your CA CSM system administrator to upgrade the SCS address space to the correct version needed for this product.
  6. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2460E

SIA hash manifest segments out of order

Reason:

The retrieval of a deployment hash manifest was initiated. A manifest segment out of sequence error was encountered when processing multiple segments of the manifest data.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2461E

SIA retrieving the MVS system symbols failed

Reason:

The retrieval of the MVS system symbols was initiated and an error was encountered when getting the MVS symbol list.

Action:

Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2500E

A configuration build error was encountered

Reason:

An error was detected during a build attempt of the configuration at the SCS address space. Configuration name: configuration_name.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2501E

Configuration build request status reset invalid

Reason:

An error was encountered when attempting to reset the build results status.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2502E

Configuration build request status reset failed

Reason:

An error was encountered when attempting to reset the build results status.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2503E

Configuration state error not eligible to be built

Reason:

The definition for configuration_name completed within all panels of the configuration wizard before the configuration was eligible for building. Current_configuration_state.

Action:

  1. Verify that the configuration wizard completed the configuration process.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2504E

Failure attempting to send build configuration request to the SCS address space

Reason:

An unknown error was encountered during the transmission of a configuration build request to the address space. Additional information can be found in the details and additional diagnostics portion of this message.

Action:

  1. Refer to the SCS address space and CA CSM client software log files for additional information.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2505E

A configuration request sent to the SCS address space has failed

Reason:

A request sent to the SCS address space requesting a validate or implement request has failed.

Action:

  1. Refer to the SCS address space and CA CSM client software log files for additional information.
  2. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2550E

Delete configuration error encountered

Reason:

An exception was encountered when trying to delete a configuration. Error encountered: error_name

Action:

  1. Verify that the configuration is in a deletion state.
  2. See the product documentation for information regarding proper status states of configurations.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2600E

user_ID is not authorized to implement configurations

Reason:

The specified user does not have the user level authority required to implement the target configuration. User ID: user_identification.

user_identification indicates the user ID of the user that is not authorized.

Action:

  1. Verify with the CA CSM administrator that the user ID has the required CA CSM authority.
  2. Verify with the CA CSM administrator that the user ID has the required system level authority.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2601E

Configuration implementation stop request was invalid

Reason:

An error was detected during a configuration implementation attempting to process a Stop request.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2602E

SCS Address Space error occurred during implementation

Reason:

An error was detected while the SCS Address Space was processing the configuration implementation.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2603E

Starting of a supporting thread for Implementation has failed

Reason:

An error was detected while attempting to start a listening thread required to support the implementation process.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMC2604E

The ability to implement a configuration on this system has been disabled

Reason:

An environment variable has been set which disables implementing configurations on the target system.

Action:

  1. Refer to the error message details to determine if there are action suggestions.
  2. Consult with the CA CSM administrator to verify that the SCS address space is operating as expected.
  3. Search problem reporting databases for a fix for the problem. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.