# MetaDataConfiguration Subsystem Messages

The MetaDataConfiguration1.0 catalog contains messages in the range BEA2013400 - BEA2013499.
BEA-2013400 | Warning: WARNING : A FAILURE HAS OCCURRED WHILE READING THE META-DATA CONFIGURATION: s.
Description | There was a failure which occurred while reading the meta-data configuration. It is possible that the metadata-config.xml does not exist. This is not an error condition and the controller will start up successfully.
Cause | An error while reading the meta-data configuration
Action | There was a failure which occurred while reading the meta-data configuration. It is possible that the metadata-config.xml does not exist. This is not an error condition and the controller will start up successfully.
BEA-2013401 | Error: ERROR: THE METADATA-CONFIG.XML IS NOT VALID: s
Description | There was a validation error which occurred while reading the meta-data configuration. See message and stack trace for details.
Cause | A problem was found while validating the metadata-config.xml
Action | Take corrective action for the cause of the validation problem described in the message text.
BEA-2013402 | Error: A failure has occurred while sending the configuration to the configuration manager: s
Description | There was a failure which occurred after reading the configuration. See message and stack trace for details.
Cause | An error during initialization while sending the configuration to the configuration manager.
Action | A stack trace will be printed for this failure. Review the stack trace informaion to determine the cause.
BEA-2013403 | Error: An exception was thrown while updating path: s
Description | There was an error while trying to update the metadata-config.xml. See message for details
Cause | This is usually due to a validation problem or an I/O problem writing the file. The error message will contain more details.
Action | Take action based on the details in the error message.
BEA-2013404 | Warning: WARNING: THE METADATA CONFIGURATION COULD NOT BE PROCESSED. MOVING 'orig' TO 'curr' SO THAT IT WILL NOT BE OVERWRITTEN.
Description | The metadata-config.xml file for the controller was invalid. The invalid version will not be used to initialize the controller and will be moved to a backup file so that it will not be overwritten.
Cause | The metadata-config.xml is invalid. This may be due to an XML parsing error or higher level validation run on the file after it is loaded.
Action | There are basically two options. You can continue running the controller an build a new metadata-config.xml through the console or you can shut down the controller, correct the problem in the backed up file and then rename it back to metadata-config.xml so that the next boot of the controller picks up the repaired version.