Platform Manager Messages

SPMADME0000 Administration SPI for "{0}" and namespace "{1}" not found.
Explanation

The Administration SPI for the specified entity and namespace should be registered beforehand.

Action

Check if the correct entity ID and namespace are provided or if the product plug-in is available.


SPMADME0001 Error while invoking administration function "{0}" with arguments "{2}" of "{1}" and namespace "{3}".
Explanation

The specified administration function does not work properly. The administration function is either not available, or the arguments used to invoke the function are incorrect.

Action

Check the functions supported by component "{4}" registered with properties "{5}" .


SPMADME0002 Administration function "{0}" with arguments "{2},{3}" of "{1}" and namespace "{4}" not found.
Explanation

The specified administration function is not defined for the entity with the specified arguments.

Action

Check the functions supported by the Administration SPI.


SPMADME0003 {0} process finished with error code {1}. Requested command: {2} Output: {3}
Explanation

The requested command could not be executed successfully.

Action

Check the upgrade and migration help for the product.


SPMCCPEMIE0001 An error occurred during a call to wm.monitor.util:configSettings. The error reported is: {0}.
Explanation

An error occurred during the service call to write the configuration settings to WmMonitor. A probable cause for the error is failing to access the IntegrationServer\packages\WmMonitor\config\monitor.cnf file. The error could also occur when the monitor.cnf file is not present initially and the service call to write the configuration settings creates and populates the file with default values.

Action

Ensure that the IntegrationServer\packages\WmMonitor\config\monitor.cnf file is present, contains name=value pairs, and the name=value pairs are valid. Also, ensure that the name-value pairs are acceptable for your configuration.


SPMCCPEMIE0002 Only BASIC authentication is supported.
Explanation

The specified authentication is not supported.

Action

Change authentication to BASIC.


SPMCCPEMIE0003 The My webMethods Server URL is not valid.
Explanation

The URL for pinging My webMethods Server is not valid.

Action

Check that your WmMonitor configuration values for host, port, username and password are valid.


SPMCCPEMIE0009 No My webMethods Server credentials were provided.
Explanation

The connection to My webMethods Server cannot be validated without proper credentials.

Action

Specify values for username and password.


SPMCCPEMIE0014 The My webMethods Server host, port, and/or connection protocol were not provided.
Explanation

You must specify values for the My webMethods Server host, port, and connection protocol.

Action

Specify values for host, port, and connection protocol.


SPMCCPEMIE0015 The values are required.
Explanation

You must specify values in the fields.

Action

Specify values for these fields.


SPMCCPEMIW0000 My webMethods Server password was not provided.
Explanation

The password is a required field.

Action

Provide a password for My webMethods Server.


SPMCCPEMIW0004 The My webMethods Server URL is not accessible. Click Show Details for more information.
Explanation

The URL for pinging My webMethods Server is not accessible.

Action

Check that your WmMonitor configuration values for host, port, username and password are valid, and also confirm that My webMethods Server is reachable on the network.


SPMCCPEMIW0005 My webMethods Server credentials are not valid.
Explanation

The username or password are incorrect.

Action

Check that the username and password are correct.


SPMCCPEMIW0011 The password is required.
Explanation

You must specify a password.

Action

Specify a password.


SPMCCPEMIW0012 No value was provided for 'Data Level Security Administrator'
Explanation

A value for the Data Level Security, DLS, super user was not provided.

Action

No action is required if the default value of \'Administrator\' is acceptable.


SPMCCPEMIW0013 A default value of 'Administrator' was provided; it will be displayed upon Save.
Explanation

Because no value was provided for the Data Level Security super user, the default value of \'Administrator\' is used.

Action

Set a value for Data Level Security Administrator.


SPMCFCE0012 Properties serializer supports only instances of java.util.Properties
Explanation

The user is trying to use a Properties serializer on an inapropriate object type.

Action

Use proper serializer for your object.


SPMCFCE0023 There is no registered ConfigurationSerializer under runtimeComponentId {0} and configurationTypeId {1}
Explanation

No registered ConfigurationSerializer exists under the entered runtimeComponentId and configurationTypeId.

Action

Register a ConfigurationSerializer under the entered runtimeComponentId and configurationTypeId.


SPMCFCE0026 ConfigurationManager should be registered with the runtimeComponentId and configurationTypeId properties.
Explanation

ConfigurationManager should be registered with the runtimeComponentId and configurationTypeId properties. They cannot be null.

Action

Register ConfigurationManager and set values for the runtimeComponentId and configurationTypeId properties.


SPMCFCE0030 Error ocurred during serialization/deserialization.
Explanation

Error ocurred during serialization/deserialization.

Action

Check for user permissions and hardware failures and try again.


SPMCFCE0049 Configuration is not available for this component.
Explanation

The component requires a configuration to function properly.

Action

Set the configuration for this component.


SPMCFCI0000 Port Settings
Explanation

PortSettingsConfigurationType Display Name

Action

None.


SPMCFCI0001 Listener ports configuration
Explanation

PortSettingsConfigurationType description.

Action

None.


SPMCFCI0019 The keystore truststore settings cannot be null.
Explanation

The keystore truststore settings cannot be set to null.

Action

Provide a valid keystore truststore setting.


SPMCFCI0028 There can be only one primary pool defined in the JDBC configuration.
Explanation

There can be only one primary pool defined in the JDBC configuration.

Action

Specify only one pool with the primary as true.


SPMCFGE0000 The configuration type argument is not set.
Explanation

The configuration type argument is not set.

Action

Set the configuration type argument.


SPMCFGE0001 Configuration type {0} cannot be found.
Explanation

A Configuration Manager that can handle configuration type {0} cannot be found.

Action

Make sure that configuration type {0} is supported, for example check if there is a Configuration Manager registered for it.


SPMCFGE0002 A Configuration instance with ID = {0} does not exist.
Explanation

A Configuration instance with the provided ID does not exist.

Action

Use the ID of an existing Configuration instance.


SPMCFGE0003 Loaded configuration cannot be null.
Explanation

The requested configuration cannot be null.

Action

Provide valid runtimeComponent, configurationInstance, and configurationStatus.


SPMCFGE0004 The Configuration Manager Service is not set.
Explanation

The Configuration Manager Service is not set.

Action

Set the Configuration Manager Service.


SPMCFGE0005 The component ID or configurationType ID is wrong.
Explanation

The component ID or configurationType argument ID is wrong.

Action

Use an appropriate component ID or configurationType ID.


SPMCFGE0006 Configuration is not available for this component.
Explanation

This component needs configuration in order to function.

Action

Set the configuration for this component.


SPMCFGE0007 ConfigurationSerializer SPI could not be found for RuntimeComponentId "{0}" and ConfigurationTypeId "{1}" .
Explanation

Platform Manager did not find registered ConfigurationSerializer that can handle ConfigurationInstances with these properties.

Action

Register ConfigurationSerializer SPI implementation that can handle ConfigurationInstances with these properties.


SPMCFGE0008 Id cannot be null.
Explanation

When creating a configuration instance, the id argument cannot be null.

Action

Provide a non-null id argument.


SPMCFGE0009 ConfigurationTypeId cannot be null.
Explanation

When creating a configuration instance, the ConfigurationTypeId argument cannot be null.

Action

Provide a non-null id argument.


SPMCFGE0010 DisplayName cannot be null.
Explanation

When creating a configuration instance, the displayName argument cannot be null.

Action

Provide a non-null id argument.


SPMCFGE0011 The component to be updated is null.
Explanation

The runtime component to be updated cannot be null.

Action

Provide a non-null runtime component.


SPMCFGE0012 Protocol value cannot be changed.
Explanation

The protocol value for an existing port configuration cannot be changed.

Action

Retry the operation without changing the protocol.


SPMCFGE0013 Create command is not supported.
Explanation

Create configuration command is not supported by this configuration manager.

Action

Check the logs.


SPMCFGE0020 ConfigurationService is not set.
Explanation

ConfigurationService is not set.

Action

Register a ConfigurationService.


SPMCFGE0021 New configuration is null.
Explanation

The configuration sent for validation is null.

Action

Send a valid configuration that is not null.


SPMCFGE0022 Delete command is not supported
Explanation

Delete configuration command is not supported by this configuration manager.

Action

Check the logs.


SPMCFGE0023 The new configuration to be validated can not be null.
Explanation

The new configuration to be validated can not be null.

Action

Send a valid configuration that is not null for validation.


SPMCFGE0024 Duplicate truststore aliases in the existing instances.
Explanation

Duplicate truststore aliases are present in the existing instances.

Action

Use a unique truststore alias.


SPMCFGE0025 Duplicate truststore aliases are present in the existing instances.
Explanation

Duplicate truststore aliases are present in the existing instances.

Action

Use a unique truststore alias.


SPMCFGE0026 Duplicate keystore aliases in existing instances.
Explanation

Duplicate keystore alias is present in the existing instances.

Action

Use a unique keystore alias.


SPMCFGE0027 Duplicate keystore alias is present in existing instances.
Explanation

Duplicate keystore alias is present in the existing instances.

Action

Use a unique keystore alias.


SPMCFGE0028 The file location provided in the keystore could not be found.
Explanation

The file location provided in the keystore could not be found.

Action

The file location provided in the keystore configuration must point to an existing file. Use an existing file location.


SPMCFGE0040 The keystore location information is missing.
Explanation

The keystore location information is missing in the new configuration.

Action

Use a valid keystore location that points to an existing file.


SPMCFGE0041 The keystore location information is either null or empty. It should point to an existing file.
Explanation

The keystore location information is either null or empty. It should point to an existing file.

Action

The keystore location should point to an existing file.


SPMCFGE0042 An exception occurred when trying to get the existing aliases.
Explanation

The PlatformManagerException exception occured when trying to get the existing aliases.

Action

You need to correct the existing configuration instances with valid aliases.


SPMCFGE0043 An exception occurred when trying to get the existing aliases.
Explanation

The IOException exception occurred when trying to get the existing aliases.

Action

Provide a valid runtime ID and configuration type ID to the validator.


SPMCFGE0049 Configuration of type Common-JDBC is null.
Explanation

Configuration object for Common-JDBC is null.

Action

Specify the valid configuration object for Common-JDBC.


SPMCFGE0051 Duplicate alias for Jdbc Pool is found.
Explanation

Alias for Jdbc Pool is not unique. This is not a valid configuration.

Action

Specify a unique Jdbc Pool alias.


SPMCFGE0053 There can be only one pool with primary as true.
Explanation

There is more than one pool defined as primary. This is not valid.

Action

Specify only one pool with primary as true.


SPMCFGE0055 JDBC Pool information is not available. Specify valid JDBC Pool Settings.
Explanation

JDBC Pool information is not available in the JDBC Settings Configuration Object. This is not valid.

Action

Specify valid JDBC Pool Settings.


SPMCFGE0058 An exception occurred when trying to get the existing aliases.
Explanation

The PlatformManagerException exception occured when trying to get the existing aliases.

Action

You need to correct the existing configuration instances with valid JDBC pool aliases.


SPMCFGE0059 The JDBC connection failed.
Explanation

The JDBC connection failed because it was invalid.

Action

Specify valid JDBC connection data.


SPMCFGE0060 Failed to close a valid JDBC connection.
Explanation

Failed to close a valid JDBC connection.

Action

Contact your system administrator.


SPMCFGE0061 Password verification failed.
Explanation

The password provided to load the certificate is incorrect.

Action

You need to provide a valid password and try again.


SPMCFGE0065 Configuration Instance "{0}" does not exist.
Explanation

Configuration Instances should be backed up by existing source.

Action

Make sure this particular Configuration Instance is declared correctly.


SPMCFGE0066 Configuration Instance "{0}" is not a valid URL.
Explanation

Configuration Instance "{0}" should be backed up by valid URL source.

Action

Make sure this particular Configuration Instance is declared correctly.


SPMCFGE0067 Unknown property name "{0}".
Explanation

The property is not recognized.

Action

Make sure this particular Configuration Instance is declared correctly.


SPMCFGE0068 The specified port number is already in use. The port number is bound to an application outside the current installation of Software AG Suite of products.
Explanation

The specified port number is already in use. The port number is bound to an application outside the current installation of Software AG Suite of products.

Action

Specify a different port number or shut down the component that is running on this port.


SPMCFGE0071 The value {0} cannot be used. A non-negative number is expected.
Explanation

The specified value must not be a negative number.

Action

Specify a non-negative number.


SPMCFGE0073 The value of the Threadpool Min parameter cannot be equal to or more than the value for the Threadpool Max parameter.
Explanation

The value of the Threadpool Min parameter cannot be equal to or more than the value of the Threadpool Max parameter.

Action

Change the configuration to make the value of the Threadpool Max parameter more than the value of the Threadpool Min parameter.


SPMCFGE0078 The configuration contains duplicate log file name entries.
Explanation

Duplicate log file names exist in the log configuration appendices.

Action

Make sure each log file name in the log configuration is unique.


SPMCFGE0079 Log file name {0} already exists.
Explanation

The specified log file name exists in another runtime component's log configuration.

Action

Make sure each file name is unique across runtime components.


SPMCFGE0080 Not enough disk space.
Explanation

The disk partition free space is less that 10Mb.

Action

Make sure the disk partition has enough free space.


SPMCFGE0081 The user does not have privileges to perform file operations. Check the current security policy.
Explanation

The user performing the file operation does not have the proper privileges necessary to create or write to a log file.

Action

Make sure the user has adequate privileges to perform the operation.


SPMCFGE0082 Error creating temp file in {0}. Make sure the specified directory is valid.
Explanation

The log configuration validation failed because the specified log directory is not valid or does not exist.

Action

Make sure the specified log directory is valid.


SPMCFGE0084 The "from" or "to" email address is not correct.
Explanation

In Platform Manager, during validation of sending a test email, if the "from" or "to" email address is not correct, this error is thrown.

Action

Ensure that the "from" or "to" email address is correct, and try again.


SPMCFGE0086 Not able to connect to the SMTP server {0}.
Explanation

In Platform Manager, the socket connection is not able to connect to the SMTP server with the given credentials.

Action

Ensure the server is running and the specified credentials are correct.


SPMCFGE0088 Unable to send a test mail to the recipient {1} using the SMTP server {0}.
Explanation

