CCEADME0000 | Unknown node alias. |
Explanation |
A node with the specified alias is not found. |
Action |
Provide a valid node alias. |
CCECAME0000 | The specified flatfile location does not exist. |
Explanation |
The flatfile repository was not located at the specified location on the file system. |
Action |
Specify a valid location for the flatfile repository. |
CCECAME0001 | A repository already exists at the same location. |
Explanation |
Two or more repositories cannot point to the same location. |
Action |
Specify a unique location for the new repository. |
CCECAME0002 | A repository with this name already exists. |
Explanation |
The name of the repository is not unique. |
Action |
Check the repository name and provide a unique name for the repository. |
CCECAME0003 | Repository name, type and location cannot be empty or missing. |
Explanation |
The name, type, and location are required parameters when creating asset type repositories. |
Action |
Specify values for all required parameters. |
CCECAME0004 | Name and type cannot be empty or missing. |
Explanation |
All parameters are required. |
Action |
Specify values for all parameters. |
CCECAME0005 | Update failed.Trying to update {0} asset repository when the cached repository is of type {1}. |
Explanation |
The specified asset repository type is incorrect. |
Action |
Specify the correct repository type. |
CCECCBE0000 | File with path {} can not be deleted. |
Explanation |
The file can not be deleted. |
Action |
Make sure the file is not used by any process. |
CCECCUI0143 | No ports configured for the specified runtime. |
Explanation |
There are no ports configured for the specified runtime. |
Action |
Configure a port. |
CCECCUI0288 | No rows were selected. You are about to download all Log Sources. |
Explanation |
No rows were selected in the Log Sources table before clicking the Download Selected Files menu option. |
Action |
No action required. |
CCECFRE0000 | The content of the response is not acceptable according to the accept headers |
Explanation |
The response content cannot be converted into the requested media type that is specified in the HTTP Accept header. For example, the response is in text format and cannot be converted into XML or JSON format. |
Action |
Try to load the configuration again and specify a supported media type. |
CCECFRE0001 | The ConfigurationTypeId "{1}" does not exist for RuntimeComponentId "{0}". |
Explanation |
One or more configuration types specified do not match or are not valid for the specified properties. |
Action |
Provide valid configuration types for the specified properties. You can determine the valid configuration types using the following command:cc list configuration types |
CCECFRE0002 | The ConfigurationTypeId "{0}" does not exist for RuntimeComponentId "{1}". |
Explanation |
There is no registered ConfigurationType with the provided ID for the specified runtime component. |
Action |
Provide a valid ConfigurationTypeId for the specified runtime component. You can determine the IDs for configuration typesusing the following command:cc list configuration types |
CCECFRE0005 | LandscapeConfigurationUiBindingService is not available. |
Explanation |
The LandscapeConfigurationUiBindingService is not registered. |
Action |
Ensure that the bundle that contains this service is active. |
CCECFRE0006 | Configuration instance {0} cannot store license keys. |
Explanation |
The specified configuration instance {0} cannot store license keys. |
Action |
Specify a configuration instances that is able to store license keys. Such configuration instances always start with the COMMON-LICENSE prefix. |
CCECFRE0007 | Getting the content of an input stream as string fails |
Explanation |
Command Central cannot convert the input stream as string. |
Action |
Check the logs for more information. |
CCECLTE0001 | The expected values expression could not be parsed correctly. |
Explanation |
The expected values expression could not be parsed correctly. |
Action |
Check the expected values expression for errors. |
CCECLTE0012 | A resource was not specified. |
Explanation |
The REST call failed because a remote resource location was not specified in the REST service. |
Action |
Specify a valid resource in the REST service, for example, spm/inventory/components. |
CCECLTE0013 | A URL was not specified. |
Explanation |
The REST call to the remote host failed because the URL was not specified. |
Action |
Specify a valid URL, for example, http://localhost:8092. |
CCECNFE0000 | LandscapeDefinition service is not available. |
Explanation |
The LandscapeDefinition service is not registered. |
Action |
Ensure that the bundle that contains this service is active and the service is properly configured. |
CCECNFE0001 | Landscape inventory service not available. |
Explanation |
The landscape inventory service was not configured. |
Action |
Ensure that the bundle that contains this service is active. |
CCECNFE0002 | Configuration service factory not available. |
Explanation |
A configuration service factory is not configured. |
Action |
Ensure that the bundle that contains the configuration service factory is active and that the component definition is correct. |
CCECNFE0003 | The configuration service encountered a remote request failure. |
Explanation |
The remote request for a configuration item failed. |
Action |
Ensure that the node in the request is active. |
CCECNFE0004 | The remote request encountered a concurrency error. |
Explanation |
The system could not execute parallel remote requests. |
Action |
Contact Software AG Global Support. |
CCECNFE0005 | Can not update credentials. |
Explanation |
The user credentials on Command Central can not be updated. |
Action |
Ensure that the runtimeComponentId and nodeAlias parameters are valid. |
CCECNFE0006 | Can not process JSON configuration. |
Explanation |
The JSON format of an old configuration is incorrect. |
Action |
Verify that the configuration uses proper JSON format. |
CCECNFE0008 | Can not update configurations cache because of failure during retrieval of remote configurations. |
Explanation |
The remote request for configuration items failed and the configurations cache can not be updated. |
Action |
Ensure that the node in the request is active. |
CCECNFE0009 | The configuration service encountered a remote request failure while retrieving configuration data for runtime component {0}, configuration instance {1}. |
Explanation |
The remote request for the specified configuration item failed. |
Action |
Ensure that the node in the request is active and check the Platform Manager logs. |
CCECOME0000 | Cannot perform an operation on nodes that are not accessible. The offline nodes are {0}. |
Explanation |
The specified nodes cannot be accessed because they are offline. |
Action |
Check the status of the specified nodes. Command Central can only access nodes that are online. |
CCECOME0002 | {0} on {1} ({2}) became unresponsive. Component restart may help to resolve this quickly. |
Explanation |
Specified components became unresponsive. |
Action |
Component restart may help to resolve this quickly. |
CCECOME0003 | {0} on {1} ({2}) crashed. You will need to start it again and investigate the cause of the failure. |
Explanation |
Specified components crashed. |
Action |
You will need to start it again and investigate the cause of the failure. |
CCECOME0007 | {0} of {1} on {2} ({3}) spiked into critical zone. The component may become overloaded! |
Explanation |
The specified component becomes overloaded. |
Action |
Try to release the load on the specified component. |
CCECOME0015 | Node {0} was not found. |
Explanation |
The specified node was not found. |
Action |
Check if the correct alias is used. If the node is not present in the landscape it can be added using the landscape service. If the node has been added but is still not accessible, contact Software AG Global Support. |
CCECOME0016 | Node {0} could not be created. |
Explanation |
A node with alias {0} could not be created because another node with alias {1} already exists. |
Action |
Provide a different alias for the new node. |
CCECOME0017 | Environment {0} could not be created. |
Explanation |
An environment with alias {0} could not be created because another environment with alias {1} already exists. |
Action |
Provide a different alias for the new environment. |
CCECOME0018 | Generation of checksum for license metering report failed |
Explanation |
The generation of the checksum for the license metering report failed. |
Action |
Contact Software AG Global Support. |
CCECOME0019 | Generation of report id for license metering report failed |
Explanation |
The generation of the report ID for the license metering report failed. |
Action |
Contact Software AG Global Support. |
CCECOME0020 | Cannot convert XML report to string |
Explanation |
The convertion of the XML report failed. |
Action |
Contact Software AG Global Support. |
CCECOME0025 | Generation of XML string for object instance of class {0} failed |
Explanation |
The generation of the XML string for object instance of class {0} failed. |
Action |
Provide a valid object instance. |
CCECOME0029 | License key {0} not found. |
Explanation |
The license key with the specified alias {0} is not found. |
Action |
Upload and assign a valid license key for this alias or use a different existing license key alias. |
CCECOME0030 | Checksum verification of report {0} failed! |
Explanation |
The checksum verification of report {0} failed. |
Action |
Contact Software AG Global Support. |
CCECOME0033 | Unable to parse this date string({0}). |
Explanation |
Unable to parse this date string({0}). |
Action |
Contact Software AG support. |
CCECOME0034 | Unexpected exception occurred: {0}. |
Explanation |
An unexpected exception occurred: {0}. |
Action |
Contact Software AG support. |
CCECOME0038 | The remote Platform Manager job with id {0} was not found. |
Explanation |
A job with the specified id was not found on Platform Manager. |
Action |
Specify an existing job id. |
CCECORE0001 | Exceeded the maximum nodes allowed as per the configured license. |
Explanation |
You have exceeded the nodes allowed to you as per the license configured for Command Central. |
Action |
Contact Software AG support to upgrade the license. |
CCECORE0002 | Invalid License found. The system is going to shutdown in 30 minutes. |
Explanation |
The configured license is invalid. You need to configure a valid license immediately else the system will shutdown in 30 mintures. |
Action |
Configure a valid license immediately. If you do not have one, contact your system dministrator or Software AG support. |
CCECORE0003 | Invalid License found. The system is shutting down. |
Explanation |
The system is shutting down as the configured license is invalid. |
Action |
Contact your Administrator or Software AG support. |
CCECORE0004 | The license has expired. |
Explanation |
The configured license has expired. |
Action |
Contact your system administrator or Software AG support. |
CCECORE0005 | The license is not valid for the current operating system. |
Explanation |
The configured license is not valid for the current operating system. |
Action |
Contact your Administrator or Software AG support. |
CCECORE0006 | The number of nodes has exceeded as per the configured license. |
Explanation |
As per the configured license, you are not allowed to add more nodes as you have exhausted the licensed number of nodes. |
Action |
Contact your system administrator or Software AG support to get the license upgraded to add more nodes. |
CCECORE0007 | Falied to get the node count from the license. |
Explanation |
This issue may occur when your license file is corrupt. |
Action |
Contact your system administrator or Software AG support. |
CCECORE0008 | The configured license is not valid for this product. |
Explanation |
Either the license file is not for Command Central or it may have be a corrupt file. |
Action |
Contact your system administrator or Software AG support. |
CCECORE0009 | Failed to read the product code from the license. |
Explanation |
This issue may occur when your license file is corrupt. |
Action |
Contact your system administrator or Software AG support. |
CCECORE0010 | The configured license is not valid for this product version. |
Explanation |
This issue may occur when your license file is corrupt. |
Action |
Contact your system administrator or Software AG support. |
CCECORE0011 | Failed to read the product version from the license. |
Explanation |
Either the license file is not for current version of Command Central or teh license file may be corrupt. |
Action |
Contact your system administrator or Software AG support. |
CCECORE0012 | Node with alias {0} is not found. |
Explanation |
The specified node is not found in Command Central. |
Action |
Ensure that the node alias is spelled correctly. You can view a list of installations and their aliases using either the Command Central Web user interface, the cc list landscape nodes command, or the REST API. |
CCECORE0013 | The specified search query is not valid. The supported search attributes are: {0} |
Explanation |
One or more attributes are not supported for this type of search. |
Action |
Ensure that the search attributes are supported for the type of search you want to perform. Make sure that the attributes are spelled correctly. The supported search attributes are listed in the error message. Note that search attributes are case-sensitive. |
CCECORE0014 | Task "{0}" for node "{1}" failed. |
Explanation |
The specified task failed to execute for the specified node. |
Action |
Read through the details provided in the error message and the logs, then take corrective steps. |
CCECORE0015 | Tasks execution has failed. |
Explanation |
Some or all of the tasks failed to execute. |
Action |
Read through the details provided in the error message and the logs, then take corrective steps. |
CCECORE0016 | The specified attribute name and the attribute name in the request are not the same. |
Explanation |
The attribute name in the body and the attribute name in the path segment should be the same. |
Action |
Fix the request and try again. |
CCECORE0017 | Specify attributes to created or updated. |
Explanation |
The request does not contain search attributes to be created or updated. |
Action |
Fix the request and submit it again. |
CCECORE0018 | {0} did not get {1} for {2} seconds! |
Explanation |
The specified node did not reach the expected status in the given amount of time. |
Action |
Retry the operation or contact SoftwareAG Global Support. |
CCECORE0019 | Key {0} is invalid. |
Explanation |
The specified key {0} is invalid. |
Action |
Specify a valid key, followed by a valid contract item identifier (for example, item=<contractItemIdentifier>). |
CCECORE0020 | Contract item identifier {0} is invalid. |
Explanation |
The specified contract item identifier {0} is invalid. |
Action |
Specify a valid contract item identifier (for example, item=<contractItemIdentifier>). You can find the valid contract item identifiers using the following command: cc list license-tools manifests contracts basepeak <nodeAlias> <productId> |
CCECORE0021 | One contract item identifier expected. |
Explanation |
Command Central expects one contract item identifier. |
Action |
Specify one valid contract item identifier. |
CCECORE0022 | Could not retrieve Version of node {0}. |
Explanation |
The error usually occurs because of issues connecting to node {0}. |
Action |
Check the logs for details about the connectivity issues. |
CCECORE0023 | Cannot add contract item identifier assignment for runtime components with base and peak license key. |
Explanation |
Command Central cannot add the manual contract item identifier assignment if the runtime component has a base and peak license key. |
Action |
Specify contract item idenfiers only for runtime components without base and peak license key. |
CCECORE0025 | {0} did not get {1} for {2} seconds! |
Explanation |
The specified node did not reach the expected status in the given amount of time. |
Action |
Retry the operation or contact SoftwareAG Global Support. |
CCECORE0026 | {0} did not get {1} for {2} seconds! |
Explanation |
The specified node did not reach the expected status in the given amount of time. |
Action |
Retry the operation or contact SoftwareAG Global Support. |
CCECORE0027 | A node with the specified alias does not exist. |
Explanation |
An installation (node) with the specified alias name does not exist. |
Action |
Specify a valid alias name for an existing installation (node). |
CCECORE0028 | A runtime component with the specified id does not exist. |
Explanation |
A runtime component with the specified ID does not exist on the node(s). |
Action |
Specify an ID of an existing runtime component. |
CCECORE0029 | Cache update operation failed. |
Explanation |
One of the automatic cache update operations failed to complete. |
Action |
Check the logs for details. |
CCECORE0030 | Unknown cahce type: {0}. EventListener was not added because the required cache could not be created. |
Explanation |
Ehcache is not configured properly. |
Action |
Contact Software AG global support. |
CCECORE0031 | Unknown cahce type: {0}. EventListener was not removed because the required cache could not be created. |
Explanation |
Ehcache is not configured properly. |
Action |
Contact Software AG global support. |
CCECORE0032 | Invalid settings format: {0} |
Explanation |
The format of the settings is as follows: key:value[;key:value]... |
Action |
Make sure that the settings comply with the specified format. |
CCECORE0033 | Invalid value for period: {0} |
Explanation |
The value for period must match the following pattern \d+h|m. Examples: 9m, 3h, 45m, 12h |
Action |
Make sure the period value complies with the specified format. |
CCECPTE0000 | Invalid composite template alias: {0} |
Explanation |
The composite template alias is not present or contains special characters. |
Action |
Specify a composite template alias. The template alias can include the following characters: letters, digits, hyphen and dot. |
CCECPTE0001 | A composite template with alias {0} already exists. |
Explanation |
A composite template with the specidied alias already exists. |
Action |
Change the alias of the composite template that is being imported or delete the existing composite template that has the same alias. |
CCECPTE0002 | Missing property {0}. |
Explanation |
A property is missing from the composite template definition. |
Action |
Add the missing property with a proper value. |
CCECPTE0003 | Invalid value {0} for property {1}. |
Explanation |
A property has an invalid value. |
Action |
Provide a proper value as described in the Command Central documentation. |
CCECPTE0004 | A composite template with alias {0} does not exist. |
Explanation |
A composite template with the specified alias does not exist. |
Action |
Import a composite template with the specified alias or use the alias of an existing composite template. |
CCECPTE0005 | The requested repository version {0} was not found. |
Explanation |
The requested repository version was not found. |
Action |
Provide an existing repository version or specify an image file location if the repository is of type image. |
CCECPTE0006 | Invalid repository definition. |
Explanation |
An invalid combination of properties was specified. |
Action |
See the Command Central documentation on how to define a repository. |
CCECPTE0007 | The repository definition cannot have both version and location. |
Explanation |
In the repository definition, the specified location defines that this is an image repository. However, a version cannot be specified for an image repository. |
Action |
Fix the repository definition. If it is an image repository, specify only a location. Otherwise, remove the location and specify proper credentials. |
CCECPTE0008 | Cannot have both credentials and location in repository definition. |
Explanation |
In the repository definition, location defines that this is an image repository. However, you cannot specify credentials for an image repository. |
Action |
Fix the repository definition. If the repository is an image repository, specify a location. If the repository is a master repository, remove the location and specify proper credentials. |
CCECPTE0015 | The runtime status of runtime component {0} on node {1} is not online. |
Explanation |
The runtime component has a status different than online. |
Action |
Check the logs on the node for issues which may cause the behavior. |
CCECPTE0016 | The {0} lifecycle job of a runtime component on node {1} did not complete successfully. |
Explanation |
The lifecycle job of a runtime component on a node did not complete successfully. |
Action |
Check the jobs on the node. |
CCECPTE0017 | Define layers when there is a provisioning section. |
Explanation |
Provisioning requires layers to be defined. |
Action |
Define a layers section. |
CCECPTE0018 | Provisioning requires layer {0} however a layer is not defined. |
Explanation |
All layers defined in the provisioning section should be defined in the layers section. |
Action |
Fix the layers section by adding the missing layers or change the provisioning section to not include layers. |
CCECPTE0019 | Invalid layer alias: {0} |
Explanation |
The layer alias is not present or contains special characters. |
Action |
Provide a layer alias. The layer alias can contain the following characters: letters, digits, hyphen and dot. |
CCECPTE0020 | Invalid template alias: {0} |
Explanation |
The template alias is not present or contains special characters. |
Action |
Provide a layer alias. The layer alias can contain the following characters: letters, digits, hyphen and dot. |
CCECPTE0021 | Repository with name {0} is already defined. |
Explanation |
A repository with the same name is already defined in the YAML document. |
Action |
Change the name of the repository, so that the name is unique in the scope of the document. |
CCECPTE0022 | The maximum number of retries for applying template {0} on node {1} due to possible Platform Manager restarts is reached. |
Explanation |
The maximum number of retries for applying a template on a node due to possible Platform Manager restarts is reached. |
Action |
Check the logs for details about previous attempts to apply the template to determine what the issues are. |
CCECPTE0023 | {0} did not get {1} for {2} seconds! |
Explanation |
The specified node did not reach the expected status in the given amount of time. |
Action |
Retry the operation or contact SoftwareAG Global Support. |
CCECPTE0024 | Can not find any repository matching the provided host and name. |
Explanation |
Command Central does not find a repository matching the specified host and name. |
Action |
Specify valid host and name. |
CCECPTE0025 | Snapshot template {0} not found! |
Explanation |
The snapshot template referred from the composite template cannot be found. |
Action |
Import a snapshot template with the specified alias and re-apply the composite template. |
CCECPTE0027 | Server action {0} failed with a non-zero exit code: {1} |
Explanation |
An action executing on the CommandCentral server failed. |
Action |
Make sure the action itself is correct and try again. |
CCECPTE0032 | The jar command executable cannot be found on the source node installation. |
Explanation |
The jar command executable cannot be found on the source node installation. |
Action |
Check the composite template logs. |
CCECPTE0038 | Remote action {0} failed with a non-zero exit code: {1} |
Explanation |
An action executing remotely failed. |
Action |
Make sure the action itself is correct and try again. |
CCECPTE0039 | Neither script nor file exist for action: {0}! |
Explanation |
An action must have either a script, or a file associated with it. |
Action |
Add a script or file and try again. |
CCECPTE0040 | The runtime status of runtime component {0} on node {1} is not paused. |
Explanation |
The runtime component has a status other than paused. |
Action |
Check the logs on the node for issues which may cause the behavior. |
CCECPTE0041 | Environment {0} is not defined in 'provision'! |
Explanation |
The environments in the 'provision' and 'migration' sections do not match. |
Action |
Make sure the same set of environments is present in both the 'provision' and 'migration' sections and try again. |
CCECPTE0042 | Layer {0} referenced in 'migration' but not in 'provision'! |
Explanation |
The layers referenced in the 'provision' and 'migration' sections do not match. |
Action |
Make sure the same set of layers are referenced from both the 'provision' and 'migration' sections and try again. |
CCECPTE0043 | The number of nodes for layer {0} in 'migration' and 'provision' don't match! |
Explanation |
The number of nodes for a given layer in the 'migration' section must match the number of nodes for the same layer in the 'provision' section. |
Action |
Make sure the number of nodes per layer is the same across the 'migration' and 'provision' sections and try again. |
CCECPTE0044 | Executing more than one migration type in a single composite template is not supported: {0}, {1}. Check the source and target nodes hostnames and installation directories. |
Explanation |
The composite template contains nodes that should be migrated using different migration type scenarios. This is not supported. |
Action |
Split or parameterize the template so that the migration is done using a single migration type. |
CCECPTE0045 | Error during archiving the migration source node installation directory. |
Explanation |
An error occurred during archiving the migration source node installation directory. |
Action |
Check the logs for the result of the executed remote archive command. |
CCECPTE0046 | Runtime component with id {0} cannot be found. |
Explanation |
Runtime component with the provided ID cannot be found. |
Action |
Check the Command Central logs for inventory service errors. |
CCECPTE0047 | Cannot find node with alias {0} in the list of the bootstrapped migration source nodes: {1}. |
Explanation |
Command Central cannot find the source node with the specified nodeAlias in the list of bootstrapped migration source nodes. |
Action |
Check the logs for previous errors. |
CCECPTE0048 | Aborted because of a migration failure, see the logs for more details. |
Explanation |
The entire composite template operation failed because of a migration error. |
Action |
Check the logs to identify the issue and try again. |
CCECPTE0049 | Cannot skip run-time components stop operation when doing migration on the same host. |
Explanation |
Skipping the run-time components stop operation when doing migration on the same host is not supported. |
Action |
To stop the run-time components, enable the migration/options/shutdown option in the composite template definition. |
CCECPTE0050 | A {0} file could not be found in the imported composite template archive {1}. |
Explanation |
The expected template yaml file could not be found in the imported composite template archive. |
Action |
Provide a valid template archive containing the expected template yaml file. |
CCECPTE0051 | Source backup archive {0} was not found on the Command Central host. |
Explanation |
The backup archive, created from the migration source node, was not found on the Command Central host. |
Action |
Check the logs for previous errors related to the backup archive creation or archive transfer from the source host to the Command Central host. |
CCECPTE0052 | Source backup archive {0} was not found on host {1}. |
Explanation |
The backup archive, created from the migration source node, was not found on the target host. |
Action |
Check the logs for previous errors related to backup archive transfer from the Command Central host to the target host. If the backup was transfered manually then check if its location is the expected by Command Central one. |
CCECPTE0053 | Cygpath command returned empty result. |
Explanation |
The Cygpath command returned empty result. |
Action |
Check the Command Central template logs. |
CCECPTE0054 | Cannot skip run-time components stop operation for node {0} running on Windows when doing migration of type different hosts. |
Explanation |
Skipping the run-time components stop operation when doing migration on different hosts running on Windows is not supported. |
Action |
To stop the run-time components, enable the migration/options/shutdown option in the composite template definition. |
CCECPTE0055 | Unexpected YAML type {0} in field {1}! The correct type is integer. |
Explanation |
Non-integer data was used in a field that requires integer. |
Action |
Use the correct integer value and try again. |
CCECPTE0078 | Composite template validation for {0} completed: {1} |
Explanation |
The validation detected that the compoiste template cannot be applied successfully. |
Action |
Read the validation report, fix the errors and try again. |
CCECPTE0079 | The repository definition should not be empty. |
Explanation |
A repository definition without properties is provided. |
Action |
Read the Command Central help on how to define a repository and provide the required properties. |
CCECPTE0081 | Concrete node mapping or variable expected on {0}! |
Explanation |
An unexpected value was specified. |
Action |
Use a concrete node mapping or variable and try again. |
CCECPTE0083 | Support patches are not allowed in the "fixes" section: {0} |
Explanation |
From DSL version 1.1 and above, support patches are not allowed in the "fixes" section. |
Action |
Move all patches to the "patches" section. |
CCECPTE0084 | Node with alias {0} should be present in the landscape when alias mapping policy is EXISTING. |
Explanation |
The nodes should be already registered in the landscape when alias mapping policy is "EXISTING." |
Action |
Add the node in the Command Central landscape. |
CCECPTE0085 | Unknown node identifier type {0} |
Explanation |
Command Central cannot identify the provided node identifier type. |
Action |
Provide a valid node identifier type. |
CCECPTE0086 | The node host {0} is not part of the infrastructure layer. |
Explanation |
The provided node host is not part of the infrastructure layer. |
Action |
Add the node host to the list of infrastructure layer hosts. |
CCECPTE0087 | Illegal node index value {0}. |
Explanation |
The provided node index value is not valid. |
Action |
Provide a value between 1 and number of nodes in the infrastructure layer. |
CCECPTE0088 | Illegal node index {0} in the node alias {1}. |
Explanation |
The provided node index value in the node alias is not valid. |
Action |
Provide an index value between 1 and the number of nodes in the infrastructure layer. |
CCECPTE0089 | {0} policy cannot be used without having infrastructure layer defined. |
Explanation |
The provided policy cannot be used without having an infrastructure layer defined. |
Action |
Provide an infrastructure layer. |
CCECPTE0090 | Node with index {0} requested while the infrastructure layer has {1} nodes. |
Explanation |
Invalid node index is requested. |
Action |
Provide a node index that corresponds to the layer nodes count. |
CCECPTE0091 | DSL version 1.0 is not compatible with alias mapping policy: {0}. Allowed alias mapping policy: {1}. |
Explanation |
DSL version 1.0 is not compatible with the provided alias mapping policy. |
Action |
Provide a compatible alias mapping policy, or use a DSL version above 1.0. |
CCECPTE0092 | The "patches" section is not allowed for DSL version 1.0. |
Explanation |
The "patches" section is allowed from DSL version 1.1 and above. |
Action |
Either specify the patches in the fixes section or change the DSL version to 1.1 or above. |
CCECPTI0026 | The following runtime components are started but not ready to accept client requests: {0} |
Explanation |
Some runtime components have started, but are not ready to accept client requests. |
Action |
The components might require additional configuration. |
CCECPTI0080 |
CCECPTI0093 | Patches validation |
CCECPTW0030 | Source migration step {0} finished with error: {1} |
Explanation |
The source node migration step finished with an error. |
Action |
Check the logs and identify the error root cause. |
CCECPTW0031 | Skipping source node archive step. Source node installation directory is null. |
Explanation |
Command Central will skip the source node archive step, because the source node installation directory is null. |
Action |
Start Platform Manager on the source node, retrieve the node information on Command Central when Platform Manager gets online. |
CCEIMPE0004 | You cannot update the license location for the configuration type COMMON-LICLOC in Command Central. |
Explanation |
You cannot update the license location for the configuration type COMMON-LICLOC in Command Central. |
Action |
Use the default license location. |
CCEIMPE0005 | You cannot create a license location for the configuration type COMMON-LICLOC in Command Central. |
Explanation |
You cannot create a license location for the configuration type COMMON-LICLOC in Command Central. |
Action |
Use the default license location. |
CCEIMPE0006 | You cannot delete the license location for the configuration type COMMON-LICLOC in Command Central. |
Explanation |
You cannot delete the license location for the configuration type COMMON-LICLOC in Command Central. |
Action |
Use the default license location. |
CCEIMPE0007 | The product version is invalid. |
Explanation |
In Command Central, when the license is created or updated for Command Central Engine, if the product version in license validation does not match the version of the product installed, this error is thrown. |
Action |
Provide a new license file with the product version matching the installed product. |
CCEIMPE0009 | The product code is invalid. |
Explanation |
In Command Central, when the license is created or updated for the Command Central Engine, if the product code does not match the Command Central Engine product code, this error is thrown. |
Action |
Provide a new license file with the product code matching with the Command Central Engine product code. |
CCEIMPE0021 | A layer definition with the same name already exists. |
Explanation |
A layer definition with the same name already exists. |
Action |
Specify a unique name for the layer type. |
CCEIMPE0022 | A micro template with alias {0} does not exist. |
Explanation |
A micro template with the specified alias does not exist. |
Action |
Specify the alias of an existing micro template. |
CCEIMPE0023 | The provided configuration cannot be null. |
Explanation |
The provided configuration cannot be null. |
Action |
Provide non-null layer definition configuration. |
CCEIMPE0024 | Configuration of type CCE-LAYER-TYPES should have a name attribue with a valid id. |
Explanation |
The name attribute of the specified configuration type should have an ID that contains only URL friendly symbols. |
Action |
Provide a URL-friendly ID for the name attribute. |
CCEIMPE0025 | Providing micro template alias is required. |
Explanation |
Specifying the micro template alias is required. |
Action |
Specify the alias of an existing micro template. |
CCEIMPE0026 | Deleting default system layer definition {0} is not allowed. |
Explanation |
Deleting default system layer definition is not allowed. |
Action |
Do not delete the default system layer definitions. |
CCEINME0000 | Fix repository with Id {0} cannot be found. |
Explanation |
The specified repository ID is not the ID of an existing repository. |
Action |
Check the input parameters and specify the ID of an existing repository. |
CCEINME0001 | An error occurred while registering repository {0} on node {1}. Check the server logs for details. |
Explanation |
The issue might occur because of a problem with the repository contents. |
Action |
Check the server logs for details. |
CCEINRE0001 | A node with the specified alias does not exist. |
Explanation |
An installation (node) with the specified alias name does not exist. |
Action |
Specify the valid alias name for an existing installation (node). |
CCEINRE0002 | The specified runtime component is not a process! |
Explanation |
The specified run-time component is not a PROCESS. Run-time components that are in the PROCESS category are components that function on their own. In contrast, run-time components that are in the ENGINE category cannot function on their own, but rather run within a PROCESS run-time component. |
Action |
Specify a PROCESS run-time component. |
CCEJMRE0000 | A job with ID {0} cannot be found. |
Explanation |
A job with the specified ID may have never existed or it may have completed long before this request. |
Action |
Use the following URI to list all jobs that are running or recently completed: /cce/jobmanager/jobs |
CCEJMRE0001 | A node with alias {0} does not exist. |
Explanation |
There is no node with the given alias in the landscape. |
Action |
Add the node to the landscape. |
CCEJMRE0002 | A job with ID {0} on node {1} cannot be found. |
Explanation |
A job with the specified ID may have never existed or it may have completed long before this request. |
Action |
Use the following URI to list all jobs that are running or recently completed: /cce/jobmanager/landscapejobs/local where "local" is the node alias |
CCELCRE0000 | The lifecycle operation to execute is unknown. |
Explanation |
You specified a lifecycle operation that is not valid. Valid lifecycle operations are start, stop, restart, pause, resume, start in debug mode, and start in safe mode. Note, however, that a run-time component might support only a subset of the valid lifecycle operations. |
Action |
Specify a valid lifecycle operation. |
CCELCYE0003 | Error occured while executing lifecycle operation on a remote managed node with alias {0}. Remote task status is {1} |
Explanation |
Error occured while executing lifecycle operation on a remote managed node. |
Action |
Check the Command Central and target node Platform Manager logs. |
CCELCYE0004 | Error during lifecycle job execution. |
Explanation |
An error occurred during the lifecycle job execution. |
Action |
Check the logs for details about the error. |
CCELCYE0005 | At least one remote call has timed out. |
Explanation |
At least one remote lifecycle execution call has timed out. |
Action |
Check the remote Platform Manager logs for related errors. |
CCELIRE0000 | Error deleting license report with id: {0} |
Explanation |
An unexpected error occurred when trying to delete the License Report with the given ID. |
Action |
Check the report id provided and if valid, check the server log for any exception messages. |
CCELIRE0001 | Error deleting license reports. |
Explanation |
At least one of the license reports was not deleted successfully. |
Action |
Retry the delete operation later or contact Software AG Global Support. |
CCELIRE0003 | Exception while building license report Document, {0}: caught type({1}), msg({2}) |
Explanation |
A problem was encountered while attempting to build a License Report XML document from its string representation. |
Action |
Consult Software AG Global Support. |
CCELIRE0004 | Invalid license manifest file. |
Explanation |
The contents of the specified file is invalid for license manifest files. |
Action |
Specify a valid license manifest file. |
CCELIRE0007 | The specified alias is not valid. |
Explanation |
No additional details. |
Action |
Specify a valid alias. The alias can include up to 100 ASCII characters, numbers, underscore (_), hyphen (-), and period (.). |
CCELIRW0002 | Error deleting the following reports: {0} |
Explanation |
The specified reports could not be deleted successfully. |
Action |
Check the server log for more details and try to delete the reports individually. |
CCELITE0000 | Error generating license report id! |
Explanation |
An error occurred when trying to generate a unique report ID for the license report snapshot. |
Action |
Retry the operation or contact Software AG Global Support. |
CCELITE0001 | Could not find a report with id {0} |
Explanation |
No license report with the specified report ID was found in the system. |
Action |
Check the report ID value and try again. |
CCELITE0002 | Error creating license snapshots directory {0} |
Explanation |
An error occurred when trying to create a filesystem directory to store the license snapshots. |
Action |
Check if there is enough disk space and/or contact Software AG Global Support. |
CCELITE0003 | Unable to get runtime component {0}/{1} caught: {2} |
Explanation |
During license data collection, an attempt to retrieve information about this runtime component failed. The issue may indicate a communication issue between Command Central and Platform Manager. |
Action |
This could be a temporary communications issue. If the problem persists, contact Software AG Global Support. |
CCELITE0004 | Unable to get configuration types for {0}/{1} caught: {2} |
Explanation |
During license data collection, an attempt to retrieve information about this runtime component failed. The issue may indicate a communication issue between Command Central and Platform Manager. |
Action |
This could be a temporary communications issue. If the problem persists, contact Software AG Global Support. |
CCELITE0005 | Unable to get configuration instances for {0}/{1} caught: {2} |
Explanation |
During license data collection, an attempt to retrieve information about this runtime component failed. The issue may indicate a communication issue between Command Central and Platform Manager. |
Action |
This could be a temporary communications issue. If the problem persists, contact Software AG Global Support. |
CCELITE0006 | Unable to get configuration data for {0}/{1}/{2} caught: {3} |
Explanation |
During license data collection, an attempt to retrieve information about this runtime component failed. The issue may indicate a communication issue between Command Central and Platform Manager. |
Action |
This could be a temporary communications issue. If the problem persists, contact Software AG Global Support. |
CCELITE0007 | Found null value for license configuration data for {0}/{1}/{2} |
Explanation |
During license data collection, an attempt to retrieve license information about this runtime component found an invalid license. |
Action |
Contact Software AG Global Support. |
CCELITE0008 | Expected a String value for license configuration data for {0}/{1}/{2}, found type {3} |
Explanation |
During license data collection, an attempt to retrieve license information about this runtime component found an invalid license. |
Action |
Contact Software AG Global Support. |
CCELITE0010 | Checksum verification failed for License Report with id {0} {1}. |
Explanation |
The license report file may be corrupted or been tampered with, which has resulted in an integrity check failure. |
Action |
Regenerate the license report and/or contact Software AG Global Support with the affected license report file. |
CCELITE0011 | Unable to generate and store license snapshot report; caught type: {0}, msg: {1} |
Explanation |
An issue was encountered either when generating, or saving the generated license report snapshot. |
Action |
Check the exception and message to identify the exact cause, or contact Software AG Global Support. |
CCELITE0012 | Unable to generate report, no report generator configured |
Explanation |
The issue occurred because of incorrect component configuration. |
Action |
Check the license report configuration or contact Software AG Global Support. |
CCELITE0013 | Error getting license report! |
Explanation |
An error occurred when trying to retrieve the requested license report. |
Action |
Check the cause and retry the operation. |
CCELITE0014 | Unable to parse license XML for {0}/{1} from string that follows; except msg: {2}. XML: {3} |
Explanation |
The license content retrieved from the Platform Manager could not be parsed. |
Action |
Check the exception message for the exact cause and/or contact Software AG Global Support. The error may occur if a license file is found that is not in a standard Software AG format. |
CCELITE0015 | Error generating pdf report for this reportId ''{0}''. Cause: {1} |
Explanation |
The attempt to transform the XML data failed to produce a PDF data stream. |
Action |
Generate another report and verify whether the XML response is well-formed. |
CCELITE0016 | Error generating pdf license report. No XML data stream available for ''{0}'' |
Explanation |
The license reports module cannot produce a pdf report unless its canonical data is provided. |
Action |
Verify that the pdf generation task was executed properly using an existing report ID. |
CCELITE0017 | Error generating pdf license report. Unable to locate XSLT style sheet for pdf generation. ''{0}'' |
Explanation |
The license tools bundle could not locate the XSLT style used to produce a pdf report. |
Action |
Contact Software AG Global Support. |
CCELITE0018 | Error applying license pdf report stylesheet ''{0}'' to XML data ''{1}''. Cause: {2} |
Explanation |
Unexpected errors were encountered while generating the license pdf report. |
Action |
Contact Software AG Global Support. |
CCELITE0019 | Unable to serialize a license report data object for ''{0}''. Cause: {1} |
Explanation |
The license report data object could not be serialized as input for pdf report generation. |
Action |
Contact Software AG Global Support. |
CCELITE0020 | Error verifying license report checksum. |
Explanation |
An error occurred when trying to verify the license report checksum when retrieving the report. |
Action |
Retry request later or contact Software AG Global Support. |
CCELITE0022 | Unable to open extended rights table ({0}) |
Explanation |
The indicated value is not available. |
Action |
Contact Software AG Global Support. |
CCELITE0023 | Unable to load extended rights properties from {0}; caught: type({1}). message({2}) |
Explanation |
A problem was encountered while loading the indicated file into memory. |
Action |
Contact Software AG Global Support. |
CCELITE0024 | Unable to close input stream from {0}; caught: type({1}). message({2}) |
Explanation |
A problem was encountered while cleaning up after loading the indicated file into memory. |
Action |
Contact Software AG Global Support. |
CCELITE0026 | License manifest is already stored. |
Explanation |
The license manifest is already been stored with alias {0}. |
Action |
Specify a different license manifest. |
CCELITE0027 | Unable to store license manifest "{0}"; caught type: {1}, msg: {2} |
Explanation |
An issue was encountered when storing a license manifest. |
Action |
Check the exception and message to identify the exact cause, or contact Software AG Global Support. |
CCELITE0028 | Error creating storage location {0} for license manifests. |
Explanation |
An error occurred when trying to create a filesystem directory to store license manifests. |
Action |
Check access rights and disk space or contact Software AG Global Support. |
CCELITE0029 | Error retrieving license manifests. |
Explanation |
An error occurred when trying to retrieve the list of stored license manifests. |
Action |
Check the cause and retry the operation. |
CCELITE0030 | Could not find a license manifest with alias {0} |
Explanation |
No license manifest with the specified alias was found in the system. |
Action |
Check the license manifest alias value and try again. |
CCELITE0031 | Invalid license manifest. |
Explanation |
The specified file is not a valid license manifest. |
Action |
Specify a valid license manifest. |
CCELITE0032 | Checksum verification failed for LicenseMeteringConfiguration.xml file. |
Explanation |
The LicenseMeteringConfiguration.xml file which is delivered with the CCE installation is either corrupted, or modified. |
Action |
Contact Software AG Global Support to get a valid LicenseMeteringConfiguration.xml file. |
CCELITE0034 | Alias "{0}" already exists. |
Explanation |
A license manifest with the specified alias already exists. |
Action |
Specify a new alias for the license manifest. |
CCELITE0035 | License manifest alias missing. |
Explanation |
No license manifest alias has been specified. |
Action |
Specify a valid license manifest alias. |
CCELITE0036 | Deleting license manifest with alias "{0}" failed. |
Explanation |
An error occured while trying to delete the license manifest with the specified alias. |
Action |
Check the exception and message to identify the exact cause, or contact Software AG Global Support. |
CCELITE0037 | Deleting license manifests failed. |
Explanation |
An error occured while trying to delete the license manifests. |
Action |
Check the exception and message to identify the exact cause, or contact Software AG Global Support. |
CCELITE0042 | Invalid processor core class {0}. |
Explanation |
The specified processor core class is not valid. |
Action |
Specify a valid processor core class. |
CCELITE0046 | Checksum verification failed for the given License Manifest. |
Explanation |
The license manifest file is corrupted or been tampered with, which has resulted in an integrity check failure. |
Action |
Use original license manifest file from Software AG and/or contact Software AG Global Support with the affected license manifest file. |
CCELITE0047 | Cannot open license metering configuration file. |
Explanation |
The license metering configuration file could not be read. |
Action |
Contact Software AG support. |
CCELITE0048 | Updating {0} cache for node {1} failed. |
Explanation |
Updating the cache failed. The license metering report may contain invalid data. |
Action |
Contact Software AG support. |
CCELITE0049 | Processor core class is not available. Product cannot be checked. |
Explanation |
The Platform Manager where the product is installed did not provide the processor core class the node is running on. |
Action |
Contact Software AG Global Support. |
CCELITE0050 | Cannot find runtime status: {0} |
Explanation |
The run-time status of the current landscape XML file was not found. |
Action |
Provide a valid landscape XML file. |
CCELITE0051 | Cannot store license metering configuration data to file. |
Explanation |
An error occured while writing the license metering configuration data to a new file. |
Action |
Contact Software AG Global Support. |
CCELITE0053 | Platform Manager with version {0} is not sufficient for the license metering. Version 9.8 or higher is required. |
Explanation |
The version of the Platform Manager is {0}. Platform Manager version of 9.8 or higher is required for the license metering. |
Action |
Update the Platform Manager with version 9.8 or higher. |
CCELITE0054 | Consolidation of License Manifests failed. |
Explanation |
An error occurred during the consolidation of the license manifests. |
Action |
Contact Software AG support. |
CCELITE0055 | Collecting server details information failed. |
Explanation |
An error occurred during the collection of server details information. |
Action |
Contact Software AG support. |
CCELITE0056 | Generating license report compliance result failed. |
Explanation |
An error occurred during the generation of the license report compliance result. |
Action |
Contact Software AG Global Support. |
CCELITE0057 | License manifest for referenced location id {0} not found. |
Explanation |
The license manifest for the location id {0} has been removed. |
Action |
Add the license manifest for the location id {0} to Command Central or assign a different location id to the installation details in the landscape overview tab. |
CCELITE0058 | Unable to retrieve Command Central port number. |
Explanation |
An error occured while trying to retrieve the port number of Command Central. |
Action |
Ensure that the Plaform Manager that belongs to this Command Central installation is running. |
CCELITE0059 | The license metering cannot be stopped, because metering is required. |
Explanation |
One of the active license manifests contains a product for which license metering is required, so that it is not possible to stop the metering. |
Action |
Remove the license manifest that requires metering or keep license metering running. |
CCELITE0060 | No node alias specified. |
Explanation |
The alias of a node was not specified. |
Action |
Specify a valid node alias. The available node aliases can be determined from the landscape configuration. |
CCELITE0061 | No product id specified. |
Explanation |
The ID of the product for which contracts are to be retrieved is not specified. |
Action |
Specify a valid product ID. The available product IDs can be determined from the landscape configuration. |
CCELITE0062 | Node alias {0} is invalid. |
Explanation |
A node with the specified alias {0} is not registered in Command Central. |
Action |
Specify a valid node alias. The available node aliases can be determined from the landscape configuration. |
CCELITE0063 | No server details found for node with alias {0}. |
Explanation |
The server details could not be determined for the node with the specified alias {0}. |
Action |
Make sure that the Platform Manager on the node with the specified alias is running. |
CCELITE0064 | No product with id {0} found on node with alias {1}. |
Explanation |
There is no product with the specified ID {0} installed on the node with the specified alias {1}. |
Action |
Specify the ID of a product that is installed on the node with the specified alias. The available product IDs can be determined from the landscape configuration. |
CCELITE0065 | Platform Manager on node with alias {0} is not running. |
Explanation |
The Platform Manager on the node with alias {0} is not running. |
Action |
Start Platform Manager on the node with alias {0} and execute the command again. |
CCELITE0068 | Version {0} of license manifest is not supported. Highest supported version is {1}. |
Explanation |
The version {0} of the specified license manifest is higher than the version {1} currently supported. |
Action |
Update Command Central to a version that supports the version of the specified license manifest. |
CCELITE0069 | Version {0} of license report is not supported. Highest supported version is {1}. |
Explanation |
The version {0} of the specified license report is higher than the version {1} currently supported. |
Action |
Update Command Central to a version that supports the version of the specified license report. |
CCELITE0070 | Aggregated license report with alias {0} already exists. |
Explanation |
An aggregated license report with the alias {0} already exists. |
Action |
Specify an aggregated license report with a different alias. |
CCELITE0071 | Alias {0} already exists. |
Explanation |
A license key with the specified alias {0} already exists. |
Action |
Specify a different alias. |
CCELITE0072 | ProductCode and productId specified. |
Explanation |
You must specify either productCode or productId. |
Action |
Remove either productCode or productId. |
CCELITE0073 | Platform and OS specified. |
Explanation |
You must specify either platform, or operating system. |
Action |
Remove either the platform or the operating system. |
CCELITE0074 | Invalid platform(s) {0} specified. |
Explanation |
The specified platform(s) {0} is invalid. |
Action |
Specify valid platform(s). |
CCELITE0075 | Specified installationType {0} is invalid |
Explanation |
The specified installationType {0} is invalid. |
Action |
Specify a valid installationType. |
CCELITE0076 | Invalid productCode {0} specified. |
Explanation |
The specified productCode {0} is invalid. |
Action |
Specify a valid productCode. |
CCELITE0077 | Invalid productId {0} specified. |
Explanation |
The specified productId {0} is invalid. |
Action |
Specify a valid productId. |
CCELITE0078 | Invalid os {0} specified. |
Explanation |
The specified OS {0} is invalid. |
Action |
Specify valid OS. |
CCELITE0080 | Specified licenseKeyType {0} is invalid. |
Explanation |
The specified licenseKeyType {0} is invalid. |
Action |
Specify a valid licenseKeyType. |
CCELITE0081 | Error verifying landscape checksum. |
Explanation |
An error occurred when trying to verify the landscape checksum. |
Action |
Contact Software AG Global Support. |
CCELITE0082 | Invalid license key. |
Explanation |
The specified file is not a valid license key. A valid license key must not contain binary data or be empty. |
Action |
Specify a valid license key. |
CCELITE0083 | Invalid license key: {0}. |
Explanation |
Specified file is not a valid license key. |
Action |
Specify a valid license key. |
CCELITE0084 | A node with the specified alias does not exist. |
Explanation |
An installation (node) with the specified alias name does not exist. |
Action |
Specify a valid alias name for an existing installation (node). |
CCELITE0085 | A run-time component with the specified id does not exist. |
Explanation |
A run-time component with the specified ID does not exist on the node(s). |
Action |
Specify an ID of an existing runtime component. |
CCELITE0090 | Invalid productCode {0} and productId {1} specified. |
Explanation |
The specified productCode {0} and productId {1} is invalid. |
Action |
Specify a valid productCode and productId. |
CCELITE0091 | Unexpected exception occurred: {0} |
Explanation |
An unexpected exception occurred: {0} |
Action |
Contact Software AG support. |
CCELITE0092 | Failed to update server time stamp for server {0} : {1} |
Explanation |
Failed to update server time stamp for server {0} : {1} |
Action |
Make sure the Platform Manager on server {0} is running. |
CCELITE0093 | Error creating URL from urlString {0}. |
Explanation |
Error creating URL from urlString {0}. |
Action |
Specifiy a valid URL. |
CCELITE0094 | License key with specified alias {0} not found. |
Explanation |
A license key with the specified alias {0} is not stored in the license key manager. |
Action |
Specify the alias of a stored license key. |
CCELITE0102 | Alias must be specified for custom license keys. |
Explanation |
You must specify an alias when adding a custom license key. |
Action |
Specify a license key alias. |
CCELITE0105 | Invalid license key archive. |
Explanation |
The specified file is not a valid license key archive. A valid license key archive must contain license keys. |
Action |
Specify a valid license key archive. |
CCELITE0106 | License key already stored with alias {0}. |
Explanation |
This license key is already stored with alias {0}. |
Action |
Specify another license key, or add the license key with a different alias. |
CCELITE0107 | Licensing data is not available because the cache is not accessible. |
Explanation |
All license metering data, like license keys, license reports, and license manifests, is stored in the cache, which is currently inaccessible. |
Action |
This problem can occur if the machine is slow. Ensure that the machine has enough resources and try it again. |
CCELITI0033 | Type of installation is not defined. Product cannot be checked. |
Explanation |
The Platform Manager where the product is installed does not have a type of installation (Development, Production, Test) defined. |
Action |
Define a type of installation for your Platform Manager. |
CCELITI0038 | Product is not found in the license manifest(s). |
Explanation |
You have no valid license for the installed product. |
Action |
Contact Software AG for licensing your product. |
CCELITI0039 | Core class does not match: {0} is installed, {1} is licensed. |
Explanation |
The core class of the Plarform Manager server does not match the licensed core class. |
Action |
Contact Software AG Global Support for licensing a higher core class. |
CCELITI0040 | License capacity does not match: {0} {1} used, {2} {1} licensed. |
Explanation |
The number of units used does not match the licensed number of units. |
Action |
Contact Software AG Global Support for licensing a higher number of units. |
CCELITI0043 | Installation type does not match: {0} is installed, {1} is licensed. |
Explanation |
The installation type of the Platform Manager server does not match the licensed installation type. |
Action |
Contact Software AG Global Support for licensing the appropriate installation type. |
CCELITW0021 | Unable to translate extended rights code ({0}), not found |
Explanation |
The table used to look up license Extended Rights codes does not contain the indicated value. |
Action |
Contact Software AG Global Support. |
CCELITW0025 | LicenseReportFactory - unable to determine runtime status for component ({0}) on node ({1}); caught this: type({2}), msg({3}) |
Explanation |
Command Central can not determine if the identified component is up or down. |
Action |
This behavior could occur when the Platform Manager node is down, or because of some other communication issue. If this problem persists when the Platform Manager node is up, contact Software AG Global support. |
CCELNDE0000 | The node alias is invalid. |
Explanation |
An installation (node) with the specified alias name does not exist. |
Action |
Specify the valid alias name for an existing installation (node). |
CCELNDE0001 | "{0}" Run-time component is not found on node "{1}". |
Explanation |
The Landscape Inventory cache does not contain run-time component "{0}" for node "{1}". |
Action |
Use a combination of an existing run-time component Id and node alias or refresh the Landscape Inventory run-time component cache and try again. |
CCELNDE0002 | Invalid node alias or url. |
Explanation |
The specified alias name or URL for an installation (node) is not valid. |
Action |
Specify a valid alias name or URL. |
CCELNDE0003 | Specify a valid URL. |
Explanation |
The URL field in NodeInfo contains an invalid value. |
Action |
Check if the URL syntax of the node is valid. |
CCELNDE0004 | A node with a different alias for the same host:port already exist. |
Explanation |
An installation (node) with a different alias name already exists for the installation with the specified host name and port number. |
Action |
None. |
CCELNDE0006 | Node {0} could not be created. |
Explanation |
A node with alias {0} could not be created because another node with alias {1} already exists. |
Action |
Provide a different alias for the new node. |
CCELNDE0008 | Can not retrieve node's product information for {0} |
Explanation |
Command Central can not connect to Platform Manager to retrieve Platform Manager product information. |
Action |
Make sure the node is online. |
CCELNDE0009 | Can not update inventory cache because of failure during retrieval of remote inventory items. |
Explanation |
The remote request for inventory items failed and the inventory cache can not be updated. |
Action |
Ensure that the node in the request is active or the target node inventory is responsive. |
CCELNDE0010 | The node alias cannot be empty or longer than 100 characters. |
Explanation |
The specified node alias is incorrect, either because the node alias is empty, or it exceeds 100 characters. |
Action |
Specify a correct node alias and try again. |
CCELNDE0011 | The host name should be between 2 and 253 characters long. |
Explanation |
The host name is incorrect, because it is shorter or longer than the specified character length limitations. |
Action |
Provide a correct host name and try again. |
CCELNDE0012 | The node display name should not be longer than 100 characters. |
Explanation |
The node display name is incorrect, because it is longer than 100 characters. |
Action |
Specify a correct node display name and try again. |
CCELNDE0013 | Trying to use unavailable NodeInfo element. |
Explanation |
The specified element of type NodeInfo does not exist. |
Action |
Specify a NodeInfo element that is available. |
CCELNDE0014 | Node alias is not valid. Only letters, numbers, -, _ and . are allowed. |
Explanation |
The specified node alias is incorrect, because it uses special characters that are not allowed. |
Action |
Specify a correct node alias and try again. |
CCELNDI0005 | You have exhausted the number of licensed nodes that can be configured. To add more nodes, contact your system administrator or Software AG support to get the license upgraded. |
Explanation |
You have exhausted the number of licensed nodes that can be configured. |
Action |
To add more nodes, contact your system administrator or Software AG support to get the license upgraded. |
CCELSRE0001 | The node alias cannot be updated. |
Explanation |
You cannot update the alias name for an installation (node). |
Action |
Create a new installation or update the existing installation without changing the alias name. |
CCELSRE0002 | The environment alias cannot be updated. |
Explanation |
You cannot change the alias name of an environment. |
Action |
Create a new environment or update the existing environment without changing the alias name. |
CCELSRE0004 | Node Aliases not specified! |
Explanation |
To add installations (nodes) to an environment, you must specify the alias names of the installations that you want to add. |
Action |
Try again, this time specifying the installation (node) alias names as query parameters. |
CCELSRE0005 | Alias not specified or invalid. |
Explanation |
The environment could not be created or updated because the alias is invalid. |
Action |
Specify a valid alias. You can view a list of installations and theiraliases using the following command: cc list landscape nodes |
CCELSRE0006 | Node {0} could not be created. |
Explanation |
A node with alias {0} could not be created because another node with alias {1} already exists. |
Action |
Provide a different alias for the new node. |
CCELSRE0007 | Environment {0} could not be created. |
Explanation |
An environment with alias {0} could not be created because another environment with alias {1} already exists. |
Action |
Provide a different alias for the new environment. |
CCELSRE0008 | Trying to use unavailable NodeInfo element. |
Explanation |
Trying to use element of type NodeInfo that doesn't exist. |
Action |
Provide an available NodeInfo element. |
CCELSRE0012 | Alias not specified. |
Explanation |
The node could not be created because the alias is missing. |
Action |
Specify a valid alias. |
CCELSRE0013 | Node {0} could not be created. |
Explanation |
A node with alias {0} could not be created because the specified location id {1} does not exist. |
Action |
Provide an existing location id. Available location id(s): {2} |
CCELSRE0014 | Node {0} could not be updated. |
Explanation |
A node with alias {0} could not be updated because the specified location id {1} does not exist. |
Action |
Provide an existing location id. Available location id(s): {2} |
CCELSRE0015 | Node {0} could not be created. |
Explanation |
A node with alias {0} could not be created because the specified installation type {1} is invalid. |
Action |
Provide a valid installation type. Valid installation types are: {2} |
CCELSRE0016 | Node {0} could not be updated. |
Explanation |
A node with alias {0} could not be updated because the specified installation type {1} is invalid. |
Action |
Provide a valid installation type. Valid installation types are: {2} |
CCELSRI0000 | A node with the specified alias does not exist. |
Explanation |
No node alias matches {0} |
Action |
Provide a valid node alias. |
CCELSRI0003 | The environment with the provided alias doesn't exist. |
Explanation |
An environment with the specified alias name does not exist. |
Action |
Specify the valid alias name of an existing environment. |
CCEMIGE0019 | Extracting source version failed. |
Explanation |
Command Central failed to extract the source version from the bundles.info file. |
Action |
Ensure that the bundles.info file is at the correct location. |
CCEMONE0001 | {0} on {1} ({2}) became unresponsive. Component restart may help to resolve this quickly. |
Explanation |
{0} on {1} ({2}) became unresponsive. |
Action |
Component restart may help to resolve this quickly. |
CCEMONE0002 | {0} on {1} ({2}) failed. You will need to start it again and investigate the cause of the failure. |
Explanation |
RuntimeStatus of {0} went from "ONLINE" to "FAILED." |
Action |
Try to restart the operation. Have a look at {1} ({2}) for additional information about its status. |
CCEMONE0006 | {0} of {1} on {2} ({3}) spiked into critical zone. The component may become overloaded! |
Explanation |
The kpi {0} of {1} went from MARGINAL into CRITICAL status. |
Action |
Please have a look on {2} ({3}) to find out why this is happening. |
CCEMONE0011 | Node with alias {0} does not exist. |
Explanation |
There is no node with the specified alias registered with Command Central. |
Action |
Ensure that the node alias is spelled correctly and that it is registered with Command Central. |
CCEMONE0012 | No runtime monitoring information could be found for component {0}. |
Explanation |
The landscape nodes do not have monitoring information for the specified component. |
Action |
Check the landscape nodes for the for the specified component. Ensure that the specified component exists on the nodes and that it is spelled correctly. |
CCEMONE0013 | Component {0} does not exist on node {1}. |
Explanation |
The specified runtime component does not exist on the specified SPM node. |
Action |
Ensure that the specified component is spelled correctly and exists on the specified node. |
CCEMONE0014 | Removing alert with id {0} failed. |
Explanation |
The specified alert could not be found. |
Action |
Ensure that the alert with the specified ID exists in the Command Central landscape. |
CCEMONE0015 | Error getting runtime component {0} for node {1} |
Explanation |
Runtime component {0} is not available in cache. |
Action |
Try to update the inventory cache and make sure the node in the request is active and the target node inventory is responsive. |
CCEMONE0016 | includeChildren parameter requires NodeAlias and RuntimeComponentId to be provided. |
Explanation |
The <includeChildren> parameter requires the <nodeAlias> and <runtimeComponentId> parameters to be provided. |
Action |
Provide values for the <nodeAlias> and <runtimeComponentId> parameters. |
CCEMONE0017 | Alerts filtering requires both NodeAlias and RuntimeComponentId. |
Explanation |
The filtering of alerts requires both <NodeAlias> and <RuntimeComponentId> parameters to be provided. |
Action |
Provide values for both <NodeAlias> and <RuntimeComponentId> parameters. |
CCEMONE0018 | Error while handling event [{0}]. |
Explanation |
There was an error while handling an event. |
Action |
Check the logs for previous errors. |
CCEMONE0019 | Error polling SPM node [{0}]. |
Explanation |
The monitoring states for a runtime component on a target node could not be retrieved. |
Action |
Check the logs for previous errors. |
CCEMONE0020 | Error during retrieving of monitoring state of {0} on node {1}. |
Explanation |
The monitoring state for a runtime component on a target node could not be retrieved. |
Action |
Check the logs for previous errors. |
CCEMONE0021 | Error polling SPM node [{0}]. Node Status will be set to {1} and the Runtime State for all instances of the node will be set to {2}. |
Explanation |
The monitoring states on a target node could not be retrieved and as a result all states will be set to unknown. |
Action |
Check the logs for previous errors. |
CCEMONE0022 | Could not retrieve Cache. Monitoring stopped. |
Explanation |
The Command Central cache manager could not be retrieved. |
Action |
Contact Software AG Global Support. |
CCEPROE0000 | No node with alias, {0}, exists in the environment. |
Explanation |
The node alias specified in the request does not exist. |
Action |
Resubmit the request with an existing node alias. |
CCEPROE0001 | No artifacts specified in uninstall request. |
Explanation |
The uninstall request did not specify any artifacts. |
Action |
Resubmit the request with a list of valid artifacts. |
CCEPROE0002 | {0} is an invalid/unsupported type for artifacts. |
Explanation |
Only Product and Fix are valid artifact types. |
Action |
Resubmit the request with valid artifacts. |
CCEPROE0003 | {0} MASTER repository configuration is invalid. |
Explanation |
The repository configuration misses the location URL. |
Action |
Remove and add this repository again to ensure it has valid remote location URL. |
CCEPROE0004 | {0} repository is not configured with user credentials. |
Explanation |
The repository configuration misses username property value. Most likely the repository was not configured with the required user credentials after it was discovered. |
Action |
Configure the repository with valid user credentials. |
CCEPROE0005 | {0} repository is not configured with user credentials. |
Explanation |
The repository configuration misses the username property value. Most likely the repository was not configured with the required user credentials after it was discovered. |
Action |
Configure the repository with valid user credentials. |
CCEPROE0006 | {0} IMAGE repository configuration is invalid. |
Explanation |
The repository configuration misses the image file location. |
Action |
Edit this repository to ensure it has a valid image location. |
CCEPROE0007 | Node {0} is already registred and reports ONLINE status. |
Explanation |
The node that you are attempting to bootstrap already reports ONLINE status. Most likely you specified a node that is already setup and ready to use. |
Action |
Use a node alias for a Platform Manager that is not running yet. It can be a node that is already registered but does not have a backing Platform Manager, or a completely new node alias that will be added to the landscape when the Platform Manager bootstrap operation is finished. |
CCEPROE0008 | Repository {0} type is not a MASTER repository. |
Explanation |
Bootstrap images can be generated only from a MASTER PRODUCT repository. Other types are not supported. |
Action |
Specify a configured MASTER PRODUCT repository with valid user credentials and try again. |
CCEPROE0009 | Repository {0} is not configured with a user password. |
Explanation |
MASTER repositories require configuration of user credentials. |
Action |
Ensure that the selected repository is configured with a valid username and password. |
CCEPROE0010 | Target machine platform is not specified. |
Explanation |
The bootstrap operation requires the target platform to be explicitely defined. |
Action |
Select platform of the target machine that Platform Manager will be installed |
CCEPROE0011 | Cannot match requested version {0} to any of the configured repositories. |
Explanation |
The version you requested to install does not match the available repositories. |
Action |
Select a specific repository or add new repositories that will match the version you requested. |
CCEPROE0012 | No PRODUCT repositories are defined to complete the operation. |
Explanation |
You did not explicitly specify a repository or version to use and Command Central cannot automatically pick a repository. |
Action |
Ensure that you have configured a PRODUCT repository that contains the required version of Platform Manager. |
CCEPROE0013 | Remote machine credentials are not provided. |
Explanation |
Command Central cannot connect to a remove machine without valid user credentials. |
Action |
Provide user credentials for the remote machine on which you are installing Platform Manager. |
CCEPROE0014 | Error while retrieving configuration. |
Explanation |
Internal error while retrieving common proxy configuration. |
Action |
Make sure COMMON-PROXY configuration exists. |
CCEPROE0015 | Remote access service returned {0} jobs while 1 was expected. |
Explanation |
Only one remote operation was initiated but a different amount of jobs was returned. |
Action |
Contact Software AG Global Support. |
CCEPROE0016 | Java not found on {0}. |
Explanation |
The Java Runtime Environment is not available on the given node. |
Action |
Install Java Runtime Environment and try again. |
CCEPROE0017 | Remote command returned a non-zero exit code: {0} |
Explanation |
The remote installer command failed. Check the logs for more information. |
Action |
Re-try the operation. If the problem persists, contact Software AG Global Support. |
CCEPROE0018 | Can not connect to Platform Manager running on host {0} and port {1} due to wrong credentials. |
Explanation |
Can not connect to Platform Manager due to wrong credentials. |
Action |
Provide valid Platform Manager credentials. |
CCEPROE0026 | The nodeAlias field is required for each node that is added. |
Explanation |
Node alias is required field for each node that is added. |
Action |
Provide node alias. |
CCEPROE0027 | The hostname field is required for each node that is added. |
Explanation |
A hostname is required field for each node that is added. |
Action |
Provide a hostname. |
CCEPROE0028 | Platform Manager port is required field for each node that is added. |
Explanation |
A Platform Manager port is required field for each node that is added. |
Action |
Provide a port field value. |
CCEPROE0029 | Platform Manager nodes are available, but the provided credentials for them are wrong: {0} |
Explanation |
Platform Manager nodes are available, but the provided credentials for them are incorrect. |
Action |
Provide valid credentials for the Platform Manager nodes. |
CCEPROE0030 | The Platform Managers are not remotely accessible: {0} |
Explanation |
The specified Platform Managers are not remotely accessible. |
Action |
Check the connectivity and the remote accessibility to the Platform Managers. |
CCEPROE0034 | Error occured while installing {2} on node {0}. Remote task status is {1} |
Explanation |
The selected artifact was not installed on the remotely managed node. |
Action |
Check the error logs for more details about this error. |
CCEPROE0038 | The maximum number of retries for installing artifacts from repository {0} on node {1} due to possible Platform Manager restarts is reached. |
Explanation |
The maximum number of retries for installing artifacts from repository {0} on node {1} due to possible Platform Manager restarts is reached. |
Action |
Check the logs for details about previous attempts to install artifacts to determine what the issues are. |
CCEPROE0042 | The maximum number of retries for uninstalling artifacts on node {0} due to possible Platform Manager restarts is reached. |
Explanation |
The maximum number of retries for uninstalling artifacts on node {0} due to possible Platform Manager restarts is reached. |
Action |
Check the logs for details about previous attempts to install artifacts to determine what the issues are. |
CCEPROE0043 | Creating an image with name {0} failed. |
Explanation |
Creating an image from a mirror repository that is not on the local Platform Manager is not supported. |
Action |
Create a mirror repository on the local Platform Manager node and use it for bootstrapping. |
CCEPROE0044 | Bootstrapping Platform Manager on installation with alias {0} failed. |
Explanation |
The export of artifacts from a mirror repository with name {0} into image with name {1} failed. |
Action |
See the Platform Manager logs for more information. |
CCEPROE0046 | Bootstrap installer {0} not found. |
Explanation |
The bootstrap installer file was not found under install_dir/profiles/CCE/data/installers |
Action |
Make sure the specified bootstrap installer file is in the correct location. |
CCEPROE0047 | unzip command not found on {0} |
Explanation |
The unzip package is not present in your cygwin environment. |
Action |
Install unzip in your cygwin environment and try again. |
CCEPROE0048 | Local bootstrap completed with exit code: {0} |
Explanation |
The execution of the bootstrap operation failed unexpectedly. |
Action |
Check the bootstrap logs for more information. |
CCEPROE0049 | The installers directory does not exist. |
Explanation |
The directory containing the bootstrap installers does not exist. |
Action |
Create the install_dir/profiles/CCE/data/installers directory. |
CCEPROE0050 | Installer platform mismatch! Expected W64 but found {0}. |
Explanation |
The installation cannot be performed, because the incorrect platform is selected. |
Action |
Select an installer with the correct platform. |
CCEPROE0051 | {0} is not a valid installer directory or it does not exist. |
Explanation |
The bootstrap installer archive may not have been extracted correctly. |
Action |
Retry the operation or contact Software AG global support. |
CCEPROE0052 | Invalid number of Windows scripts in the installer directory: {0} |
Explanation |
The bootstrap installer archive must contain exactly one executable script (batch). |
Action |
Obtain the correct bootstrap installer. |
CCEPROE0055 | Platform Manager nodes are available, but the installation directory is different than requested: {0} |
Explanation |
The Platform Manager nodes are available, but the installation directory is different than requested. |
Action |
Change the installation directory or stop the available Platform Manager if you want to bootstrap a new instance on the same ports. |
CCEPROE0056 | Error occured while uninstalling {2} on node {0}. Remote task status is {1} |
Explanation |
The selected artifact was not uninstalled on the remotely managed node. |
Action |
Check the error logs for more details about this error. |
CCEPROW0045 | The SSH server did not return the exit code of the bootstrap operation. The operation has completed but it is not clear if it was successful or not. |
Explanation |
In some cases the SSH server may not return the exit code of the executed operation. This makes it unclear if the operation was successful or not. |
Action |
Examine the installation logs on the remote node to make sure the installation was successful. |
CCERARE0000 | Not all mandatory parameters are specified. |
Explanation |
Some of the parameters required for this request are missing. |
Action |
Check the Command Central documentation for the required parameters. |
CCERARE0001 | Nothing has been scheduled for execution for this request. |
Explanation |
This request should start jobs for execution, but no jobs have started. |
Action |
Check the logs for errors why the request has not terminated properly. |
CCERARE0002 | Remote Access Service is missing. |
Explanation |
A required service is missing. |
Action |
Check whether the remote-access bundle is started and has registered any services. |
CCERARE0003 | The private key must be specified when certificate is used for authentication. |
Explanation |
The selected authorization method is "certificate", however, a path to the private key is not specified. |
Action |
Specify the path to the private key. |
CCEREAE0003 | Authentication method {0} not supported. |
Explanation |
The specified authentication method is not supported. |
Action |
Check the Command Central documentation for the supported authentication methods. |
CCEREAE0004 | The provided private key does not exist: {0} |
Explanation |
The specified file that contains the private key does not exist on the file system. |
Action |
Make sure the private key is available. |
CCEREAE0005 | Remote host should be specified. |
Explanation |
Remote host is not specified and a connection cannot be established. |
Action |
Specify the remote host. |
CCEREAE0007 | {0} not found on {1} |
Explanation |
The specified path cannot be found on the target host. |
Action |
Make sure the specified path exists and try again. |
CCEREAE0008 | Invalid output from df: {0} |
Explanation |
The output of the df command does not match the POSIX standard. |
Action |
Make sure the target system has a POSIX compliant df command. |
CCEREAE0009 | The home directory of user {0} on host {1} could not be found. |
Explanation |
The home directory of the specified user on the specfied host could not be found. |
Action |
Check the configuration of the remote endpoint. |
CCEREAE0010 | Cannot close remote receive session. |
Explanation |
The remote session for receiving files cannot be closed. |
Action |
Check the logs for previous erros. |
CCEREMW0000 | Error producing zipped log source contents. Node alias: {0}, RuntimeComponent: {1}, Log Source Aliases: {2} Details: {3} |
Explanation |
An error occurred while producing the zipped archive containing a collection of log source contents on the Command Central server. |
Action |
Try again. If the problem persists, contact Software AG Global Support. |
CCEREMW0001 | Error attempting to close a file store used to produce zipped collection of log source contents. |
Explanation |
An error occurred while closing the zip file system object containing a collection of log source file contents. |
Action |
No action required. |
CCEREMW0002 | Error attempting to delete a temporary file used to create a zipped collection of log source contents. Filename: {0} |
Explanation |
An attempt to delete the specified file has failed. |
Action |
Locate the file on the server hosting Command Central and delete the file if it still exists. |
CCEREMW0004 | Error producing zipped log source contents. Node alias: {0} Details: {1} |
Explanation |
An error occurred while producing the zipped archive containing a collection of log source contents on the Command Central server. |
Action |
Try again. If the problem persists, contact Software AG Global Support. |
CCEREPE0000 | No repository with id, {0}, exists on managed node, {1} |
Explanation |
The specified repository does not exist. |
Action |
Ensure the correct repository id is specified in the request, or add the desired repository to the managed node. |
CCEREPE0001 | No repository with id, {0}, exists on managed node, {1} |
Explanation |
The specified repository does not exist. |
Action |
Ensure the correct repository id is specified in the request, or add the desired repository to the managed node. |
CCEREPE0002 | No such node, {0} |
Explanation |
The node alias specified in the request does not exist. |
Action |
Specify the correct node alias, or add the relevant node to the environment. |
CCEREPE0003 | The specified image location does not exist. |
Explanation |
The specified location for an image repository was not found on the file system. |
Action |
Provide a valid location for the image repository. |
CCEREPE0004 | The specified repository does not exist. |
Explanation |
The specified repository was not found. |
Action |
Check the repository name and provide the name of an existing repository. |
CCEREPE0005 | Parameters cannot be empty or missing. |
Explanation |
All parameters are required. |
Action |
Specify values for all parameters. |
CCEREPE0006 | A repository with this name already exists. |
Explanation |
The name of the repository should be unique. |
Action |
Check the repository name and provide a unique name for the repository. |
CCEREPE0007 | A repository at the same location already exists. |
Explanation |
Two or more repositories cannot point to the same location. |
Action |
Provide a unique location for the new repository. |
CCEREPE0008 | The specified repository points to an image file but the repository type is not image. |
Explanation |
The specified repository cannot point to and image file, because the repository type is not image. |
Action |
Specify the correct repository type. |
CCEREPE0009 | There is no repository to register. |
Explanation |
No repository is found for the specified name. |
Action |
Check the repository and resubmit the request. |
CCEREPE0010 | User credentials are missing. |
Explanation |
No user credentials are specified for the repository. |
Action |
Add user credentilas for the repository. |
CCEREPE0011 | Connection to node {0} failed. |
Explanation |
Could not connect to node {0}. |
Action |
Check if the node is online. |
CCEREPE0012 | Repository with type {0} does not exist. |
Explanation |
The repository with the specified type does not exist. |
Action |
Specify an existing repository type for the repository. |
CCEREPE0013 | Repository content cache invalidate failed. |
Explanation |
Invalidation of the content cache for repository {0} and nodeAlias {1} failed. |
Action |
See the Command Central logs for more details. |
CCEREPE0015 | Repository with the specified name: {0} does not exists. |
Explanation |
Importing content from the repository with name: {0} failed because a repository with the specified name was not found. |
Action |
Check the repository name and provide the name of an existing repository. |
CCEREPE0020 | Error occured while importing artifacts from repository with name: {0} to mirror repository with name: {1} for platforms: {2} |
Explanation |
An error occured while importing artifacts from repository with name: {0} to mirror repository with name: {1} for platforms: {2} |
Action |
See the corresponding Platform Manager logs for more details. |
CCEREPE0024 | Mirror repository with name: {0} is not published or registered on Command Central. |
Explanation |
Command Central cannot identify the specified mirror repository. |
Action |
Check if a mirror repository with name: {0} is published and registered on Command Central. Note that the Refresh operation refreshes a published mirror repository immediately after it is created or at a later point in time. |
CCEREPE0029 | Local mirror repository with name {0} can not be removed on target node {1} |
Explanation |
The local mirror repository with name {0} can not be removed on the target node {1} |
Action |
See the corresponding Platform Manager logs fro more details. |
CCEREPE0035 | Remote task failed: {0} |
Explanation |
Remote task failed: {0} |
Action |
See the corresponding Platform Manager logs for more details. |
CCEREPE0036 | Intiating mirror operation not from an image repository and without selecting "Product Repositories" is not supported. |
Explanation |
This operation is not supported as it might be time consuming because of the size of the source repository. |
Action |
Either select a product repository, or change the source repository to an image repository. |
CCEREPE0038 | Cannot delete Mirror repository with name: {0} because node with alias: {1} does not exists. Register node for host:{2} and port:{3}. |
Explanation |
The mirror repository is physically stored on {1} node, which was deleted and is not now registered in Command Central. |
Action |
Add the node with alias: {1} , host: {2} and port: {3} |
CCEREPE0039 | Cannot perform mirror operation because node with alias: {0} does not exists any more. Register again the node with alias: {0} for host: {1} and port: {2}. |
Explanation |
The mirror repository is physically stored on {0} node, which was deleted and is not now registered in Command Central. |
Action |
Add the node with alias: {0} , host: {1} and port: {2} |
CCEREPE0041 | Content of repository with displayName : {0} cannot be loaded. |
Explanation |
The content of the repository with displayName : {0} cannot be listed. |
Action |
Use a different repository type or check all logs for details about the error. |
CCEREPE0042 | Generation of repository status report for repository {0} will be skipped because connectivity validation failed. |
Explanation |
Generating the Repository Status report will be skipped and the list content operation will not be triggered. |
Action |
Check if the proxy is available and if the Platform Manager proxy configuration is set correctly. Also, check if the user credentials are valid. |
CCEREPE0043 | Creating a mirror repository failed because the source repository is not specified. |
Explanation |
The source repository from which to create the mirror repository is not specified. |
Action |
Specify at least one source repository. You can specify a master, image, or another mirror repository. |
CCEREPE0044 | Attempt to connect to {0} product repository from {1} installation timed out. |
Explanation |
Internet access is required to connect to this repository. The error occurred either because the proxy for the local Platform Manager is not configured, or the metadata and the user credentials for the repository are not correct. |
Action |
Configure a proxy for the local Platform Manager and check the repository metadata. |
CCEREPE0048 | Repository fix content cache update failed. |
Explanation |
An explicit repository fix content cache update failed during the regular cache update. |
Action |
Check if the connection to the fix repository is successful. |
CCEREPE0049 | Remote task failed: {0} |
Explanation |
Remote task failed\: {0} |
Action |
Check the corresponding Platform Manager logs for more details about the error. |
CCEREPE0052 | Error while retrieveing credentials with alias {0}. |
Explanation |
A credentials alias is not defined. |
Action |
Try again using an existing credentials alias. |
CCERPRE0000 | The repository name is not specified. |
Explanation |
The requested operation requires a repository name. |
Action |
Check the input and provide a repository name. |
CCERPRE0001 | Repository with the specified name {0} already exists. |
Explanation |
The repository name must be unique. |
Action |
Check the repository name and provide a unique name for the repository. |
CCERPRE0002 | Repository with the specified name {0} does not exists. |
Explanation |
Editing the repository failed, because a repository with the specified name was not found. |
Action |
Check the repository name and provide the name of an existing repository. |
CCERPRE0003 | Unknown repository type. Use one of {0} |
Explanation |
The specified repository type is not supported by Command Central. |
Action |
Use one of the suggested repository types. |
CCERPRE0004 | Destination is not specified. |
Explanation |
The destination parameter is missing. |
Action |
Specify a value for the destination parameter. For example, dest=myfixes.zip |
CCERPRE0005 | Destination parameter contains invalid characters. |
Explanation |
The destination parameter cannot contain file path manipulation characters. |
Action |
Specify a proper destination value. For example, dest=myfixes.zip |
CCERPRE0006 | Export image job is not found. |
Explanation |
The job responsible for creating an image is not found on the local Platform Manager. |
Action |
Check the logs for indication what went wrong. |
CCERPRE0007 | The specified path for the image file is not valid. |
Explanation |
The path specified for the image file is not valid. |
Action |
Provide a valid path for the image file. |
CCERPRE0008 | The specified repository content type ( {0} ) did not match the actual content type of the repository ( {1} ). |
Explanation |
The specified repository content type ( {0} ) did not match the actual content type of the repository ( {1} ). |
Action |
Verify that the specified repository content type is correct. |
CCERPRE0009 | The specified repository image file location "{0}" is not valid. |
Explanation |
The specified repository image file location "{0}" is not valid. |
Action |
Provide a valid repository image file location. |
CCERPRE0010 | The artifact : {0} is not found in the repository : {1} |
Explanation |
The identifier specified for the artifact is not valid or the artifact does not exist in the repository. |
Action |
Provide a valid identifier for the artifact: <id>_<version>. |
CCERPRE0011 | Command Central cannot find the specified image file at the specified location "{0}". |
Action |
Make sure the given path and file name are correct. |
CCERPRE0012 | Repository with name {0} is not found. |
Explanation |
There is no registered repository with the provided name. |
Action |
Provide a valid name of a registered repository. |
CCERPRE0013 | Repository image location URI is not valid. |
Explanation |
The location you provided is empty or not a valid URI. |
Action |
Ensure the provided location is not empty, does not include white spaces and points to a valid image file. |
CCERPRE0014 | The specified repository name {0} is not valid. |
Explanation |
No additional details. |
Action |
Specify a valid repository name. The name can include up to 100 ASCII characters, numbers, underscore (_), hyphen (-), and period (.). |
CCESREE0000 | Error occurred during retrieving user credentials |
Explanation |
This error might occur due to the following reasons: - Users attempt to get credentials when the credentials data store is empty; - While setting credentials, the communication with the remote SPM failed; - While deleting credentials, the communication with the remote SPM failed. |
Action |
Ensure that: - If you are attempting to get the credentials, the credentials data store is not empty. - If you are setting the credentials, the remote SPM is accessible. - If you are deleting the credentials, the remote SPM is accessible. |
CCESREE0001 | Specify the private key when certificate is used for authentication. |
Explanation |
The selected authorization method is "certificate", however, the path to the private key is not specified or is invalid. |
Action |
Specify a valid path to the private key. |
CCETEME0000 | A job with ID {0} cannot be found. |
Explanation |
The job with the specified ID may have completed long before this request. |
Action |
Use the following URI to list all recently completed or runnig jobs: /cce/jobmanager/jobs |
CCETEME0001 | The remote request encountered a concurrency error. |
Explanation |
The system could not execute parallel remote requests. |
Action |
Contact Software AG Global Support. |
CCETEME0002 | A job with ID {0} did not completed successfully in {1} seconds. |
Explanation |
The job with the specified ID may require more time to complete. |
Action |
Use the following URI to list all recently completed or running jobs: /cce/jobmanager/jobs |
CCETEME0003 | Template metadata cannot be empty. |
Explanation |
The template metadata is required for creating a template. |
Action |
Ensure that you have provided metadata for the template. The metadata.Alias and nodeAlias fields are required. |
CCETEME0004 | Template alias cannot be empty. |
Explanation |
The template alias is a required attribute of the template metadata. |
Action |
Specify a value for the template alias attribute. |
CCETEME0005 | Template nodeAlias cannot be empty. |
Explanation |
The template nodeAlias is a required attribute of the template metadata. |
Action |
Specify a value for the nodeAlias attribute. |
CCETEME0006 | Template options cannot be empty. |
Explanation |
The template options attribute is required in the template metadata. |
Action |
Specify at least one option and retry. |
CCETEME0007 | Error occurred during template creation {0} |
Explanation |
Creating the template failed with an error. |
Action |
Check the error logs for more details. |
CCETEME0008 | Error occurred during template creation on the remote managed node with alias : {0}. Remote task status is {1} |
Explanation |
Creating a template on the remote managed node with the specified ID failed with an error. |
Action |
Check the job status. |
CCETEME0009 | A template with alias: {0} already exists. |
Explanation |
Another template with the same alias already exists. |
Action |
To overwrite the existing template, add the OVERWRITE_TEMPLATE option in the template metadata.To create a new template and keep the existing template, change the template alias. |
CCETEME0010 | Node with alias : {0} does not exist. |
Explanation |
A managed installation (node) with the specified alias name does not exist. |
Action |
Specify a valid alias name for an existing installation (node). |
CCETEME0011 | A problem occured while downloading template with alias {0} on Command Central. |
Explanation |
Command Central could not create a folder for the template on the file system. |
Action |
Contact the Command Central Administrator. |
CCETEME0012 | A template with alias {0} could not be found. |
Explanation |
Command Central could not find a template with the specified alias. |
Action |
Check if the specified alias for the template you want to delete is correct. |
CCETEME0013 | Error occurred while creating a template on the remote managed node with alias: {0}. Remote task status is {1} |
Explanation |
Creating the template fails with a "Nothing to download on Command Central" error. |
Action |
See the error logs for the error details. |
CCETEME0014 | Template with alias {0} was not found. |
Explanation |
Command Central could not find a template with the specified alias. |
Action |
Verify that the alias is spelt correctly and that a template with this alias is already created. If the template is not created, execute a create template operation. |
CCETEME0015 | Template already exists. |
Explanation |
A template with the specified alias already exists. |
Action |
Change the alias of the imported template or delete the existing template with the same alias. |
CCETEME0016 | A problem occured while importing the template. |
Explanation |
Command Central could not create a folder for the template on the file system. |
Action |
Contact the Command Central Administrator. |
CCETEME0017 | Could not import template because a required file was not found. |
Explanation |
Command Central could not find or access the file from which to import the template. |
Action |
Contact the Command Central Administrator. |
CCETEME0018 | Template data is invalid. |
Explanation |
The provided template data could not be deserialised. |
Action |
Check if the provided template data is corrupted. |
CCETEME0019 | Template options cannot be empty. |
Explanation |
The template options attribute is required in the template metadata. |
Action |
Specify at least one option and retry. |
CCETEME0020 | The requested service temporarily not available. |
Explanation |
The requested service temporarily not available. This may be due to Platform Manager (SPM) being in the process of shutting down or still loading at start up. |
Action |
Ensure that Platform Manager is running and Installation has ONLINE status. |
CCETEME0021 | The Platform Manager (SPM) is shut down. |
Explanation |
The Platform Manager (SPM) is shut down. |
Action |
Ensure that Platform Manager is running and Installation has ONLINE status |
CCETEME0022 | Template metadata must be specified. |
Explanation |
Specify metadata for the template. |
Action |
Check the input parameters. |
CCETEME0023 | Node Alias must be specified. |
Explanation |
The template input parameters must include Node Alias. |
Action |
Check the input parameters. |
CCETEME0024 | Repository Id must be specified. |
Explanation |
The template input parameters must include Repository Id. |
Action |
Check the input parameters. |
CCETEME0025 | Repository with Id {0} cannot be found. |
Explanation |
The template input parameters must include Repository Id of existing Repository. |
Action |
Check the input parameters. |
CCETEME0026 | Template metadata in {0} cannot be unmarshalled. |
Explanation |
The file containing the metadata for the template cannot be read. |
Action |
Make sure the file exists, can be read and contains valid XML. |
CCETEME0027 | An error occurred while registering Repository {0} on Node {1}. Check the Server logs for details. |
Explanation |
The issue might occur because of a problem with the Repository contents. |
Action |
Check the Server logs for details. |
CCETEME0028 | Unable to obtain snapshot template job group id for node {0}. |
Explanation |
Command Central was unable to obtain the snapshot template job group id for a node. |
Action |
Contact Software AG Global Support. |
CCETEME0029 | Error during checking remote job status. |
Explanation |
An error occurred while checking the remote job status. |
Action |
Check if Platform Manager is running. |
CCETMRE0000 | Specify template alias, options, and target node. |
Explanation |
Template alias, target node alias, and options are required parameters for this template. |
Action |
Specify values for all required parameters. |
CCETMRE0001 | {0} option is specified but a repository for the option is not specified. |
Explanation |
A repository for the option is not specified. |
Action |
Specify a repository for the option. For example, if the option is PRODUCTS, specify a product repository. |
CCETMRE0002 | The specified repository is not applicable for this option {0} |
Explanation |
The specified repository is not applicable for the specified option. |
Action |
Specify a proper repository. For example, if the option is PRODUCTS, specify a product repository. |
CCETMRE0003 | There is no repository that supports the specified option {0}. |
Explanation |
The specified option is not supported by the specified repositories. For example, the error occurs if the FIXES option is specified, but the repository for this option does not support fixes. |
Action |
Specify a proper repository. For example, if the specified option is FIXES, specify a repository that contains fixes. |
CCETMRE0004 | No suitable option found for {0}. |
Explanation |
No matching option found for the specified parameter. |
Action |
Specify a supported template option. |
CCEWCME0009 | Display name cannot be empty. |
Explanation |
Display name is required. |
Action |
Provide the display name. |
CCEWCME0010 | Alias {0} cannot be empty. |
Explanation |
Environment alias and node alias cannot be empty. |
Action |
Provide a valid alias name. |
CCEWCME0011 | {0} cannot exceed {1} characters. |
Explanation |
The specified field input is incorrect. |
Action |
Check the error message and provide the correct input to the specified field. |
CCEWCME0012 | Environment name or alias cannot be {0}. |
Explanation |
Incorrect environment name/alias provided. |
Action |
Check the error message and provide the correct input. |
CCEWCME0013 | {0} alias cannot contain {1} non-ASCII characters. |
Explanation |
Environment alias cannot contain non-ASCII characters. |
Action |
Make sure the value of the alias field is correct. |
CCEWCME0014 | Alias {0} cannot contain spaces. |
Explanation |
Environment alias cannot contain spaces. |
Action |
Make sure the value of the alias field is correct. |
CCEWCME0015 | {0} already exists. |
Explanation |
The specified node/environment already exists. |
Action |
Specify a correct node/environment. |
CCEWCME0017 | Installation name cannot be empty. It must be less than 100 characters. |
Explanation |
Node name cannot be empty or contain more than 100 characters. |
Action |
Enter a valid node name. |
CCEWCME0018 | Alias cannot be empty. It should be no more than 100 characters long. It should not have spaces. Only ASCII characters, numbers, -, _, and . are allowed. |
Explanation |
The node alias cannot be empty. It should be no more than 100 characters long. |
Action |
Enter a valid node alias. |
CCEWCME0019 | Host name cannot be empty. The host name should be between two and 253 characters characters long. Do not use any special characters, except period(.) and minus(-). Do not start or end the host name with a period(.) or minus(-). |
Explanation |
The host name field cannot be empty. |
Action |
Provide a valid host name. The host name should be between two and 253 characters characters long. Do not use any special characters, except period(.) and minus(-). Do not start or end the host name with a period(.) or minus(-). |
CCEWCME0020 | Port number cannot be empty. It must be a positive number. |
Explanation |
Port number cannot be empty. |
Action |
Enter a valid port number. |
CCEWCME0028 | Installation alias {0} already exists. Please provide a different alias for the installation. |
Explanation |
Installation node already exists. |
Action |
Provide a different alias for the installation node you want to add. |
CCEWCME0039 | Null returned while retrieving the configuration types for comparison. |
Explanation |
This intermittent error occurs while retrieving the configuration types from Platform Manager. |
Action |
Retry configuration comparison. |
CCEWCME0047 | Specify a name for the template. No spaces allowed. Use only ASCII characters, numbers, "-", "_", and "." |
Explanation |
The alias field for the template cannot be empty. |
Action |
Provide a valid template alias. No spaces allowed. Use only ASCII characters, numbers, "-", "_", and "." |
CCEWCME0048 | Shared secret cannot be emtpy. |
Explanation |
The template shared secret cannot be emtpy. |
Action |
Provide a valid shared secret. |
CCEWCME0049 | The shared secrets you entered do not match. |
Explanation |
The shared secrets that you entered do not match. |
Action |
Re-enter the shared secrets. |
CCEWCME0050 | Select at least one include option. |
Explanation |
You cannot clear all include option check boxes. |
Action |
You must select at least one include option check box. |
CCEWCME0051 | No license reports were selected for deletion. |
Explanation |
At least one report must be selected in the view before clicking the delete button. |
Action |
Select one or more reports and click the delete button. |
CCEWCME0053 | No repositories configured. Add at least one repository. |
Explanation |
There are no central repositories configured in Command Central. |
Action |
Register at least one repository in Command Central. |
CCEWCME0069 | Specify a name for the repository. No spaces allowed. Use only ASCII characters, numbers, "-", "_", and "." |
Explanation |
The alias field for the repository cannot be empty. |
Action |
Provide a valid repository alias. No spaces allowed. Use only ASCII characters, numbers, "-", "_", and "." |
CCEWCME0072 | Repository {0} creation failed. |
Explanation |
Creating the repository failed. |
Action |
Check the server logs or contact your system administrator. |
CCEWCME0073 | Repository {0} update failed. |
Explanation |
Updating the specified repository failed. |
Action |
Check the server logs or contact your system administrator. |
CCEWCME0074 | Version cannot be empty. |
Explanation |
The Version field is a required field. |
Action |
Click the Advanced button and specify a valid server in the Enter server URL field. Leave this field empty to use the Software AG Download Center. |
CCEWCME0075 | Image file path cannot be empty. |
Explanation |
The Image file on server field is a required field. |
Action |
In the Image file on server field, provide a valid path to an image file on the Command Central server. |
CCEWCME0076 | An image file should be selected. |
Explanation |
Specifying an image file is required. |
Action |
In the Upload image file field, select an image file. |
CCEWCME0077 | A repository with location {0} was not found in the Software AG Download Center. |
Explanation |
The repository that you are trying to edit was not found in the Software AG Download Center. |
Action |
Contact your system administrator. |
CCEWCME0099 | Applying template {0} on installation {1} failed. |
Explanation |
The apply template operation on the target installation has failed. |
Action |
Check the logs and jobs on the target installation. |
CCEWCME0103 | Error while creating a new license report. {0} |
Explanation |
An error occurred while invoking the service action responsible for creating a new report. |
Action |
Check the Command Central server logs to determine the root cause for the error. |
CCEWCME0104 | Error while deleting license report(s). {0} |
Explanation |
An error occurred while invoking the service action responsible for deleting reports. |
Action |
Check the Command Central server logs to determine the root cause for the error. |
CCEWCME0105 | Error while refreshing the license reports view. {0} |
Explanation |
An error occurred while invoking the service action responsible for retrieving the reports from the Command Central server. |
Action |
Check the Command Central server logs to determine the root cause for the error. |
CCEWCME0114 | Saving of template {0} from installation {1} failed. |
Explanation |
The save template operation on the target installation has failed. |
Action |
Check the logs and jobs on the target installation. |
CCEWCME0119 | You do not have enough access privileges to perform requested operation. |
Explanation |
You do not have enough access privileges to perform requested operation. |
Action |
Contact your system administrator to help you get the required permissions. |
CCEWCME0124 | Bootstrapping of Platform Manager on installation with alias {0} failed. |
Explanation |
The bootstrap Platform Manager operation on the target installation has failed. |
Action |
Check the logs and jobs on Command Central. |
CCEWCME0125 | Alias {0} already exists. Provide a unique alias. |
Explanation |
Alias already exists. |
Action |
Provide a unique alias for the object you want to add. |
CCEWCME0126 | Alias cannot be empty. It should not have spaces. Only ASCII characters, numbers, -, _, and . are allowed. |
Explanation |
Alias cannot be empty. |
Action |
Enter a valid alias. |
CCEWCME0127 | No file specified. |
Explanation |
A valid file must be specified. |
Action |
Press the 'Browse' button and select a valid file. |
CCEWCME0129 | Error while deleting license manifest(s). {0} |
Explanation |
An error occurred while invoking the service action responsible for deleting license manifests. |
Action |
Check the Command Central server logs to determine the root cause for the error. |
CCEWCME0130 | Error while refreshing the license manifests view. {0} |
Explanation |
An error occurred while invoking the service action responsible for retrieving the license manifests from the Command Central server. |
Action |
Check the Command Central server logs to determine the root cause for the error. |
CCEWCME0132 | No license manifests were selected for deletion. |
Explanation |
At least one license manifest must be selected in the view before clicking the delete button. |
Action |
Select one or more license manifests and click the delete button. |
CCEWCME0135 | The contents of the specified file has invalid format. |
Explanation |
The contents of the specified file does not match the required format. |
Action |
Specify a file with valid format. |
CCEWCME0136 | Select remote installation method. |
Explanation |
A remote installation method is not selected in the web user interface. |
Action |
Select a remote installation method in the web user interface. |
CCEWCME0137 | Distribution cannot be empty. |
Explanation |
The Distribution field in the web user interface cannot be empty. |
Action |
Select a distribution in the Distribution field. |
CCEWCME0138 | Repository cannot be empty. |
Explanation |
The Repository field in the web user interface cannot be empty. |
Action |
Select a repository in the Repository field. |
CCEWCME0140 | Installation directory cannot be empty. |
Explanation |
The Installation directory field in the web user interface cannot be empty. |
Action |
Select an installation directory in the Installation directory field. |
CCEWCME0141 | Operating System cannot be empty. |
Explanation |
The Operating System field in the web user interface cannot be empty. |
Action |
Select an operating System in the Operating System field. |
CCEWCME0142 | Bootstrapped node {0} startup timed out. |
Explanation |
The status of the bootstrapped node is still OFFLINE after the required timeout. |
Action |
Check the Command Central bootstrap logs. |
CCEWCME0143 | Bootstrap installer creation failed. |
Explanation |
Bootstrap installer creation failed. |
Action |
Check the Command Central logs. |
CCEWCME0145 | User name cannot be empty. |
Explanation |
The user name field cannot be empty. |
Action |
Provide a value in the user name field. |
CCEWCME0146 | Password cannot be empty for the selected authentication method. |
Explanation |
The Password cannot be empty for the selected authentication method. |
Action |
Provide a value in the Password field for the selected authentication method. |
CCEWCME0147 | Key file cannot be empty for the selected authentication method. |
Explanation |
The Key file field cannot be empty for the selected authentication method. |
Action |
Provide a value in the Key file field for the selected authentication method. |
CCEWCME0148 | Password cannot be empty. |
Explanation |
The Password field cannot be empty. |
Action |
Provide a value in the Password field. |
CCEWCME0149 | User name cannot be empty. |
Explanation |
The user name cannot be empty. |
Action |
Provide a value in the user name field. |
CCEWCME0151 | Navigation to the log(s) for node {0} can not be initiated. |
Explanation |
A node with alias {0} does not exist in the Command Central landscape. |
Action |
Select an existing node different than {0}. |
CCEWCME0152 | You do not have access to the requested operation(s). |
Explanation |
You do not have access to the requested operation(s). |
Action |
Provide valid credentials to perform the requested operation(s). |
CCEWCME0154 | Request to create a license report failed. |
Explanation |
An error occurred during the creation of the license report. |
Action |
Contact Software AG Global Support. |
CCEWCME0155 | Select fixes to be installed. |
Explanation |
No fixes are selected for installation. |
Action |
Select at least one fix to be installed. |
CCEWCME0156 | Duplicate fixes selected. Select only one of the fix versions to be installed. |
Explanation |
Duplicate fixes with the same ID, but different versions were selected. |
Action |
Select only one of the possible versions. |
CCEWCME0157 | The key should not be empty. |
Explanation |
The Support Patch key should not be empty. |
Action |
Provide a Support Patch key. |
CCEWCME0158 | The Platform Manager (SPM) on this installation is not online. |
Explanation |
The selected fix and product installation functions are not supported when Platform Manager is not running. |
Action |
Start Platform Manager and try again. |
CCEWCME0159 | Release 9.7 and higher supports fix installation. |
Explanation |
Fix installation is supported for installations of release 9.7 and higher. See the actions suggested for your installation in the Action field. |
Action |
Use Software AG Update Manager to install fixes and support patches for this installation. Consider upgrading this installation to 9.10 or a later release, using Command Central. |
CCEWCME0162 | This installation version ({0}) does not support this feature. |
Explanation |
The selective fix uninstallation feature is supported beginning with Platform Manager 9.7. |
Action |
If it is not possible to upgrade the installation to the latest available release version, you should use Update Manager to uninstall fixes. |
CCEWCME0163 | Select a support patch to be installed. |
Explanation |
There is no support patch selected for installation. |
Action |
Select a support patch to install. |
CCEWCME0166 | Select at least one source repository. |
Explanation |
You must select at least one source repository from which to create a mirror repository. |
Action |
Select at least one source repository from which to create a mirror repository. |
CCEWCME0167 | The provided configuration is not valid. |
Explanation |
The server request can not be completed successfully. |
Action |
Expand this view for more details. |
CCEWCME0168 | No license keys were selected for deletion. |
Explanation |
You must select at least one license key in the view before clicking the delete button. |
Action |
Select one or more license keys and click the delete button. |
CCEWCME0171 | Error while refreshing the license keys view. {0} |
Explanation |
An error occurred while invoking the service action responsible for retrieving the license keys from the Command Central server. |
Action |
Check the Command Central server logs to determine the root cause for the error. |
CCEWCME0174 | Adding/Updating a repository operation failed. |
Explanation |
Adding a repository operation failed. The job status is Error. |
Action |
Check the logs and try again. |
CCEWCME0175 | Error while deleting license key(s). {0} |
Explanation |
An error occurred while invoking the service action responsible for deleting license keys. |
Action |
Check the Command Central server logs to determine the root cause for the error. |
CCEWCME0183 | Invalid username or password. |
Explanation |
Invalid username or credentials provided in the Command Central Login page. |
Action |
Provide valid username or credentials in the Command Central Login page. |
CCEWCME0184 | To mirror from a MASTER repository, you need at least one product repository that will be used as a filter for the repository content. |
Explanation |
To mirror from a MASTER repository, you need at least one product repository that will be used as a filter for the repository content. |
Action |
Select at least one product repository. |
CCEWCME0185 | Specify a name that follows the webMethods-<major.version>.<minor.version>_<name> pattern. |
Explanation |
The pattern allows to extract the version when constructing a bootstrap image for ALL SPM distribution. |
Action |
Name your product mirror repository after the pattern. |
CCEWCME0188 | Insufficient permissions to access this resource. |
Explanation |
You do not have sufficient permissions to access this resource. |
Action |
Contact your system administrator to get sufficient permissions. |
CCEWCME0209 | Release 9.8 and higher supports product installation. |
Explanation |
Product installation is supported for installations of release 9.8 and higher. See the actions suggested for your installation in the Action field. |
Action |
Use Software AG Installer to install products for this installation. Consider upgrading this installation to 9.10 or a later release, using Command Central. |
CCEWCME0210 | Release 9.8 and higher supports support patch installation. |
Explanation |
Support patch installation is supported for installations of release 9.8 and higher. See the actions suggested for your installation in the Action field. |
Action |
Use Software AG Update Manager to install support patches for this installation. Consider upgrading this installation to 9.10 or a later release, using Command Central. |
CCEWCME0214 | Enter your user name for the Software AG Download Center. |
Explanation |
The user name field cannot be epmty. |
Action |
Enter a valid user name for the Software AG Download Center. |
CCEWCME0215 | Enter your password for the Software AG Download Center. |
Explanation |
The password field cannot be epmty. |
Action |
Enter a valid password for the Software AG Download Center. |
CCEWCME0216 | Enter your user name for the remote Platform Manager. |
Explanation |
The user name field cannot be epmty. |
Action |
Enter a valid user name for the Platform Manager, which is specified in the repository URL. |
CCEWCME0217 | Enter your password for the remote Platform Manager. |
Explanation |
The password field cannot be epmty. |
Action |
Enter a valid password for the Platform Manager, which is specified in the repository URL. |
CCEWCME0220 | Updating repository contents operation failed. |
Explanation |
The repository update contents operation failed. The job status is Error. |
Action |
Check the logs and try again. |
CCEWCME0223 | Could not transfer the file to the target destination {0}. |
Explanation |
The file could not be transfered because of an error. |
Action |
Check if the target host has enough disk space or the specified file name is valid. |
CCEWCME0228 | You are not allowed to perform the requested operation. |
Explanation |
You are not allowed to perform the requested operation because of Cross Site Request Prevention. |
Action |
Ensure that you do not have several Command Central REST resources open in the same browser session. If you do, close all the instances of the browser and log into the Command Central web user interface again. |
CCEWCME0239 | Source repositories with different versions are selected: {0}. |
Explanation |
The selected source repositories have different versions. |
Action |
Select source repositories with the same version. |
CCEWCME0240 | Connecting to asset repository {0} failed. |
Explanation |
Connecting to an asset repository failed. |
Action |
Check the logs and try again. |
CCEWCME0243 | Asset repository {0} could not be connected/edited. |
CCEWCMI0021 | Installation {0} already exists in environment {1}. |
Explanation |
The selected node already exists in the environment. Drag and drop not possible. |
Action |
Verify if you have selected the correct nodes and the environment for drag and drop. |
CCEWCMI0040 | {0} must be a non-negative integer. |
Explanation |
Specified field must be a non-negative integer. |
Action |
Enter a valid field value. |
CCEWCMI0041 | {0} cannot be empty. |
Explanation |
Specified field cannot be empty. |
Action |
Enter a valid field value. |
CCEWCMI0046 | Alias cannot be empty. |
Explanation |
The port alias field cannot be empty. |
Action |
Provide a valid port alias name. |
CCEWCMI0057 | User credentials saved successfully. |
Explanation |
The provided user credentials are successfully saved. |
Action |
None. |
CCEWCMI0058 | User credentials deleted successfully. |
Explanation |
The provided user credentials are successfully deleted. |
Action |
None. |
CCEWCMI0098 | Template {0} successfully saved from installation {1}. |
Explanation |
The save template operation completed successfully. |
Action |
No action required. |
CCEWCMI0100 | Type a keyword to display only the reports that contain the keyword in the report id, creator, create date or compliance status. The search is case-insensitive. |
Explanation |
License report search filter help text. |
Action |
None. |
CCEWCMI0101 | Do you wish to continue? |
Explanation |
Part of the license report confirmation dialog for creating a new report. |
Action |
None. |
CCEWCMI0110 | It may take a few moments to generate the report. |
Explanation |
Part of the license report confirmation dialog for creating a new report. |
Action |
None. |
CCEWCMI0112 | license report(s) |
Explanation |
Part of 'delete license report(s)' confirmation dialog. |
Action |
None. |
CCEWCMI0113 | Report Id(s): {0} |
Explanation |
License report confirmation dialog for deleting one or more reports. |
Action |
None. |
CCEWCMI0115 | Template {0} successfully applied on installation {1}. |
Explanation |
The apply template operation completed successfully. |
Action |
No action required. |
CCEWCMI0117 | Scheduled job did not complete within status checker''s allotted time. |
Explanation |
The client job status checker stopped polling for an executing job's status before it completed. This does not necessarily mean the job did not complete successfully. |
Action |
Confirm if job completed via other means. |
CCEWCMI0120 | Attribute {0} successfully submitted. |
Explanation |
The attribute was successfully added or updated. |
Action |
No action required. |
CCEWCMI0121 | Attribute {0} successfully deleted. |
Explanation |
The attribute was successfully deleted. |
Action |
No action required. |
CCEWCMI0123 | Platform Manager successfully bootstrapped on installation with alias {0}. |
Explanation |
The bootstrap of Platform Manager was successful. |
Action |
No action required. |
CCEWCMI0131 | Type a keyword to display only the license manifests that contain the keyword in one of the columns. The search is case-insensitive. |
Explanation |
License manifest search filter help text. |
Action |
None. |
CCEWCMI0144 | Bootstrap installer created successfully. |
Explanation |
A new bootstrap installer was successfully created. |
Action |
None. |
CCEWCMI0180 | No licenses have been registered |
Explanation |
No license key aliases have been registered so that it is not possible to select a license key alias. |
Action |
Register a license key alias. |
CCEWCMI0186 | Provided configuration is valid. |
Explanation |
The server request is completed successfuly. |
Action |
Expand this view for more details. |
CCEWCMW0107 | No data selected for delete. |
Explanation |
You must select at least one object for deletion. |
Action |
Select at least one object from the object list. |
CCEWCMW0108 | Delete request failed, but no ErrorInfo was found. |
Explanation |
A problem occurred when executing a delete request, but the server did not provide details about the problem. |
Action |
Check the server-side log files for details. Contact Software AG Global Support. |
CCEWCMW0109 | Request to delete license reports failed for these report IDs: {0} |
Explanation |
The server was not able to delete the license reports identified here. The request may have included other report IDs for which deletion was successful. |
Action |
Refresh the display of license reports to see which were deleted. Check the server-side error log for details about why the attempt to delete failed. |
CCEWCMW0118 | Unable to determine job status due to unexpected error while checking status. {0} |
Explanation |
Job status checking encountered an error. This does not necessarily mean the job did not complete successfully. |
Action |
Confirm if job completed via other means. |
CCEWCMW0122 | The provided attribute name {0} already exists. |
Explanation |
The attribute name which you are trying to add already exists. |
Action |
Provide a unique attribute name. |
CCEWCMW0172 | Delete request failed for this alias: {0} |
Explanation |
The server was not able to delete the object with the given alias. |
Action |
Check the server-side error log for details about why the attempt to delete failed. |
CCEWCMW0187 | Provided configuration is valid, but check the warnings. |
Explanation |
The server request is completed, but check the warnings. |
Action |
Expand this view for more details. |
CCEWCMW0211 | Not all products can be installed by Command Central. |
Explanation |
The number of products that you can install using Command Central increases with each Software AG release. |
Action |
See the Command Central release readme for a list of products that you cannot install through Command Central for each Software AG release. |
CCEWCMW0212 | There are artifacts which are either not applicable for the installation or not present in the selected repository. |
Explanation |
The following artifacts are either not applicable, or not present in the selected repository: {0} |
Action |
Either continue without the missing artifacts, or use a source repository containing those artifacts. |
CCEWCMW0222 | User credentials for repository {0} are missing or invalid. |
Explanation |
The user credentials for repository {0} are missing or invalid. |
Action |
Specify valid user credentials for repository {0}. |