Resource Instances

Administrator - Resource Instances
Error Code Description
TIBCO-AMX-ADMIN-030001 Provide valid resource instances.
TIBCO-AMX-ADMIN-030002 Failed to create resource instance [{0}], the name is invalid.
TIBCO-AMX-ADMIN-030003 Provide valid host information.
TIBCO-AMX-ADMIN-030004 Failed to create resource instances as host {0} does not exist.
TIBCO-AMX-ADMIN-030005 Could not delete for resource instances.
TIBCO-AMX-ADMIN-030006 Provide valid Node information.
TIBCO-AMX-ADMIN-030007 This method only supports resource instances in TIBCO hosts.
TIBCO-AMX-ADMIN-030008 Host {0} with id {1} does not exist.
TIBCO-AMX-ADMIN-030009 Resource template does not exist for resource instance: {0}.
TIBCO-AMX-ADMIN-030010 Failed to create resource instance {0} on host{1} as HostType {2} requires resource instances to be created on nodes.
TIBCO-AMX-ADMIN-030011 Resource instance configuration is invalid.
TIBCO-AMX-ADMIN-030012 Administrator internal HTTP connector resource template {0} is not available.
TIBCO-AMX-ADMIN-030013 Server base URL or artifact server URL is not found or null. Please install the Administrator Internal HTTP connector resource instance.
TIBCO-AMX-ADMIN-030014 The host type is not currently supported for this operation.
TIBCO-AMX-ADMIN-030015 Resource instance with id {0} and name {1} does not exist.
TIBCO-AMX-ADMIN-030016 Parent does not exist for resource instance: {0}.
TIBCO-AMX-ADMIN-030017 Invalid node type{0} with Id{1}.
TIBCO-AMX-ADMIN-030018 Invalid entity type: {0}.
TIBCO-AMX-ADMIN-030019 The user does not have permission to create a resource instance on node: {0}.
TIBCO-AMX-ADMIN-030020 The node name cannot be null.
TIBCO-AMX-ADMIN-030021 The actionHandle is null.
TIBCO-AMX-ADMIN-030022 The user does not have permission to install the resource instance.
TIBCO-AMX-ADMIN-030023 Invalid parent type.
TIBCO-AMX-ADMIN-030024 {0} is not injected.
TIBCO-AMX-ADMIN-030025 Could not get a session from SessionFactory.
TIBCO-AMX-ADMIN-030026 Failed to create resource instance {0} as Node is not specified.
TIBCO-AMX-ADMIN-030027 Failed to create resource instances as Node {0} does not exist.
TIBCO-AMX-ADMIN-030028 Failed to create a resource instance. Error while retrieving details of resource instance {0} for node {1}.
TIBCO-AMX-ADMIN-030029 Failed to create resource instance as Resource Instance already exists with the name {0} on Node {1}.
TIBCO-AMX-ADMIN-030030 Failed to create resource instance as resource template is not provided for resource instance {0}.
TIBCO-AMX-ADMIN-030031 Resource instance {0} creation failed on node {1}.
TIBCO-AMX-ADMIN-030032 Resource extension plug-in is not available for resource type {0}.
TIBCO-AMX-ADMIN-030033 Failed to create a resource instance. A resource instance with the same name ({0}) and type ({1}) already exists on the same host. The existing resource instance is on Node {2} and is using the resource template {3}.
TIBCO-AMX-ADMIN-030034 Force actions are restricted to only users with explicitly granted permissions, and you do not have the permissions to invoke this action with force=true. This action is invoked with force=false.
TIBCO-AMX-ADMIN-030035 Resource template for resource instance {0} was already forcefully deleted. If there are any dependent resource instances for resource instance {1}, those dependent resource instances are not deleted.
TIBCO-AMX-ADMIN-030036 Failed to delete Resource instance as {0} is in the installed state. Uninstall the resource instance and then try again.
TIBCO-AMX-ADMIN-030037 Following resource instances [ {0} ] refer to resource instance {1}.
TIBCO-AMX-ADMIN-030038 The delete action for the resource instance {0} is processed later, after the uninstall completes.
TIBCO-AMX-ADMIN-030039 Deleting resource instance {0} even though the resource instance is in the installed state.
TIBCO-AMX-ADMIN-030040 Resource instance {0} deleted on node {1}.
TIBCO-AMX-ADMIN-030041 Resource instance {0} deleted on host {1}.
TIBCO-AMX-ADMIN-030042 The resource instance {0} has a JNDI reference {1} and the reference value is svar {2}, which does not exist.
TIBCO-AMX-ADMIN-030043 Resource instance {0} has a JNDI reference[{1}] {2}, which does not exist.
TIBCO-AMX-ADMIN-030044 Resource Instance {0} has a JNDI reference[{1}] {2} of type{3}, but the resource template for the resource instance {4} is of type {5}.
TIBCO-AMX-ADMIN-030045 Error installing resource instance {0}.
TIBCO-AMX-ADMIN-030046 Resource instance {0} is uninstalled in the background.
TIBCO-AMX-ADMIN-030047 Resource Template {0} does not exist.
TIBCO-AMX-ADMIN-030048 Invalid host for node {0}.
TIBCO-AMX-ADMIN-030049 Error reading resource template configuration for resource instance {0}.
TIBCO-AMX-ADMIN-030050 Installing resource instance {0} failed. It is secured using TCS but TCS is not running. Please start TCS before installing.
TIBCO-AMX-ADMIN-030051 Node does not exist with id {0} name {1}.
TIBCO-AMX-ADMIN-030052 Resource Instance {0} created on Node {1}.
TIBCO-AMX-ADMIN-030053 Creating resource instance {0} on Node {1}.
TIBCO-AMX-ADMIN-030054 Deleting resource instance {0}.
TIBCO-AMX-ADMIN-030055 Resource template does not exist for resource instance: {0}.
TIBCO-AMX-ADMIN-030056 Artifact server {0} is in RUNNING state on node: {1}.
TIBCO-AMX-ADMIN-030057 Uninstalling resource instance “{0}”.
TIBCO-AMX-ADMIN-030058 From {0} existing RIs, {1} were uninstalled.
TIBCO-AMX-ADMIN-030059 Installing a resource instance with the name “{0}” and Id “{1}”.
TIBCO-AMX-ADMIN-030060 Error processing the internal HTTP Connector resource instance {0}.
TIBCO-AMX-ADMIN-030061 The artifact service application is not installed.
TIBCO-AMX-ADMIN-030062 The artifact service application is not in the RUNNING state.
TIBCO-AMX-ADMIN-030063 The artifact service application {0} is not installed.
TIBCO-AMX-ADMIN-030064 Artifact service {0} is not in the RUNNING state on node: {1}.
TIBCO-AMX-ADMIN-030065 Failed to process the resource instance in fixer request, as one of the following required fields: JNDI Name, resource template identifier and node or host identifier is not provided. Provided values are: JNDI Name {0} Resource Template identifier: {1} Target identifier: {2}.
TIBCO-AMX-ADMIN-030066 Failure retrieving the resource instance tree.
TIBCO-AMX-ADMIN-030067 Existing uninstalled resource instance.
TIBCO-AMX-ADMIN-030068 Resource instance {0} is already in-sync; the install action is being ignored.
TIBCO-AMX-ADMIN-030069 Warnings while installing resource instance {0}. {1}.
TIBCO-AMX-ADMIN-030070 Missing this JNDI reference: {0}.
TIBCO-AMX-ADMIN-030071 Driver extension NOT registered for Resource Instance “{0}” (internal id “{1}”).
TIBCO-AMX-ADMIN-030072 A resource instance with name {0} and Id {1} does not require a driver to be provisioned.
TIBCO-AMX-ADMIN-030073 Resource template blob configuration does not exist for resource instance with name {0} and Id {1}.
TIBCO-AMX-ADMIN-030074 Driver not found for resource instance {0}. In case the resource instance install is successful it might happen that you have provisioned the driver in the old fashioned way by keeping the driver inside a custom feature and deployed that custom feature on the node before installing this resource instance. The custom feature is missing metadata, which says that it embeds a driver so only seeing this message. In future versions the metadata is supposed to be fixed and you cannot see this message even though you provision the driver using custom feature.
TIBCO-AMX-ADMIN-030075 Requested driver feature {0}{1} is not found for resource instance {2}.
TIBCO-AMX-ADMIN-030076 Driver not found for resource instance {0}.
TIBCO-AMX-ADMIN-030077 Error installing resource instance {0} on node {1}.
TIBCO-AMX-ADMIN-030078 Error installing resource instance {0} on host {1}.
TIBCO-AMX-ADMIN-030079 HPA Manager not available for host type: {0}.
TIBCO-AMX-ADMIN-030080 Error while uninstalling resource instance {0} on node {1}.
TIBCO-AMX-ADMIN-030081 Error while uninstalling resource instance {0} on host {1}.
TIBCO-AMX-ADMIN-030082 Port {0} is being already used by resource instance {1} on node {2}.
TIBCO-AMX-ADMIN-030083 All the existing compatible driver features [ {0} ] are already installed on node {1}.
TIBCO-AMX-ADMIN-030084 Could not update driver defaults for resource templates.
TIBCO-AMX-ADMIN-030085 Node {0} is not running. Please start node and check the state.
TIBCO-AMX-ADMIN-030086 The resource instance is waiting for the following dependencies to be installed: {0}.
TIBCO-AMX-ADMIN-030087 Resource instance is in installed state and Node is also in running state, but the status emitted for resource instance might be missing.
TIBCO-AMX-ADMIN-030088 Compatible driver feature [{0}] for resource instance {1} already exists on node.
TIBCO-AMX-ADMIN-030089 Resource instance [{0}] is being used by applications [ {1} ].
TIBCO-AMX-ADMIN-030090 Port {0} is being used by node {1} on host {2}.
TIBCO-AMX-ADMIN-030091 Error while generating the resource packaging descriptor for resource instance {0}.
TIBCO-AMX-ADMIN-030092 The resource instance [{0}] is being used indirectly by one or more resource instances [{1}].
TIBCO-AMX-ADMIN-030093 The resource instance [{0}] is being used indirectly by one or more applications [{1}].
TIBCO-AMX-ADMIN-030094 Extension of resource template [{0}] is not registered to admin yet.
TIBCO-AMX-ADMIN-030095