In Platform Manager, an error occurs when sending an email to the recipient.

Action

The email ID is non-existent. Enter a valid email ID and try again.


SPMCFGE0090 An exception occurred when trying to get the existing aliases.
Explanation

The IOException exception occurred when trying to get the existing aliases.

Action

Provide a valid runtime ID and configuration type ID to the validator.


SPMCFGE0091 An exception occurred when trying to get the existing JDBC pools defined as primary.
Explanation

The PlatformManagerException exception occured when trying to get the existing JDBC pools defined as primary.

Action

You need to correct the existing configuration instances with only one JDBC pool as primary.


SPMCFGE0092 An exception occurred when trying to get the existing JDBC pools defined as primary.
Explanation

The IOException exception occurred when trying to get the existing JDBC pools defined as primary.

Action

Provide a valid runtime ID and configuration type ID to the validator.


SPMCFGE0093 No value was specified for the Protocol parameter.
Explanation

No value was specified for the Protocol parameter.

Action

Specify a value for the Protocol parameter.


SPMCFGE0094 The keystore truststore setting is empty.
Explanation

The keystore truststore setting does not contain any fields.

Action

Provide either the keystore, truststore or extended properties.


SPMCFGE0095 The keystore truststore setting does not contain any element.
Explanation

The keystore truststore setting should either have the keystore, the truststore, or the extended properties, which is missing.

Action

Add the keystore, the truststore, or the extended properties to the keystore truststore setting.


SPMCFGE0096 There can be only one primary pool defined in the JDBC configuration.
Explanation

There can be only one primary pool defined in the JDBC configuration.

Action

Specify only one pool with the primary as true.


SPMCFGE0097 The JDBC Pool name is not unique.
Explanation

The JDBC Pool name is not unique.

Action

Specify a unique JDBC Pool name.


SPMCFGE0098 The JDBC driver class should not be null when the database server type is Custom.
Explanation

The JDBC driver class should not be null when the database server type is Custom.

Action

Specify the JDBC Driver class if the database server type is Custom.


SPMCFGE0099 The database server host should not be null when the database server type is non-custom and the URL is not specified.
Explanation

The database server host should not be null when the database server type is non-custom and the URL is not specified.

Action

Specify the hostname for the database server when the server type is non-custom and the database URL is not specified.


SPMCFGE0100 The database server port number should not be null when the database server type is non-custom and the URL is not specified.
Explanation

The database server port number should not be null when the database server type is non-custom and the URL is not specified.

Action

Specify the port number for the database server when the server type is non-custom and the database URL is not specified.


SPMCFGE0101 The database server SID should not be null when the database server type is Oracle and the URL is not specified.
Explanation

The database server SID should not be null when the database server type is Oracle and the URL is not specified.

Action

Specify the Oracle SID when the database server type is Oracle and the database URL is not specified.


SPMCFGE0102 The database server's database name should not be null when the database server type is non-Oracle and the URL is not specified.
Explanation

The database server's database name should not be null when the database server type is non-Oracle and the URL is not specified.

Action

Specify the database name when the database server type is non-Oracle and the URL is not specified.


SPMCFGE0103 An error occured while getting either the runtime components or configuration instances using the configuration or inventory service.
Explanation

An error occured while getting either the runtime components or configuration instances using the configuration or inventory service.

Action

Retry the action.


SPMCFGE0105 Configuration instance and its configuration manager must have the same configuration type.
Explanation

Configuration instance and its configuration manager must have the same configuration type.

Action

Check the type of the provided configuration instance.


SPMCFGE0106 Not able to connect to the SMTP server(s) {0} with the given credentials and also not able to send a test mail to the recipient using the SMTP server(s) {1}.
Explanation

In Platform Manager, the socket connection is not able to connect to the SMTP server with the given credentials (if provided). Also, a test mail to the recipient using the SMTP server is also not sent.

Action

Ensure the server is running and the server credentials entered are correct. Also, enter the correct email address and try again.


SPMCFGE0109 The license file can not be empty.
Explanation

In Platform Manager, when an empty license file is uploaded, this message is seen.

Action

You need to ensure to upload a license file that is not empty.


SPMCFGE0110 The truststore location information is missing.
Explanation

The truststore location information is missing in the new configuration.

Action

Use a valid truststore location that points to an existing file.


SPMCFGE0111 The truststore location information is either null or empty. It should point to an existing file.
Explanation

The truststore location information is either null or empty. It should point to an existing file.

Action

The truststore location should point to an existing file.


SPMCFGE0112 The specified port is already bound by configuration instance {0} of runtime {1} and is enabled.
Explanation

The specified port is already bound by configuration instance {0} of runtime {1} and is enabled.

Action

Change the port number and retry.


SPMCFGE0114 The specified Bind Address value of {0} is invalid.
Explanation

The value of {0} is invalid for Bind Address.

Action

Specify a valid bind address and retry.


SPMCFGE0115 The specified port {0} is already in use by another configuration instance.
Explanation

The specified port {0} is already in use by configuration instance {1} of runtime {2}.

Action

Change the port number and retry.


SPMCFGE0117 The specified port number {0} is already in use.
Explanation

The specified port number {0} is already in use. The port number is bound to an application outside the current installation of Software AG Suite of products.

Action

Specify a different port number or shut down the component that is running on this port.


SPMCFGE0120 License file location is not specified in License Location Manager.
Explanation

The location of the license file is not specified in the License Location Manager.

Action

Specify a valid license file location in License Location Manger before loading the License instance.


SPMCFGE0121 The configured license is not valid for this product : {0}
Explanation

The product code in the license file does not match with the product installed.

Action

Contact your system administrator or Software AG Global Support.


SPMCFGE0122 The configured license is not valid for this version : {0}
Explanation

The product version in the license file does not match with the product installed version.

Action

Contact your system administrator or Software AG Support.


SPMCFGE0125 The provided port alias {0} already exists.
Explanation

The provided port alias {0} already exists for this runtime component.

Action

Provide a unique port alias for the runtime component.


SPMCFGE0126 The specified port alias {0} differs from the existing port alias {1}
Explanation

The specified port alias {0} differs from the existing port alias {1}

Action

Do not change the port alias when you execute an update operation.


SPMCFGE0127 The JDBC Pool alias cannot be changed once it is created.
Explanation

While updating a JDBC Pool, the alias was modified. The alias for the JDBC Pool must not change after creating the pool.

Action

Specify the same JDBC Pool alias in the request, or remove it.


SPMCFGE0128 Configuration of type COMMON-JNDI is null.
Explanation

The configuration object for COMMON-JNDI is null.

Action

Specify the valid configuration object for COMMON-JNDI.


SPMCFGE0129 Configuration of type COMMON-JNDI should have one JNDI element.
Explanation

A configuration of type COMMON-JNDI should have one JNDI element.

Action

Provide one JNDI element for this configuration.


SPMCFGE0130 Configuration of type COMMON-JNDI should have JNDI element with valid alias.
Explanation

A configuration of type COMMON-JNDI should have a JNDI element with a valid alias.

Action

Provide URL friendly alias for the JNDI element.


SPMCFGE0131 Configuration of type COMMON-JNDI should have JNDI element with unique alias.
Explanation

A configuration of type COMMON-JNDI should have a JNDI element with a unique alias.

Action

Provide a unique alias for the JNDI element.


SPMCFGE0132 Error occurred while retrieving the JNDI configuration instances.
Explanation

An error occurred while retrieving the JNDI configuration instances.

Action

See the Platform Manager logs for mode details.


SPMCFGE0133 Provide a URL for the specified JNDI provider type.
Explanation

The URL for the specified JNDI provider type is missing.

Action

Specify the URL for the specified JNDI provider type.


SPMCFGE0134 Provide Initial Context Factory for the specified JNDI provider type.
Explanation

The specified JNDI provider type does not have an Initial Context Factory.

Action

Specify the Initial Context Factory for the specified JNDI provider type.


SPMCFGE0135 DbFunctional alias was not found.
Explanation

A DbFunctional alias with the specified alias value could not be found.

Action

Check if a DbFunctional alias with the provided alias value is available.


SPMCFGE0136 Element value is not set.
Explanation

The value of an integral element has not been set.

Action

Ensure that the specified data contains valid values for all required elements.


SPMCFGE0137 Invalid DbFunctional alias.
Explanation

The provided DbFunctional alias is invalid.

Action

Check the provided DbFunctional alias for invalid characters.


SPMCFGE0138 Duplicate DbFunctional alias.
Explanation

The provided alias already exists.

Action

Provide a new alias.


SPMCFGE0139 Invalid Pool alias.
Explanation

The provided Pool alias is invalid.

Action

Provide a new Pool alias.


SPMCFGE0140 Problem detected while trying to read/write DbFunctional alias data.
Explanation

The read/write operation failed.

Action

Check if the DbFunctional alias data file is available.


SPMCFGE0141 Configuration of type COMMON-JMS should have JMS element with valid alias.
Explanation

A configuration of type COMMON-JMS should have a JMS element with a valid alias.

Action

Specify a URL friendly alias for the JMS element.


SPMCFGE0142 Configuration of type COMMON-JMS is null.
Explanation

Configuration object for COMMON-JMS is null.

Action

Specify the valid configuration object for COMMON-JMS.


SPMCFGE0143 Configuration of type COMMON-JMS should have a JMS element.
Explanation

A configuration of type COMMON-JMS should have a JMS element.

Action

Specify a JMS element for this configuration.


SPMCFGE0144 Provide URL for the specified JMS provider type.
Explanation

The URL for the specified JMS provider type is missing.

Action

Provide a URL for the specified JMS provider type.


SPMCFGE0145 Provide an existing JNDI alias for the specified JMS provider type.
Explanation

The JNDI alias provided for the specified JMS provider type does not exist.

Action

Provide an existing JNDI alias for the specified JMS provider type.


SPMCFGE0146 The provided JNDI alias does not exist. Provide an existing JNDI alias for the specified JMS provider type.
Explanation

The JNDI alias provided for the specified JMS provider type does not exist.

Action

Provide an existing JNDI alias for the specified JMS provider type.


SPMCFGE0147 Configuration of type COMMON-JMS should have JMS element with unique alias.
Explanation

A configuration of type COMMON-JMS should have a JMS element with a unique alias.

Action

Provide unique alias for the JMS element.


SPMCFGE0148 Error occurred while retrieving the JMS configuration instances.
Explanation

An error occurred while retrieving the JMS configuration instances.

Action

See the Platform Manager logs for mode details.


SPMCFGE0149 ConfigurationUiBindingService is not set.
Explanation

The ConfigurationUiBindingService is not set.

Action

Register the ConfigurationUiBindingService.


SPMCFGE0150 Configuration ui binding for {0} runtimeComponent and {1} configurationType cannot be retrieved.
Explanation

The configuration user interface binding cannot be retrieved because of incorrect search parameters or incorrect SPI implementation.

Action

Provide a valid runtimeComponent ID and configurationType ID or check the SPI implementation.


SPMCFGE0151 Error occured while trying to unmarshal ui binding XML data.
Explanation

An error occured while trying to unmarhall the user interface binding XML data.

Action

Check if the XML file is well-formed and valid.


SPMCFGE0152 Error occurred while trying to parse XSD Schema.
Explanation

An error occurred while trying to parse the XSD Schema.

Action

Check if the XSD schema is valid.


SPMCFGE0153 Client group for webMethods Messaging alias is invalid or not specified.
Explanation

While configuring webMethods Messaging alias, if provider type is Broker, Client Group cannot be empty.

Action

Provide a valid Client Group while configuring webMethods Messaging alias.


SPMCFGE0154 Broker messaging alias must have valid authentication configuration.
Explanation

If the webMethods Messaging alias provider is Broker, you must specify valid authentication configuration.

Action

Provide a valid authentication while configuring webMethods Messaging alias.


SPMCFGE0155 Broker Messaging alias must have a valid user.
Explanation

While configuring webMethods Messaging alias, if provider type is Broker, you must specify a valid user.

Action

Provide a valid user while configuring webMethods Messaging alias.


SPMCFGE0156 Broker Messaging alias must have a valid password.
Explanation

When the messaging alias provider is Broker, the alias should have a valid password.

Action

Provide a valid password for a messaging alias with provider type Broker.


SPMCFGE0157 Broker Messaging alias must have a valid keystore definition.
Explanation

When the messaging alias provider is Broker, it should have valid keystore definition.

Action

Provide a valid keystore for a messaging alias with provider type Broker.


SPMCFGE0158 Broker Messaging alias must have a valid encryption definition.
Explanation

When the messaging alias provider is Broker, the alias should have a valid encryption definition.

Action

Provide a valid encryption definition for a messaging alias with provider type Broker.


SPMCFGE0159 Specify at least one server log facility to be updated.
Explanation

When updating the server logger, you must specify at least one server log facility.

Action

Ensure that you specify a server log facility.


SPMCFGE0160 While updating a global variable, you can modify only the value for the global variable.
Explanation

You attempted to modify the key while updating a global variable. You can modify only the value for the global variable.

Action

Ensure that you modify only the value for the global variable.


SPMCFGE0161 Configuration of type COMMON-LOCAL-USERS should have User element with a valid id.
Explanation

The User element should have an ID that contains only URL friendly symbols.

Action

Provide URL friendly ID for the User element.


SPMCFGE0162 Configuration of type COMMON-LOCAL-USERS should have one User instance.
Explanation

Configuration of type COMMON-LOCAL-USERS should have one User instance.

Action

Provide one User element for this configuration.


SPMCFGE0163 Configuration of type COMMON-LOCAL-USERS should have User element with unique id.
Explanation

The ID should be unique among all configurations of type COMMON-LOCAL-USERS.

Action

Provide a unique ID for the User element.


SPMCFGE0164 Retrieving COMMON-LOCAL-USERS configuration instances failed.
Explanation

An error occurred while retrieving the configuration instances of type COMMON-LOCAL-USERS.

Action

Check the error logs for more information.


SPMCFGE0165 Configuration of type COMMON-LOCAL-USERS should have password.
Explanation

A password is required for the User element, but it is missing.

Action

Provide a password for the User.


