E_assertionNotFound30000 | Signifies that a particular publisher assertion (consisting of two businessKey values, and a keyed reference with three components) cannot be identified in a save or delete operation. |
Explanation |
The specified publisher assertion does not exist in the registry. |
Action |
Please make sure the publisher assertion exists before deleting or updating it. |
E_authTokenRequired10120AUTH | The authentication token value is missing in the authInfo argument of the UDDI request. |
Explanation |
The authInfo element is not present in the UDDI request. CentraSite requires the authInfo element to be present in the request with a valid authToken. |
Action |
Please make sure that authInfo is present in UDDI request. |
E_authTokenRequired10120DEF | Signifies that an invalid authentication token was passed to an API call that requires authentication. |
Explanation |
The authentication token passed is not valid. |
Action |
Please fetch the authentication token using get_authToken API and use it in the API. |
E_authTokenRequired10120INVAUTH | The authentication token value {0} passed in the authInfo argument of the UDDI request is not valid. |
Explanation |
The authentication token passed is not valid. |
Action |
Please fetch the authentication token again using get_authToken API and use it in the API. |
E_fatalError10500 | {0} |
Explanation |
Fatal error occurred while processing the request. |
Action |
Please retry and make sure the UDDI request is valid. |
E_fatalError10500APPDOWN | UDDI application not properly initialized. Please try restarting the CentraSite server. |
Explanation |
UDDI application received UDDI API calls before the UDDI web application initialized properly. |
Action |
Restart the CentraSite server. |
E_fatalError10500CUSTOWN | Custody and Ownership Transfer API calls are not supported when security policy is Deactivated |
Explanation |
CentraSite needs a security policy to be activated for processing the Custody and Ownership Transfer API. |
Action |
Please activate a security policy. |
E_fatalError10500INFOSEL | Attribute infoSelection is not present in request. |
Explanation |
The get_registeredInfo API requires the infoSelection attribute. If it is not present in the request then this error will occur. |
Action |
Please make sure the infoSelection attribute is present in the get_registeredInfo request. |
E_fatalError10500INVFINDGET | Invalid find_xx or get_xx api specified in the subscriptionFilter |
Explanation |
The subscriptionFilter does not contain the valid UDDI v3 subscription filter. |
Action |
Please make sure the subscription filter in the save_subscription request is valid. |
E_fatalError10500KREFNATB | KeyedReference does not contain required attribute. |
Explanation |
The KeyedReference should contain the keyValue attribute. |
Action |
Please make sure the keyedReference in the request has attribute keyValue. |
E_fatalError10500MISCFAT | Saving subscription failed due to internal registry error. |
Explanation |
Internal registry error. |
Action |
Please retry the request. |
E_fatalError10500MSE | Search limit exceeded, maximum allowed is {0}. Contact node operator to increase the search limit. |
Explanation |
Maximum search limit reached. |
Action |
Please reduce the number of search keys in the inquiry request or increase the search limit via the System Management Hub. |
E_fatalError10500PERF | Performance metrics with key {0} cannot be saved. Please make sure Performance Log is enabled in SMH. |
Explanation |
The user is trying to save performance metrics, but the performance log is disabled in SMH. Performance metrics will be saved only if the performance log is enabled in SMH. |
Action |
Please make sure the performance log is enabled in SMH. |
E_fatalError10500SUBKEXP | The subscription with subscriptionKey {0} has expired. Please renew this subscription. |
Explanation |
The subscription has expired as the specified expiration date has been reached. |
Action |
Please renew the subscription by saving it with a new expiration date. |
E_invalidCombination40500QUA | The combination of Qualifiers is not allowed |
Explanation |
Invalid find qualifier combinations were found in the request. |
Action |
Please make sure the combination of find qualifiers present in the inquiry request is valid. The invalid combinations are: andAllKeys, orAllKeys and orLikeKeys are mutually exclusive; sortByNameAsc and sortByNameDesc are mutually exclusive; sortByDateAsc and sortByDateDesc are mutually exclusive; combineCategoryBags, serviceSubset and bindingSubset are mutually exclusive; exactMatch and approximateMatch are mutually exclusive; exactMatch and caseInsensitiveMatch are mutually exclusive; binarySort and UTS-10 are mutually exclusive, as are all collation algorithm tModels with each other; diacriticSensitiveMatch and diacriticInsensitiveMatch are mutually exclusive; exactMatch and diacriticInsensitiveMatch are mutually exclusive; caseSensitiveSort and caseInsensitiveSort are mutually exclusive; caseSensitiveMatch and caseInsensitiveMatch are mutually exclusive. |
E_invalidCompletionStatus30100 | {0} is not a valid completion status. |
Explanation |
An invalid value was passed for completion status argument. Valid completion status are status:complete, status:fromKey_incomplete, status:toKey_incomplete and status:both_incomplete. |
Action |
Please provide a proper completion status. |
E_invalidKeyPassed10210 | No matching key found in the registry for {0}. |
Explanation |
CentraSite does not contain any UDDI entity with the key specified in the UDDI request. |
Action |
Please make sure the key specified in the request is valid. |
E_invalidKeyPassed10210BEBEK | Could not find the business entity corresponding to the business key. |
Explanation |
CentraSite does not contain any business entity with the key specified in the UDDI request. |
Action |
Please make sure the business key specified in the request is valid. |
E_invalidKeyPassed10210BEBK | Could not find the business service corresponding to the binding key {0}. |
Explanation |
CentraSite does not contain a business service corresponding to the service key specified in the binding template. |
Action |
Please make sure the service key specified in the request is valid. |
E_invalidKeyPassed10210BEMAT | No businessEntity in the UDDI registry matched the key {0}. |
Explanation |
CentraSite does not contain any business entity with the key specified in the UDDI request. |
Action |
Please make sure the business key specified in the request is valid. |
E_invalidKeyPassed10210BKBE | Tried to get a businessEntity with key {0}, but key did not match with any existing businessEntities. |
Explanation |
CentraSite does not contain any business entity with the business key specified in the UDDI request. |
Action |
Please make sure the business entity with the specified business key exists in CentraSite. |
E_invalidKeyPassed10210BKINV | BusinessKey invalid. |
Explanation |
The BusinessKey specified in the request is invalid. |
Action |
Please make sure the specified businessKey is valid. |
E_invalidKeyPassed10210BKMAT | No bindingTemplate in the UDDI registry matched the key {0}. |
Explanation |
CentraSite does not contain a binding template with the key specified in the UDDI request. |
Action |
Please make sure the binding key specified in the request is valid. |
E_invalidKeyPassed10210BSMAT | No businessService in the UDDI registry matched the key {0}. |
Explanation |
CentraSite does not contain a business service with the key specified in the UDDI request. |
Action |
Please make sure the service key specified in the request is valid. |
E_invalidKeyPassed10210BSNE | A businessService with key {0} does not exist. |
Explanation |
CentraSite does not contain a business service with the key specified in the UDDI request. |
Action |
Please make sure the service key specified in the request is valid. |
E_invalidKeyPassed10210BSNF | Could not find the businessService corresponding to the service key {0} |
Explanation |
CentraSite does not contain a business service corresponding to the service key specified in the binding template. |
Action |
Please make sure the service key specified in the request is valid. |
E_invalidKeyPassed10210BT | The bindingKey of the bindingTemplate to save does not match any existing bindingTemplate in the UDDI registry. |
Explanation |
CentraSite does not contain a binding template with the key specified in the UDDI request. |
Action |
Please make sure the binding key specified in the request is valid. |
E_invalidKeyPassed10210BTNF | Could not find the binding Template corresponding to the binding key {0} |
Explanation |
CentraSite does not contain a binding template with the key specified in the UDDI request. |
Action |
Please make sure the binding key specified in the request is valid. |
E_invalidKeyPassed10210BTSK | The bindingTemplate to save does not contain a serviceKey. |
Explanation |
The binding template to be saved does not contain the service key required for this binding template. The service key has to be specified when saving a binding template. |
Action |
Please specify a valid service key in the UDDI request. |
E_invalidKeyPassed10210CAT | Invalid tModelKey in categoryBag. |
Explanation |
The category bag should contain keyedReference/KeyedReferenceGroups with valid values for tModelKey and KeyValue. |
Action |
Please specify valid values for tModelKey/KeyValue in the category bag. |
E_invalidKeyPassed10210DBE | Tried to delete a businessEntity with key {0}, but key did not match with any existing businessEntities. |
Explanation |
CentraSite does not contain any business entity with the business key specified in the delete request. |
Action |
Please make sure the business key specified in the request is valid. |
E_invalidKeyPassed10210DEF | Signifies that the uuid_key value passed did not match with any known key values. |
Explanation |
CentraSite does not contain any UDDI entity with the key specified in the UDDI request. |
Action |
Please make sure the key specified in the request is valid. |
E_invalidKeyPassed10210DELSUB | Tried to delete a subscription with key {0}, but key did not match with any existing subscriptions. |
Explanation |
CentraSite does not contain any subscription with the key specified in the delete request. |
Action |
Please make sure the key specified in the request is valid. |
E_invalidKeyPassed10210EMTTMBAG | Tmodel bag is empty |
Explanation |
TModelBag cannot be empty, but the UDDI request contains an empty tModelBag. |
Action |
Please make sure tModelBag contains the required values. |
E_invalidKeyPassed10210FRMK | No businessEntity in the UDDI registry matched the fromKey {0} |
Explanation |
The fromKey specified in the add_publisherAssertion request is either invalid, or no business entity matched the fromKey. |
Action |
Please make sure the fromKey specified in the request is valid. |
E_invalidKeyPassed10210HIDTM | Tried to delete a tModel with key {0} which is not hidden. |
Explanation |
Hidden Tmodels cannot be deleted. |
Action |
Hidden tModels cannot be deleted. Please update the tModel and delete it. |
E_invalidKeyPassed10210IBAG | Invalid tModelKey in identifierBag. |
Explanation |
The identifier bag should contain keyedReference/KeyedReferenceGroups with valid values for tModelKey and KeyValue. |
Action |
Please specify valid values for tModelKey/KeyValue in the identifier bag. |
E_invalidKeyPassed10210INVKEY | The Key {0} is invalid. |
Explanation |
The specified key is not valid. |
Action |
Please make sure the key is valid according to the UDDI standard. |
E_invalidKeyPassed10210INVTMK | Invalid tModelKey {0}. |
Explanation |
CentraSite does not contain a TModel with the key specified in the UDDI request. |
Action |
Please specify a valid tModelKey in the UDDI request. |
E_invalidKeyPassed10210KBAGK | key {0} passed in the key bag does not match any businessEntity or tModel. |
Explanation |
CentraSite does not contain a business entity or tModel with the key specified in key bag of the discard_transferToken request. |
Action |
Please specify a valid business key or tModel key in the key bag. |
E_invalidKeyPassed10210KREF | KeyedReference should be passed ! |
Explanation |
The publisher assertion should contain a keyedReference and it is missing in the UDDI request. |
Action |
Please specify a KeyedReference for the publisher assertion. |
E_invalidKeyPassed10210MITS | Multiple instances of the same {0} {1} were passed. |
Explanation |
Keys should be unique for all UDDI entities. The UDDI request contains an existing UDDI entity key. |
Action |
Please provide a unique key for the UDDI entity. |
E_invalidKeyPassed10210MREF | The tModelKey cannot have multiple references to be deleted. |
Explanation |
Multiple references of a tModelKey were specified in the UDDI request. |
Action |
Please make sure that a single reference exists for a single tModelKey in the request. |
E_invalidKeyPassed10210NBE | Tried to update a businessEntity with key {0}, but no businessEntity in the UDDI registry matched the key. |
Explanation |
CentraSite does not contain any business entity with the business key specified in the save request. |
Action |
Please make sure the business key specified in the request is valid. |
E_invalidKeyPassed10210NULTM | Tried to delete a tModel with key, but the key did not match with any existing tModel or it is null. |
Explanation |
CentraSite does not contain any TModel with the key specified in the delete request. |
Action |
Please make sure the key specified in the request is valid. |
E_invalidKeyPassed10210OPINFMAT | No OperationalInfo in the UDDI registry matched the key {0}. |
Explanation |
The operational info cannot be found for the given key. |
Action |
Please make sure the key specified in the request is valid. |
E_invalidKeyPassed10210PAINV | The Publisher Assigned Key {0} is not a valid key. |
Explanation |
The key provided for the UDDI entity by the publisher is not valid. |
Action |
Please specify the key according to the UDDI standard |
E_invalidKeyPassed10210PANAL | The Publisher Assigned Key is not allowed. |
Explanation |
The user is not allowed to assign keys for the UDDI entity (CentraSite object). |
Action |
Save the UDDI entity without assigning a key to it. |
E_invalidKeyPassed10210SUBMAT | No subscription in the UDDI registry matched the key {0}. |
Explanation |
CentraSite does not contain any subscription with the key specified in the delete request. |
Action |
Please make sure the key specified in the request is valid. |
E_invalidKeyPassed10210SUBNE | The subscription having subscriptionKey as {0} does not exist. |
Explanation |
CentraSite does not contain any subscription with the key specified in the delete request. |
Action |
Please make sure the key specified in the request is valid. |
E_invalidKeyPassed10210TMIBK | Invalid tModelKey in tModelInstanceInfo for BindingKey {0}. |
Explanation |
The specified binding template does not contain a valid tModelKey in tModelInstanceInfo. |
Action |
Please make sure the tModelKey specified in tModelInstanceInfo of the binding template is valid. |
E_invalidKeyPassed10210TMKN | TModelvalue should not be null ! |
Explanation |
The key value of KeyedReference does not contain a valid value. |
Action |
Please specify a valid key value for the KeyedReference. |
E_invalidKeyPassed10210TMKNF | No matching tmodelkey was found. Please check that the tModelKey is of relationship type. |
Explanation |
CentraSite does not contain a tModel with the key specified in the UDDI request. |
Action |
The tModelKey of the keyedReference in the publisher assertion must be the key of the uddi-org:relationships tModel. |
E_invalidKeyPassed10210TMKREF | tModelKey not specified in one of the keyedReferenceGroup. |
Explanation |
The tModel key has to be specified for all KeyedReferenceGroups. |
Action |
Please specify a valid tModel key for all KeyedReferenceGroups. |
E_invalidKeyPassed10210TMMAT | No tModel in the UDDI registry matched the key {0}. |
Explanation |
CentraSite does not contain a tModel with the key specified in the UDDI request. |
Action |
Please specify a valid tModel key in the UDDI request. |
E_invalidKeyPassed10210TMNF | The specified tModelkey {0} cannot be found. |
Explanation |
CentraSite does not contain a TModel with the key specified in the UDDI request. |
Action |
Please specify a valid tModelKey in the UDDI request. |
E_invalidKeyPassed10210TOK | No businessEntity in the UDDI registry matched the toKey {0} |
Explanation |
The toKey specified in the add_publisherAssertion request is either invalid or no business entity matched the toKey. |
Action |
Please make sure the toKey specified in the request is valid. |
E_invalidKeyPassed10210USUBK | Tried to update a subscription with key {0}, but no subscription in the UDDI registry matched the key. |
Explanation |
CentraSite does not contain any subscription with the key specified in the delete request. |
Action |
Please make sure the key specified in the request is valid. |
E_invalidKeyPassed10210UTM | Tried to update a TModel with key {0}, but no TModel in the UDDI registry matched the key. |
Explanation |
CentraSite does not contain a TModel with the key specified in the UDDI request. |
Action |
Please specify a valid tModelKey in the UDDI request. |
E_invalidProjection20230 | No businessService with service key {0} exists in the UDDI registry. |
Explanation |
CentraSite does not contain a business service with the key specified in the UDDI request. |
Action |
Please make sure the service key specified in the request is valid. |
E_invalidTime40030 | Invalid time period specified or the date/time pair is invalid. |
Explanation |
The date/time provided in the UDDI request is not valid. |
Action |
Please provide the date/time in the format specified in UDDI specification. |
E_invalidValue20200EXPAFTDAT | The specified expiresAfter date value is incorrect |
Explanation |
The specified expiresAfter value for the subscription is not in the proper format. |
Action |
Please provide expiresAfter in the proper format. |
E_invalidValue20200EXPAFTVAL | expiresAfter has a value older than the current date/time. |
Explanation |
The expiresAfter element of the subscription denotes when the subscription will expire. However, the value specified in the expiresAfter element is older than the current time. |
Action |
Please provide a newer date/time value than the current time for the expiresAfter attribute. |
E_invalidValue20200INV | {0} is not a valid value |
Explanation |
The specified attribute does not contain a valid value in the UDDI request. |
Action |
Please provide a valid value. |
E_invalidValue20200INVVAL | Invalid Value: {0} |
Explanation |
The key value of the relationship KeyedReference is invalid. |
Action |
Please provide a valid key value. |
E_invalidValue20200KNAMNUL | keyName and keyValue should be specified for {0} keyedReference |
Explanation |
In UDDI, the keyedReference with tModelKey “uddi:uddi.org:categorization:general_keywords or uuid:A035A07C-F362-44dd-8F95-E2B134BF43B4” has different behavior. Unchecked value sets can be specified using this KeyedReference. Since this is unchecked, the value sets keyName and KeyValue are mandatory. |
Action |
Please provide a value for KeyName and the KeyValue attribute of the uddi-org:general_keywords KeyedReference. |
E_invalidValue20200KVALINV | The attribute keyValue {0} for keyedReference {1} failed validation. |
Explanation |
Validation failed for the KeyedReference as it does not contain a proper key value. |
Action |
Please provide valid key value. |
E_invalidValue20200KVALNUL | The attribute keyValue should not be null for a keyedReference. |
Explanation |
KeyValue is a mandatory attribute and it should contain a valid value. |
Action |
Please provide a value for the KeyValue attribute of KeyedReference. |
E_invalidValue20200MAXENT | maxEntities has a negative value. |
Explanation |
The maxEntities attribute of the subscription should contain a positive number. |
Action |
Please provide a positive value for the maxEntities attribute. |
E_invalidValue20200NOVAL | For asynchronous subscription, both the bindingKey and notificationInterval values should be specified |
Explanation |
To identify whether a subscription is asynchronous or synchronous, the elements bindingKey and notificationInterval are used. Element bindingKey is used to identify to which web service/email address the notification has to be sent. Element notificationInterval is used to identify how often the notification has to be sent. Both elements are required for asynchronous subscription. |
Action |
Please provide values for the bindingKey and notificationInterval attributes for asynchronous subscription. |
E_invalidValue20200NTFINT | {0} is not a valid value for notification interval. |
Explanation |
The notificationInterval attribute has to be specified in xsd:duration format. |
Action |
Please provide notificationInterval attribute in xsd:duration format. |
E_tokenAlreadyExists40070 | Token Generated for key {0} has expired or the token is already occupied for the specified entities. |
Explanation |
CentraSite already generated a transfer token for the specified entities. |
Action |
Please re-generate the token or use the existing token for the specified entities. |
E_transferNotAllowed40600DEF | Transfer Not Allowed!! |
Explanation |
CentraSite does not allow this transfer. The specified transfer token is not present in CentraSite. It might be discarded. |
Action |
Transfer of the entities are not allowed |
E_transferNotAllowed40600DNE | TransferToken does not exist. |
Explanation |
The specified transfer token does not exist in CentraSite. It might be invalid or discarded. |
Action |
Please generate new transfer token. |
E_transferNotAllowed40600INV | Transfer not allowed. Custody (Operator) or ownership are not same. |
Explanation |
CentraSite does not allow the entities to be transferred if the owners or operator are not the same. |
Action |
Operator and ownership must be the same to transfer entities. |
E_transferNotAllowed40600TCBE | Transfer the custody of this businessEntity {0} to the node {1} on which it is modified. |
Explanation |
CentraSite does not support transferring the node businessEntity. |
Action |
The transfer is not allowed for this business entity. |
E_transferNotAllowed40600TCBS | Transfer the custody of this businessService {0} to the node {1} on which it is modified. |
Explanation |
The node of the businessService does not match the CentraSite node businessEntity. |
Action |
Transfer is not allowed for this businessService. |
E_transferNotAllowed40600TCBT | Transfer the custody of this bindingTemplate {0} to the node {1} on which it is modified. |
Explanation |
The node of the bindingTemplate does not match the CentraSite node businessEntity. |
Action |
Transfer is not allowed for this bindingTemplate. |
E_transferNotAllowed40600TCTM | Transfer the custody of this tModel {0} to the node {1} on which it is modified. |
Explanation |
The node of the tModel does not match the CentraSite node businessEntity. |
Action |
Transfer is not allowed for this tModel. |
E_transferNotAllowed40600TTNEX | This TransferToken does not exist. |
Explanation |
CentraSite does not contain the specified transfer token. |
Action |
Please fetch a new transfer token. |
E_unknownUser10150ID | User ID {0} and password pair passed in a get_authToken API is unknown to the UDDI node or is not valid. |
Explanation |
A user ID in the get_authToken request is mandatory, but the userId element in the get_authTokenRequest request is null. |
Action |
Please provide a valid user ID and password in the get_authToken request. |
E_unknownUser10150PASS | User ID and password {0} pair passed in a get_authToken API is unknown to the UDDI node or is not valid. |
Explanation |
The cred element in the get_authToken request is mandatory, but the cred element in the get_authTokenRequest request is null. |
Action |
Please provide a valid user ID and password in the get_authToken request. |
E_unrecognizedVersion10040 | Namespace {0} is unsupported by the node being queried. |
Explanation |
The request is not a valid UDDI request or the request cannot be processed by CentraSite. |
Action |
Please provide a valid UDDI request as defined in the UDDI specification. |
E_unsupported10050 | Feature {0} is not supported. |
Explanation |
The request is not a valid UDDI request or the request cannot be processed by CentraSite. |
Action |
Please provide a valid UDDI request as defined in the UDDI specification. |
E_unsupported10050AUTH | authInfo element present in get_assertionStatusReport element is required. |
Explanation |
Authorization is required to process the get_assertionStatusReport call. |
Action |
Please provide an authInfo element with a proper authToken in the get_assertionStatusReport call. Please fetch the authToken using a get_authToken call. |
E_unsupported10050INVFINDGET | Invalid find_xx or get_xx api specified in the subscriptionFilter or some part of the subscription to be saved is invalid. |
Explanation |
The subscription filter for the subscription is not valid. |
Action |
Please provide the subscription filter for the subscription according to the UDDI specification. |
E_unsupported10050INVFQ | {0} is not a valid find qualifier value in version {1}. |
Explanation |
The provided find qualifier is not valid. The valid qualifiers can be found in UDDI specification. |
Action |
Please provide find qualifiers compliant with the UDDI specification. |
E_unsupported10050NINV | The notification interval specified is less than {0}. Please increase the notification interval. |
Explanation |
UDDI configuration parameter UDDIMinimalNotificationInterval specified the minimal notification interval that the UDDI engine can handle. If the given value is less than the UDDIMinimalNotification interval then this error will occur. |
Action |
Please increase the notification interval |
E_unsupported10050QUA | This Qualifier is not allowed with FindBinding Inquiry API. |
Explanation |
The find qualifiers binarySort, bindingSubset, caseInsensitiveSort, caseSensitiveSort, combineCategoryBags, sortByNameAsc, sortByNameDesc, serviceSubset and suppressProjectedServices are not supported in the find_binding call. |
Action |
Please specify find qualifiers other than binarySort, bindingSubset, caseInsensitiveSort, caseSensitiveSort, combineCategoryBags, sortByNameAsc, sortByNameDesc, serviceSubset and suppressProjectedServices for the find_binding call. |
E_unsupported10050QUARELB | This Qualifier is not allowed with FindRelatedBusinesses Inquiry API. |
Explanation |
The find qualifiers andAllKeys, bindingSubset, combineCategoryBags, orAllKeys, orLikeKeys, serviceSubset and suppressProjectedServices are not supported in the find_relatedBusinesses call. |
Action |
Please specify find qualifiers other than andAllKeys, bindingSubset, combineCategoryBags, orAllKeys, orLikeKeys, serviceSubset and suppressProjectedServices for the find_relatedBusinesses call. |
E_unsupported10050QUARSER | This Qualifier is not allowed with FindService Inquiry API. |
Explanation |
The serviceSubset find qualifier is not supported in the find_service call. |
Action |
Please remove the serviceSubset find qualifier from the find_service request. |
E_unsupported10050QUARTM | This Qualifier is not allowed with FindTModel Inquiry API. |
Explanation |
The find qualifiers bindingSubset, combineCategoryBags, serviceSubset and suppressProjectedServices are not supported in the find_tModel call. |
Action |
Please specify find qualifiers other than bindingSubset, combineCategoryBags, serviceSubset and suppressProjectedServices for the find_tModel call. |
E_unvalidatable20220UNVALID | The referenced tModel has been marked unvalidatable. |
Explanation |
CentraSite does not allow an unvalidatable KeyedReference to be present in the UDDI request. |
Action |
The specified tModel cannot be used in the keyedReference. |
E_userMismatch10140 | Signifies that an attempt was made to use the publishing API to change data that is controlled by another party. |
Explanation |
An access violation exception occurred as the user tried to modify a UDDI entity owner by another user. |
Action |
Please make sure proper permissions are assigned to the user to update the entity. |
E_userMismatch10140DELSUBUSR | Tried to delete a subscription that is controlled by another individual. |
Explanation |
An access violation exception occurred as the user tried to delete the subscription owned by another user. |
Action |
Please provide the authToken of the user who owns the subscription. |
E_userMismatch10140DIFSUB | The owner of the subscription is different. |
Explanation |
The subscription is not owned by the specified user. |
Action |
Please provide the authToken of the user who owns the subscription. |
E_userMismatch10140FRMTOK | USER-MISMATCH for publisherAssertion fromKey {0} and toKey {1}. |
Explanation |
The user should own the business specified in fromKey or toKey. |
Action |
Please provide the business key owned by the user either in fromKey or in toKey. |
E_userMismatch10140PBE | You are not authorized to publish a businessEntity. |
Explanation |
The user does not have permission to create a business in CentraSite. |
Action |
Please make sure the user has permission to create a business in CentraSite. |
E_userMismatch10140TT | You are not authorized to get the TransferToken for the key {0} which is owned by another publisher. |
Explanation |
The transfer token for an entity can be fetched by the user who owns the entity. Transfer token for the entities which the user does not own cannot be fetched. |
Action |
Please provide the key of the owned UDDI entity. |
E_userMismatch10140UEK | Tried to update the {0} {1} that is controlled by another individual. |
Explanation |
The user does not own or does not have permission to update the UDDI entity. |
Action |
Make sure the user has permission to update the UDDI entity, or make sure the user owns the UDDI entity. |
E_userMismatch10140USUBUSR | Tried to update the subscription with key {0}, that is controlled by another individual. |
Explanation |
The subscription is not owned by the specified user. |
Action |
Please provide the authToken of the user who owns the subscription. |
E_valueNotAllowed20210NODE | This checked category system is only permitted to be used by the node itself. |
Explanation |
The node business cannot be updated by the user. |
Action |
The node business cannot be updated by the user. |
INMAFE0001 | The registry object must not be null. |
Explanation |
The constructor CSAppFixedRegistryObject() is trying to create a new instance so the registry object passed can't be null. |
Action |
Pass valid registry object. |
INMAFE0002 | A fixed registry object's name cannot be changed. |
Explanation |
This is a fixed Registry Object. It's name must not be changed. |
Action |
Don't change a fixed registry object's name. |
INMAFE0003 | Different object with duplicate key already registered: {0} |
Explanation |
Two different objects that have the same keys are being registered. |
Action |
Check for any reasons why the duplicate keys exist or change one of the object's keys. |
INMAFE0004 | Different association type with duplicate name already registered {0} |
Explanation |
Two different associations that have the same names are being registered. |
Action |
Change one of the association's names. |
INMAFE0005 | Different object type with duplicate name already registered {0} |
Explanation |
Object types have to have unique names. |
Action |
Change the object type name to a unique one. |
INMAFE0006 | Different child list already registered for parent path: {0} |
Explanation |
for this path there is already a defined child list. |
Action |
Create another parent path to add the new child list. |
INMAFE0007 | Unknown taxonomy: {0} |
Explanation |
The desired taxonomy does not exist. |
Action |
Use an existing Taxonomy. |
INMAFE0008 | Multiple taxonomies named {0} found. |
Explanation |
Taxonomies must have unique names. |
Action |
Find a way to make the used taxonomies have a unique name. |
INMAFE0010 | Different object with duplicate name already registered: {0} |
Explanation |
The objects are classification schemes, their names must be unique. |
Action |
Find a way to change the object names to unique ones. |
INMAFE0011 | No such concept: {0} |
Explanation |
This Concept does not exist in the database. |
Action |
Create such a Concept or change to an existing one. |
INMAFE0012 | No such classification scheme: {0} |
Explanation |
This classification scheme does not exist in the database. |
Action |
Create a new one or change to an existing classification scheme. |
INMAFE0013 | No such association type: {0} |
Explanation |
This association type does not exist in the database. |
Action |
Create a new one or change to an existing association type. |
INMAFE0014 | No such object type: {0} |
Explanation |
This object type does not exist in the database. |
Action |
Create a new one or change to an exisitng object type. |
INMAFE0015 | Child list not available for parent {0}, did you set the cache strategy 'childs'? |
Explanation |
The cache strategy "childs" needs to be set in order to access child concepts. |
Action |
Set the cache strategy 'childs'. |
INMAFE0017 | Child list not available for taxonomy {0}, did you set the cache strategy 'childs'? |
Explanation |
The cache strategy "childs" needs to be set in order to access child concepts. |
Action |
Set the cache strategy 'childs'. |
INMAFE0018 | Child list not available for parent concept {0}, did you set the cache strategy 'childs'? |
Explanation |
The cache strategy "childs" needs to be set in order to access child concepts. |
Action |
Set the cache strategy childs. |
INMAFE0019 | No object with key {0} is known by the pool. |
Explanation |
No fixed RegistryObject was found in the bean pool. |
Action |
The fixed registry object must be added to the bean pool. |
INMAFE0021 | Invalid element {0}, expected either of {1} |
Explanation |
The specified element is not contained in the list of expected elements. |
Action |
Use or change the element to one of the expected types. |
INMAFE0023 | Missing attribute: {0} |
Explanation |
The searched attribute is mandatory and must be provided. |
Action |
Provide the missing attribute or change it so it is not mandatory any more. |
INMAFE0024 | Empty attribute: {0} |
Explanation |
The attribute is empty. |
Action |
Provide data for the attribute. |
INMAFE0025 | Duplicate objectType name: {0} |
Explanation |
Object Types must have unique names. |
Action |
Provide a unique name for the object type, delete or rename the existing one. |
INMAFE0026 | Duplicate associationType name: {0} |
Explanation |
The assoiation type name must be unique. |
Action |
Provide a unique association type name, delete or rename the exisitng one. |
INMAFE0027 | Duplicate taxonomy name: {0} |
Explanation |
Taxonomy name must be unique. |
Action |
Provide unique name for the Taxonomy, rename or delete the existing one. |
INMAFE0028 | Invalid value for {0} |
Explanation |
The specified value is invalid. |
Action |
Provide valid value. |
INMAFE0029 | Invalid element {0}, expected {1} |
Explanation |
The specified element does not match the expected element. |
Action |
The element must be changed accordingly to the expected item. |
INMAFE0031 | Duplicate concept value for taxonomy {0} |
Explanation |
Taxonomy must have a unique concept value. |
Action |
Provide a unique concept value for the taxonomy. |
INMAFE0032 | Duplicate concept value for concept {0} |
Explanation |
Concept must have a unique concept value. |
Action |
Provide a unique concept value for the concept. |
INMAFE0033 | Invalid argument: {0} |
Explanation |
The specified argument is invalid. |
Action |
Provide a valid argument. |
INMAFE0034 | The class {0} has no annotation of type {1} or has an empty 'implementation' attribute. |
Explanation |
The given class does not have the expected annotation, or the annotation's "implementation" attribute is empty. |
Action |
Provide an annotation of the given type or fill in the 'implementation' attribute. |
INMAFE0037 | The object type's qualified name must not be null. |
Explanation |
One of the arguments has a null value. |
Action |
Provide arguments with a valid value. |
INMAFE0038 | A classification's scheme must not be null. |
Explanation |
The classification has a null value. |
Action |
Provide a valid value for classification. |
INMAFE0039 | A classification's value must not be null. |
Explanation |
The classification has a null value. |
Action |
Provide a valid value for classification. |
INMAFE0040 | The object type's qualified name must not be null. |
Explanation |
The object type's qualified name has null value. |
Action |
Provide a valid value for object type's qualified name. |
INMAFE0041 | The classification schemes must not be null. |
Explanation |
The classification schemes have a null value. |
Action |
Provida a valid value for the classification schemes. |
INMAFE0042 | This object is unmodifiable. |
Explanation |
The object cannot be modified. |
Action |
Do not try to modify the object. |
INMAFE0043 | Unknown property {0} |
Explanation |
The property has unknown value. |
Action |
Provide a valid value for the property. |
INMAFE0044 | The IOC annotation of the field {0} has no ID or an empty ID. |
Explanation |
Some annotation has an empty ID or no ID. |
Action |
Provide a valid ID for the annotation. |
INMAFE0045 | The object to initialize must not be null. |
Explanation |
The initializer has a null value. |
Action |
Provide a valid value for the initializer. |
INMAFE0046 | The document must not be null. |
Explanation |
The document is null. |
Action |
Provide a valid value for the document. |
INMAFE0047 | The QName {0} is invalid, because it contains no terminating '}' character. |
Explanation |
The value argument has no enclosing '}' character. |
Action |
Make sure the value argument has an enclosing '}' character. |
INMAFE0049 | Expected {0} element, got {1} |
Explanation |
The element is different than expected. |
Action |
Make sure the element type is as expected. |
INMAFE0051 | Missing attribute for {0} |
Explanation |
The attribute has a null value. |
Action |
Provide a valid value for the attribute. |
INMAFE0052 | Invalid attribute {0} for element {1} |
Explanation |
The attribute has an invalid value. |
Action |
Provide a valid value for the attribute. |
INMAFE0054 | The attribute {0} for element {1} is using an invalid prefix: {2} |
Explanation |
Some of the attributes have an invalid prefix. |
Action |
Make sure the attribute has a valid prefix. |
INMAFE0056 | Missing attribute: {0} |
Explanation |
Attribute is missing. |
Action |
Provide attribute. |
INMAFE0057 | Empty attribute: {0} |
Explanation |
Attribute is missing. |
Action |
Provide attribute. |
INMAFE0058 | The class {0} doesn't implement {1} |
Explanation |
Wrong class provided. |
Action |
Provide a valid class. |
INMAFE0116 | Missing @RegistryObject annotation on persistent class {0} |
Explanation |
The processed class has no @RegistryObject annotation. As long as there is no such annotation the persistent class cannot be considered a RegistryBean and cannot be processed. |
Action |
Add a @RegistryObject annotation to the persistent class interface or use different RegistryBean. |
INMAFE0119 | The given registry bean is managed by another pool: {0} |
Explanation |
A registry bean instance can be managed by one bean pool only. For example it is not allowed to read a bean with one bean pool instance and update it with another. |
Action |
Check for multiple beanPool instances managing your registry beans. For a single thread, make one bean pool instance to handle the registry beans. |
INMAFE0121 | The given registry bean is not managed by the pool: {0} |
Explanation |
The registry bean is being used by a bean pool it does not belong to. |
Action |
Find and use the bean pool instance that this registry bean belongs to. For exmaple if a registry bean is read or created by one bean pool instance, this is the instance it belongs to and it cannot be managed by another one. |
INMAFE0123 | Missing information for attribute with name {0} of type {1} |
Explanation |
This attribute should have an attribute description but it does not. For example, attribute description is required for @Relationship , @DateAttribute and other attributes. |
Action |
When using @Relationship, @DateAttribute etc. an attributeName property must be specified, which corresponds to the name of an existing AttributeDescription. Either create new attribute description, or change the name of the attributeName property to an existing one. |
INMAFE0128 | The RegistryObject must be an association, but is a {0} |
Explanation |
The RegistryObject to be processed must be a javax.xml.registry.infomodel.Association. The method is trying to create a RegistryBean instance from a javax.xml.registry.infomodel.Association instance. |
Action |
Check the mapping of theRegistryBean that is being created for any inconsistencies. |
INMAFE0129 | AssociationTarget property of {0} is null. Association target cannot be null. |
Explanation |
While creating a javax.xml.registry.infomodel.Association instance from a registry bean Association instance. The target of the association must be present in order to create a javax.xml.registry.infomodel.Association. |
Action |
Set target for the association. |
INMAFE0130 | Unable to determine object type. Missing RegistryObject annotation for class {0}. |
Explanation |
Either the processed registry bean is not a registry bean at all, or it is missing its RegistryObject annotation. Without it the registry bean cannot be created and it is not considered a registry bean. |
Action |
Either use a different registry bean that has a RegistryObject annotation, or add the annotation in the used registry bean interface. |
INMAFE0131 | Missing concept with key {0}. |
Explanation |
The key that is specified is either wrong or does not belong to a concept instance. |
Action |
Use a different object type key for this annotation. |
INMAFE0132 | Missing concept with name {0} |
Explanation |
The name that is specified is either wrong or does not belong to a concept instance. |
Action |
Use a different object type name for this annotation. |
INMAFE0133 | The RegistryObject must be a classification. |
Explanation |
The registry object to be processed must be a javax.xml.registry.infomodel.Classification instance. |
Action |
Use a registry object that is an instance of javax.xml.registry.infomodel.Classification. |
INMAFE0134 | ClassificationConcept property of {0} is null. The concept for internal classification cannot be null. |
Explanation |
The classification's concept property is not specified. |
Action |
Specify a concept for this classification. |
INMAFE0135 | Missing {0} annotation. {1} must be classified instance. |
Explanation |
The ClassifiedInstances annotation is missing. It must be present in order to create a ClassifiedInstances property. |
Action |
Add the ClassifiedInstances annotation to the registry bean. |
INMAFE0136 | {0} is not specified as ClassifiedInstance |
Explanation |
None of the bean interfaces is a classified instance in the ClassifiedInstances annotation's instances. |
Action |
Specify a bean interface as ClassifiedInstance. |
INMAFE0137 | Cannot find the required classification on {0} |
Explanation |
There is no corresponding classification for the given registry object. |
Action |
Provide the classification. |
INMAFE0138 | BeanInfo {0} for {1} must be instance of {2} |
Explanation |
The BeanInfo instance is not of type BackedBeanInfo. |
Action |
Make the BeanInfo an instance of BackedBeanInfo. |
INMAFE0139 | No setter found for property {0} in class {1} |
Explanation |
The name of the setter is different and a corresponding setter cannot be found in the jaxr representation of this registry bean. |
Action |
Change the name of the setter in the registry bean interface. |
INMAFE0140 | Missing type information for {0} |
Explanation |
The BeanType for this jaxr registry object cannot be found in the registry object model. It is not supported by CSAF. |
Action |
Add BeanType for the required jaxr registry object type in the registry object model. |
INMAFE0141 | Getter returns unexpected value type: {0} . Expected: Collection. For property: {1} in class: {2} |
Explanation |
The value returned by the getter method does not match the return type specified in the bean interface. |
Action |
Change the return type to collection or change the annotation used for this property. |
INMAFE0142 | No instance of SlotHandler registered for the type {0} |
Explanation |
None of the existing slot handlers handles the given property type. |
Action |
Add a slot handler or change the property type. |
INMAFE0143 | Expected RegistryObject of type javax.xml.registry.infomodel.User or javax.xml.registry.infomodel.Organization {0} |
Explanation |
The javax.xml.registry.infomodel.TelephoneNumbers support type can only be found in a javax.xml.registry.infomodel.User or javax.xml.registry.infomodel.Organization instance. |
Action |
Use a javax.xml.registry.infomodel.User or javax.xml.registry.infomodel.Organization instance for operations with javax.xml.registry.infomodel.TelephoneNumbers. |
INMAFE0144 | A Collection is expected {0} |
Explanation |
TelephoneNumbers is always a collection. Single property is not allowed. |
Action |
Use a collection of TelephoneNumbers. |
INMAFE0145 | Expected RegistryObject of type User or Organization RegistryBeans {0} |
Explanation |
The CSAF support type TelephoneNumbers can only be found in a User or Organization RegistryBean instance. |
Action |
Use a User or Organization RegistryBean instance for operations with CSAF TelephoneNumbers. |
INMAFE0146 | Beans to restore must be of BackedBeanInfo instance |
Explanation |
Only BackedBeanInfo instances can provide access to the underlying RegistryObject. |
Action |
Use BackedBeanInfo to provide access to the RegistryObject that is standing behind the RegistryBean. |
INMAFE0147 | Invalid bean mode |
Explanation |
The bean mode of a configuration can be BACKED or SIMPLE (has been deprecated). Any other bean mode set to the configuration will result in this exception. |
Action |
Set the bean mode of the configuration to BACKED. The BACKED constant is located under com.softwareag.centrasite.appl.framework.persistence.BeanMode.java. |
INMAFE0148 | The object to be read must be a RegistryObject instance: {0} |
Explanation |
The object to be read must be an instance of javax.xml.registry.infomodel.RegistryObject but is not. |
Action |
Read a different object that is of javax.xml.registry.infomodel.RegistryObject instance. |
INMAFE0149 | Unsupported value type passed: {0} |
Explanation |
The value type passed is not supported by this method and cannot be processed. |
Action |
Change the value Type or change the method you are using to process this value. For example, the toJaxrValue() method expects one of the support types defined in CSAF (EmailAddress, TelephoneNumbers etc.) and processes it to a JAXR support type , while the toBeanValue method does the opposite. |
INMAFE0150 | Missing type information for {0} |
Explanation |
No BeanType found in the registry object model for the given registry object. It is not supported by CSAF. |
Action |
Create a BeanType and add it to the registry object model for the given registry object type. |
INMAFE0151 | The BulkResponse collection must currently be java.util.List {0} |
Explanation |
The result method of the Search class always has to return a java.util.List object. |
Action |
Change the Search's BulkResponse collection to java.util.List. |
INMAFE0152 | Missing type information for {0} |
Explanation |
No BeanType found in the registry object model for the given registry object. It is not supported by CSAF. |
Action |
Create a BeanType and add it to the registry object model for the given registry object type. |
INMAFE0153 | Property is null, this kind of predicate is not allowed |
Explanation |
A predicate has bean created for a property that does not exist. |
Action |
Check the search criteria for wrong property names. |
INMAFE0154 | The given class: {0} is not supported |
Explanation |
No BeanType found for the given class in the registry object model. |
Action |
Add BeanType in the registry object model for the desired class. |
INMAFE0159 | Invalid attribute name. Attribute name must not contain a space or special characters. |
Explanation |
Creating a slot attribute with spaces or special characters in it's name is not allowed. |
Action |
Use camel case (example: SlotAttribute) or '_' (example: Slot_Attribute) in the name instead of space, or change the name in a different way that it does not contain spaces. |
INMAFE0160 | Invalid slot attribute data type. |
Explanation |
The data type passed when creating slot attribute is not supported. |
Action |
Change the data type to one that is supported. Constants with supported data types can be found in AttributeDescription class. |
INMAFE0161 | Unknown Error |
Explanation |
The error that has been thrown has unknown reasons. |
Action |
Contact your software supplier. |
INMAFE0162 | The parent concept must not be null. |
Explanation |
The Concept must have a parent. |
Action |
Add parent to the concept. |
INMAFE0163 | Invalid namespace prefix: {0} |
Explanation |
The namespace prefix is invalid. |
Action |
Change the namespace to a valid one. |
INMAFE0164 | Don't know how to handle skipped entity: {0} |
Explanation |
The Parser has encountered a skipped entity. CSAF does not support skipped entities. |
Action |
Exclude the skipped entities from the entity list. |
INMAFE0165 | Expected empty stack. |
Explanation |
The Parser has reached the end of the file, and its stack should be empty. |
Action |
Check the file for any inconsistencies or errors. |
INMAFE0166 | No getter for property {0} found in class {1} |
Explanation |
In order to access a RegistryBean property it must have a getter method. |
Action |
Provide a getter method for this RegistryBean property. In some cases the getter methods are not provided for a purpose. These RegistryBeans should be documented. |
INMAFE0167 | The method {0} in class {1} must be public, and neither static, nor abstract. |
Explanation |
There is a restriction that must be followed. |
Action |
Change the method to public and remove any static or abstract modifiers. |
INMAFE0168 | Failed to parse getter name: {0} |
Explanation |
A getter method follows a rule when created. It must begin with either get or is. Any other case will result in this exception. |
Action |
Rename the getter method so it follows the described rule. |
INMAFE0169 | The setter {0} in class {1} has return type {2} , not void. |
Explanation |
A setter method must have a void return type. |
Action |
Change the setter return type to void. |
INMAFE0170 | The method {0} in class {1} must be public, and not static. |
Explanation |
There is a restriction to this method, namely it must be public and not static. |
Action |
Follow the restriction. |
INMAFE0171 | Failed to parse method name: {0} |
Explanation |
The method must start with either get, set, has or is. This is necessary in order to be recognized by the parser so a property name can be extracted. |
Action |
Change the method name accordingly. |
INMAFE0172 | Illegal access to default constructor of class {0} : {1} |
Explanation |
Nested exception is thrown here. The constructor has to be called with an empty expression list, or check {1} for more information. |
Action |
Change the constructor accordingly. |
INMAFE0173 | Failed to instantiate class {0} : {1} |
Explanation |
Nested exception is thrown here. More details are found in {1} |
Action |
Handle according to the nested exception message. |
INMAFE0174 | Illegal access to default constructor of class {0} : {1} |
Explanation |
Nested exception is thrown here. The constructor has to be called with an empty expression list, or check {1} for more information. |
Action |
Change the constructor accordingly. |
INMAFE0175 | Failed to instantiate class {0} : {1} |
Explanation |
Nested exception is thrown here. More details are found in {1} |
Action |
Handle according to the nested exception message. |
INMAFE0176 | Failed to invoke constructor of class {0} : {1} |
Explanation |
Nested Exception. See {1} for more information. |
Action |
Handle the case according to information in {1}. |
INMAFE0177 | No field named {0} found in class {1} or any of its superclasses. |
Explanation |
The desired field is not present in the class, nor in any of the superclasses. |
Action |
Provide the missing field, or change the field name being searched. |
INMAFE0178 | Illegal access to field {0} in class {1} : {2} |
Explanation |
Nested Exception thrown, see {2} for more details. |
Action |
Handle according to the information in {2}. |
INMAFE0179 | Failed to load the class named {0}. |
Explanation |
The class with the given name was not found. |
Action |
Provide the missing class. |
INMAFE0180 | Invalid property specification: {0} |
Explanation |
The property has opening bracket [ but no closing bracket ]. |
Action |
Provide the closing bracket ] . |
INMAFE0181 | Invalid property specification: {0} |
Explanation |
The property was not specified correctly. |
Action |
Make sure that the property follows all rules. |
INMAFE0182 | No list was returned for property specification {0} |
Explanation |
This property is expected to return a list. |
Action |
Check the property for any inconsistencies. |
INMAFE0183 | No add method found for property {0} in class {1} |
Explanation |
The property must correspond to an add method, but it doesn't. |
Action |
Provide an add method, change the property or check the property for inconsistencies. |
INMAFE0184 | No remove method found for property {0} in class {1} |
Explanation |
The property must correspond to a remove method, but it doesn't. |
Action |
Provide a remove method, change the property or check the property for inconsistencies. |
INMAFE0185 | A fixed registry object's description cannot be changed. |
Explanation |
This registry object description cannot be changed. |
Action |
Don't attempt to change a fixed registry object's description. |
INMAFE0186 | The interface {0} doesn't have its implementation attribute set in the {1} annotation. |
Explanation |
Each interface bean needs to specify its implementation class. |
Action |
Please use correct value for the annotation attribute. |
INMAFE0187 | The key must not be null. |
Explanation |
Each key must have a non-null id value. |
Action |
Provide non-empty, unique key value. |
INMAFE0188 | The concept key must point to a Concept: {0} |
Explanation |
Classifications can only ne based on concepts. |
Action |
Make sure that the Classification's concept key is actually pointing to a Concept registry object. |
INMAFE0189 | The registry object type key must point to a Concept from the ObjectType taxonomy: {0} |
Explanation |
The required object needs to be a child of the "ObjectType" taxonomy. |
Action |
Make sure that object type key points to a Concept from the ObjectType taxonomy (Classification Scheme). |
INMAFE0190 | The association type key must point to a Concept from the AssociationType taxonomy: {0} |
Explanation |
The required object needs to be a child of the "AssociationType" taxonomy. |
Action |
Make sure that association type key points to a Concept from the AssociationType taxonomy (Classification Scheme). |
INMAFE0191 | The property is null. |
Explanation |
The getMapper() method requires a non-null property argument. |
Action |
Make sure the property is available. |
INMAFE0192 | No property mapper found for Property {0} |
Explanation |
The property mapper for the desired property does not exist. |
Action |
Make sure that a suitable property mapper is available for this property. |
INMAFE0193 | Wrong value type passed. Expected Collection<com.softwareag.centrasite.appl.framework.beans.standard.TelephoneNumber> |
Explanation |
The method requires an argument of type "Collection". |
Action |
Make sure the correct value type is used. |
INMAFE0194 | Cannot parse string to long(timestamp) {0} |
Explanation |
The given value does not match the syntax rules for long numeric values. |
Action |
Expected long numeric value. |
INMAFE0195 | Cannot parse date string {0} |
Explanation |
The given value does not match the syntax rules for dates. |
Action |
Make sure the string is in the proper date format. |
INMAFE0196 | Unsupported value passed: {0}. String value expected: either {namespace}localPart or localPart only. |
Explanation |
The method expects a vlue of type "String". |
Action |
Please provide the correct value. |
INMAFE0197 | Unsupported value type {0} |
Explanation |
The KeyPredicate value type must be one of "String", "Key", or "RegistryBean". |
Action |
Please provide a valid value. |
INMAFE0198 | Unable to create predicate for : {0}. Check the passed sequence and try again. |
Explanation |
The values specified for the predicate cannot be properly converted to a query criterion. |
Action |
Please provide a valid predicate. |
INMAFE0199 | The given object is not a RegistryObject. |
Explanation |
The method requires a RegistryObject parameter. |
Action |
Please provide the correct object. |
INMAFE0200 | Given object is not Classification: {0} |
Explanation |
The method requires a Classification object. |
Action |
Please provide a valid Classification object. |
INMAFE0201 | Unsupported collection. Should be java.util.List or java.util.Set. |
Explanation |
The method requires a parameter of type List or Set. |
Action |
Please provide a collection of valid type. |
INMAFE0202 | Only attributes of type Slot can be indexed. |
Explanation |
Index definitions are only possible for Slot attributes. |
Action |
Use an attribute of valid type. |
INMAFE0203 | Value and forward label must not be null. |
Explanation |
When creating a new association type it is mandatory to specify a value and a forward label. |
Action |
Correct the application program. |
INMAFE0204 | Object type to be generated not found: {0} |
Explanation |
The object type name specified when calling the RegistryBeanGenerator does not exist. |
Action |
Specify an existing type name. |
INMAFE0205 | Invalid object ({0}) passed to delete operation |
Explanation |
The delete operation only accepts RegistryBean instances. In particular, NULL pointers are rejected. |
Action |
Call the delete operation with correct RegistryBean instances. |
INMAPE0001 | The user {0} does not have the view permission; contact the asset owner or administrator for help. |
Explanation |
If the current user has no permission to view this object, then this error will be thrown. |
Action |
The user needs to be provided proper permission to view this object. |
INMBUE0002 | Invalid URI {0}. |
Explanation |
You have entered an invalid URI. |
Action |
Enter a valid URI. |
INMBUE0003 | Invalid phone number. |
Explanation |
You have entered an invalid phone number. |
Action |
Enter a valid phone number. |
INMBUE0004 | Search scope is empty. |
Explanation |
You have not entered a valid search scope in the recipe. |
Action |
Enter a valid search scope. |
INMBUE0007 | Saved search token is not valid. |
Explanation |
You have entered an invalid saved search token in the URL. |
Action |
Enter a valid saved search token. |
INMBUE0009 | Failed to initialize the Unwatch action on selected assets. |
Explanation |
Could not initialize the Unwatch action on selected assets; possibly because one or more of the selected assets are not already watched. |
Action |
Choose the assets that are already watched. |
INMBUE0011 | Enter a valid IP address |
Explanation |
Enter a valid IP address |
Action |
Enter a valid IP address |
INMBUE0012 | Duplicate values for {0} |
Explanation |
A user was selected as an administrator, but this user has already been selected. |
Action |
Avoid selecting a user as administrator that has already been chosen. |
INMBUE0013 | Invalid URL |
Explanation |
You have entered an invalid URL. |
Action |
Enter a valid URL. |
INMBUE0014 | Enter a valid Administrator |
Explanation |
You have entered an invalid administrator name. |
Action |
Enter a valid administrator name. |
INMBUE0015 | Group name is empty |
Explanation |
You have not entered a group name while creating a local group. |
Action |
Enter a group name. |
INMBUE0016 | Invalid URI. |
Explanation |
You have entered an invalid URI. |
Action |
Enter a valid URI. |
INMBUE0017 | Invalid numeric value in attribute. |
Explanation |
You have entered an invalid numeric value for this attribute. |
Action |
Enter a valid numeric value. |
INMBUE0018 | Invalid attribute value. |
Explanation |
You have entered an invalid attribute value for the chosen type. |
Action |
Enter a valid value for the chosen type. |
INMBUE0019 | Required attribute value is empty. |
Explanation |
You have entered a blank value for the required attribute. |
Action |
Enter a value for the required attribute. |
INMBUE0020 | Enter a valid string value for the attribute. |
Explanation |
You have entered an invalid value for this string attribute. |
Action |
Enter a valid string value. |
INMBUE0021 | Enter a valid IP address. |
Explanation |
You have entered an invalid IP address. |
Action |
Enter a valid IP address. |
INMBUE0022 | Enter a valid email address. |
Explanation |
You have entered an invalid email address. You must enter a valid email address (e.g. example@example). |
Action |
Enter a valid email address (e.g. example@example). |
INMBUE0023 | Invalid category name. |
Explanation |
You have entered an invalid category name for this classification attribute. |
Action |
Enter a valid category name for the defined taxonomy. |
INMBUE0024 | Refresh interval is empty. |
Explanation |
Number. Required. An input denoting the time interval for refreshing a portlet automatically is not specified. |
Action |
Enter a value (in seconds) for refresh interval. |
INMBUE0025 | Required attribute value is empty. |
Explanation |
You have entered a blank value for the required attribute. |
Action |
Enter a value for the required attribute. |
INMBUE0026 | Invalid search condition. |
Explanation |
An invalid search condition has occurred. A search condition consists of one or more predicates, each joined by a keyword (ALL or ANY). A predicate can be a comparison predicate, such as an Equals predicate, NotEquals predicate, StartsWith predicate, or a Contains predicate. This error occurs when none of the above search conditions are met. |
Action |
Correct the search condition. |
INMBUE0028 | Invalid combination of x and y axes; at least one of the axes must have a numeric attribute for the graph to render properly. |
Explanation |
One of the attribute in the x or y axis should have a numeric value. |
Action |
Choose a numeric attribute in one of the two axes. |
INMBUE0029 | Invalid search for charts; you must choose at least one numeric attribute. |
Explanation |
The chosen search does not have a numeric attribute to plot the chart. To plot a chart you must have a combination of non-numeric attribute and numeric attribute. |
Action |
Choose a search with at least one numeric attribute. |
INMBUE0030 | Organization name is empty |
Explanation |
The organization name field is empty, but the organization name must be provided when creating an organization. |
Action |
Enter the organization name. |
INMBUE0031 | Role name is empty |
Explanation |
The role name field is empty, but the role name must be provided when creating a role. |
Action |
Enter a role name. |
INMBUE0032 | Enter a valid consumer application name. |
Explanation |
The consumer application name specified is either invalid or empty. |
Action |
Enter a valid consumer application name. |
INMBUE0035 | Base URL should not be empty. |
Explanation |
The Base URL is empty. |
Action |
Enter the Base URL. |
INMBUE0036 | Add at least one method to the resource. |
Explanation |
A resource should have at least one HTTP method to perform a certain operation. This error occurs when an attempt is made to add a resource in the API without specifying at least one method. |
Action |
Add at least one HTTP method for the resource. |
INMBUE0037 | Parameter name must not be empty. |
Explanation |
The parameter name is empty. |
Action |
Enter the parameter name. |
INMBUE0038 | Method name must not be empty. |
Explanation |
The method name is empty. |
Action |
Enter the method name. |
INMBUE0039 | Resource name must not be empty. |
Explanation |
The resource name is empty. |
Action |
Enter the resource name. |
INMBUE0040 | Resource path must not be empty. |
Explanation |
The resource path is empty. |
Action |
Enter the resource path. |
INMBUE0041 | Default value should be a value in the possible values list. |
Explanation |
The default value does not match with any of the values in the list of possible values. |
Action |
Enter a value from the list of possible values. |
INMBUE0042 | The resource already exists. |
Explanation |
An attempt was made to add a resource with the same name as an existing resource in the same service. |
Action |
Enter a new resource name that is not already in use in the service. |
INMBUE0043 | Resource with path already exists in this API. |
Explanation |
An attempt was made to add a resource with the same path as an existing resource in the same API. |
Action |
Enter a new resource path which is not already in use in the API. |
INMBUE0044 | Parameter already exists for this parameter type. |
Explanation |
An attempt was made to add a parameter with the same name as an existing parameter for the given parameter type. |
Action |
Enter a new parameter name that is not already available for the parameter type. |
INMBUE0045 | Select at least one resource to virtualize. |
Explanation |
An attempt was made to virtualize a REST service without selecting the resource. |
Action |
Select at least one resource to virtualize the REST service. |
INMBUE0046 | Request message cannot be empty. |
Explanation |
You have not entered a request message when adding sample request and response to the REST service. |
Action |
Enter the sample request message. |
INMBUE0051 | API Portal Name field cannot be empty. |
Explanation |
You have not entered the name of API Portal when registering API Portal in CentraSite. |
Action |
Enter the API Portal name. |
INMBUE0052 | API Portal Alias field cannot be empty. |
Explanation |
You have not entered the name of API Portal alias when registering API Portal in CentraSite. |
Action |
Enter the API Portal alias name. |
INMBUE0053 | Deployment Endpoint field cannot be empty. |
Explanation |
You have not entered the deployment endpoint address when registering API Portal in CentraSite. |
Action |
Enter a valid deployment endpoint. |
INMBUE0054 | CentraSite Alias field cannot be empty. |
Explanation |
You have not entered the name of CentraSite alias when registering API Portal in CentraSite. |
Action |
Enter the CentraSite alias name. |
INMBUE0055 | Consumer Onboarding Organization field cannot be empty. |
Explanation |
You have not entered the name of the consumer onboarding organization when registering API Portal in CentraSite. |
Action |
Enter the consumer onboarding organization name. |
INMBUE0056 | The base URL already exists. |
Explanation |
An attempt was made to add a base URL with the same value as an existing base URL in the same service. |
Action |
Enter a new base URL value that is not already in use in the service. |
INMBUE0058 | Select at least one API Portal to publish. |
Explanation |
An attempt was made to publish the API without selecting at least one API Portal. |
Action |
Select at least one API Portal to publish the API. |
INMBUE0059 | Username field cannot be empty. |
Explanation |
You have not entered the CentraSite username when registering API Portal in CentraSite. |
Action |
Enter a valid CentraSite username. |
INMBUE0060 | Password field cannot be empty. |
Explanation |
You have not entered the CentraSite password when registering API Portal in CentraSite. |
Action |
Enter a valid CentraSite password. |
INMBUE0062 | Gateway URL is not valid. Specify a valid URL, and try again. |
Explanation |
The gateway URL is not valid, or not in the correct format. |
Action |
Specify a valid gateway URL, and try again. |
INMBUE0063 | Invalid value |
Explanation |
Value entered is not valid. |
Action |
Enter a valid value and try again. |
INMBUE0065 | Maximum payload size cannot take the value "0". |
Explanation |
You have specifed the value "0" for the maximum payload size parameter. |
Action |
Specify "-1" for unlimited size or an integer value greater than "0" for the maximum payload size, and try again. |
INMBUE0066 | Select at least one request content type. |
Explanation |
A request content type is required if you have added either a schema or an example content for request. |
Action |
Add at least one content type for request. |
INMBUE0067 | Select at least one response content type. |
Explanation |
A respons content type is required if you have added either a schema or an example content for response. |
Action |
Add at least one content type for response. |
INMBUE0068 | The request(s) of this method do not consume the content type(s) {0}. |
Explanation |
There is a mismatch between the method's request Content-Types and the Content-Type set for the request. |
Action |
Provide the correct method content type that matches the request content type. |
INMBUE0069 | The response(s) of this method do not consume the content type(s) {0}. |
Explanation |
There is a mismatch between the method's response Content-Types and the Content-Type set for the Response. |
Action |
Provide the correct method content type that matches the response content type. |
INMBUE0074 | The error status code is not valid. |
Explanation |
You have entered an incorrect error status code. |
Action |
Enter an error status code between 400 to 500. |
INMBUE0076 | Message Subject field cannot be empty. |
Explanation |
You have not entered the subject line of the email which is used for the consumer notifications. |
Action |
Enter the subject line of the email in the Message Subject field. |
INMBUE0077 | Message Body field cannot be empty. |
Explanation |
You have not entered the message content of the email which is used for the consumer notifications. |
Action |
Enter the message content of the email in the Message Body field. |
INMBUE0078 | Required alias '${sys:dyn-Endpoint}' is missing in the Route Through field. |
Explanation |
You have not specified the alias '${sys:dyn-Endpoint}' in the Route Through field. |
Action |
Make sure the alias '${sys:dyn-Endpoint}' is specified in the Route Through field. |
INMBUE0079 | Taxonomy name cannot be empty. |
Explanation |
You have not provided a name for the taxonomy. |
Action |
Provide a name for the taxonomy. |
INMBUE0080 | Asset type name cannot be empty. |
Explanation |
You have not provided a name for the asset type. |
Action |
Provide a name for the asset type. |
INMBUE0081 | Invalid profile name. |
Explanation |
The entered value for profile name is not valid. |
Action |
Enter a valid profile name. |
INMBUE0082 | Invalid attribute name. |
Explanation |
The entered value for attribute name is not valid. |
Action |
Enter a valid attribute name. |
INMBUE0083 | Lifecycle stage name cannot be empty. |
Explanation |
You have not entered a name for the lifecycle stage. |
Action |
Enter the lifecycle stage name. |
INMBUE0084 | Lifecycle stage endpoint cannot be empty. |
Explanation |
You have not entered an endpoint URL for the lifecycle stage. |
Action |
Enter a valid lifecycle stage endpoint. |
INMBUE0085 | Invalid lifecycle stage endpoint. |
Explanation |
The specified lifecycle stage URL is invalid. |
Action |
Specify a valid lifecycle stage endpoint and try again. If the problem persists, contact your administrator. |
INMBUE0086 | More than one default response exist. |
Explanation |
Only one default response can be added. This error occurs when an attempt is made to add a default response more than once for a method. |
Action |
Add only one default response for the method. |
INMBUE0087 | Server URL must not be empty. |
Explanation |
Enter the server URL. |
Action |
Enter the Server URL. |
INMBUE0088 | Callback name must not be empty. |
Explanation |
The callback name is empty. |
Action |
Enter the callback name. |
INMBUE0089 | Select at least one method |
Explanation |
Select at least one method |
Action |
Method selection is needed |
INMBUE0090 | Select at least one content type |
Explanation |
A respons content type is required if you have added either a schema or an example content for response or request. |
Action |
Add at least one content type for response or request |
INMBUE0091 | The default value should not be empty |
Explanation |
The default value should not empty if possible value is empty also |
Action |
The default value should empty |
INMBUI0005 | No document(s) available. |
Explanation |
Documents are not available to download. |
Action |
No action required. |
INMBUI0006 | Selected item(s) not applicable for Export |
Explanation |
The selected item(s) are not applicable for export. |
Action |
No action required. |
INMBUI0008 | No target found for deployment. |
Explanation |
No target found was for deployment |
Action |
Register a target for deployment before initiating the Publish action. |
INMBUI0010 | Error while instantiating the activity {0}. |
Explanation |
Could not instantiate the activity {0}. The failure is likely to be cause by incorrect configuration. |
Action |
Verify that the activity has been configured correctly. |
INMBUI0027 | Unable to view the profile information. |
Explanation |
You do not have sufficient access right to view the profile information. |
Action |
Verify that you have the appropriate access rights. Contact your administrator and request access if necessary and then try again. |
INMBUI0033 | Enter the base URL for API requests. |
Explanation |
Base URL is mandatory for making requests to the API. |
Action |
Enter the base URL for API requests. |
INMBUI0034 | Enter a namespace. |
Explanation |
A namespace should be specified for the API. |
Action |
Enter a valid namespace. |
INMBUI0057 | Select a sandbox for base URL. |
Explanation |
No sandbox has been selected for the base URL. A base URL is classified with a sandbox environment such as a Development, Production or Test to indicate the usage. |
Action |
Select a sandbox for the base URL. |
INMBUI0075 | Enter the Endpoint Prefix for the API. |
Explanation |
Endpoint Prefix is optional for Virtual API. |
Action |
Enter the Endpoint Prefix for the API. |
INMBUW0001 | Invalid search query. |
Explanation |
You have entered an invalid search query, possibly because the query is not available in the CentraSite repository. |
Action |
The search query {0} is not available. Configure your portlet with a valid search query. |
INMBUW0047 | Specified value is a duplicate value. Specify a valid unique value. |
Explanation |
An alias value is already defined for this target. |
Action |
Specify a valid unique value. |
INMBUW0048 | A value is already specified for the target. Select a different gateway. |
Explanation |
This is an alias value already defined for this target. |
Action |
Select a different gateway. |
INMBUW0049 | Provide an alias value. |
Explanation |
You have to provide an alias value. |
Action |
No action required. |
INMBUW0050 | Specify a value for this target, else delete the row. |
Explanation |
You must specify a value for this target. |
Action |
Specify target specific alias value or else delete the entire row. |
INMBUW0061 | To add multiple resources, you must manually reconfigure the Route to endpoint field. To reconfigure the Route to endpoint, append the resource path tokenizer ${sys:resource_path} with the base URL of the native API in the format <base-url>/${sys:resource_path}. For more information about handling multiple resources, see the documentation Run-Time Goveranance with CentraSite. |
Explanation |
To add multiple resources, you must manually reconfigure the Route to endpoint field. To reconfigure the Route to endpoint, append the resource path tokenizer ${sys:resource_path} with the base URL of the native API in the format <base-url>/${sys:resource_path}. For more information about handling multiple resources, see the documentation Run-Time Goveranance with CentraSite. |
Action |
To add multiple resources, you must manually reconfigure the Route to endpoint field. To reconfigure the Route to endpoint, append the resource path tokenizer ${sys:resource_path} with the base URL of the native API in the format <base-url>/${sys:resource_path}. For more information about handling multiple resources, see the documentation Run-Time Goveranance with CentraSite. |
INMBU_ERR_EMPTY_ERROR_TEMPLATE | Select an error template in the Use as Default option. |
Explanation |
You have not specified an error template to use as the default in the Use as Default option. |
Action |
Configure a default error template for the error condition and try again. |
INMBU_ERR_SAME_TYPE_MULTIPLE_SELECTION | Multiple error templates are not permitted for same content type. |
Explanation |
You have selected more than one error template for the same content type. |
Action |
Remove duplicate error templates with same content type and try again. |
INMBU_LBL_API_UNPUBLISH_WARNING | If you unpublish an API from API Portal, the API keys associated with the API will be lost. |
INMBU_LBL_USER_BEEPER_PHONE | Beeper |
INMBU_LBL_USER_DOMAIN_NAME | Display Name |
INMBXE0003 | Enter a valid username or passsword. |
Explanation |
You have entered an invalid username or password. To log in to CentraSite, you must enter a valid username and password. |
Action |
Enter a valid username or password. |
INMBXE0004 | Enter your username (full email address). |
Explanation |
You have entered an invalid username. To log in to CentraSite, you must enter your email address as username. |
Action |
Enter a valid username. |
INMBXE0005 | Enter a valid email address (e.g. example@example) |
Explanation |
You have entered a wrong or blank email address. You must enter a valid email address (e.g. example@example). |
Action |
Enter a valid email address (e.g. example@example). |
INMBXE0009 | Enter your password. |
Explanation |
To request an account in CentraSite, you must enter a password. |
Action |
Enter a valid password. |
INMBXE0010 | Enter your first name. Example: John. |
Explanation |
To request an account in CentraSite, you must enter your first name. |
Action |
Enter your first name. |
INMBXE0011 | Enter your last name. Example: Smith. |
Explanation |
To request an account in CentraSite, you must enter your last name. |
Action |
Enter your last name. |
INMBXE0012 | Enter a reason for requesting access to CentraSite. |
Explanation |
To register an account in CentraSite, you must provide a valid reason for requesting the account to CentraSite. |
Action |
Enter a valid reason for requesting access to CentraSite. |
INMBXE0016 | Password does not match |
Explanation |
The password for Confirm Password does not match the given password. |
Action |
Confirm the given password by entering the same password again. |
INMBXE0017 | Access is denied. |
Explanation |
Could not log in to the CentraSite Business UI as a guest user, probably because the guest access is disabled. |
Action |
Verify the centrasite.xml file. Make sure that the property element "Guest visiblity" is set to "true". For more information about the usage of "Guest visiblity" property, see the CentraSite Administrator's Guide. If the property is already set to "true" and the error persists, contact your administrator. |
INMBXI0001 | CentraSite gives your organization a single place to store, find and reuse service and process assets. That speeds up development. Automatic policy enforcement helps you ensure new services and processes perform consistently and to the quality standards you've set. |
Explanation |
This message provides an introduction to CentraSite in the login page. |
Action |
Get an overview of the product. |
INMBXI0002 | Log in to Your Account |
Explanation |
Enter the user account credentials to log in to CentraSite. |
Action |
Log in to CentraSite. |
INMBXI0006 | Create Your Account |
Explanation |
Request for an account in CentraSite. |
Action |
Enter the user credentials and create an account in CentraSite. |
INMBXI0008 | Thank you for your registration in CentraSite. |
Explanation |
Thank you for your registration. We will contact you soon and inform you of the next steps. In the meantime you may visit CentraSite as a guest. |
Action |
Log in to CentraSite as a guest. |
INMBXI0013 | You will be contacted by a CentraSite administrator. |
Explanation |
The CentraSite administrator will process your registration request and contact you shortly. |
Action |
The CentraSite Administrator will process your request and contact you shortly. |
INMBXI0014 | Access CentraSite as a guest. |
Explanation |
You may access CentraSite as a guest. |
Action |
Access CentraSite as a guest. |
INMBXW0015 | JavaScript is not enabled in your web browser. |
Explanation |
If JavaScript is already installed but the application does not work, you may need to enable JavaScript in your web browser. |
Action |
Enable the JavaScript in your web browser. |
INMBX_LBL_ERROR_PAGE | Enable your CentraSite license |
Explanation |
Members of the CentraSite Community Edition (CE) are not allowed to use the CentraSite Business UI. This is because the Community Edition is a free-of-charge version of CentraSite that does not include a CentraSite license. In order to use the CentraSite Business UI, you must have the CentraSite license installed. |
Action |
Install the CentraSite license. For further information contact your software supplier. |
INMBX_LBL_IE8_COMPATIBILITY_TEXT | CentraSite Business UI is not designed to run in compatibility mode. Disable the compatibility mode to render the Business UI. |
Explanation |
CentraSite Business UI is not designed to run in compatibility mode. |
Action |
Disable the compatibility mode to render the Business UI. |
INMBX_LIC_ACCESS_ERROR | Error accessing license information. Check the error log for more information. |
Explanation |
Error encountered while accessing the CentraSite license information. |
Action |
If this error persists, contact your administrator. |
INMCBE0009 | You do not have sufficient access rights to modify this object. |
Explanation |
You do not have sufficient access rights to modify this object. |
Action |
Verify that you have the appropriate access rights. Contact your administrator and request access if necessary and then try again. |
INMCBE0012 | Invalid password specified. |
Explanation |
You have specified an invalid password. |
Action |
Correct password and try again. |
INMCBE0013 | HTTP response {0} received while updating password. |
Explanation |
While updating the password, the user received an http error with the given error code. |
Action |
Analyse the reason for this error based on the http error code. |
INMCBE0014 | Error occurred when reading configuration file at {0}. |
Explanation |
An error occurred when reading the user-specific configuration file at the given location. |
Action |
Refer to the stack trace - you may need to delete the given file from the repository. |
INMCBE0015 | You have entered no file or folder name. |
Explanation |
You have entered no file or folder name. |
Action |
Enter a name. |
INMCBE0016 | The name you have entered is invalid. Web Folder names cannot include any of the following characters: :*?<>|\/" |
Explanation |
The name you have entered is invalid. Web folder names cannot include any of the following characters: :*?<>|\/" |
Action |
Specify another name. |
INMCBE0017 | The name you have entered exceeds the maximum allowed name length. |
Explanation |
The name you have entered exceeds the maximum allowed name length. |
Action |
Specify a shorter name. |
INMCBE0018 | No report definition is linked to given report object |
Explanation |
The report must have an external link referencing the report definition created via BIRT. |
Action |
Repeat the import of the report either via the "Import Report" command in the user interface or via the "Export to CentraSite" command in the BIRT plugin of Eclipse. |
INMCBE0020 | Failed to obtain value of parameter {0} |
Explanation |
Could not determine value for the parameter with given name. |
Action |
Contact your software supplier. |
INMCBE0021 | The domain of the specified user is invalid. |
Explanation |
The domain of the specified user is invalid. For non-windows platforms, only the domain LOCAL or LDAP is allowed. |
Action |
Enter a valid domain. For non-Windows platforms, only the domain LOCAL or LDAP is allowed. |
INMCBE0022 | Object no longer available |
Explanation |
The selected object does not exist, possibly because it has been implicitly discarded before or an import has failed. |
Action |
Check recent activities. |
INMCBE0024 | The passwords you typed do not match. |
Explanation |
The passwords you typed do not match. |
Action |
Enter the new password in both text boxes. |
INMCBE0027 | The specified user does not exist. |
Explanation |
The specified user is not present in CentraSite. |
Action |
Specify a valid user. |
INMCBE0029 | Error occurred when initializing CentraSite Control - disabling plug-in. |
Explanation |
An error occurred when initializing CentraSite Control. |
Action |
Check details of error message for further information. |
INMCBE0030 | Invalid change of data type for existing data. |
Explanation |
An attempt is being made to change the data type of a property that already has data present that is not of the type specified. |
Action |
Select a data type that matches the existing data. |
INMCBE0032 | Asset name must not be empty. |
Explanation |
No name is specified for the asset. |
Action |
Enter a valid asset name. |
INMCBE0033 | Asset type not valid. |
Explanation |
The selected asset type is not valid for this operation. |
Action |
Select a valid asset type. |
INMCBE0035 | The associated object of type Associated with could not be deleted |
Explanation |
User does not have permission to delete the associated object |
Action |
Grant delete permission to the user for the associated object |
INMCBE0036 | The associated object of type WS-Policy attachment could not be deleted |
Explanation |
The user does not have permission to delete the WS-Policy associated with the virtual service. |
Action |
Verify that you have the appropriate access rights. Contact your administrator and request access if necessary and then try again. |
INMCBE0037 | The associated object of type External Link could not be deleted |
Explanation |
The user does not have permission to delete associated external links. |
Action |
Verify that you have the appropriate access rights. Contact your administrator and request access if necessary and then try again. |
INMCBE0038 | Asset with name {0} already exists of type {1} |
Explanation |
There is a duplicate asset name. |
Action |
Enter another name for the asset. |
INMCBI0001 | New ExternalLink has been copied to the internal clipboard. It can be added to arbitrary registry objects now. |
Explanation |
The newly created ExternalLink object has been copied to the internal clipboard. It can be used to add the ExternalLink to any registry object via the tab "External Links". |
Action |
No action required. |
INMCBW0002 | Resource cannot be deleted as it is the target of one or more ExternalLink objects. |
Explanation |
You cannot delete this resource as it is referenced by one or more external links. |
Action |
You may run the impact analysis in order to determine the registry objects that have an external link referencing this resource. |
INMCBW0003 | Folder cannot be deleted as it is the target of one or more ExternalLink objects. |
Explanation |
You cannot delete this folder as it is referenced by one or more External Links. |
Action |
You may run the impact analysis in order to determine the registry objects that have an external link depending on this folder. |
INMCBW0004 | Resource cannot be renamed as it is the target of one or more ExternalLink objects. |
Explanation |
You cannot rename this resource as it is referenced by one or more registry objects. |
Action |
You may run the impact analysis in order to determine the registry objects that have an external link depending on this resource. |
INMCBW0007 | No report is linked to type {0}. |
Explanation |
No report has been associated to the type via the 'Link Reports' command. |
Action |
You can associate a report via the command 'Link Reports' for the respective type. |
INMCBW0010 | No operation is defined for type {0}. |
Explanation |
The definition of the respective type does not contain any operations. |
Action |
You can add operations via the 'Modify Type' command for the respective type. |
INMCBW0011 | You are connected as a read-only user. This will lead to limited functionality being available. |
Explanation |
A read-only user does not have privileges to modify registry objects. |
Action |
Log in as another user if you want to modify registry objects. |
INMCBW0019 | No items have been exported |
Explanation |
No items have been exported - this may happen if items selected for export are embedded into other objects and thus cannot be exported without their parent objects. |
Action |
Select the parent object for export. |
INMCBW0031 | File cannot be deleted as it is the target of one or more Favorite objects of My CentraSite. |
Explanation |
You cannot delete this file as it is referenced by one or more External Links in My CentraSite. |
Action |
You may run the impact analysis in order to determine the Favorite Object in My CentraSite that has an external link referencing this resource. |
INMCCE0001 | Command {0} is not supported by CentraSite command line tool |
Explanation |
The specified command cannot be executed by the CentraSite command line tool. It is not in the list of supported commands. |
Action |
Please check the usage of CentraSiteCommand and make sure you specify the command which is listed in the usage. |
INMCCE0002 | Exception while fetching email properties |
Explanation |
CentraSiteCommand is not able to fetch the email properties from CentraSite. |
Action |
Please make sure all the parameters are valid and re-execute the command. |
INMCCE0003 | Exception while storing email properties |
Explanation |
CentraSiteCommand is not able to store the email properties into CentraSite. |
Action |
Please make sure all the parameters are valid and re-execute the command. |
INMCCE0006 | Parsing failed! Please make sure configuration file syntax and path are correct. |
Explanation |
Parsing the CentraSiteCommand option and/or configFile failed. |
Action |
Please make sure the CentraSiteCommand options are specified properly and configFile exists in the specified location. |
INMCCE0007 | Parsing failed! Please make sure configuration file syntax and path are correct. |
Explanation |
This error can occur because of two reasons. 1) The syntax of the configuration file is not valid. 2) The specified configuration file path is incorrect. |
Action |
Please refer to the documentation for information on creating a valid configuration file. |
INMCCE0008 | Failed to execute command {0} |
Explanation |
Error occurred while executing the command. |
Action |
Please check the error message for details. |
INMCCE0009 | Internal error occurred |
Explanation |
This error may occur because of problems in the system execution. |
Action |
Please contact the administrator. |
INMCCE0010 | {0} is an invalid log unit, possible values are {1} |
Explanation |
The provided log unit is invalid. This can occur when the user specifies a log unit other than the supported ones. |
Action |
Please refer to the error message for the possible values. |
INMCCE0011 | {0} is invalid log unit value, possible values are {1} |
Explanation |
The provided log unit value is invalid. This can occur when the user specifies a log unit value other than the supported ones. |
Action |
Please refer to the error message for the possible values. |
INMCCE0012 | Purger unavailable for {0} |
Explanation |
No purger was found for the given log unit. This error can occur if an appropriate purger is not found/available for the given log unit. |
Action |
Please ensure the correct log units are provided in the configuration file. |
INMCCE0013 | Purging stopped for {0} as there is no write permission for export location {1} |
Explanation |
This error will occur when the user does not have the required write permission for the export location. |
Action |
Please provide required permissions before purging. |
INMCCE0014 | Insufficient disk space in {0}. Required space {1}. Available space {2}. |
Explanation |
The specified export location does not contain enough space for the exported logs. Please refer to the error message for the available and required space. |
Action |
Please choose a different export location. |
INMCCE0015 | Purging Failed. Following error occurred {0}. |
Explanation |
Purging failed for the log unit mentioned in the error message. Some failures may happen because of network time out and similar problems. |
Action |
Please try again later or contact the administrator for assistance. |
INMCCE0016 | Unable to archive the export directory {0} |
Explanation |
The archiving of the exported logs failed. This may happen because of files being accessed by an other application. |
Action |
Please close the other application and try again. |
INMCCE0017 | Unable to create the export directory {0} |
Explanation |
This error can occur when the user does not have the required write permission for the export location or the export location is invalid. |
Action |
Please provide required permissions before purging or make sure the export location is valid. |
INMCCE0018 | Command {0} is not supported by CentraSite command line tool |
Explanation |
The displayed command is invalid. This can occur when the user specifies a command other than the supported ones. For example, to purge logs, you should specify -command purge_logs. |
Action |
Please refer to the documentation for the list of supported commands and their usage. |
INMCCE0019 | castUri option is mandatory for the command {1} |
Explanation |
The castUri option is required for the specified commands. |
Action |
Please specify the cast URI in the -castUri option. |
INMCCE0020 | CentraSite Application Server Object (CAST) already registered in CentraSite with the specified castUri {0} |
Explanation |
The CAST will be identified using the host present in castUri option, and CentraSite already contains a CAST registered with the specified host. |
Action |
Specify a different value in the castUri option or de-register the existing CAST and register it again. A CAST can be de-registered using the deregister_cast command. |
INMCCE0021 | {0} and {1} both present in configuration for log unit {2} |
Explanation |
The tags Until and OlderThan are both present in the configuration file. |
Action |
Please use only one of the given tags in the configuration file. For more information, please refer to the Administration guide. |
INMCCE0022 | Unable to obtain policy query manager. Cause: {0} |
Explanation |
It was not possible to obtain the policy query manager. |
Action |
Verify your installation or contact the administrator. |
INMCCE0023 | Exception occurred during restore operation. Cause: {0}. |
Explanation |
An exception occurred during the restore operation. |
Action |
Please check the exception message for more details. |
INMCCE0024 | Archive seal error. Invalid start/end date entries in the archive seal properties for the Archive file {0} located in {1}. |
Explanation |
An archive seal error occurred. There are invalid start/end date entries in the archive seal properties. |
Action |
Please verify the seal properties file for correctness. |
INMCCE0025 | Error creating archive seal file. Cause {0}. |
Explanation |
An error occurred while creating the archive seal file. |
Action |
Please check the error message for more details. |
INMCCE0026 | Command option {0} missing |
Explanation |
The specified command requires a command option. |
Action |
See the usage information for the correct command syntax. |
INMCCE0028 | Domain {0} not found |
Explanation |
The domain to be processed does not exist. |
Action |
Correct the specified domain name. |
INMCCE0029 | Domain {0} already exist |
Explanation |
A domain entry with the specified name is already present. |
Action |
Correct the specified domain name. |
INMCCE0030 | Error processing configuration file: {0} |
Explanation |
The configuration file does not contain a valid domain entry. |
Action |
Correct the domain entry in the configuration file. |
INMCCE0031 | Error deleting domain entry: {0} |
Explanation |
The specified domain entry could not be deleted. |
Action |
Contact your support center. |
INMCCE0039 | {0} is not a LDAP domain |
Explanation |
The validate command is only supported for LDAP domains. |
Action |
Specify an LDAP domain for validating an authentication configuration. |
INMCCE0040 | LDAP basic configuration validation error |
Explanation |
The basic LDAP configuration is invalid. |
Action |
Check the basic settings for the specified domain. |
INMCCE0041 | LDAP user login validation error |
Explanation |
The user could not log on with supplied user name and password. |
Action |
Check if the user name and password were specified correctly. Check the settings for the specified domain. |
INMCCE0042 | LDAP user properties validation error |
Explanation |
The user properties configuration is invalid. |
Action |
Check the user properties settings for the specified domain. |
INMCCE0043 | LDAP group resolution validation error |
Explanation |
The group resolution configuration is invalid. |
Action |
Check the group resolution settings for the specified domain. |
INMCCE0046 | CS Admin user {0} not created |
Explanation |
An error occurred while attempting to create a user with the CentraSite Administrator role. |
Action |
See the additional information provided to find the reason. |
INMCCE0047 | CS Admin user {0} ({1}) not created |
Explanation |
An error occurred while attempting to create a user with the CentraSite Administrator role. |
Action |
See the additional information provided to find the reason. |
INMCCE0053 | {0} No Users found! |
Explanation |
Searched users are not found |
Action |
user has to retry the search |
INMCCE0054 | {0} No group properties found! |
Explanation |
The group properties entered for the configuration are not correct. |
Action |
Correct the group properties. |
INMCCE0055 | Can't get group properties. {0} |
Explanation |
{0} --> error message from the LDAP |
Action |
re-configuration needs to be done |
INMCCE0056 | cannot read user property {0} |
Explanation |
{0} --> user property configured |
Action |
Re-configure the user properities |
INMCCE0058 | cannot read user property {0} |
Explanation |
{0} --> user property |
Action |
Re-configure the property |
INMCCE0059 | {0} No user properties found! |
Explanation |
{0} --> status warning message |
Action |
Re-configure the user properties |
INMCCE0060 | Cannot contact the server. {0} |
Explanation |
An attempt to connect to the server failed with the error message {0}. |
Action |
Re-configure the server properties. |
INMCCE0066 | Unable to connect to socket! |
Explanation |
There was a problem while connecting to the socket. |
Action |
Re-configure the connection. |
INMCCE0067 | The old file is not deleted |
Explanation |
An SSX trace file already exists and should be deleted. |
Action |
The SSX trace file needs to be deleted manually. |
INMCCE0068 | Unable to listen to port |
Explanation |
It was not possible to connect to the given port. |
Action |
Re-configure the port. |
INMCCE0088 | Cannot write to log4j. |
Explanation |
A message could not be written to the log4j log file. |
Action |
Check your log4j configuration. |
INMCCE0089 | Cannot write in the {0} |
Explanation |
A message could not be written to the SSX trace file {0}. |
Action |
Chekc your trace file configuration. |
INMCCE0090 | cannot connect to database - possibly password wrong? |
Explanation |
An error was detected while trying to connect to the database. |
Action |
Check that you entered the correct pasword. |
INMCCE0091 | Database 'CentraSite' not running |
Explanation |
The database 'CentraSite' is not running. |
Action |
Start the CentraSite database. |
INMCCE0092 | {0} User authentication for "{0}" failed! |
Explanation |
{0} --> State error {1} --> user name |
Action |
Re-enter the user authentication |
INMCCE0093 | The user repository cannot be created with parameters: {0} |
Explanation |
The user repository cannot be created with the given parameters. |
Action |
Re-configure the repository. |
INMCCE0094 | {0} open SSXRepository - {1} |
Explanation |
The SSX repository is not connected. The state error is {0} and the error message is {1}. |
Action |
Re-configure the connection to the repository. |
INMCCE0096 | Can't get users {0} |
Explanation |
The user mapping does not match any entry on the LDAP server. |
Action |
Provide a user mapping that matches an entry in LDAP. |
INMCCE0100 | Can't get member of group {0} |
Explanation |
An incorrect group ID was specified. |
Action |
Provide a correct group ID. |
INMCCE0103 | Can't get groups for user {0} |
Explanation |
No groups were found for the given user. |
Action |
Provide a proper group resolution. |
INMCCE0105 | db 'CentraSite' not running |
Explanation |
The database "CentraSite" is not currently active. |
Action |
Restart the "CentraSite" database. |
INMCCE0111 | Failed to obtain the user {0} folder from CentraSite |
Explanation |
Could not obtain the folder for the user with given name. The username is used to store a search definition in CentraSite. |
Action |
Make sure the user is registered in CentraSite. |
INMCCE0112 | Search definition {0} already exists in CentraSite |
Explanation |
An attempt was made to overwrite the existing report search definition. |
Action |
Make sure that you publish a new module or pass the argument -overwrite option_value. |
INMCCE0113 | File {0} not found |
Explanation |
The file {0} was not found in the folder. |
Action |
Check the availability of the file in the specified path. |
INMCCE0114 | Retrieving the namespace from {0} failed because the namespace is null. |
Explanation |
Cannot retrieve the namespace in the search definition since the namespace is null. |
Action |
Make sure a valid namespace is declared in the search definition. |
INMCCE0115 | Namespace does not match with the module |
Explanation |
The specified namespace does not match with the new module and search definition. |
Action |
Make sure that the namespace matches with the new module and search definition. |
INMCCE0116 | Error loading the module |
Explanation |
Failed to load the new module into CentraSite. |
Action |
Make sure the module format is correct. |
INMCCE0117 | The namespace {0} is already used by a module in CentraSite |
Explanation |
The specified namespace {0} was already used by a module. The module namespace should be unique in CentraSite. |
Action |
Difine a new module namespace or use -overwrite TRUE to overwrite the existing module with this new namespace. |
INMCCE0118 | The user you specified does not exist |
Explanation |
The user you specified is not a known user. |
Action |
Specify the name of a known user. |
INMCCE0119 | The number of Arguments for the command SetAsymmetricBindingConfigurations is not sufficient |
Explanation |
The number of Arguments for the command SetAsymmetricBindingConfigurations is not sufficient |
Action |
Please provide proper number of Arguments |
INMCCE0120 | Additional arguments provided to the Command SetAsymmetricBindingConfiguration |
Explanation |
Additional arguments provided to the Command SetAsymmetricBindingConfiguration |
Action |
Please delete the unwanted arguments |
INMCCE0121 | Required parameters missing |
Explanation |
Alleat one of the parameters among InitiatorTokenInclusion,RecipientTokenInclusion,AlgorithmSuite and Layout required for the command. |
Action |
Please Add one of InitiatorTokenInclusion,RecipientTokenInclusion,AlgorithmSuite or Layout |
INMCCE0122 | Invalid values provided for InitiatorTokenInclusion |
Explanation |
InitiatorTokenInclusion value can only be one among Always,AlwaysToRecipient,AlwaysToInitiator,Once,Never |
Action |
Please provide one value among Always,AlwaysToRecipient,AlwaysToInitiator,Once,Never |
INMCCE0123 | Invalid values provided for RecipientTokenInclusion |
Explanation |
RecipientTokenInclusion value can be one among AlwaysToRecipient,Always,AlwaysToInitiator,Once,Never |
Action |
Please provide one among AlwaysToRecipient,Always,AlwaysToInitiator,Once,Never |
INMCCE0124 | Invalid values provided for AlgorithmSuite |
Explanation |
Invalid values provided for AlgorithmSuite |
Action |
Please provide a valid value |
INMCCE0125 | Invalid value provided for Layout |
Explanation |
Layout can have one value among Strict,Lax,LaxTsFirst,LaxTsLast |
Action |
Please provide one value among Strict,Lax,LaxTsFirst,LaxTsLast |
INMCCE0126 | Exception writing the values to the repository .Reason : {0} |
Explanation |
{0} |
Action |
{0} |
INMCCE0127 | Exception while reading from the repository .Reason : {0} |
Explanation |
{0} |
Action |
{0} |
INMCCE0129 | The target for federation cannot be configured in the file at {0} |
Explanation |
While trying to configure a target for federation, the file at location {0} will be modified to include the configuration. This error occurs if the "multicast" element cannot be found in the file. |
Action |
Check to ensure that the "multicast" element is available after "from" in the file {0}. |
INMCCE0130 | The mandatory parameter(s), {0} is/are not specified for the command |
Explanation |
The command requires some parameters for proper execution and they are not specified. Without these mandatory parameters, the execution cannot proceed. |
Action |
Provide the parameters needed for the command execution. If you don't know the command format, just provide the command name alone to get the usage for the command. |
INMCCE0131 | The provided configFile {0} is not configured with the {1} element. |
Explanation |
While parsing the XML configFile, {0}, the parser cannot obtain the {1} element which is needed for the command execution. |
Action |
Check the configFile {0} to see if the {1} element is configured. If it is not, provide the necessary details. |
INMCCE0132 | The given federation id {0} does not have any target associated with it. |
Explanation |
The provided ID {0} is not configured to have a federation target. |
Action |
Use show_uddi_federation to determine the list of configured federation targets and identifiers. |
INMCCE0139 | An Internal Error occurred |
Explanation |
An Internal Error occurred |
Action |
An Internal Error occurred |
INMCCE0140 | Invalid Credentials |
Explanation |
Invalid Credentials provided |
Action |
Please provide valid credentials |
INMCCE0141 | Provide details for any one of the following parameters: api, accessToken, apiPortal |
Class | E |
Explanation |
An error occurred while sending the access tokens using the send AccessTokens command because the details for more than one of the parameters was provided. |
Action |
Provide details for any one of the parameters. |
INMCCE0142 | Invalid Virtual Service name |
Explanation |
The specified virtual service name is invalid. |
Action |
Enter a valid virtual service name. |
INMCCE0144 | Invalid Target name |
Explanation |
The target is not created or is invalid for virtual services to be deployed, undeployed or redeployed. |
Action |
Please provide a valid target name. |
INMCCE0152 | Command execution failed. Parameter value cannot be null or empty. |
Explanation |
A command parameter value was not entered. |
Action |
Before you execute a command, make sure that you set a value for every parameter in the command. |
INMCCE0153 | Command execution failed. Description of the path already exists. |
Explanation |
Description of the command path already exists. |
Action |
Before you execute a command, make sure that you set a valid command path. |
INMCCE0154 | Command execution failed. Combination of the path already exists. |
Explanation |
Combination of the command path already exists. |
Action |
Before you execute a command, make sure that you set a valid command combination. |
INMCCE0155 | Command execution failed. The name for command token is not valid. |
Explanation |
You have entered an invalid name for the command token. |
Action |
Enter a valid name for the command token. |
INMCCE0156 | Command execution failed. The input for command token is not valid. |
Explanation |
You have entered invalid input for the command token. |
Action |
Enter a valid input for the command token. |
INMCCE0157 | Command execution failed. Path already exists for the tokens: {0} |
Explanation |
The path already exists for the command tokens: {0}. |
Action |
Before you execute a command, make sure that you set a valid path for the tokens. |
INMCCE0158 | Command execution failed. Parameter value cannot be null or empty. |
Explanation |
A command parameter value was not entered. |
Action |
Before you execute a command, make sure that you set a value for every parameter in the command. |
INMCCE0159 | Command execution failed. Token or parameter value cannot be null or empty. |
Explanation |
A command token or parameter value was not entered. |
Action |
Before you execute a command, make sure that you set a value for every token and parameter in the command. |
INMCCE0160 | Command execution failed. Combination of the command tokens {} already exists. |
Explanation |
An attempt was made to specify the same token that is already present in the command. |
Action |
Before you execute a command, make sure that you set a valid token in the command. |
INMCCE0161 | Parameter {0} should not empty. |
Explanation |
The '{0}' parameter is mandatory. |
Action |
Enter a value for the {0} parameter. |
INMCCE0162 | Check the length of the command help. |
Explanation |
The command help text you have entered does not meet the minimum requirement of {0} characters. |
Action |
Correct the help text appropriately. |
INMCCE0163 | Command execution failed. Unable to join null or empty strings, or a single string. |
Explanation |
The combination of a null and empty string, or a null and single string is not valid. |
Action |
Before you execute a command, make sure that you set valid combination of strings in the command. |
INMCCE0164 | Configuration property {0} cannot be empty. |
Explanation |
The configuration property '{0}' was not specified. |
Action |
Specify the property {0}. |
INMCCE0165 | Command execution failed. Invalid value {0} for configuration parameter {1}. |
Explanation |
The value {0} for configuration parameter {1} is not valid. |
Action |
Before you execute a command, make sure that you set a valid value for parameter {1} in the command. |
INMCCE0166 | Invalid input file. |
Explanation |
The specified input file is invalid, possibly because there are one or more elements which are not allowed for this command. |
Action |
Specify a valid input file and try again. If the problem persists, contact your administrator. |
INMCCE0170 | The default domain {0} cannot be deleted. |
Explanation |
The specified domain entry is the domain displayed by default and cannot be deleted. |
Action |
To delete the default domain first designate a different domain as the default domain. |
INMCCE0171 | The "set Log" command failed due to incorrect data. |
Explanation |
This is an internal error probably because the "set Log" command expects starting element {0} instead of {1}. |
Action |
Verify the config.xml contents. Make sure the configuration has starting element as <LogSettings>. For more information about the usage of "set Log" command, see the CentraSite Administrator's Guide. Contact your administrator if the problem persists. |
INMCCE0172 | The "set Log" command failed due to incorrect data. |
Explanation |
This is an internal error probably because the specified "set Log" command expects child element {0} instead of {1}. |
Action |
Verify the config.xml contents. Make sure the configuration has child element as <LogUnit>. For more information about the usage of "set Log" command, see the CentraSite Administrator's Guide. Contact your administrator if the problem persists. |
INMCCE0173 | The "set Log" command failed due to incorrect data. |
Explanation |
This is an internal error probably because the "set Log" command expects a <LogUnit> element {0} instead of {1}. |
Action |
Verify the config.xml contents. Make sure the configuration contain <LogUnit> element with attribute <name>. For more information about the usage of "set Log" command, see the CentraSite Administrator's Guide. Contact your administrator if the problem persists. |
INMCCE0174 | Upload failed! The file {0} has an invalid extension. |
Explanation |
An attempt was made to upload the specified file {0} with extension other than .xml. |
Action |
Upload a valid XML file. |
INMCCE0175 | Failed to obtain the Organization folder of the user {0} from CentraSite. |
Explanation |
Could not fetch the Organization folder of the specified user {0}, possibly because the user has been deleted from the CentraSite registry. |
Action |
Make sure the specified user exists in the CentraSite registry. If the user exists and the error persists, contact your administrator. |
INMCCE0178 | The set gateway command failed. {0} |
Explanation |
The gateway command has failed to create a new gateway or update the specified gateway. You might not have the necessary permissions to create/update a gateway in CentraSite or CentraSite might be down. |
Action |
Ensure that you have the necessary permissions in CentraSite and that CentraSite is up and running. Also, provide all the mandatory parameters when you run the command to create/update a gateway. |
INMCCE0180 | Gateway deletion failed. {0} |
Explanation |
The gateway command has failed to delete the specified gateway. You might not have the necessary permissions to delete a gateway in CentraSite or CentraSite might be down. |
Action |
Ensure that you have the necessary permissions in CentraSite and that CentraSite is up and running. Also, ensure that you have provided the correct gateway name or ID. |
INMCCE0181 | The list gateways command failed. {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0183 | Unable to find a gateway in CentraSite with the name or key "{0}". |
Explanation |
You have provided a gateway name or key that does not exist in CentraSite. The delete gateway command failed to delete the specified gateway. |
Action |
Ensure that the gateway name or ID that you specify is correct and exists in CentraSite. |
INMCCE0184 | Unable to find an organization in CentraSite with the specified name or key "{0}". |
Explanation |
You have provided an organization name or key that does not exist in CentraSite. The set gateway command failed to create a new gateway. |
Action |
Ensure that the organization name or key that you specify is correct and exists in CentraSite. |
INMCCE0185 | Unable to find a sandbox in CentraSite with the specified name or key "{0}". |
Explanation |
You have provided a name or key of a sandbox category that does not exist in CentraSite. The set gateway command failed to create a new gateway. |
Action |
Ensure that the sandbox category with the specified name or key exists in CentraSite. |
INMCCE0186 | Report with that name doesn't exist or name is not unique. |
Explanation |
Either the name is misspelled or multiple reports with that name exist. |
Action |
Check the report name and provide a valid report name. |
INMCCE0187 | Sharing of report failed. |
Explanation |
Sharing of report failed possibly due to an internal error. |
Action |
Contact your local support. |
INMCCE0189 | Error occurred while publishing API Key {0} to API Portal {1}. |
Class | E |
Explanation |
An error occurred while trying to publish API Key {0} to API Portal {1}. |
Action |
Ensure that the API Portal server is up and running. If the problem persists, contact your administrator. |
INMCCE0191 | Error occurred while publishing OAuth token {0} to API Portal {1}. |
Class | E |
Explanation |
An error occurred while trying to publish OAuth token {0} to API Portal {1}. |
Action |
Ensure that the API Portal server is up and running. If the problem persists, contact your administrator. |
INMCCE0197 | "{0}" is not a valid value for "{1}". |
Explanation |
You have provided a value which is not part of the specified list. |
Action |
Ensure that the provided value is part of the specified list. |
INMCCE0198 | Report with name "{0}" was not found. |
Explanation |
You have provided a report name that does not exists in CentraSite. |
Action |
Ensure that the report name that you specified is correct and exists in CentraSite. |
INMCCE0199 | More than one reports with the name "{0}" found. |
Explanation |
You have provided a report name which is not unique in CentraSite. |
Action |
If the report name is not unique in CentraSite specify the report id. |
INMCCE0200 | Unable to add a new Report to CentraSite. |
Explanation |
An error occurred during the "add report" operation. |
Action |
A new report could not be created. For more information check the CentraSiteCommand log. |
INMCCE0201 | Unable to delete the report with the id "{0}". |
Explanation |
An error occurred during the "delete report" operation. |
Action |
Ensure that the report id is correct and exists in CentraSite. For more information check the CentraSiteCommand log. |
INMCCE0202 | Unable to access the specified Report Template file. |
Explanation |
You have provided a path to a report template file which does not exist. |
Action |
Ensure that the specified report template file exists. |
INMCCE0203 | Unable to update the report with id "{0}". |
Explanation |
An error occurred during the "update report" operation. |
Action |
Ensure that the report id is correct and exists in CentraSite. For more information please check the CentraSiteCommand log. |
INMCCE0204 | Scheduled report with name "{0}" was not found. |
Explanation |
You have provided a scheduled report name that does not exist in CentraSite. |
Action |
Ensure that the scheduled report name that you specified is correct and exists in CentraSite. |
INMCCE0205 | More than one scheduled report with the name "{0}" found. |
Explanation |
You have provided a scheduled report name which is not unique in CentraSite. |
Action |
If the scheduled report name is not unique in CentraSite the scheduled report id has to be specified. |
INMCCE0206 | Unable to add a new scheduled report to CentraSite. |
Explanation |
An error occurred during the "add scheduled report" operation. |
Action |
A new scheduled report could not be created. For more information check the CentraSiteCommand log. |
INMCCE0207 | Unable to delete the scheduled report with the id "{0}" |
Explanation |
An error occurred during the "delete scheduled report" operation. |
Action |
Ensure that the scheduled report id is correct and exists in CentraSite. For more information please check the CentraSiteCommand log. |
INMCCE0208 | Unable to trigger the execution of the scheduled report with the id "{0}". |
Explanation |
An error occurred during the "trigger scheduled report" operation. |
Action |
Ensure that the scheduled report id is correct and exists in CentraSite. For more information check the CentraSiteCommand log. |
INMCCE0209 | Unable to update the scheduled report with the id "{0}". |
Explanation |
An error occurred during the "update scheduled report" operation. |
Action |
Ensure that the scheduled report id is correct and exists in CentraSite. For more information check the CentraSiteCommand log. |
INMCCE0210 | The property "{0}" is mandatory. |
Explanation |
You have provided a configuration file where the property is missing. |
Action |
Ensure that the property is set in the configuration file. |
INMCCE0211 | Unable to download the report template for the report id "{0}". |
Explanation |
An error occurred during the "download report template" operation. |
Action |
Ensure that the report id is correct and exists in CentraSite. For more information check the CentraSiteCommand log. |
INMCCE0215 | File {0} already exists. |
Explanation |
The specified file already exists. |
Action |
Provide the correct file name. |
INMCCE0217 | User level scope is not allowed. |
Explanation |
You have provided the scope as user level. |
Action |
Change the scope either to global or org. |
INMCCE0218 | Provide details for any one of the following parameters: scope, targetUser |
Explanation |
An error occurred while copying the saved search because details for more than one of the parameters was provided. |
Action |
Provide details for any one of the parameters. |
INMCCE0219 | Cannot find saved search with name {0}. |
Explanation |
Cannot find saved search with name {0} while performing copy saved search operation. |
Action |
Make sure the saved search with name {0} is present. |
INMCCE0220 | Specify a value for scope or targetUser. |
Explanation |
You have not provided a value for both scope and targetUser. |
Action |
Enter a valid value for scope or targetUser. |
INMCCE0222 | Insufficient privilege for user "{0}" to execute copy search command. |
Explanation |
To execute copy search the user should be either an CentraSite Administrator or an Organization Administrator. |
Action |
Please make sure you have sufficient privileges. |
INMCCE0224 | Insufficient privilege for user "{0}" to execute add search command in organization scope. |
Explanation |
To execute add search in organization scope the user should be either an CentraSite Administrator or an Organization Administrator. |
Action |
Please make sure you have sufficient privileges. |
INMCCE0225 | LDAP server {0} is not known. |
Explanation |
The specified LDAP server {0} is not known, probably because the IP address or the host name of the LDAP server could not be determined. |
Action |
Enter a valid IP address, or the fully qualified host name of the LDAP server. |
INMCCE0226 | LDAP server {0} is not reachable. |
Explanation |
The specified LDAP server {0} is not reachable. |
Action |
Make sure that the LDAP server is reachable. |
INMCCE0227 | Authentication failed {0}. |
Explanation |
An error occurred while trying to access the LDAP server, possibly because of invalid credentials. |
Action |
Make sure the credentials for accessing the LDAP server are valid. |
INMCCE0231 | The temporary configuration file name {0} already exists. |
Explanation |
The name you are giving the temporary configuration file already exists for another file in CentraSite. |
Action |
Enter a configuration file name that does not already exist in CentraSite. |
INMCCE0234 | Invalid object class. |
Explanation |
The specified object class for users or groups does not exist in the LDAP server. |
Action |
Make sure the specified object class name exists in the LDAP server. |
INMCCE0235 | Invalid root DN. |
Explanation |
The specified root DN (distinguished name) for user or group searches does not exist in the LDAP server. |
Action |
Make sure the specified root DN exists in the LDAP server. |
INMCCE0238 | Invalid attribute name. |
Explanation |
The specified attribute name does not exist in the LDAP server. |
Action |
Make sure the specified attribute name exists in the LDAP server. |
INMCCE0259 | Dynamic configuration property files of domain {0} are not unique. |
Explanation |
The dynamic configuration property files of the specified domain {0} are not unique. The dynamic configuration files include the property files for the domain, and the property files for the alias declaration. |
Action |
Remove either the property files for the domain, or the property files for the alias declaration. |
INMCCE0260 | The Truststore Type and Truststore URL fields or the Keystore Type and Keystore URL fields cannot be empty. |
Explanation |
You have not entered values for the required Truststore Type and Truststore URL fields, or the Keystore Type and Keystore URL fields, when using LDAP over SSL (LDAPS). |
Action |
Enter valid values for either the Truststore Type and Truststore URL fields, or the Keystore Type and Keystore URL fields. |
INMCCE0261 | Malformed URL. |
Explanation |
Either no legal protocol could be found in the URL string or the URL string could not be parsed. |
Action |
Enter a valid URL. |
INMCCE0262 | URL is not accessible. |
Explanation |
An exception occurred when trying to connect to the specified URL. |
Action |
Check that the URL is correct. |
INMCCE0266 | Target user {0} does not exist in the CentraSite registry. |
Explanation |
Could not find the specified target user {0}, possibly because the user has been deleted from the CentraSite registry. |
Action |
Make sure the specified target user exists in the CentraSite registry. If the target user exists and the error persists, contact your administrator. If the target user does not exist, enter a valid CentraSite username. |
INMCCE0267 | Incorrect date format {0}. |
Explanation |
The specified date format is incorrect. |
Action |
Specify a valid date in the format yyyy-mm-dd. |
INMCCE0268 | The access key or token does not match the authentication option. |
Explanation |
The specified access key or token does not match the given authentication option. |
Action |
Specify the correct access key or token configured in the authentication option. |
INMCCE0269 | Incorrect value for year {0}. |
Explanation |
The specified value for year is incorrect. |
Action |
Specify a valid value for year in the format 'yyyy'. |
INMCCE0270 | Incorrect value for month {0}. |
Explanation |
The specified value for month is incorrect. |
Action |
Specify a valid value for month in the format 'mm'. |
INMCCE0271 | Incorrect value for date {0}. |
Explanation |
The specified value for date is incorrect. |
Action |
Specify a valid value for date in the format 'dd'. |
INMCCE0272 | Failed to purge access token {0}. |
Explanation |
Could not purge the specified access token using the CentraSite Command "purge accesstokens", possibly because of insufficient permissions or CentraSite database server is down. |
Action |
Make sure the CentraSite database server is up and running, and you have sufficient permissions to purge access tokens. |
INMCCE0273 | The specified key is not available in DB. |
Explanation |
The specified key is not available in DB . |
Action |
The specified key is not available in DB. |
INMCCE0274 | Type with the given name does not exist or is not unique in the CentraSite registry. |
Explanation |
Type with the given name does not exist or multiple type with the same name exist in the CentraSite registry. |
Action |
Provide a valid type name. |
INMCCE0276 | {0} is the current logged in user. |
Explanation |
An attempt was made to delete the logged in user. |
Action |
Ensure that the selected user for deletion is not the current logged in user. |
INMCCE0277 | {0} is the primary contact of {1}. |
Explanation |
The logged in user tried to delete the primary contact of an organization. |
Action |
Ensure that the selected user for deletion is not the primary contact of an organization. |
INMCCE0278 | {0} is the CentraSite Administrator. |
Explanation |
The logged in user tried to delete the user who is the CentraSite Administrator. |
Action |
Ensure that the selected user for deletion is not the CentraSite Administrator. |
INMCCE0279 | At least one {0} should be present. |
Explanation |
This is possible because there is only one user with the CentraSite Administrator or Organization Administrator role, and an attempt is made to delete this user. |
Action |
Make sure there is at least one CentraSite Administrator or Organization Administrator user at any time. |
INMCCE0280 | User {0} has pending approvals and cannot be deleted. |
Explanation |
The user selected for deletion has one or more pending approvals. |
Action |
Approve or reject the pending approvals for the selected user. |
INMCCE0281 | Provide details for any one of these parameters: forceDelete, targetUser |
Explanation |
An error occurred while deleting organization because details for more than one of these parameters were provided: forceDelete, targetUser. |
Action |
Provide details for any one of these parameters. |
INMCCE0282 | Could not delete the organization that has deployed service(s). |
Explanation |
Could not delete the organization, possibly because there is at least one service with key {0} deployed to a gateway. |
Action |
Undeploy the services before deleting the organization. |
INMCCE0284 | Insufficient permissions for user "{0}" to execute delete search command in organization scope. |
Explanation |
To execute delete search in organization scope the user should be either an CentraSite Administrator or an Organization Administrator. |
Action |
Make sure you have sufficient permissions to execute delete search command in organization scope. |
INMCCE0285 | Insufficient permissions for user "{0}" to execute delete search command in global scope. |
Explanation |
To execute delete search in global scope the user should be an CentraSite Administrator. |
Action |
Make sure you have sufficient permissions to execute delete search command in global scope. |
INMCCE0286 | The list Action Categories command failed: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0287 | Action category with the given name {0} already exists. |
Explanation |
Action category with the given name {0} already exists. |
Action |
Specify an unique ID (uuid) to rename the action category. |
INMCCE0289 | Invalid ID(uuid) {0}. |
Explanation |
Action category with the given ID(uuid) {0} does not exist. |
Action |
Provide valid UDDI key for the action category. |
INMCCE0292 | Action category named {0} is updated successfully, but could not update the category type. |
Explanation |
N/A |
Action |
N/A |
INMCCE0293 | The add Action Category command failed: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0294 | The delete Action Category command failed: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0295 | Action category deletion failed. The category includes at least one active policy action. \nPolicy Action details: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0297 | The list Action Categories command failed: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0303 | The add action template command failed. {0} |
Explanation |
Could not execute the add action template command. |
Action |
Check the CentraSite logs for the reason for the failure. Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0313 | The delete Action Category command failed: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0314 | The update action template command failed. {0} |
Explanation |
Could not execute the update action template command. |
Action |
Check the CentraSite logs for the reason for the failure. Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0315 | The download Action Template command failed: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0317 | The get action template command failed. {0} |
Explanation |
Could not execute the get action template command. |
Action |
Check the CentraSite logs for the reason for the failure. Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0319 | File path does not exist. |
Explanation |
Destination Directory does not exist. |
Action |
Create Directory and execute the command again |
INMCCE0321 | The setup Custom Action command failed: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0322 | The sync Ldap group command failed: {0} |
Explanation |
Check the CentraSite logs for the reason for the failure. |
Action |
Run the command again after you have identified and fixed the issue(s). Ensure that all the parameters are correct and valid before you run the command. If the issue persists, contact Software AG support. |
INMCCE0327 | Could not retrieve keystore aliases: {0}. |
Explanation |
An error occurred while trying to retrieve the keystore aliases, possibly becuase of an invalid keystore format. |
Action |
Contact your administrator. |
INMCCI0027 | Domain {0} not found |
Explanation |
The domain to be processed does not exist. |
Action |
Correct the specified domain name. |
INMCCI0032 | Domain {0} successfully added |
Explanation |
The domain entry of the authentication configuration was created. |
Action |
No action required. |
INMCCI0033 | Domain {0} successfully removed |
Explanation |
The domain entry of the authentication configuration was removed. |
Action |
No action required. |
INMCCI0034 | Validating LDAP domain {0} |
Explanation |
The validate command has started. |
Action |
No action required. |
INMCCI0035 | The LDAP server configuration has been successfully validated. |
Explanation |
The specified LDAP server configuration is valid. |
Action |
No action required. |
INMCCI0036 | LDAP user login validated successfully |
Explanation |
The user could log on with supplied user name and password. |
Action |
No action required. |
INMCCI0037 | LDAP user properties validated successfully |
Explanation |
The user properties configuration is valid. |
Action |
No action required. |
INMCCI0038 | LDAP group resolution validated successfully |
Explanation |
The group resolution settings are valid. |
Action |
No action required. |
INMCCI0044 | Creating CS Admin user {0} for domain {1} |
Explanation |
The processing for creating a user with the CentraSite Administrator role has started. |
Action |
No action required. |
INMCCI0045 | CS Admin user {0} created |
Explanation |
A user with the CentraSite Administrator role has been successfully created. |
Action |
No action required. |
INMCCI0048 | Do you want to see the LDAP search trace? {0}: |
Explanation |
This prompt asks you whether or not you want to see the LDAP search results. |
Action |
Type Y (for yes) or N (for no) as appropriate, then press Enter. The default is N. |
INMCCI0049 | User elements found: {0}. Do you want to see them? |
Explanation |
The LDAP search found the given number of users. |
Action |
Type Y to see the results, otherwise N. |
INMCCI0050 | Do you want to see all the users? (Y/N) [N]: |
Explanation |
This prompt asks you whether or not to display all of the users. |
Action |
Type Y (for yes) or N (for no) as appropriate, then press Enter. The default is N. |
INMCCI0051 | User with filter: {0} |
Explanation |
User search filter |
Action |
search filter needs to be entered |
INMCCI0052 | {0} The following group was found: |
Explanation |
{0} --> ok |
Action |
No action |
INMCCI0057 | Can't get user properties. {0} |
Explanation |
{0} --> error message |
Action |
re-configure the user properties |
INMCCI0061 | {0} User authenticated successfully |
Explanation |
The user authentication was successful. The returned status is {0}. |
Action |
No action required. |
INMCCI0062 | Trying to ping the server now... |
Explanation |
An attempt is being made to connect to the server. |
Action |
No action required. |
INMCCI0063 | Is the connection to the server protected with SSL? (Y/N) [N]: |
Explanation |
This prompt asks you whether or not the LDAP connection to the server is protected with SSL. |
Action |
Type Y (for yes) or N (for no) as appropriate, then press Enter. The default is N. |
INMCCI0064 | Do you want use LDAP Technical User? (Y/N) [N]: |
Explanation |
The prompt asks whether or not you wish to use the LDAP Technical User. |
Action |
Type Y (for yes) or N (for no) as required. The default is N. |
INMCCI0065 | Provide the LDAP Technical User credentials file: |
Explanation |
The credentials file of the the LDAP Technical User needs to be given as input. |
Action |
Specify the credentials file. |
INMCCI0069 | Direct binding using the constructed DN was successful. |
Explanation |
A direct binding using the constructed DN was successful. |
Action |
No action required. |
INMCCI0070 | Do you want use LDAP Technical User Key file? |
Explanation |
User key file needs to be given or not |
Action |
File path will be given as input |
INMCCI0071 | Trying to connect to LDAP at: {0}:{1} |
Explanation |
An attempt is being made to connect to LDAP at host {0} and port {1}. |
Action |
No action required. |
INMCCI0072 | To test the connection, please provide the credentials of a valid LDAP user. |
Explanation |
To test the connection, the credentials of a valid LDAP user are required. |
Action |
Provide the credentials of a valid LDAP user. |
INMCCI0074 | Do you want to save the configuration to CentraSite? (Y/N) [N]: |
Explanation |
The prompt asks you whether or not to save the modified configuration to CentraSite. |
Action |
Reply Y (for yes) or N (for no). The default value is N. |
INMCCI0075 | To store the connection, please provide the credentials of a user with role "CentraSite Administrator". |
Explanation |
The connection can only be stored by a user with the role "CentraSite Administrator". |
Action |
Provide the credentials of a user with the role "CentraSite Administrator". |
INMCCI0076 | Repeat configuration step {0}, Continue, or End? (R/C/E) [C]: |
Explanation |
You can either repeat the given configuration step, continue to the next step, or end the processing. |
Action |
Type R, C or E to select the required option. The default is C. |
INMCCI0077 | Repeat configuration step {0} or End? (R/E) [R]: |
Explanation |
You can repeat the given configuration step or end the processing. |
Action |
Type R or E to select the required option. The default is R. |
INMCCI0078 | Check {0} - Validating LDAP server configuration. Please wait... |
Explanation |
This message is displayed when validating the LDAP server configuration settings. |
Action |
No action required. |
INMCCI0079 | Check 2: LDAP User >> PLEASE WAIT... |
Explanation |
This message is shown when the configuration of the LDAP user is being checked. |
Action |
No action required. |
INMCCI0080 | Check 3: LDAP User Authentication >> PLEASE WAIT... |
Explanation |
This message is shown when the configuration of the LDAP user authentication is being checked. |
Action |
No action required. |
INMCCI0081 | Check 3: LDAP User Properties >> PLEASE WAIT... |
Explanation |
This message is shown when the configuration of the LDAP user properties is being checked. |
Action |
No action required. |
INMCCI0082 | Check 4: LDAP User Search >> PLEASE WAIT... |
Explanation |
This message is shown when the configuration of the LDAP user search is being checked. |
Action |
No action required. |
INMCCI0083 | Check 5: LDAP Group >> PLEASE WAIT... |
Explanation |
This message is shown when the configuration of the LDAP group is being checked. |
Action |
No action required. |
INMCCI0084 | Check 6: LDAP Group Mapping >> PLEASE WAIT... |
Explanation |
This message is shown when the configuration of the LDAP group mapping is being checked. |
Action |
No action required. |
INMCCI0085 | Check 7: LDAP Group Search >> PLEASE WAIT... |
Explanation |
This message is shown when the configuration of the LDAP group search is being checked. |
Action |
No action required. |
INMCCI0086 | Check 8: LDAP Group Resolution Host >> PLEASE WAIT... |
Explanation |
This message is shown when the configuration of the LDAP group resolution host is being checked. |
Action |
No action required. |
INMCCI0087 | Check 9: Displaying and saving configuration in CentraSite >> PLEASE WAIT... |
Explanation |
This message is shown when the checked LDAP configuration is being saved in CentraSite. |
Action |
No action required. |
INMCCI0095 | Do you want to see the complete trace? {0} : |
Explanation |
The prompt asks you whether or not you want to see the complete trace. |
Action |
Type Y (yes) or N (no) as required. The default is N. |
INMCCI0097 | Group elements found: {0} . Do you want to see them? |
Explanation |
This is a confirmation message indicating that group elements have been found. |
Action |
Reply Yes if you want to see the group elements. |
INMCCI0098 | Do you want to see all groups? {0} : |
Explanation |
This prompt asks you if you want to see all groups. |
Action |
Reply Yes if you want to see the groups. |
INMCCI0099 | Groups with filter: {0} |
Explanation |
This is a confirmation message indicating that groups have been found with the filter. |
Action |
No action required. |
INMCCI0101 | Groups for user found: {0} Do you want to see them? |
Explanation |
Groups were found for the given user. |
Action |
Reply Yes if you want to see the groups that were found. |
INMCCI0107 | Do you want to use the LDAP Technical User {0}: |
Explanation |
This prompt asks you whether you want to use the LDAP Technical User (LDAP Principal) to access the LDAP user repository. If you reply Y, all authentication requests sent to the LDAP server will be made using this user. If you reply N, the client has to send its own credentials to LDAP to access a user record. |
Action |
Type Y (for yes) or N (for no) as appropriate, then press Enter. The default is N. |
INMCCI0108 | Provide the LDAP Technical User credentials file. |
Explanation |
This prompt asks you to provide the LDAP Technical User credentials file. |
Action |
Provide the LDAP Technical User credentials file. |
INMCCI0109 | Provide the LDAP Technical User Key file |
Explanation |
This prompt asks you to provide the LDAP Technical User Key file. |
Action |
Provide the LDAP Technical User key file. |
INMCCI0110 | Trying to connect to LDAP at: {0} |
Explanation |
An attempt is being made to connect to the LDAP Server with the given host name and port. |
Action |
No action required. |
INMCCI0133 | The target identified by "{0}" has been removed from the configured federation targets. |
Explanation |
The target identified by "{0}" has been removed from the configured federation targets during the execution of the command. |
Action |
No action required. |
INMCCI0134 | A target is already associated with the given federation id "{0}". |
Explanation |
The provided federation identifier already has a target associated with it. |
Action |
To obtain more details about the target associated with ID "{0}", execute the command show_uddi_federation. |
INMCCI0135 | Do you want to update/overwrite the target at {0} ? {1} : |
Explanation |
While running the add_uddi_federation command with the ID {0}, it may be already configured with another target. Then you should choose whether you want to update the target or not. |
Action |
Enter either y (Yes) to update/overwrite the target, or n (No) to do no modification. The default is y (Yes). |
INMCCI0136 | Not overwriting the current configuration. Please provide another federation identifier |
Explanation |
While executing the add_uddi_federation command, if an already existing identifier is provided, and you choose not to overwrite the target, then this message is displayed. |
Action |
You can provide a new identifier which does not already exist. To obtain the list of configured federation identifiers, execute the command show_uddi_federation. |
INMCCI0137 | Overwriting/updating the target identified by "{0}" |
Explanation |
While executing the command add_uddi_federation, if the provided federation identifier already exists, and you choose to overwrite/update the target, then you get this message. |
Action |
No action required. |
INMCCI0138 | A target has been added/updated with the federation identifier {0} |
Explanation |
This message is displayed if a target for federation has been successfully configured with the provided federation ID. |
Action |
No action required. |
INMCCI0143 | Number of targets configured for federation : {0} |
Explanation |
This message displays the number of targets configured for federation. {0} - Number of targets |
Action |
No action required. |
INMCCI0145 | Deployment succeeded |
Explanation |
The deployment succeeded. |
Action |
No action required. |
INMCCI0147 | There are no Consumer Applications to deploy. |
Explanation |
There are no consumer applications created in CentraSite to deploy. |
Action |
Create consumer applications in CentraSite to deploy to Mediator. |
INMCCI0148 | The XML configuration of the Federation target "{0}": |
Explanation |
The XML configuration of the federation target identified by {0} will be displayed in the console. |
Action |
No action required. |
INMCCI0149 | The XML configuration of the Federation target "{0}" has been written to file "{1}" |
Explanation |
This message informs that the XML configuration of the federation target identified by {0} has been written to the file located at {1}. |
Action |
No action required. |
INMCCI0150 | The XML log configuration can be seen below: |
Explanation |
The XML log configuration will be displayed to the console. |
Action |
No action required. |
INMCCI0151 | The XML log configuration has been written to the file "{0}" |
Explanation |
This message informs that the XML log configuration has been written to the file located at {0}. |
Action |
No action required. |
INMCCI0176 | Domain {0} not found in jaas.config |
Explanation |
The domain to be processed does not exist in jaas.config |
Action |
Correct the specified domain name. |
INMCCI0228 | Do you really want to save the configuration {0} |
Explanation |
When the end of the command is reached, the user is asked if the created LDAP configuration should be added to the current jaas.config file. |
Action |
Reply Y (for yes) or N (for no). There is no default value. |
INMCCI0229 | The configuration has been saved successfully. |
Explanation |
The LDAP configuration has been added successfully to the current jaas.config file. |
Action |
No action required. |
INMCCI0232 | Check {0} - Validating LDAP user configuration. Please wait... |
Explanation |
This message is displayed when validating the LDAP user configuration settings. |
Action |
No action required. |
INMCCI0233 | The LDAP user configuration has been successfully validated. |
Explanation |
The specified LDAP user configuration is valid. |
Action |
No action required. |
INMCCI0236 | Check {0} - Validating LDAP user mapping configuration. Please wait... |
Explanation |
This message is displayed when validating the LDAP user mapping configuration settings. |
Action |
No action required. |
INMCCI0237 | The LDAP user mapping configuration has been successfully validated. |
Explanation |
The specified LDAP user mapping configuration is valid. |
Action |
No action required. |
INMCCI0239 | The following attributes have been retrieved for the LDAP user {0}: |
Explanation |
Displays a list of mapped user attributes for the LDAP user {0}. |
Action |
No action required. |
INMCCI0240 | No attributes could be retrieved for user {0}. |
Explanation |
Could not retrieve attributes for the specified LDAP user {0}, possibly because all of the attributes are empty. |
Action |
No action required. |
INMCCI0241 | No users were found matching search criteria {0}. |
Explanation |
Could not find any users matching the specified search criteria {0}. |
Action |
No action required. |
INMCCI0242 | The following users match the search criteria {0}: |
Explanation |
Displays a list of LDAP users matching the search criteria {0}. |
Action |
No action required. |
INMCCI0243 | The following users match the search criteria {0}. The following list only displays the first ten users matching the specified search criteria: |
Explanation |
Displays the first ten users matching the search criteria {0}. |
Action |
No action required. |
INMCCI0244 | No attributes could be retrieved for group {0}. |
Explanation |
Could not retrieve attributes for the specified LDAP group {0}, possibly because all of the attributes are empty. |
Action |
No action required. |
INMCCI0245 | No groups were found matching search criteria {0}. |
Explanation |
Could not find any groups matching the specified search criteria {0}. |
Action |
No action required. |
INMCCI0246 | The following groups match the search criteria {0}: |
Explanation |
Displays a list of LDAP groups matching the search criteria {0}. |
Action |
No action required. |
INMCCI0247 | The following groups match the search criteria {0}. The following list only displays the first ten groups matching the specified search criteria: |
Explanation |
Displays the first ten groups matching the search criteria {0}. |
Action |
No action required. |
INMCCI0248 | The LDAP group mapping configuration has been successfully validated. |
Explanation |
The specified LDAP group mapping configuration is valid. |
Action |
No action required. |
INMCCI0249 | Check {0} - Validating LDAP group mapping configuration. Please wait... |
Explanation |
This message is displayed when validating the LDAP group mapping configuration settings. |
Action |
No action required. |
INMCCI0250 | The following attributes have been retrieved for the LDAP group {0}: |
Explanation |
Displays a list of mapped group attributes for the LDAP group {0}. |
Action |
No action required. |
INMCCI0251 | Check {0} - Validating LDAP group configuration. Please wait... |
Explanation |
This message is displayed when validating the LDAP group configuration settings. |
Action |
No action required. |
INMCCI0252 | The specified LDAP group could not be found. |
Explanation |
Could not find the specified LDAP group in the LDAP server. |
Action |
No action required. |
INMCCI0253 | The LDAP group configuration has been successfully validated. |
Explanation |
The specified LDAP group configuration is valid. |
Action |
No action required. |
INMCCI0254 | Check {0} - Validating LDAP group resolution configuration. Please wait... |
Explanation |
This message is displayed when validating the LDAP group resolution configuration settings. |
Action |
No action required. |
INMCCI0255 | User {0} belongs to the following groups: |
Explanation |
Displays a list of LDAP groups to which the user with name {0} belongs to. |
Action |
No action required. |
INMCCI0256 | The LDAP group resolution configuration has been successfully validated. |
Explanation |
The specified LDAP group resolution configuration is valid. |
Action |
No action required. |
INMCCI0257 | User {0} belongs to the following groups: |
Explanation |
Displays the first ten LDAP groups to which the user with name {0} belongs to. |
Action |
No action required. |
INMCCI0258 | No groups were found to which the user {0} belongs to. |
Explanation |
Could not find any groups to which the specified user with name {0} belongs to. |
Action |
No action required. |
INMCCI0263 | Test user has successfully logged in. |
Explanation |
Test user has successfully logged in. |
Action |
No action required. |
INMCCI0265 | Search for user was successful. |
Explanation |
|
Action |
|
INMCCI0288 | Action category named {0} is created successfully. |
Explanation |
N/A |
Action |
N/A |
INMCCI0290 | Action category named {0} is updated successfully. |
Explanation |
N/A |
Action |
N/A |
INMCCI0291 | No changes available |
Explanation |
N/A |
Action |
N/A |
INMCCI0296 | Action category named {0} is deleted successfully. |
Explanation |
NA |
Action |
NA |
INMCCI0298 | Action template named {0} is created successfully. |
Explanation |
N/A |
Action |
N/A |
INMCCI0310 | Action template named {0} is updated successfully. |
Explanation |
N/A |
Action |
N/A |
INMCCI0312 | Action template named {0} is deleted successfully. |
Explanation |
NA |
Action |
NA |
INMCCI0316 | Action template named {0} is downloaded successfully to {1}. |
Explanation |
NA |
Action |
NA |
INMCCI0318 | Action template named {0} is downloaded successfully to {1}. |
Explanation |
NA |
Action |
NA |
INMCCI0320 | Custom policy action setup successful at {0}. |
Explanation |
NA |
Action |
NA |
INMCCI0323 | Group {0} synchronized successfully. |
Explanation |
N/A |
Action |
N/A |
INMCCI0324 | Members of the group {0} are already registered in CentraSite. |
Explanation |
NA |
Action |
NA |
INMCCW0004 | Default Organization is not present in CentraSite. Hence UDDI configurations cannot be saved. |
Explanation |
UDDI Configurations for CentraSite will be stored in "Default Organization". CentraSiteCommand is not able to find the "Default Organization" in CentraSite and hence cannot store the UDDI configurations. |
Action |
Make sure the user provided to execute the command has permission to update the "Default Organization". |
INMCCW0005 | No CentraSite Application Server Tier (CAST) found in CentraSite with specified cast URI {0}. Please specify fully qualified host name in -casturi option. |
Explanation |
UDDI configurations for a CAST will be stored in an Application Server object. The object will have the host and port details. This object is required to store the local configurations for the CAST. CentraSiteCommand is not able to find the ApplicationServer object with the host specified in the cast URI option. |
Action |
Please make sure the value specified for the option cast URI is valid. Please specify the host as a fully qualified domain name in the cast URI option. |
INMCCW0104 | unknown host |
Explanation |
The host name provided is not the name of a known host. |
Action |
Provide a proper host name. |
INMCCW0128 | An error occurred while trying to close a resource - {0} |
Explanation |
Occasionally an error might be encountered while trying to close open connections, streams, etc., This is just a warning that an error was encountered and can be ignored. |
Action |
Make sure that the resource in question is not opened and/or modified by another program/application. |
INMCCW0146 | Deployment failed |
Explanation |
The deployment failed. |
Action |
Check related messages to find the reason why the deployment failed. |
INMCCW0168 | Missing <LogSetting> attribute for <LogUnit> {0}. |
Explanation |
The <LogSetting> attribute used to configure <LogUnit> {0} is missing. |
Action |
The <LogSetting> attribute is specified as an attribute name when configuring log unit in the config.xml file. For more information about log settings, see the CentraSite Administrator's Guide. |
INMCCW0169 | The <LogUnit> {0} has a null value for the <LogSetting> attribute. |
Explanation |
Required <LogSetting> attribute value is missing. |
Action |
The <LogSetting> value is specified as an attribute value when configuring log unit in the config.xml file. For more information about log settings, see the CentraSite Administrator's Guide. |
INMCCW0230 | Configuration was not saved on user request! |
Explanation |
The configuration was not saved, possibly because the user chose to reject it. |
Action |
No action required. |
INMCCW0264 | Test User was not found. |
Explanation |
Could not find the specified test user. |
Action |
No action required. |
INMCCW0275 | You cannot deactivate the user(s). Reason |
Explanation |
The user cannot be deactivated for the following reason(s): |
Action |
Check for the above reasons and then try again. |
INMCCW0299 | Implementation-File parameter cannot be empty. Enter the name of a Java implementation file for policy action. |
Explanation |
N/A |
Action |
N/A |
INMCCW0300 | Action category named {0} does not exist. |
Explanation |
N/A |
Action |
N/A |
INMCCW0301 | Template-File parameter cannot be empty. Enter the name of an output file to download the action template. |
Explanation |
N/A |
Action |
N/A |
INMCCW0302 | Action template named {0} already exists. |
Explanation |
N/A |
Action |
N/A |
INMCCW0304 | Action must be associated at least to one object type. |
Explanation |
N/A |
Action |
N/A |
INMCCW0305 | Event type should have at least one value. |
Explanation |
N/A |
Action |
N/A |
INMCCW0306 | Parameter name cannot be empty. |
Explanation |
N/A |
Action |
N/A |
INMCCW0307 | Parameter type cannot be empty. |
Explanation |
N/A |
Action |
N/A |
INMCCW0308 | Policy action template with the given name {0} does not exist. |
Explanation |
NA |
Action |
NA |
INMCCW0309 | Implementation file of predefined action templates cannot be modified. |
Explanation |
NA |
Action |
NA |
INMCCW0311 | One or more required parameters in the action template configuration are missing. |
Explanation |
NA |
Action |
NA |
INMCCW0325 | Group with the given name {0} does not exist in {1}. |
Explanation |
NA |
Action |
NA |
INMCCW0326 | The specified object group {0} has wrong type. |
Explanation |
NA |
Action |
NA |
INMCLE0005 | CentraSite cannot delete the gateway. {0} |
Explanation |
An error occured while deleting a gateway in CentraSite. |
Action |
Contact your system administrator with the stack trace information in the CentraSite log. |
INMCLE0013 | Caught an exception while retrieving the configurator instance. |
Explanation |
This is an internal error. It is probably because of an invalid data in the configuration file. |
Action |
Verify that the data in configuration file are valid. |
INMCLE0014 | System is unable to retrieve value for {0}. |
Explanation |
This is an internal error. It is probably because of an invalid data in the configuration file. |
Action |
Verify that the data in configuration file are valid. |
INMCLE0015 | Invalid path {0}. |
Explanation |
You have entered an invalid path. |
Action |
Enter a valid path. |
INMCLE0017 | Failed to check whether or not property of {0} is read-only. |
Explanation |
Could not check whether or not the property of the given path {0} is read-only. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0018 | Caught an exception while retrieving the configuration file of type {0}. |
Explanation |
This is an internal error. It is probably because of an invalid data in the configuration file. |
Action |
Verify that the data in configuration file are valid. |
INMCLE0019 | Caught an exception while trying to save the configuration file of type {0}. |
Explanation |
This is an internal error. It is probably because of an invalid data in the configuration file. |
Action |
Verify that the data in configuration file are valid. |
INMCLE0020 | Failed to remove {0}. |
Explanation |
This is an internal error. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0021 | Caught an exception while trying to get the configuration file URL for type {0}. |
Explanation |
Could not get configuration file URL for type {0}, possibly because of an invalid data in the configuration file. |
Action |
Verify that the data in configuration file are valid. |
INMCLE0022 | Path or property value is empty. |
Explanation |
You have entered an empty path or property value. |
Action |
Enter a valid path or property value. |
INMCLE0023 | Failed to set configuration(s) for the path(s), {0} |
Explanation |
Unable to set configuration(s) for the path(s). This is probably because of the following reasons: 1) configuration file is modified 2) failed to save the configuration file. |
Action |
Check to make sure that the configuration in a higher level is not already protected. Else, check the stack trace for detailed information. |
INMCLE0024 | Failed to setProtectAll. |
Explanation |
Unable to set ProtectAll configuration. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0025 | Failed to getAllItems. |
Explanation |
Unable to get one or more configuration items. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0026 | Unable to construct ActivityMenuItem for id {0}. |
Explanation |
Could not construct ActivityMenuItem for the given id {0}, possibly because the XPath of the ActivityMenuItem is invalid. |
Action |
Verify that the XPath of the ActivityMenuItem is valid. |
INMCLE0027 | Unable to construct activity for id {0}. |
Explanation |
Could not construct activity for the given id {0}, possibly because the XPath of the activity is invalid. |
Action |
Verify that the XPath of the activity is valid. |
INMCLE0028 | Unable to construct ActivityMenuItem for activity {0}. |
Explanation |
Check for the above possible reasons. If the problem persists, contact the CentraSite administrator. |
Action |
Check to make sure that the XPath of the ActivityMenuItem and Activity is correct and the corresponding Activity could be created. |
INMCLE0029 | Failed to instantiate class {0}. |
Explanation |
Could not instantiate the implementation class {0}, possibly because the class does not follow a valid syntax. |
Action |
Verify that the implementation class follows a valid syntax. Refer to the documentation reference for Activity Implementation class. |
INMCLE0030 | Unable to find activity entry for id {0}. |
Explanation |
Could not find an activity entry for the given id {0}, possibly because the id is invalid. |
Action |
Verify that the given activity id is correct. |
INMCLE0031 | Unable to construct an ActivityMenu using activities. |
Explanation |
Could not construct an ActivityMenu using the given activities. It is probably because, the activities do not exist. |
Action |
Verify that the activities exist. If the problem persists, contact the CentraSite administrator. |
INMCLE0033 | Failed to remove ActivityMenuItems. |
Explanation |
Could not remove the ActivityMenuItems from given configuration file. It is possibly because of the following reasons: 1) XPath to remove the ActivityMenuItem is invalid. 2) ActivityMenuItem does not exist. |
Action |
Check for the above possible reasons. If the problem persists, contact the CentraSite administrator. |
INMCLE0034 | Failed to save ActivityMenuItems. |
Explanation |
Could not save the ActivityMenuItems from given configuration file. It is possibly because of the following reasons: 1) XPath to save the ActivityMenuItem is invalid. 2) ActivityMenuItem does not exist. |
Action |
Check for the above possible reasons. If the problem persists, contact the CentraSite administrator. |
INMCLE0035 | User has not passed the CentraSite connection object. For a valid diagnostics configuration, CentraSite connection object is mandatory. |
Explanation |
User has not passed the CentraSite connection object, which is mandatory for a valid diagnostics configuration. |
Action |
Enter a valid CentraSite connection object. |
INMCLE0036 | Email address is empty, |
Explanation |
You have not entered the email address for diagnostics configuration. An email address is mandatory to send the diagnostic information. |
Action |
Enter a valid email address. |
INMCLE0037 | Email subject and template are empty. |
Explanation |
You have not entered the email subject and template for diagnostics configuration. An email template is mandatory to send the diagnostic information. Refer to the CentraSite online documentation’s section “Message Handling and Diagnostics”. |
Action |
Enter the email subject and a valid template. |
INMCLE0038 | Failed to get all activities. |
Explanation |
Could not get all the activities, possibly because the activity classes are not set in the classpath. |
Action |
Verify that the activity classes are set in the classpath. If the problem persists, contact the CentraSite administrator. |
INMCLE0039 | Failed to remove activity for given id {0}. |
Explanation |
Could not remove the activity for given id {0}, possibly because the activity id is invalid. |
Action |
Verify that the given activity id is valid. |
INMCLE0040 | Failed to show one or more activity menu items that are associated with activity menu. |
Explanation |
Could not display one or more activity menu items, possibly because the menu items are not associated with the activity menu. |
Action |
Verify that all the activity menu items are associated with activity menu. |
INMCLE0041 | Failed to populate diagnostic context. |
Explanation |
Could not populate the diagnostic context object, possibly because the CentraSite Connection object is incorrect. |
Action |
Verify that the CentraSite Connection object is correct. |
INMCLE0042 | Invalid CentraSite connection URL {0}. |
Explanation |
You have entered an invalid CentraSite Connection URL. |
Action |
Enter a valid CentraSite Connection URL. |
INMCLE0043 | User has not passed CLLException object. For a valid diagnostics configuration, CLLException object is mandatory. |
Explanation |
User has not passed the CLLException object which is mandatory for the diagnostics configuration. |
Action |
Enter a valid CLLException object. |
INMCLE0044 | Unable to fetch email template from repository {0}. |
Explanation |
Could not fetch the email template from given repository {0}, possibly because of the following reasons: 1) email template does not exists 2) repository URL is invalid. |
Action |
Check for the above possible reasons. If the problem persists, contact the CentraSite administrator. |
INMCLE0045 | Error loading implementation class for ActivityManager. |
Explanation |
An unexpected error occurred while trying to load the implementation class for given ActivityManager. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0046 | Error loading diagnosticHandler implementation class. |
Explanation |
An unexpected error occurred while trying to load the diagnosticHandler implementation class. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0048 | Failed to instantiate class {0}. |
Explanation |
Could not instantiate the given class {0}, possibly because of the following reasons: 1) class file does not exist 2) classpath is incorrect. |
Action |
Check for the above possible reasons. If the problem persists, contact the CentraSite administrator. |
INMCLE0049 | Failed to initialize {0}. |
Explanation |
Could not initialize the given component {0}. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0050 | Failed to get CentraSite registry object property {0}. |
Explanation |
Could not get the CentraSite registry object property. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0051 | Failed to set registry object property {0}. |
Explanation |
Could not set the CentraSite registry object property. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0052 | Failed to save CentraSite object {0}. |
Explanation |
An error occurred while trying to save CentraSite model object. Possible reasons: {1} |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0053 | Failed to delete CentraSite object {0}. |
Explanation |
Could not delete the CentraSite object. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0054 | Failed to get CentraSite object for id {0}. |
Explanation |
Could not get CentraSite object for the given id {0}, possibly because the object id is invalid. |
Action |
Verify that the object id is valid. |
INMCLE0055 | Failed to create CentraSite object {0}. |
Explanation |
You cannot create the CentraSite object {0}, possibly because of the following reasons: 1) insufficient privileges to create the object 2) object type is invalid. |
Action |
Check for the above possible reasons and execute again. If the problem persists, contact the CentraSite administrator. |
INMCLE0056 | Failed to delete CentraSite object. |
Explanation |
You cannot delete the CentraSite object {0}, possibly because you do not have the required permission to delete the object. |
Action |
Verify that you have the required permission to delete the CentraSite object. Contact your administrator and request permission if necessary and try again. |
INMCLE0057 | Unable to get list of CentraSite objects: {0}. |
Explanation |
You cannot retrieve the following list of CentraSite objects: {0}. It is possibly because you do not have the required permission to retrieve the objects. |
Action |
Verify that you have the required permission to retrieve the given objects. Contact your administrator and request permission if necessary and try again. |
INMCLE0058 | Unable to save list of CentraSite objects: {0} |
Explanation |
You cannot save the following list of CentraSite objects: {0}. It is possibly because you do not have the required permission to save the objects.{0} |
Action |
Verify that you have the required permission to save the given objects. Contact your administrator and request permission if necessary and try again. |
INMCLE0059 | Unable to delete list of CentraSite objects: |
Explanation |
You cannot delete the following list of CentraSite objects: {0}. It is possibly because you do not have the required permission to delete the objects. |
Action |
Verify that you have the required permission to delete the given objects. Contact your administrator and request permission if necessary and try again. |
INMCLE0060 | Caught an unexpected exception while converting concept to CentraSiteObjectType. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0061 | Failed to populate ObjectType for given name {0}. |
Explanation |
Could not populate the ObjectType for display name {0}, possibly because the given display name is incorrect. |
Action |
Verify that the display name is correct. |
INMCLE0062 | Error retrieving the list of gateways. |
Explanation |
CentraSite could not retrieve the list of existing gateways because of an error during gateway name validations. |
Action |
Contact your CentraSite Administrator. |
INMCLE0063 | Unsupported attribute {0} for object type {1}. |
Explanation |
This is an internal error. Cannot find the attribute {0} of the specified object type {1}. |
Action |
Check to make sure that the attribute {0} is present in the object type {1}. |
INMCLE0064 | Failed to fetch attributes for {0}. |
Explanation |
Could not fetch attributes for {0}, possibly because the object type {1} is invalid. |
Action |
Verify that the object type {1} is valid. |
INMCLE0065 | Unable to obtain value for attribute {0}. |
Explanation |
Could not obtain the value for attribute {0}. The cause is not immediately known. |
Action |
Verify integrity of the object and try later. |
INMCLE0066 | Unsupported method for attribute {0} of object type {1}. |
Explanation |
This method is not applicable for attribute {0} of object type {1}. |
Action |
Do not use this method for attribute {0} of object type {1}. |
INMCLE0067 | Error while initializing CentraSiteConnector {0}. |
Explanation |
Could not initialize the CentraSiteConnector {0}. It is probably because of the following reasons: 1) invalid class as CentraSite Connection Factory 2) invalid system property (com.softwareag.centrasite.common.connection.impl) for initializing. |
Action |
Check for the above possible reasons and execute again. If the problem persists, contact the CentraSite administrator. |
INMCLE0068 | Failed to create an ActivityMenuItem for id {0}. |
Explanation |
Could not create the ActivityMenuItem for above id, possibly because of the invalid configurations. |
Action |
Verify that the activity id and class name are configured properly. |
INMCLE0069 | Error when closing connection {0}. |
Explanation |
Error occurred when trying to close the underlying connection. |
Action |
Initialize before opening a connection. |
INMCLE0070 | Failed to log in {0}. |
Explanation |
Could not log in {0}, possibly because the login credentials are invalid. |
Action |
Enter valid login credentials. |
INMCLE0071 | Cannot instantiate CentraSiteConnector class {0}. |
Explanation |
Could not instantiate the CentraSiteConnector implementation class, possibly because the implementation class in invalid. |
Action |
Check to make sure that the CentraSiteConnector class is valid. |
INMCLE0072 | Error loading email template {0} {1}. |
Explanation |
Error when loading the admin and/or user email templates, possibly because the email template path is invalid. |
Action |
Verify that the email template path is valid. |
INMCLE0073 | Email address is empty. |
Explanation |
You have not entered an email address. |
Action |
Enter a valid email address. |
INMCLE0074 | Invalid attribute {0} {1}. |
Explanation |
The attribute {1} is not a valid {0} attribute. |
Action |
Check to make sure that the {1} attribute is valid. |
INMCLE0075 | Usage of {0} operation in object {1} is not supported. |
Explanation |
This operation is not supported on the given object {1}. |
Action |
Refer to the usage document for further information on the supported APIs. |
INMCLE0076 | Unable to obtain relationship details of attribute {0} to object type {1}. |
Explanation |
Could not obtain the relationship details of attribute {0} associated to the above object type {1}. |
Action |
Make sure that the attribute {0} is a valid relationship attribute for the object type {1}. |
INMCLE0077 | Failed to execute query {0}. |
Explanation |
Could not execute the query {0}, possibly because the query syntax is incorrect. |
Action |
Correct the query syntax. |
INMCLE0078 | Failed to execute query {0}. |
Explanation |
Could not execute the query {0}, possibly because the query syntax is incorrect. |
Action |
Correct the query syntax. |
INMCLE0079 | Failed to get objectTypeValue from given ObjectType. |
Explanation |
Could not get the objectTypeValue from ObjectType, possibly because the given ObjectType is invalid. |
Action |
Check to make sure that the given ObjectType is valid. |
INMCLE0080 | Failed to construct search query. |
Explanation |
Could not construct the search query. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0081 | Caught an exception while getting iterator from CSOSearchResult. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0082 | Failed to get search result count. |
Explanation |
Could not get the number of results displayed on the Search Results page. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0083 | Unable to fetch next object for id {0}. |
Explanation |
An unexpected exception occurred while trying to fetch the next object for above id. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0084 | The configuration file is invalid; attribute {0} is mandatory for multi-valued elements. |
Explanation |
The required attribute for multi-valued elements is not specified in the XML configuration file. |
Action |
Before you save the configuration file, check to make sure that all the required attributes are specified. |
INMCLE0085 | The configuration file is invalid; attribute {0} is mandatory for multi-valued elements. |
Explanation |
The required attribute for multi-valued elements is not specified in the XML configuration file. |
Action |
Before you save the configuration file, check to make sure that all the required attributes are specified. |
INMCLE0086 | Failed to fetch common attribute {0}. |
Explanation |
Could not fetch the common attribute {0}, possibly because the attribute does not exist. |
Action |
Verify that the common attribute {0} is valid. |
INMCLE0087 | Caught an exception while trying to set value for attribute {0}. |
Explanation |
Could not set a value for attribute {0}. It is probably because of the following reasons: 1) attribute does not exist 2) attribute is read-only. |
Action |
Check for the above possible reasons and execute again. If the problem persists, contact the CentraSite administrator. |
INMCLE0088 | Failed to retrieve attribute {0}. |
Explanation |
Could not retrieve attribute {0}, possibly because the attribute does not exist. |
Action |
Verify that the attribute is valid. |
INMCLE0089 | {0} based search has null or empty value. |
Explanation |
Could not execute {0} based search, possibly because of a null or empty value in the search criteria. |
Action |
Check to make sure that the search criteria is valid. |
INMCLE0090 | Data type {0} in search criteria is invalid. |
Explanation |
The specified data type {0} in search criteria is not supported. |
Action |
Specify a valid data type. Refer to the CentraSite online documentation’s section “Attribute Data Types” for a list of the supported data types. |
INMCLE0091 | The number of values provided in the search criteria does not match with the mandatory number allowed for the operator {0}. |
Explanation |
Every operator will support only the specified number of values. This error occurs when the number of values entered is less than or greater than the specified number. |
Action |
Refer to the CentraSite online documentation’s section “Searching the CentraSite Catalog”. |
INMCLE0092 | Failed to serialize search {0}. |
Explanation |
Could not serialize the above search, possibly because of invalid parameters in the search criteria. |
Action |
Check to make sure that the mandatory parameters are specified in search criteria. |
INMCLE0093 | Failed to create folder in WebDav. |
Explanation |
Could not create folder in the WebDav, possibly because you do not have the necessary permission to create a folder or intermediate folder in WebDav. |
Action |
Verify that you have the required permission to create a folder or intermediate folder in WebDav. |
INMCLE0094 | Failed to retrieve file from given URI {0}. |
Explanation |
Could not retrieve file from the above URI. This is probably because of the following reasons: 1) file does not exist 2) insufficient permissions to read the file. |
Action |
Check for the above possible reasons and execute again. If the problem persists, contact your service provider. |
INMCLE0095 | Search cannot be executed with given URI {0}. |
Explanation |
Could not execute a search with URI {0}, possibly because the given URI is invalid. |
Action |
Verify that the specified URI is valid. If the problem persists, contact the CentraSite administrator. |
INMCLE0096 | Failed to parse persisted search output {0}. |
Explanation |
Could not parse the search output, possibly because of an invalid XML syntax. |
Action |
Verify that the XML syntax is correct. |
INMCLE0097 | Failed to convert input {0} to bytes. |
Explanation |
Could not convert the given input {0} to bytes. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0098 | Failed to read output. |
Explanation |
Failed to read the output, possibly because the input or output stream is closed. |
Action |
Make sure that the input or output stream is open. |
INMCLE0099 | Failed to initialize parser. |
Explanation |
Error: could not initialize parser. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0100 | Failed to get search data stored in folder {0}. |
Explanation |
Could not get search data files that were stored in the above folder, possibly because you do not have insufficient permission to access the files. |
Action |
Verify that you have required permissions to access the data files. |
INMCLE0101 | Cannot instantiate class{0}. |
Explanation |
Could not instantiate the above class, possibly because the class is incorrect. |
Action |
Check to make sure that the implementation class is correct and follows a specified syntax. Refer to the documentation reference for Action Implementation class. |
INMCLE0102 | Failed to load actions from system configurations. |
Explanation |
Could not load specific actions from the system configuration file because of the following reasons: 1) class name for action is incorrect 2) action is not configured. |
Action |
Check to make sure that the class name for actions is correct and is configured in your system.xml file. |
INMCLE0103 | Unable to retrieve actions for null parameter. |
Explanation |
Internal error. It is possibly because you are trying to pass parameter with null value. |
Action |
Check if the parameter contains a null value. |
INMCLE0104 | Failed to get configurator {0} |
Explanation |
Could not get the above configurator, possibly because you do not have the required permissions. |
Action |
Verify that you have the required permission to get configurator. Contact your administrator and request permission if necessary and try again. |
INMCLE0105 | Failed to get owner from connection. |
Explanation |
Could not get the owner from connection, possibly because you do not have the required permissions. |
Action |
Verify that you have the required permission to get owner from connection. Contact your administrator and request permission if necessary and try again. |
INMCLE0106 | Login failed. |
Explanation |
Failed to login to CentraSite. It is possibly because of the following reasons: 1) incorrect CentraSite URL 2) invalid authentication credentials. |
Action |
Check for the above possible reasons and execute again. If the problem persists, contact the CentraSite administrator. |
INMCLE0107 | {0} object is null. |
Explanation |
Error: given object is null. |
Action |
Check to make sure that the given object is not null. |
INMCLE0108 | Failed to get an instance of component {0}. |
Explanation |
Could not get an instance of the above component. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0111 | Failed to remove file {0} from WebDaV. |
Explanation |
Could not create a folder in WebDav. It is probably because of the following reasons: 1) file does not exist in WebDav 2) insufficient permission to remove a file from WebDav. |
Action |
Check for the above possible reasons and execute again. If the problem persists, contact the CentraSite administrator. |
INMCLE0112 | Failed to create a file in {0}. |
Explanation |
Could not create a file in {0}, possibly because the parent directory does not exist in the given location. |
Action |
Verify that parent directory exists in the given location. |
INMCLE0113 | Could not instantiate AccessControlElement. |
Explanation |
Unable to instantiate the AccessControlElement. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0114 | Failed to find resource exists for given URL {0}. |
Explanation |
Could not find the file for given URL. It is probably because the file does not exist in the given URL. |
Action |
Check to make sure that the file exists in given URL. |
INMCLE0115 | Failed to purge older versions of CentraSite object. |
Explanation |
Could not purge older versions of the CentraSite object. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0116 | Unable to version CentraSite object. |
Explanation |
Could not create a new version of the CentraSite object. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0117 | Unable to obtain base type for {0}. |
Explanation |
Could not obtain the base type for {0}. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0118 | Failed to retrieve profiles for {0}. |
Explanation |
Could not retrieve profiles for {0} because of the following reasons: 1) failure in retrieving profiles from type 2) insufficient permission for accessing the profiles. |
Action |
Check for the above possible reasons and execute again. If the problem persists, contact the CentraSite administrator. |
INMCLE0119 | Failed to retrieve information for profile {0}. |
Explanation |
Could not retrieve the information for profile. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0120 | Failed to choose assets for {0}. |
Explanation |
Could not choose the assets for executing above action, possibly because the action is not in the 'initial' state. |
Action |
Verify that the action is in 'initial' state. |
INMCLE0122 | Failed to retrieve immediate allowed states. |
Explanation |
This is an unexpected exception. It is probably because the current lifecycle state does not have at least one immediate state. |
Action |
Check to make sure that the current lifecycle state has at least one immediate state. |
INMCLE0123 | Failed to retrieve immediate preferred state |
Explanation |
This is an unexpected exception. It is probably because the current lifecycle state does not have at least one immediate state. |
Action |
Check to make sure that the current lifecycle state has at least one immediate state. |
INMCLE0124 | Failed to retrieve current state. |
Explanation |
This is an unexpected exception. It is probably because the object is not associated with any of the lifecycle model. |
Action |
Check to make sure that the object type is associated with at least one lifecycle model. |
INMCLE0125 | Failed to retrieve pending state. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact your system administrator. |
INMCLE0126 | Failed to identify if state of object is pending or not. |
Explanation |
Could not identify if state of the object is in pending or not. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact your system administrator. |
INMCLE0127 | Failed to get lifecycle model assigned types. |
Explanation |
Could not get the lifecycle model assigned types. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact your system administrator. |
INMCLE0128 | Failed to identify initial state of lifecycle model. |
Explanation |
Could not identify initial state of the lifecycle model. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact your system administrator. |
INMCLE0129 | Failed to get applicable states of lifecycle model. |
Explanation |
Could not get applicable states of the lifecycle model. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact your system administrator. |
INMCLE0130 | Failed to identify if given lifecycle model is global or not. |
Explanation |
Could not identify if the given lifecycle model belongs to the global category. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact your system administrator. |
INMCLE0131 | Mandatory parameters to identify applicable lifecycle models are empty. |
Explanation |
An attempt is made to pass one or more of the mandatory parameters (CentraSiteObjectType or Organization) empty. |
Action |
Enter valid value for the mandatory parameters. |
INMCLE0132 | Mandatory parameters to identify applicable lifecycle models are empty. |
Explanation |
An attempt is made to pass one or more of the mandatory parameters (Keyword, CentraSiteObjectType or Organization) empty. |
Action |
Enter valid value for the mandatory parameters. |
INMCLE0133 | setParameter value for a CSOSearch is empty. |
Explanation |
An attempt is made to pass an empty list of values for the setParameter of CSOSearch. |
Action |
Enter a valid list of values for the CSOSearch. |
INMCLE0134 | Invalid authentication credentials. |
Explanation |
You have entered invalid authentication credentials. |
Action |
Enter valid authentication credentials. |
INMCLE0135 | Folder {0} does not exist. |
Explanation |
The specified folder does not exist in WebDav. |
Action |
Create the folder in WebDav and try again. |
INMCLE0136 | Choose the CentraSite Object(s) to perform this action. |
Explanation |
You have not chosen the CentraSite Object(s) for performing this action. |
Action |
Choose the CentraSite Object(s) to perform this action. |
INMCLE0137 | Failed to perform {0} on multiple CentraSite objects. |
Explanation |
You cannot perform {0} on multiple CentraSite objects at a time. |
Action |
Ensure you choose only one CentraSite object for performing {0}. |
INMCLE0138 | Failed to check if {0} is applicable or not. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0139 | Failed to perform {0} on specified CentraSite object(s). |
Explanation |
Could not perform {0} on the specified CentraSite object(s) due to one or more of the following reasons: (1) inufficient permission (2) CentraSite object is in 'Pending' state (3) CentraSite object is locked for editing by another user. |
Action |
Check for the above possible reasons and execute again. Else, contact the CentraSite administrator. |
INMCLE0140 | Failed to verify if current user has Edit permission on {0}. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0141 | You are trying to modify an outdated asset. |
Explanation |
You are trying to modify an asset which is outdated. |
Action |
Before you start to edit an asset, refresh the details page. |
INMCLE0142 | Failed to verify if user has Move permission on CentraSite object. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0143 | Failed to cancel {0}. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0144 | Error loading saved search with name {0}. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
If the problem persists, contact our technical support. |
INMCLE0145 | {0} is required for CSOSearch. |
Explanation |
Mandatory property {0} for executing a CSOSearch is missing. |
Action |
Check to make sure that the mandatory property is specified. |
INMCLE0146 | Mismatch of attribute {0} specified in {1} with {2}. |
Explanation |
The attribute in {1} does not match with the given {2}. |
Action |
Remove the faulty {1} and execute again. |
INMCLE0147 | Caught an exception while getting profile id for {0}. |
Explanation |
Could not retrieve the profile id for {0}. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0148 | {0} with name {1} used in {2} does not exist. |
Explanation |
{0} with name {1} used in {2} does not exist. |
Action |
Contact the CentraSite administrator. |
INMCLE0149 | Object {0} is null. |
Explanation |
Could not get the object {0}. |
Action |
The object should be initialized before executing this operation. |
INMCLE0150 | Caught an exception while trying to fetch pending approval requests. |
Explanation |
Could not fetch pending approval requests for the logged in user. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0151 | Caught an exception while trying to verify if the logged in user has CentraSite Administrator role. |
Explanation |
Could not verify if the logged in user has CentraSite Administrator role. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0152 | Wrong usage of {0} method. |
Explanation |
Wrong usage of {0} method. This method is allowed only in the following scenarios: (1) if the action is in {1} state (2) before triggering the finishAllSteps() execution. |
Action |
Make sure that the method is used in one of the above scenarios. If the problem persists, contact the CentraSite administrator. |
INMCLE0153 | {0} execution without comments is invalid. |
Explanation |
{0} execution without comments is invalid. The approver has not specified his/her comments for {0}. |
Action |
Enter the comments for {0} using {1} API. |
INMCLE0154 | Failed to execute {0}. |
Explanation |
Could not execute {0}. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0155 | Failed to execute {0} |
Explanation |
Could not execute {0} due to one or more of the following reasons: (1) {0} is not allowed at the time of execution (2) assets for {0} are in 'Completed' state (3) for a Revert action, the you should have the CentraSite administrator role (4) you do not have a pending approval flow to proceed with {0}. |
Action |
Check for the above possible reasons and execute again. Else, contact the CentraSite administrator. |
INMCLE0157 | Invalid state transition from {0} by invoking {1} operation. |
Explanation |
The state transition from {0} by invoking the {1} operation is not valid. |
Action |
See the Action Java API documentation for more details. |
INMCLE0158 | One or more assets you have selected is not the most recent version of the asset. |
Explanation |
One or more selected assets is not the most recent version of the asset.The New Version action does not apply to assets with intermediate version. |
Action |
Check to make sure that the selected assets for versioning are in their most recent version. |
INMCLE0159 | Failed to create new version assets. |
Explanation |
Error occured when trying to create new version assets. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0160 | Caught an exception while invoking {0} operation. |
Explanation |
An unexpected exception occurred while trying to execute the {0} operation. |
Action |
Check the stack trace for detailed information. |
INMCLE0161 | Could not exclude a CentraSite object in {0} state from export. The object should be in "Export Preview" state. |
Explanation |
CentraSite object in a state other than "Export Preview" cannot be excluded from export. The CentraSite object in "Export Preview" state will only have the option to preview and modify the export list. |
Action |
Verify that the CentraSite object is in "Export Preview" state. Read the usage instructions of Export action before use. |
INMCLE0162 | Could not obtain export archive of a CentraSite object in {0} state. The object should be in "Completed" state. |
Explanation |
You cannot obtain an export archive of the CentraSite object, if the object is in a state other than "Completed". |
Action |
Verify that the CentraSite object is in "Completed" state. Read the usage instructions of Export action before use. |
INMCLE0163 | Failed to execute Consume action. |
Explanation |
Could not execute a Consume action, possibly because of one or more of the following reasons: 1) username is invalid 2) password is invalid 3) connection URL is incorrect. |
Action |
Check for the above possible reasons and execute again. Else, contact the CentraSite administrator. |
INMCLE0164 | An action in {0} state will not have Export List viewable. The action should be in "Export Preview" state. |
Explanation |
You cannot view an export list if the action is in a state other than "Export Preview". |
Action |
Verify that the action is in "Export Preview" state. Read the usage instructions of Export action before use. |
INMCLE0165 | Failed to execute Consume action. |
Explanation |
{0} execution can fail due to one or more of the following reasons: (1) consumers are not selected (2) consumer requests are not registered. |
Action |
Check for the above possible reasons and execute again. Else, contact the CentraSite administrator. |
INMCLE0166 | CentraSiteObject type list is empty. |
Explanation |
You have not entered a CentraSiteObject type list. |
Action |
Enter a valid CentraSiteObject type list. |
INMCLE0167 | Invalid object {1} for object type {2}. |
Explanation |
The specified CentraSite object {1} does not belong to CentraSiteObject type {2}. |
Action |
Enter a valid CentraSite object of type {2}. |
INMCLE0168 | Caught an exception while trying to convert CentraSite objects. |
Explanation |
This is an unexpected exception. This is probably because an attempt is made to convert RegistryObjects to CentraSiteObjects, and vice versa. |
Action |
Check the stack trace for detailed information. |
INMCLE0169 | Invalid value set for {0}. Expected value : {1} Current value : {2}. |
Explanation |
The specified values for search condition does not match with the expected value. |
Action |
See the CentraSite online documentation’s section “Searching the CentraSite Catalog” for details. |
INMCLE0170 | Failed to verify if user {0} is watching asset {0}. |
Explanation |
Could not verify if the user {0} is watching the given asset. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0171 | Invalid operator set for {0}. Current operator: {1}. Supported operators for {2} type are {3}. |
Explanation |
The specified operator for search does not match with the attribute's applicable operators. |
Action |
See the CentraSite online documentation’s section “Searching the CentraSite Catalog” for details. |
INMCLE0172 | Failed to get existing lists. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0173 | List {0} does not exist. |
Explanation |
An attempt is made to pass the list {0} that is not available for the current user. |
Action |
Check to make sure that the list you pass for setExistingList(..) is available for the current user. |
INMCLE0174 | Wrong usage of Add to List action API. |
Explanation |
Incorrect usage of the Add to List action API. This problem occurs, when the '{0}' method is triggered with action in a state other than 'Show Available Lists'. |
Action |
Before you execute the {0} method, verify that the Add to List action is in 'Show Available Lists' state. |
INMCLE0175 | List to add selected assets is not set. |
Explanation |
List to add the selected set of assets is not set. Use the {0} method to set this list. |
Action |
Make sure that you use the {0} method to set the list to add selected assets. |
INMCLE0176 | Failed to execute {0}. |
Explanation |
{0} execution can fail for a number of reasons: (1) action is not allowed (2) action is not applicable at the time of execution (3) action is in 'Completed' state. |
Action |
Check for the above possible reasons and execute again. Else, contact the CentraSite administrator. |
INMCLE0177 | Failed to create a new list {0}. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0178 | Failed to add selected assets to the list. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0179 | Choose a document to attach to asset. |
Explanation |
The document to attach to the asset is not specified. |
Action |
Call the setDocument method before invoking the execute method in Attach Document action. |
INMCLE0180 | Failed to create {0} |
Explanation |
Failed to create resources or asset. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite administrator. |
INMCLE0182 | Data of type {0} is ignored. |
Explanation |
Data of the above type defined for a CSOParameter is not supported. |
Action |
Use the supported data types for CSOParameter. See the CentraSite online documentation’s section “Searching the CentraSite Catalog” for details. |
INMCLE0183 | Current CSOSearch has unresolved parameters: {0}. |
Explanation |
Current CSOSearch holds parameters that have a null value. |
Action |
Enter values for the unresolved parameters. |
INMCLE0184 | Number of parameters defined in CSOSearch differs from parameters defined for the XQuery module. |
Explanation |
Number of Parameters defined in the XQuery: {0} Number of Parameters defined in the CSOSearch: {1}. |
Action |
Validate your CSOSearch against the XQuery module. |
INMCLE0185 | Missing parameters |
Explanation |
The XQuery module used by the current CSOSearch requires {0} parameters. |
Action |
Validate the CSOSearch definition against the XQuery module that is being used. |
INMCLE0186 | Cannot find Xquery module {1} in namespace {0}. |
Explanation |
Could not find or load the XQuery module($0}:{1}) used by CSOSearch. |
Action |
Load the module / correct the CSOSearch definition. |
INMCLE0187 | No CentraSite object is available for Export action. |
Explanation |
You have not chosen the CentraSite objects for Export action. |
Action |
Choose the CentraSite objects for Export action. |
INMCLE0188 | Configuration base directory is not set. |
Explanation |
The configuration base directory specified by the path "com.softwareag.centrasite.api.configuration.basedir" is not set. |
Action |
Set the configuration base directory correctly. See the CentraSite online documentation for more details. |
INMCLE0189 | Type {0} not valid for Attach Document action. |
Explanation |
Could not perform the Attach Document action on selected type {0}. |
Action |
Enter a valid file. If the problem persists, contact the CentraSite administrator. |
INMCLE0190 | Failed to attach given document. |
Explanation |
Could not attach the given document, possibly because the document is invalid. |
Action |
Enter a valid document. |
INMCLE0191 | CentraSite object {0} does not belong to any of the given types {1}. |
Explanation |
The specified CentraSite object {0} does not belong to any of the given types {1}. Only objects that belong to the given types {1} are applicable for the Consume action. |
Action |
Choose a CentraSite object that belongs to one of the types {1}. |
INMCLE0192 | Could not choose consumer object in current state {0}. |
Explanation |
You cannot choose a consumer object in the current state {0}. The object should be in state {1}. |
Action |
Make sure that the consumer is in state {1}. Read the usage instructions of Consume action before use. |
INMCLE0193 | List of consumers is empty. |
Explanation |
An attempt is made to add an empty list of consumers for the Consume action. |
Action |
Choose a valid list of consumers. Read the usage instructions of Consume action before use. |
INMCLE0194 | Error: Timeout - The Document Processor Thread timed out waiting for the required inputs. |
Explanation |
You have not entered the required inputs within the time that the Document Processor was prepared to wait. |
Action |
Enter the required inputs as soon as prompted. |
INMCLE0195 | Failed to process missing resources, {0}. |
Explanation |
Could not process because the following resources are missing: {0}. |
Action |
Check to make sure that the required resources are specified. |
INMCLE0196 | Failed to initialize AttachDocumentProcessorThread. |
Explanation |
This is an internal error. The cause is not immediately known. |
Action |
Check to make sure that the mandatory inputs are specified. |
INMCLE0198 | Failed to attach given document(s), Reason : {0}. |
Explanation |
An exception occurred while trying to attach the document(s). This is probably because of the following reasons: 1) document is invalid 2) network failure. |
Action |
Check for the above possible reasons and execute again. If the problem persists, contact the CentraSite administrator. |
INMCLE0199 | Failed to get applicable reports for object {0}. |
Explanation |
An unexpected exception occurred while trying to get applicable reports for {0}. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0200 | Wrong usage of the View Report action API {0}. |
Explanation |
Incorrect usage of the View Report action API. This problem occurs, when the '{0}' method is triggered with action in a state other than '{1}'. |
Action |
Before you execute the '{0}' method, verify that the action is in '{1}' state. |
INMCLE0201 | Could not get selected report. |
Explanation |
Failed to get the selected report, possibly because the report is not implicitly set for retrieval. |
Action |
Use the 'setSelectedReport(..)' to set a report for this action. |
INMCLE0202 | Could not generate the selected report {0}. |
Explanation |
An unexpected exception occurred while trying to generate the selected report {0}. The cause is not immediately known. |
Action |
Check the log file for detailed information. |
INMCLE0203 | Failed to execute {0}. |
Explanation |
You do not have permission to perform this action. |
Action |
Before executing {0} make sure that you have the 'Use the Reports UI' permission. Contact your CentraSite administrator and if necessary request access and then try again. |
INMCLE0204 | Failed to close Centrasite ResourceAccessManager. |
Explanation |
Caught an exception while trying to close the ResourceAccessManager. This is a system error. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0205 | CentraSite cannot create a gateway because the gateway already exists. Gateway type: {0}, gateway name: {1}. Specify another name for the gateway. |
Explanation |
You are trying to create a gateway in CentraSite with an existing name and gateway type. |
Action |
Provide another name for the gateway and try the "set gateway" command again. |
INMCLE0206 | Failed to export {0}. |
Explanation |
Could not export the asset (s). This is probably because of the following reasons: 1) mandatory input is missing 2) prerequisite not satisfied. |
Action |
Check for the above possible reasons. If the problem persists, contact the CentraSite administrator. |
INMCLE0207 | Exception in Export Processor Thread |
Explanation |
Export Processor Thread caught an unhandled exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0208 | Specify mandatory {0}s for performing operation {1}. |
Explanation |
To perform this operation you should set the mandatory inputs. |
Action |
Check to make sure that the mandatory inputs are specified. |
INMCLE0209 | List to remove the selected assets is not set. |
Explanation |
The list to remove the selected assets is not set. Use the {0} method to set this list. |
Action |
Make sure that you use the {0} method to set the list to remove the selected assets. |
INMCLE0210 | Caught an unexpected exception when setting notification options for user {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0211 | Invalid file; specify a valid path to external file {0}. |
Explanation |
You have entered an invalid file path. |
Action |
Enter a valid file path. |
INMCLE0212 | Exception occurred when setting the specified email addresses for user {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0213 | Exception occurred when adding the specified telephone number for user {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0214 | Exception occurred when setting the specified name for user {0}. |
Explanation |
An unexpected exception occurred when trying to set one of the specified name (First Name, Middle Name or Last Name) for the user {0}. |
Action |
Check the stack trace for detailed information. |
INMCLE0215 | Parameter passed for {0} is null. |
Explanation |
An attempt is made to specify the mandatory parameter {0} with a null value. |
Action |
Check to make sure that the {0} has a valid value. |
INMCLE0216 | Exception occurred when trying to store the given profile picture in WEBDAV for user {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0217 | Exception occurred when trying to check for pending consumer registrations for user {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0218 | Exception occurred when trying to get Approval Request Reason for {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0219 | Exception occurred when trying to get Approval Workflow Name for {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0220 | {0} is triggered for consumer registration approval / rejection process; accessing {1} is invalid. |
Explanation |
The {0} is triggered for consumer registration approval / rejection; accessing {1} is not valid. |
Action |
Accessing the {1} method for this kind of {0} is not valid. Ensure that you do not call this method here. |
INMCLE0221 | Could not create/update a gateway because the gateway type is not specified. Specify the gateway type and try again. |
Explanation |
The gateway type attribute is required to identify a gateway along with the gateway name. You have not specified the gateway type for the "set gateway" command in CentraSite. |
Action |
Specify the gateway type along with the name and other mandatory parameters, and try the "set gateway" command again. |
INMCLE0222 | Exception occurred when trying to get Consumer Registration Requestor for {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0223 | Exception occurred when trying to get profile picture for user {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0224 | Exception occurred when getting the notification options for user {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0225 | Error loading predefined notification concepts |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. If the problem persists, contact the CentraSite administrator. |
INMCLE0226 | Invalid phone type {0}. |
Explanation |
You have entered an invalid phone type. The phone type should match one of the predefined types. |
Action |
Refer to CLL API documentation for details on predefined phone types. |
INMCLE0228 | Invalid name {0}. |
Explanation |
You have entered an invalid name. |
Action |
Enter a valid name without special characters. |
INMCLE0229 | CentraSite could not create the gateway. You might not have permission to create a Mediator gateway. |
Explanation |
User is not authorized to create a Mediator gateway in CentraSite. |
Action |
Contact your CentraSite administrator. |
INMCLE0230 | Failed to create {0} for given URI {1}. |
Explanation |
Failed to create a {0} for the given URI {1}, possibly because the Save operation is applicable only for WebDav resources. |
Action |
Save is applicable only for WebDaV resources. |
INMCLE0231 | Failed to get content type for given URI {0}. |
Explanation |
Failed to get content type for given URI {0}, possibly because the content type could not find the external URI. |
Action |
Failed to get content type for given URI {0}, possibly because the content type could not find the external URI. |
INMCLE0232 | Unable to fetch folders from external URL {0}. |
Explanation |
Could not get folders from an external URL, because this operation is only supported for a WebDaV URL. |
Action |
Enter a valid WebDav URL. |
INMCLE0233 | Unable to fetch files from external URL {0}. |
Explanation |
Could not fetch files from an external URL, because this operation is only supported for a WebDav URL. |
Action |
Enter a valid a WebDav URL. |
INMCLE0234 | Failed to read XQuery from file {0}. |
Explanation |
Could not read the XQuery from file, possibly because the file does not exist. |
Action |
Enter a valid file path. |
INMCLE0235 | Parameter passed to the method {0} is null. |
Explanation |
The parameter passed to the method {0} is null. |
Action |
Pass a valid parameter to the method {0}. |
INMCLE0236 | Invalid values for keyword condition |
Explanation |
Keyword condition takes only one string value as input. The value should be put in the collection and then set to keyword condition. |
Action |
Check to make sure that valid values are set as input to the keyword condition. |
INMCLE0237 | Failed to get TransformedContent {0}. |
Explanation |
Failed to get the TransformedContent, possibly because of a connection failure. |
Action |
Check the network connection. If the problem persists, contact CentraSite administrator. |
INMCLE0240 | {0} cannot be reset. |
Explanation |
An attempt is made to reset the {0} that already has a value specified and that is read-only. |
Action |
{0} is read-only. |
INMCLE0241 | Exception occured while trying to get the webdav location of computed profile template. |
Explanation |
An unexpected exception occurred while trying to get the webdav location of computed profile template, possibly because the template does not exist. |
Action |
Check to make sure that the uploaded archive contains the computed profile template. |
INMCLE0242 | Exception occured while loading the implementation class of computed profile. |
Explanation |
An unexpected exception occurred while loading the implementation class of computed profile, possibly because the class does not exist. |
Action |
Check to make sure that the uploaded archive contains the implementation class. |
INMCLE0243 | Database access is denied. |
Explanation |
Access to the database is denied. |
Action |
Login again. |
INMCLE0244 | Exception while trying to retrieve the computed profile data. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Make sure that the getProfileDataAsJson() implementation is correct. |
INMCLE0245 | Exception while trying to compute the profile data. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Make sure that the computeProfileData implementation is correct. |
INMCLE0246 | Required input is missing. |
Explanation |
The required input is missing. |
Action |
Enter a valid input. |
INMCLE0247 | Error loading profile data. |
Explanation |
An unexpected error occurred while trying to load the profile data, possibly because of the following reasons: {0}. |
Action |
Check for the above possible reasons. If the problem persists, contact the CentraSite administrator. |
INMCLE0248 | Search cannot be saved. |
Explanation |
The current search contains validation errors. |
Action |
Correct the validation errors and try again. |
INMCLE0249 | Error establishing a database connection. |
Explanation |
Unable to connect the database, possibly because the database server is down. |
Action |
Start the database server. |
INMCLE0250 | Failed to convert the given duration {0} to date. |
Explanation |
Exception occurred while trying to convert the given duration to date; possibly because the duration string is invalid. |
Action |
Enter a valid duration. |
INMCLE0251 | Failed to covert the given string {0} to date. |
Explanation |
Exception occurred while trying to convert the given string to date; possibly because the string is invalid. |
Action |
Check to make sure that the string is valid and it supports the date format like "E MMM dd HH:mm:ss Z yyyy". |
INMCLE0252 | Failed to create a new {0}. |
Explanation |
The {0} could not be created; possibly because the inputs were invalid. |
Action |
Make sure the inputs are valid. |
INMCLE0253 | Failed to save an asset with the given permissions. |
Explanation |
Failed to save an asset with the given permissions; possibly because the asset is unlocked. |
Action |
Make sure the asset is locked and available for editing. |
INMCLE0254 | Exception fetching the asset's instace-level and profile-level permissions. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Contact your system administrator if the problem persists. |
INMCLE0255 | Display Interval {0} is invalid. |
Explanation |
Specify the time interval how frequently you want to collect metrics for the service. The expected format is 3m 2d 6h; where m indicates the month, d indicates the day and h indicates the hour. |
Action |
Check to make sure that the time interval is specified in exactly the above format. |
INMCLE0256 | Exception {0} occurred while trying to fetch the list of targets. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Check the exception stack trace information. |
INMCLE0257 | Target {0} is not active. |
Explanation |
The target {0} is not active. The cause is not immediately known. |
Action |
Check the stack trace information for details. |
INMCLE0258 | Failed to deploy asset {0} on gateway {1}. |
Explanation |
Could not deploy the asset {0} on the specified gateway {1}. Possible reason: {2} |
Action |
Check the stack trace information for details. |
INMCLE0259 | Unable to fetch policy with UUID '{0}'. |
Explanation |
Could not fetch policies with the given UUID '{0}'; possibly because of the following reasons: 1. A policy with a UUID '{0}' does not exist. 2. Logged in user does not have the required permission on policy. |
Action |
Ensure that at least one policy exists with the given UUID and the logged in user has the required permissions on the policy. |
INMCLE0260 | Unable to fetch policies with name pattern '{0}'. |
Explanation |
Could not fetch policies with the given name pattern '{0}'; possibly because of the following reasons: 1. A policy with a name pattern '{0}' does not exist. 2. Logged in user does not have the required permission on policy. |
Action |
Ensure that at least one policy exists with the given name pattern and the logged in user has the required permissions on the policy. |
INMCLE0261 | The policy action template is invalid. |
Explanation |
Invalid action template; possibly because one or more vital parameters are null or not available. |
Action |
Enter valid parameters for the action template. |
INMCLE0262 | Unable to fetch policy actions with UUID '{0}'. |
Explanation |
Could not fetch policy actions with the given UUID '{0}'; possibly because of the following reasons: 1. A policy action with a UUID '{0}' does not exist. 2. Logged in user does not have the required permission on action. |
Action |
Ensure that at least one policy action exists with the given UUID and the logged in user has the required permissions on the action. |
INMCLE0263 | Unable to fetch policy actions with name pattern '{0}'. |
Explanation |
Could not fetch policy actions with the given name pattern '{0}'; possibly because of the following reasons: 1. A policy action with a name pattern '{0}' does not exist. 2. Logged in user does not have the required permission on policy action. |
Action |
Ensure that at least one policy action exists with the given name pattern and the logged in user has the required permissions on the policy action. |
INMCLE0264 | Unable to fetch {0}. |
Explanation |
Could not fetch the {0}. The cause is not immediately known. |
Action |
Check the exception stack trace information. |
INMCLE0266 | Failed to identify the consumers for the asset {0}. |
Explanation |
Could not identify the consumers for the given asset {0} |
Action |
This is an internal error. If the problem persists, contact the system administrator. |
INMCLE0267 | Failed to identify the targets to which the asset {0} is deployed. |
Explanation |
Exception occurred when populating the targets to which the asset {0} is deployed. |
Action |
This is an internal error. If the problem persists, consult the system administrator. |
INMCLE0268 | Failed to identify the events for the given search filter. |
Explanation |
Exception occurred when populating events for the given search filter. |
Action |
This is an internal error. If the problem persists, consult the system administrator. |
INMCLE0269 | Failed to revoke profile permissions. |
Explanation |
Caught an exception when trying to revoke the profile permissions. |
Action |
This is an internal error. If the problem persists, consult the system administrator. |
INMCLE0270 | Failed to set profile permissions. |
Explanation |
Caught an exception when trying to set the profile permissions. |
Action |
This is an internal error. If the problem persists, consult the system administrator. |
INMCLE0271 |
INMCLE0272 | Error obtaining the classifications for object {0}. |
Explanation |
Caught an unexpected exception occurred while trying to obtain the classifications of object {0} and which prevented the application from proceeding further. |
Action |
Check the stack trace information for details. |
INMCLE0273 | Missing attribute in virtualization. |
Explanation |
Mandatory attribute (Virtual Alias or Endpoint) is missing. Virtual Alias and Endpoint attributes are mandatory for virtualizing an API. |
Action |
Set the Virtual Alias and Endpoint attributes. |
INMCLE0274 | Invalid Display Interval {0}. |
Explanation |
The display interval specified is invalid. |
Action |
Specify a valid interval (ex. 1m 1d 1h) and try again. |
INMCLE0275 | Failed to configure the API Key. |
Explanation |
Could not configure the API Key for the given asset; possibly because of missing parameters. |
Action |
Check to make sure all the required parameters are set. |
INMCLE0276 | Failed to load approval groups from the CentraSite registry. |
Explanation |
One or more approval groups could not be loaded from the CentraSite registry. |
Action |
Make sure that an approval group exists and try again. |
INMCLE0277 | Error checking permissions or validity over objects. |
Explanation |
Could not check permissions or validity over the specified objects. |
Action |
Verify the user and asset type are valid in the CentraSite registry. |
INMCLE0278 | Failed to check if the current user has Manage Organizations permission. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0279 | Unable to delete/remove the selected {0} {1} |
Explanation |
You cannot delete the {0} {1}, because you do not have the required permission to delete/remove the {0}. |
Action |
Verify that you have the required permission to delete/remove the {0}. Contact your administrator, request permission if necessary and try again. |
INMCLE0280 | Unable to delete the selected user {0}. |
Explanation |
{1}. A user cannot be deleted if the user owns/modifies object(s), or if the user has any pending actions or if the user is the sole administrator for an organization. Also, if the user modified some object, and the corresponding audit trail entry is still present, deletion is rejected.{0} - The user that was attempted to be deleted. |
Action |
Delete all of the objects owned by the user, complete all pending actions, ensure another user is appointed as administrator for the corresponding organization and after all modification audit trail entries are purged (if any), user deletion will be allowed. |
INMCLE0281 | Unable to delete the selected group {0} |
Explanation |
{1}. You cannot delete the selected group either because you do not have the required permission or the group is associated with another object which creates a dependency to the group. |
Action |
Verify that you have the required permission to delete the user. Ensure that the group does not have any associations to other objects and try deleting the associations (if any) before attempting to delete the group again. |
INMCLE0282 | Unable to delete the selected role {0} |
Explanation |
{1}. You cannot delete the selected role either because you do not have the required permission, or the role is a pre-defined system role which cannot be deleted, or the role is associated with another object which is dependent on it. |
Action |
Verify that you have the required permission to delete the role. Ensure that you are not attempting to delete a pre-defined role. |
INMCLE0283 | Unable to delete the selected Child Organization |
Explanation |
{0}. You cannot delete the selected Child Organization either because you do not have the required permission, or the organization has policies which are active, or other objects are associated with the organization. |
Action |
Verify that you have the required permission to delete the Child Organization. Ensure that organization dependencies are resolved before attempting to delete again. |
INMCLE0284 | Unable to delete/modify the selected group {0} |
Explanation |
You cannot modify the users of/delete pre-defined groups of CentraSite such as "Users" and "Members". Since the group {0} is a pre-defined object, the deletion/modification of the group has been rejected. |
Action |
Ensure that the group that you are trying to delete/modify is not a pre-defined object. |
INMCLE0285 | Unable to delete the selected role {0} |
Explanation |
You cannot delete the OrganizationAdministrator role of an organization. This is because this role indicates the Administrator(s) of an organization. |
Action |
Ensure that the role you are trying to delete is not that of the OrganizationAdministrator. |
INMCLE0286 | Caught an Exception while creating the VSProcessingStepsAdapter instance |
Explanation |
This is an internal error. It is probably because of an invalid connection. |
Action |
Verify that the user session is valid. |
INMCLE0287 | Invalid Native service. |
Explanation |
This is an internal error. It is probably because the native service Registry Object is null. |
Action |
Verify that the native service is valid. |
INMCLE0288 | Unable to virtualize the native service. Reason: {0} |
Explanation |
This is an internal error within the virtualization of a service |
Action |
Check your native service and the policies to be used |
INMCLE0289 | Cannot Construct MessageFlow from VirtualService. |
Explanation |
This is an internal error. It is probably because of an invalid VirtualService. |
Action |
Verify that the VirtualService is valid. |
INMCLE0290 | Invalid Virtual service. |
Explanation |
This is an internal error. It is probably because the virtual service Registry Object is null. |
Action |
Verify that the virtual service is valid. |
INMCLE0291 | Falied to edit the VirtualService . |
Explanation |
Cannot edit the VirtualService. It is probably because of an invalid MessageFlow. |
Action |
Verify the MessageFlow for the virtual service. |
INMCLE0292 | Caught an Exception while creating Default StraightThrough routing for the Virtual Service |
Explanation |
This is an internal error. It is probably because of an invalid route-to. |
Action |
Verify the endpoints for the virtualization |
INMCLE0293 | Caught an Exception while creating Default Routing Endpoints for the Virtual Service. |
Explanation |
This is an internal error. It is probably because of an invalid route-to. |
Action |
Verify the endpoint properties for the virtualization. |
INMCLE0294 | Cannot build Processing steps with Empty MessageFlow. |
Explanation |
This is an internal error. It is because the MessageFlow is empty. |
Action |
Verify the MessageFlow for the virtual service. |
INMCLE0295 | Caught an Exception while building Processing steps for the VirtualService. |
Explanation |
This is an internal error. It is probably because of an invalid MessageFlow. |
Action |
Verify that the MessageFlow is valid. |
INMCLE0296 | Cannot add the PolicyActionInstance with templateId {0} to Routing Step |
Explanation |
This probably occurs because the PolicyActionInstance does not belong to the routing step. |
Action |
Verify that the PolicyActionInstance is valid. |
INMCLE0297 | Cannot add empty Default StraightThrough routing and empty Default Routing Endpoints for a Virtual Service. |
Explanation |
Default routing and endpoint properties are mandatory for a virtual service and cannot be deleted. |
Action |
Verify that the default routing and endpoint properties are not deleted. |
INMCLE0298 | Cannot add the PolicyActionInstance with templateId {0} to Enforce Step. |
Explanation |
This probably occurs because the policy action instance does not belong to the enforce step. |
Action |
Verify that the policy action instance is valid. |
INMCLE0299 | Virtualization is not supported for type {0} |
Explanation |
The asset passed to the virtualization action is not supported for virtualization. |
Action |
Verify that the asset is suitable for virtualization. |
INMCLE0300 | Unable to delete the selected asset. |
Explanation |
{0}. You cannot delete the selected asset either because you do not have the required permission or the asset has dependencies/associations with other objects (Example: pending approval of assets). |
Action |
Verify that you have the required permission to delete the asset. Also delete all dependencies with the asset and then attempt the deletion again. |
INMCLE0301 | Unable to remove the selected role(s) for the user {0} |
Explanation |
{1} Removal of role(s) for the user may have failed if you are trying to delete role(s) inherited through group membership, or if there are dependencies/associations between the objects. |
Action |
Ensure that all dependencies are resolved, and do not attempt to delete roles inherited through group memberships. |
INMCLE0302 | Unable to remove the selected role(s) for the group {0} |
Explanation |
{1}. Removal of role(s) from the group may have failed if a role has dependencies/associations and hence the role removal for the group may fail. |
Action |
Ensure that the roles do not have any dependencies and then try again. |
INMCLE0303 | Unable to remove the group membership {0} for the user |
Explanation |
{1}. You may not be able to remove a user's group membership if the user has dependencies/associations with the group (example: due to an approval policy). In such cases, membership removal for a user will be rejected. |
Action |
Ensure that all dependencies are resolved between the user and the group, then try again. |
INMCLE0304 | Unable to retrieve {0} of a {1} |
Explanation |
{2}. The retrieval may have failed because you do not have required permission, or due to database access error. |
Action |
Verify that you have required permissions and also ensure that the database is running, then try again. |
INMCLE0305 | Failed to instantiate class {0} |
Explanation |
Could not instantiate the given class {0}, possibly because of the following reasons: 1) class file does not exist 2) classpath is incorrect. |
Action |
Check for the above possible reasons. If the problem persists, contact the CentraSite administrator. |
INMCLE0306 | Failed to check User {0} has Role {1} |
Explanation |
An exception occurred while checking the role {1} for the user {0}. |
Action |
This is an internal error. Please contact the system administrator. |
INMCLE0307 | Invalid Super User |
Explanation |
The given super user configuration in CentraSite web.xml is invalid. |
Action |
Please provide a valid super user ID for the com.softwareag.centrasite.service.privilege.user.id Init-Param property under CentraSite web.xml. |
INMCLE0308 | Invalid Super User Role |
Explanation |
The super user configured under CentraSite web.xml does not have the required role to perform the privileged service. |
Action |
Please assign the CentraSite Administrator role for the super user or provide a user ID that has the CentraSite Administrator role. |
INMCLE0309 | Invalid Calling User Role |
Explanation |
The calling user does not have the appropriate role to execute a privileged service. |
Action |
Please assign an appropriate role to the user in order to perform the privileged service. |
INMCLE0310 | API Key settings cannot be updated or deleted |
Explanation |
A policy related to API Key settings is in the pending state, hence the settings cannot be updated. |
Action |
Ask the approvers to process the pending approval request pertaining to this asset. |
INMCLE0311 | Cannot find a category for the policy. |
Explanation |
This is an internal error. The category type cannot be found. |
Action |
Please verify the message flow. |
INMCLE0312 | Caught an Exception while retrieving Default StraightThrough routing endpoint for the Virtual Service |
Explanation |
This is an internal error. It is probably because of an invalid route-to. |
Action |
Verify the endpoints for the virtualization |
INMCLE0313 | Caught an Exception while creating Default HTTP Authentication for the Virtual Service. |
Explanation |
This is an internal error. It is probably because of an invalid policy instance. |
Action |
Verify the policy instance. |
INMCLE0314 | Unable to create/edit the selected {0}. |
Explanation |
You cannot create the {0} {1}, because you do not have the required permission to create/edit the {0}. |
Action |
Verify that you have the required permission to create/edit the {0}. Contact your administrator, request permission if necessary and try again. |
INMCLE0315 | Unable to modify the selected group {0} |
Explanation |
Since the group you are trying to modify is associated with an external repository, you will not be able to modify the external group. |
Action |
Ensure that the group that you are trying to modify is not an external group. |
INMCLE0316 | Unable to remove the selected role |
Explanation |
The logged in user and the user for whom roles are attempted to be removed are the same. This is not allowed. |
Action |
Please make sure that you are not trying to remove roles assigned to you. It can only be done by the CentraSite Administrator or your Organization Administrator. |
INMCLE0317 | Failed to find the alias which exists with the given name {0} |
Explanation |
An exception occurred while trying to find the asset which already exists with the given name {0}. |
Action |
Please make sure the given asset name does not have any special characters. |
INMCLE0319 | Email address already registered in CentraSite |
Explanation |
This email address is already registered to a user in CentraSite. |
Action |
Enter a different email address. |
INMCLE0320 | Please wait while we process your registration. |
Explanation |
User registration with the given email address is being processed by the administrator. |
Action |
Please wait while we process your registration. |
INMCLE0321 | Configure parameters for the New Account Registration policy |
Explanation |
The parameters required for the New Account Registration Policy are missing. |
Action |
Configure parameters (such as, Approver Group, Approval Mode) for the New Account Registration policy. |
INMCLE0322 | Failed to publish the asset |
Explanation |
Unable to publish the asset; possibly because of an incorrect attribute. |
Action |
Check to make sure that the specified input parameters are correct. |
INMCLE0323 | Failed to get the publish progress |
Explanation |
An exception occurred while getting the publish progress information. |
Action |
Please make sure that the request end point, request and header parameters are correct. |
INMCLE0324 | Failed to get the publish failed targets |
Explanation |
An exception occurred while getting the deployment failed targets information. |
Action |
Please make sure that the request end point, request and header parameters are correct |
INMCLE0325 | Failed to cancel publish operation |
Explanation |
An exception occurred while canceling the publish operation. |
Action |
Please make sure that the request end point, request and header parameters are correct. |
INMCLE0326 | Privileged user credentials are not configured. |
Explanation |
The expected privileged user credentials are not configured in {0}. |
Action |
Check to make sure that the privilege user credentials are configured in {0}. |
INMCLE0327 | Required roles to perform the publish are missing |
Explanation |
One or more roles that are required to perform the publish are missing. |
Action |
Please contact the administrator to add roles required to perform the publish. |
INMCLE0328 | Aliases or Targets input is empty |
Explanation |
The publish request does not contains aliases or tagets information. |
Action |
Please make the you have provided the aliases and targets required to perform the publish operation. |
INMCLE0329 | You do not have sufficient permissions to execute {0}. |
Explanation |
You do not have sufficient permissions to execute {0}. |
Action |
Verify that you have the "Manage Organizations" permission. Contact your administrator and request permission if necessary and then try again. |
INMCLE0330 | Unauthorized: Access is denied. |
Explanation |
Access to the service is denied possibly because of insufficient permissions. |
Action |
Check to make sure that you have the required permissions for accessing the service. |
INMCLE0331 | Forbidden: Access is denied. |
Explanation |
Request is forbidden at the moment; possibly because the API key is pending for a renewal request. |
Action |
Kindly retry after sometime. |
INMCLE0332 | Required policies to execute the API key renewal and/or revocation are not found. |
Explanation |
Could not process the renewal and/or revocation requests for the API key; possibly because the requried policies are not found. |
Action |
Check to make sure that the API key settings are configured for renewal and/or reovcation. If the problem persists, contact your system administrator. |
INMCLE0333 | The Message Flow stage {0} that includes the action {1} must include at least one of the following dependent actions: Require Signing, Require Encryption, Require SLL, Require WSS X.509 Token. |
Explanation |
This action {1} depends on the following actions: Require Signing, Require Encryption, Require SLL, Require WSS X.509 Token. |
Action |
Choose at least one of the dependent actions for {1}. |
INMCLE0339 | The Message Flow stage {0} that includes the action {1} must also include {2} of the following dependent action(s): {3}. |
Explanation |
This action {1} mandate that at least one of the dependent actions {3} be included in the message flow. |
Action |
Choose at least one of the dependent actions for {1}. |
INMCLE0340 | Required field is missing |
Explanation |
Required field {0} for the policy action {1} cannot be empty. |
Action |
Enter a value for the required field {0}. |
INMCLE0341 | No action is defined for policy. |
Explanation |
The Message Flow area in the indicated policy does not contain any actions. |
Action |
Add one or more actions to the Message Flow area in the indicated policy. |
INMCLE0342 | Value set of Message Flow is null. |
Explanation |
Value returned by Message Flow is null. |
Action |
Set a value for the Message Flow. |
INMCLE0343 | {0} attribute not valid. |
Explanation |
The specified attribute {0} is not a valid policy constraint. |
Action |
Specify a valid attribute. |
INMCLE0344 | One or more dependent actions or action parameters are not configured. |
Explanation |
There are no dependent actions or action parameters configured for the Message Flow. |
Action |
Configure the dependent actions and action parameters in the Message Flow area. |
INMCLE0345 | Failed to change lifecycle state of {0}. |
Explanation |
Could not change lifecycle state of this {0}, possibly because it has been implicitly locked by the server for an ongoing modification. |
Action |
Please try after some time. |
INMCLE0346 | Failed to change lifecycle state of {0}. |
Explanation |
Could not change lifecycle of this {0}, possibly because you do not have the required permissions. |
Action |
Check to make sure that you have the required permissions to change state of this{0}. |
INMCLE0347 | Failed to delete {0}. |
Explanation |
Could not delete this {0}, possibly because you do not have the required permissions. |
Action |
Check to make sure that you have the required permissions to delete this {0}. |
INMCLE0348 | Failed to delete {0}. |
Explanation |
Could not delete this {0}, possibly because it has been implicitly locked by the server for an ongoing modification. |
Action |
Please try after some time. |
INMCLE0349 | CentraSite could not create the runtime alias. {0} |
Class | Error |
Explanation |
Error while creating a runtime alias in CentraSite. |
Action |
Check if a runtime alias with the same name already exists and if the parameters specified for the runtime alias are correct. |
INMCLE0350 | CentraSite failed to publish the runtime alias to targets. {0} |
Class | Error |
Explanation |
Error while publishing runtime alias from CentraSite to target(s). |
Action |
Check the log file for more information. |
INMCLE0351 | {0} action failed because the required objects {1} are not set. |
Explanation |
Action {0} requires that the objects be set before it can execute. |
Action |
Ensure that the required objects {1} are set accordingly for the action. |
INMCLE0352 | You must select valid objects for publishing/unpublishing to/from API Portals. |
Explanation |
One or more of the selected registry objects cannot be published/unpublished to/from the specified API Portals. This is possibly because, one or more of the selected objects does not belong to the asset type "Service" or its variants. |
Action |
Make sure that the objects selected for publishing/unpublishing are of the asset type "Service" or any of its variants. |
INMCLE0353 | {0} ERROR: Could not publish/unpublish APIs to API Portals. |
Explanation |
An error {0} occurred while trying to publish/unpublish APIs to/from API Portals, possibly because one or more of the API Portal servers were unavailable. |
Action |
Make sure the API Portal servers are up and running. If the problem persists, contact your administrator. |
INMCLE0354 | Category {0} does not belong to the taxonomy "Sandbox". |
Explanation |
An attempt was made to classify an endpoint with the taxonomy "Sandbox", but the specified category {0} does not exist in the taxonomy "Sandbox". |
Action |
Make sure the category exists in the taxonomy "Sandbox". |
INMCLE0355 | Failed to publish asset {0} to target. |
Explanation |
Could not publish the specified asset {0} to the target, possibly because the specified asset is under the control of a lifecycle model (LCM), and is in a non-deployable state. |
Action |
Make sure you switch the asset to an active, ready-to-deploy state, before trying to publish asset to the target. |
INMCLE0356 | Error while deploying runtime aliases. {0} |
Class | Error |
Explanation |
CentraSite could not deploy runtime aliases. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0357 | Error while undeploying runtime aliases. {0} |
Class | Error |
Explanation |
CentraSite cannot undeploy runtime aliases. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0358 | Could not get information from API Portal {0}, because of invalid user credentials. |
Explanation |
An error occurred while getting an information from the specified API Portal {0}, possibly because of invalid username and/or password. |
Action |
Enter a valid username and/or password, and then try again. |
INMCLE0359 | Could not get information from API Portal {0}. |
Explanation |
An error occurred while getting an information from the specified API Portal {0}. There could be multiple reasons why this might have occurred: (1) API Portal server is down or inaccessible (2) invalid user credentials (3) application error on the CentraSite or API Portal server. |
Action |
Make sure the API Portal server is up and running, and the user credentials are correct. |
INMCLE0360 | The API is published successfully but cannot be associated with API Portal. |
Explanation |
The API was successfully published to the API Portal server, but could not be associated with it. This could be caused by an application error. |
Action |
Make sure the API Portal server is up and running. If the problem persists, contact your administrator. |
INMCLE0361 | The API is unpublished successfully, but existing association with API Portal cannot be revoked. |
Explanation |
The API was successfully unpublished from the API Portal server, but its existing association with API Portal could not be revoked. This could be caused by an application error. |
Action |
Make sure the API Portal server is up and running. If the problem persists, contact your administrator. |
INMCLE0362 | Could not find API id {0} in the CentraSite registry. |
Explanation |
An attempt was made to publish or unpublish the specified API which is not found in the CentraSite registry. |
Action |
Verify the API id is correct. If the API id is correct and the error persists, contact your administrator. |
INMCLE0363 | Could not find API Portal id {0} in the CentraSite registry. |
Explanation |
An attempt was made to publish or unpublish an API to the specified API Portal which is not found in the CentraSite registry. |
Action |
Verify the API Portal id is correct. If the API Portal id is correct and the error persists, contact your administrator. |
INMCLE0364 | Could not find status id {0} of the publish/unpublish action in the CentraSite registry. |
Explanation |
The publish or unpublish status could not be determined. The identifier used to get the status of the action is no longer valid, possibly because the action has already been completed. |
Action |
Verify the status id is correct. If the status id is correct and the error persists, contact your administrator. |
INMCLE0365 | Database access error. Could not connect to the CentraSite Registry Repository. |
Explanation |
The CentraSite Registry Repository is unavailable. |
Action |
Restart the Software AG CentraSite Registry Repository and Software AG Runtime. If the problem persists, contact your administrator. |
INMCLE0366 | One or more of the selected resources have HTTP methods that are not supported for virtualization. |
Explanation |
Resources with GET, POST, PUT, PATCH and DELETE methods are only allowed for virtualization. The following resource(s) have been found to have unsupported HTTP methods: {0} |
Action |
Select the resources that have supported HTTP methods. |
INMCLE0367 | Could not set attribute {0} of the REST/XML service. |
Explanation |
{1}: An error occurred while trying to set the attribute {0} of the REST/XML service. There could be multiple reasons why this might have occurred: (1) insufficient permissions (2) transaction timeouts (3) trying to modify an outdated service (4) invalid value for the attribute. |
Action |
Ensure that you have sufficient permissions to modify the service. If the underlying error is a transaction timeout or an outdated service, try setting the attribute again. |
INMCLE0368 | Could not save the web service "{0}". |
Explanation |
{1}: An error occurred while trying to save the specified REST/XML service {0}. There could be multiple reasons why this might have occurred: (1) insufficient permissions (2) transaction timeouts (3) trying to modify an outdated service (4) invalid property values for the service (5) a policy denies the save. |
Action |
Ensure that you have sufficient permissions to modify and save the service. Check for enabled policies denying the save. If the underlying error is a transaction timeout or an outdated service, try saving the service again. |
INMCLE0369 | Failed to virtualize web service. |
Explanation |
Could not virtualize the web service, possibly because the specified service doesn't reference any WSDL:binding element. |
Action |
Make sure that the WSDL contains a binding element. |
INMCLE0370 | Failed to register CentraSite in the following API Portals: {0} |
Explanation |
An error occurred while registering CentraSite in the indicated API Portals {0}. There could be multiple reasons why this might have occurred: (1) API Portal server is down or inaccessible (2) invalid user credentials (3) application error on the API Portal server. |
Action |
Make sure the API Portal server is up and running, and the user credentials are correct. |
INMCLE0371 | Failed to delete the API {0}. |
Explanation |
The selected API {0} cannot be deleted, because it is published to one or more API Portals. |
Action |
To delete the selected API first unpublish it from all the API Portals and then try again. |
INMCLE0372 | An unexpected error occurred while communicating with API Portal {0} (HTTP status code {1}). |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Contact your system administrator with exception stack trace information present in the error log. |
INMCLE0373 | Trying to access a resource {0} in API Portal {1} is forbidden. |
Explanation |
A HTTP 403 error occurred while trying to access the resource {0} in API Portal {1} , possibly because you do not have sufficient access rights to access the specified resource in API Portal. |
Action |
Verify that you have the appropriate access rights. Contact your administrator and request access if necessary and then try again. |
INMCLE0374 | Resource {0} is not found in API Portal {1}. |
Explanation |
A HTTP 404 error occurred while trying to access the resource {0} in API Portal {1}. There could be multiple reasons why this might have occurred: (1) API Portal server is down or inaccessible (2) invalid resource endpoint. |
Action |
Make sure the API Portal server is up and running, and the resource endpoint is correct. If the problem persists, contact your administrator. |
INMCLE0375 | Technical error encountered in API Portal {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
Contact your system administrator with exception stack trace information present in the error log. |
INMCLE0376 | An error occurred while creating a gateway in CentraSite. |
Explanation |
One or more gateway configuration parameters are null. |
Action |
Specify the mandatory gateway parameters, and try again. |
INMCLE0377 | An error occurred while creating a gateway in CentraSite. {0} |
Explanation |
An error occurred while creating a gateway in CentraSite. Check the CentraSite logs for details. |
Action |
Fix the error(s) and retry the "set gateway" command. If the issue persists, contact Software AG support with the log information. |
INMCLE0379 | Unable to find a gateway in CentraSite with the ID, "{0}". |
Explanation |
A gateway with the specified identifier does not exist in CentraSite. |
Action |
Specify a valid gateway ID, and try again. |
INMCLE0380 | CentraSite cannot retrieve the gateway details because the mandatory attribute, gateway ID is not available. |
Explanation |
Gateway ID for the gateway is not available in CentraSite. |
Action |
Check if the gateway ID set in CentraSite is valid. |
INMCLE0381 | CentraSite could not delete the gateway because the gateway ID is not specified. |
Explanation |
The mandatory gateway ID parameter is not specified for the "remove gateway" command in CentraSite. |
Action |
Specify the gateway ID parameter and try and command again. |
INMCLE0382 | CentraSite could not create/update a gateway because a mandatory attribute for the command is not specified. Attribute not specified: {0}, gateway: {1} |
Explanation |
A mandatory attribute is not specified for the set gateway command in CentraSite. |
Action |
Specify the mandatory parameter and try the "set gateway" command again. |
INMCLE0383 | Error in synchronizing consumers with Mediator gateway. |
Explanation |
An error occurred while synchronizing consumers with the Mediator gateway. There could be multiple reasons why this might have occurred: (1) Mediator is down or inaccessible. (2) At least one consumer application is not available for synchronizing. |
Action |
Make sure that Mediator is up and running, and at least one consumer application is available for synchronizing with the gateway. |
INMCLE0384 | You do not have permission in CentraSite to publish/unpublish the API Portal, {0}. |
Explanation |
To perform publish/unpublish operation on an API Portal, you must have either API Portal Administrator role or the modify permission on the selected API Portal(s). |
Action |
Contact the CentraSite administrator to add roles/permissions required to perform the publish or unpublish APIs. |
INMCLE0385 | Error publishing CentraSite communication details to Mediator. |
Explanation |
CentraSite cannot publish communication details to Mediator. Possible reasons could be: (1) Mediator is down or inaccessible (2) invalid user credentials or (3) Error in Mediator when you publish information from CentraSite to Mediator. |
Action |
Check Mediator and CentraSite log files and take corrective actions. |
INMCLE0386 | Could not publish CentraSite Communication Details to Mediator. |
Explanation |
An error occurred while trying to publish CentraSite Communication Details to Mediator. There could be multiple reasons why this might have occurred: (1) Integration Server on which Mediator is running is down or inaccessible (2) invalid user credentials (3) application error on the CentraSite server or Integration Server. |
Action |
Make sure the Integration Server is up and running, and the user credentials are correct. If the problem persists, contact your administrator. |
INMCLE0387 | Could not deploy 'CentraSite Communication Details' to Mediator due to HTTP connection failure. |
Explanation |
Failure of HTTP connection between CentraSite and Mediator. |
Action |
Check if the Mediator credentials and endpoint URL specified are valid and try again. |
INMCLE0388 | Mediator endpoint URL format is not correct. Format: <PROTOCOL>://<HOSTNAME>:<PORT>or <PROTOCOL>://<HOSTNAME> |
Explanation |
The Mediator endpoint URL should be specified in one of the following formats:(1) <PROTOCOL>://<HOSTNAME>:<PORT>(2) <PROTOCOL>://<HOSTNAME> |
Action |
Enter the Mediator endpoint URL in the correct format and try again. |
INMCLE0389 | Could not unpublish instances of API Portal. |
Explanation |
An error occurred while unpublishing the selected instances of API Portal. There could be multiple reasons why this might have occurred: (1) API Portal server was down or inaccessible (2) instances of API Portal was successfully unpublished, but its existing association with published APIs and access tokens could not be revoked, possibly because of an application error. |
Action |
Make sure the API Portal server is up and running. Try unpublishing the selected instances of API Portal using the "Force Unpublish" action. If the problem persists, contact your administrator. |
INMCLE0390 | Path parameters can only be defined at the Resource level. |
Explanation |
Path parameters can be defined at the Resource level; but cannot be defined at the API level or Method level. |
Action |
Specify a path parameter at the Resource level. |
INMCLE0391 | Error while publishing/un-publishing to/from the gateways selected. |
Explanation |
You do not have permission to publish/un-publish to/from one or more of the selected gateways. |
Action |
Check if you have permission to publish/un-publish to/from the selected targets, and try again. |
INMCLE0392 | Download Documents action failed. |
Explanation |
An attempt was made to execute the Download Documents action without selecting an asset of the type Service. |
Action |
Select an asset of the type Service to execute this action. |
INMCLE0393 | No document(s) to download. |
Explanation |
Service doesn’t have any documents to download. |
Action |
Ensure there is at least one document to download. Service owner has to first upload documents which can be downloaded later. |
INMCLE0394 | Organization field cannot be empty. |
Explanation |
You have not entered the name of the submitting organization when creating an asset in CentraSite. |
Action |
Enter the organization name. |
INMCLE0395 | Failed to create an asset because the required {0} specification file is invalid.\n {1} |
Explanation |
Could not create an asset, possibly because the given {0} specification file is invalid. |
Action |
Upload a valid {0} specification file. If the problem persists, contact your administrator. |
INMCLE0396 | Unable to initialize and load {0} importer implementation. |
Explanation |
{1}: An error occurred while initializing the {0} importer implementation. There could be multiple reasons why this might have occurred: (1) incorrec importer implementation class is incorrect (2) importer implementation class could not be identified (3) importer implementation class failed to instantiate. |
Action |
Make sure that the importer implementation and specifications are correct. For more information about importer specifications, see the document Working with REST-based APIs. Contact your administrator if the problem persists. |
INMCLE0397 | Failed to create an asset of type {0} from the specification type {1}. |
Explanation |
In CentraSite, certain asset types require a particular type of specification file for creating asset instances of that type. An asset could not be created if the given type of specification file is not supported for that asset type. |
Action |
For a list of the asset types and their supported specification files, see the document Working with REST-based APIs. Contact your administrator if the problem persists. |
INMCLE0398 | Could not create or modify {1} asset from the {0} specification file. |
Explanation |
{2}: An error occurred while trying to import the specification file. There could be multiple reasons why this might have occurred: (1) specification file is invalid (2) data type or specification type is not supported in CentraSite (3) an internal error in saving the asset. |
Action |
Make sure the specification file is valid. For information on the mappings between the specification file and asset in CentraSite, see the document Working with REST-based APIs. Contact your administrator if the problem persists. |
INMCLE0399 | Error occurred while importing the archive file: {0} |
Explanation |
An error occurred while importing the archive file. |
Action |
Check the stack trace for the cause of the failure and if required, contact your system administrator. |
INMCLE0400 | {0} ERROR: Could not unpublish APIs from API Portals. |
Explanation |
An error {0} occurred while trying to unpublish APIs from API Portals, possibly because one or more of the API Portal servers were unavailable. |
Action |
Make sure the API(s) are already published and API Portal servers are up and running. If the problem persists, contact your administrator. |
INMCLE0401 | Could not generate access token for API Portal. |
Explanation |
An attempt was made to request access token through an API Portal, but the specified API Portal UUID {0} does not exist in the CentraSite registry. |
Action |
Make sure the API Portal UUID exists in the CentraSite registry. |
INMCLE0402 | Could not generate access token for API Portal user, possibly because the user does not have an E-mail address. |
Explanation |
A request for the access token triggered by an API Portal user could not processed, possibly because the specified user does not have an E-mail address. |
Action |
Enter a valid E-mail address. |
INMCLE0403 | CentraSite cannot update the gateway. {0} |
Explanation |
An error occured while updating a gateway in CentraSite. |
Action |
Contact your system administrator with exception stack trace information in the CentraSite log. |
INMCLE0407 | Failed to undeploy the asset {0} on target {1}. |
Explanation |
Could not undeploy the asset {0} on given target {1}. Possible reason: {2} |
Action |
Check the stack trace information for details. |
INMCLE0409 | Could not find user with email address {0} |
Explanation |
No user with the specified email address was found. |
Action |
Correct the parameter value of ‘__consumerEmailAddress’ in the configuration file and try again. |
INMCLE0410 | Could not find CentraSite object with id {0} |
Explanation |
A CentraSite object with the specified id was not found. |
Action |
Correct the CentraSite object id and try again. |
INMCLE0411 | User is not a CentraSite Administrator. |
Explanation |
The user does not have necessary permission to perform the service. |
Action |
Log in with a CentraSite Administrator role. |
INMCLE0412 | Value for parameter '{0}' is missing. |
Explanation |
The value for the mandatory parameter {0} is missing. |
Action |
Provide a value for the mandatory parameter {0}. |
INMCLE0413 | Failed to remove consumer/s {0} from asset/s {1}. Possible reason for failure: {2} |
Explanation |
You may encounter an error while trying to remove a consumer from an asset. It could be due to one of the following reasons: (1) Insufficient permissions (2) The consumer is not properly associated (3) The consumed asset is in Pending state (4) Internal error occurred while removing the consumer. |
Action |
Ensure that you have modify permission on the asset whose consumer or consumed assets you are trying to remove. If it is an internal error, please retry the operation after sometime. |
INMCLE0414 | API does not have a valid end point. |
Explanation |
The API to be published to API Portal does not have a valid end point. |
Action |
Ensure that the API has valid endpoint. If there is an endpoint available, ensure that the endpoint is categorized with the category which is chosen during the API publish. For example, if the API endpoint is categorized as “production” endpoint and the publisher chooses to publish only “Test” endpoint, then technically API has no endpoint to publish. |
INMCLE0415 | Failed to get applicable usecases for object {0}. |
Explanation |
An unexpected exception occurred while trying to get applicable usecases for {0}. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0416 | Wrong usage of the Impact Analysis action API {0}. |
Explanation |
Incorrect usage of the Impact Analysis action API. This problem occurs, when the '{0}' method is triggered with action in a state other than '{1}'. |
Action |
Before you execute the '{0}' method, verify that the action is in '{1}' state. |
INMCLE0417 | Could not retrieve the selected usecase. |
Explanation |
Failed to retrieve the selected usecase, possibly because the report is not implicitly set for retrieval. |
Action |
Use the 'setSelectedUseCase(..)' to set a report for this action. |
INMCLE0418 | Failed to execute {0}. |
Explanation |
You do not have necessary permission to perform this action. |
Action |
Before executing {0} make sure that you have the permission. Contact your CentraSite administrator and if necessary request access and then try again. |
INMCLE0419 | CentraSite could not create/update the gateway because a gateway with the gateway name specified in the command already exixts. |
Explanation |
A gateway already exists with the gateway name given in the command. |
Action |
Modify the gateway name and try the "set gateway" command again. |
INMCLE0420 | Could not retrieve the parameters of the selected report {0}. |
Explanation |
An unexpected exception occurred while trying to retrieve the parameters of the selected report {0}. The cause is not immediately known. |
Action |
Check the log file for detailed information. |
INMCLE0421 | Error while fetching action for template-id {0} from enforce-actions. |
Explanation |
Invalid Template Id found while fetching action for template-id {0} from enforce-actions. |
Action |
Contact your CentraSite Administrator. |
INMCLE0422 | Cannot register consumers since there are no consumable types defined for {0} type. |
Explanation |
You cannot register consumers for this asset since the asset type {0} does not have any consumable types defined for it. Asset instances of the defined consumable types can only be registered as consumers. |
Action |
Ensure that the type {0} has consumable types defined for it. Refer to the documentation to define consumable types for an asset type. |
INMCLE0423 | Could not save a scheduled report. |
Explanation |
An unexpected exception occurred while trying to save a scheduled report. The cause is not immediately known. |
Action |
Check the log file for detailed information. |
INMCLE0424 | Invalid parameter name {0}. |
Explanation |
You have entered an invalid parameter name. |
Action |
Provide a valid parameter name without special characters and try again. |
INMCLE0425 | Invalid parameter type {0}. |
Explanation |
You have entered an invalid parameter type. |
Action |
Provide a valid parameter type and try again. |
INMCLE0426 | Failed to delete the asset {0}. |
Explanation |
The selected asset {0} cannot be deleted because it is consumed by one or more assets. |
Action |
Make sure you unconsume all consumers from the asset, before trying to delete it. |
INMCLE0428 | Exception occurred while searching for Gateways. |
Explanation |
An exception occurred while searching for Gateways. |
Action |
Contact your System Administrator. |
INMCLE0429 | Failure in performing resource synchronization for virtual alias {0} during virtualization. |
Explanation |
An error occurred while performing resource synchronization for the virtual alias {0}. This may be due to improper resource selection during synchronization or an invalid message flow. |
Action |
Verify the resources that you have selected for synchronization with the native service and verify the message flow for the virtual service. |
INMCLE0430 | Error while fetching saved search {0}.xml |
Explanation |
An error occurred because the specified saved search resource cannot be found. |
Action |
Make sure the specified saved search is available. |
INMCLE0431 | Invalid Consumer Certificate {0}. |
Explanation |
The attached consumer certificate is invalid. |
Action |
Attach a valid consumer certificate and try again. |
INMCLE0432 | Failed to create an OData service due to unsupported version {0} of OData. |
Explanation |
Could not create OData service in the CentraSite registry. This is because the specified OData version {0} is not supported in CentraSite. |
Action |
For a list of supported OData versions, see the CentraSite documentation. |
INMCLE0433 | Failed to publish CentraSite details to the following Mediators: {0} |
Explanation |
An error occurred while publishing CentraSite details in the indicated Mediators {0}. There could be multiple reasons why this might have occurred: (1) Mediator server is down or inaccessible (2) invalid user credentials (3) application error on the Mediator server. |
Action |
Make sure the Mediator server is up and running, and the user credentials are correct. |
INMCLE0434 | Failed to execute {0}. |
Explanation |
Could not execute {0}. This is possibly because you do not have the sufficient permissions to execute {0}. |
Action |
Verify that you have the sufficient permissions. Contact your administrator and request permission if necessary and then try again. |
INMCLE0435 | Failed to create an OData service due to unexpected metadata at {0}. |
Explanation |
The metadata of the specified OData service has unexpected content. One or more of the required elements are missing. |
Action |
Check the metadata of the given OData service. |
INMCLE0436 | An error occurred while executing an extension enabled for the CentraSite Business UI.\nError Message: {0} |
Explanation |
A detailed explanation of the error thrown by the extension can be found here. Explanation: {1} |
Action |
Possible action steps to take: {2}\nIf the information provided by this error message is insufficient, please refer to the logs or contact your Administrator. |
INMCLE0437 | Failed to check the permissions of the current user. |
Explanation |
This is an unexpected exception. The cause is not immediately known. |
Action |
Check the stack trace for detailed information. |
INMCLE0438 | Error publishing CentraSite communication details to Mediator. |
Explanation |
CentraSite cannot publish communication details to Mediator version older than 9.8. |
Action |
Configure a supported version of Mediator. |
INMCLE0439 | Could not remove API Key configuration because one or more API Key consumers are associated to the virtual service. |
Explanation |
All API Key consumers associated to the virtual service must be deleted before revoking the API Key option in API Consumption Settings. |
Action |
Delete all associations between the virtual service and API Key consumers and try again. |
INMCLE0440 | Could not remove OAuth configuration because one or more OAuth consumers are associated to the virtual service. |
Explanation |
All OAuth consumers associated to the virtual service must be deleted before revoking the OAuth option in API Consumption Settings. |
Action |
Delete all associations between the virtual service and OAuth consumers and try again. |
INMCLE0441 | Failed to initialize an action class. |
Explanation |
Could not initialize the action class. Check the CentraSite logs for the action class name and for more details. |
Action |
Check to make sure that the implementation class is correct and follows a specified syntax. Refer to the documentation reference for Action Implementation class. |
INMCLE0445 | Could not publish CentraSite communication details to {0}. |
Explanation |
An error occurred while trying to publish the CentraSite communication details to {0}. There could be multiple reasons why this might have occurred: (1) {0} is down or inaccessible (2) invalid user credentials (3) application error in {0}. |
Action |
Make sure {0} is up and running, user credentials are correct, and then try again. |
INMCLE0446 | Failed to publish CentraSite communication details to {0}. |
Explanation |
Could not publish the CentraSite communication details to {0}, possibly because of a HTTP connection failure between CentraSite and {0}. |
Action |
Make sure the endpoint URL is valid, user credentials are correct, and then try again. |
INMCLE0447 | {0} endpoint URL is invalid. |
Explanation |
The specified {0} endpoint URL is invalid, possibly because it does not comply to the following formats:(1) <PROTOCOL>://<HOSTNAME>:<PORT>(2) <PROTOCOL>://<HOSTNAME> |
Action |
Enter a valid {0} endpoint URL and try again. |
INMCLE0448 | Failed to publish CentraSite communication details to {0}. |
Explanation |
Could not publish the CentraSite communication details to {0}, possibly because the SNMP configuration is not accessible. |
Action |
Please contact your administrator. |
INMCLE0449 | Failed to register CentraSite in {0}. |
Explanation |
An error occurred while registering CentraSite in {0}, possibly because {0} is already registered with another instance of CentraSite. |
Action |
Deregister the existing CentraSite instance from {0}, and then register CentraSite again. |
INMCLE0450 | Failed to deregister CentraSite from {0}. |
Explanation |
An error occurred while deregistering CentraSite from {0}. There could be multiple reasons why this might have occurred: (1) {0} is down or inaccessible (2) invalid user credentials (3) application error in {0}. |
Action |
Make sure {0} is up and running, user credentials are correct, and then try again. |
INMCLE0451 | Failed to load SNMP configuration file. |
Explanation |
Could not load the SNMP configuration file, possibly because the configuration file is missing or the file path is incorrect. |
Action |
Please contact your administrator. |
INMCLE0452 | Failed to parse SNMP configuration file. |
Explanation |
Could not parse the SNMP configuration file, possibly because the configuration file structure is not as expected. |
Action |
Please contact your administrator. |
INMCLE0453 | Could not update the publish or unpublish status of API Gateway asset. |
Explanation |
An error occurred while trying to update the publish or unpublish status of API Gateway asset. |
Action |
Please contact your administrator. |
INMCLE0454 | Could not update the publish or unpublish status of API Gateway asset. |
Explanation |
An error occurred while trying to update the publish or unpublish status of API Gateway asset, possibly because the update gateway status call does not have a valid value for the gateway ID. |
Action |
Please contact your administrator. |
INMCLE0455 | Could not update the publish or unpublish status of API Gateway asset. |
Explanation |
An error occurred while trying to update the publish or unpublish status of API Gateway asset, possibly because the update gateway status call does not have a valid value for the status parameter. |
Action |
Please contact your administrator. |
INMCLE0457 | Asset type with the namespace URI {0} already exists. |
Explanation |
An asset type with the given namespace URI {0} already exists. |
Action |
Change the name of the asset type and try it again. |
INMCLE0458 | Failed to add a new asset type. |
Explanation |
Could not add the new asset type. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0459 | Failed to get the relationship types. |
Explanation |
Could not fetch the relationship types. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0460 | Failed to get the association types. |
Explanation |
Could not fetch the association types. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0461 | Failed to get the object types. |
Explanation |
Could not fetch the object types. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0462 | Failed to get the consumable types. |
Explanation |
Could not fetch the consumable types. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0463 | Failed to set the consumable types. |
Explanation |
Could not set the consumable types. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0464 | Unable to get the option {0} for asset type {1}. |
Explanation |
Could not fetch the option {0} for asset type {1}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0465 | Unable to update option {0} for asset type {1}. |
Explanation |
Could not update the option {0} for asset type {1}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0466 | Failed to add attribute {0} to asset type {1}. |
Explanation |
Could not add the attribute {0} to asset type {1}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0467 | Failed to modify attribute {0} of asset type {1}. |
Explanation |
Could not modify the attribute {0} of asset type {1}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0468 | Failed to delete attribute {0} from asset type {1}. |
Explanation |
Could not delete the attribute {0} from asset type {1}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0469 | Failed to set the profile sequence for asset type {0}. |
Explanation |
Could not set the profile sequence for asset type {0}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0470 | Failed to get the profiles of asset type {0}. |
Explanation |
Could not fetch the profiles of asset type {0}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0471 | Failed to add profile {0} to asset type {1}. |
Explanation |
Could not add the profile {0} to asset type {1}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0472 | Failed to modify profile {0} of asset type {1}. |
Explanation |
Could not modify the profile {0} of asset type {1}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0473 | Failed to delete profile {0} from asset type {1}. |
Explanation |
Could not delete the profile {0} from asset type {1}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0474 | Failed to create a template for computed attribute or profile {0}. |
Explanation |
Could not create a template for computed attribute or profile {0}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0475 | Failed to update the template for computed attribute or profile {0}. |
Explanation |
Could not update the template for computed attribute or profile {0}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0476 | Failed to save asset type {0}. |
Explanation |
An error occurred while trying to save the asset type {0}. |
Action |
Check the stack trace information in the log file for more information. |
INMCLE0477 | Unable to initialize and load {0} exporter implementation. |
Explanation |
{1}: An error occurred while initializing the {0} exporter implementation. There could be multiple reasons why this might have occurred: (1) exporter implementation class is incorrect (2) exporter implementation class could not be identified (3) exporter implementation class failed to instantiate. |
Action |
Make sure that the exporter implementation and specifications are correct. Contact your administrator if the problem persists. |
INMCLE0478 | Could not delete lifecycle models '{0}'. {1} |
Explanation |
An error occurred while trying to delete the lifecycle models. There could be multiple reasons why this might have occurred: (1) insufficient permissions (2) lifecycle model is in Productive state (3) lifecycle model is an intermediate version. |
Action |
Ensure that you have sufficient permissions to delete the lifecycle model. Ensure that the lifecycle model you are trying to delete is either in a New or Retired state. Ensure that you are trying to delete the most recent version of lifecycle model. |
INMCLE0479 | Could not delete lifecycle stages '{0}'. {1} |
Explanation |
An error occurred while trying to delete the lifecycle stages. There could be multiple reasons why this might have occurred: (1) insufficient permissions (2) lifecycle stage is assigned to the final state of a lifecycle model. |
Action |
Ensure that you have sufficient permissions to delete the lifecycle stage. Ensure that the lifecycle stage you are trying to delete is not assigned to the final state of a lifecycle model. |
INMCLE0480 | Failed to undeploy asset {0} from gateway {1}. |
Explanation |
Could not undeploy the asset {0} from given gateway {1}. Possible reason: {2} |
Action |
Check the stack trace information for details. |
INMCLE0481 | Failed to set initial state for lifecycle model {0}. {1} |
Explanation |
An error occurred while trying to set an initial state for the lifecycle model {0}, possibly because the specified state is not defined for the lifecycle model. |
Action |
Check the logs to obtain more detailed information about the error. Contact your administrator if the problem persists. |
INMCLE0482 | Failed to set states for lifecycle model {0}. {1} |
Explanation |
An error occurred while trying to set states for the lifecycle model {0}, possibly because the specified states are not valid. |
Action |
Check the logs to obtain more detailed information about the error. Contact your administrator if the problem persists. |
INMCLE0483 | Failed to set organization for lifecycle model {0}. {1} |
Explanation |
An error occurred while trying to set organization for the lifecycle model {0}. There could be multiple reasons why this might have occurred: (1) insufficient permissions (2) organization is invalid or unavailable. |
Action |
Check the logs to obtain more detailed information about the error. Contact your administrator if the problem persists. |
INMCLE0484 | Failed to save lifecycle model {0}. {1} |
Explanation |
An error occurred while trying to save the lifecycle model {0}. There could be multiple reasons why this might have occurred: (1) initial state of the LCM is not set. (2) final state is not set (3) one or more defined states are not reachable from the initial state. (4) organization to which the LCM belongs is not set. |
Action |
Make sure the lifecycle model is not violating any of the above mentioned criteria. Check the logs to obtain more detailed information about the error. Contact your administrator if the problem persists. |
INMCLE0485 | Failed to set asset types for lifecycle model {0}. {1} |
Explanation |
An error occurred while trying to set the applicable asset types for the lifecycle model {0}. There could be multiple reasons why this might have occurred: (1) an asset type already enabled for an active lifecycle model cannot be added to another active model (2) if an asset is already associated to a lifecycle state, then its asset type cannot be removed from the enabled types for the model. (3) an asset type that is added is not enabled to be associated with the model. |
Action |
Make sure the lifecycle model is not violating any of the above mentioned criteria. Check the logs to obtain more detailed information about the error. Contact your administrator if the problem persists. |
INMCLE0486 | Could not unpublish assets from Mediator instances: ‘{0}’ |
Explanation |
An error occurred while trying to unpublish assets from Mediator instances, possibly because one or more of the Mediator instances are down or inaccessible. |
Action |
Make sure the Mediator instances are up and running. If the problem persists, contact your administrator. |
INMCLE0487 | Failed to set property {0} for lifecycle state {1}. {2} |
Explanation |
An error occurred while trying to set the property {0} for the lifecycle state {1}. There could be multiple reasons why this might have occurred. |
Action |
Make sure the lifecycle state is not violating any of the above mentioned criteria. Check the logs to obtain more detailed information about the error. Contact your administrator if the problem persists. |
INMCLE0488 | Could not delete Policy {0} . {1} |
Explanation |
An error occurred while trying to delete the policy. There could be multiple reasons why this might have occurred: (1) insufficient permissions (2) Policy model is in Productive state (3) Policy is an intermediate version |
Action |
Ensure that you have sufficient permissions to Policy. Ensure that the Policy you are trying to delete is either in a New or Retired state. Ensure that you are trying to delete the most recent version of policy. |
INMCLE0489 | Failed to get the promote progress information |
Explanation |
An exception occurred while getting the promote progress information. |
Action |
Please make sure that the request end point, request and header parameters are correct. |
INMCLE0490 | Failed to get the promote failed targets |
Explanation |
An exception occurred while getting the deployment failed targets information. |
Action |
Please make sure that the request end point, request and header parameters are correct |
INMCLE0491 | Failed to retrieve stages from gateway {0}. Gateway returned HTTP status code {1}. |
Explanation |
Could not retrieve stages from gateway {0}. Gateway returned HTTP status code {1}. |
Action |
Contact your administrator. |
INMCLE0492 | Failed to retrieve stages from gateway {0}. Possible reason: {1}. |
Explanation |
Could not retrieve stages from gateway {0}. Possible reason: {1}. |
Action |
Check the stack trace information for details. |
INMCLE0493 | Failed to add a stage to gateway {0}. Gateway returned HTTP status code {1}. |
Explanation |
Could not add a stage to gateway {0}. Gateway returned HTTP status code {1}. |
Action |
Contact your administrator. |
INMCLE0494 | Failed to add a stage to gateway {0}. Possible reason: {1}. |
Explanation |
Could not add a stage to gateway {0}. Possible reason: {1}. |
Action |
Check the stack trace information for details. |
INMCLE0495 | Failed to promote a virtual service {0} to gateway {1}. Gateway returned HTTP status code {2}. |
Explanation |
Could not promote a virtual service {0} to gateway {1}. Gateway returned HTTP status code {2}. |
Action |
Contact your administrator. |
INMCLE0496 | Failed to promote a virtual service {0} to gateway {1}. Possible reason: {2}. |
Explanation |
Could not promote a virtual service {0} to gateway {1}. Possible reason: {2}. |
Action |
Check the stack trace information for details. |
INMCLE0497 | Failed to get gateways on which the service {0} is deployed. Possible reason: {1}. |
Explanation |
Could not get gateways on which the service {0} is deployed. Possible reason: {1}. |
Action |
Check the stack trace information for details. |
INMCLE0498 | Failed to mark service {0} as promoted. Possible reason: {1}. |
Explanation |
Could not mark service {0} as promoted. Possible reason: {1}. |
Action |
Check the stack trace information for details. |
INMCLE0499 | Cannot establish UDDI connection for privileged user {0}. |
Explanation |
An error occurred {1} while trying to establish a UDDI connection for the privileged user. |
Action |
Contact your system administrator with the stack trace information in the CentraSite log. |
INMCLE0500 | Failed to synchronize application object from API Gateway {0} for API {1}. |
Explanation |
An error occurred {2} while trying to synchronize the consumer application from API Gateway {0} registered with the API {1}. This could have happened due to multiple reasons. Check the error logs for detailed information. |
Action |
Contact your system administrator with the stack trace information in the CentraSite log. |
INMCLE0501 | Failed due to {0}. Possible reason: {1} {2} |
Explanation |
Failed due to {0}. Possible reason: {1} {2}. |
Action |
Check the stack trace information for details. |
INMCLE0502 | Failed to publisn api into portal via gateway {0}. Possible reason: {1} {2}. |
Explanation |
Could not publisn api into portal via gateway {0}. Possible reason: {1} {2}. |
Action |
Check the stack trace information for details. |
INMCLE0503 | Failed to unpublish Gateway Applications |
Explanation |
Unable to delete Gateway Application or remove Gateway Application Association of the asset, possibly because of an incorrect attribute. |
Action |
Check to make sure that the specified input parameters are correct. |
INMCLE0504 | Failed due to {0}. The following {1} failed due to possible reason: {1}. |
Explanation |
Failed due to {0}. The following {1} failed due to possible reason: {1}. |
Action |
Check the stack trace information for details. |
INMCLE0505 | Receive following status code from the server {0} |
Explanation |
Receive following status code from the server {0} |
Action |
Check the stack trace information for details. |
INMCLE0506 | This API Gateway does not support publishing an API to more than one API Portal. |
Explanation |
This API Gateway does not support publishing an API to more than one API Portal. |
Action |
Please check your settings or install an API Gateway version that supports this functionality. |
INMCLI0001 | Parsing failed. Make sure the configuration file syntax (or) path is correct. |
Explanation |
This is probably because of the following reasons: 1) syntax of the configuration file is invalid 2) specified configuration file path is incorrect. |
Action |
Check for the above possible reasons and execute again. Refer to the CentraSite documentation for creating a valid configuration file. |
INMCLI0002 | Internal error. |
Explanation |
An unexpected error occurred due to failure in the system execution. |
Action |
Contact the CentraSite administrator. |
INMCLI0003 | Error while executing command ${0}. |
Explanation |
Unexpected error occurred while executing the command. |
Action |
Check the error message for details. |
INMCLI0004 | ${0} is an invalid log unit; possible values are ${1}. |
Explanation |
The specified log unit is not supported. Possible values are ${1}. |
Action |
Refer to the error message for a list of possible values. |
INMCLI0006 | Purger is unavailable for ${0}. |
Explanation |
Purger is not available for the specified log unit. |
Action |
Check to make sure that the log units specified in the XML configuration file are valid. Else, contact the CentraSite administrator. |
INMCLI0007 | Purging stopped for ${0} as there is no write permission for export location ${1}. |
Explanation |
Purging stopped for the log unit, possibly because you do not have the explicit permission to write to the export location. |
Action |
Verify if the user has required permissions for purging to the export location. |
INMCLI0008 | Insufficient disk space in ${0}. Required space ${1}. Available space ${2}. |
Explanation |
The specified export location does not contain enough space for the exported logs. Refer to error message for the available space and required space. |
Action |
Choose a different export location. |
INMCLI0009 | Purging Failed. Following error occurred ${0}. |
Explanation |
Purging failed for the log unit due to a network connection timeout. |
Action |
Try again later or contact CentraSite administrator. |
INMCLI0010 | Unable to archive export directory ${0}. |
Explanation |
An unexpected exception occurred while trying to archive the exported logs. This is probably because the files may be accessed by another application. |
Action |
Close the application and retry the operation. |
INMCLI0011 | Unable to create export directory ${0}. |
Explanation |
An unexpected exception occurred while trying to create the export directory. This is probably because of the following reasons: 1) you do not have the explicit permission to write to the export location 2) export location is invalid. |
Action |
Check for the above possible reasons and execute again. If the problem persists, conctact the CentraSite administrator. |
INMCLI0012 | Command ${0} is invalid. |
Explanation |
The specified command is not supported. For example, to purge logs you must specify -command purge_logs. |
Action |
Refer to CentraSite documentation for a list of the supported commands and their usage. |
INMCLI0016 | Attribute {0} does not exist for specified path {1}. |
Explanation |
The given attribute does not exist for the specified path. |
Action |
Verify that the attribute and path values are configured properly. |
INMCLI0121 | Error: Invalid session. |
Explanation |
CentraSite session has expired (or) already closed. |
Action |
Close your browser and log in again. |
INMCLI0156 | Parameters for New Version action can only be set in "Show Params" state. Current state of action is {0}. |
Explanation |
Parameters for versioning an asset can only be set in "Show Params" state. Current state of the action is {0}. |
Action |
Refer to the CSOAction related java document. |
INMCLI0181 | Current search criteria is invalid. |
Explanation |
The current search criteria is invalid. Validate the search criteria before you run. |
Action |
Check to make sure that the current search criteria is valid. |
INMCLI0239 | No list available to perform {0}. |
Explanation |
List is not available to perform {0}. |
Action |
Make sure that at least one of the selected items is added to the logged in user’s list already. |
INMCLI0265 | Failed to create the custom activity {0}. |
Explanation |
The custom activity syntax in the configuration file was invalid. |
Action |
Check the activity syntax in the configuration file. |
INMCLI0334 | This action cannot be added to the Message Flow more than {0} time(s). |
Explanation |
You cannot include this action more than the allowed number of time(s) in the Message Flow. |
Action |
Do not include this action more than the allowed number of time(s) in the Message Flow. |
INMCLI0335 | This action cannot co-exist with {0}. |
Explanation |
This action cannot co-exist with the existing {0} in the Message Flow. This is possibly because, the two actions are mutually exclusive. |
Action |
Check to make sure that there are no mutually exclusive actions in the Message Flow. |
INMCLI0336 | {0} of the dependent actions {1} should be configured in the Message Flow. |
Explanation |
This action mandates that at least one of the dependent actions {1} be included in the Message Flow. |
Action |
Choose at least one of the dependent actions for {1}. |
INMCLI0337 | This action cannot be added to the Message Flow more than once. |
Explanation |
You cannot include this action more than once in the Message Flow. |
Action |
Do not include this action more than once in the Message Flow. |
INMCLI0338 | This action is not applicable to the {0} Message Flow stage. |
Explanation |
You cannot include this action in the {0} Message Flow stage. |
Action |
Ensure that you include the action in the applicable Message Flow stage. |
INMCLI0442 | Provide a valid IP address range. |
Explanation |
You cannot specify only one IP address for a type. |
Action |
Ensure you have provided both the From and To IP address values. |
INMCLW0032 | Activity {0} is not applicable for given user. |
Explanation |
Activity {0} is not applicable for the given user. |
Action |
Assign the activity to given user. |
INMCLW0047 | Failed to synchronize configurator items with other configurators. |
Explanation |
Could not synchronize or update the configurator item changes with other configurators. |
Action |
Reset the configurator items. If the problem persists, contact the CentraSite administrator. |
INMCLW0109 | Failed to retrieve guest locale. Instead, returns the default locale {0}. |
Explanation |
An unexpected exception occurred while trying to retrieve the locale for logged in user. The cause is not immediately known. |
Action |
If the problem persists, contact the CentraSite adminsitrator. |
INMCLW0110 | Exception occurred when closing connection. |
Explanation |
An unexpected exception occurred when trying to close the underlying connection. |
Action |
Initialize before opening a connection. |
INMCLW0197 | Duplicate search condition. |
Explanation |
An attempt is made to specify a duplicate condition in the search recipe. |
Action |
Remove the duplicate condition from search recipe. |
INMCLW0227 | Search name '{0}' already exists. |
Explanation |
The same name is not allowed for two different searches. This error occurs when an attempt is made to save a search with a name that already exists. |
Action |
Enter a different search name. |
INMCLW0238 | Enable at least one notification option in User Preferences. |
Explanation |
At least one notification options in the User Preferences page should be selected to allow the current user to receive notifications through email and/or Inbox. |
Action |
Enable at least one notification option in the User Preferences page before subscribing to an asset. |
INMCLW0318 | Action {0} is not applicable for the message flow step {1}. |
Explanation |
The chosen action {0} is not applicable for the message flow step {1}. |
Action |
Choose a valid action for the message flow. |
INMCLW0456 | The service published to API Gateway could not be activated in API Gateway: {0} |
Explanation |
The service published to API Gateway could not be activated in API Gateway. Reason: {0} |
Action |
Check for reasons and solve the problem in API Gateway. |
INMCL_COMMON_ATTR_PENDING_APPROVALS | Pending Approvals |
INMCL_COMMON_ATTR_PENDING_APPROVALS_DEC | Pending approvals for the asset |
INMCL_USECASE_ASSETDEPENDENCY | Asset Dependency |
Explanation |
Displays the list of assets which the selected asset is depending upon. |
INMCL_USECASE_ASSETUSAGE | Asset Usage |
Explanation |
Displays the list of assets which make use of the selected asset. |
INMCL_USECASE_ASSET_VERSIONING_AND_CONSUMERS | Asset Versioning And Consumers |
Explanation |
Displays the different versions of the selected asset and the consumers for each of the versions. |
INMCL_USECASE_DEPLOYMNENT | Deployment Overview |
Explanation |
Displays the list of gateways to which the selected asset is deployed. |
INMCL_USECASE_ORG | Organization Structure |
Explanation |
Displays the list of organizations and their related objects. |
INMCL_USECASE_RUNTIMELANDSCAPEVIEW | Runtime Landscape View |
Explanation |
Displays the list of gateways and the assets deployed to them. |
INMCL_USER_ATTR_AVATAR_URL_DESC | The WebDAV URL of the Avatar for the User |
INMCL_USER_ATTR_AVATAR_URL_NAME | Avatar URL Location |
INMCL_USER_ATTR_EMAIL_DESC | The email address for the user |
INMCL_USER_ATTR_EMAIL_NAME | Email Address |
INMCL_USER_ATTR_FIRSTNAME_DESC | The details of the user's first name |
INMCL_USER_ATTR_FIRSTNAME_NAME | First Name |
INMCL_USER_ATTR_LASTNAME_DESC | The details of the user's last name |
INMCL_USER_ATTR_LASTNAME_NAME | Last Name |
INMCL_USER_ATTR_PHONE_DESC | The user's telephone number details |
INMCL_USER_ATTR_PHONE_NAME | Telephone Number |
INMCSE0006 | Select a taxonomy to delete |
Explanation |
Attempting to execute the delete action without selecting a taxonomy. |
Action |
Select a taxonomy to be deleted. |
INMCSE0007 | Select JPG, GIF or PNG image format |
Explanation |
Adding files other than JPG, GIF or PNG formats into a taxonomy or concept object. |
Action |
Add only files with JPG, GIF or PNG formats into a taxonomy or concept object. |
INMCSE0008 | The given URL is not a proper WebDAV URL. |
Explanation |
Wrong WebDAV URL or resource added into the taxonomy. |
Action |
Enter a correct WebDAV URL or resource. |
INMCSE0011 | Select at least one user |
Explanation |
At least one user should be selected. |
Action |
Select at least one user. |
INMCSE0012 | Select at least one permission |
Explanation |
At least one permission should be selected. |
Action |
Select at least one permission. |
INMCSE0013 | Select an organization to delete |
Explanation |
An attempt was made to delete an organization without selecting an organization object. |
Action |
Select an organization object to delete. |
INMCSE0014 | Select the property to delete |
Explanation |
An attempt was made to delete a property without selecting a property. |
Action |
Select the property to delete. |
INMCSE0015 | Select at least one administrator |
Explanation |
At least one administrator should be selected. |
Action |
Select at least one administrator. |
INMCSE0018 | Organization {0} already exists |
Explanation |
The same name is not allowed for two different organizations. This error occurs when an attempt is made to create an organization with a name that already exists. |
Action |
Enter a different organization name. |
INMCSE0019 | Select a user to delete |
Explanation |
An attempt was made to delete a user without selecting the user object. |
Action |
Select the user object to delete. |
INMCSE0020 | Enter a valid user |
Explanation |
A valid user is required. |
Action |
Enter a valid user. |
INMCSE0033 | Enter the mandatory fields |
Explanation |
Some mandatory fields were not entered. |
Action |
Enter the mandatory fields. |
INMCSE0038 | Enter a valid user |
Explanation |
A valid user has not been entered. |
Action |
Enter a valid user. |
INMCSE0042 | Select permission to remove |
Explanation |
At least one permission should be selected. |
Action |
Select at least one permission. |
INMCSE0044 | E-mail address is not valid |
Explanation |
An invalid E-mail address has been specified. |
Action |
Enter a valid E-mail address. |
INMCSE0045 | Check the length of the contact input |
Explanation |
The length of the contact input exceeds the limit. |
Action |
Check the length of the contact input. |
INMCSE0046 | Enter valid contact input |
Explanation |
A wrong value was entered in the contact input. |
Action |
Enter valid contact input. |
INMCSE0047 | First name should not be empty |
Explanation |
An empty first name was entered. |
Action |
Enter a value for the first name. |
INMCSE0051 | A request with status 'Pending' can’t be deleted. |
Explanation |
It is not possible to perform an unregister if a selected request has 'InProgress' as its status. |
Action |
Ensure that none of the selected requests has the status 'InProgress'. |
INMCSE0052 | Enter valid IP values |
Explanation |
Valid IP values are required. |
Action |
Enter valid IP values. |
INMCSE0062 | {0} is the current logged in user |
Explanation |
An attempt was made to delete the logged in user. |
Action |
Ensure that selected user is not the current logged in user. |
INMCSE0063 | {0} is the primary contact of {1} |
Explanation |
The logged in user tried to delete the primary contact of an organization. |
Action |
Ensure that the selected user-{0} is not the primary contact of an organization-{1}. |
INMCSE0064 | {0} is the CentraSite Administrator |
Explanation |
The logged in user tried to delete the user who is the CentraSite Administrator. |
Action |
Ensure that the selected user to delete is not the CentraSite Administrator. |
INMCSE0068 | Group {0} already exists in this organization |
Explanation |
An attempt was made to create a group with the same name as an existing group in the same organization. |
Action |
Use a new group name which is not already in use in the organization. |
INMCSE0074 | At least one {0} should be present |
Explanation |
When there is only one user with the role CentraSite Administrator or Organization Administrator, and if that user is deleted, this error will be thrown. |
Action |
There should be at least one CentraSite Administrator or Organization Administrator user. Make sure that another user with the same role is available in CentraSite. |
INMCSE0075 | Database access error. Can't connect to server CentraSite. |
Explanation |
The CentraSite Server is not running. |
Action |
Start the CentraSite Server. |
INMCSE0076 | There are no results matching your search criteria |
Explanation |
No results were found that match the search criteria. |
Action |
No action required. |
INMCSE0077 | The WSDL file is unreachable. Make sure the input information is correct. |
Explanation |
The URL for the given WSDL is wrong. |
Action |
Verify the URL given for this WSDL file. |
INMCSE0084 | {0} has child organization(s) and cannot be deleted. |
Explanation |
An organization cannot be deleted if there is at least one child organization associated to it. |
Action |
Make sure that the parent organization is not associated with any child organization, and then the parent organization can be deleted. |
INMCSE0085 | Select an attribute to move |
Explanation |
If a user tries to re-order the attribute without selecting anything, this error will be thrown. For this the user has to first select any attribute and then do the re-ordering. |
Action |
Select an attribute to move. |
INMCSE0086 | Reordering multiple attributes is not allowed |
Explanation |
While assigning attributes to the profile, a user can re-order the attributes. If the user tries to re-order multiple attributes simultaneously, this error will be thrown. |
Action |
Ensure that you do not select multiple attributes for reordering. |
INMCSE0087 | HTTP Methods cannot be empty |
Explanation |
HTTP methods for an XML / REST service cannot be empty during import. |
Action |
Please select any one of the HTTP methods for the XML / REST service. |
INMCSE0090 | User {0} not found in external user store |
Explanation |
The sychronization of users can be done only with users who belong to the current default external user store. |
Action |
Deselect the users who do not belong to the default external user store. |
INMCSE0091 | Users not found in external user store |
Explanation |
The sychronization of users can be done only with users who belong to the current default external user store. |
Action |
Deselect the users who do not belong to the default external user store. |
INMCSE0092 | No endpoint defined |
Explanation |
For the namespace to be defined, declare the endpoint of the service. |
Action |
Provide the endpoint information for the service before giving the namespace. |
INMCSE0093 | Only CentraSite Administrator can change the ownership |
Explanation |
Only a CentraSite Administrator can change the ownership or the organization. |
Action |
If you want to change the ownership or the organization, ensure that you are a CentraSite Administrator. |
INMCSI0071 | It is not allowed to add multiple associations if Relationship attribute is not multi-value |
Explanation |
For any single value relationship attribute, multiple value is not possible. |
Action |
Verify the given value for the single value relationship attribute. |
INMCSW0053 | Define the primary contact |
Explanation |
A primary contact is required when creating the organization. |
Action |
Define the primary contact. |
INMCSW0060 | {0} cannot be deleted |
Explanation |
You can only delete an organization if you have the necessary permissions. |
Action |
Ensure that you have the necessary permissions to delete an organization. |
INMCSW0061 | Default organization cannot be deleted |
Explanation |
The default organization cannot be deleted by any user. |
Action |
It is not possible to delete the default organization. |
INMEUE0001 | A connection with the same name already exists. |
Explanation |
A CentraSite connection name should be unique. |
Action |
Enter another connection name. |
INMEUE0002 | Could not connect to host. |
Explanation |
The specified host could not be connected. But the connection can be saved in the workspace. |
Action |
Enter a reachable host name. |
INMEUE0003 | Could not resolve host address. |
Explanation |
The specified host could not be reached. But the connection can be saved in the workspace. |
Action |
Enter a reachable host name. |
INMEUE0004 | Log on failed. Make sure your user name and password are correct. |
Explanation |
A logon failed due to invalid credentials. |
Action |
Make sure your user name and password are correct. |
INMEUE0005 | Connection Name should not be empty |
Explanation |
The required name for the connection is missing. |
Action |
Enter a name for the connection. |
INMEUE0006 | An error has occurred. See error log for more details. |
Explanation |
An internal error has been occurred. Refer to the log files for more details. |
Action |
Refer to the log files for more details. |
INMEUE0007 | Cannot connect to server. Verify the specified connection information!\nMaybe the application server or the registry is currently not available. |
Explanation |
Maybe the application server or the registry is currently not available. |
Action |
Check whether the application server and CentraSite are available and accessible. |
INMEUE0008 | Cannot initialize predicate editors. |
Explanation |
Due to non-compliance with the Eclipse UI, the UI rendering failed. |
Action |
Check your implementation and make sure it handles the predicate properly. |
INMEUE0009 | No editor found for predicate class {0} |
Explanation |
No editors are associated with the predicate. |
Action |
Check whether the implementation of IPredicateEditor is associated in your plugin description. |
INMEUE0010 | Profile already exists |
Explanation |
The specified profile already exists with the asset type. |
Action |
Create another profile if required. |
INMEUE0011 | Attribute already exists |
Explanation |
An attribute with the same name already exists. |
Action |
Enter another name for the attribute if required. |
INMEUE0012 | You cannot modify this predicate. Delete it and create a new one instead. |
Explanation |
Predefined profiles are not modifiable. |
Action |
Delete it and/or create a new one instead. |
INMEUE0013 | Could not save. Correct the input errors first! |
Explanation |
The input value is not compatible with the selected type. |
Action |
Enter an input value that is compatible with the selected type. |
INMEUE0014 | The object cannot be deleted because it still has incoming associations. |
Explanation |
An object with incoming/outgoing association cannot be deleted. |
Action |
If you want to delete this object, first delete the associations. |
INMEUE0015 | {0} cannot be renamed as it is the target of one or more ExternalLink objects. |
Explanation |
If this object is the target of any ExternalLink object, the name cannot be modified. |
Action |
No action required. |
INMEUE0016 | {0} cannot be deleted as it is the target of one or more ExternalLink objects. |
Explanation |
If this object is the target of any ExternalLink object, the object cannot be deleted. |
Action |
No action required. |
INMEUI0001 | You do not have the required authority. |
Explanation |
The permission required to do this operation has not been granted. |
Action |
Contact the CentraSite administrator to get sufficient permission to do this operation if required. |
INMFEE0011 | Error occurred while trying to publish UDDI object(s) : {0} |
Explanation |
While trying to publish UDDI object(s), if the program encounters any errors, it displays this message. {0} - The Disposition Report Fault Message exception. |
Action |
Ensure that the object in question is valid and any dependency required by the object is already federated to the target registry. For example, key generators specific to the source registry might not be recognized by the target. |
INMFEE0012 | Cannot find the taxonomy object : {0}, {1} |
Explanation |
The taxonomy processor is looking for the taxonomy object in the target registry and cannot find it. {0} - Object name {1} - Object key |
Action |
This error occurs very rarely. So make sure that a connection to the target registry can be obtained and re-execute the program. |
INMFEE0013 | Concept publish failed |
Explanation |
If you are using the taxonomy processor, then it will attempt to publish concepts and classification schemes to the target regsistry. If not all the concepts can be published, then this error occurs. |
Action |
Make sure that the concepts have valid values and try to re-execute the program. |
INMFEE0014 | The TModel for the key {0} is not available in the federated data. |
Explanation |
This message is displayed by the taxonomy processor. While trying to federate the data, if a particular TModel is identified as a taxonomy, then it looks for the TModel in the federated data. If the data is not available, then this error occurs. {0} - TModel key |
Action |
Provide the TModel name for federation in the configuration file and re-execute the program. |
INMFEE0018 | The given default Business Entity name "{0}" is not available in the target registry. |
Explanation |
In the configuration file, you will provide a default business entity name for the target, so that services can be associated with this business. If this business entity name does not have any businesses in the target registry, then this error occurs. {0} Business entity name. |
Action |
Provide the right business entity name after ensuring that it exists in the target registry. |
INMFEE0022 | The {0} registry details are not configured properly |
Explanation |
The federation takes the data specification from the provided configuration file. If the {0} registry details are not configured in the configuration file, you will get this error. {0} source / target. |
Action |
Make sure the {0} registry details are provided with the proper syntax in the configuration file. To get more details, please refer to the product documentation. |
INMFEE0023 | The provided configFile is not configured properly. |
Explanation |
The configuration file provided does not have the required elements eventTypeStoreLoc and nervAssetsLoc. These elements should be present in the configFile. |
Action |
Ensure that these two elements are provided in the configuration XML file. Also ensure that you provide a valid path. |
INMFEE0026 | Cannot obtain OSGi instance for federation process. |
Explanation |
The OSGi instance is required to emit events across the event bus for federation. It could be that the OSGi container initialization is aborted. |
Action |
Restart your default OSGi container. Wait until the OSGI container is initialized before you begin the federation process. |
INMFEI0001 | No data available for federation. Terminating program execution. |
Explanation |
The configuration file specifies the data that has to be inquired from the source registry. If the result of the inquiry does not have any data, then the federation cannot proceed and the program will terminate. |
Action |
Make sure that the configuration file specifies the correct data that is needed for federation. |
INMFEI0002 | Results of inquiring the source registry : |
Explanation |
CentraSite is currently inquiring the source registry and will display the results of the inquiry. |
Action |
No action required. |
INMFEI0003 | Obtained number of {0} : {1} |
Explanation |
This message displays the number of business objects obtained from inquiring the source registry {0} - Business(es) {1} - Number |
Action |
No action required. |
INMFEI0004 | Timestamp based update will be performed |
Explanation |
The federated objects will be compared with the modification timestamp and the update will be performed based on that. |
Action |
No action required. |
INMFEI0005 | Timestamp based update will not be performed |
Explanation |
The federated objects will be published, irrespective of whether the object to be published is the same or modified. |
Action |
No action required. |
INMFEI0006 | Key generator processor : Modifying the keys to belong to the domain {0} |
Explanation |
The UDDI keys of the federated objects will go through the key generator processor which will modify the UDDI keys such that they belong to the provided domain {DomainKey} {0} - Domain Key |
Action |
No action required. |
INMFEI0007 | The federated data is received as the following event : |
Explanation |
The Federation framework enables event emission. So the data is federated as events. This message informs that the emitted event is received for publishing to the target registry. |
Action |
No action required. |
INMFEI0008 | Time taken for publishing the data : {0} seconds |
Explanation |
The time taken for publishing the UDDI objects to the target registry is displayed by this message {0} - Time taken. |
Action |
No action required. |
INMFEI0009 | The given UDDI object(s) were federated to this target registry. |
Explanation |
The federation operation has completed and the required UDDI objects were published to this target registry. |
Action |
No action required. |
INMFEI0010 | Trying to update/publish {0} : {1}, {2} |
Explanation |
This message is displayed when an attempt is made to publish a UDDI object. The object can be identified by the object name and the UDDI key which will be displayed in the message. {0} Business / Service / TModel {1} Name of the UDDI object {2} UDDI key. |
Action |
No action required. |
INMFEI0015 | Taxonomy processor : Categories (Concepts) and Taxonomies (Classification Schemes) were identified and published to the target registry |
Explanation |
The taxonomies and categories were identified from the provided data and published to the target registry. |
Action |
No action required. |
INMFEI0016 | No {0} were found with the provided UDDIv3 Inquiry API parameters |
Explanation |
The UDDI object to be inquired should be specified in the configuration file for federation. It is provided as UDDI v3 Inquiry API calls, find_business, find_service, find_tModel. If no UDDI object could be inquired with the provided Inquiry API, then this message is displayed. {0} - Business(es) / Service(s) / TModel(s). |
Action |
Make sure that the Inquiry API adheres to the UDDI standards and that the inquiry parameters can inquire the data from the registry. |
INMFEI0017 | UDDI registry configured for {0} with the following properties: user {1}, {2} Authentication. |
Explanation |
This message is displayed if a connection could be established to the UDDI registry with the provided details. {0} - host {1} - user {2} - AuthToken, Basic |
Action |
No action required. |
INMFEI0019 | The above mentioned {0} is published to the target registry |
Explanation |
The UDDI object identified by the given name and the UDDI key has been updated/published in the target registry. {0} Business / Service / TModel. |
Action |
No action required. |
INMFEI0020 | Not updating {0} : {1}, {2} in the target registry |
Explanation |
While the program was performing timestamp based updates in the target registry, the UDDI object identified by the given name and the UDDI key was not updated/published in the target registry because it is already available in the target. {0} - Business, Service, TModel {1} - Name of the UDDI object {2} - UDDI key. |
Action |
No action required. |
INMFEI0021 | Number of {0} received for publishing : {1} , number published : {2} |
Explanation |
This message displays the number of {0} that were published to the target registry. {0} - Business(es) / Service(s) / TModel(s) {1} - Number of objects received {2} - Number published. |
Action |
No action required. |
INMFEI0024 | The federated data has reached the target : {0} |
Explanation |
There can be multiple targets configured for federation. This message displays the details of the target which has received the federated data through the federation ID {0}. |
Action |
No action required. |
INMFEW0025 | An error occurred while trying to close a resource - {0} |
Explanation |
Occasionally an error might be encountered while trying to close open connections, streams, etc. This is just a warning that an error was encountered and can be ignored. |
Action |
Make sure that the resource in question is not opened and/or modified by another program/application. |
INMIEE0001 | The call to the registry layer of CentraSite has failed. |
Explanation |
During export and import, access to the registry layer of CentraSite is required. The call to the registry layer of CentraSite has failed. |
Action |
Please contact your software supplier. |
INMIEE0002 | The archive file {0} could not be opened. |
Explanation |
The archive file is used to store the registry objects for export and import. The access to this archive file has failed. |
Action |
Please make sure that the archive file name is correct and you have sufficient access rights to access this file. |
INMIEE0003 | The archive file {0} could not be closed. |
Explanation |
The archive file is used to store the registry objects for export and import. The closing of this archive file has failed. |
Action |
Please make sure that the archive file has not been removed meanwhile. |
INMIEE0005 | The object with name {0}, type {1} and key {2} references another object in the context {3}. The referenced object has the key {4}, but it does not exist in the registry. |
Explanation |
Referenced object cannot be resolved, neither from the import set nor by existing objects. |
Action |
Add the referenced object. |
INMIEE0006 | The registry object cannot be imported, because it is older than the existing registry object. |
Explanation |
The import of the registry object has been rejected, because the timestamp of the existing registry object is newer than the timestamp of the import registry object. You can set the replace option of the import operation to overwrite the existing registry object with an older import object. |
Action |
You can set the replace option of the import operation to overwrite the existing registry object with an older import object. |
INMIEE0007 | The import object refers to the invalid object "{0}" and thus cannot be imported either. |
Explanation |
The import object refers to the specified invalid object, and thus cannot be imported either. |
Action |
Check why the referenced object is invalid by analyzing its error message. |
INMIEE0013 | The object cannot be imported because the embedded object {0} which is embedded in the existing object does not exist and is referenced by object {1}. |
Explanation |
The existing object contains an embedded object which is not defined in the object to be imported. This embedded object is referenced by another object either directly or through one of its embedded objects. |
Action |
Please add the missing object and try importing the object. |
INMIEE0014 | The external link with URI {0} could not be found. |
Explanation |
Specified resource could not be found. It may have been previously deleted. |
Action |
No action required. |
INMIEE0016 | The user has no read/write privilege to access/modify already existing registry objects |
Explanation |
The user wants to access or write an object for which the user has no privileges. |
Action |
The action must be performed by a more privileged user. |
INMIEE0017 | The user has no write privilege to modify existing registry objects |
Explanation |
The user wants to modify an object for which the user has no modify privileges. |
Action |
The action must be performed by a more privileged user. |
INMIEE0018 | The database with the URL {0} cannot be accessed. |
Explanation |
A connection to the database cannot be established. |
Action |
Check whether the URL is correct. |
INMIEE0019 | The connection to database {0} cannot be closed. |
Explanation |
The database connection has been lost and cannot be closed. |
Action |
Please contact your software supplier. |
INMIEE0021 | The registry object could not be deleted. |
Explanation |
The registry object should have been deleted after the export, but the deletion has failed. |
Action |
Please contact your software supplier. |
INMIEE0022 | The lifecycle stage URL of the registry object does not match the URL of the import registry, which is {0} |
Explanation |
The registry object carries information about valid target registries. This information is called the lifecycle stages of the particular lifecycle state of this registry object. This registry object thus can only be imported into matching target registries. |
Action |
The registry object can be imported into matching target registries only. |
INMIEE0025 | The import of a user registry object has failed, because a user with identical name and key {0} already exists. |
Explanation |
The user registry object already exists. |
Action |
No action required. |
INMIEE0026 | The import of a group registry object has failed, because a group with identical name and key {0} already exists. |
Explanation |
The group registry object already exists. |
Action |
No action required. |
INMIEE0027 | The import operation has failed, because the update of the security information has failed, object "{0}" ({1}). |
Explanation |
The update of the security information has failed. |
Action |
Please contact your software supplier. |
INMIEE0028 | The import archive does not have the expected compatibility level of {0}. |
Explanation |
The import archive must contain a file named MANIFEST.TXT which contains the compatibility level of the import archive. The compatibility level of the import archive must be the same as the compatibility level of the CentraSite version used. |
Action |
Use the same CentraSite version for exporting and importing. |
INMIEE0030 | The provided import organization key {0} does not exist in the registry. |
Explanation |
The lookup of this key in the registry was not successful. |
Action |
Please provide a valid import organization key. |
INMIEE0031 | The provided import organization key {0} does not refer to an organization. |
Explanation |
The provided key exists in the registry, but the referred object is not an organization object. |
Action |
Please provide a valid import organization key. |
INMIEE0032 | The setting of the import organization {0} has failed. |
Explanation |
During import, the setting of the import organization has failed. |
Action |
Please contact your software supplier. |
INMIEE0034 | The deletion of the repository resource {0} has failed. |
Explanation |
The option delete after export has been set and the deletion of a repository resource has failed. |
Action |
Please contact your software supplier. |
INMIEE0035 | The query to find all external links with the external URI {0} has failed. |
Explanation |
The option delete after export has been set and the query to find all external links with the same URI has failed. |
Action |
Please contact your software supplier. |
INMIEE0036 | The collection of the registry objects of the policy {0} has failed. |
Explanation |
The delete after export option is active and the policy is to be deleted after export. The collection of the registry objects belonging to the policy has failed. |
Action |
Please contact your software supplier. |
INMIEE0040 | The import of a role registry object has failed, because a role with identical name and key {0} already exists. |
Explanation |
Role objects cannot be replaced. |
Action |
Re-establish the organization's roles. |
INMIEE0041 | The import of a permission registry object has failed, because a permission with identical name and key {0} already exists. |
Explanation |
Permission objects cannot be replaced. |
Action |
Re-establish the organization's permission. |
INMIEE0044 | The user has no privilege to create/update an asset type ({0}) |
Explanation |
The user has not enough permission to create or update an asset type. |
Action |
Check the roles of the user. |
INMIEE0046 | The import of the organization with key {0} has failed, because the organization has not been exported with the option to include users, groups, roles and permissions. |
Explanation |
You can only import an organization together with its users, groups, roles and permissions. However, if the organization already exists, then it is possible to just import an organization without its users, groups, roles and permissions. |
Action |
Export the organization with the option to include users, groups, roles and permissions. |
INMIEE0048 | Creating/updating of asset type "{0}" failed with internal error: {1} |
Explanation |
An asset type cannot be imported or updated because of an internal registry problem. |
Action |
View the internal error reason and the stack trace in the log. |
INMIEE0049 | Replacement of asset type "{0}" failed due to layout mismatch |
Explanation |
The asset type cannot be replaced because the layout of the importing type is incompatible with the exisiting one. |
Action |
View the stack trace for the details. |
INMIEE0050 | The asset type "{0}" references another object with key {1}, but it does not exist in the registry. |
Explanation |
A reference from the asset type to be imported is not in the registry. This is usually a referenced asset type and must be present. Due to internal reasons the import cannot continue. |
Action |
Check that the referenced object (asset type) is present in the target registry. |
INMIEE0055 | Asset to be imported does not fit to Asset type definition with attribute mismatch, attribute: {0} |
Explanation |
The asset does not match the asset type. Possibly the asset has an attribute which is not defined for the given asset type. |
Action |
Check the asset type for missing attributes. Import the asset type which matches the asset. |
INMIEE0057 | Selective import not supported with old export archives |
Explanation |
No selective import is possible, only importing the whole archive is supported. |
Action |
Do not select particular keys. |
INMIEE0061 | User {0} not found |
Explanation |
The requested user name was not found in the registry. |
Action |
Use a valid user name. |
INMIEE0063 | The document cannot be imported, because the associated asset type will be rejected |
Explanation |
The schema file of an asset type cannot be imported because the asset type itself will be rejected for another reason. |
Action |
Analyze the existing asset type. |
INMIEE0064 | Replacement of asset type {0} failed due to layout mismatch, reason: {1} |
Explanation |
The given asset type cannot be replaced because it would change or remove used information, e.g. attributes. |
Action |
Check the attributes of the existing asset type. There are assets with attributes which would be removed by the import. |
INMIEE0066 | The document cannot be imported, because its parent was rejected |
Explanation |
The repository document will not be imported because its parent object (e.g. an ExternalLink object) was rejected. |
Action |
Check why the parent object was rejected. |
INMIEE0067 | The object cannot be replaced, because it would lose its attribute {0}, which is referenced within registry by: {1} |
Explanation |
The given object cannot be replaced, because the object that is already present has an attribute which would disappear as a result of the replacement. This attribute is referenced by others, therefore the attribute must be kept. |
Action |
Check the existing object and its references. |
INMIEE0068 | No privilege to update object |
Explanation |
The user has no privilege to update an object, present in the archive, to the registry. This could happen when updating asset types or taxonomies. |
Action |
Check if you can import the archive as a user with more privileges. |
INMIEE0072 | Cannot update asset type because of version mismatch ("{0}" / "{1}") |
Explanation |
The asset type to be imported has a lower version number than the one in the registry. The type is incompatible to the registry and therefore a replacement would destroy relevant information. |
Action |
The asset type from a previous version cannot be imported. |
INMIEE0074 | Insufficient permissions to access CentraSite's webdav for user {0} at resource {1}. |
Explanation |
The user {0} tries to access the CentraSite webdav resource without insufficient permissions. |
Action |
Make sure the user has insufficient permissions to access the CentraSite webdav resource. |
INMIEE0075 | Invalid credentials for promotion user {0}. |
Explanation |
The promotion user defined in the asset promotion policy does not have the sufficient permissions to access the target CentraSite. |
Action |
Make sure the user has insufficient permissions to access the target CentraSite. |
INMIEI0010 | The registry object is not imported, because it has the same timestamp as the existing object. |
Explanation |
The object to be imported already exists with the same timestamp. |
Action |
No action required. |
INMIEI0011 | The imported registry object has replaced the existing object. |
Explanation |
The registry object to be imported already exists and has been replaced. |
Action |
No action required. |
INMIEI0012 | The imported registry object has been created. |
Explanation |
The registry object to be imported has been created. |
Action |
No action required. |
INMIEI0020 | The registry object with key {0} was deleted after it has been exported. |
Explanation |
The option delete after export has been set and the registry object has been deleted after the export. |
Action |
Please contact your software supplier. |
INMIEI0023 | The document cannot be imported, because it is older than the existing document. |
Explanation |
The import of the document has been rejected, because the timestamp of the existing document is newer than the timestamp of the import document. You can set the replace option of the import operation to overwrite the existing document with an older import document. |
Action |
You can set the replace option of the import operation to overwrite the existing document with an older import document. |
INMIEI0024 | The document was not imported, because it has the same timestamp as the existing document. |
Explanation |
The import document and the existing document have the same timestamp. No import is necessary. |
Action |
No action required. |
INMIEI0033 | The repository resource was deleted after it has been exported. |
Explanation |
The option delete after export has been set and the registry object has been deleted after the export. |
Action |
No action required. |
INMIEI0039 | Referenced object not in export set: {0} --> {1} |
Explanation |
The target object is not in the export set. |
Action |
Before importing, the referenced (target) objects must be present in the registry. |
INMIEI0065 |
INMIEI0069 | The document cannot be imported because it is already present |
Explanation |
The document, which contains executable code, is not imported because it is already present. |
Action |
No action required. |
INMIEI0070 | The registry object is not imported, because it is already present |
Explanation |
The object cannot be replaced because the root object was not imported. |
Action |
No action required. |
INMIEW0008 | Embedded objects cannot be exported. |
Explanation |
Embedded objects like Classification, AuditableEvent, ExternalIdentifier, ServiceBinding, SpecificationLink and Association cannot be exported. |
Action |
Deselect object from list of objects to be exported. |
INMIEW0009 | Export of selected object does not find any objects to be exported. |
Explanation |
Export of selected object does not find any objects to be exported. |
Action |
Remove object from list of objects to be exported. |
INMIEW0029 | The referenced registry object with key {0} is not part of the export archive. |
Explanation |
A referenced object is not selected for export. Therefore there might be problems at import. |
Action |
Check your associated objects and decide whether to add them to the export. |
INMIEW0037 | Delete of registy objects failed, reason: {0} |
Explanation |
The deletion of one or more registry objects has failed during the export with delete option. The export archive however is complete. |
Action |
See the reason for the rejection within the message. |
INMIEW0038 | The referenced registry object with key {0} is not part of the export archive. It is referenced from object: "{1}" |
Explanation |
A referenced object is not selected for export. Therefore there might be problems later when you try to import the archive. |
Action |
Check your associated objects and decide whether to add them to the export. |
INMIEW0042 | Delete after export of object "{0}" is not supported |
Explanation |
It is currently not supported to delete specified object with the delete-after-export function. |
Action |
Delete the object manually. |
INMIEW0043 | User "{0}" could not be deleted from organization |
Explanation |
The user cannot be deleted from an organization after import because this user is already in use. |
Action |
Clean up the user manually with the imported organization. |
INMIEW0047 | Object {0} modified due to unreferenced association |
Explanation |
The association to an unreferenced target object was removed from the object. |
Action |
Check the object and repair it if necessary. |
INMIEW0051 | Unprivileged reference to key: {0} |
Explanation |
An exported object has a reference to an object that the user has no privilege to access. This means for import that the referenced object must be present and the importing user must have privileges to access this object. |
Action |
Keep this situation in mind for a later import. |
INMIEW0052 | One ore more asset types may be corrupted, key: {0} |
Explanation |
Due to resolving an access violation situation, it may happen that asset types may be corrupted. |
Action |
Import the archive as CentraSite Administrator. |
INMIEW0053 | {0} association to object "{1}" removed |
Explanation |
The association to the given object has been removed during import because the target object is not present. |
Action |
Re-establish the removed association if possible. |
INMIEW0054 | Classification "{0}" removed because of unreferenced category |
Explanation |
The classification has been removed from the object because its concept is not present in the registry. |
Action |
Re-establish the classification if possible. |
INMIEW0058 | External link reference removed from object "{0}" |
Explanation |
An external link reference which does not exist for the object has been removed. |
Action |
Check if the external link can be re-inserted manually. |
INMIEW0059 | Lifecycle state removed because of missing model |
Explanation |
The object has a lifecycle state at import, however the associated lifecycle model is not present in the target registry. |
Action |
Import the lifecycle model first. |
INMIEW0060 | User object cannot be imported because of a missing name, key: {0} |
Explanation |
The import processing detected an invalid user element and ignored the import. |
Action |
Verify the user entry in the archive. |
INMIEW0062 | contains unprivileged reference |
Explanation |
The object given contains a reference to an object which cannot be exported because the user has no privilege of that object. Only the reference gets exported. At import, this reference is checked and possibly removed from the object if the referenced object is not present. |
Action |
Check if a more privileged user should export the object. |
INMIEW0071 | ServiceBinding "{0}" removed because of unreferenced specificationObject |
Explanation |
A service binding points to a specification object, which is not present in the archive or registry. Therefore the service binding gets removed from the service. |
Action |
Check the service and its specification objects. |
INMIEW0073 | Asset type is replaced with a lower version number. |
Explanation |
An older version of the asset type has been replaced in the registry. |
Action |
Consider that some values are changed in the type, for example, attributes no longer there. |
INMIEW0076 | {0} {1} is imported without valid credentials. |
Explanation |
The import cannot restore passwords in a target CentraSite. Please verify user and password settings. |
Action |
Specify a valid username and password for the alias or policy. |
INMIEW0077 | Alias with name {0} is already persent in registry |
Explanation |
There is another alias object with the same in registry which could cause problems in using them |
Action |
Try to rename the alias in registry to avoid ambiguity |
INMIME0001 | ObjectType {0} does not exist. |
Explanation |
The required object type does not exist in CentraSite. |
Action |
Make sure the required object type is available in CentraSite and create an instance of it. |
INMIME0002 | Asset {0} not found. |
Explanation |
A required asset is not available in CentraSite. |
Action |
Create the required asset. |
INMIME0003 | Error while executing JAXR operation. |
Explanation |
An internal JAXR operation failed. |
Action |
Retry your request. |
INMIME0004 | XPDL file {0} not found. |
Explanation |
An XPDL file does not exist in the location specified. |
Action |
Make sure the given XPDL file is in the specified location. |
INMIME0005 | Error while parsing the XPDL file. |
Explanation |
The XPDL file does not match the XPDL format. |
Action |
Make sure the given XPDL format is valid. |
INMIME0006 | Error while connecting to CentraSite. |
Explanation |
It is not possible to establish a connection to the CentraSite database. |
Action |
Make sure the CentraSite database URL and CentraSite user credentials are valid. |
INMIME0007 | Given XPDL File not supported. |
Explanation |
The given XPDL file is not supported by CentraSite. CentraSite supports only XPDL 2.x. |
Action |
Make sure the given XPDL version is 2.x. |
INMIME0008 | Specified process {0} is not available |
Explanation |
There is no process with the specified asset ID |
Action |
Check the asset ID provided in the request |
INMIME0009 | Required id is missing in Pool |
Explanation |
While parsing the XPDL file, a pool element has been found but the attribute "id" is missing. |
Action |
Please make sure the specified XPDL file is valid. |
INMIME0010 | From reference is missing in Transition |
Explanation |
While parsing the XPDL, a transition element has been found but the "from reference" is missing in the transition element. |
Action |
Please make sure the "from reference" element contains a proper value. |
INMIME0011 | To reference is missing in Transition |
Explanation |
While parsing the XPDL, a transition element has been found but the "to reference" is missing in the transition element. |
Action |
Please make sure the "to reference" element contains a proper value. |
INMIME0012 | Id is missing in Transition |
Explanation |
While parsing the XPDL, a transition element has been found but the "id" is missing in the transition element. |
Action |
Please make sure "id" is present in the transition element and contains a proper value. |
INMIME0013 | Id is missing in lane element |
Explanation |
While parsing the XPDL, a lane element has been found but the "id" is missing in the transition element. |
Action |
Please make sure the "id" is present in the lane element and contains a proper value. |
INMIME0014 | Id is missing in activity element |
Explanation |
While parsing the XPDL, a lane element has been found but the "id" is missing in the activity element. |
Action |
Please make sure "id" is present in the activity element and contains a proper value. |
INMJRE0001 | Database access error: {0} |
Explanation |
An error occurred while accessing the database. The corresponding stack trace contains a "caused by" message with the reason of the failure. |
Action |
Please contact your software supplier if you can't analyze the reason of the database access error. |
INMJRE0002 | Expected {0} objects |
Explanation |
Certain operations that accept a collection of input objects (such as for example LifeCycleManager.saveOrganizations()) expect certain object types ("Organization" in this example). The affected operation can be found in the stack trace. |
Action |
Correct the client program. |
INMJRE0003 | Invalid property name ''{0}'' |
Explanation |
The name of a property must be a valid NCName as in XML schema, e.g. it must not contain colon or whitespace. |
Action |
Correct the name. |
INMJRE0004 | Invalid object in {0} parameter |
Explanation |
Certain operations that accept a collection of input objects expect certain object types. The affected operation can be found in the stack trace. |
Action |
Correct the client program. |
INMJRE0005 | Mutually exclusive find qualifiers: {0}, {1} |
Explanation |
The listed find qualifiers are mutually exclusive with respect to the performed operation. |
Action |
Correct the client program. |
INMJRE0006 | Found multiple matches |
Explanation |
The performed query method is supposed to return zero or one result object, however the database contains multiple matches. |
Action |
Please contact your software supplier. |
INMJRE0007 | The javax.xml.registry.queryManagerURL property is not set |
Explanation |
Before creating a new Connection, the javax.xml.registry.queryManagerURL property has to be set to a non-null value. |
Action |
Correct the client program. |
INMJRE0008 | The credentials parameter must not be null |
Explanation |
The setCredentials() method was called with a null value for the credentials parameter. |
Action |
Correct the client program. |
INMJRE0009 | Re-connect failed |
Explanation |
An error occurred while recreating the database connection according to the given credentials. The stack trace contains a "caused by" message with the reason of the failure. |
Action |
Please contact your software supplier. |
INMJRE0010 | Invalid credentials: expected PasswordAuthentication |
Explanation |
The credentials have to be passed as an instance of java.net.PasswordAuthentication. |
Action |
Correct the client program. |
INMJRE0011 | User name is not unique: {0}, only readonly access granted |
Explanation |
For each user, there should be only one user object in the database. For the given user however, several objects with the same name were found. When the user tries to log in he is granted readonly access. |
Action |
Log in using a different user (probably an administrator) and delete or rename the duplicate user objects. |
INMJRE0012 | The declarative query manager is not supported by this implementation |
Explanation |
The declarative query manager is not supported by this implementation. |
Action |
See the documentation for the available query functionality. |
INMJRE0013 | Invalid interface name parameter: {0} |
Explanation |
The method LifeCycleManager.createObject() was called with an illegal interface name. |
Action |
Correct the client program. |
INMJRE0014 | Invalid XML response when saving documents |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INMJRE0015 | The object to be undeprecated ({0}) is not in deprecated state |
Explanation |
Only deprecated objects may be undeprecated. |
Action |
Select only deprecated objects for undeprecation. |
INMJRE0016 | Illegal object type: {0} |
Explanation |
A delete operation was called with an illegal object type. |
Action |
Correct the client program. |
INMJRE0017 | Internal error: object with key "{0}" lost from cache |
Explanation |
This internal error indicates an inconsistency in the object cache. |
Action |
Please contact your software supplier. |
INMJRE0018 | Invalid null value in {0} parameter |
Explanation |
The method QueryManager.getRegistryObjects() was called with a null value. |
Action |
Correct the client program. |
INMJRE0019 | The object identified by the ConnectionFactory property {0}="{1}" is not a classification scheme |
Explanation |
The default postal scheme was not specified correctly. |
Action |
Specify a correct default postal scheme. |
INMJRE0020 | This implementation does not support makeRegistrySpecificRequest() |
Explanation |
This implementation does not support makeRegistrySpecificRequest(). |
Action |
See the documentation for the available query functionality. |
INMJRE0021 | Invalid schema name ''{0}'', please consult the documentation for correct syntax |
Explanation |
The schema name of a type must be a valid NCName as in XML schema, e.g. it must not contain colon or whitespace. |
Action |
Correct the name. |
INMJRE0022 | An association cannot have itself as source object |
Explanation |
An association cannot have itself as source object. |
Action |
Specify a correct association. |
INMJRE0023 | An association cannot have itself as target object |
Explanation |
An association cannot have itself as target object. |
Action |
Specify a correct association. |
INMJRE0024 | Association type must not be null |
Explanation |
When creating a new association the association type must not be null. |
Action |
Specify a correct association. |
INMJRE0025 | The object to be deleted is not of type {0} |
Explanation |
The delete operation specified that only objects of a particular type should be deleted, however at least one of the given keys points to a different object. |
Action |
Specify only keys of the requested type. |
INMJRE0026 | An auditable event object cannot be deleted |
Explanation |
It is not allowed to delete an auditable event. |
Action |
Correct the client program. |
INMJRE0027 | Concept must have a classification scheme ancestor |
Explanation |
The concept used for an internal classification has to belong to a classification scheme. |
Action |
Supply a correct concept for an internal classification. |
INMJRE0028 | {0} parameter must not be null |
Explanation |
The function shown on the call stack must not be called with a null value. |
Action |
Correct the client program. |
INMJRE0029 | Concept must not have a parent |
Explanation |
If a ClassificationScheme is created from a concept, then this concept must not have a parent. |
Action |
Supply a correct concept. |
INMJRE0030 | Invalid value type: {0} |
Explanation |
ClassificationScheme.setValueType() was called with an invalid value type. |
Action |
Supply a valid value type. |
INMJRE0031 | The classification scheme to be deleted still has children |
Explanation |
A classification scheme cannot be deleted if it has child concepts. |
Action |
Delete the child concepts before deleting the classification scheme. |
INMJRE0032 | Parent not allowed for concept |
Explanation |
The parent of a concept has to be a classification scheme or another concept. |
Action |
Supply a valid parent. |
INMJRE0034 | The concept to be deleted still has children |
Explanation |
A concept cannot be deleted if it has child concepts. |
Action |
Delete the child concepts before deleting the concept. |
INMJRE0035 | Invalid value for {0} ({1}) |
Explanation |
An internal error occurred during the XML serialization of Java objects. |
Action |
Please contact your software supplier. |
INMJRE0036 | Invalid string value for {0} ({1}) |
Explanation |
An internal error occurred while deserializing an XML document to a Java object. |
Action |
Please contact your software supplier. |
INMJRE0037 | The external link to be deleted still has linked objects |
Explanation |
An external link cannot be deleted if it has linked objects. |
Action |
Remove the external link from its linked objects before deleting it. |
INMJRE0039 | Cannot add a non-KeyRef to a KeyRefList |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMJRE0040 | toArray failed with attached JAXRException while resolving an object reference |
Explanation |
An exception occurred while copying a collection to an array. See the "caused by" message in the stack trace for the cause of the problem. |
Action |
Please contact your software supplier. |
INMJRE0041 | RegistryObjectIterator failed with attached JAXRException while resolving an object reference |
Explanation |
An exception occurred while iterating a query result. See the "caused by" message of the stack trace for the cause of the problem. |
Action |
Please contact your software supplier. |
INMJRE0042 | Invalid locale |
Explanation |
An internal error occurred while deserializing an XML document to a Java object. |
Action |
Please contact your software supplier. |
INMJRE0043 | The organization to be deleted still has child organizations |
Explanation |
An organization cannot be deleted if it has child organizations. |
Action |
Delete the child organizations before deleting the organization. |
INMJRE0044 | The organization to be deleted still has services |
Explanation |
An organization cannot be deleted if it has child services. |
Action |
Remove the services before deleting the organization. |
INMJRE0045 | The organization to be deleted still has users |
Explanation |
An organization cannot be deleted if it has users. |
Action |
Remove the users before deleting the organization. |
INMJRE0046 | Invalid stability value: {0} |
Explanation |
The setStability() method was called with an invalid stability value. |
Action |
Supply a valid stability value. |
INMJRE0047 | This registry provider does not support client supplied keys |
Explanation |
This registry provider does not support client supplied keys. |
Action |
Do not call the setKey() method. |
INMJRE0048 | Internal error: duplicate key in object cache "{0}" |
Explanation |
This internal error indicates an inconsistency in the object cache. |
Action |
Please contact your software supplier. |
INMJRE0049 | Cannot modify object type classification |
Explanation |
An instance of a user-defined type cannot be assigned another object type classification. |
Action |
Correct the client program. |
INMJRE0050 | Duplicate object type classification |
Explanation |
An instance of a user-defined type can only be classified with one concept from the "ObjectType" classification scheme. |
Action |
Correct the client program. |
INMJRE0051 | Cannot remove object type classification |
Explanation |
For instances of user-defined types it is not allowed to remove the classification that represents the object type. |
Action |
Correct the client program. |
INMJRE0052 | This object ({0}) is deprecated and must not be referenced |
Explanation |
A deprecated object must not be referenced in any way by another object. |
Action |
Do not create references to deprecated objects. |
INMJRE0053 | An object to be deleted has not been previously saved |
Explanation |
Only objects that have been previously saved can be deleted. |
Action |
Correct the client program. |
INMJRE0054 | The "{0}" object to be deleted ({1}) is the target of the "{2}" association "{3}". The source of the association is the {4} object "{5}" with key "{6}". |
Explanation |
An object cannot be deleted if it is still the target of an association. |
Action |
Delete the association before deleting the object. |
INMJRE0055 | The registry package to be deleted still has members |
Explanation |
A registry package cannot be deleted if it has member objects. |
Action |
Remove the member objects from the package before deleting it. |
INMJRE0056 | Cannot modify the name of a slot after it was added to a registry object |
Explanation |
The name of a slot cannot be changed after the slot was added to a registry object. |
Action |
Correct the client program. |
INMJRE0057 | Invalid namespace ''{0}'' of type |
Explanation |
The namespace of a type must be a valid URI. |
Action |
Correct the namespace. |
INMJRE0058 | Invalid XML stream |
Explanation |
An internal error occurred while deserializing an XML document to a Java object. |
Action |
Please contact your software supplier. |
INMJRE0059 | XML parsing error |
Explanation |
An internal error occurred while deserializing an XML document to a Java object. |
Action |
Please contact your software supplier. |
INMJRE0060 | STAX configuration error |
Explanation |
An internal error occurred while deserializing an XML document to a Java object. |
Action |
Please contact your software supplier. |
INMJRE0061 | Invalid URL value |
Explanation |
An internal error occurred while deserializing an XML document to a Java object. |
Action |
Please contact your software supplier. |
INMJRE0062 | Invalid boolean value for attribute {0} |
Explanation |
An internal error occurred while deserializing an XML document to a Java object. |
Action |
Please contact your software supplier. |
INMJRE0063 | Incomplete object ({0} is missing or does not have a value) |
Explanation |
The indicated required part of an object was missing when an object was to be saved. |
Action |
Correct the client program. |
INMJRE0064 | Cannot add an existing association to another object |
Explanation |
It is not possible to add the same association object to several separate registry objects. |
Action |
Create a new association object. |
INMJRE0065 | Cannot add an existing classification to another object |
Explanation |
It is not possible to add the same classification object to several separate registry objects. |
Action |
Create a new classification object. |
INMJRE0066 | Cannot add an existing external identifier to another object |
Explanation |
It is not possible to add the same external identifier object to several separate registry objects. |
Action |
Create a new external identifier object. |
INMJRE0067 | Unexpected owner type |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INMJRE0068 | Cannot delete the pre-defined object with key "{0}" |
Explanation |
The CentraSite Registry/Repository database is installed with some pre-defined JAXR objects that are required for CentraSite operation. These objects must not be deleted. |
Action |
Do not delete pre-defined objects. |
INMJRE0069 | Incomplete principal |
Explanation |
A CentraSitePrincipal has to be either an href representing a user or a group, or an "all" indicator, or an "authenticated" indicator, or an "unauthenticated" indicator. None of these were set. |
Action |
Create a correct CentraSitePrincipal object. |
INMJRE0070 | Cannot set instance based security for objects of type {0} |
Explanation |
Instance based security cannot be set for the following object types: AuditableEvent, Association, Classification, ExternalIdentifier, ServiceBinding and SpecificationLink. |
Action |
Do not try to set instance based security for these object types. |
INMJRE0071 | Failed with attached JAXRException |
Explanation |
Comparison of two key references failed. See the "caused by" message in the stack trace for the cause of the failure. |
Action |
Please contact your software supplier. |
INMJRE0072 | A ServiceBinding cannot have both a TargetBinding and an AccessURI |
Explanation |
For a ServiceBinding object, TargetBinding and AccessURI are mutually exclusive. |
Action |
Choose either TargetBinding or AccessURI. |
INMJRE0073 | Expected empty XML element {0}, but found content "{1}" |
Explanation |
An internal error occurred while deserializing instance based security information to a Java object. |
Action |
Please contact your software supplier. |
INMJRE0074 | Trying to use a closed connection (created by {0} at "{1}", closed at "{2}") |
Explanation |
A previously closed connection must not be used any more. |
Action |
Open a new connection. |
INMJRE0075 | A concept object must not have a HasParent association |
Explanation |
In order to allow for a proper mapping between JAXR and UDDI, a concept object must not have a HasParent association. |
Action |
Do not create HasParent associations for concept objects. |
INMJRE0076 | Internal error: object type concept not found |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMJRE0077 | The operation "{0}" can only be called for objects of type "{1}" |
Explanation |
Each operation belongs to one object type, and it can only be executed on objects of that type. |
Action |
Call the operation only for objects of the correct type. |
INMJRE0078 | Internal error: method should not be called |
Explanation |
Internal error. |
Action |
Do not call this method. |
INMJRE0079 | Invalid status value: {0} |
Explanation |
An invalid status value was specified. |
Action |
See the JAXR javadoc for correct status values. |
INMJRE0080 | The status of the deprecated object ({0}) cannot be modified |
Explanation |
The status of a deprecated object cannot be modified. |
Action |
Undeprecate the object before modifying its status. |
INMJRE0082 | A concept ({0}) in the ObjectType classification scheme is to be saved without an external link to an XML schema file |
Explanation |
Concepts in the ObjectType classification scheme represent JAXR object types. These concepts have to have an external link to an XML schema file (XSD). |
Action |
Supply an XSD file for this concept. |
INMJRE0087 | Invalid value ''{0}'' of property ''{1}'' |
Explanation |
The given value does not match the declared datatype of the property. |
Action |
Correct the value. |
INMJRE0088 | The concept to be deleted ({0}) is used by a classification ({1}). The classification belongs to the {2} object with key "{3}". |
Explanation |
A concept must not be deleted if it is used by a classification. |
Action |
Remove the classification before deleting the concept. |
INMJRE0089 | Trying to add a concept with the already existing value "{0}" under the parent object with key "{1}". |
Explanation |
Concepts under the same parent object must have unique values. |
Action |
Choose a different value for the new concept. |
INMJRE0090 | Invalid slot name: "{0}" |
Explanation |
In the CentraSite JAXR implementation a JAXR slot name has to have the format {uri}localname, where the {uri} part is optional. The localname has to be a valid NCName according to the XML specification. Basically this means it may start with a letter or an '_' character, followed by letters, digits, or the characters '_', '.', '-'. In particular, the localname must not contain any whitespace characters. |
Action |
Supply a valid slot name. |
INMJRE0091 | Invalid concept used as association type: "{0}" |
Explanation |
Only concepts from the classification scheme "AssociationType" may be used as association types. |
Action |
Choose a valid concept. |
INMJRE0092 | Commit or rollback not allowed if connection does not have client controlled transactions |
Explanation |
Only JAXR connections that were created with com.centrasite.jaxr.ClientTransaction=yes support commit and rollback operations. |
Action |
Correct the JAXR client program. |
INMJRE0093 | The value "{0}" of slot "{1}" is not a valid "{2}". |
Explanation |
The given value does not conform to the datatype as specified in the type definition. |
Action |
Specify a valid value. |
INMJRE0094 | Trying to modify the value of the ObjectType concept "{0}". |
Explanation |
It is not allowed to modify the value of a concept in the classification scheme ObjectType. |
Action |
Correct the client program. |
INMJRE0095 | Invalid concept value: {0} |
Explanation |
As described in the JAXR standard, a concept value has to be a valid NCName. |
Action |
Provide a valid concept value. |
INMJRE0096 | Trying to use an internal classification scheme ({0}) for an external classification. |
Explanation |
An external classification requires an external classification scheme. |
Action |
Supply a correct classification scheme. |
INMJRE0097 | Trying to save object "{0}" which is marked to be modified without lock. |
Explanation |
Objects which are marked to be modified without lock cannot be saved. |
Action |
Correct the client program. |
INMJRE0098 | Trying to modify an outdated object ("{0}") |
Explanation |
The application tried to modify a registry object which has been modified by someone else in the meantime. |
Action |
Make sure to modify only the latest version of a registry object. |
INMJRE0099 | Repository access error. |
Explanation |
An error occurred accessing the repository. |
Action |
Ensure the repository is available. Check there are no resource issues (e.g. lack of disk space). |
INMJRE0100 | Lock not available for object "{0}" |
Explanation |
The requested lock could not be granted. |
Action |
Wait until the lock is available. |
INMJRE0103 | Cannot handle a collection of values with a simple ParameterInstance |
Explanation |
A simple non-array ParameterInstance is associated with a single value. |
Action |
Use a single value. |
INMJRE0104 | ParameterType mismatch: requested {0}, present {1} |
Explanation |
The value(s) of a ParameterInstance have to correspond to the type of the respective ParameterTemplate. |
Action |
Read / set values according to the ParameterType. |
INMJRE0105 | The readonly property "{0}" must not be modified. |
Explanation |
Readonly properties can only be added to new objects. Existing property values must not be changed. |
Action |
Do not modify readonly properties. Do not add readonly properties to existing objects. |
INMJRE0106 | Login rejected, user "{0}" not registered |
Explanation |
Each user has to be registered before being used for login. |
Action |
Register the user. |
INMJRE0107 | The "login user" option must not be modified for existing users. |
Explanation |
The "login user" option can only be assigned to new users. |
Action |
Do not modify an existing user's "login user" option. |
INMJRE0108 | For an existing user with "login user" option, the name must not be changed. |
Explanation |
A user with "login user" option has to keep his name. |
Action |
Do not modify the name of a user with "login user" option. |
INMJRE0109 | Invalid URI specified for principal: {0}. |
Explanation |
The URI specified for the principal is not valid. It must be an absolute URI or one with an absolute path. The scheme of "ino:" is not a valid scheme. |
Action |
Ensure that the URI is valid. |
INMJRE0110 | "post insert" policy event failed for RegistryObject ("{0}") |
Explanation |
The enclosed exception explains the reason of the failure. |
Action |
Analyze the enclosed exception. |
INMJRE0111 | "post update" policy event failed for RegistryObject ("{0}") |
Explanation |
The enclosed exception explains the reason of the failure. |
Action |
Analyze the enclosed exception. |
INMJRE0112 | "post delete" policy event failed for RegistryObject ("{0}") |
Explanation |
The enclosed exception explains the reason of the failure. |
Action |
Analyze the enclosed exception. |
INMJRE0113 | Please set the mandatory parameter {0} before activating the policy |
Explanation |
The policy activation verifies whether all mandatory paramters are set. 0 - Name of the mandatory parameter which was not set. |
Action |
Please set all the mandatory parameters before activating the policy |
INMJRE0114 | Action {0} does not match the scope of the policy {1} |
Explanation |
The selected action does not match the scope of the policy 0 - Name of the action 1 - Name of the policy. |
Action |
Please ensure that the selected action matches the scope of the policy. |
INMJRE0115 | The name of the default organization must not be changed. |
Explanation |
The name of the default organization must not be changed. |
Action |
None |
INMJRE0117 | Name not specified for user with "login user" option |
Explanation |
A user without a name cannot have the "login user" option. |
Action |
Specify a user name. |
INMJRE0119 | Enumeration not allowed for data type {0} |
Explanation |
Enumerations are not allowed for data types InternationalString and InternationalRichText. |
Action |
Do not specify the enumeration option for these data types. |
INMJRE0120 | Internal error: missing ExternalLink to schema document |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INMJRE0121 | Internal error: target of {0} external link does not exist. |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INMJRE0122 | Duplicate type name {0} |
Explanation |
Each object type is identified by a name consisting of a namespace and a schema name. This name has to be unique. |
Action |
Provide a unique type name. |
INMJRE0123 | Trying to remove the primary contact from organization {0} ({1}). |
Explanation |
Each organization has to have a primary contact. It is not allowed to remove the primary contact. |
Action |
Do not remove the primary contact from an organization. |
INMJRE0124 | Cannot delete an ObjectType concept ({0}) |
Explanation |
The taxonomy "ObjectType" contains concepts that represent object types. It is not allowed to delete these concepts. |
Action |
Do not delete ObjectType concepts. |
INMJRE0125 | The user "{0}" ({1}) is the owner of, or modified the "{2}" object "{3}" ({4}) |
Explanation |
A user who still owns an object cannot be deleted. Also, if the user modified some object, and the corresponding audit trail entry is still present, deletion is rejected. However, the audit trail can be purged, and after all modification audit trail entries are purged, user deletion will be allowed. |
Action |
Delete all of the user's objects before deleting the user. |
INMJRE0126 | Attempt to modify a readonly privilege |
Explanation |
Readonly privileges must not be modified. |
Action |
Do not modify a readonly privilege. |
INMJRE0127 | Unsupported data type '{0}' |
Explanation |
The requested datatype is not supported. |
Action |
This is an internal error. Please contact your software supplier. |
INMJRE0128 | Illegal usage of deny ACE |
Explanation |
An ACE with deny can only be used with principal ALL and privilege ALL. |
Action |
Correct the ACE. |
INMJRE0129 | Not a valid revision object |
Explanation |
The object specified is not a object from the revision part. |
Action |
Check objects for the revision restore. |
INMJRE0130 | Expected revision object not present |
Explanation |
Unexpectedly a revision object could not be located. Obviously there is no version present of the actual object. |
Action |
Contact your software supplier because there is a structural problem with the revision part. |
INMJRE0131 | Revision object must not be modified ("{0}") |
Explanation |
Revision object must not be modified, these objects are readonly. |
Action |
Check your objects. |
INMJRE0132 | Invalid revision object encountered ("{0}") |
Explanation |
Invalid revision object encountered. The keys must be the same but are different. |
Action |
Check registry objects. |
INMJRE0133 | The "{0}" to be deleted ({1}) is an intermediate version object |
Explanation |
The object to be deleted is a target of a version association and must not be explicitly deleted. |
Action |
To delete objects of old versions use the purge() methods of the VersionManager interface. |
INMJRE0134 | Login rejected, user "{0}" not active |
Explanation |
Deactivated users cannot log in. |
Action |
Activate the user. |
INMJRE0135 | Association type "{0}" already used in this asset type |
Explanation |
There can be only one association of type "Implements" per asset type. You attempted to create such an attribute, but one exists already. |
Action |
Use a different association type. |
INMJRE0136 | Uploaded computed profile zip does't contain computed implementation |
Explanation |
the zip does not the class which implements the interfaces like {0} |
Action |
Make sure the computed profile implementation bundled in zip |
INMJRE0138 | User "{0}" is still the primary contact of organization "{1}" |
Explanation |
A user cannot be deleted if this user is still the primary contact of an organization. |
Action |
Do not delete primary contact users. |
INMJRE0139 | Taxonomy "{0}" still used to classify object "{1}" |
Explanation |
An external taxonomy cannot be deleted as long as it is referenced by classifications. |
Action |
Remove the classifications before deleting the taxonomy. |
INMJRE0140 | The association type to be deleted ({0}) is used by an association ({1}). The association belongs to the {2} object "{3}". |
Explanation |
An association type cannot be deleted if there are still associations of that type. |
Action |
Delete all associations of that type before deleting the association type. |
INMJRE0141 | Untyped RegistryEntry "{0}" must not be saved |
Explanation |
Java RegistryEntry objects are used to represent instances of user-defined types. In order to make a RegistryEntry an instance of a type, it has to be classified with the corresponding type concept. |
Action |
Save only typed RegistryEntries. |
INMJRE0142 | must not replace existing type concept |
Explanation |
This is an internal error. |
Action |
Please contact your software supplier. |
INMJRE0143 | duplicate target type "{0}" |
Explanation |
For a RelationShip attribute the same target type was specified twice. |
Action |
Specify each target type only once. |
INMJRE0144 | invalid maxOccurs value "{0}" |
Explanation |
Allowed values for maxOccurs are "1" and "unbounded". |
Action |
Specify a valid value. |
INMJRE0145 | invalid minOccurs value "{0}" |
Explanation |
Allowed values for minOccurs are "0" and "1". |
Action |
Specify a valid value. |
INMJRE0146 | Missing taxonomy for classification attribute "{0}" |
Explanation |
Each classification attribute needs a taxonomy. |
Action |
Specify a taxonomy. |
INMJRE0147 | For the classification attribute "{0}", the default value "{1}" does not belong to the taxonomy "{2}". |
Explanation |
The default value needs to belong to the taxonomy. |
Action |
Select a concept from the taxonomy as the default value. |
INMJRE0148 | Missing association type for relationship attribute "{0}" |
Explanation |
Each relationship attribute needs an association type. |
Action |
Specify an association type. |
INMJRE0149 | duplicate attribute name "{0}" |
Explanation |
Attribute names have to be unique within classification, relationship, and file attributes. |
Action |
Choose a unique attribute name. |
INMJRE0150 | trying to access a deleted type |
Explanation |
After a type was deleted, the corresponding Java instance must no longer be used. |
Action |
Correct the client program. |
INMJRE0151 | must not rename existing type's schema name |
Explanation |
The schema name uniquely identifies a type, it must not be modified. |
Action |
Do not rename an existing schema name. |
INMJRE0152 | Cannot save object due to missing lifecycle state. The object "{0}" is classified with lifecycle state "{1}" which does not exist. |
Explanation |
A call to saveObjects fails, when a saved object contains a lifecycle state classification which does not exist. This can occur after importing objects, when the lifecycle model data has not been imported beforehand. |
Action |
Make sure that any referenced lifecycle models are available in the registry before importing objects that refer to them. |
INMJRE0153 | Invalid attribute "{0}" applied to object of type "{1}" |
Explanation |
A setAttributeValue() or getAttributeValue() operation was issued against a registry object whose type does not contain the specified attribute. |
Action |
Correct the application. |
INMJRE0154 | Conflicting aggregation settings |
Explanation |
A relationship attribute can be aggregating, or reversely aggregating, but not both. |
Action |
Choose a correct aggregation setting. |
INMJRE0155 | "{0}" is not a virtual type |
Explanation |
The given type concept is not a virtual type. |
Action |
Please supply a virtual type. |
INMJRE0156 | The delete operation failed due to a hidden association. |
Explanation |
The object to be deleted is still the target of an association. However, the user that tries to delete the object does not have view permissions on the association and its source object. Probably a CentraSite administrator with full permissions is required to perform the delete operation. |
Action |
Please contact your CentraSite administrator. |
INMJRE0158 | The locale {0} is not contained in the set of restricted locales. |
Explanation |
The set of restricted locales defines which locales may be used when creating a value for an InternationalString. |
Action |
Choose a different locale. |
INMJRE0159 | Invalid or missing default locale |
Explanation |
When defining the set of restricted locales, exactly one locale needs to be marked as the default locale. |
Action |
Specify a proper default locale. |
INMJRE0160 | The "{0}" package to be deleted ({1}) still has members, e.g. the {2} object "{3}" with key "{4}". |
Explanation |
A registry package cannot be deleted if it still has members. |
Action |
Delete the members before deleting the registry package. |
INMJRE0161 | no value provided for required attribute {0} of {1} "{2}" |
Explanation |
The attribute is defined with the "required" option, but the attribute value was not supplied when storing the object. |
Action |
Provide a value for the attribute. |
INMJRE0162 | too many values provided for single-value attribute {0} of {1} "{2}" |
Explanation |
For single-value attributes, at most one value may be provided. |
Action |
Provide a correct attribute value. |
INMJRE0163 | Internal error: cannot construct a RegistryObject from {0}. |
Explanation |
This is an internal error. |
Action |
Contact your software provider. |
INMJRE0164 | Internal error: missing object id for {0} |
Explanation |
This is an internal error. |
Action |
Contact your software provider. |
INMJRE0165 | Cannot modify attribute {0} of type {1} to be required, because it does not exist in the object with key "{2}" |
Explanation |
While updating a type description, an attribute was modified to be a required attribute. This modification however can only be done when the attribute is already present in all existing objects of the type (which is trivially true if there are no existing objects), or it has been equipped at the same time with a default value. |
Action |
Define a default value for the attribute, or refrain from setting the attribute to "required", then retry the modification only after the attribute has been added to all existing objects of the given type. |
INMJRE0166 | Failed to check that the given profile is a computed profile |
Explanation |
While parsing the uploaded zip file, an unexpected exception occurred. |
Action |
Please make sure the uploaded zip file is not corrupted. |
INMJRE0167 | Uploaded computed profile implementation zip file does not contain profile implementation class, which implements the interface like {0} |
Explanation |
The uploaded computed profile implementation zip file does not contain the class that implements the interface like {0}. |
Action |
Please make sure the zip file contains the computed profile implementation. |
INMJRE0168 | Default value should be given for all required attributes when the types have instances. Please provide the default value for the required attribute "{0}". |
Explanation |
When updating an asset type which already has instances, all the required attributes of that type should be provided with default values. |
Action |
Ensure that all the required attributes of the edited asset type have default values. |
INMJRE0169 | The predefined attribute cannot be deleted |
Explanation |
You cannot delete the predefined attributes. |
Action |
You cannot delete the predefined attribute. |
INMJUE0001 | Check your access rights and the proxy settings |
Explanation |
The accessing user does not have sufficient privileges for the target object. |
Action |
Do the action as a more privileged user. |
INMJUE0005 | No privilege to access target object from object: {0} |
Explanation |
The accessing user does not have sufficient privileges for the target object. |
Action |
Do the action with a more privileged user. |
INMJUE0006 | Uploaded computed profile implementation zip does't contain profile implementation class, which implements the interface like {0} |
Explanation |
The uploaded computed profile implementation zip file does not contain the class that implements the interface like the one shown. |
Action |
Make sure the zip file contains the computed profile implementation. |
INMJUE0007 | Failed to check that a given profile is a computed profile |
Explanation |
While parsing the uploaded zip file an unexpected exception occurred. |
Action |
Make sure that the uploaded zip file is not corrupted. |
INMJUW0002 | The associated object of type "External Link" could not be deleted |
Explanation |
This can happen while deleting virtual services. |
Action |
No action required. |
INMJUW0003 | The associated object of type "WS-Policy attachment" could not be deleted |
Explanation |
This can happen when deleting virtual services. |
Action |
No action required. |
INMJUW0004 | The associated object of type "Associated with" could not be deleted |
Explanation |
This can happen when deleting virtual services. |
Action |
No action required. |
INMLFE0001 | Provider not set for {0} |
Explanation |
The LCM factory could not be initialized since the property for the provider class is not set appropriately. |
Action |
Please check the javadoc of the LCM API to set the appropriate property. |
INMLFE0002 | Provider {0} not found |
Explanation |
The LCM provider class could not be loaded. |
Action |
Please check that the name of provider class is appropriately set and is available for class loading. |
INMLFE0003 | Provider {0} could not be instantiated |
Explanation |
An exception occurred while trying to load the provider class. |
Action |
Please check that the name of provider class is appropriately set and is available for class loading |
INMLFE0004 | No initial state defined |
Explanation |
There should be an initial state defined for any lifecycle model. |
Action |
Please make sure that there is an initial state defined for the lifecycle model. |
INMLFE0005 | The state(s) {0} are unreachable |
Explanation |
It should be possible to traverse to each state within a lifecycle model from the initial state 0 - name(s) of the state(s) unreachable from the initial state. |
Action |
Please make sure that each state is reachable from the initial state in the lifecycle model. |
INMLFE0006 | A lifecycle model should have at least one end state |
Explanation |
Any lifecycle model should have at least one state that does not have a next state. |
Action |
Please make sure that the lifecycle model has at least one end state. |
INMLFE0007 | The given object type {0} cannot be LCM enabled |
Explanation |
Only asset types, policies and lifecycle models can be LCM enabled 0 - name of the invalid object type |
Action |
Please make sure that an appropriate object type that can be LCM enabled is used. |
INMLFE0008 | The state {0} cannot be set as an initial state. The state is currently not present in the lifecycle model. |
Explanation |
Only states which are already part of the lifecycle model can be set as an initial state. |
Action |
Please make sure that you add the state to the lifecycle model before setting it as the initial state. |
INMLFE0009 | The state {0} cannot be set as a preferred next state. The state is currently not a next state. |
Explanation |
Only states which are part of the next states can be set as preferred next state 0 - name of the invalid preferred next state. |
Action |
Please ensure that the state is part of the next states before setting it as the preferred next state. |
INMLFE0010 | Each lifecycle model should belong to an organization |
Explanation |
Each LCM should belong to one organization. |
Action |
Please assign an organization to which the lifecycle model belongs. |
INMLFE0011 | It is only possible to define a lifecycle model for lifecycle models in CentraSite Active SOA version |
Explanation |
A lifecycle model for lifecycle models can only be defined in the CentraSite Active SOA edition. |
Action |
No action required. |
INMLFE0012 | {0] is not a type in CentraSiteRegistryTypes taxonomy |
Explanation |
The concept used for the registry type should belong to the predefined CentraSiteRegistryTypes taxonomy 0 - key of the invalid concept. |
Action |
Please use a concept that belongs to the predefined CentraSiteRegistryTypes taxonomy. |
INMLFE0014 | A type with the given name {0} was not found |
Explanation |
No object type was found with the given name 0 - name of the given object type. |
Action |
Please specify a valid type name. |
INMLFE0015 | No active lifecycle model for the given registry object found |
Explanation |
The given registry object is not associated with any active lifecycle model. |
Action |
No action required. |
INMLFE0016 | The given state {0} is not a valid follow up state of {1} for the given registry object {2} |
Explanation |
The current state of the registry object does not have a state transition to the specified target state. 0 - specified target state 1 - current state of the registry object 2 - name of the registry object. |
Action |
Please ensure that there is a valid state transition from the current state of the registry object to the specified target state. |
INMLFE0017 | The given registry object is never in a work flow to change its state |
Explanation |
The given registry object cannot be approved or rejected since it was never in a work flow to change its state. |
Action |
No action required. |
INMLFE0018 | For each object type, only one lifecycle model can be active per organization |
Explanation |
For any object type and organization, there can be at most one active LCM. |
Action |
Please make sure that there are no active LCMs associated with the given object type and organization, before trying to activate this LCM. |
INMLFE0019 | A promotion node can be set only on the final states of the lifecycle model |
Explanation |
Promotion nodes be only be set for final states of a lifecycle model. |
Action |
Please make sure that promotion nodes are set only for final states. |
INMLFE0020 | The registry object is in a workflow to change its state |
Explanation |
Next states cannot be determined for a registry object with a pending state change. |
Action |
No action required. |
INMLFE0021 | The given registry object is not a user or a role or a group that could be used to restrict transitions to the state |
Explanation |
The registry object used to restrict transitions to the state should be either a user or group or role. No other type of registry object can be used. |
Action |
Please make sure that the registry object used to restrict transitions to the state is either a user or a group or a role. |
INMLFE0022 | The current user is not allowed to perform the state transition |
Explanation |
The current user does not have the necessary permissions to perform the requested state transition. |
Action |
Please make sure that the current user has the necessary permissions to perform the requested state transition. |
INMLFE0024 | Failed to set the initial state for the registry object {0} |
Explanation |
The registry object could not be set to the initial state of the life cycle model since there is an approval work flow. |
Action |
Please make sure that there are no approval work flows triggered for the initial state of the LCM. |
INMLFE0026 | The lifecycle model is deleted! |
Explanation |
Deleted lifecycle models cannot be reused. |
Action |
Please use an existing lifecycle model and do not refer to deleted lifecycle models. |
INMLFE0027 | The lifecycle model is not associated with any types |
Explanation |
Each lifecycle model should be associated with at least one object type. |
Action |
Please choose at least one object type which will be associated with the lifecycle model. |
INMLFE0028 | Internal error: User {0}/{1} does not belong to any organization |
Explanation |
The logged in user does not belong to any organization 0 - Name of the user 1 - Key of the user. |
Action |
Please make sure that the logged in user belongs to some organization. |
INMLFE0029 | Internal error: please specify the organization for which the lifecycle model has to be found |
Explanation |
A lifecycle model can be found only in the context of an organization for which the registry object is to be created. |
Action |
Please specify the organization for which the lifecycle model has to be found. |
INMLFE0030 | {0} lifecycle model cannot be modified |
Explanation |
A lifecycle model which is active or in a state after active cannot be modified. |
Action |
Please ensure that the lifecycle model is in a state before active so that it can be modified. |
INMLFE0031 | The lifecycle model cannot be deleted! |
Explanation |
The lifecycle model could not be deleted because of an internal exception. |
Action |
Please look at the exception for more details. |
INMLFE0032 | The model cannot be set to state {0} |
Explanation |
The lifecycle model could not be set to the given state since it is not a valid transition from the current state of the model 0 - name of the invalid state. |
Action |
Please make sure that the model is set to a state that is a valid transition from its current state. |
INMLFE0033 | Transition from any state to initial state is not allowed |
Explanation |
Transition from any state to initial state is not allowed. |
Action |
Transition from any state to initial state is not allowed. |
INMLFE0034 | The lifecycle model cannot be activated since the older version of this model could not be superseded |
Explanation |
The lifecycle model which is a newer version of some other model could not be activated since the older version model could not be marked as superseded. |
Action |
Please ensure that the older version model can be marked as superseded before activating the newer lifecycle model. |
INMLFE0035 | An active lifecycle model cannot be deleted |
Explanation |
An attempt was made to delete an active lifecycle model. |
Action |
An active lifecycle model cannot be deleted. |
INMLFE0036 | State transition can only be made between states which belong to the same lifecycle model |
Explanation |
There are state transitions which have been made between states which belong to different lifecycle models. |
Action |
Please ensure that the state transitions are not made between states of two different lifecycle models. |
INMLFE0037 | Lifecycle Model for Lifecycles cannot be deleted |
Explanation |
The predefined lifecycle model for lifecycles cannot be deleted. |
Action |
No action required. |
INMLFE0038 | Policy Lifecyle cannot be deleted |
Explanation |
The predefined lifecycle model for policies cannot be deleted. |
Action |
No action required. |
INMLFE0041 | Intermediate versions of a Lifecycle cannot be deleted using 'Delete' option |
Explanation |
There are two options to delete a lifecycle and its version objects, namely 'Delete' and 'Purge'. The 'Delete' option can be used only for the latest version of the lifecycle. |
Action |
Deletion will not be allowed. |
INMLYE0002 | Lifecycle Model Name should not be empty |
Explanation |
The model name is mandatory. |
Action |
Enter the model name. |
INMLYE0003 | Stage Name should not be empty |
Explanation |
The stage name is mandatory. |
Action |
Enter the stage name. |
INMLYE0005 | Only one row can be moved down |
Explanation |
For the order of the lifecycle state, only one row can be moved up or down. |
Action |
While moving down any lifecycle state, please ensure that only one state is selected. |
INMLYE0007 | Only one row can be moved up |
Explanation |
To order the LC State, only one row can be moved up. |
Action |
Lifecycle state order. |
INMLYE0008 | Lifecycle model(s) should be selected for saving report |
Explanation |
Saving a report should have one LCM object. |
Action |
Saving a report should have one LCM object. |
INMLYE0009 | Two state names cannot have the same name |
Explanation |
There is a duplicate state name. |
Action |
Choose a unique state name. |
INMPEE0003 | Namespace {0} does not match any of the possible namespaces {1} |
Explanation |
Service namespace is validated against the set of possible namespaces as specified by the policy. 0 - Namespace of the service 1 - Allowed namespaces from policy. |
Action |
Please ensure that the namespace of the service matches at least one of the allowed namespaces. |
INMPEE0009 | Policy {0} cannot be deactivated since an approval triggered by the policy for {1} {2} is in progress |
Explanation |
Since there is an approval which is in progress, this policy cannot be deactivated. 0 - Name of the policy 1 - Type of the object which is pending 2 - Name of the object which is pending. |
Action |
Please complete the approval flow for the specific object and then deactivate the policy. |
INMPEE0013 | Organization {0} should have Administrator |
Explanation |
Every organization should have an administrator assigned 0 - Name of the organization |
Action |
Please ensure that the organization has an administrator assigned to it. |
INMPEE0016 | {0} {1} must be classified by taxonomy {2} |
Explanation |
The given registry object is validated to be classified by the given taxonomy. 0 - Type name of the object 1 - Registry Object name 2 - Taxonomy node name. |
Action |
Please ensure that the registry object is classified by the given taxonomy. |
INMPEE0021 | Policy without any actions cannot be executed |
Explanation |
A policy without any actions cannot be executed. |
Action |
Please assign some actions to this policy. |
INMPEE0030 | Service WSDL size {0} does not conform with the specified size {1} |
Explanation |
The service WSDL size does not match the size specified by the policy. 0 - WSDL size of the service 1 - WSDL size specified in the policy. |
Action |
Please ensure that the WSDL size of the service conforms with the specified size. |
INMPEE0031 | {0} name {1} does not conform with the pattern {2} |
Explanation |
The registry object name does not match the specified pattern. 0 - Type of the registry object 1 - Name of the registry object 2 - Name pattern specified in the policy. |
Action |
Please ensure that the name of registry object conforms to the specified pattern. |
INMPEE0039 | Service Binding Type(s) {0} are missing in the WSDL. The mandatory bindings specified in the policy are {1} |
Explanation |
The binding types of the service are validated against the specified bindings. 0 - Violating binding types of the service 1 - Binding types specified by the policy. |
Action |
Please ensure that the service binding types conform to the specified binding types. |
INMPEE0043 | User does not have the permission to create {0} |
Explanation |
The user does not have the required permission to create an object of the given type. {0} refers to the object type for which the user is creating an instance. |
Action |
Please assign the necessary permissions to the user before trying to create an object of the type. |
INMPEE0045 | Namespace cannot be empty for {0} {1} |
Explanation |
The namespace of the applied object is empty. {0} - type of the applied object {1} - name of the applied object. |
Action |
Please ensure that the namespace is provided for the object. |
INMPEE0046 | Description is empty for {0} {1} |
Explanation |
The description of the registry object is empty. 0 - Type of the registry object 1 - Name of the registry object. |
Action |
Please make sure that the registry object has a non-empty and valid description. |
INMPEE0047 | Name is empty for {0} |
Explanation |
The name of the registry object is empty 0. - Type of the registry object. |
Action |
Please make sure that the registry object has a non-empty and valid name. |
INMPEE0048 | Policy {0} cannot be activated since there is a newer active version of this policy |
Explanation |
Since there is a newer version of this policy which is active, the policy cannot be activated. |
Action |
Please use the newest active version of the policy for enforcement. |
INMPEE0049 | Policy {0} cannot be activated since the older version of the policy could not be superseded |
Explanation |
The policy which is a newer version of some other policy could not be activated since the older version could not be marked as superseded. |
Action |
Please ensure that the older version policy can be marked as superseded before activating the newer policy. |
INMPEE0052 | {0} description {1} does not conform with the pattern {2} |
Explanation |
The registry object description does not conform to the pattern specified in the policy. 0 - Type of the registry object 1 - Description of the registry object 2 - Description pattern specified in the policy. |
Action |
Please ensure that the description of the registry object conforms to the specified pattern. |
INMPEE0057 | {0} {1} does not belong to an LCM state |
Explanation |
The registry object does not belong to an LCM state. 0 - Type name of the object 1 - Name of the object. |
Action |
Please ensure that the registry object is set to an appropriate LCM state. |
INMPEE0059 | {0} {1} belongs to state {2} which does not conform to the allowed states {3} |
Explanation |
The LCM state of the registry object is validated against the allowed states specified in the policy. 0 - Type name of the registry object 1 - Name of the registry object 2 - Current state name of the registry object 3 - Allowed states specified in the policy. |
Action |
Please ensure that the registry object is set to an appropriate LCM state. |
INMPEE0064 | {0} {1} does not have a value set for attribute {2} |
Explanation |
The registry object does not have a value set of the specified attribute. 0 - Type of the registry object 1 - Name of the registry object 2 - Attribute name specified in the policy. |
Action |
Please ensure that the object has a value set for the specific attribute. |
INMPEE0066 | {0} {1} has value {2} set for attribute {3} which does not conform to the allowed values {4} |
Explanation |
The registry object has a value set of the specified attribute which does not conform to the allowed values. 0 - Type of the registry object 1 - Name of the registry object 2 - Attribute value of the registry object 3 - Attribute name specified in the policy 4 - Allowed attribute values specified in the policy. |
Action |
Please ensure that the object has an appropriate value set for the specific attribute. |
INMPEE0069 | Policy {0} cannot be activated as some mandatory action parameters are not set |
Explanation |
The policy has some mandatory parameters which are not set, so the policy cannot be activated. 0 - Name of the policy. |
Action |
Please ensure that all mandatory parameters of the policy are set before activation. |
INMPEE0071 | Priority for a policy should be between {0} and {1} |
Explanation |
The priority for a policy should be within the specified limits. |
Action |
Please enter a priority within the specified limits. |
INMPEE0072 | Policy action rule {0} is invalid |
Explanation |
The action.properties file is not accessible for this policy action rule. 0- name of the policy action. |
Action |
Please enter the correct rule file for the policy action. |
INMPEE0073 | {0} is not a valid Groovy script |
Explanation |
The action file is not a valid Groovy script. 0 – name of the Groovy script. |
Action |
Please upload a valid Groovy script. |
INMPEE0074 | Result message not set for Groovy action {0} |
Explanation |
The Groovy script did not set the result object. 0 – name of the Groovy action. |
Action |
Set the result inside the Groovy action. |
INMPEE0087 | Active user {0} cannot be deleted. |
Explanation |
Only deactivated users can be deleted in CentraSite. {0} specifies the user name. |
Action |
Deactivate the user before deletion. |
INMPEE0089 | Organization level permission for {0} is not created yet for organization {1} |
Explanation |
Firstly we have to create an organization before creating any registry object for an organization. This is because organization level permissions of that organization are used in instance level permission for those registry objects. 0 – name of the registry object 1 – name of the organization. |
Action |
Create the organization first. |
INMPEE0091 | User cannot update the role {0} with permissions that he does not have |
Explanation |
A user can assign permissions that he has to a role. If a user tries to update a role with a permission that he does not have, then this error will be thrown. 0 – name of the role. |
Action |
Please ensure that the user has the permissions that he is assigning to a role. |
INMPEE0092 | {0} cannot be deleted |
Explanation |
The default organization cannot be deleted. |
Action |
Do not try to delete the default organization. |
INMPEE0094 | Policy {0} cannot be activated since an active older version of the policy has a pending approval |
Explanation |
Since there is an older version of this policy which is active and has a pending approval, this newer policy version cannot be activated. 0 – name of the policy. |
Action |
Please ensure that any approval triggered by the older active version of this policy gets completed before activating the newer version. |
INMPEE0102 | Organization Primary Contact has to be an active user |
Explanation |
A deactivated user cannot become the primary contact of an organization. |
Action |
Please assign an active user as the primary contact of an organization. |
INMPEE0104 | User cannot assign the role {0} to a user/group that he cannot manage |
Explanation |
If a user with "Manage Users" permission in one organization tries to assign a role from another organization or a system level role to his own organization's user, then this error message will be thrown. |
Action |
The user needs to have the "Manage Users" permission of the role's organization (if it is an organization level role) or the user should have the "Manage System-wide Roles" permission if it is a system level role. Only then can the user assign that role to a user. |
INMPEE0105 | User cannot create the Role {0} with permissions that the user does not have |
Explanation |
A user can update the role only with the permissions that he possesses. If a user with Organization level "Manage Users" permission or "Manage System-wide Roles" permission tries to update a role then this user can assign only the permission that he/she already has, otherwise this error message will be thrown. |
Action |
Please ensure that the user has the permissions that he/she is assigning to a role. |
INMPEE0106 | Action class {0} not found in {1} |
Explanation |
The action class mentioned in the properties file should be present in the action rule archive. 0 – name of the executable class, 1 – name of the action rule archive. |
Action |
The action class mentioned in the properties file is not present in the action rule archive. Please make sure the class mentioned in the property file is present in the archive. |
INMPEE0110 | WS-I actions should not be combined with other actions in a single policy |
Explanation |
A policy containing WS-I actions cannot contain any actions other than WS-I policy actions |
Action |
Make sure WS-I actions are not combined with other actions in a single policy. |
INMPEE0111 | Dependent actions {0} for {1} is not included |
Explanation |
Dependent actions of a WS-I action are not included. 0 – name of the missing dependent WS-I action, 1 - name of the included WS-I action. |
Action |
Dependent actions of a WS-I action should be included in a policy. |
INMPEE0113 | There are no lifecycle states associated with the {0} event for the policy {1} and hence this policy cannot be activated |
Explanation |
The pre/post state change policy does not have any lifecycle states associated with it and hence the policy will not be executed for any state transition. Hence this policy cannot be activated. 0 - Pre/Post State Change event, 1 - Name of the policy. |
Action |
Please ensure that the policy is associated with the appropriate lifecycle states for the pre/post state change events |
INMPEE0114 | Lifecycle state {0} from {1} does not match the scope of the policy {2} |
Explanation |
The lifecycle state associated with the policy does not correspond to the object types specified in the scope of the policy. 0 - Name of the lifecycle state associated with this policy, 1 - Name of the lifecycle model to which this state belongs, 2 - Name of the policy. |
Action |
Please ensure that the lifecycle states associated to the policy belong to a lifecycle model whose object type conform to the object types specified in the policy scope |
INMPEE0115 | Consumer Registration Request {0} is not associated with any asset |
Explanation |
A consumer registration request object must be associated with an asset. 0 – Name of the consumer registration request. |
Action |
Associate the consumer registration request object with an asset using an association with the association type "relatedTo". The source object of the association is the consumer registration request. The target object of the association is the asset. |
INMPEE0118 | {0} {1} is pending on state change. So it cannot be modified or deleted. |
Explanation |
The object has a pending state change. So this object cannot be modified or deleted. 0 - Type of the object 1 - Name of the object. |
Action |
If you want to modify or delete the object, release the object from the pending state. If there are pending approvals, get them completed. |
INMPEE0120 | Attribute {0} is read only and hence cannot be set for {1} {2} |
Explanation |
Since the attribute is read only, the given attribute value cannot be set for the registry object. 0 - Name of the read only attribute, 1 - Type of the registry object, 2 - Name of the registry object. |
Action |
Please ensure that the chosen attribute is not a read only attribute. |
INMPEE0129 | Initial State {0} cannot be used to define policy on Pre-State Change event |
Explanation |
Pre-state change policies cannot be defined on initial states of any lifecycle model. 0 - Name of the initial state associated with the policy. |
Action |
Please use a lifecycle state other than the initial state to define the pre-state change policy. |
INMPEE0136 | Policy action {0} is used, so it cannot be edited or deleted |
Explanation |
If the policy action is used by any other policy, the policy action can't be edited or deleted. |
Action |
Before editing or deleting any policy action, the user has to verify whether any policy is using this action or not. |
INMPEE0142 | {0} {1} has a pending approval and hence cannot be moved |
Explanation |
The registry object has an approval in pending state. So it cannot be moved to a new owner and/or organization. 0 - Type of the registry object 1 - Name of the registry object. |
Action |
Please complete the pending approval for the registry object before moving it. |
INMPEE0143 | {0} {1} has a pending consumer registration request and hence cannot be moved |
Explanation |
The registry object has a pending consumer registration, so it cannot be moved to a new owner and/or organization. 0 - Type of the registry object 1 - Name of the registry object. |
Action |
Please complete the consumer registration request for the registry object before moving it. |
INMPEE0144 | {0} {1} is an internal object of CentraSite and hence cannot be moved |
Explanation |
Internal objects of CentraSite cannot be moved. |
Action |
Internal objects of CentraSite cannot be moved. |
INMPEE0145 | {0} {1} cannot be moved to inactive or internal users of CentraSite |
Explanation |
Ownership of the registry object cannot be transferred to inactive or internal users of CentraSite. 0 - Type of the registry object 1 - Name of the registry object. |
Action |
Please ensure that the new owner for the registry object is an active and non-internal user of CentraSite. |
INMPEE0146 | The mandatory attribute {0} does not have value for this object |
Explanation |
An attribute should have a value for a registry object if it is marked as required. |
Action |
Provide appropriate value(s). |
INMPEE0148 | Only user with CentraSite Administrator role can do the change ownership action |
Explanation |
Only a user with the CentraSite Administrator role can do the change ownership action. |
Action |
Please make sure that you log in as a user who has CentraSite Administrator role to perform the ownership change. |
INMPEE0149 | Only user with CentraSite Administrator role can do the change organization action |
Explanation |
Only a user with the CentraSite Administrator role can do the change organization action for assets. |
Action |
Please make sure that you log in as a user who has the CentraSite Administrator role to perform the organization change. |
INMPEE0150 | Internal users cannot be moved across organizations. |
Explanation |
If the user is trying to move any of the predefined or internal users from one organization to another organization, this error message will be displayed. |
Action |
Remove the predefined/internal users from the list for moving users across organizations. |
INMPEE0151 | Owner for the object {0} of type {1} is not present in CentraSite |
Explanation |
The owner for the object is not present in CentraSite. {0} - Name of the object {1} - Type of the object. |
Action |
The owner should not be allowed to be removed from CentraSite while owning some objects. So, identify how the owner was removed from CentraSite with this object dependency and report a bug. |
INMPEE0153 | View permission on {0} {1} is not available for {2} {3} |
Explanation |
The view permission on the registry object is not available for the specific user or group. 0 - Type of the registry object for which the profile permissions are being set 1 - Name of the registry object 2 - User or Group 3 - Name of the user or group. |
Action |
Please set the view permission on the registry object for the specific user or group before setting the profile permissions. |
INMPEE0154 | Modify permission on {0} {1} is not available for {2} {3} |
Explanation |
The modify permission on the registry object is not available for the specific user or group. 0 - Type of the registry object for which the profile permissions are being set 1 - Name of the registry object 2 - User or Group 3 - Name of the user or group. |
Action |
Please set the modify permission on the registry object for the specific user or group before setting the profile permissions. |
INMPEE0156 | The new owner {0} does not have create asset permission in organization {1} |
Explanation |
An attempt was made to move an asset to a user who does not have "create assets" permission in the asset's organization. |
Action |
Assign the Asset Provider role or any custom role which contains the "create assets" permission in the asset' organization to the target user. |
INMPEE0167 | The RejectHandler policy prohibited the operation for {0} {1} |
Explanation |
Operations like "move", "delete", etc. are only allowed for specific object types. |
Action |
Correct the application program. |
INMPEE0175 | Virtual Service {0} cannot be deleted because it has been deployed to the target. |
Explanation |
This error message is thrown when you are attempting to delete the virtual service which is deployed to a target. |
Action |
Undeploy the virtual service before attempting to delete. |
INMPEE0176 | Target information not available for the deployment operation. |
Explanation |
A target is mandatory for deployment operations of Virtual Service/Virtual XML service/Virtual REST service/Consumer Application/Aliases. |
Action |
Trigger deployment from the deployment profile. |
INMPEE0180 | IS Service Interface {0} should have at least one associated IS Service Object, hence the corresponding REST service is not created. |
Explanation |
The IS Service Interface object should have at least one associated IS Service Object. |
Action |
Make sure at least one IS Service Object (HTTP methods get, put, post and delete) is associated to the IS Service Interface and also make sure the name of the IS Service Object should contain the following strings (get, put, post and delete) appropriate to the method definition. |
INMPEE0181 | REST Service {0} should have at least one native endpoint, hence the corresponding REST service is not created. |
Explanation |
The REST service published from the webMethods product suite should have at least one native endpoint. |
Action |
Make sure the port attribute (IS Server object) has a value defined. |
INMPEE0184 | Cannot remove the existing life cycle state from the object {0} |
Explanation |
It is not possible to remove the existing life cycle state from the given object |
Action |
No action required. |
INMPEE0185 | {0} {1} must be classified by at least one of {2} |
Explanation |
The given registry object is validated to be classified by the given taxonomy or category. 0 - Type name of the object 1 - Registry Object name 2 - Taxonomy node name or category node name. |
Action |
Please ensure that the registry object is classified by the given taxonomy or category. |
INMPEE0190 | Unable to delete the exported archive file |
Explanation |
The intermediate archive file created for asset promotion could not be deleted. |
Action |
No action required. |
INMPEE0204 | The mandatory attribute {0}, of {1} "{2}" does not have a value |
Explanation |
The mandatory attribute {0} of {2} created from type {1} does not have a value. Attribute {0} has been marked "required" in the definition of type {2} and hence should have a value. |
Action |
Provide a value for the attribute {0} or provide a default value for the attribute in the definition of type {2}. |
INMPEE0206 | The validation pattern "{0}" is invalid for policy "{1} at {2}". Repair the regular expression pattern. |
Explanation |
The validation policy action of the specified policy contains an invalid/unsupported regular expression pattern. |
Action |
Specify a syntactically correct regular expression for the policy action. |
INMPEE0210 | Key Generator Policy is not enabled for the API {0} |
Explanation |
The Key Generator Policy for the given API is not generated. |
Action |
Contact the API provider. |
INMPEE0211 | Onboarding Organization {0} with Administrator User {1} has failed |
Explanation |
Onboarding the given organization with the given administrator user of that organization has failed. |
Action |
Contact the CentraSite administrator. |
INMPEE0212 | Onboarding User {0} in Organization {1} has failed |
Explanation |
Onboarding of the given user has failed in the given organization. |
Action |
Contact the organization administrator. |
INMPEE0218 | API key revocation failed. |
Explanation |
The specified API key could not be revoked. This problem can occur because the requestor does not have the required permisison to revoke API key. |
Action |
Only a user with Administrator or Asset Provider role can revoke API keys. |
INMPEE0225 | CentraSite cannot delete the alias because it is already deployed to the target. Alias: {0} |
Class | Error |
Explanation |
You are trying to delete an alias which is already deployed to a target. |
Action |
You must undeploy an alias before you delete it. |
INMPEE0226 | The user {0} of the API Portal cannot be deleted. |
Explanation |
You do not have sufficient access rights to delete the specified user {0} of API Portal, who has onboarded in the CentraSite registry. To delete the specified user, you must belong to the CentraSite Administrator role. |
Action |
Verify that you have the appropriate access rights. Contact your administrator and request access if necessary and then try again. |
INMPEE0227 | Could not send key revocation notice to the user configured in the API consumption settings. |
Explanation |
An email notification for the key revocation status could not be sent to the user configured in the API consumption settings, possibly because the user specified has been deleted from the CentraSite registry. |
Action |
Verify that the specified user exists in the CentraSite registry. If the user exists and the error persists, contact your administrator. If the user does not exist, remove the user from the API consumption settings. |
INMPEE0228 | API Portal user {0} was off-boarded. |
Explanation |
The API Portal user {0} has been off-boarded prior to the key generation/renewal operation. |
Action |
Onboard the API Portal user and try again. |
INMPEE0229 | Key revocation policy must be enabled for the API. |
Explanation |
The key revocation policy required for revoking an API's key has not been enabled for the API. |
Action |
Contact the API provider. |
INMPEE0230 | Failed to delete the API {0}. |
Explanation |
Could not delete the specified API {0} from CentraSite registry, possibly because the specified API is published to one or more API Portals. |
Action |
Make sure you unpublish the API from all of the API Portals, before trying to delete it. |
INMPEE0231 | Failed to create object {0} in organization {1}. |
Explanation |
Could not create the object {0} in the organization {1}, possibly because of insufficient permissions. |
Action |
Ensure that you have sufficient permissions to create the object in the selected organization. |
INMPEE0234 | The asset {0} cannot be deleted, because it is consumed by one or more assets. |
Explanation |
The asset {0} cannot be deleted, because it is consumed by one or more assets. |
Action |
Make sure you unconsume all consumers from the asset, before trying to delete it. |
INMPEE0236 | The WSDL does not have any service element for {0}. |
Explanation |
The WSDL cannot be validated if there are no service elements in it. |
Action |
If the service {0} is a Virtual type, the service element will be available only after it is deployed to a Mediator gateway. |
INMPEI0002 | Namespace {0} matches one of the possible namespaces {1} |
Explanation |
The service namespace validated against the set of possible namespaces as specified by the policy. 0 - Namespace of the service 1 - Allowed namespaces from policy. |
Action |
No action required. |
INMPEI0004 | User {0} does not have the role specified in the policy |
Explanation |
Since the user does not have the role specified in the policy, the role group policy is not applicable for the user 0 - Name of the user. |
Action |
No action required. |
INMPEI0005 | Attribute {0} is not applicable for {1} {2} |
Explanation |
The specified attribute is not applicable for the given object. 0 - Name of the attribute 1 - Type of the object 2 - Name of the object. |
Action |
No action required. |
INMPEI0006 | Policy {0} was successfully validated for activation |
Explanation |
The policy was successfully validated for activation. 0 - Name of the policy. |
Action |
No action required. |
INMPEI0007 | LC Model {0} was successfully validated for activation |
Explanation |
The lifecycle was successfully validated for activation. 0 - Name of the lifecycle model. |
Action |
No action required. |
INMPEI0008 | Policy {0} was successfully validated for deactivation |
Explanation |
The policy was successfully validated for deactivation. 0 - Name of the policy. |
Action |
No action required. |
INMPEI0010 | Permissions assigned successfully for {0} {1} |
Explanation |
Default permissions were assigned successfully for the given registry object. 0 - Type of the object 1 - Name of the object. |
Action |
No action required. |
INMPEI0012 | User {0} was assigned to organization groups successfully |
Explanation |
The user was assigned to organization groups successfully. 0 - Name of the user. |
Action |
No action required. |
INMPEI0014 | Organization {0} has Administrator |
Explanation |
The given organization has an administrator assigned to it. 0 - Name of the organization. |
Action |
No action required. |
INMPEI0015 | {0} {1} is classified by taxonomy {2} |
Explanation |
The given registry object is validated to be classified by the given taxonomy. 0 - Type name of the object 1 - Registry object name 2 - Taxonomy node name. |
Action |
No action required. |
INMPEI0017 | Default Roles, Permissions and Groups created successfully for Organization {0} |
Explanation |
Default roles, permissions and groups were created successfully for the given organization. 0 - Name of the organization. |
Action |
No action required. |
INMPEI0018 | Default Roles, Permissions and Groups deleted successfully for Organization {0} |
Explanation |
Default roles, permissions and groups were deleted successfully for the given organization. 0 - Name of the organization. |
Action |
No action required. |
INMPEI0019 | Adding {0} privilege for {1} {2} on {3} {4} |
Explanation |
The chosen privilege on the given registry object was successfully added for the particular user/group. 0 - View/Modify 1 - User/Group 2 - Name of the user/group 3 - Type of the registry object 4 - Name of the registry object. |
Action |
No action required. |
INMPEI0022 | Default roles, groups, permissions and SDL for organization {0} created successfully |
Explanation |
Default roles, groups, permissions and SDL were created successfully for the given organization. 0 - Name of the organization. |
Action |
No action required. |
INMPEI0023 | Default roles, groups, permissions for organization {0} removed successfully |
Explanation |
Default roles, permissions and groups were removed successfully for the given organization. 0 - Name of the organization. |
Action |
No action required. |
INMPEI0024 | User creation policy for User {0} was successful |
Explanation |
The user was successfully added to the default groups of the organization to which the user belongs. 0 - Name of the user. |
Action |
No action required. |
INMPEI0025 | Request Approval Flow {0} for {1} created successfully |
Explanation |
Request approval flow with the specified name was created successfully for the object. 0 - Approval Flow Name 1 - Name of the object for which approval is triggered. |
Action |
No action required. |
INMPEI0026 | Default instance level permissions for Asset {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given asset. 0 - Name of the asset. |
Action |
No action required. |
INMPEI0027 | Email with subject {0} successfully sent to {1} |
Explanation |
An email with the given subject was successfully sent to the recipients. 0 - Subject of the sent email 1 - email address of the recipient(s). |
Action |
No action required. |
INMPEI0029 | Service WSDL size {0} conforms with the specified size {1} |
Explanation |
The service WSDL size validated against the size specified by the policy. 0 - WSDL size of the service 1 - WSDL size specified in the policy. |
Action |
No action required. |
INMPEI0032 | {0} name {1} conforms with the pattern {2} |
Explanation |
The registry object name matches the specified pattern. 0 - Type of the registry object 1 - Name of the registry object 2 - Name pattern specified in the policy. |
Action |
No action required. |
INMPEI0033 | Default instance level permissions for Group {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given group. 0 - Name of the group. |
Action |
No action required. |
INMPEI0034 | Default instance level permissions for Lifecycle Model {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given lifecycle model. 0 - Name of the lifecycle model. |
Action |
No action required. |
INMPEI0035 | Default instance level permissions for Policy {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given policy. 0 - Name of the policy. |
Action |
No action required. |
INMPEI0036 | Default instance level permissions for Report Template {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given report template. 0 - Name of the report template. |
Action |
No action required. |
INMPEI0037 | Default instance level permissions for Role {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given role. 0 - Name of the role. |
Action |
No action required. |
INMPEI0038 | Default instance level permissions for Taxonomy {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given taxonomy. 0 - Name of the taxonomy. |
Action |
No action required. |
INMPEI0040 | Service Binding Type(s) conform with the specified bindings {0} |
Explanation |
The binding types of the service validated against the specified bindings. 0 - Binding types specified by the policy. |
Action |
No action required. |
INMPEI0041 | Default instance level permissions for User {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given user 0 - Name of the User |
Action |
No action required |
INMPEI0042 | Default instance level permissions for Policy Action {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given policy action. 0 - Name of the policy action. |
Action |
No action required. |
INMPEI0050 | {0} {1} successfully classified by specified taxonomies {2} |
Explanation |
The given registry object has been classified with the specified taxonomy nodes. 0 - Type name of the registry object 1 - Name of the registry object 2 - Name(s) of the taxonomy nodes. |
Action |
No action required. |
INMPEI0051 | {0} {1} successfully unclassified from specified taxonomies {2} |
Explanation |
The given registry object has been unclassified from the specified taxonomies. 0 - Type name of the registry object 1 - Name of the registry object 2 - Name(s) of the taxonomies. |
Action |
No action required. |
INMPEI0053 | {0} description {1} conforms with the pattern {2} |
Explanation |
The registry object description validated with the specified pattern. 0 - Type of the registry object 1 - Description of the registry object 2 - Description pattern specified in the policy. |
Action |
No action required. |
INMPEI0054 | {0} {1} was triggered to change to initial state {2} |
Explanation |
The registry object has been triggered to change to initial state of the corresponding lifecycle model. 0 - Type name of the object 1 - Name of the registry object 2 - Name of the initial state of the corresponding lifecycle model. |
Action |
No action required. |
INMPEI0055 | Object type of {0} - {1} is not LCM-enabled |
Explanation |
The type of the registry object is not lifecycle-enabled. 0 - Name of the object 1 - Type name of the object. |
Action |
No action required. |
INMPEI0056 | {0} {1} was triggered to change activation to {2} |
Explanation |
The registry object has been triggered to change activation to Active/Inactive. 0 - Type name of the object 1 - Name of the object 2 - Change activation to Active/Inactive. |
Action |
No action required. |
INMPEI0058 | {0} {1} belongs to state {2} which conforms to the allowed states {3} |
Explanation |
The lifecycle state of the registry object is validated against the allowed states specified in the policy. 0 - Type name of the registry object 1 - Name of the registry object 2 - Current state name of the registry object 3 - Allowed states specified in the policy. |
Action |
No action required. |
INMPEI0060 | State change to {0} is not applicable for {1} {2} |
Explanation |
The state change to the specified state is not applicable for the given object. 0 - Change to state name specified in the policy 1 - Type of the registry object 2 - Name of the registry object. |
Action |
No action required. |
INMPEI0061 | State change to {0} is initiated for {1} {2} |
Explanation |
The state change to the specified state has been initiated for the given object. 0 - Change to state name specified in the policy 1 - Type of the registry object 2 - Name of the registry object. |
Action |
No action required. |
INMPEI0062 | {0} {1} cannot be applied role groups policy |
Explanation |
Role groups policy can be applied only to user objects. 0 - Type of the registry object 1 - Name of the registry object. |
Action |
No action required |
INMPEI0063 | User {0} was added or removed from group {1} |
Explanation |
The given user was added or removed from the specified group. 0 - Name of the user 1 - Name of the group where the user was added or removed. |
Action |
No action required. |
INMPEI0065 | {0} {1} has value {2} set for attribute {3} which conforms to the allowed values {4} |
Explanation |
For the specified attribute of the given registry object, a value has been set which conforms to the allowed values. 0 - Type of the registry object 1 - Name of the registry object 2 - Attribute value of the registry object 3 - Attribute name specified in the policy 4 - Allowed attribute values specified in the policy. |
Action |
No action required. |
INMPEI0067 | Attribute {2} of {0} {1} was set to value {3} |
Explanation |
The specified attribute of the registry object was set to the specified value. 0 - Type of the registry object 1 - Name of the registry object 2 - Attribute name specified in the policy 3 - Attribute value specified in the policy. |
Action |
No action required |
INMPEI0068 | LC Model {0}'s enabled object type instances were initiated into initial state {1} |
Explanation |
The instances of the object types which are LCM enabled by the given LC Model have been triggered to change to the initial state of the LC Model. 0 - Name of the LC Model 1 - Name of the initial state of the LC Model. |
Action |
No action required |
INMPEI0076 | Default instance level permissions for Target {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given target. 0 - Name of the target |
Action |
No action required. |
INMPEI0077 | Default instance level permissions for Lifecycle State {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given lifecycle state. 0 - Name of the lifecycle state. |
Action |
No action required. |
INMPEI0078 | Default instance level permissions for Asset Type {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given asset type. 0 - Name of the asset type. |
Action |
No action required. |
INMPEI0079 | Default instance level permissions for Taxonomy {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given taxonomy. 0 - Name of the taxonomy. |
Action |
No action required. |
INMPEI0080 | Default instance level permissions for Event Type {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given event type. 0 - Name of the event type |
Action |
No action required. |
INMPEI0081 | Default instance level permissions for Profile {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given profile. 0 - Name of the profile |
Action |
No action required. |
INMPEI0082 | Default instance level permissions for UDDI Subscription {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given UDDI subscription. 0 - Name of the UDDI subscription |
Action |
No action required. |
INMPEI0083 | Default instance level permissions for Federation {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given federation. 0 - Name of the federation. |
Action |
No action required. |
INMPEI0084 | Default instance level permissions for Concept {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given concept. 0 - Name of the concept. |
Action |
No action required. |
INMPEI0085 | Taxonomy {0} instance level permissions were assigned successfully to its child objects |
Explanation |
The instance level permissions of the taxonomy were successfully assigned to its children concepts. 0 - Name of the taxonomy. |
Action |
No action required. |
INMPEI0086 | Policy {0} instance level permissions were assigned successfully to its child objects |
Explanation |
Policy has child objects like Policy Condition and Policy Parameter. When we assign the instance level permission to a Policy, the permission should be assigned also to its child objects. The message states that this action was performed successfully. |
Action |
No action required. |
INMPEI0088 | User {0} is not active |
Explanation |
The user is not active and hence can be deleted. 0 - Name of the user. |
Action |
No action required. |
INMPEI0095 | Pending state transition was terminated by CSA |
Explanation |
The CentraSite administrator has terminated the pending state transition on the registry object. |
Action |
No action required. |
INMPEI0103 | Organization Primary Contact is an active user |
Explanation |
The primary contact of the organization is an active user and hence the validation for updating the organization is successful. |
Action |
No action required. |
INMPEI0119 | Default instance level permissions for ConsumerRegistrationRequest {0} were assigned successfully |
Explanation |
Default instance level permissions for the consumer registration request were assigned successfully. 0 – Name of the consumer registration request. |
Action |
No action required. |
INMPEI0134 | Default instance level permissions for ExternalLink {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given external link. 0 - Name of the external link. |
Action |
No action required. |
INMPEI0135 | Default instance level permissions for ExtrinsicObject {0} were assigned successfully |
Explanation |
Default instance level permissions were successfully assigned for the given extrinsic object. 0 - Name of the extrinsic object. |
Action |
No action required. |
INMPEI0137 | Collector was successfully executed for {0} {1} |
Explanation |
The collector policy was executed successfully for the given object. 0 - Type of the object 1 - Name of the object. |
Action |
No action required. |
INMPEI0138 | Default delete handler was successfully executed for {0} {1} |
Explanation |
The default delete handler policy was executed successfully for the given object. 0 - Type of the object 1 - Name of the object. |
Action |
No action required. |
INMPEI0140 | WSDL regeneration skipped for Service {0} since the service is not a VirtualService, VirtualXMLService or VirtualRESTService |
Explanation |
WSDL regeneration can be performed only for a virtual service, virtual XML service or virtual REST service. |
Action |
Make sure the asset is a virtual service, virtual XML service or virtual REST service. |
INMPEI0141 | {0} {1} moved successfully |
Explanation |
The registry object has been moved successfully to the new owner and/or organization. 0 - Type of the registry object 1 - Name of the registry object. |
Action |
No action required. |
INMPEI0147 | Registry Object {0} has been validated successfully against its mandatory attributes of type Classification, File and Relationship |
Explanation |
All the mandatory classification, file and relationship attributes for the given registry object have been populated. 0 - Name of the registry object. |
Action |
No action required. |
INMPEI0155 | Profile permissions for {0} {1} were assigned successfully |
Explanation |
The profile level permissions for the given registry object were successfully assigned. |
Action |
No action required. |
INMPEI0158 | Organization export handler was successfully executed for {0} |
Explanation |
The organization export handler was executed successfully for the given organization. |
Action |
No action required. |
INMPEI0159 | Taxonomy/Concept export handler was successfully executed for {0} {1} |
Explanation |
The Taxonomy/Concept export handler was executed successfully for the given object. |
Action |
No action required. |
INMPEI0160 | Default export handler was successfully executed for {0} {1} |
Explanation |
The default export handler policy was executed successfully for the given object. 0 - Type of the object 1 - Name of the object. |
Action |
No action required. |
INMPEI0161 | Asset type export handler was successfully executed for {0} {1} |
Explanation |
The asset type export handler policy was executed successfully for the given object. 0 - Type of the object 1 - Name of the object. |
Action |
No action required. |
INMPEI0164 | Metrics does not contain serviceKey hence will not be saved in Runtime Metrics Collection |
Explanation |
Metrics must be saved against a service. But the user is trying to save a metrics object without classifying it with a proper service key. This metrics will be discarded. |
Action |
Please classify the metrics objects with the classificationScheme “uddi:centrasite.com:management:service.key”. The value of the classification must be the key of the service to which the metrics belongs. |
INMPEI0168 | The required permissions are already available for {0} {1} |
Explanation |
The permissions to be set by the policy are already available in the registry object. 0 - Type of the registry object 1 - Name of the registry object. |
Action |
No action required. |
INMPEI0169 | Request Approval Flow {0} for {1} was automatically approved |
Explanation |
The approval flow for the registry object was automatically approved since the triggering user is part of the approver group. |
Action |
No action required. |
INMPEI0170 | CentraSite does not contain an object of type {0} and with name {1} |
Explanation |
The policy executed successfully, since CentraSite does not contain an object of the specified type and with specified name. |
Action |
No action required. |
INMPEI0171 | CentraSite already contains an object of type {0} and with name {1} |
Explanation |
This policy enforces uniqueness in names of the object. As the user tried to create an object using a name which already exists in CentraSite, this policy failed. |
Action |
Please use a different name |
INMPEI0173 | Notified Webservice endpoint {0} hosted in application server {1} successfully. |
Explanation |
A Webservice request has been published to the endpoint successfully. |
Action |
No action required. |
INMPEI0174 | Failed to notify Webservice endpoint {0} hosted in application server {1}: Error Message {2} |
Explanation |
The Webservice request could not be published to the specified endpoint. |
Action |
Provide a valid webservice endpoint which can accept the SOAP message configured in the notify policy. |
INMPEI0177 | {0} {1} has kept the current LCM state |
Explanation |
The LCM state has been retained during the import. |
Action |
No action required. |
INMPEI0178 | Successfully deleted the rest service of IS Service Interface '{0}' |
Explanation |
Rest service deletion has completed successfully while retracting the IS Service Interface from the Designer. |
Action |
No action required. |
INMPEI0179 | Failed to delete the rest service '{0}' ({1}) used by IS Service Interface '{2}' |
Explanation |
The deletion of the Rest Service failed while retracting the IS Service Interface from the Designer. |
Action |
No action required. |
INMPEI0182 | IS Service Interface {0} object has been transformed successfully into REST service {1}. |
Explanation |
The IS Service Interface object has been transformed successfully into a REST service in CentraSite. |
Action |
No action required. |
INMPEI0183 | The given object {0} does not contain the state |
Explanation |
The given object 0 does not contain the state. |
Action |
No action required. |
INMPEI0186 | Target Group not applicable for the operation |
Explanation |
The target group is not applicable for the operation. |
Action |
No action required. |
INMPEI0187 | Target Group created for the Target |
Explanation |
The target group was created for the target. |
Action |
No action required. |
INMPEI0188 | Target Group not created for the Target |
Explanation |
The target group was not created for the target. |
Action |
No action required. |
INMPEI0189 | {0} {1} promoted successfully |
Explanation |
The registry object has been promoted successfully to the specified target stage. 0 - Type of the registry object 1 - Name of the registry object. |
Action |
No action required. |
INMPEI0191 | Not updating Consumer WSDL for VirtualService {0} as it does not contain WSDL or Consumer WSDL is already contains the proper WSDL file. |
Explanation |
The Consumer WSDL attribute will not get updated if the Virtual Service does not have WSDL associated with it. Also the attribute will get updated if it contains the proper value in it. |
Action |
No Action Required, as this policy get triggered when WSDL is attached to the Virtual Service |
INMPEI0193 | Consumer WSDL attribute is populated with proper WSDL |
Explanation |
Policy Action successfully executed by populated the Consumer WSDL attribute with proper WSDL |
Action |
No action required |
INMPEI0194 | Not updating Consumer WSDL for {0} since it is not a Service |
Explanation |
Consumer WSDL attribute is applicable only for Virtual Service and hence it can't be updated for other objects |
Action |
Please make sure applicable object for "Consumer WSDL Generator" policy is set only to Virtual Service |
INMPEI0201 | , |
Explanation |
This is a user display name separator. |
Action |
No action required. |
INMPEI0202 | {0} {1} {2} |
Explanation |
This is a user display name. |
Action |
No action required. |
INMPEI0203 | Ownership of {0} {1} was changed successfully to user {2} |
Explanation |
The ownership of the given asset was changed successfully to the specified user. 0 - Type of the object; 1 - Name of the object; 2 - New owner of the object. |
Action |
No action required. |
INMPEI0205 | {0} of type {1} has been validated for all mandatory Slot, Classification, File and Relationship attribute types. |
Explanation |
The "required" attributes of the registry object {0} of type {1} have been identified and all such "required" attributes have been provided with values. |
Action |
No action required. |
INMPEI0207 | The API Key is deployed successfully to target {0} |
Explanation |
The specified API key was successfully deployed to the specified target. |
Action |
No action required. |
INMPEI0208 | A new API Key is generated. |
Explanation |
A new API key has been generated. |
Action |
No action required. |
INMPEI0209 | Onboarded user {0} proceeds with consume API request for {1} |
Explanation |
The onboarding of the user was successful, and the consume API request for the API has been triggered. |
Action |
User registration completion information will be sent as an email. |
INMPEI0213 | Onboarding User {0} in Organization {1} is successful |
Explanation |
Onboarding of the user in API Management solution was successful. |
Action |
The Consume API request will be generated automatically for the onboarded user. |
INMPEI0214 | Onboarding Organization {0} with Administrator User {1} is successful |
Explanation |
Onboarding of the given Organization with the given User in API Management solution was successful. |
Action |
The Consume API request will be generated automatically for the the onboarded administrator user. |
INMPEI0215 | Congratulations from API management team |
Explanation |
Email subject for successful onboarding of user. |
Action |
No action. |
INMPEI0216 | API key deleted successfully from target {0}. |
Explanation |
The API key is deleted successfully from the target {0}. |
Action |
None. Informational only. |
INMPEI0220 | WSDL regeneration skipped for virtual service {0} as WSDL related objects are not modified. |
Explanation |
WSDL regeneration is needed only if JAXR binding is updated, else WSDL update not required. CentraSite updates it only if it really required. |
Action |
No action required. |
INMPEI0221 | API key has been renewed successfully. |
Explanation |
API key has been renewed successfully. |
Action |
No action required |
INMPEI0232 | OAuth2 Client is revoked successfully. |
Explanation |
The OAuth2 Client was revoked successfully. |
Action |
No action required. |
INMPEI0235 | Swagger2.0 file is generated successfully for the API {0}. |
Explanation |
|
Action |
|
INMPEW0028 | WSDL URL is empty for {0} |
Explanation |
The service WSDL URL is empty. 0 - Name of the service. |
Action |
Please ensure that the service has a WSDL URL. |
INMPEW0172 | Could not send notification to application server as it is not configured with APG_SERVICE_ENDPOINT |
Explanation |
The notification will be send only if the application server is configured with APG_SERVICE_ENDPOINT in the object specific property. |
Action |
Configure a valid webservice endpoint to the application server which is associated to the registry object. |
INMPEW0192 | Consumer WSDL attribute is not found Virtual Service type |
Explanation |
This policy action will update the Consumer WSDL attribute with WSDL which may contain WS Policy in it. So this policy action requires Consumer WSDL attribute |
Action |
Please make sure Consumer WSDL file attribute exists for Service type |
INMPEW0217 | Failed to delete API key from target {0} . |
Explanation |
The specified API key could not be deleted from the target {0}. This problem can occur because the requestor does not have the required permisison to delete API key. |
Action |
Only a user with Administrator role can delete API key from targets. |
INMPEW0219 | You can revoke an access token only once. |
Explanation |
The access token is revoked twice. |
Action |
Revoke an access token only once. |
INMPEW0233 | Failed to revoke OAuth2 Client from Mediator. |
Explanation |
Could not revoke the OAuth2 Client from the specified Mediator. There could be multiple reasons why this might have occurred: (1) Integration Server on which Mediator is running is down or inaccessible (2) invalid user credentials (3) application error on the Integration Server. |
Action |
Make sure the Integration Server on which Mediator is up and running, and the user credentials are correct. |
INMPUE0003 | Action category and action template types are mismatched |
Explanation |
For a design time/ change time category, the action template type should be programmatic. If the action template type does not match the design time/ change time category, this causes an error. |
Action |
Ensure that the action category and action template types are matched. |
INMPUE0006 | Action template name already exists |
Explanation |
An action template name should be unique across the system, otherwise this will create confusion for the user. So this error occurs if a user tries to create an action template with a name that is already in use. |
Action |
Use a different action template name. |
INMPUE0015 | WS-I actions cannot be combined with other actions |
Explanation |
While creating a policy, WS-I actions should not be combined with other actions. If a user tries to do so, this problem will happen. |
Action |
WS-I actions cannot be combined with other actions. |
INMPUE0020 | Reordering multiple actions is not allowed |
Explanation |
While assigning actions to the policy, a user can re-order the actions. If the user tries to re-order multiple actions at a time, this error will be thrown. |
Action |
Reordering multiple actions is not allowed. |
INMPUE0028 | Select an action to move |
Explanation |
If a user tries to re-order the actions without selecting anything, this error will be thrown. For this the user has to first select any action and then do the re-ordering. |
Action |
Select an action to move. |
INMPUE0029 | Action category with name {0} already available |
Explanation |
Action category names are unique across the system. If a user tries to create an action category with a name that exists already, this error will be thrown. |
Action |
Enter a valid action category name. |
INMPUE0030 | Provide the URL of ZIP file |
Explanation |
When creating an action template with the selected rule type of Java, the user has to provide a valid zip file, otherwise this error will be thrown. |
Action |
Enter the URL of the ZIP file. |
INMPUE0032 | Set Profile Permission action cannot be applied to multiple object types |
Explanation |
If the policy applies to multiple object types, then the set profile permission action cannot be applied |
Action |
Change the object types or create a new policy with a single object type |
INMPUE0033 | Provide the correct Attribute Values |
Explanation |
The attribute value provided is incorrect for the chosen type. |
Action |
Provide the correct attribute value for the chosen type. |
INMPUE0034 | You must specify a value for Attribute Name |
Explanation |
The required value forthe duration attribute name is missing. |
Action |
Supply a correct value for the duration attribute name. |
INMRAE0001 | Cannot obtain {0} from closed Resource Access Manager. |
Explanation |
The Resource Access Manager is closed and thus not yet initialized. |
Action |
Make sure that the Resource Access Manager is opened before using it. |
INMRAE0002 | No configuration set. |
Explanation |
No configuration info set was found. |
Action |
Please provide a configuration info set. Refer to the Resource Access javadoc for additional information. |
INMRAE0003 | No valid credentials found. |
Explanation |
No valid credentials were found. |
Action |
Please provide valid credentials. |
INMRAE0004 | Found {0} while expecting instance of XmlServerRoleManager. |
Explanation |
Failed authentication against CentraSite server or absence of XmlServerLoginModule from security configuration. |
Action |
Check logs and security configuration. |
INMRAE0005 | SagRoleManagementPrincipal instance not available for the authenticated subject. |
Explanation |
The SagRoleManagementPrincipal security artefact is missing. |
Action |
Check the security configuration. |
INMRAE0006 | Authenticated Subject cannot be null. |
Explanation |
After successful authentication, the Subject instance was not found. |
Action |
Contact your software supplier. |
INMRAE0007 | No representation of the Group to be associated in external user repository. |
Explanation |
The external group, to be associated with a local group, is no longer present in the external repository. |
Action |
External user repositories are managed outside of CentraSite. |
INMRAE0008 | Error during System level permission copy. |
Explanation |
Error during System level permission copy. |
Action |
Contact your software supplier. |
INMRAE0009 | An organization must be set. |
Explanation |
A permission has to belong to an organization. |
Action |
Assign an organization to the permission instance. |
INMRAE0010 | Organization level permission needs to have a corresponding system level permission. |
Explanation |
An organization level permission needs to have a corresponding system level permission. |
Action |
Assign the system level permission to the organization level permission instance. |
INMRAE0011 | A Role needs to belong to an Organization. |
Explanation |
A role needs to belong to an organization. |
Action |
Assign an organization to the role instance. |
INMRAE0012 | The user does not have a working Organization set. |
Explanation |
The user does not have a working organization set. |
Action |
Set the working organization of the user. |
INMRAE0013 | Roles can be assigned only to registered users. |
Explanation |
Roles can be assigned only to registered users associated with an external user repository. |
Action |
Register a user instance to CentraSite. |
INMRAE0014 | Unsupported collection type. |
Explanation |
The passed collection is of an unsupported type. |
Action |
The collection expected is a list-backed one. |
INMRAE0015 | Got {0} while expecting {1} |
Explanation |
Passed in Registry Object instance is not of group type. |
Action |
Make sure that passed in Registry Object instance is of group type. |
INMRAE0016 | Cannot obtain external user repository type. |
Explanation |
Cannot retrieve the currently effective external user repository type. |
Action |
Check the security configuration. |
INMRAE0017 | Unsupported external user repository type {0}. |
Explanation |
The currently effective external user repository type is unknown. |
Action |
Check the security configuration. |
INMRAE0018 | Currently effective external user repository type {0} does not support custom predicate. |
Explanation |
Currently effective external user repository type does not support custom predicate. |
Action |
Use predicates instead. |
INMRAE0019 | Currently effective external user repository type {0} does not support predicates. |
Explanation |
Currently effective external user repository type does not support predicates. |
Action |
Use custom predicate instead. |
INMRAE0020 | SagUserPrincipal instance not available for the authenticated subject. |
Explanation |
The SagUserPrincipal security artefact is missing. It is possible that authentication against the external user repository is not performed, for example internal user accounts such as the Guest user account. |
Action |
Check the security configuration. |
INMRAE0021 | PersonName must be added |
Explanation |
A user instance must have PersonName. |
Action |
When creating a User object, the first name, middle name and last name of the user object need to be provided. |
INMSOE0001 | HTTP Routing Protocol not enabled |
Explanation |
During configuration of routing protocol, if any of the routing types are StraightThrough/LoadBalance/ContentBased/ContextBased routing, then the transport of the routing should be HTTP enabled. |
Action |
Enable the HTTP transport for routing protocol. |
INMSOE0002 | JMS Routing Protocol not enabled |
Explanation |
During configuration of the routing protocol, if the routing type is JMS routing, then the transport of the routing should be JMS enabled. |
Action |
Enable the JMS transport for routing protocol. |
INMSOE0007 | TargetType definition file missing |
Explanation |
The input JAR file provided does not contain the relevant TargetType definition XML. |
Action |
Add the relevant TargetType definition XML to the input JAR file. |
INMSOE0008 | Transformation definition file missing |
Explanation |
The input JAR file provided does not contain the relevant transformation file. |
Action |
Add the relevant transformation file to the input JAR file. |
INMSOE0010 | Target Type name should not be empty |
Explanation |
The input JAR file provided does not contain the target type name in the Target Type Definition file. |
Action |
Provide the Target Type name. |
INMSOE0011 | Event Type definition file missing |
Explanation |
The input JAR file provided does not contain the relevant Event Type definition. |
Action |
Add the relevant Event Type definition to the input JAR file. |
INMSOE0012 | Target Type name already exists |
Explanation |
The Target Type already exists with the provided name in Target Type definition file. |
Action |
Change the Target Type name. |
INMSOE0013 | Service WSDL does not contain the WSDL Service Element |
Explanation |
The imported WSDL does not contain the service element. |
Action |
Make sure service element is present in the service WSDL. |
INMSOE0015 | Service WSDL is mandatory for deployment operations |
Explanation |
The WSDL is not present for the created virtual service. |
Action |
Make sure the created virtual service contains the WSDL. |
INMSOE0016 | Deployment activity {0} is the current activity log for {1} {2} |
Explanation |
An activity log which is the latest deployment log for a deployed asset cannot be deleted. |
Action |
Unselect the particular deployment log from the deployment history before deleting other old entries. |
INMSOE0019 | The consumer application defined in the routing rule of the asset is no longer available in CentraSite. Specify a valid consumer application in the routing rule. |
Explanation |
The consumer application used as part of the context based routing condition of the asset to be deployed is not available in the CentraSite Repository. |
Action |
Provide a valid consumer application in the routing rule. |
INMSOE0020 | Data type mismatch during attribute mapping for RuntimeEventType: {0}. Expected data type for attribute {1} is {2}, while the supplied data type is {3}. |
Explanation |
This exception is thrown when a data type mismatch is encountered when mapping SNMP Trap attributes from EventType.xml to RuntimeEventType attributes. |
Action |
Ensure the data type matches. |
INMSOE0021 | Entry protocol not defined for asset {0} |
Explanation |
The inbound transport information is not defined for the asset to be deployed to the Mediator. |
Action |
Configure the entry protocol in the processing steps profile of the asset to be deployed. |
INMSOE0022 | WSDL not found for native service |
Explanation |
A WSDL is not available for the native service to be virtualized. |
Action |
Attach the WSDL for the native service to be virtualized. |
INMSOE0023 | Cannot virtualized this WebService since the service does not contain any wsdl:bindings |
Explanation |
Service must contain at least one service binding, otherwise it cannot be virtualized |
Action |
Getting error while virtualizing the service without service binding |
INMSOE0027 | TrapOID (Object Identifier) {0} is duplicated in the EventType.xml inside the provided Target Type definition jar file |
Explanation |
During target type creation, if the SNMP Trap OID is duplicated in EventType.xml, this exception is thrown. |
Action |
SNMP Trap OIDs should be unique within and across target types. |
INMSOE0028 | TrapOID {0} already defined in existing Target Type {1} |
Explanation |
During target type creation, if the SNMP Trap OID is already present in an existing target type, this exception is thrown. |
Action |
SNMP Trap OIDs should be unique within and across target types. |
INMSOE0031 | Scoped Virtual Service deployment will not be triggered since dependent assertion {0} does not exist |
Explanation |
Scoped Virtual Service deployment will not be triggered since some of the dependent assertions are missing in the Runtime Policy. |
Action |
Ensure dependent assertions exist. |
INMSOE0033 | Scoped Virtual Service deployment will not be triggered since dependent assertion {0} does not exist |
Explanation |
Virtual Service will have policies associated with it. These policies may be dependent on other policies. If the dependent policies are not applied for the virtual service, this exception will arise. |
Action |
Please create the dependent runtime policy and make sure it is applicable for the virtual service to be deployed. |
INMSOE0036 | Error in API Key Creation |
Explanation |
An error occurred while creating an API Key instance. |
Action |
Check if there are any related messages in the log to determine the cause of the problem. |
INMSOE0037 | Mandatory parameters are not present for creation of API Key instance |
Explanation |
Mandatory parameters were not provided while creating API Key object |
Action |
Provide the mandatory parameters. |
INMSOE0039 | Invalid parameter {0} is selected which is not supported in the version of Mediator installed |
Explanation |
The version of mediator to which the asset is being deployed does not support the parameter {0}. |
Action |
Change the parameter to one that is supported in the mediator version installed. |
INMSOE0041 | Error occurred during creation of OAuth2 Client asset |
Explanation |
An error was encountered while creating the OAuth2 Client asset. |
Action |
Check if there are any related messages in the log to determine the cause of the problem. |
INMSOE0042 | Mandatory parameters are missing for creation of OAuth2 client instance |
Explanation |
Mandatory parameters were missing while creating OAuth2 client object. |
Action |
Check if the mandatory parameters 'Service' and 'Consumer' are missing. |
INMSOE0043 | Cannot enforce evaluate actions ApiKey and OAuth2 for the service. |
Explanation |
When both API Keys and OAuth2 are enforced for an API in AND condition, this exception is thrown. |
Action |
Change the enforce condition to OR. |
INMSOE0044 | Deployment of the Virtual Service failed. Check the Integration Server log. |
Explanation |
The deployment of the Virtual Service has failed. |
Action |
Check the Integration Server log. |
INMSOE0045 | You might not be authorized to view the runtime alias type |
Class | Error |
Explanation |
Alias Key Name Map is not initialized. |
Action |
Check if you have permission to use the alias type. |
INMSOE0049 | Default value not specified for the runtime alias. CentraSite cannot save the alias. |
Class | Error |
Explanation |
CentraSite cannot save the runtime alias because the default value for the alias is not specified. |
Action |
Retry after you specify a default value for the runtime alias. |
INMSOE0050 | Required values are missing for runtime target: {0} for alias {1} |
Class | Error |
Explanation |
An error occurred while trying to associate a target to a runtime alias, possibly because some of the required values are missing. |
Action |
Provide target-specific values for the runtime alias, and try again. |
INMSOE0053 | CentraSite does not support alias deployment for runtime target Mediator version {0}. Runtime alias deployment is supported only for Mediator version {1} and above. |
Class | Error |
Explanation |
CentraSite cannot deploy runtime aliases because they are not support in the Mediator version installed. |
Action |
If you would like to create and deploy runtime aliases, upgrade to Mediator 9.7 |
INMSOE0054 | Alias with name {0} already exists. Provide a different name. |
Explanation |
CentraSite cannot have aliases with same name as this will have issues when it is deployed to the same Mediator. |
Action |
Provide a different name for alias and save it. |
INMSOE0055 | Runtime alias is already deployed to target(s). You must disassociate the alias from the services and undeploy it before you change the alias name. |
Class | Error |
Explanation |
You are trying to change the alias name of a runtime alias that is already deployed to its target(s). |
Action |
Disassociate the alias from the services and undeploy it before you change the alias name. |
INMSOE0056 | Runtime alias not found. Alias name: {0} |
Class | Error |
Explanation |
You are trying to use a runtime alias that is not defined in CentraSite. |
Action |
Check if the alias is defined in CentraSite or use an alias that is already defined. |
INMSOE0057 | The authentication type in the secure alias does not match the authentication type in the virtual service. Secure alias: {0}, virtual service: {1}. Check the authentication type of the secure alias that you published and change it to match the authentication type used in the virtual service |
Class | Error |
Explanation |
The authentication type specified in the secure alias does not match with the outbound authentication policy specified in CentraSite. |
Action |
Check the authentication type of the secure alias that you published and change it to match the authentication type used in the virtual service. |
INMSOE0058 | Target does not support deployment of REST services with more than one resource and/or tokenized routing endpoints. |
Explanation |
Older Mediators before version 9.7 do not support more than one REST resource and tokenized routing endpoints. |
Action |
Make sure that you deploy to a newer version of Mediator. |
INMSOE0059 | Invalid deployment endpoint. |
Explanation |
The deployment endpoint is not valid. |
Action |
Provide a valid deployment endpoint. |
INMSOE0061 | HTTP protocol is not supported for Kerberos. Select HTTPS protocol only. |
Explanation |
HTTP protocol is not supported for Kerberos. Only, HTTPS protocol is supported. |
Action |
Select HTTPS protocol only during virtualization. |
INMSOE0062 | The Custom Error Variable name field must not be empty. |
Explanation |
You have not entered a name while adding a Custom Error Variable in the Conditional Error Processing step. |
Action |
Enter a name for the Custom Error Variable. |
INMSOE0063 | The Custom Error Variable Xpath expression cannot be empty. |
Explanation |
You have not entered an Xpath expression while adding Custom Error Variable in the Conditional Error Processing step. |
Action |
Provide an Xpath expression for the Custom Error Variable. |
INMSOE0064 | Gateway with version {0} does not support OData services. |
Explanation |
The gateway is too old for deploying OData services. |
Action |
Use a newer gateway (>= 9.10) |
INMSOE0065 | Service {0} is not of supported type for {1}. |
Explanation |
The service is not supported for the give action. This is an internal problem. |
Action |
Check the type of service. |
INMSOE0066 | VSD cannot be generated for virtual service {0}. |
Explanation |
The VSD document of a virtual service cannot be generated due to internal problems. |
Action |
Check the details of the virtual service. |
INMSOE0067 | Gateway with version {0} does not support the HTTP PATCH method for REST service {1}. |
Explanation |
The deployed REST service exposes the HTTP PATCH method, which is not supported by this version of Mediator. |
Action |
Deploy the REST service with HTTP PATCH method to a newer version of Mediator. |
INMSOE0068 | The REST service {0} uses the HTTP PATCH method, however the deployment mode is not set to "axis-free". |
Explanation |
The REST service {0} uses the HTTP PATCH method, however the deployment mode is not set to "axis-free". This is becasue only the axis-free deployment mode supports the PATCH method. |
Action |
Check if you can activate the axis-free deployment mode in centrasite.xml. |
INMSOE0069 | Incompatible gateway types. |
Explanation |
The gateway types of the CentraSite registry object and the running instance are not the same type. |
Action |
Check your running target and the CentraSite gateway object. |
INMSOE0070 | REST service deployment to API Gateway requires "axis-free" setting. |
Explanation |
REST service deployment to API Gateway is only supported if the CentraSite deployment mode was set to axis-free. |
Action |
Configure the axis-free mode in CentraSite. |
INMSOE0071 | Could not publish the virtual service because the associated {0} {1} has no valid credentials. |
Explanation |
An error occurred while trying to publish the runtime alias, possibly because the associated {0} {1} has no valid credentials. |
Action |
Specify a valid username and password for the runtime alias, and try again |
INMSOE0072 | Failed to connect to deployment endpoint. {0}. |
Explanation |
An error occurred while trying to connect to the deployment endpoint of a target. There could be multiple reasons why this might have occurred: (1) target deployment endpoint is down or inaccessible (2) invalid user credentials. |
Action |
Make sure the target deployment endpoint is up and running, and the user credentials are correct. |
INMSOE0073 | Gateway not active or accessible. |
Explanation |
The selected gateway is not active or accessible. |
Action |
Check the accessibility of gateway. |
INMSOE0074 | Invalid credentials |
Explanation |
Invalid username or password specified for accessing the gateway. |
Action |
Check the username and passord for accessing the gateway. |
INMSOE0075 | Unknown host: {0} |
Explanation |
The host to be accessed is unknown. |
Action |
Check if the host is accessible. |
INMSOE0077 | Deployment timout value of {0} seconds exceeded |
Explanation |
The timeout value of a deployment request to a gateway has been exceeded |
Action |
Configure a greater timeout value or specify one with a CentraSiteCommand option |
INMSOI0017 | Connection to deployment endpoint failed |
Explanation |
This occurs if no connection can be established to the deployment endpoint defined in a target during deployment/undeployment/syncconsumers operations. This could be because the deployment endpoint is down or the credentials used for accessing the deployment endpoint are wrong. |
Action |
Check if the deployment endpoint is up and running. Also check if the credentials defined in the target for accessing the deployment endpoint are correct. |
INMSOI0035 | API Key for {0} of {1} |
Explanation |
This is how the name of the API key will be generated where the service name is passed as a parameter. |
Action |
No action required. |
INMSOI0040 | OAuth2 Client for {0} of {1} |
Explanation |
This is how the name of the OAuth2 Client is created when the service name and consumer name are passed as parameters. |
Action |
No action required. |
INMSOW0034 | The parameter(s)/action(s) {0} were ignored as it is not supported by Mediator {1} |
Explanation |
Virtual Service can be deployed from latest version of CentraSite to Mediator version 8.2.2 and above. If you deploy any service to older version of Mediator from latest version of CentraSite, some policy parameters or actions cannot be executed on older version of Mediator. Such policy parameters or actions will be ignored. This warning message will list those ignored parameter/actions. |
Action |
If the ignored parameters or actions need to be executed, then Mediator has to be upgraded to version in which CentraSite is running. If the ignored parameter or actions are not needed, then this warning message can be ignored. |
INMSOW0076 | Service is published to API gateway but activation is denied. |
Explanation |
Service was successfully published to API gateway but the service is still in deactivation state. |
Action |
Log into API Gateway and try to activate the service. |
INMSTE0001 | Referenced service does not exist ("{0}") |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMSTE0002 | Dangling reference ("{0}") |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMSTE0003 | Conflicting state ({0}) |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMSTE0004 | Invalid Reference ("{0}") |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMSTE0005 | Type concept is not found in ImportList |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMSTE0006 | No schema definition generated |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMSTE0007 | schemaName for selected concept is null |
Explanation |
Internal error. |
Action |
Please contact your software supplier. |
INMSTE0008 | At least one instance does not comply with the type modifications. |
Explanation |
A type is being modified in a way that is not compliant with the existing instances of that type. |
Action |
Modify the type in a compliant way. |
INMSTE0009 | Type concept not found for "{0}" |
Explanation |
While updating or deleting a JAXR object type, the corresponding type concept was not found in the registry. |
Action |
This is an internal error. Please contact your software supplier. |
INMSUE0001 | Reordering multiple actions is not allowed |
Explanation |
Reordering multiple actions not allowed. |
Action |
Reordering multiple actions not allowed. |
INMSUE0002 | You must select valid jar file |
Explanation |
The selected jar file(s) are not valid. |
Action |
Select valid jar files. |
INMSUE0003 | Enter unique name |
Explanation |
The event type name already exists. |
Action |
Enter a unique name for the event type |
INMSUE0004 | Target name should not be empty |
Explanation |
An attempt was made to add a target object without a name. |
Action |
Supply a target name. |
INMSUE0005 | Target type should not be empty |
Explanation |
An attempt was made to add a target type object without a name. |
Action |
Supply a target type name. |
INMSUE0006 | Policy name cannot be empty |
Explanation |
An attempt was made to add a policy object without a name. |
Action |
Supply a policy name. |
INMSUE0007 | Select an Asset Type for the policy |
Explanation |
For creating a runtime policy object, the object needs an associated object type. |
Action |
Select an object type for the policy. |
INMSUE0008 | Select a target type for the policy |
Explanation |
The target type for the policy is missing. |
Action |
Select a target type for the policy. |
INMSUE0009 | Default route cannot be empty |
Explanation |
The default route is missing. |
Action |
Define a default route. |
INMSUE0010 | XPath expression cannot be empty |
Explanation |
An empty XPath expression was supplied. |
Action |
Supply an XPath expression. |
INMSUE0011 | Enter the valid XPath to the 'Element Required to be Signed' |
Explanation |
The correct XPath to the 'Element Required to be Signed' is required. |
Action |
Enter the valid XPath to the 'Element Required to be Signed'. |
INMSUE0012 | Virtual Service name should not be empty |
Explanation |
The required name is missing. |
Action |
Supply the name. |
INMSUE0013 | Version cannot be empty |
Explanation |
A version was not entered. |
Action |
Enter a version. |
INMSUE0014 | No WSDL Found |
Explanation |
For the given URL, there is no WSDL available. |
Action |
Supply a WSDL for the URL. |
INMSUE0015 | Virtual service with name {0} already exists |
Explanation |
A virtual service with the given name already exists. |
Action |
Supply a different name for the virtual service. |
INMSUE0016 | Assign actions for the policy |
Explanation |
The actions required for the runtime policy object are missing. |
Action |
Assign actions for the policy. |
INMSUE0017 | Create target type before creating runtime policy |
Explanation |
The target type required for creating the runtime policy is not available. |
Action |
Create the target type before creating the runtime policy. |
INMSUE0018 | Create target type before creating target |
Explanation |
The target type must be created before the target can be created. |
Action |
Create the target type before creating the target. |
INMSUE0019 | Select at least one target to deploy |
Explanation |
No target was selected to deploy. |
Action |
Select at least one target to deploy. |
INMSUE0020 | Default route cannot be empty |
Explanation |
The default route was not specified. |
Action |
Specify a default route |
INMSUE0022 | JMS alert destination cannot be empty |
Explanation |
The JMS alert destination was not specified. |
Action |
Specify the JMS alert destination. |
INMSUE0023 | Select at least one consumer application |
Explanation |
No consumer applications have been selected. |
Action |
Select at least one consumer application. |
INMSUE0024 | Rule name already exists |
Explanation |
The specified rule name already exists. |
Action |
Specify a different rule name. |
INMSUE0025 | Endpoint URL cannot be empty |
Explanation |
An empty endpoint URL was specified. |
Action |
Specify a value for the endpoint URL. |
INMSUE0026 | Consumer application cannot be empty |
Explanation |
The consumer application was not specified. |
Action |
Specify the consumer application. |
INMSUE0027 | Invalid hour given |
Explanation |
The input for hour is invalid. |
Action |
Enter a valid hour. |
INMSUE0028 | Invalid minute given |
Explanation |
The input for minute is invalid. |
Action |
Enter a valid minute. |
INMSUE0029 | Date cannot be empty |
Explanation |
A date was not entered. |
Action |
Enter a date. |
INMSUE0030 | Assertion type not found |
Explanation |
The assertion type was not found. |
Action |
Specify an assertion type. |
INMSUE0031 | Virtual service name cannot be same as web service name |
Explanation |
The virtual service name should not be the same as the web service name. |
Action |
Specify a different virtual service name. |
INMSUE0032 | HTTP header value cannot be empty |
Explanation |
An HTTP header value was not entered. |
Action |
Enter an HTTP header value. |
INMSUE0033 | HTTP header name cannot be empty |
Explanation |
The HTTP header name is empty. |
Action |
Enter an HTTP header name. |
INMSUE0034 | JMS message property name cannot be empty |
Explanation |
The JMS message property name is empty. |
Action |
Enter a JMS message property name. |
INMSUE0035 | JMS message property value cannot be empty |
Explanation |
The JMS message property value is empty. |
Action |
Enter a JMS message property value. |
INMSUE0036 | Virtual service name cannot have # character |
Explanation |
The virtual service name contains the "#" character. |
Action |
Ensure that the name of the virtual service does not contain the "#" character. |
INMSUE0037 | JMS header name cannot be empty |
Explanation |
The JMS header name is empty. |
Action |
Enter the JMS header name. |
INMSUE0038 | JMS header value cannot be empty |
Explanation |
The JMS header value is empty. |
Action |
Enter the JMS header value. |
INMSUE0039 | Select a policy to delete |
Explanation |
No policy has been selected for deletion. |
Action |
Select a policy to delete. |
INMSUE0062 | Undeploy the Service(s) before deleting the Target |
Explanation |
Before deleting the target, undeploy all virtual services from the target. |
Action |
Make sure that the target instance has no deployed virtual services before trying to delete the target. |
INMSUE0066 | Virtual XML Service with name {0} already exists |
Explanation |
A virtual XML service with the given name already exists. |
Action |
Supply a different name for the virtual XML service. |
INMSUE0067 | HTTP Methods not declared for the native XML Service |
Explanation |
HTTP methods required for the XML service being virtualized were not declared. |
Action |
Update the HTTP methods of the native XML service being virtualized. |
INMSUE0068 | HTTP Methods are not declared for the XML Service |
Explanation |
The HTTP methods cannot be empty when creating an XML service. |
Action |
Select any one of the HTTP methods provided to create an XML Service. |
INMSUE0069 | Select an HTTP Method for Entry Protocol |
Explanation |
HTTP Methods for an entry protocol policy of a virtual XML service cannot be empty |
Action |
Select any one of the options available for HTTP Methods for an Entry Protocol policy |
INMSUE0070 | Select the data type for predefined context variable |
Explanation |
The data type for the predefined context variable should be selected. |
Action |
Select either the String or Int data type for the predefined context variable. |
INMSUE0071 | Select the name for predefined context variable |
Explanation |
The context variable name cannot be empty. |
Action |
Select any of the available context variable names. |
INMSUE0072 | Enter the value for predefined context variable |
Explanation |
The context variable value cannot be empty. |
Action |
Enter the value of the selected context variable. |
INMSUE0073 | Select the data type for custom context variable |
Explanation |
The data type for the selected custom context variable is invalid. |
Action |
Select the data type of the custom context variable. |
INMSUE0074 | Enter the name for custom context variable |
Explanation |
The name of the custom context variable cannot be empty. |
Action |
Enter the custom context variable name. |
INMSUE0075 | Enter the value for custom context variable |
Explanation |
The value for the custom context variable cannot be empty. |
Action |
Enter the value for the custom context variable. |
INMSUE0076 | Virtual REST Service with name {0} already exists |
Explanation |
A virtual REST service with the given name already exists. |
Action |
Supply a different name for the virtual REST service. |
INMSUE0077 | Select at least one asset to deploy |
Explanation |
There are no assets selected for deployment |
Action |
Please select the assets to be deployed |
INMSUE0078 | User does not have permission to create groups in the organization |
Explanation |
When a target is created, a corresponding synchronization group is created in the organization selected with the given target name, but the user who is trying to create the target does not have permission to create a group in the organization he belongs to or the selected organization. |
Action |
Grant manage users permission to the user. |
INMSUE0079 | Abstract WSDL services cannot be virtualized |
Explanation |
The chosen service is an abstract service and hence cannot be virtualized |
Action |
Please choose a service which has concrete service definitions to virtualize |
INMSUE0080 | Reserved characters except _ and - and non-ASCII characters are not allowed in the virtual service name. |
Explanation |
The virtual service name can only contain the letters A-Z, a-z, numbers from 0-9, _ and - characters. |
Action |
Remove the special characters from the virtual service name. |
INMSUE0081 | Logged in user {0} does not have permission to deploy the asset |
Explanation |
To deploy an asset to the target, the user must have manage targets permission. |
Action |
Request the manage targets permission from the CentraSite administrator and try again. |
INMSUE0083 | Hard Limit value should not be empty |
Explanation |
Number. Required. Specifies the maximum number of invocations allowed per Interval before stopping the processing of further requests and issuing an alert. Typically, this limit should be higher than the soft limit. |
Action |
On Save of Throttling Policy |
INMSUE0085 | Select Consumer Application to Limit traffic |
Explanation |
Specifies the consumer application(s) that this action applies to. To specify multiple consumer applications, use the plus button to add rows, or select Any Consumer |
Action |
Specifies the consumer application(s) that this action applies to. To specify multiple consumer applications, use the plus button to add rows, or select Any Consumer |
INMSUE0086 | Soft Limit value should not be empty |
Explanation |
Number. Optional. Specifies the maximum number of invocations allowed per Interval before issuing an alert. Reaching the soft limit will not affect further processing of requests (until the Hard Limit is reached. |
Action |
On Save of Throttling Policy |
INMSUE0087 | Soft Limit should not be higher than the Hard Limit |
Explanation |
Hard limit should be higher than the soft limit |
Action |
On Save of Throttling Policy |
INMSUE0089 | Reserved characters except _ and - and non-ASCII characters are not allowed in the target name. |
Explanation |
The target name can only contain the letters A-Z, a-z, numbers from 0-9, _ and - characters. |
Action |
Remove the special characters from the target name. |
INMSUI0082 | Service URL is invalid |
Explanation |
Service URL should not contain characters like * |
Action |
Replace character ' * ' with a valid character. |
INMSUI0084 | Interval should not be empty. |
Explanation |
Specifies the amount of time for the soft limit and hard limit to be reached. |
Action |
Specifies the amount of time for the soft limit and hard limit to be reached. |
INMSUI0088 | Please enter a valid URL or URI |
Explanation |
A URL or URI was specified that is an invalid endpoint. |
Action |
Specify a valid URL or URI. |
INMUCE0001 | Error while creating Axis2 SOAP Service Stub for UDDI Security API |
Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure that the classpath has the correct version of Axis2 jars. |
INMUCE0002 | Error while creating Axis2 SOAP Service Stub for UDDI Inquiry API |
Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure the classpath has the correct version of Axis2 jars. |
INMUCE0003 | Error while creating Axis2 SOAP Service Stub for UDDI Publish API |
Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure the classpath has the correct version of Axis2 jars. |
INMUCE0004 | Error while creating Axis2 SOAP Service Stub for UDDI Subscription API |
Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure the classpath has the correct version of Axis2 jars. |
INMUCE0005 | Error while creating Axis2 SOAP Service Stub for Taxonomy API |
Explanation |
This error may happen if the host or port specified in RegistryConfiguration is not valid or if there is an incorrect version of Axis jars in the classpath. |
Action |
Please make sure the host and port of the registry provided in RegistryConfiguration are valid. And also make sure the classpath has the correct version of Axis2 jars. |
INMUCE0006 | Not able to connect to the UDDI Registry. get_authToken call failed. |
Explanation |
Remote exception thrown while connecting to UDDI registry. |
Action |
Please make sure the host and port provided in RegistryConfiguration are valid. |
INMUCE0007 | Not able to connect to the UDDI Registry. discard_authToken call failed. |
Explanation |
Remote exception thrown while connecting to UDDI registry. |
Action |
Please make sure the host and port provided in RegistryConfiguration are valid. |
INMUCE0008 | Not able to fetch the modified date of service with key {0}. get_operationalInfo call failed due to RemoteException. |
Explanation |
Remote exception was thrown while getting operational info for the given service. |
Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
INMUCE0009 | Not to able to fetch the virtual services for the specified target {0} |
Explanation |
Not to able to fetch the virtual services for the specified target {0}, as remote exception was caught in find_service call. |
Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
INMUCE0011 | Not able to fetch the service with name {0}. find_service call failed due to RemoteException. |
Explanation |
Remote exception was thrown while inquiring the registry for services. |
Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
INMUCE0012 | Not able to fetch the details of the service {0}. get_serviceDetail call failed due to RemoteException. |
Explanation |
Remote exception was thrown while inquiring the registry for service details. |
Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
INMUCE0013 | Not able to fetch the details of the tModel {0}. get_tModelDetail call failed due to RemoteException. |
Explanation |
Remote exception was thrown while inquiring the registry for tModel details. |
Action |
Please make sure the registry is running the host and port provided in RegistryConfiguration. |
INMUCW0010 | Unable to find the virtual service with specified name {0} |
Explanation |
There is not virtual service with the specified name in the UDDI registry. |
Action |
Please make sure the UDDI registry has a virtual service with the specified name. If it exists please make sure the user provided in RegistryConfiguration has the privilege to view the virtual service. |
INMVSE0001 | Internal JAXR error happened |
Explanation |
An exception inside JAXR occurred. |
Action |
Analyze the JAXR exception given by the stack. |
INMVSE0002 | Invalid NULL parameter given |
Explanation |
A version interface method was called with invalid parameters containing NULL. |
Action |
Correct the usage of the version management interface. |
INMVSE0003 | Object of type {0} not supported for External Link versioning |
Explanation |
This object must not be used for duplicating external links. |
Action |
Do not use this kind of object. |
INMVSE0004 | Invalid external link for versioning, must be a WebDAV one. URI: {0} |
Explanation |
The external link object provided for versioning is not supported. It must be an external link of a WebDAV resource. |
Action |
Do not use this kind of external link. |
INMVSE0005 | Unexpected external link. URI: {0} |
Explanation |
During external link versioning the exteranl link handling was unexpected. |
Action |
Check your WebDAV resources of external links. |
INMVSE0006 | Object of type {0} not supported for a versioning operation |
Explanation |
A non-versionable object was found during a versioning operation. |
Action |
Check your registered objects. |
INMVSE0007 | Unexpected: no new external link in duplication list |
Explanation |
Internal error: an element was not properly duplicated during versioning. |
Action |
Contact your software supplier. |
INMVSE0008 | Object to be versioned ({0}) does not have the highest version number |
Explanation |
The registry object to be versioned is an intermediate one in the versioning hierarchy, which is not permitted. |
Action |
Use only the highest versioned object for a versioning action. |
INMVSE0009 | Object ({0}) is not granted for a versioning operation. |
Explanation |
A registered listener rejected the object for the given versioning operation. |
Action |
Check your registry entries and why the listener has denied the action. |
INMVSE0010 | Invalid association ID specified: {0} |
Explanation |
An invalid association type was specified by the user of the API. |
Action |
Correct the association type, e.g. for HasParent, Uses, etc. |
INMVSE0011 | Invalid WebDAV URL: {0} |
Explanation |
The WebDAV URL has an invalid format. |
Action |
Correct the format. |
INMVSE0012 | WebDAV cannot be accessed |
Explanation |
Failure on WebDAV access. |
Action |
Inspect the original exception. |
INMVSE0013 | Resource cannot be stored to WebDAV |
Explanation |
Internal error on storing a file to WebDAV. |
Action |
Inspect the original exception. |
INMVSE0014 | Unexpected: copied object not found in list |
Explanation |
An object which was duplicated was not found in the list holding those elements. |
Action |
No action required. |
INMVSE0015 | Unsupported copy mode for a Package object |
Explanation |
The copy mode for versioning a package is not supported. |
Action |
Use only supported copy modes. |
INMVSE0016 | Error retrieving checkpoint objects for ID: {0} |
Explanation |
The revision or checkpoint object cannot be determined. |
Action |
See the embedded exception description. |
INMVSE0017 | Error finding checkpoint records |
Explanation |
Checkpoint records couldn't be determinded during a find with qualifiers. |
Action |
See the embedded exception description. |
INMVSE0018 | The restore of revision objects failed |
Explanation |
The replacement of the current object with an older revision of the object was not successful. |
Action |
See the embedded exception description. |
INMVSE0019 | The method is not allowed if revision feature not enabled |
Explanation |
The revision feature must be enabled in CentraSite before using certain methods. |
Action |
Enable CentraSite's revision feature. |
INMVSE0020 | Checkpoint label {0} already in use |
Explanation |
A checkpoint label must only be used once in the system. |
Action |
Use another label or delete the label first. |
INMVSE0021 | Setting of checkpoint label '{0}' failed |
Explanation |
Setting of checkpoint label to revision objects failed. |
Action |
See embedded exception description. |
INMVSE0022 | Error reading checkpoint with label '{0}' |
Explanation |
Reading revision objects failed due to an internal reason. |
Action |
See embedded exception description. |
INMVSE0023 | Error on finding checkpoint label names |
Explanation |
Retrieving all checkpoint label names was not successful. |
Action |
See embedded exception description. |
INMVSE0024 | Error during deletion of checkpoint label '{0}' |
Explanation |
Deleting checkpoint labels from objects was not successful. |
Action |
See embedded exception description. |
INMVSE0025 | Checkpoint label count cannot be determined |
Explanation |
The checkpoint label count cannot be determined due to internal problems. |
Action |
Please contact your software supplier. |
INMVSE0026 | Error getting minor version of object: {0} |
Explanation |
Error getting minor version of object. |
Action |
See embedded exception description. |
INMVSE0027 | Error getting checkpoint label of object: {0} |
Explanation |
Error getting checkpoint label of object. |
Action |
See embedded exception description. |
INMVSE0028 | Invalid keepCount parameter |
Explanation |
Invalid keepCount parameter. |
Action |
Correct the keepCount parameter. |
INMVSE0029 | Error purging checkpoints of object: {0} |
Explanation |
Error purging checkpoints of object. |
Action |
See embedded exception description. |
INMVSE0030 | Revision and Checkpoint enablement failed |
Explanation |
Revision and Checkpoint enablement failed. |
Action |
See embedded exception description. |
INMVSE0031 | Disable of Revision and Checkpoint failed |
Explanation |
Disable of Revision and Checkpoint failed. |
Action |
See embedded exception description. |
INMVSE0032 | Base collection not present |
Explanation |
The base CentraSite collection is not available. The registry seems to be inconsistent. |
Action |
Please contact your software supplier. |
INMVSE0033 | The common CentraSite schema is not present. |
Explanation |
Schema CentraSiteObjects is not present. |
Action |
Check the CentraSite environment. |
INMVSE0034 | Asset Type ({0}) does not support the Versioning Capability |
Explanation |
An instance of an asset type should get a new version, but the asset type does not support this. |
Action |
Check the properties of your asset type. |
INMWSE0001 | Unable to connect to {0} using the provided username and password. |
Explanation |
The service was unable to connect to the provided CentraSite address. |
Action |
Make sure the CentraSite address is valid and the username and password are correct. |
INMWSE0002 | Error reading {0}. |
Explanation |
The service was unable to read the document. |
Action |
Make sure that the document is accessible and valid. |
INMWSE0003 | Unable to import service. |
Explanation |
The application was unable to import the service in the CentraSite registry. |
Action |
Make sure the arguments are correct or manually check the CentraSite registry for problems. |
INMWSE0004 | Error retrieving product with name {0}. |
Explanation |
The service was unable to find the product with the provided product name. |
Action |
Make sure that the product name is correct and exists in the CentraSite registry. |
INMWSE0005 | Unable to import {0} {1}. |
Explanation |
The service was unable to import the file. |
Action |
Make sure the arguments are correct or manually check the CentraSite registry for problems. |
INMWSE0006 | Failed to retrieve the imported service ID. |
Explanation |
Unable to retrieve the UDDI key of the service which has been imported. |
Action |
Check connection to CentraSite server. Check the logs for errors. |
INMWSE0007 | Unable to retrieve the registered BPEL process ID. |
Explanation |
The application was unable to retrieve the imported BPEL process ID. |
Action |
Check connection to CentraSite server. Check the logs for errors. |
INMWSE0008 | Unable to import BPEL process. |
Explanation |
The application was unable to import the BPEL process in the CentraSite registry. |
Action |
Make sure the arguments are correct or manually check the CentraSite registry for problems. |
INMWSE0009 | Unable to import XSD schema. |
Explanation |
The service was unable to import the XSD schema in the CentraSite registry. |
Action |
Make sure the arguments are correct or manually check the CentraSite registry for problems. |
INMWSE0010 | Missing attachment with content ID {0}. |
Explanation |
The service was unable to retrieve the attachment. |
Action |
Make sure the content ID of the attachment is valid. |
INMWSE0011 | Invalid file descriptor. Missing file type. |
Explanation |
The value for file type was missing. |
Action |
Make sure the arguments are valid. |
INMWSE0012 | Invalid file descriptor. Missing file name. |
Explanation |
The value for the file name was missing. |
Action |
Make sure the arguments are valid. |
INMWSE0013 | Invalid file descriptor. Missing content ID string. |
Explanation |
The value for the content ID string was missing. |
Action |
Make sure the arguments are valid. |
INMWSE0014 | Invalid file type. Must be XSD, WSDL, BPEL, XPDL, META_INFO, DOCUMENT or REFERENCED. |
Explanation |
CentraSite web services will only accept the following file types: XSD, WSDL, BPEL, XPDL, META_INFO, DOCUMENT or REFERENCED. |
Action |
Please provide valid file type. |
INMWSE0015 | Missing Authorization header. |
Explanation |
Authorization header for HTTP basic authentication was not found in the request. |
Action |
Provide username and password to connect to the CentraSite server. |
INMWSE0016 | The creation of a folder in the temp directory has failed. |
Explanation |
The creation of a folder in the temp directory has failed. The folder could not be created in the temp directory which is determined by the system property java.io.tmpdir. |
Action |
Please make sure that the temp directory has enough free space. |
INMWSE0017 | The creation of folder {0} has failed. |
Explanation |
The specified folder could not be created. |
Action |
Please make sure that you have sufficient privileges to create the folder. |
INMWSE0018 | Exception while importing XPDL |
Explanation |
An exception occurred while importing the XPDL file. |
Action |
Please make sure the SOAP request has all required parameters filled with proper values. |
INMWSE0019 | Referenced file {0} not found |
Explanation |
The XPDL file to be imported has a reference to a web service. But the WSDL file for the referenced file was not passed to the XPDL importer service. |
Action |
Please create a file descriptor for the referenced WSDL file and send it to ImportXPDLService. |
INMWSE0020 | Response from XPDL importer does not contain any registry objects |
Explanation |
The XPDL Importer didn't report any error. Also it didn't return any response which needs to be filled for a web service response. |
Action |
Please make sure the XPDL file contains the Process element which will be created in CentraSite and returned in the web service response. |
INMWSE0021 | Error while fetching LCM state for process |
Explanation |
A system error has occurred while loading the LCM state of the process. |
Action |
Please check whether the Process object is in a valid state. If it is in a valid state, please retry the request. |
INMWSE0022 | Parameter name (wild card) is mandatory input |
Explanation |
This operation requires a keyword as a parameter. In the request, the keyword is not set. |
Action |
Please set the keyword in the SOAP request. |
INMWSE0023 | Error while fetching processes from CentraSite |
Explanation |
A system error has occurred while fetching process objects from CentraSite. Perhaps the connection to the CentraSite Server has been lost. |
Action |
Please check whether the CentraSite Server is up and running. |
INMWSE0024 | Error while fetching services from CentraSite |
Explanation |
A system error has occurred while fetching services from CentraSite. Perhaps the connection to the CentraSite Server has been lost. |
Action |
Please check whether the CentraSite Server is up and running. |
INMWSE0025 | Error while fetching organizations from CentraSite |
Explanation |
A system error has occurred while fetching organizations from CentraSite. Perhaps the connection to the CentraSite Server has been lost. |
Action |
Please check whether the CentraSite Server is up and running. |
INMWSE0026 | Invalid LCM states {0} are used in search filters |
Explanation |
At least one lifecycle state provided in the search filter is not valid. |
Action |
Please provide proper lifecycle states in the search filter. |
INMWSE0027 | Invalid file descriptor. |
Explanation |
The value for file type was missing. |
Action |
Make sure the arguments are valid. |
INMWSE0028 | The XPDL is not passed as FileDescriptor in the request |
Explanation |
The request does not contain a file descriptor. |
Action |
Please pass the XPDL content as the file descriptor in the request. |
INMWSE0029 | Specified organization key {0} is not valid |
Explanation |
CentraSite does not contain an organization with the provided key. |
Action |
Please make sure the organization key provided in the request is valid. |
INMWSE0030 | Specified product {0} is not valid |
Explanation |
CentraSite does not contain the product concept with the specified key. |
Action |
Please make sure the product specified in the request is valid. |
INMWSE0031 | Exception while fetching the properties from META-INFO |
Explanation |
The user can provide attributes with values in the request. CentraSite is not able to fetch the properties from the provided META-INFO file descriptor. |
Action |
Please provide the properties in the format which is supported by CentraSite. Please refer http://localhost:53307/wsstack/services/Property.xsd for the CentraSite supported format. Please replace the host and port in the above URL accordingly. |
INMWSE0032 | Referenced file {0} not found |
Explanation |
The WSDL file to be imported imports another WSDL/XSD. But the other imported WSDL/XSD file was not passed to the WSDL importer service. |
Action |
Please create a file descriptor for the referenced WSDL/XSD file and send it to ImportWSDLService. |
INMWSE0033 | Exception occurred while executing getApprovalHistory operation |
Explanation |
An internal issue occurred while performing the getApprovalHistory operation. It might be a CentraSite issue or the data provided to the CentraSite is not sufficient. |
Action |
Please make sure the web service operation is executed with right set of parameters. |
INMWSE0034 | Exception occurred while executing getPendingApprovals operation |
Explanation |
An internal issue occurred while performing the getPendingApprovals operation. It might be a CentraSite issue or the data provided to the CentraSite is not sufficient. |
Action |
Please make sure the web service operation is executed with right set of parameters. |
INMWSE0035 | Exception occurred while approving the approval flow using approve operation |
Explanation |
An internal issue occurred while performing the approve operation. It might be a CentraSite issue or the data provided to the CentraSite is not sufficient. |
Action |
Please make sure the web service operation is executed with right set of parameters. |
INMWSE0036 | Exception occurred while executing getApprovalRequests operation |
Explanation |
An internal issue occurred while performing the getApprovalRequests operation. It might be a CentraSite issue or the data provided to the CentraSite is not sufficient. |
Action |
Please make sure the web service operation is executed with right set of parameters. |
INMWSE0037 | Exception occurred while executing getApprovalActions operation |
Explanation |
An internal issue occurred while performing the getApprovalActions operation. It might be a CentraSite issue or the data provided to the CentraSite is not sufficient. |
Action |
Please make sure the web service operation is executed with right set of parameters. |
INMWSE0038 | Revert Pending State operation can only be performed by CentraSite Administrator |
Explanation |
Not all users have permission to revert the pending state of a registry object. The user should have the CentraSite Administrator role to perform a revert pending state operation. |
Action |
Please provide the user with CentraSite Administrator role for the revert pending state operation. |
INMWSE0039 | CentraSite does not contain a registry object with the specified key {0}. |
Explanation |
The revert pending state operation requires a key of the registry object which exists in CentraSite. The pending state change cannot be reverted for a registry object that does not exist in CentraSite. |
Action |
Please make sure a registry object exists in CentraSite with the specified key. |
INMWSE0040 | Exception occurred while executing revertPendingStateChange operation |
Explanation |
An internal issue occurred while reverting a pending state change. It might be a CentraSite issue or the data provided to the CentraSite is not sufficient. |
Action |
Please make sure the web service operation is executed with right set of parameters. |
INMWSE0041 | Exception occurred while executing reject operation |
Explanation |
An internal issue occurred while performing the reject operation. It might be a CentraSite issue or the data provided to the CentraSite is not sufficient. |
Action |
Please make sure the web service operation is executed with right set of parameters. |
INMWSE0042 | applicationServeKeyOrName parameter is missing in the request |
Explanation |
This error happens when the user does not set the applicationServerKeyOrName in the request parameter. |
Action |
Set the applicationServerKeyOrName in the request parameter. |
INMWSE0043 | serviceKey parameter is missing in the request message |
Explanation |
This error happens when the user does not set serviceKey in the request parameter. |
Action |
Set the serviceKey in the request parameter. |
INMWSE0044 | Invalid product {0} has been specified in the request |
Explanation |
The value given as product parameter is invalid. |
Action |
Give a valid product name in the product parameter. |
INMWSE0045 | Found {0} {1} application server instances during search. Use application server key to find unique instance. |
Explanation |
This error happens if the search result matches more than one application server instance. |
Action |
Use the key to find a unique application server instance in the web service request operation. |
INMWSE0046 | Failed to associate the given application server {0} and service {1} |
Explanation |
This error may happen if the given CentraSite location is wrong or because of invalid credentials. |
Action |
Check the CentraSite location and its credentials. Also check if the application server instance exists. |
INMWSE0047 | Invalid application server {0} |
Explanation |
The given application server key or name is not valid. |
Action |
Give the correct application server key in the request parameter. |
INMWSE0048 | Parameter name (serviceKeys) is mandatory input |
Explanation |
The serviceKeys element is mandatory for the GetServiceDetails request. |
Action |
Specify at least one service key for the GetServiceDetails request. |
INMWSE0049 | Error while retrieving service detail |
Explanation |
Verify that the given request parameters are appropriate for the getServiceDetails call. |
Action |
Validate the parameters supplied for the getServiceDetails operation. |
INMWSE0050 | Error while retrieving associated type for Lifecycle model {0} |
Explanation |
An error occurred while retrieving an associated type for a lifecycle model. |
Action |
Verify that the associated types for the lifecycle model are appropriate. |
INMWSE0051 | Error while retrieving transition state for the Lifecycle model {0} |
Explanation |
An error occurred while retrieving the transition state for the lifecycle state and lifecycle model. |
Action |
Verify that the transition states are appropriate for the retrieved lifecycle state. |
INMWSE0052 | Error while retrieving LC State for the LC Model {0} |
Explanation |
An error occurred while retrieving a lifecycle state for the lifecycle model. |
Action |
Verify that the lifecycle states are appropriate for the retrieved lifecycle model. |
INMWSE0053 | Error while retrieving LC Model {0} |
Explanation |
An error occurred while retrieving the lifecycle model. |
Action |
Verify that the retrieved lifecycle model is correct. |
INMWSE0054 | Failed to process getLifecycleModels operation |
Explanation |
The getLifecycleModels operation could not be processed. |
Action |
Verify that the parameters are appropriately specified in the request. |
INMWSE0055 | Error while registering the application server {0} |
Explanation |
An error occurred while registering the application server. |
Action |
Verify that the parameters are appropriately specified in the request. |
INMWSE0056 | Error while deregistering the application server |
Explanation |
An error occurred while deregistering the application server. |
Action |
Verify that the parameters are appropriately specified in the request. |
INMWSE0057 | Error while reading product version information |
Explanation |
An error occurred while getting the application server version. |
Action |
Verify that the parameters are specified in the request. |
INMWSE0058 | Error while retrieving installed language information from CentraSite |
Explanation |
Error while retrieving installed language information from CentraSite. |
Action |
Validate the web service request or contact the CentraSite administrator. |
INMWSE0059 | Invalid owner key {0} specified in request |
Explanation |
The request XML contains an invalid owner key. |
Action |
Specify the appropriate owner key in the request XML. |
INMWSE0060 | Invalid organization key {0} specified in request |
Explanation |
The request contains an invalid organization key. |
Action |
Specify an appropriate organization key in the request. |
INMWSE0061 | Invalid object type {0} specified in request |
Explanation |
The request contains an invalid object type. |
Action |
Specify an appropriate object type string in the request. |
INMWSE0062 | Object Type is mandatory when Organization Key is specified in request |
Explanation |
The object type is mandatory when the organization key is specified in the request. |
Action |
Specify a valid object type string in the request. |
INMWSE0063 | Service {0} is not available in organization {1} |
Explanation |
The organization key specified for this service is not correct. |
Action |
Provide the correct organization key of this service. |
INMWSE0064 | Invalid asset key {0} passed in the request |
Explanation |
The request contains an invalid asset key. |
Action |
Pass a valid asset key in the request. |
INMWSE0065 | Error while processing getAssociatedServices request |
Explanation |
An error occurred while processing a getAssociatedServices request. |
Action |
Check if the given request parameters are correct. |
INMWSE0066 | Error while processing releaseProcesses request |
Explanation |
It was not possible to process the releaseProcesses request. |
Action |
Check if the given request parameters are correct. |
INMWSE0067 | CentraSite does not contain an Application Server with the specified key or name {0}. |
Explanation |
A CentraSite web service received a RegisterApplicationServer request with a key or name specified. The web service tried to update the object with the specified key or name, but the web service was not able to find any Application Server object with the specified key or name. |
Action |
Please check whether an Application Server object exists in CentraSite with the specified key or name. If an object exists in CentraSite, please make sure the requested user has view/edit permission on the Application Server object. |
INMWSE0068 | Specified application server {0} does not exist |
Explanation |
The application server name or key given in the request is not valid. |
Action |
Check the given application server name or key and correct it. |
INMWSE0073 | Invalid application server key {0} |
Explanation |
The request contains an invalid application server key. |
Action |
Specify a valid application server key. |
INMWSE0074 | Exception while parsing XPDL file {0} |
Explanation |
CentraSite will parse the specified XPDL file to create corresponding objects in CentraSite. CentraSite is not able to parse the specified the XPDL file as the given XPDL file does not comply with the XML and XPDL specification. |
Action |
Please make sure the specified XPDL file is in accordance with the XML and XPDL specification. |
INMWSE0075 | The given organization key {0} in the request does not match the key of the existing asset's organization {1} |
Explanation |
The organization key given in the importWSDL request does not match the organization key of the existing asset's organization. |
Action |
Provide the existing asset's organization key in the request. |
INMWSE0077 | Failed to find application server in given name {0}. |
Explanation |
This exception is unexpected. The cause is not immediately known. |
Action |
If the problem persists, contact CentraSite administrator. |
INMWSE0078 | Application Server name is empty |
Explanation |
No name was supplied for the application server. |
Action |
Provide a valid application server name. |
INMWSE0079 | Unsupported Association Type {0} |
Explanation |
The specified association type is not supported. |
Action |
Correct the association type. |
INMWSE0080 | Check your access rights and proxy settings. |
Explanation |
You do not have sufficient privileges to access the target object. |
Action |
Execute the action with sufficient privileges. |
INMWSE0081 | The {0} parameter value is null. |
Explanation |
The function shown on the call stack is called with a null value. |
Action |
Correct the client program. |
INMWSE0082 | The credentials parameter value is null. |
Explanation |
The setCredentials() method is called with a null value for the credentials parameter. |
Action |
Correct the client program. |
INMWSE0083 | Specified process {0} is unavailable. |
Explanation |
Process with the specified asset ID is not available. |
Action |
Check the asset ID provided in the request. |
INMWSI0069 | Asset {0} is already associated with the server {1} |
Explanation |
The given asset key request is already associated with the specified application server. |
Action |
Remove the asset key from the request. |
INMWSI0070 | Asset {0} has been associated with the server {1} successfully |
Explanation |
The asset {0} has been associated with the server {1} successfully. |
Action |
The association between the asset key and the server was created successfully. |
INMWSI0071 | The asset {0} has not been associated with the server {1} |
Explanation |
The asset is not associated with the specified server. |
Action |
Associate the asset and the server first before disassociating. |
INMWSI0072 | Asset {0} has been disassociated from the server {1} successfully |
Explanation |
The given asset has been disassociated from the server successfully. |
Action |
The given asset has been disassociated from the server successfully. |
INMWSI0076 | Application server does not exist for given name {0}. |
Explanation |
An application server does not exist in the given name. |
Action |
Create an application server in the given name. |
INOQJE0001 | XQConnection for {0} is closed! |
Explanation |
The connection to the specified database is closed. |
Action |
Make sure that the connection in use is not closed prior to any later operation. |
INOQJE0002 | XQExpression is closed! |
Explanation |
The underlying expression is already closed. |
Action |
Make sure that the expression / connection in use is not closed prior to any later operation. |
INOQJE0003 | XQItemType mismatch! Item is not of type {0}. |
Explanation |
The specified item is not of the declared item type. |
Action |
Check for the compatibility of item types. |
INOQJE0004 | No cursor handle given! |
Explanation |
The cursor associated with the query handle was not found. |
Action |
This happens if there is no proper result set associated with the specified query. |
INOQJE0005 | Error reading from file - {0} |
Explanation |
This exception is thrown by the Java run-time architecture when an input error has occurred while reading from the specified file. |
Action |
Possible causes for this exception are an error reading from the specified file or the specified file is not found. |
INOQJE0006 | Error while parsing the XMLStream - {0} |
Explanation |
This is an error for unexpected errors during processing / XML handling, namely, to report well-formedness errors as well as unexpected processing conditions. |
Action |
The error message contains the explanation from the StAX parser. Modify the XML accordingly. |
INOQJE0007 | Parser configuration error - {0} |
Explanation |
Indicates a serious configuration error. An exception occurred during configuration of the XML parser being used. |
Action |
Add the corresponding XML parser jars in the CLASSPATH. |
INOQJE0008 | Factory Configuration Error - {0} |
Explanation |
A problem with configuration of the Parser Factories exists. This error will typically be thrown when the class of a parser factory specified in the system properties cannot be found or instantiated. |
Action |
Add the XML parser jars to the CLASSPATH and set the JAXP factory names. |
INOQJE0009 | Cannot access the XQItem of type XQITEMTYPE_ATTRIBUTE |
Explanation |
Indicates that the base item type of the current item is an attribute while writing the current item to a SAX stream. |
Action |
The current item should not be of type attribute. |
INOQJE0010 | SAX Parse Error - {0} |
Explanation |
Represents a general SAX error or warning. |
Action |
Possible causes for this error are if the value of the "org.xml.sax.driver" system property is null or the class cannot be loaded and instantiated. |
INOQJE0011 | I/O Error - {0} |
Explanation |
This exception is thrown by the Java run-time architecture when an input / output error of some kind has occurred while reading from the specified input source. |
Action |
Refer to the Java documentation for the error message. |
INOQJE0012 | End of the sequence is reached |
Explanation |
Execution of an XQuery returns a sequence of results. You can traverse the sequence of results using the XQResultSequence API. |
Action |
Reading or trying to modify items in the sequence after reaching the end of the sequence will result in this error. |
INOQJE0013 | Positioned before the start of the sequence |
Explanation |
Execution of an XQuery returns a sequence of results. You can traverse the sequence of results using the XQResultSequence API. Invoking the next() method for the first time will get to the first item in the sequence. If any operations are tried before this, this will result in this error. |
Action |
Invoke the next() method to get the first item. |
INOQJE0014 | Server {0} unavailable |
Explanation |
The specified database or server is not running. |
Action |
Provide the correct database URL, and check if the database is stopped. |
INOQJE0015 | Error when attempting to change the transaction mode |
Explanation |
The attempt to change the transaction mode failed. |
Action |
Check the Server documentation for the specified error code in the error message. |
INOQJE0016 | Error closing the {0} |
Explanation |
An attempt to close the underlying connection or result sequence that is specified along with the error failed. |
Action |
Make sure that the underlying connection is not closed before closing the result sequence. |
INOQJE0017 | Transaction failed while committing the changes |
Explanation |
Committing the changes failed. |
Action |
Check the Server documentation for the specified error code in the error message. |
INOQJE0018 | Transaction failed while rolling back the changes |
Explanation |
Rolling back the changes failed. |
Action |
Check the Server documentation for the specified error code in the error message. |
INOQJE0019 | The scrollability type {0} is not supported |
Explanation |
The mentioned scrollability type is not supported. |
Action |
Set a valid value for the scrollability type. |
INOQJE0020 | The property {0} is not supported |
Explanation |
The mentioned property is not supported. |
Action |
Provide a valid property. |
INOQJE0021 | A property mentioned in the list is not supported |
Explanation |
One of the mentioned properties in the property list is not supported. |
Action |
Check if all the properties in the property list are supported by the current implementation. |
INOQJE0022 | Error executing the server command : {0} |
Explanation |
An error occurred while executing the specified database command. |
Action |
Please refer to the documentation of the specified command. |
INOQJE0023 | XQTypeException thrown - Error Code : {0} Message : {1} |
Explanation |
External variable binding to XQuery failed. |
Action |
Check the server documentation for the error code displayed in the error. |
INOQJE0024 | Error fetching cursor |
Explanation |
Indicates a cursor based failure when fetching a number of documents from a cursor. |
Action |
Check the server documentation for the error code displayed in the error. |
INOQJE0025 | XQuery exception: {0} |
Explanation |
Error in the XQuery. |
Action |
Please check the XQuery for errors. |
INOQJE0026 | Error while opening cursor |
Explanation |
Indicates a failure when opening a cursor. |
Action |
Check the server documentation for the error code displayed in the error. |
INOQJE0027 | Error executing XQuery {0}: {1} |
Explanation |
Executing the XQuery failed. See the error code for more information. |
Action |
Check the server documentation for the error code displayed in the error. |
INOQJE0028 | Sequence is non-scrollable |
Explanation |
Cannot scroll on a non-scrollable sequence. |
Action |
Avoid scrolling, because the sequence is non-scrollable. |
INOQJE0029 | Failed because of following exception |
Explanation |
The cause of the exception is specified in the error message. |
Action |
Check the server documentation for the specified error code in the error message. |
INOQJE0030 | Error creating the cached item |
Explanation |
Creating a cached item failed. |
Action |
Check if the items are closed. |
INOQJE0031 | Error binding the {0} Message - {1} |
Explanation |
Binding the specified value to the expression / prepared expression failed. |
Action |
Check if the values declared and bound to the query are the same. |
INOQJE0032 | Error executing the request with error [{0} {1} {2} {3}] |
Explanation |
The message appears with the specific error code and information from the server. |
Action |
Refer to the server documentation for the specified error code. |
INOQJE0033 | Sequence not scrollable |
Explanation |
Cannot scroll a non scrollable sequence. |
Action |
Avoid scrolling, because the sequence is non-scrollable. |
INOQJE0034 | Expected type {0} Current type {1} Location {2} |
Explanation |
The expected type and the current type specified do not match. |
Action |
Check the types mentioned in the error at the specified location. |
INOQJE0035 | Expected start or end tag {0} |
Explanation |
When trying to move to the next tag in the resulting XML Stream, any white space , COMMENT, or PROCESSING_INSTRUCTION is skipped until a START_ELEMENT or END_ELEMENT is reached. If anything other than white space characters, COMMENT, PROCESSING_INSTRUCTION, START_ELEMENT, END_ELEMENT is encountered, this error is thrown along with the location number. |
Action |
Check the error message for the missing start or end in the XML. |
INOQJE0036 | {0} cannot be null! |
Explanation |
The underlying object specified is null. |
Action |
Make sure that the underlying object is properly initialized. |
INOQJE0037 | The {0} method is not supported |
Explanation |
The method specified in the error message is not supported. |
Action |
The specified method is not supported by the current XQJ implementation. |
INOQJE0038 | XQPreparedExpression is closed! |
Explanation |
The underlying prepared expression is already closed. |
Action |
Make sure that the XQPreparedExpression is not closed before any usage. |
INOQJE0039 | XQSequence is closed! |
Explanation |
The underlying sequence is already closed. |
Action |
Make sure that the XQSequence is not closed before any usage. |
INOQJE0040 | XQItem is closed! |
Explanation |
The underlying item is already closed. |
Action |
Make sure that the XQItem is not closed before any usage. |
INOQJE0041 | The value for the property {0} cannot be null |
Explanation |
The value for the specified property in the error message cannot be null. |
Action |
Mention a property value for the specified property name in the error message. |
INOQJE0042 | Access Failure Exception - {0} |
Explanation |
The cause for the exception is specified in the error message. |
Action |
Check the server documentation for the specified error code in the error message. |
INOQJE0043 | Invalid user ID or password |
Explanation |
The supplied user ID and password combination is invalid. |
Action |
Check the user ID and password. |
INOQJE0044 | Cannot access the XQItem of type XQITEMKIND_ATTRIBUTE |
Explanation |
This indicates that the item kind of the current item is an attribute while writing the current item to a SAX stream. |
Action |
The current item should not be of type attribute. |
INOQJE0045 | Error creating the XQ item |
Explanation |
An error occurred while creating an XQ item. |
Action |
Check if the items are closed. |
INOQJE0046 | Binding to {0} not supported |
Explanation |
While binding an external variable to an XQuery, the type specification was not valid. Either the type is not supported at all for binding external variables, or it was used with a binding method that does not support this specific type. |
Action |
Use one of the supported types with a proper binding method. |
UDDIE00002 | No businessKey was defined |
Explanation |
Keys have to be specified to fetch the details. |
Action |
Please provide keys in the UDDI request to fetch the details. |
UDDIE00005 | At least keyBag or transferToken should be specified |
Explanation |
The discard_transferToken request is not valid. It has to be according to the UDDI v3 specification. |
Action |
Please specify transferToken to discard it. |
UDDIE00006 | The value of the attribute maxRows is not a valid number. |
Explanation |
The value for the maxRows attribute in the UDDI request should be a number. |
Action |
Please specify an integer value for the maxRows attribute in the UDDI request. |
UDDIE00007 | {0} is not a valid find qualifier value in version {1}. |
Explanation |
The find qualifier is not supported in the specified version. |
Action |
Please specify find qualifiers corresponding to the UDDI version. |
UDDIE00008 | No entityKey was defined |
Explanation |
Keys have to be specified to fetch the operationa info. |
Action |
Please provide keys in the get_operationalInfo request to fetch the operational information. |
UDDIE00011 | Publisher assertions are null |
Explanation |
The add_publisherAssertions, delete_publisherAssertions and set_publisherAssertions requests should have publisher assertions in them. |
Action |
Please add the publisherAssertions element in add_publisherAssertions, delete_publisherAssertions and set_publisherAssertions requests. |
UDDIE00012 | Exactly one BusinessKey must be defined. |
Explanation |
Either fromKey, toKey or businessKey should be specified. |
Action |
Please specify a value for the toKey or fromKey or businessKey attribute of the find_relatedBusiness call. |
UDDIE00013 | Only one keyedReference element may be defined in a find_relatedBusinesses message. |
Explanation |
The publisher assertion should contain only one keyedReference element. |
Action |
Please provide one KeyedReference in the find_relatedBusiness call. |
UDDIE00014 | {0} is not a valid UUID. |
Explanation |
The specified key is not valid. |
Action |
Please make sure the key is valid according to the UDDI standard. |
UDDIE00015 | The specified names are not valid for version |
Explanation |
The names are not specified according to the UDDI specification. |
Action |
Please specify valid names. |
UDDIE00016 | Only one key may be defined |
Explanation |
Multiple keys are defined for the UDDI entity. |
Action |
Please specify a single key for the UDDI entity. |
UDDIE00017 | The fromKey element is mandatory in a publisherAssertion document |
Explanation |
The fromKey element does not contain a valid value. |
Action |
Please provide values for the fromKey element in the publisherAssertion element. |
UDDIE00018 | The toKey element is mandatory in a publisherAssertion document |
Explanation |
The toKey element does not contain valid value. |
Action |
Please provide values for the toKey element in the publisherAssertion element. |
UDDIE00019 | The keyedReference element is mandatory in a publisherAssertion document |
Explanation |
The keyedReference element does not contain valid value. |
Action |
Please provide values for the keyedReference element in the publisher assertion element. |
UDDIE00020 | The keyedReference element in a publisherAssertion must be defined exactly one time |
Explanation |
The publisher assertion should contain only one keyedReference element. |
Action |
Please provide one KeyedReference in the publisher assertion element. |
UDDIE00022 | {0} is not a valid findQualifier value |
Explanation |
Provided findQualifier is not valid. The valid qualifiers can be found in UDDI specification. |
Action |
Please provide findQualifiers according to the UDDI specification |
UDDIE00024 | The string representation may not be empty. |
Explanation |
A value for the element in the UDDI request is not according to the UDDI specification. |
Action |
Please make sure the UDDI request is valid according to UDDI specification. |
UDDIE00025 | A tag of the language code must have at least one character and no more than eight characters. |
Explanation |
A value for the language code in the UDDI request does not comply with the UDDI specification. |
Action |
Please make sure the UDDI request is valid according to UDDI specification. |
UDDIE00026 | A language code may only contain ASCII alphanumerics. |
Explanation |
A value for the language code in the UDDI request does not comply with the UDDI specification. |
Action |
Please make sure the UDDI request is valid according to UDDI specification. |
UDDIE00027 | Could not authenticate the user {0} |
Explanation |
The user specified in the UDDI request is not valid. |
Action |
Please specify a valid CentraSite user. |
UDDIE00042 | {0} does not represent a businessKey. |
Explanation |
CentraSite does not contain any business entity with the specified key. |
Action |
Please make sure the business key specified in the request is valid. |
UDDIE00043 | No businessKey in the registry matches the key {0}. |
Explanation |
CentraSite does not contain any business entity with the specified key. |
Action |
Please make sure the business key specified in the request is valid. |
UDDIE00045 | No entity in the registry matches the key {0}. |
Explanation |
CentraSite does not contain any UDDI entity with the specified key. |
Action |
Please make sure the key specified in the request is valid. |
UDDIE00047 | The value of maxRows parameter is not a valid number. |
Explanation |
The value for the maxRows attribute in the UDDI request should be a number. |
Action |
Please specify an integer value for the maxRows attribute in the UDDI request. |
UDDIE00049 | The contact {0} already exists. Please specify a different contact. |
Explanation |
The specified contact already exists in the CentraSite. A contact cannot be present in multiple businesses |
Action |
Please make sure the contact is not present in any other business |
UDDIE00050 | The value of maxEntities parameter is not valid |
Explanation |
The maxEntities attribute of the subscription should contain an valid non-negative number. |
Action |
Please provide valid non-negative number for the maxEntities attribute. |
uddi:107e04bd-bdf4-11e2-b6b3-c566c3aaf997 | Verify Required Attributes |
Explanation |
During asset instance creation and modification, verifies whether the required attributes of that Asset Type are provided with values |
uddi:18bf0e3d-bdf4-11e2-b6b3-886f1ce73523 | Verify Required Attributes Policy |
Explanation |
During asset instance creation and modification, this policy verifies whether the required attributes of that Asset Type are provided with values. |
uddi:44e3e2de-064c-432f-b67a-8fbca0fb04d6 | Invoke webMethods Integration Server |
Explanation |
Processing steps calling an Integration Server (IS) Service which will be executed when the consumer invokes the Virtual Service. |