Reason:
An attempt was made to build a container for a configuration that already has one.
Action:
The status of the configuration is incorrect. Refresh the table of configurations under the Configurations tab.
Reason:
An attempt was made to build a container but the build was unable to locate the metadata for the configuration.
Action:
Reason:
An attempt was made to build a container but the build was unable to parse the metadata for the configuration.
Action:
Delete the configuration and try to rebuild it again. If the problem persists, save and report this message to CA Support.
Reason:
An attempt was made to build a configuration but no configuration descriptors were found.
Action:
Delete the configuration and recreate it. If the problem persists, save and report this message to CA Support.
Reason:
An attempt was made to build a configuration but no FMIDs were selected.
Action:
Edit you configuration and verify that at least one FMID has been selected. If the problem persists, save and report this message to CA Support.
Reason:
An attempt was made to build a configuration but there was an internal metadata error.
Action:
Contact CA Support.
Reason:
A resource with this name is already being used as part of another configuration, and a duplicate cannot be created.
Action:
Go back and edit your configuration. Review the list of resources, and correct any errors that are reported.
Reason:
An attempt was made to build a configuration but a resource that is trying to be updated is currently locked.
Action:
Wait for the configuration that has locked the resource to complete and try again.
Reason:
An attempt was made to delete a configuration that is currently in use by another process.
Action:
Make sure that the configuration is not currently being edited, and that no implementation or validation tasks are running against it.
Reason:
An attempt was made to delete a configuration but NOMAINT is set on in the database.
Action:
Disable NOMAINT mode in the database, and try to delete the configuration again.
Reason:
An attempt was made to delete a configuration but a shared resource cannot be deleted because it is currently locked.
Action:
Complete the processing that is currently locking the resource and try to delete the configuration again.
Reason:
An error has occurred while trying to access the database.
Action:
See the CA Datacom/DB Message Reference Guide for more information.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|