SPMCFGE0166 The User element id for existing configuration of type COMMON-LOCAL-USERS cannot be updated.
Explanation

User ID cannot be changed on update operation.

Action

Use the the same User ID from the existing configuration.


SPMCFGE0167 Configuration of type COMMON-CLUSTER is null.
Explanation

The configuration object for COMMON-CLUSTER is null.

Action

Specify the valid configuration object for COMMON-CLUSTER.


SPMCFGE0168 The provided server name should be unique within the landscape.
Explanation

The provided server name already exists in the landscape.

Action

Provide a server name that is unique within the landscape.


SPMCFGE0169 Error occurred while retrieving the COMMON-CLUSTER configuration instances.
Explanation

An error occurred while retrieving the COMMON-CLUSTER configuration instances.

Action

See the Platform Manager logs for mode details.


SPMCFGE0170 Path to the internal user repository file cannot be found.
Explanation

File {0} does not exist.

Action

Specify a valid path to the user.txt file relative to profile or product suite directories.


SPMCFGE0171 User does not exist.
Explanation

User with id {0} is not found in the User repository file.

Action

Try to refresh the configuration metadata.


SPMCFGE0172 One of the existing servers has changed name.
Explanation

One of the existing servers has a changed name.

Action

The names of existing servers should not change.


SPMCFGE0173 Invalid value of Init Size.
Explanation

Only positive integers are allowed.

Action

Provide Init Size greater than zero.


SPMCFGE0174 Path to users.txt not specified.
Explanation

The path to the users.txt file is not specified in the component XML data.

Action

Specify a property named "usersRepoPath" with a value relative to profile or Software AG installation directories.


SPMCFGE0175 Missing or invalid ProxyServer alias.
Explanation

The ProxyServer alias is missing or invalid.

Action

Provide a valid ProxyServer alias.


SPMCFGE0176 Protocol or Host value is not set.
Explanation

The value of a required element (Host or Protocol) has not been set.

Action

Ensure that the specified data contains valid values for Host and Protocol.


SPMCFGE0177 Duplicate ProxyServer alias.
Explanation

The provided alias already exists.

Action

Provide a new alias.


SPMCFGE0178 Invalid Protocol value.
Explanation

The provided Protocol value is invalid.

Action

Provide a valid Protocol value.


SPMCFGE0179 Invalid Host value.
Explanation

The provided Host value is invalid.

Action

Provide a valid Host value.


SPMCFGE0180 Problem detected while trying to read/write Proxy data.
Explanation

The read/write operation failed.

Action

Check if the Proxy data file is available.


SPMCFGE0181 Invalid value of Max Size.
Explanation

Only positive integers greater than Init Size are allowed.

Action

Provide Max Size greater than zero and greater than Init Size.


SPMCFGE0182 Error in configuration changed event handler for run-time component {0}.
Explanation

An event was raised but most likely this run-time component does not exist anymore.

Action

Change the configuration for existing run-time components.


SPMCFGE0183 Missing or invalid Component Endpoint alias.
Explanation

The Component Endpoint alias is missing or invalid.

Action

Provide a valid Component Endpoint alias.


SPMCFGE0184 Duplicate Component Endpoint alias.
Explanation

The provided alias already exists.

Action

Provide a new unique alias.


SPMCFGE0185 Problem detected while trying to read/write configuration data.
Explanation

The read/write operation failed.

Action

Check if the configuration data file is available.


SPMCFGE0186 There is no existing ProxySettings configuration instance with the provided ProxyAlias.
Explanation

The provided ProxyAlias was not found in the existing ProxySettings aliases.

Action

Provide existing ProxyAlias.


SPMCFGE0187 There is no existing Keystore configuration instance with the provided KeystoreAlias.
Explanation

The provided KeystoreAlias was not found in the existing Keystore aliases.

Action

Provide existing KeystoreAlias.


SPMCFGE0188 There is no existing Truststore configuration instance with the provided TruststoreAlias.
Explanation

The provided TruststoreAlias was not found in the existing Truststore aliases.

Action

Provide existing TruststoreAlias.


SPMCFGE0189 Missing or empty BASIC authentication user.
Explanation

The BASIC authentication user is missing or empty.

Action

Provide BASIC authentication user.


SPMCFGE0190 Either KeystoreAlias or KeystoreDefinition can be specified, but not both.
Explanation

Either KeystoreAlias or KeystoreDefinition can be specified, but not both at the same time.

Action

Provide either KeystoreAlias or KeystoreDefinition.


SPMCFGE0191 Either TrustoreDefinition or TruststoreAlias can be used, but not both.
Explanation

Either TrustoreDefinition or TruststoreAlias can be used, but not both at the same time.

Action

Provide either TrustoreDefinition or TruststoreAlias.


SPMCFGE0193 The "configuration" property is not set.
Explanation

The "configuration" property defines where the proxy settings are stored.

Action

Set the "configuration" property.


SPMCFGE0194 This configuration instance is not intended to be deleted.
Explanation

This configuration can only be modified.

Action

Modify the configuration instead of deleting it.


SPMCFGE0195 Configuration password decryption failed. The provided value for shared secret is incorrect.
Explanation

Decrypting the configuration password has failed. The value specified for the shared secret is incorrect.

Action

Check if the values for shared secret on Command Central and Platform Manager are the same.


SPMCFGE0196 The server cannot be null.
Explanation

The creation of a cluster configuration requires servers.

Action

Specify at least one server.


SPMCFGE0197 Wrong configuration ID.
Explanation

The configuration ID is not recognized.

Action

Re-try using a valid configuration ID.


SPMCFGE0198 LDAP configuration file not found.
Explanation

An LDAP configuration file with the specified alias is not found.

Action

Specify a valid configuration instance ID.


SPMCFGE0199 Configuration {0} can not be deleted.
Explanation

The configuration file can not be deleted.

Action

Make sure that a configuration with the specified alias exists.


SPMCFGE0201 Error while processing jaas.config entries.
Explanation

Cannot store the JAAS configuration file.

Action

Check the wrapper log for details about the error.


SPMCFGE0202 {0} process finished with error code "{1}".
Explanation

CMD: {2}, OUTPUT: {3}

Action

Check the upgrade and migration help for the product.


SPMCFGE0204 There is no existing Credentials configuration instance with the provided alias {0}.
Explanation

The specified alias {0} was not found in the existing credentials configuration instances.

Action

Specify an existing credentials alias.


SPMCFGE0205 Credentials configuration file not found.
Explanation

A credentials configuration file with the specified alias is not found.

Action

Specify a valid configuration instance ID.


SPMCFGE0206 Specified alias is reserved for default credentials and cannot be used.
Explanation

The default credentials have reserved aliases, such as NONE, TRUSTED or DEFAULT_ADMINISTRATOR.

Action

Specify a valid alias.


SPMCFGE0207 Configuration instance with alias {0} does not exist.
Explanation

The specified configuration instance does not exist.

Action

Specify a valid alias of an existing configuration instance.


SPMCFGE0209 Proxy configuration file not found.
Explanation

The configuration instance ID is not valid.

Action

Specify a valid configuration instance ID.


SPMCFGE0210 A realm with the same name already exists.
Explanation

A JAAS realm with the same name already exists.

Action

Specify a unique realm name.


SPMCFGE0212 Installation name {0} may not contain "{1}".
Explanation

The specified installation name {0} contains the reserved character sequence "{1}".

Action

Remove the character sequence "{1}" from the installation name.


SPMCFGE0213 Missing or invalid port number. A positive number is expected.
Explanation

The specified value must be a positive number.

Action

Specify a positive number.


SPMCFGE0214 A configuration of type COMMON-CREDENTIALS should have a CommonCredentials element with a valid alias.
Explanation

A configuration of type COMMON-CREDENTIALS should have a CommonCredentials element with a valid alias.

Action

Provide a URL-friendly alias for the CommonCredentials element.


SPMCFGE0215 Configuration Type {1} is not implemented for Runtime Component {0}.
Explanation

Platform Manager could not find a registered ConfigurationSerializer for Configuration Type {1} and Runtime Component {0}.

Action

Register a ConfigurationSerializer and a ConfigurationManager SPIs implementation that can handle Configuration Type {1} and Runtime Component {0}.


SPMCFGE0216 No shared secret is configured.
Explanation

Shared secret is required for encryption of sensitive information.

Action

Configure a shared secret for all Command Central environments.


SPMCFGE0217 Configuration of type COMMON-CREDENTIALS should have a username specified.
Explanation

Configuration of type COMMON-CREDENTIALS should have a username specified.

Action

Specify a username for COMMON-CREDENTIALS.


SPMCFGE0218 Alias cannot be empty.
Explanation

Alias cannot be empty.

Action

Provide an alias.


SPMCFGE0219 Alias "{0}" cannot be changed.
Explanation

The alias must be "{0}".

Action

Do not change the alias.


SPMCFGE0220 COMMON-CREDENTIALS configuration with alias "{0}" already exists.
Explanation

COMMON-CREDENTIALS configuration with alias "{0}" already exists.

Action

Provide a COMMON-CREDENTIALS configuration with a different alias.


SPMCFGE0221 Invalid file path.
Explanation

Invalid file path.

Action

Check the specified {0} file path.


SPMCFGE0222 Deleting {0} credentials is not allowed.
Explanation

Deleting Administrator credentials is not allowed.

Action

If changes are required, edit the credentials configuration.


SPMCFGE0223 The administrator password for the {0} credentials does not match the required complexity rules.
Explanation

The password does not match the required complexity rules.

Action

Provide an Administrator password that matches the required complexity rules.


SPMCFGI0108 No primary or HTTPS ports are found for {0} component and its parent/child relations.
Explanation

No primary or HTTPS ports were found for {0} component and its parent/child relations.

Action

Check configured and available ports for availability and collisions.


SPMCFGW0029 The validator with the given type is not able to instantiate a KeyStore.
Explanation

The validator with the given type is not able to instantiate a KeyStore.

Action

Provide the correct certificate information.


SPMCFGW0030 An exception occurred when trying to load the keystore certificate.
Explanation

The NoSuchAlgorithmException exception occurred when trying to load the keystore certificate.

Action

Provide the correct certificate information.


SPMCFGW0031 An exception occurred while trying to load the keystore certificate.
Explanation

The CertificateException exception occurred while trying to load the keystore certificate.

Action

Provide the correct certificate information.


SPMCFGW0032 An exception occurred when trying to load the keystore certificate.
Explanation

The IOException exception occurred when trying to load the keystore certificate.

Action

Provide the correct certificate information.


SPMCFGW0033 An exception occurred when trying to load the keystore certificate.
Explanation

The URISyntaxException exception occurred when trying to load the keystore certificate.

Action

Provide the correct certificate information.


SPMCFGW0034 The file location provided in the truststore could not be found.
Explanation

The file location provided in the truststore could not be found.

Action

Provide the correct certificate information.


SPMCFGW0035 An exception occurred when trying to load the truststore certificate.
Explanation

The KeyStoreException exception occurred when trying to load the truststore certificate.

Action

Provide the correct certificate information.


SPMCFGW0036 An exception occurred when trying to load the certificate.
Explanation

The NoSuchAlgorithmException exception occurred when trying to load the certificate.

Action

Provide the correct certificate information.


SPMCFGW0037 An exception occurred when trying to load the certificate.
Explanation

The CertificateException exception occurred when trying to load the certificate.

Action

Provide the correct certificate information.


SPMCFGW0038 The validator could not load the certificate because of an exception.
Explanation

The validator could not load the certificate when trying to load the certificate because of the IOException exception.

Action

Provide the correct certificate information.


SPMCFGW0039 URI syntax provided is incorrect.
Explanation

The URISyntaxException occurred when trying to load the certificate.

Action

Provide the correct certificate information.


SPMCFGW0057 JDBC Driver cannot be loaded.
Explanation

JDBC Driver is not installed.

Action

Verify that the specified JDBC Driver is installed. For more information, see the Command Central documentation.


SPMCFGW0083 The path of the log file {0} is not fully qualified.
Explanation

The specified log file path is not fully qualified.

Action

Provide the absolute path for the log file.


SPMCFGW0104 Could not perform configuration validation for {0} because {1} error was encountered.
Explanation

Could not perform configuration validation for {0} because {1} error was encountered.

Action

Retry the action.


SPMCFGW0113 The specified port is already bound by configuration instance {0} of runtime {1} and is not enabled.
Explanation

The specified port is already bound by configuration instance {0} of runtime {1} and is not enabled.

Action

Change the port number and retry.


SPMCFGW0116 The specified port {0} is already in use by another configuration instance.
Explanation

The specified port {0} is already in use by configuration instance {1} of runtime {2}, but it is either not enabled, or on a different bind address.

Action

Specify a different port number.


SPMCFGW0203 Advanced Memory settings are deprecated.
Explanation

Using the COMMON-MEMORY configuration type to set up advanced memory settings is deprecated.

Action

Use the COMMON-JVM-OPTIONS configuration type to configure the advanced memory settings.


SPMCFGW0211 JDBC Driver Class is required for validation.
Explanation

Default JDBC Driver not found for Database Server Type {0}. JDBC Driver Class is required for performing validation.

Action

Please specify the JDBC Driver in your JDBC Settings configuration and make sure that the specified Driver is installed. For more information, see the Command Central documentation.


SPMCFRE0000 The content of the response is not acceptable according to the accept headers
Explanation

The content of the response is not acceptable according to the accept headers.

Action

Check the response and the accept headers.


SPMCFRE0001 Unexpected exception occured.
Explanation

Unexpected exception occured.

Action

Check the logs.


SPMCFRE0002 Configuration partial failure for runtime component: {0}, instance: {1} with type {2} - with linked exception:
Explanation

Configuration partial failure for runtime component: {0}, instance: {1} with type {2} - with linked exception:

Action

Check the logs.


SPMCFRE0003 ConfigurationSerializersRegistry is not available.
Explanation

ConfigurationSerializersRegistry is not available.

Action

Contact Software AG Global Support.


SPMCFRE0004 ConfigurationSerializer SPI could not be found for RuntimeComponentId "{0}" and ConfigurationTypeId "{1}" .
Explanation

Platform Manager could not find a registered ConfigurationSerializer that can handle ConfigurationInstances with these properties.

Action