Unable to determine whether the failed installation of the resource instance “{0}” has left any feature installed on the host. If it has, then a repeat installation of this resource instance also fails with the error code TIBCO-AMX-INFRA-000251.

If you see this behavior, you must manually remove the feature “{1}” from the host. Error from host: {2}.

TIBCO-AMX-ADMIN-030096 The current user does not have permissions to start / stop the application: {0}.
TIBCO-AMX-ADMIN-030097 Environment scope is required if the parent scope is an application scope type.
TIBCO-AMX-ADMIN-030098 Error while getting a resource template for the specified resource instance.
TIBCO-AMX-ADMIN-030099 Resource instance is not found “{0}”. Getting the resource template to create the resource instance.
TIBCO-AMX-ADMIN-030100 The resource template “{0}” is found in “{1}” scope.
TIBCO-AMX-ADMIN-030101 No resource instance with Id “{0}” was found. So cannot find dependencies for this resource instance.
TIBCO-AMX-ADMIN-030102 Creating resource instance {0} on node {1} using resource template {2} from “{3}” scope.
TIBCO-AMX-ADMIN-030103 Resource instance “{0}” not found on the specified scope “{1}”.
TIBCO-AMX-ADMIN-030104 Failed to create resource instance “{0}” because it already exists on node “{1}” and was created using resource template {2} from “{3}” scope.
TIBCO-AMX-ADMIN-030105 Failed to create resource instance “{0}”. Cannot create resource instance with a different name for application scope resource template. It should be the same as the resource template name.
TIBCO-AMX-ADMIN-030106 Name: “{0}”, Resource Template “{1}”, on Node: “{2}”, on Host: “{3}”.
TIBCO-AMX-ADMIN-030107 Action: “{0}”, ID: “{1}”, Name: “{2}”.
TIBCO-AMX-ADMIN-030108 Failed to create resource instance “{0}” because it already exists on node “{1}” and the resource template, which was used to create this resource instance was already deleted. This existing resource instance can only be uninstalled and deleted. It cannot be installed as the resource template was already deleted. If you want to uninstall/delete this resource instance, you can go to "Resource Instances" sub-tab under "Infrastructure -> Hosts -> (select a host)" OR "Infrastructure -> Nodes -> (select a node)".
TIBCO-AMX-ADMIN-030109 Failed to get the environment for resource instances “{0}”.
TIBCO-AMX-ADMIN-030110 Stand by state means that this HTTP connector is not yet accepting client requests. At the moment there are no running services or applications to process the requests, hence client connections are not being accepted. This HTTP connector is standing by for an application to be available (running) before activating itself.
TIBCO-AMX-ADMIN-030111 Resource instance “{0}” is using a substitution variable “{1}” for attribute “{2}”, but the substitution variable does not exist.