Register a ConfigurationSerializer SPI implementation that can handle ConfigurationInstances with these properties.


SPMCFRE0005 A ConfigurationTypeId "{0}" doesn't exist for RuntimeComponentId "{1}" .
Explanation

There is not registered ConfigurationType with the provided ID for the required RuntimeComponent.

Action

Provide valid ConfigurationTypeId for the required RuntimeComponent.


SPMCFRE0006 Configuration Service cannot handle Configuration Model "{0}". Supported models are: {1}. Check Configuration Type "{2}" definition.
Explanation

Most likely there is an error in the definition of the Configuration Type SPI in the respective product plug-in.

Action

Check the Configuration Type "{2}" definition.


SPMCLTE0014 ConfigurationSerializer SPI could not be found for RuntimeComponentId "{0}" and ConfigurationTypeId "{1}" .
Explanation

Platform Manager could not find a registered ConfigurationSerializer that can handle ConfigurationInstances with these properties.

Action

Register a ConfigurationSerializer SPI implementation that can handle ConfigurationInstances with these properties.


SPMCLTE0015 Authentication call to SPM failed to execute.
Explanation

Authentication call to SPM failed to execute.

Action

Make sure that the user has valid access rights to the service.


SPMCLTE0016 Cannot retrieve the delegated assertion for the current user.
Explanation

Cannot retrieve the delegated assertion for the current user.

Action

Check if the user has valid delegated rights.


SPMCLTE0017 Internal Error processing Platform Manager request
Explanation

The server encountered an error and it cannot complete the request.

Action

Contact your system administrator.


SPMCLTE0018 The specified runtime component {0} could not be found on node {1}.
Explanation

There is no component called {0} registered for node {1}. The data could not be retrieved.

Action

Check the components for Platform Manager node {1}.


SPMCLTE0020 {0} is not a valid type for the runscript request
Explanation

The type for the runscript request is not valid. Valid types are fix or product.

Action

Resubmit the request with a valid type.


SPMCLTE0021 No artifacts specified in uninstall request
Explanation

The unistall request does not specify any products or fixes.

Action

Resubmit the request with a valid list of products and fixes.


SPMCLTE0022 Invalid artifact type for uninstall
Explanation

The artifact type must be product or fix.

Action

Specify valid artifacts in the request.


SPMCLTE0023 Invalid repository type: {0}
Explanation

The specified repository type is not supported.

Action

Use fix or product as the repository type.


SPMCLTE0024 No such repository: {0}
Explanation

The repository does not exist.

Action

Specify a valid repository.


SPMCLTE0025 Unsupported repository type: {0}
Explanation

Fix and product are the only supported repository types.

Action

Use fix or product as the repository type.


SPMCLTE0026 Unsupported repository type: {0}
Explanation

Fix and product are the only supported repository types.

Action

Specify a valid repository type.


SPMCLTE0027 The response cannot be converted to java.util.Properties: {0}
Explanation

The response does not comply with the java.util.Properties text or XML format.

Action

Make sure the format is correct or contact Software AG Global Support.


SPMCLTE0028 {0} is not a valid type for the install request.
Explanation

The type for the install request is not valid. Valid types are fix or product.

Action

Resubmit the request with a valid type.


SPMCLTE0030 Failed to store license metering time stamp.
Explanation

The products on the platform {0} were metered by the license metering tool of Command Central, but the time stamp when this metering was performed by node {1} could not be stored.

Action

Make sure that the harddisc on the specified server is not full or contact Software AG Global Support.


SPMCLTE0031 Remote task failed: {0}
Explanation

Remote task failed: {0}

Action

Check the corresponding Platform Manager logs for more details about the error.


SPMCLTI0009 Internal Server Error
Explanation

Internal server error.

Action

Make sure that the required services are running, communication channels are accessible, and parameters are valid.


SPMCLTI0010 Unknown Error
Explanation

An unspecified error occured during communication.

Action

Make sure that the required services are running, communication channels are accessible, and parameters are valid.


SPMCLTI0011 Error occurred during execution of the command!
Explanation

An error occured during communication.

Action

Make sure that the required services are running, communication channels are accessible, and parameters are valid.


SPMCLTW0001 An exception has occured while retrieving remotely RuntimeStatus from: {0}
Explanation

This might be happenning due to a number of reasons, such as missing monitoring implementation in the product plugin, network interference, and others.

Action

See detailed stack trace in order to define the actual reason for this exception.


SPMCOME0000 {0} is unknown runtime component.
Explanation

This component ID does not exist.

Action

Use runtimeComponentId that already exists.


SPMCOME0001 {0} is an unknown product.
Explanation

The required productId does not exist in the list of InventoryService.getInstalledProducts()

Action

Use a productId of a product that is already installed.


SPMCOME0002 No available implementation for {0}.
Explanation

Displayed status of a product plug-in after calling a specific operation that is not available.

Action

Use an available operation.


SPMCOME0003 The PortSettings XML cannot be empty.
Explanation

The PortSettings XML response cannot be empty.

Action

Add data in the PortSettings XML response.


SPMCOME0004 PortSettings contains property keys that do not match properties in the config.ini file.
Explanation

PortSettings contains property keys that do not match properties in the config.ini file.

Action

Check the property keys and try to find the matching one or fix the config.ini file.


SPMCOME0005 Load configuration error.
Explanation

Indicates issues with reading/writing a configuration.

Action

Fix any issues related to reading or writing the configuration.


SPMCOME0006 Unexpected exception.
Explanation

An unexpected exception occurred while reading/writing a configuration.

Action

Fix the unexpected exception.


SPMCOME0007 Un-handled internal server error. {0}
Explanation

A Platform Manager Exception occurred.

Action

Resolve the exception.


SPMCOME0010 Error:
Explanation

This is most likely an error that is not expected.

Action

None.


SPMCOME0017 Provided configuration is not valid.
Explanation

The provided configuration does not comply with the rules for the specified configuration type.

Action

Check the provided configuration for errors and rule violations.


SPMCOME0018 Unexpected component status: {0} but should have one of {1}
Explanation

The requested operation cannot be completed because the component cannot do the operation in its current runtime status.

Action

Ensure that the component is in one of the expected statuses to complete this operation. For ONLINE status, start the parent runtime instance.


SPMCOME0020 A Configuration instance with ID = {0} does not exist.
Explanation

A Configuration instance with the provided ID does not exist.

Action

Use the ID of an existing Configuration instance.


SPMCOME0029 Server did not find anything matching the request URI.
Explanation

There is no resource for this URI.

Action

Check if the URI is correct. Check if the resource IDs are valid.


SPMCOME0030 The request cannot be understood by the server.
Explanation

Inconsistent or empty body.

Action

Do not retry without modifications of the request.


SPMCOME0031 The request is not acceptable as stated in the accept headers.
Explanation

Platform Manager cannot return the response in the desired format.

Action

Either change the accept headers, or the data format of the response.


SPMCOME0033 The KPI {0} contains invalid data and cannot be created.
Explanation

The error occurs when the RuntimeStateZone can not be calculated. Possible reasons for this issue are that the given values for max, marginal, and normal are null or in the wrong format.

Action

Check the content of the KPI and provide correct data.


SPMCOME0043 Node version is not supported.
Explanation

Command Central connects to an old Platform Manager node.

Action

Remove the old Platform Manager node.


SPMCOME0045 Failed provisioning operation. Status is {0}.
Explanation

The failed operation status is {0}.

Action

Try to correct the issue and retry the operation.


SPMCOME0046 Operation failed due to unsatisfied dependencies: {0}
Explanation

There are missing dependencies.

Action

Try to correct the situation. Retry the operation.


SPMCOME0047 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.


SPMCOME0048 Configuration password decryption failed. The provided value for shared secret is incorrect.
Explanation

Decrypting the configuration password has failed. The value specified for the shared secret is incorrect.

Action

Check if the values for shared secret on Command Central and Platform Manager are the same.


SPMCOME0049 Un-handled internal server error.
Explanation

A Platform Manager Exception occurred.

Action

Resolve the exception.


SPMCOME0051 Cannot connect to the repository due to {0}.
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 URL for the repository are not correct.

Action

Make sure the proxy for the local Platform Manager is configured and the given repository URL is valid. To find the URL, run 'sagcc list repository products properties=*.


SPMCOME0053 Service {0} is not available.
Explanation

The service did not start in time.

Action

Retry the operation or refresh.


SPMCOME0055 Cannot connect to the repository. {0}
Explanation

The selected release is an innovation release to which you do not currently have access.

Action

For more information about the innovation release and how to get access, visit http://empower.softwareag.com/innovationrelease/


SPMCOME0057 Cannot connect to the repository.
Explanation

The repository does not accept the credentials.

Action

Check if you have supplied valid credentials and accepted the license agreement for the specified credentials. The troubleshooting steps are described in the Command Central documentation.


SPMCOME0058 Cannot connect to the repository {0}.
Explanation

The proxy for the local Platform Manager is not configured.

Action

See the Command Central documentation for information on configuring proxies.


SPMCOME0061 Error reading metering data cache file.
Explanation

The metering data cache file could not be read.

Action

Check the access rights to the metering folder.


SPMCOME0062 Error writing to metering data cache file.
Explanation

Writing to the metering data cache file failed.

Action

Check the access rights to the metering folder.


SPMCOME0067 Validation of Configuration Instance {0} for Runtime Component {1} having Configuration Type {2} failed during {3}: {4}
Explanation

The provided configuration does not comply with the rules for the specified configuration type.

Action

Check the provided configuration for errors and rule violations.


SPMCOME0068 Product {0} is not found in product repository {1}
Explanation

The product repository does not contain the specified product and the fix cannot be applied.

Action

Verify that the specified repository contains the product, on which you want to install a fix.


SPMCOME0069 Connection refused to host: {0}
Explanation

The connection to the host was refused.

Action

Verify that at least one enabled JMX port configuration is available.


SPMCOME0070 {0}
Explanation

{1}

Action

{2}


SPMCOMI0008 The command is disabled.
Explanation

Most probably an important OSGi service is not registered.

Action

None.


SPMCOMI0009 No help available.
Explanation

This command does not provide a help message.

Action

None.


SPMCOMI0011 [DISABLED]
Explanation

A command with this info line prefix cannot be executed.

Action

None.


SPMCOMI0032 Unsupported operation.
Explanation

The attempted operation is currently not supported by the Platform Manager server.

Action

Contact you administrator.


SPMCONE0001 Error while loading configuration.
Explanation

An error occurred while loading configuration.

Action

Provide valid arguments.


SPMCONE0006 Error while getting a configuration type.
Explanation

An error occurred while getting a configuration type.

Action

Resubmit the request.


SPMCONE0007 Error during serialization
Explanation

An error occurred during the serialization step.

Action

Resubmit the serialization step.


SPMCONE0013 Error while updating configuration.
Explanation

An error occurred while updating the configuration.

Action

Resubmit the configuration.


SPMCONE0015 Error while getting configuration status.
Explanation

Error while getting configuration status.

Action

Get the configuration status correctly.


SPMCONE0024 Error while getting configuration instances.
Explanation

An error occurred while getting configuration instances.

Action

Resubmit the configuration instances get operation.


SPMCONI0000 The command is not recognized. Type {0} for help.
Explanation

The typed command is not recognized.

Action

Type spm for help.


SPMCONI0002 {0} - get configuration values for the given configuration type
Explanation

Missing configuration values for the given configuration type.

Action

Get configuration values for the given configuration type.


SPMCONI0003 Configuration (JavaModel): {0}
Explanation

Configuration (JavaModel) information.

Action

None.


SPMCONI0004 Configuration (Text): {0}
Explanation

Configuration (Text) information.

Action

None.


SPMCONI0005 No load configuration.
Explanation

No load configuration.

Action

None.


SPMCONI0008 Configuration status: {0}
Explanation

Information about the configuration status.

Action

None.


SPMCONI0009 No configuration status.
Explanation

No configuration status.

Action

None.


SPMCONI0010 The specified resource doesn't exist.
Explanation

The specified resource doesn't exist.

Action

None.


SPMCONI0011 There is no configuration type found for this runtime component.
Explanation

There is no configuration type found for this runtime component.

Action

None.


SPMCONI0012 {0} - Submit configuration and get the configuration status
Explanation

The configuration status is missing or the configuration is not submitted.

Action

Submit the configuration and get the configuration status.


SPMCONI0014 Bad URI - {0}
Explanation

Bad URI is submitted.

Action

None.


SPMCONI0016 Configuration status: {0}
Explanation

Information about the configuration status.

Action

None.


SPMCONI0017 No configuration status.
Explanation

No configuration status.

Action

None.


SPMCONI0018 {0} - query for the current configuration status.
Explanation

A query for the current configuration status.

Action

None.


SPMCONI0019 No configuration instance.
Explanation

No configuration instance.

Action

None.


SPMCONI0020 No configuration instances.
Explanation

No configuration instances.

Action

None.


SPMCONI0021 Configuration Instance description: {0}
Explanation

Configuration Instance description.

Action

None.


SPMCONI0022 Configuration Instance ID: {0}
Explanation

Information about the Configuration Instance ID.

Action

None.


SPMCONI0023 Configuration Instance name: {0}
Explanation

Information about the Configuration Instance name.

Action

None.


SPMCONI0025 {0} - list of the configuration instances for a given runtime component
Explanation

List of the configuration instances for a given runtime component.

Action

None.


SPMCONI0026 JobManagerService is not available.
Explanation

JobManagerService is not available.

Action

None.


SPMCONI0027 Invalid job ID: {0}
Explanation

Information about an invalid job ID.

Action

None.


SPMCONI0028 Number of jobs: {0}
Explanation

Information about the number of jobs.

Action

None.


SPMCONI0029 Job ID: {0}
Explanation

Information about the job ID.

Action

None.


SPMCONI0030 The status of the job with ID ({0}) is {1}.
Explanation

Information about the job status.

Action

None.


SPMCONI0031 The job started at {0}.
Explanation

Information about when the job started.

Action

None.


SPMCONI0032 The job ended at {0}.
Explanation

Information about when the job ended.

Action

None.


SPMCONI0033 The job is still running.
Explanation

The job is still running.

Action

None.


SPMCONI0034 The duration of the job so far is {0} seconds.
Explanation

Information about the duration of the job.

Action

None.


SPMCONI0035 {0} - lists all (not done) jobs or status of a specific job
Explanation

Lists all (not done) jobs or status of a specific job.

Action

None.


SPMCONI0036 {0} - runtime status of the component identified by this ID.
Explanation

Runtime status of the component identified by this ID.

Action

None.


SPMCONI0037 No RuntimeState found for {0}.
Explanation

No RuntimeState found.

Action

None.


SPMCONI0038 {0} - list of the runtime components
Explanation

List of the runtime components.

Action

None.


SPMCONI0039 {0} - list of the installed products
Explanation

List of the installed products.

Action

None.


SPMCONI0040 {0} - starts the runtime component with this ID with safe mode enabled.
Explanation

Starts the runtime component with this ID with safe mode enabled.

Action

None.


SPMCONI0041 {0} - starts the runtime component with this ID with debug mode enabled.
Explanation

Starts the runtime component with this ID with debug mode enabled.

Action

None.


SPMCONI0042 {0} - stops the runtime component with this ID.
Explanation

Stops the runtime component with this ID.

Action

None.


SPMCONI0043 {0} - starts the runtime component with this ID.
Explanation

Starts the runtime component with this ID.

Action

None.


SPMCONI0044 {0} - resumes the runtime component with this ID.
Explanation

Resumes the runtime component with this ID.

Action

None.


SPMCONI0045 {0} - restarts the runtime component with this ID.
Explanation

Restarts the runtime component with this ID.

Action

None.


SPMCONI0046 {0} - pauses the runtime component with this ID.
Explanation

Pauses the runtime component with this ID.

Action

None.


SPMCONI0047 {0} - creates a new configuration instance for a given runtime component and a given configuration type.
Explanation

Creates a new configuration instance for a given runtime component and a given configuration type.

Action

None.


SPMCONI0048 Error during creating configuration
Explanation

Error during creating configuration

Action

None.


SPMCONI0049 {0} - Delete configuration and get the configuration status.
Explanation

Delete configuration and get the configuration status.

Action

Delete configuration and get the configuration status.


SPMCONI0050 ConfigurationSerializer is not found for runtimeComponent with ID: {0} and configurationType with ID: {1}
Explanation

ConfigurationSerializer is not found for runtimeComponent with ID: {0} and configurationType with ID: {1}.

Action

None.


SPMCONI0051 {0} - runtime state of the comonent identified by this ID
Explanation

Runtime state of the comonent identified by this ID

Action

None


SPMCORE0001 Exception handling directory change events.
Explanation

An exception occurred when handling directory change events.

Action

Contact your Command Central Administrator.


SPMCORE0002 Exception processing directory change events.
Explanation

An exception occurred when processing directory change events.

Action

Contact your Command Central Administrator.


SPMCORE0003 The provided observer should not be null.
Explanation

The provided observer should not be null.

Action

Provide a non-null observer to the Directory Watcher infrastructure.


SPMCORE0004 The provided observed directory should not be null.
Explanation

The provided observed directory should not be null.

Action

Provide a non-null observed directory to the Directory Watcher infrastructure.


SPMCORE0005 The provided observed directory change types should not be null or empty.
Explanation

The provided observed directory change types should not be null or empty.

Action

Provide valid observed directory change types to the Directory Watcher infrastructure.


SPMCORE0007 Could not get JMXConnector for runtime component with id {0}
Explanation

The runtime component does not have a configured JMX port, or there was a problem obtaining the configuration.

Action

Check if the runtime component is online and verify that at least one enabled JMX port configuration is available.


SPMCORE0008 Repository configuration under {0} cannot be deleted. Try to delete the file manually.
Explanation

The repository configuration file cannot be deleted.

Action

Delete the file manually and restart Platform Manager


SPMCORE0009 Configuration for repository under {0} is corrupted. Retry the operation.
Explanation

Repository configuration file got corrupted while being stored on disk.

Action

Retry the repository operation.


SPMCORE0010 Connection refused to host: {0}
Explanation

The connection to the host was refused.

Action

Verify that at least one enabled JMX port configuration is available.


SPMCORI0000 TestMessage
Explanation

Test message to be removed.

Action

None.


SPMCTCE0000 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.


SPMDBCE0000 Unsupported parameter name: {0}
Explanation

The parameter name is not supported.

Action

See the Command Central documentation for a list of supported parameters.


SPMDIAE0000 Log source not found: {0}
Explanation

The requested log source does not exist.

Action

Use getLogSources() prior to retrieveLog().


SPMDIAE0001 {0} does not exist or is not a directory.
Explanation

The specified location does not exist or is not a directory.

Action

Provide a location that exists and is a directory.


SPMDIAW0002 Missing 'logDirs' configuration property for DefaultLogAccess service component configuration.
Explanation

An SPM bundle has a LogAccess service component that is missing its 'logDirs' configuraiton property.

Action

The OSGI service configuration must include this property if log files are to be collected.


SPMDIAW0003 {0} cannot be evaluated.
Explanation

The path expression {0} cannot be evaluated.

Action

Make sure the component definition has the correct path expression.


SPMDIAW0004 The instance management service did not return a proper instance name.
Explanation

The default log access component defintion did not provide an instance name regular expression and the instance management service did not return a proper instance name.

Action

Provide an instance name regular expression or a proper implementation of the instance management service.


SPMDIRE0000 {0} not found!
Explanation

A runtime component or a log was not found.

Action

Verify the requested item is really present in the system.


SPMIMGE0000 Product {0} does not support instance management.
Explanation

The Platform Manager plugin for product {0} does not support instance management.

Action

See the Software AG Platform Manager documentation to double check if product {0} supports instance management. If the product supports instance management, contact Software AG Global Support.


SPMIMGE0002 Properties for {0} cannot be returned.
Explanation

A server error occured during properties extraction.

Action

Contact Software AG Global Support.


SPMIMGE0003 {0} cannot be matched against {1}
Explanation

The specified regular expression in the component definition does not match the run-time component ID.

Action

Revise the regular expression in the component definition or contact Software AG Global Support.


SPMIMGE0004 Mandatory property {0} is not specified.
Explanation

A required property in the component definition is missing.

Action

Specify the required property in the component definition.


SPMIMGE0005 Instance management script {0} cannot be resolved.
Explanation

The instance management script was not found on the file system or there is another I\O error.

Action

Make sure the instance management script has the correct name and is in the correct location.


SPMIMGE0007 This instance management command cannot be performed because the following input properites are missing: {0}
Explanation

The input properties are insufficient for performing the requested instance management operation.

Action

Provide the input properties that are missing or contact Software AG Global Support.


SPMIMGE0008 Instance management operation failed with exit code: {0}
Explanation

The execution of the instance management operation failed.

Action

Check the logs for more details or contact SoftwareAG Global Support.


SPMIMGE0009 Instance Management process finished with error code "{0}".
Explanation

CMD: {1}, OUTPUT: {2}

Action

Check the administration documentation for the specified product instance.


SPMIMGE0010 Property [{0}] has an invalid value [{1}].
Explanation

Null or empty values are not allowed.

Action

Provide a valid value and try again.


SPMIMGE0011 The properties for {0} cannot be returned because the thread was interrupted.
Explanation

A server error occured while extracting the properties.

Action

Try again. If the error persists, contact Software AG Global Support.


SPMIMPE0000 Unable to locate configuration source property for persistent ID: {0}; configuration properties for this PID are: {1}.
Explanation

Most probably the persistent ID configuration is not provided by Dynamic Configurator.

Action

Provide the persistent ID using Dynamic Configurator.


SPMIMPE0001 The configuration source location for the persistent ID {0} is not a valid URL: {1}
Explanation

The configuration source location is not a valid URL.

Action

Dynamic Configurator should point to a valid URL for the given persistent ID.


SPMIMPE0020 The CC asset {0} does not contain the required {1} file.
Explanation

The asset does not contain file that is requied for the install asset operation.

Action

Check if the asset was built correctly.


SPMINRI0000 Nothing found for ID = {0}
Explanation

Nothing found for this ID.

Action

None.


SPMINRI0001 Inventory Service is not set.
Explanation

Inventory Service is not set.

Action

None.


SPMINVI0000 Product cannot be null.
Explanation

Product cannot be null.

Action

None.


SPMINVI0001 Category cannot be null.
Explanation

Category cannot be null.

Action

None.


SPMINVI0002 ID must start with productId.
Explanation

ID must start with productId.

Action

None.


SPMJBRE0000 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: /spm/jobmanager/jobs


SPMJOBE0001 Maximum number of non-done jobs reached. Try again later or increase {2}. Current jobs: {0} max jobs: {1}.
Explanation

The job manager queue is full and new jobs cannot be scheduled.

Action

Wait a few moments or increase com.softwareag.platform.management.jobmanager.impl.Configuration.SYS_PROP_MAX_JOBS.


SPMJOBE0002 Job sequence exhausted. Try again later or set a bigger {0}
Explanation

All job sequence IDs have been consumed.

Action

Wait a few moments or set a bigger com.softwareag.platform.management.jobmanager.impl.Configuration.SYS_PROP_JOB_SEQUENCE_MAX_SIZE.


SPMJOBE0003 Job {0} failed!
Explanation

The task being carried out by this job has failed.

Action

Inspect the logs to troubleshoot the problem or contact SoftwareAG Global Support.


SPMJOBI0000 This job is done or not available due to a problem.
Explanation

The Null Job status.

Action

None.


SPMLCCE0000 runtimeComponentId for productId {0} is null.
Explanation

The AdvancedLifecycleOperations service is registered in with productID that does not contain the given runtimeComponentId.

Action

Make sure that your product plugin has correct productId and runtimeComponentId IDs.


SPMLCCE0001 Runtime component "{0}" does not support life cycle operation "{1}".
Explanation

This Runtime component does not support the specified life cycle operation.

Action

Make sure you execute life cycle operations supported by this run-time component.


SPMLCCE0015 The run-time status of runtimeComponent {0} is not {1}.
Explanation

The lifecycle operation did not complete as expected.

Action

Check the logs for details about the error.


SPMLCCE0016 Runtime status of component with id: {0} can not be retrieved or component is not stopped on time.
Explanation

The run-time status of the component with id: {0} can not be retrieved on time.

Action

Check the logs for details about the error.


SPMLCCE0032 The runtimeComponent with id: {0} does not have LifeCycleOperations SPI registered.
Explanation

A LifeCycleOperations SPI has not been found for runtimeComponent : {0}

Action

Check the component definition, used for registering the SPI.


SPMLCCE0041 Runtime component {0} did not become online.
Explanation

The runtime component did not become online.

Action

Check the runtime component logs.


SPMLCCE0042 Restart job with ID {0} finished with a status error.
Explanation

The restart job finished with status error.

Action

Check the logs for details about the restart job.


SPMLCCE0043 The thread was interrupted while waiting for runtime status.
Explanation

Checking the runtime status of a component was interrupted.

Action

Check the logs for JVM errors.


SPMLCCE0044 An exception occurred while obtaining the runtime status.
Explanation

An exception occured while checking the runtime status of a component.

Action

Check the SPM logs for system errors.


SPMLCCE0045 The thread was interrupted while setting a runtime status.
Explanation

Checking the runtime status of a component was interrupted.

Action

Check the logs for JVM errors.


SPMLCRE0000 The lifecycle operation to execute is unknown.
Explanation

The operation is not a part of the predefined list of lifecycle operations that can be executed: start, stop, restart, pause, resume, start in debug, and start in safe mode.

Action

Specify an operation from the predefined list.


SPMMICE0000 Extracting source version failed.
Explanation

Failed to extract the source version from the bundles.info file.

Action

Ensure that the bundles.info file is at the correct location.


SPMMONE0000 Could not get JMXConnector for runtime component with id {0} because JMX port configuration was not found.
Explanation

This particular run-time component does not have a configured JMX port or there was a problem obtaining the configuration.

Action

Check if the run-time component is online and that at least one enabled JMX port configuration is available.


SPMMWSE0000 Provide "sysadmin" credentials in CCE for "{0}"
Explanation

When BASIC authentication is used, credentials for the "sysadmin" user must be supplied in Command Central for the My webMethods Server component.

Action

Verify that BASIC authentication for the My webMethods component uses credentials for "sysadmin" user.


SPMMWSE0002 Primary port not set for {0}
Explanation

A primary port is required to connect to My webMethods Server.

Action

Provide primary port value for {0}.


SPMMWSE0003 Invalid URI
Explanation

The supplied URI for connection to My webMethods Server does not have a valid syntax according to RFC 3986.

Action

Verify that the correct hostname and port are provided.


SPMMWSE0004 An error occurred while constructing the URL
Explanation

The connection URL to My webMethods Server is malformed.

Action

Verify that the correct hostname and port are provided.


SPMMWSE0005 Root context path ''{0}'' is invalid.
Explanation

The context path may start with a slash and can contain only the following characters: uppercase or lowercase letters, decimal digits, hyphen, period, and underscore.

Action

Verify that the root context path contains only valid characters.


SPMMWSE0006 Invalid credentials set for user "sysadmin"
Explanation

The password supplied for the "sysadmin" user is not correct.

Action

Provide the correct password for the "sysadmin" user in the authentication information in Command Central.


SPMMWSE0007 First Name is required
Explanation

The First Name field must not be empty.

Action

Enter a first name.


SPMMWSE0008 Last Name is required
Explanation

The Last Name field must not be empty.

Action

Enter a last name.


SPMMWSE0009 Unable to find server log directory: {0}
Explanation

Unable to read the server log directory path from systemPaths.properties

Action

Check if there is a connection to the My webMethods Server database.


SPMMWSE0010 Encryption failed for: {0}
Explanation

The encryption of a value failed.

Action

Contact Software AG Global Support. Provide the logs for Platform Manager and My webMethods Server and the reproduction steps for the issue.


SPMMWSE0011 Decryption failed for: {0}
Explanation

The decryption of a value failed.

Action

Contact Software AG Global Support. Provide the Platform Manager and My webMethods Server logs and the reproduction steps of the issue.


SPMMWSE0012 Primary datasource cannot be deleted
Explanation

You cannot delete the primary My webMethods Server database connection datasource.

Action

None required.


SPMMWSE0013 Adding a Derby data source is not supported
Explanation

My webMethods Server does not support additional Derby data sources.

Action

Add a datasource of one of the supported database types.


SPMMWSE0014 Missing or invalid db.xml
Explanation

A My webMethods Server system configuration file is either missing or invalid.

Action

Contact the My webMethods Server system administrator.


SPMMWSE0015 Only TRUSTED and BASIC authentication are supported
Explanation

The specified authentication is not supported.

Action

Change authentication to TRUSTED or BASIC.


SPMMWSE0030 Please enter a valid email address.
Explanation

An invalid email address was entered.

Action

Enter a new email address.


SPMOGIE0000 Could not obtain the runtime component id from "cplm" file: {0}
Explanation

There was a problem obtaining metadata information about a specific profile.

Action

Check the profile folder structure and if cplm.xml contains any errors.


SPMOGIE0002 Following exception occured "{0}" while parsing "{1}".
Explanation

One of the profiles contains wrong metadata.

Action

Check listed file for errors.


SPMOGIE0003 The Common Platform Lifecycle Management (cplm-v.xml) file is malformed.
Explanation

The profile metadata file contains errors.

Action

Try to check cplm.xml file for errors in the specific profile.


SPMOGIE0005 Operation "{0}" is not defined in the "cplm" file.
Explanation

There was lifecycle operation for the specific component that is not defined inside cplm.xml.

Action

Try to repair cplm.xml file in the component profile folder.


SPMOGIE0008 Common Platform Lifecycle Management (cplm-v.xml) file not found!
Explanation

A file called cplm.xml is expected inside the profile folder.

Action

Try to create cplm.xml file for the component.


SPMOGIE0009 Configuration with version "{0}" was not found in the metadata file.
Explanation

No configuration with the specified version exists inside the cplm.xml file.

Action

Check the profile folder for cplm.xml and make sure it is up to date.


SPMOGIE0010 Recursive actions not allowed.
Explanation

A recursive action exists inside cplm.xml file.

Action

Check the cplm.xml file in the profile and remove any recursive actions.


SPMOGIE0011 Malformed action "{0}".
Explanation

Wrong metadata information exists inside the profile cplm.xml file.

Action

Check the cplm.xml file for the profile and correct errors.


SPMOGIE0012 Action "{0}" not found.
Explanation

Unknown action definied inside cplm.xml.

Action

Correct the cplm.xml file for the profile.


SPMOGIE0013 Script "{0}" does not exist.
Explanation

The specified script cannot be found in cplm.xml.

Action

Specify valid script/path inside the profile cplm.xml file.


SPMOGIE0014 Failed executing: {0}
Explanation

A problem occurred while executing the specified script.

Action

Check the specified script for errors.


SPMOGIE0015 Missing value data for element "argument".
Explanation

Wrong data format inside the profile cplm.xml file.

Action

Provide valid data inside cplm.xml.


SPMOGIE0016 More than one "action" element with the same name exist.
Explanation

A naming conflict exists inside cplm.xml.

Action

Provide different action names.


SPMOGIE0017 Two "configuration" elements have the same version.
Explanation

A conflict exists inside cplm.xml file.

Action

Provide different versions for "configuration" elements.


SPMOGIE0018 Missing attribue "path" or "actionReference" for element "execute".
Explanation

Wrong data exists inside the profile cplm.xml.

Action

Provide the missing data.


SPMOGIE0019 Cannot specify both "path" and "actionReference" attributes in one "execute" element.
Explanation

Wrong data exists inside cplm.xml.

Action

Correct cplm.xml file inside the profile folder.


SPMOGIE0026 Unable to find configuration instances for the runtime component with ID: "{0}". The '"{1}"' system property is not set.
Explanation

Such a property should be available in the config.ini file located under the configuration folder of this runtime component.

Action

Add the property by hand. The value must be the absolute path to the folder that contains the configuration properties files.


SPMOGIE0027 Unable to find configuration instances for the runtime component with ID: "{0}". "{1}" is either not existing or is not a directory.
Explanation

This folder should contain the configuration properties files.

Action

Check if the location is configured properly in the config.ini file.


SPMOGIE0029 Unable to load the configuration instance with ID "{0}" for the "{1}" runtime component.
Explanation

None of the available configuration handlers can load the configuration instance. The configuration instance type might not be supported.

Action

Check the supported configuration instance types.


SPMOGIE0030 Unable to update the configuration instance with ID "{0}" for the "{1}" runtime component.
Explanation

None of the available configuration handlers can update the configuration instance. The configuration instance type might not be supported.

Action

Check the supported configuration instance types.


SPMOGIE0031 Unable to load the configuration instance with ID: "{0}" for the "{1}" runtime component. The "{2}" property is not available but is required.
Explanation

Unable to load the instance because of invalid set of configuration properties. The required properties must be available.

Action

Add the required property and report the invalid configuration instance.


SPMOGIE0032 Unsupported protocol for configuration instance {0}.
Explanation

Unknown protocol for the specified configuration instance.

Action

Check documentation for supported protocols.


SPMOGIE0033 The update of the "{0}" configuration instance for the "{1}" runtime component failed. The port settings are empty.
Explanation

The incoming configuration is empty. No port settings data is available.

Action

Port settings data should be present inside incoming configuration.


SPMOGIE0034 No port available in configuration instance {0}.
Explanation

Port number cannot be found inside the configuration instance.

Action

Provide port number inside the configuration instance.


SPMOGIE0035 The update of the "{0}" configuration instance for the "{1}" runtime component failed. The available port configurations are more than one.
Explanation

The configuration instance should contain only one port configuration.

Action

Remove obsolete port configurations.


SPMOGIE0036 The update of the "{0}" configuration instance for the "{1}" runtime component failed. The port is null.
Explanation

The port settings do not contain any port configuration.

Action

Provide port configuration.


SPMOGIE0037 Invalid or missing port number: "{0}"
Explanation

The validation of the port number failed. The port number should be greater than 1024 and smaller than 65535.

Action

Check the source of the port number and provide a value in the specified range.


SPMOGIE0038 Error writing the new configuration. An attempt was made to overwrite an existing configuration file "{0}" with the new configuration.
Explanation

The port number is a part of the configuration file name. Therefore, if the user sets a port that is already used in another configuration, a collision in the file names occurs. In such case the write operation is aborted because configuration data might be lost.

Action

Check if the port number set in the configuration that is being written is not used in another configuration of the same type.


SPMOGIE0039 The new configuration could not be written. Unable to delete the original configuration instance file: "{0}"
Explanation

A problem occurred while deleting the configuration instance file.

Action

For more details, check the I/O exceptions in the log file.


SPMOGIE0040 ConfigurationService not found!
Explanation

Most probably spm configuration bundle was not started.

Action

Try to start spm the configuration bundle.


SPMOGIE0042 No connector configurations or connector port found for component: {0}
Explanation

Expected data is missing for the specified component.

Action

Provide configuration for the specified component.


SPMOGIE0045 Cannot start "{0}" profile in debug mode without debug port configuration.
Explanation

It is possible that wrong data exists inside the cplm.xml file.

Action

Escape single quote with another single quote.


SPMOGIE0046 Cannot start "{0}" profile in debug mode because the debug port configuration is disabled.
Explanation

It is possible that wrong data exists inside the cplm.xml file.

Action

Escape single quote with another single quote.


SPMOGIE0048 Exception occurred while obtaining port configurations for profile "{0}".
Explanation

A problem occurred while reading profile port configurations.

Action

Check profile port configurations for errors.


SPMOGIE0050 {0} cannot be null.
Explanation

{0} cannot be null.

Action

Make sure the parameter is not null.


SPMOGIE0051 {0} must begin with {1}
Explanation

{0} must begin with {1}

Action

Make sure {0} begins with {1}.


SPMOGIE0055 A log configuration not found: {0}
Explanation

A log configuration was not found.

Action

Check your configuration instance path.


SPMOGIE0056 Could not retrieve parent runtime component with id {0} for child runtime component with id {1}.
Explanation

An error occurred while obtaining information for the runtime component.

Action

Check if the runtime component is online and at least one enabled JMX port configuration is available.


SPMOGIE0057 Could not get JMXConnector for a runtime component of category {0}. Runtime component id is {1}.
Explanation

An error occurred while obtaining information for the runtime component.

Action

Check if the runtime component is online and at least one enabled JMX port configuration is available.


SPMOGIE0058 Could not get JMXConnector because no JMX port configuration is available for runtime component with id {0}.
Explanation

An error occurred while obtaining information for the runtime component.

Action

Check if the runtime component is online and at least one enabled JMX port configuration is available.


SPMOGIE0059 Could not get JMXConnector for runtime component with id {0} because none of the configured JMX ports is open.
Explanation

An error occurred while obtaining information for the runtime component.

Action

Check if the runtime component is online and at least one enabled JMX port configuration is available.


SPMOGIE0060 Could not get SubsystemMBean for a runtime component of a type different than ENGINE. Category : {0}, runtime component id : {1}
Explanation

An error occurred while obtaining information for the runtime component.

Action

Check if the runtime component is online and at least one enabled JMX port configuration is available.


SPMOGIE0061 No subsystem with id {0} is found for runtime component with id {1}.
Explanation

An error occurred while obtaining information for the runtime component.

Action

Check if the runtime component is online and at least one enabled JMX port configuration is available.


SPMOGIE0062 Exactly one subsystem is expected for runtime component with id {0}.
Explanation

Exactly one subsystem is expected for the given runtime component.

Action

Make sure there is exactly one subsystem specified for runtime component.


SPMOGIE0064 Executing "{0}" lifecycle operation shell script "{1}" returned non-zero exit code: {2}.
Explanation

Non-zero exit code indicates an error.

Action

Check the product and Platform Manager logs for more details. Try to execute the script from the command line.


SPMOGIE0065 Cannot start "{0}" profile in debug mode because the configured debug port is already in use.
Explanation

Another application is started using the same port number.

Action

Stop the other product using the same port for debug mode.


SPMOGIE0066 Platform Manager is unable to find configuration instances for the runtime component with ID: "{0}". "{1}" is either not existing or is not a directory.
Explanation

No configuration instances were found in the listed location.

Action

Check if the location is configured correctly in the config.ini file.


SPMOGIE0067 Platform Manager is unable to find configuration instances for the runtime component with ID: "{0}". "{1}" is empty.
Explanation

Platform Manager is unable to find configuration instances for the runtime component. This folder should contain the profile-related folders and files for the specified runtime component. The path is configured in the config.ini file.

Action

Check if this folder is empty.


SPMOGIE0070 Error while getting runtime status.
Explanation

A problem occurred while obtaining data from an Engine.

Action

Check if the connection and credentials are OK.


SPMOGIE0081 "{0}" operation failed for runtime component with id {1}. Reason:{2}
Explanation

Executing operation against engine failed.

Action

Check JMX credentials and properties for this engine.


SPMOGIE0090 No alias provided for the port configuration.
Explanation

Providing a value for the alias during the creation of the port configuration is required.

Action

Specify an alias for the port configuration.


SPMOGIE0091 The provided port alias is not URL friendly.
Explanation

The provided port alias contains symbols that are not URL friendly.

Action

Provide only URL friendly symbols for the port alias.


SPMOGIE0092 Failed to construct the Configuration Instance ID.
Explanation

Platform Manager failed to construct the Configuration Instance ID.

Action

Check the configuration file for this instance.


SPMOGIE0093 Missing common port alias. This configuration will be ignored.
Explanation

The common port alias is missing and the configuration will be ignored.

Action

Provide an alias for this port configuration.


SPMOGIE0094 Failed to construct the configuration instance.
Explanation

Platform Manager failed to construct the configuration instance.

Action

Provide valid configuration data.


SPMOGIE0096 Cannot read config.ini file for RuntimeComponent with ID {0}. Fall back on default product: {1}.
Explanation

Cannot retrieve the parent product for the specified run-time component because an error occured while reading the corresponding config.ini file. The default product will be used instead.

Action

Check if the config.ini is a valid properties file.


SPMOGIE0099 Exception while retrieving engines for runtime component {0} through JMX:

SPMOGIE0101 Interrupted while waiting for port {0} to be released.

SPMOGIE0103 Exception while reading the port from configuration {0}.

SPMOGIW0001 Could not pass the validating schema. The "cplm" file will not be validated.
Explanation

File called cplm.xml does not contain expected metadata.

Action

Check profile folder files called cplm.xml for errors.


SPMOGIW0028 Unable to find configuration instances for the runtime component with ID: "{0}". "{1}" is empty.
Explanation

This folder should contain the configuration properties files for the specified runtime component. The path is configured in the config.ini file.

Action

Check if this folder should be empty.


SPMOGIW0054 Could not retrieve engines for runtime component with id : {0}.
Explanation

Most likely the component with the specified ID was offline.

Action

Check if the runtime component is online and at least one enabled JMX port configuration is available.


SPMPROE0003 Script failed with status {0}
Explanation

A fix script job failed with indicated status.

Action

Refer to the Software AG Update Manager log for more information.


SPMPROE0004 Install fixes is not supported.
Explanation

The requested feature is not supported yet.

Action

Use the runscript method to install fixes.


SPMPROE0005 Nothing to install.
Explanation

None of the artifacts exist in the specified repository.

Action

Use different artifacts or install from a different repository.


SPMPROE0006 Install from local repository not supported.
Explanation

The feature is not yet supported.

Action

Export artifacts from the repository into an image archive and install from the archive.


SPMPROE0007 No repository found for {0}
Explanation

The specified repository does not exist.

Action

Create the repository or use a different one.


SPMPROE0008 Install from remote repository is not supported.
Explanation

Installing from a remote repoitory is not supported.

Action

Create an image archive using installer client, and install from the archive.


SPMPROE0009 Unable to process fix script.
Explanation

Failures occurred processing a fix script.

Action

See the Software AG Update Manager logs and exception for failure details.


SPMPROE0010 Invalid Type: {0}
Explanation

The type of script is unrecognized. Valid types are either product, or fix.

Action

Use product or fix as the script type.


SPMPROE0011 Uninstall of fixes is not supported by the uninstall method.
Explanation

The operation is not supported.

Action

Use runscript to remove fixes.


SPMPROE0012 Invalid artifact type: {0}
Explanation

The artifact was not a product or fix artifact.

Action

Use a valid artifact.


SPMPROE0013 Script failed with exit code {0}. See log at {1} for more information.
Explanation

An installation script failed.

Action

Refer to the log for more details on the failure.


SPMPROE0014 The provided configuration does not include the com.softwareag.plm.spm.provisioning.pathtosum property.
Explanation

The property must be specifried in the configuration.

Action

Include a com.softwareag.plm.spm.provisioning.pathtosum property setting that references the Software AG Update Manager installation directory.


SPMPROE0016 The com.softwareag.plm.spm.provisioning.pathtosum property does not reference an existing directory.
Explanation

The property must reference the installation directory of Software AG Update Manager.

Action

Specify a valid directory.


SPMPROE0018 Removal of ProvisioningService configuration is not supported.
Explanation

The ProvisioningService requires a configuration.

Action

None required.


SPMPROE0020 No such repository, {0}
Explanation

The install request specified a nonexistant repository.

Action

Specify a valid repository ID.


SPMPROE0021 No matching products to uninstall.
Explanation

The uninstall request specified products that are not installed.

Action

Ensure that the correct product list or managed node is included in the request.


SPMPROE0022 {0} is not in repository {1} or the required products {2} are not installed.
Explanation

The fix cannot be installed because it does not reside in the source repository or required products are not installed.

Action

Specify a different fix repository. Verify with Update Manager if the fix can be resolved.


SPMPROE0023 Multple fixes with id, {0}, reside in the repository {1}
Explanation

Platform Manager cannot determine which fix version to install.

Action

Specify a complete version number for the fix (<fixname>_<version>).


SPMPROE0024 Script failed with exit code {0}:{1}. See log at {2} for more details.
Explanation

The execution of the script failed.

Action

Rerun script after resolving the errors listed in the log.


SPMPROE0025 Script failed with status {0}: {1}
Explanation

The execution of the fix script failed.

Action

Rerun the script after resolving the errors.


SPMPROE0026 Unrecognized repository type: {0}
Explanation

The repository is not a supported type.

Action

Use a valid repository type.


SPMPROE0027 Unsupported repository. Use P2 enabled repository for provisioning artifacts.
Explanation

Only P2 enabled repositories are supported.

Action

Use a P2 enabled repository for provisioning artifacts.


SPMPROE0028 Artifact with id "{0}" and version "{1}" not found in the repositories {2}
Explanation

The repositories do not contain any of the desired artifacts.

Action

Check the template and repository definitions.


SPMPROE0030 Platform Manager restart failed.
Explanation

The attempt at restarting Platform Manager failed.

Action

Check the Platform Manager logs.


SPMPROE0031 Failed detecting Platform Manager Components.
Explanation

The attempt to identify whether Platform Manager components (for example, the product plug-ins) are about to be provisioned has failed.

Action

Check the Platform Manager logs.


SPMPROE0032 Platform Manager will be restarted.
Explanation

Platform Manager will be restarted because Platform Manager components have been installed.

Action

Wait for Platform Manager to start. Check the logs for more details.


SPMPROE0048 Could not uninstall products {0}. See sd-provisioning.log for details.
Explanation

Could not uninstall products {0}.

Action

See sd-provisioning.log for more details.


SPMPROE0049 Fixes {0} provided for uninstallation are not installed.
Explanation

The fixes, provided for uninstallation are not found on the target installation.

Action

Provide only installed fixes for uninstallation.


SPMPROE0050 The following fixes provided for uninstallation cannot be uninstalled: {0}
Explanation

Some of the fixes, provided for uninstallation cannot be uninstalled.

Action

Provide only installed fixes which can be uninstalled.


SPMPROI0000 Fix installation completed with exit code: {0}
Explanation

The fix script has completed with the indicated exit status.

Action

If status is nonzero, review the Software AG Update Manager logs for possible problems.


SPMPROI0001 Launching: {0}
Explanation

A fix script is being started in a separate process. The specific shell command is included in the message.

Action

None required.


SPMPROI0002 Failed to launch fix script.
Explanation

A scipt could not be launched. The associated job will be given an error status.

Action

Refer to the exception included in the message to resolve the problem.


SPMPROW0029 {0} is not in repository {1} or the required products are not installed.
Explanation

The fix cannot be installed because it does not reside in the source repository or required products are not installed.

Action

Specify a different fix repository. Verify with Update Manager if the fix can be resolved.


SPMREPE0000 Unsupported operation.
Explanation

The getContent operation is not supported for fix images.

Action

Use UpdateManager to view fixes.


SPMREPE0001 Unsupported operation.
Explanation

The import operation is only supported on local product repositories.

Action

None required.


SPMREPE0002 Invalid configuration detected for repository, {0}
Explanation

The location property of the repository is invalid. The configuration refers to a fix image, which must be a local file.

Action

Delete the configuration.


SPMREPE0003 Repository not found at {0} for configuration, {1}
Explanation

A configuration was found for a fix image repository that does not exist.

Action

Remove the configuration.


SPMREPE0004 Unsupported operation.
Explanation

The export operation is not supported for this artifact type or repository.

Action

None required.


SPMREPE0005 Unsupported operation.
Explanation

The repository type does not support dependencies.

Action

None required.


SPMREPE0006 Unsupported operations.
Explanation

Publishing is not supported for this repository type.

Action

None required.


SPMREPE0007 Unable to parse canonical in {1}: {0}
Explanation

The product properties could not be processed. The file is not a valid image archive.

Action

Use a valid image archive.


SPMREPE0008 Importing of artifacts into an image archive is not supported.
Explanation

Importing artifacts into an image archive is not supported.

Action

To create an image archive, use the export feature.


SPMREPE0009 URI scheme for image archive repository, {0}, must be file
Explanation

The repository configuration is invalid.

Action

Specify a local file as the archive location.


SPMREPE0010 Repository not found at {0}
Explanation

There is no archive at the specified location.

Action

Specify a valid location for the archive.


SPMREPE0011 Exporting from images is not supported.
Explanation

The function is not supported.

Action

None required.


SPMREPE0012 Dependencies not available for image archives.
Explanation

The function is not supported.

Action

Non required.


SPMREPE0013 Publish feature is not supported for image archives.
Explanation

Only local repositories may be published.

Action

None required.


SPMREPE0016 Platform Manager cannot list product or fix repositories of release 9.7 or earlier.
Explanation

The listing of product or fix repositories is not supported for releases 9.7 or earlier.

Action

Start the Software AG Installer and select the release that includes the products you want to see, or start the Software AG Update Manager and select the release and products that include the fixes you want to see.


SPMREPE0017 Sandboxes are not modifiable.
Explanation

Importing into sandboxes is not supported.

Action

None required.


SPMREPE0018 Exporting from sandboxes is not supported.
Explanation

The function is not supported.

Action

Use the installer client to export images from legacy sandboxes.


SPMREPE0019 Dependencies not available for sandboxes.
Explanation

The function is not supported.

Action

Use installer client to interact with legacy sandboxes.


SPMREPE0020 Only local repositories can be published.
Explanation

Sandboxes cannot be published.

Action

None required.


SPMREPE0021 Unable to load/create repository at {0}
Explanation

Platform Manager was not able to read the repository content.

Action

See to logs for more information. The repository may have been corrupted.


SPMREPE0024 Unable to verify archive: {0} due to {1}
Explanation

The file could not be verified as a ZIP archive.

Action

Ensure the path to the archive is correct.


SPMREPE0025 The specified file is not a valid image file.
Explanation

A valid image file can be created with Software AG Installer or Software AG Update Manager.

Action

To validate a product image, open the Software AG Installer and go to Advanced Options > Images. If required, re-create the product or fix image by following the instructions in the Software AG Installer documentation for product images, or the Software AG Update Manager documentation for fix images, and try again.


SPMREPE0026 Local repository, {0}, has an invalid location: {1}
Explanation

The repository configuration is invalid.

Action

Delete the configuration.


SPMREPE0027 Unable to create repository at {0}
Explanation

The repository could not be created.

Action

See the logs for more information.


SPMREPE0028 Exporting of fixes is not supported.
Explanation

The function is not supported.

Action

Use Software AG Update Manager to export fixes.


SPMREPE0037 Unsupported operation.
Explanation

getContent is not supported for remote fix repositories.

Action

Use Software AG Update Manager to view repository content.


SPMREPE0038 Unsupported operation.
Explanation

Import is not supported for remote fix repositories.

Action

Use Software AG Update Manager to manage fix repositories.


SPMREPE0039 Unsupported operation.
Explanation

Export is not supported for remote fix repositories.

Action

Use Software AGUpdate Manager to manage fix repositories.


SPMREPE0040 Unsupported operation.
Explanation

Dependencies not supported for remote fix repositories.

Action

Use Software AG Update Manager to manage fix repositories.


SPMREPE0041 Unsupported operation.
Explanation

Publish is not supported for remote fix repositories.

Action

Use Software AG Update Manager to manage fix repositories.


SPMREPE0042 Unable to access SD Security Service.
Explanation

The security service used to access remote repositories is not available.

Action

Try to restart the security service.


SPMREPE0043 Unable to obtain security token for user, {0}, for the {1} repository.
Explanation

The attempt to login to the SD security service failed.

Action

Ensure correct credentials are set for the repository.


SPMREPE0044 Unable to load remote repository, {0}, due to {1}
Explanation

A failure was detected attempting to access the repository.

Action

See the logs for more information.


SPMREPE0045 Unsupported operation.
Explanation

Importing into a remote repository is not supported.

Action

None required.


SPMREPE0047 Unsupported operation.
Explanation

Exporting from a remote repository is not supported.

Action

Import the artifacts into a local repository, then export from the local repository.


SPMREPE0048 Unsupported operation.
Explanation

Publish is not supported for remote repositories. They are already published.

Action

None required.


SPMREPE0049 {0} not found in repository.
Explanation

The specifed artifact does not exist in the repository.

Action

Verify that the correct artifact is used.


SPMREPE0050 Unable to list repositories.
Explanation

Failures occurred while reading repository configuration.

Action

Ensure read access is provided for repositories defined in the SPM profile.


SPMREPE0051 Unable to list repositories.
Explanation

Failures occurred while reading repository configuration.

Action

Ensure read access is provided for the repositories defined in the SPM profile.


SPMREPE0053 Location can not be null.
Explanation

When adding a new repository configuration, the location property must be provided.

Action

Provide a location for the repository being configured.


SPMREPE0054 Invalid content type: {0}
Explanation

The type of a repository must be either product or fix.

Action

Provide a valid repository type.


SPMREPE0055 Repository already configured for {0}
Explanation

A repository at this location is already configured.

Action

None required.


SPMREPE0057 {0} is an invalid path.
Explanation

The location cannot be represented as a valid URI.

Action

Use a valid path.


SPMREPE0058 Location does not exist: {0}
Explanation

There is no fix image archive at the specified location.

Action

Provide the location of an existing fix image archive.


SPMREPE0062 Unable to delete configuration properties: {0}
Explanation

The configuration properties for a repository could not be deleted.

Action

Manually delete the property file.


SPMREPE0064 Must specify repository type.
Explanation

The type argument for listing repositories cannot be null.

Action

Specify the repository type, either product or fix.


SPMREPE0065 No such repository - {0}
Explanation

There is no repository with the given ID.

Action

Use a known repository configuration.


SPMREPE0066 Source and destination arguments cannot be null.
Explanation

Both source and destination arguments must be specified for the import operation.

Action

Provide valid source and destination repository arguments.


SPMREPE0067 No such repository registered, {0}
Explanation

The source repository for the import operation does not exist.

Action

Provide a valid source repository argument.


SPMREPE0068 No such repository registered, {0}
Explanation

The destination repository for the import operation does not exist.

Action

Provide a valide destination repository.


SPMREPE0069 Incompatable repositories.
Explanation

The source and destination repositories must have the same content type.

Action

Ensure that both repositories are either product, or fix repositories.


SPMREPE0070 Cannot import into remote repository, {0}
Explanation

Importing into remote repositories is not supported.

Action

Specify a local repository as the destination.


SPMREPE0071 Unable to create path to provisioning configuration: {0}
Explanation

Unable to create provisioning configuration directory.

Action

Ensure that the Platform Manager configuration directory is writable.


SPMREPE0072 Invalid repository type: {0}
Explanation

The repository type must be product or fix.

Action

Specify a valid repository type.


SPMREPE0073 No repository name provided.
Explanation

A repository name must be provided for discovering fix repositories.

Action

Provide the repository name.


SPMREPE0074 Invalid server or repository name: {0}
Explanation

The server or name arguments contain invalid characters for a URL.

Action

Specify valid server and names for the fix repository.


SPMREPE0075 Repository discovery failed: No ProductRepositoryManagementService available
Explanation

Unable to discover product repositories as the necessary services are not active.

Action

See the logs to determine why the repository manager service is inactive.


SPMREPE0076 Cannot connect to Software AG repository: {0}
Action

Make sure the Platform Manager has Internet access and the proxy configuration is present and correct. You can also check the logs for the Platform Manager. Then try again to connect.


SPMREPE0077 Source repository cannot be null.
Explanation

A source repository must be specified for the export operation.

Action

Specify the local repository to use for export.


SPMREPE0078 Path cannot be null.
Explanation

The path to the destination archive must be specified for the export operation.

Action

Provide a path where the archive should be created.


SPMREPE0079 No such repository registered, {0}
Explanation

There is no repository with the given ID.

Action

Specify a valid source repository.


SPMREPE0080 Unsupported operation.
Explanation

Platform Manager cannot export from archive.

Action

Specify a local repository from which to export.


SPMREPE0081 Cannot export into existing file: {0}
Explanation

Exporting cannot be used to add to an existing archive.

Action

Specify the location to create a new archive.


SPMREPE0082 Artifact must be specified.
Explanation

An artifact argument for get dependencies was null.

Action

Specify the artifact for its list of dependecnies.


SPMREPE0083 Source repository cannot be null.
Explanation

The source repository for get dependencies cannot be null.

Action

Specify a valid repository in which to search for dependencies.


SPMREPE0084 No such repository registered, {0}
Explanation

The specified repository does not exist.

Action

Specify a valid repository in which to search for dependencies.


SPMREPE0085 No such repository: {0}
Explanation

The specified repository does not exist.

Action

Specify a valid local repository to publish.


SPMREPE0086 Source and destination repositories are the same.
Explanation

The source and destination repositories must refer to different repositories.

Action

Specify valid repositories.


SPMREPE0087 {0} not found in repository.
Explanation

The specifed artifact does not exist in the repository.

Action

Verify that the correct artifact is used.


SPMREPE0088 Unsupported operation.
Explanation

The publishing of local repositories is not supported in this release.

Action

None required.


SPMREPE0089 Unsupported operation.
Explanation

The unpublish operation is not supported for repository type.

Action

None required.


SPMREPE0090 No such repository registered, {0}
Explanation

The specified repository is not registered.

Action

Specify a valid repository, or add the repository.


SPMREPE0091 Failures occurred attempting to publish a repository: {0}
Explanation

Internal errors prevented the publish operation from completing.

Action

Depends on the specific error. Check the logs for the error details.


SPMREPE0092 The repository, {0}, is already published with context, {1}
Explanation

Specify the correct repository or republish to use a different context.

Action

To change context, unpublish, then republish with new context.


SPMREPE0093 Web publishing service is unavailable.
Explanation

The necessary service to publish repositories is not active.

Action

None required.


SPMREPE0094 Invalid context: {0}
Explanation

The context in the publish request may not be null and must start with /

Action

Check if the context of the publish request is null and verify that it starts with /


SPMREPE0095 Invalid context: {0}
Explanation

The context must not be null and start with /

Action

Use a valid context.


SPMREPE0096 Repository {0}, is not published.
Explanation

The request assumes the repository has been published.

Action

None required.


SPMREPE0097 Failures detected while unpublishing repository: {0}
Explanation

The unpublishing operation failed.

Action

Depends on the type of failure. Check the logs for the error details.


SPMREPE0098 No credentials for accessing the remote fix repository, {0}, have been configured.
Explanation

You must provide user credentials to access remote repositories.

Action

Specify the user and password properties for the repository.


SPMREPE0099 The location of a repository is invalid: {0}
Explanation

The URI of a repository does not have a valid path.

Action

Specify a valid location when registering repositories.


SPMREPE0100 No repository found at the specified location: {0}
Explanation

The location specified did not match any known repository.

Action

Specify a valid location.


SPMREPE0101 No fix service available.
Explanation

A required service for managing fix repositories is unavailable.

Action

Review the Platform Manager logs for indications of fix service failures.


SPMREPE0103 {0} is an invalid path. It must be relative.
Explanation

To create a new local repository, you must use only relative paths.

Action

Specify a relative path.


SPMREPE0104 Login to repository, {1}, failed for user, {0},
Explanation

Repository configured with incorrect credentials.

Action

Reconfigure the repository credentials.


SPMREPE0105 Only one platform may be specified in the provided filter .
Explanation

The repository operation included a filter with multiple platforms.

Action

Specify only one platform in the filter and retry the operation.


SPMREPE0106 The repository, {0}, is currently in use.
Explanation

The operation cannot be processed until the specified repository becomes available.

Action

Retry when all provisioning operations are completed.


SPMREPE0107 Failed to load repository, {0}
Explanation

An error occurred while attempting to access the repository.

Action

Check the logs for the error details.


SPMREPE0108 Publish with non-default realm or roles is not supported.
Explanation

The requested operation is not supported.

Action

Retry the request without specifying a realm or roles.


SPMREPE0109 {0} is not in repository {1} or is not applicable for the requested platform.
Explanation

Unable to export the specified fix into the archive because the fix does not reside in the source repository, or it is not applicable for the requested platform.

Action

Specify a different fix, repository, or platform.


SPMREPE0110 Invalid SDC installer properties.
Explanation

The servers/production/versions property in the server.properties file is missing.

Action

This is an internal error and should be reported. Contact Software AG Global Support.


SPMREPE0111 No such repository, {0}
Explanation

The specified repository is not registered.

Action

Specify an valid repository, or create one.


SPMREPE0112 Unsupported operation.
Explanation

The getReadme operation is not supported by the repository.

Action

Specify an appropriate repository.


SPMREPE0113 Unable to load remote repository {0}. The server returned null result.
Explanation

The attempt to load to the specified remote repository failed.

Action

Ensure that the correct repository metadata is provided and try again.


SPMREPE0114 Update Manager threw unexpected exception: {0}.
Explanation

Update Manager threw unexpected exception: {0}.

Action

Check the Update Manager installation.


SPMREPE0115 Login failed for user: {0} and location: {1}
Explanation

The login operation failed for user: {0} and location: {1}

Action

Provide valid credentials and valid repository location.


SPMREPE0116 The Repository Validation parameter should not be null.
Explanation

The Repository Validation parameter should not be null.

Action

Provide a valid (not null) Repository Validation parameter.


SPMREPE0117 The repository path should not be empty.
Explanation

The repository path should not be empty.

Action

Provide a valid non-empty repository path.


SPMREPE0118 The provided username or password should not be empty.
Explanation

The username or password should not be empty.

Action

Provide non-empty valid username or password.


SPMREPE0119 Fixes repository validation failed.
Explanation

The fixes repository validation failed.

Action

Analyze the error and provide valid input.


SPMREPE0120 Products repository validation failed.
Explanation

The products repository validation failed.

Action

Analyze the error and provide valid input.


SPMREPE0121 Trusted authentication failed while trying to log in {0} repository.
Explanation

Connecting to the specified repository using trusted authenticaion failed.

Action

See the Platform Manager wrapper log for more details.


SPMREPE0122 Repository {0} not found.
Explanation

The specified repository is not registered.

Action

Check the repository name or register a repository with the same name.


SPMREPE0123 Dependencies resolution failed. {0}
Explanation

The dependencies resolution of the selected products failed.

Action

Try to correct the issue and retry the operation.


SPMREPE0124 Artifact with id "{0}" and version "{1}" not found in the repositories {2}.
Explanation

The repositories do not contain any of the required artifacts.

Action

Check the template and the repository definitions.


SPMREPE0125 Dependencies resolution failed. {0} Possible runtimes are {1}.
Explanation

The dependencies resolution of the selected products failed because a product can be installed on multiple runtimes.

Action

Choose the runtime you would like to use and discard the others.


SPMREPE0126 The specified products {0} are not found in the product repository {1}.
Explanation

The specified products {0} are not found in the product repository {1}.

Action

Verify that the correct product codes are used.


SPMREPE0127 Product mirror operation into {0} repository failed with status : {1}
Explanation

Importing products into the mirror repository failed.

Action

See the products' sd-provisioning.log for more information.


SPMREPE0128 Failing Fix Mirror Repository operation: {0}
Explanation

{0}

Action

For more details check the Update Manager logs.


SPMREPE0129 Failed to obtain fix dependencies. {0}
Explanation

No additional information.

Action

Check if the specified fix dependency is a valid fix and if it exists in the repository.


SPMREPE0130 The mirror repository with name {0} is not found.
Explanation

The repository with name {0} either does not exists, or is not a mirror repository.

Action

Use an existing mirror repository, or create a new one with the specified name.


SPMREPE0131 Mirror repository validation failed. {0}
Explanation

The mirror repository checksum validation failed. The repository is corrupted.

Action

Remove the mirror repository and create it again.


SPMREPE0132 Accessing {0} via HTTP failed because the repository is hosted on a Platform Manager which HTTP port is disabled.
Explanation

Installing products from mirror repositories on nodes with version 10.1 and lower can only be executed over HTTP.

Action

Enable the SPM HTTP port, use a master repository, or migrate to Command Central 10.3 or higher.


SPMREPE0135 Cannot export more than one platform for a repository. Only one platform should be provided for repository {0}.
Explanation

Cannot export more than one platform for a repository.

Action

Provide only one platform for exporting the repository.


SPMREPE0136 Cannot export all platforms for а repository. Only one platform should be provided for repository {0}.
Explanation

Cannot export all platforms for а repository.

Action

Provide only one platform for exporting the repository.


SPMREPI0014 Importing into {0}
Explanation

Importing of artifacts is starting.

Action

None required.


SPMREPI0015 Import failed: {0}
Explanation

An import operation failed.

Action

See the installation log for more information.


SPMREPI0023 Creating local repository at {0}
Explanation

A new local repository is being created.

Action

None required.


SPMREPI0029 No matching products found in {0} repository
Explanation

The request to mirror a repository is ignored as none of the specified artifacts reside in the repository.

Action

None required.


SPMREPI0030 Import from {0} to {1} failed.
Explanation

The import operation failed.

Action

See the logs for more information.


SPMREPI0031 Importing all products from {0} to {1}
Explanation

All products in the source repository will be imported.

Action

None required.


SPMREPI0032 Importing products fro {0} to {1}
Explanation

A subset of products is being imported. The specific products are listed as subsequent log entries.

Action

None required.


SPMREPI0033 {0}
Explanation

The id of a product being imported.

Action

None required.


SPMREPI0034 Import from {0} to {1} was successful.
Explanation

The import operation completed successfully..

Action

None required.


SPMREPI0035 Exporting artifacts from {0} to {1}
Explanation

An export operation is starting.

Action

None required.


SPMREPI0036 Export from {0} to {1} failed due to {2}
Explanation

The export operation failed.

Action

See the logs for more information.


SPMREPI0056 The configuration of repository {0} has an invalid location property: {0}
Explanation

The location property is not a valid URI.

Action

Remove the repository.


SPMREPI0059 Unable to add repository {0}.
Explanation

The location is an invalid URL.

Action

Noe required.


SPMREPI0060 Unable to add repoistory {0}.
Explanation

The attempt to configure the remote repository failed.

Action

See the logs for more information.


SPMREPI0061 Failures occurred during removal of repository {0}.
Explanation

The repository configuration may not have been completely removed.

Action

See the logs for further information.


SPMREPI0063 Removed repository configuration, {0}
Explanation

The repository was successfully removed.

Action

None required.


SPMREPW0022 Unable to delete {0}
Explanation

The directory of the local repository to be created was not empty.

Action

None required.


SPMREPW0046 Failed to remove password handle for repository, {0}
Explanation

Cleanup of passman data was incomplete while removing the repository.

Action

None required.


SPMREPW0052 Unable to initialze repository {0}.
Explanation

The repository could not be validated.

Action

Remove the repository configuration.


SPMREPW0102 Failed to remove password handle for repository, {0}
Explanation

The passman cleanup was incomplete.

Action

None required.


SPMRMCE0001 Invalid input data.
Explanation

The submitted data failed to un-marshal or validate against the schema.

Action

Correct the reported problem in the input data and retry the request.


SPMRMCE0002 Internal Error processing the request.
Explanation

The server encountered an error and cannot execute the request.

Action

Contact your system administrator.


SPMRMCE0003 Invalid client request.
Explanation

The submitted client request is rejected by the server.

Action

Check the status code for more details or consult the Software AG Platform Manager documentation. Correct the problem and resubmit the request.


SPMRMCE0005 The requested functionality is not supported.
Explanation

Platform Manager does not support the requested functionality.

Action

See the Software AG Platform Manager documentation for the supported requests for this resource.


SPMRMCI0000 Configuration partial failure for runtime component: {0}, instance: {1} with type {2} - with linked exception:
Explanation

The configuration operation for the specified run-time component, instance, and type failed with the specified exception.

Action

Check the logs for the error details.


SPMRPIE0000 Use RepositoryService to create new repository configurations.
Explanation

The ConfigurationService cannot be used to add repository configurations.

Action

Use the RepositoryService to configure new repositories.


SPMRPRE0000 Invalid filter specification.
Explanation

A request was made that included a product filter and the useInventory option.

Action

Resubmit with the appropriate filter. Use either a product list or the useInventory option, not both at the same time.


SPMRPRE0001 No repository with id, {0}, and type, {1} exists
Explanation

The request references a non-existant repository.

Action

Specify the correct repository ID and/or type.


SPMSCOE0000 No Credentials in Data Store for handle: {0}
Explanation

Searching for exact credentials match does not return results.

Action

Search again for existing credentials.


SPMSCOE0001 No Credentials available in Secured Store for handle: {0}
Explanation

Searching for exact credentials match does not return results.

Action

Search again for existing credentials.


SPMSURE0000 Some of the required properties for retrieving a UiBinding are not provided. Please provide values for {0} and a value for one of {1}.
Explanation

Some of the required properties for retrieving a UiBinding are not provided.

Action

Provide the full set of required properties.


SPMSURE0002 Could not transfer the file to the target destionation {0}. Reason: {1}.
Explanation

The file could not be transfered due to an error.

Action

Check if the target host has enough disk space or the provided file name is valid.


SPMSURW0001 Some of the required properties for retrieving a UiBinding are not provided. Provide values for {0}.
Explanation

Some of the properties required for retrieving a UiBinding are not provided.

Action

Provide the full set of required properties.


SPMTEME0000 Error occurred while reading the configuration instances for {0}
Explanation

The error occurred while creating a template that includes configuration information.

Action

Check whether the configuration instances for the specified runtime component are available by querying them explicitly. Check the logs for errors if the query fails.


SPMTEME0001 Error occurred while applying template {0}
Explanation

The error occurred when applying the specified template.

Action

Check the logs for more details.


SPMTEME0006 Error occurred during template creation {0}
Explanation

The error occurred when creating a template.

Action

Check the logs for more details about the error.


SPMTEME0012 Error occured while executing a task with id: {0} and status: {1}
Explanation

Executing the specified task failed.

Action

Check the Platform Manager logs for more information.


SPMTEME0014 Deleting configuration instance with type {0} is not supported operation.
Explanation

Platform Manager does not support deleting the configuration instance with the specified type.

Action

Check the warning to determine if any damage to the system will occur.


SPMTEME0015 Skipping deleting configuration instance ({0}) for runtime component - {1}. Reason: {2}
Explanation

The error occurred because either the runtime component, or a configuration manager for the configuration instance is missing in the Platform Manager.

Action

Check if the specified runtime component is present or that the appropriate SPM plugin is installed. Check the warning to determine if any damage to the system will occur.