TCM-00006 to TCM-99009

31 TCM-00006 to TCM-99009

TCM-00006: The NameId for the request is not valid.
Category:: Requests/Responses
Cause:: The NameId for a service request did not contain a Name or an Identifier.
Action:: Provide either a Name or an Identifier for a service request.

TCM-00007: The Id for the request is not valid.
Category:: Requests/Responses
Cause:: The document identifier for the request was not valid. The value supplied was null or an empty string.
Action:: Provide a valid document identifier for a document service request.

TCM-00008: The SectionFlags for the request are not valid.
Category:: Programmatic
Cause:: The wrong section flags were provided for the request.
Action:: Consult the API documentation for the proper section flags for the request.

TCM-00009: No session has been established.
Category:: Requests/Responses
Cause:: A session was expected to exist but was not found. This may occur if operations were called after logging out.
Action:: Log in and properly establish a session before attempting an operation.

TCM-00010: The version of the JRE used by the repository is too low to support Imaging. The required minimum is {0}. The repository is using {1}.
Category:: Configuration
Cause:: An attempt was made to establish a connection to a Content Server repository using the wrong JRE.
Action:: Upgrade the Content Server JRE to the minimum required version. The required version will be stated in the error message.

TCM-00013: Basic Authentication requires SSL.
Category:: Configuration
Cause:: An attempt was made to log in to imaging without using SSL, which is required.
Action:: Configure the imaging server for SSL and use https in the web services URL.

TCM-00015: Unable to find file {0}
Category:: Requests/Responses
Cause:: A file used for input could not be found.
Action:: Check the file path given in the error message and verify that it exists.

TCM-00016: Unable to open file {0}
Category:: Requests/Responses
Cause:: A file used for input could not be opened.
Action:: Check the file path given in the error message and verify that it is readable.

TCM-00020: Unable to authenticate user.
Category:: Requests/Responses
Cause:: Invalid credentials were supplied during login.
Action:: Provide valid credentials.

TCM-00021: This session is already established.
Category:: Requests/Responses
Cause:: An attempt was made to log in to a session that was already established.
Action:: Either use the existing session without logging in again, or log out to establish a new session.

TCM-00022: Service was called without credentials. The calling user cannot be authenticated.
Category:: Requests/Responses
Cause:: No credentials were provided for the service request.
Action:: Ensure the proper security credentials are applied to the login services.

TCM-00026: The requested definition is not found.
Category:: Requests/Responses
Cause:: The definition requested does not exist. The user does not have access to the definition.
Action:: Check the requested definition name or identifier for correctness. Check the user's access to the requested definition.

TCM-00027: User does not have permission to access this page.
Category:: Requests/Responses
Cause:: An attempt was made to access a definition page that the user does not have permission to access.
Action:: Check the user's permissions to the requested definition.

TCM-00028: The definition arrays supplied are empty.
Category:: Programmatic
Cause:: The definitions supplied for an import or export operation were empty arrays.
Action:: Make sure that the definitions arrays are filled in with valid definition NameIds.

TCM-00029: The {0} section is read-only and cannot be modified.
Category:: Programmatic
Cause:: At least one definition section specified for modify was read only and cannot be changed.
Action:: Remove the read-only section from the modify section set argument.

TCM-00030: Invalid date string: {0}
Category:: Requests/Responses
Cause:: The value that was parsed was not a supported date format.
Action:: Fix the value so that it is a supported date format.

TCM-00031: Invalid group, the groupPrincipalHolder is null!
Category:: Requests/Responses
Cause:: The groupPrincipalHolder is null!
Action:: If using Active Directory please verify that the security provider "Use Token Groups for Group Membership Lookup" is disabled or that the configured security provider user accessing Active Directory has tokenGroups privileges to the LDAP.

TCM-00040: Encountered exception initializing regions.
Category:: Requests/Responses
Cause:
Action:

TCM-00041: Cache is Ready = {0}
Category:: Requests/Responses
Cause:
Action:

TCM-00042: Cache Distributed = {0}
Category:: Requests/Responses
Cause:
Action:

TCM-00043: Imaging region exists.
Category:: Requests/Responses
Cause:
Action:

TCM-00044: Cache failed during initialization and may be disabled.
Category:: Requests/Responses
Cause:
Action:

TCM-00045: The cache age limit must be set to a positive number
Category:: Requests/Responses
Cause:
Action:

TCM-00102: Workflow Agent login failure.
Category:: Requests/Responses
Cause:: The Workflow Agent failed to log in.
Action:: Review the server logs for further information.

TCM-00103: Workflow Agent logout failure.
Category:: Requests/Responses
Cause:: The Workflow Agent failed to log out.
Action:: Review the server logs for further information.

TCM-00104: Workflow Agent error processing a message.
Category:: Requests/Responses
Cause:: An error occurred trying to process a worklfow agent message.
Action:: Review the server logs for further information.

TCM-00105: Document {0} returning to workflow agent queue for retry.
Category:: Requests/Responses
Cause:
Action:

TCM-00106: Workflow agent processing fault recorded for document {0}.
Category:: Requests/Responses
Cause:: An error was encountered processing a document. The document was identified in the error message. The error could be due to the workflow server being down.
Action:: Review the server logs for further information. The workflow agent will attempt to reprocess the document.

TCM-00107: Workflow agent cannot record fault for document {0}. Returning to workflow agent queue for retry.
Category:: Requests/Responses
Cause:: An error was encountered processing a document, and the workflow agent was unable to record the error as a fault. The document was identified in the error message.
Action:: Review the server logs for further information. The workflow agent will attempt to reprocess the document.

TCM-00110: Constructed Input Agent Bean.
Category:: Requests/Responses
Cause:
Action:

TCM-00111: Destroyed Input Agent Bean.
Category:: Requests/Responses
Cause:
Action:

TCM-00112: Input Agent encountered an error during shutdown.
Category:: Requests/Responses
Cause:
Action:

TCM-00113: An error occurred trying to read the Input Agent configuration.
Category:: Requests/Responses
Cause:: An error occurred trying to read the Input Agent Bean configuration.
Action:: Review the server logs for further information.

TCM-00114: An error occurred initializing the Input Agent Bean.
Category:: Requests/Responses
Cause:: An error occurred initializing the Input Agent Bean.
Action:: Review the server logs for further information.

TCM-00115: Beginning Input Agent initialization.
Category:: Requests/Responses
Cause:
Action:

TCM-00116: Input Agent initialization is complete.
Category:: Requests/Responses
Cause:
Action:

TCM-00118: Input Agent timer service is not initialized. Cannot continue.
Category:: Requests/Responses
Cause:: Input Agent timer service is not initialized.
Action:: Check the Application Server installation and restart the service.

TCM-00119: Input Agent configuration is empty. Cannot continue.
Category:: Requests/Responses
Cause:: Input Agent configuration is empty.
Action:: Check the JDBC connection and reboot the server.

TCM-00120: Input Agent time interval is not set. Cannot continue.
Category:: Requests/Responses
Cause:: Input Agent time interval is not set.
Action:: Update the Check Interval setting to a valid value in the WebCenter Content: Imaging config MBean.

TCM-00121: An error occurred resetting an input job.
Category:: Requests/Responses
Cause:: An error occurred resetting an input job.
Action:: Review the server logs for further information.

TCM-00122: An error occurred checking for work.
Category:: Requests/Responses
Cause:
Action:

TCM-00126: Beginning Input Agent servlet initialization.
Category:: Requests/Responses
Cause:
Action:

TCM-00127: Input Agent servlet initialization is complete.
Category:: Requests/Responses
Cause:
Action:

TCM-00128: The JMS Queue browser cannot be closed properly.
Category:: Requests/Responses
Cause:: There was a problem closing the JMS Queue browser.
Action:: Review the server logs for more information.

TCM-00129: Input Agent is checking for work.
Category:: Requests/Responses
Cause:
Action:

TCM-00130: Beginning Input Agent Cleanup timer initialization.
Category:: Requests/Responses
Cause:
Action:

TCM-00131: Input Agent Cleanup timer initialization is complete.
Category:: Requests/Responses
Cause:
Action:

TCM-00132: Input Agent Cleanup is looking for expired images.
Category:: Requests/Responses
Cause:
Action:

TCM-00150: Constructed Input Filing MDB.
Category:: Requests/Responses
Cause:
Action:

TCM-00151: Destroyed Input Filing MDB.
Category:: Requests/Responses
Cause:
Action:

TCM-00152: Error while unregistering Input Filing MDB.
Category:: Requests/Responses
Cause:: An error occurred while unregistering Input Filing MDB.
Action:: Review the server logs for further information.

TCM-00153: Beginning filing for Input {0} and data source {1}.
Category:: Requests/Responses
Cause:
Action:

TCM-00154: Filing {0} completed successfully with {1} documents processed successfully out of {2} documents.
Category:: Requests/Responses
Cause:
Action:

TCM-00155: Filing {0} failed with {1} documents that failed to index.
Category:: Requests/Responses
Cause:
Action:

TCM-00156: Error indexing document number {0}.
Category:: Requests/Responses
Cause:: An error occurred while indexing a document.
Action:: Review the server logs for further information.

TCM-00157: An error occurred filing file {0}.
Category:: Requests/Responses
Cause:: An error occurred while filing a job.
Action:: Review the server logs for further information.

TCM-00158: Failed to cancel job.
Category:: Requests/Responses
Cause:: Failed to cancel a job.
Action:: Review the server logs for further information.

TCM-00159: Cannot determine what Input Source to use for job and cannot abort or cancel job.
Category:: Requests/Responses
Cause:
Action:

TCM-00160: Input Filing MDB failed to log out.
Category:: Requests/Responses
Cause:
Action:

TCM-00161: Failed to resume filing for data source {0} and batch {1}.
Category:: Requests/Responses
Cause:
Action:

TCM-00162: Failed to load Batch for new filing.
Category:: Requests/Responses
Cause:
Action:

TCM-00163: An error occurred while completing a batch.
Category:: Requests/Responses
Cause:
Action:

TCM-00164: Input Agent cannot find WLS Runtime MBean server.
Category:: Requests/Responses
Cause:
Action:

TCM-00165: The Input {0} is currently marked offline, so the request to process data source {1} is being rolled back
Category:: Requests/Responses
Cause:
Action:

TCM-00166: Resubmitting job for input source {0} due to error: {1}
Category:: Requests/Responses
Cause:
Action:

TCM-00170: Constructed Ticket Agent MDB.
Category:: Requests/Responses
Cause:
Action:

TCM-00171: Destroyed Ticket Agent MDB.
Category:: Requests/Responses
Cause:
Action:

TCM-00172: Beginning Ticket Agent servlet initialization.
Category:: Requests/Responses
Cause:
Action:

TCM-00173: Ticket Agent servlet initialization is complete.
Category:: Requests/Responses
Cause:
Action:

TCM-00174: An error occurred while restarting the Ticket Agent MDB.
Category:: Requests/Responses
Cause:: An error occurred while restarting the Ticket Agent MDB.
Action:: Review the server logs for further information.

TCM-00175: Ticket Agent timer service is not initialized. Cannot continue.
Category:: Requests/Responses
Cause:: Ticket Agent timer service is not initialized.
Action:: Check the Application Server configuration and restart the service

TCM-00176: An error occurred while initializing Ticket Agent MDB.
Category:: Requests/Responses
Cause:: An error occurred while initializing Ticket Agent MDB.
Action:: Review the server logs for further information.

TCM-00177: Beginning Ticket Agent initialization.
Category:: Requests/Responses
Cause:
Action:

TCM-00178: Ticket Agent initialization is complete.
Category:: Requests/Responses
Cause:
Action:

TCM-00179: Encountered an error while attempting to clean up expired tickets from the imaging system
Category:: Requests/Responses
Cause:
Action:

TCM-00196: Encountered an error while logging out of the imaging system
Category:: Requests/Responses
Cause:
Action:

TCM-00197: Beginning initialization of the Rendering Cache
Category:: Requests/Responses
Cause:
Action:

TCM-00198: Initialization of the Rendering Cache is complete
Category:: Requests/Responses
Cause:
Action:

TCM-00199: WebCenter Content: Imaging API error encountered, attempting restart.
Category:: Requests/Responses
Cause:: A WebCenter Content: Imaging API error was encountered.
Action:: Review the server logs for further information.

TCM-00777: A database error occurred.
Category:: Data
Cause:: An operation caused an unexpected database error.
Action:: Review the logs for the specifics of the database error. You may need to contact Oracle Support Services to resolve the issue.

TCM-00787: A repository error occurred.
Category:: Requests/Responses
Cause:: An unknown error has occurred with a repository.
Action:: Review the logs to determine the cause of the error. You may need to contact Oracle Support Services to resolve the issue.

TCM-00788: The following error is reported by the repository: {0}
Category:: Requests/Responses
Cause:: An error has occurred with a repository. The details of the error were part of the error message.
Action:: Review the message and logs to determine the cause of the error. You may need to contact Oracle Support Services to resolve the issue.

TCM-00789: The Content Server returned no data. This may be an indication of an incorrect server port number, or a connection failure during a request.
Category:: Configuration
Cause:: The Content Server repository returned no data, and it did so without an error. The Content Server was shut down in the middle of a request
Action:: Check the server port used for the connection and make sure it is a correct value. A common mistake is to provide the web server port. The value should match the Content Server IntradocServerPort setting. Check to make sure the Content Server is still up and running.

TCM-00791: The Content Server does not have a defined document profile field.
Category:: Configuration
Cause:: The Content Server repository did not have a defined profile trigger.
Action:: Configure a profile trigger in the Content Server. This can be accomplished by setting EnableIdcProfileField=1 and then restarting the Content Server.

TCM-00792: Your search has timed out. Timeouts are typically a result of searching with value(s) that can be matched by too many documents. Please try refining your search value(s) to narrow the number of documents that will be returned.
Category:: Requests/Responses
Cause:: A timeout error has occurred with a repository.
Action:: The specified query required too much time to complete and timed out while awaiting a response from the database.

TCM-00888: Validation Error.
Category:: Requests/Responses
Cause:: Data supplied to an imaging operation was invalid.
Action:: Correct the invalid data and resend.

TCM-00998: Multiple errors in a subsystem. {0}
Category:: Requests/Responses
Cause:: An error occurred in UOA that has multiple causes.
Action:: Review the logs for the errors. You may need to contact Oracle Support Services to resolve the issue.

TCM-00999: Error in a subsystem. {0}
Category:: Requests/Responses
Cause:: An error occurred in a repository, or when communicating with a workflow server.
Action:: Review the logs for the error. You may need to contact Oracle Support Services to resolve the issue.

TCM-01008: Unable to add application. The application category already exists.
Category:: Requests/Responses
Cause:: A UOA category of the same name already exists.
Action:: Contact Oracle Support Services.

TCM-01009: Unable to add application. The system document category does not exist.
Category:: Requests/Responses
Cause:: A UOA system document category has not been properly configured.
Action:: Ensure that the UOA repository has been initialized prior to creating applications.

TCM-01010: Unable to add application. The application documents folder already exists
Category:: Requests/Responses
Cause:: A UOA folder used for storage of application documents already exists.
Action:: Contact Oracle Support Services.

TCM-01017: Unable to update application. User does not have proper permissions.
Category:: Requests/Responses
Cause:: The current user has not been given the proper rights to update the application.
Action:: Refrain from modifying the application until the proper rights have been granted.

TCM-01018: Unable to delete application. The application contains documents.
Category:: Requests/Responses
Cause:: A user attempted to delete an application that still contains documents.
Action:: Delete all of the documents belonging to the application before attempting to delete the application.

TCM-01019: Another application operation is in progress. Try again later.
Category:: Requests/Responses
Cause:: A user attempted an application operation while another operation was in progress.
Action:: Wait 30 to 60 seconds and try again.

TCM-01020: This document operation is blocked by repository database inconsistencies. This may be due to concurrent application activity (for example, adding, modifying, or deleting an application). Try again later.
Category:: Requests/Responses
Cause:: A user attempted a document operation while the repository metadata table is in an inconsistent state. This could be due to a concurrent application operation.
Action:: Wait 30 to 60 seconds and try again.

TCM-01021: Failed to delete application in the repository. Contact an administrator for assistance.
Category:: Requests/Responses
Cause:: The system was not able to delete the application in the repository.
Action:: Review the logs for possible reasons.

TCM-01025: The NameId for the application does not contain a name or an identifier.
Category:: Requests/Responses
Cause:: The NameId for the application did not contain a name or an identifier.
Action:: Provide either a name or an identifier for the application.

TCM-01027: Lifecycle policy action specification, {0}, is not found.
Category:: Configuration
Cause:: The specified lifecycle policy action specification was not found in the UOA system.
Action:: Ensure that UOA is configured with the specified lifecycle policy action specification.

TCM-01028: Lifecycle policy date rule specification, {0}, is not found.
Category:: Configuration
Cause:: The specified lifecycle policy date rule specification was not found in the UOA system.
Action:: Ensure that UOA is configured with the specified lifecycle policy date rule specification.

TCM-01031: Missing a closing delimiter near "{0}".
Category:: Programmatic
Cause:: An opening delimiter ([) was found without a closing delimiter (]) in a Format Value function.
Action:: Review the Format Value text and ensure that there are matching delimiters.

TCM-01032: The workflow mapping function, {0}, is not a known function.
Category:: Programmatic
Cause:: A workflow Format Value contains a reference to an unknown function.
Action:: Review the API documentation for valid workflow function names.

TCM-01033: The workflow mapping function, {0}, is not allowed.
Category:: Programmatic
Cause:: A workflow function was specified in a location where it is not allowed.
Action:: Review the API documentation for valid workflow function usage.

TCM-01034: The workflow mapping function, {0}, has too many parameters.
Category:: Programmatic
Cause:: Too many parameters were provided for a workflow function.
Action:: Review the API documentation for valid workflow function usage.

TCM-01035: The workflow mapping function, {0}, requires a parameter.
Category:: Programmatic
Cause:: A workflow function was missing a required parameter.
Action:: Review the API documentation for valid workflow function usage.

TCM-01036: The workflow mapping function, {0}, does not accept a parameter.
Category:: Programmatic
Cause:: A parameter was provided to a workflow function that does not accept parameters.
Action:: Review the API documentation for valid workflow function usage.

TCM-01037: Null applications are not allowed.
Category:: Requests/Responses
Cause:: A null value was provided to a function that requires an application definition.
Action:: Provide a valid, non-null, application definition.

TCM-01039: The document is not allowed to be updated. It is read-only.
Category:: Requests/Responses
Cause:: The current user was not given the proper rights to update documents belonging to the application.
Action:: Refrain from modifying the application's documents until the proper rights have been granted.

TCM-02001: The requested document, id={0}, was not found.
Category:: Requests/Responses
Cause:: Document does not exist, or user does not have proper rights.
Action:: Verify document and user rights before attempting to access the document.

TCM-02003: The requested id, {0}, is not a document.
Category:: Requests/Responses
Cause:: Item returned by UOA is not a document.
Action:: Retry action against document.

TCM-02004: The document is currently locked by {0}
Category:: Requests/Responses
Cause:: Document is already locked.
Action:: Unlock document and try again.

TCM-02005: The document cannot be locked
Category:: Requests/Responses
Cause:: Document could not be locked to the user.
Action:: Verify user permissions and try again.

TCM-02006: The document is locked to another user: {0}
Category:: Requests/Responses
Cause:: Document is locked to another user.
Action:: Administrator or current document owner must unlock document.

TCM-02007: The document cannot be unlocked
Category:: Requests/Responses
Cause:: Document could not be unlocked by the user.
Action:: Verify the document state and try to unlock document again.

TCM-02008: The documents cannot be deleted because they are in a legislative hold in the repository.
Category:: Requests/Responses
Cause:: An attempt was made to delete documents that are in legislative hold.
Action:: Refrain from deleting documents until legislative holds have been removed.

TCM-02011: The document is not locked to the requester
Category:: Requests/Responses
Cause:: Document is not locked to the user.
Action:: Document must be unlocked before trying again.

TCM-02012: An invalid file was received "{0}".
Category:: Requests/Responses
Cause:: Invalid file was given to the API.
Action:: Verify the file and try again.

TCM-02014: Original document field values cannot be retrieved.
Category:: Requests/Responses
Cause:: Document fields could not be retrieved from UOA.
Action:: Verify user permissions and try again.

TCM-02015: Invalid field value for field "{0}".
Category:: Requests/Responses
Cause:: Could not resolve field for field value.
Action:: Verify application definition and try again.

TCM-02016: The file name is invalid. A file name must have a file extension, cannot be empty or null, and cannot include any path information.
Category:: Requests/Responses
Cause:: An invalid file name was provided for the document.
Action:: Enter a valid file name. Do not include any path information.

TCM-02019: Replacement or versioning is not allowed for this document.
Category:: Requests/Responses
Cause:: Document cannot be updated.
Action:: Document update is not allowed for documents in this application.

TCM-02020: Page Management functions are valid only with TIFF document types.
Category:: Requests/Responses
Cause:: Cannot modify because it is not a tiff document.
Action:: Page management functions are only valid for tiff documents.

TCM-02021: A page management operation cannot complete because of a system error.
Category:: Requests/Responses
Cause:: Page operation failed. System error occurred accessing image.
Action:: Verify and try again.

TCM-02022: The supporting content key is invalid.
Category:: Requests/Responses
Cause:: Supporting content key for the document is invalid.
Action:: Enter unique supporting content key.

TCM-02023: Cannot find the field {0}, id {1} in the application context.
Category:: Requests/Responses
Cause:: Document missing field information. Cannot create document.
Action:: Enter correct field information.

TCM-02024: Invalid upload token.
Category:: Requests/Responses
Cause:: Token for the uploaded file is invalid.
Action:: Use valid token.

TCM-02025: Cannot move document. Source and destination application are the same.
Category:: Requests/Responses
Cause:: Source and destination applications are the same.
Action:: Specify different application when moving documents.

TCM-02026: The document data provided to the service is invalid
Category:: Requests/Responses
Cause:: Invalid data stream was given to the API
Action:: Check the file and make sure it is valid

TCM-02027: The requested supporting content for the document, id={0}, key={1}, was not found.
Category:: Requests/Responses
Cause:: Supporting content key does not return any results.
Action:: Verify supporting content key is correct.

TCM-02028: This document consists of multiple versions. The destination application does not support versioning.
Category:: Requests/Responses
Cause:: Document consists of multiple versions. Destination application does not support versioning.
Action:: Choose a destination application that supports versioning.

TCM-02029: Write permissions are required on the document in order to set supporting content.
Category:: Requests/Responses
Cause:: Write permissions are required on the document in order to set supporting content.
Action:: Verify user permissions are set correctly for the document

TCM-02030: View permissions are required on the document in order to get supporting content.
Category:: Requests/Responses
Cause:: View permissions are required on the document in order to get supporting content.
Action:: Verify user permissions are set correctly for the document

TCM-02031: Copy failed, document not found.
Category:: Requests/Responses
Cause:: Document does not exist or user does not have rights to copy.
Action:: Verify document and user rights before attempting to copy.

TCM-02032: Moved failed, no document move rights
Category:: Requests/Responses
Cause:: Document does not exist or user does not have rights to move.
Action:: Verify document and user rights before attempting to move.

TCM-02033: Update failed, no document update rights
Category:: Requests/Responses
Cause:: Document does not exist or user does not have rights to update
Action:: Verify document and user rights before attempting to update.

TCM-02034: The document version must be greater than 0.
Category:: Requests/Responses
Cause:: Document version must be greater than 0
Action:: Set version to a value greater than 0

TCM-02035: File, "{0}," is zero length. Documents must have a file length greater than zero.
Category:: Requests/Responses
Cause:: File with zero length was given to the API.
Action:: Check the file and make sure its length is greater than zero.

TCM-02036: Either a valid file, a valid field list, or both, are required to update a document.
Category:: Requests/Responses
Cause:: Invalid file and field list has been passed into update document.
Action:: Verify valid file and field list have been passed in.

TCM-02037: The supporting content key already exists.
Category:: Requests/Responses
Cause:: Supporting content key for the document already exists.
Action:: Enter unique supporting content key.

TCM-02038: The document identifier, {0}, is invalid.
Category:: Requests/Responses
Cause:: The document identifier for the request was invalid.
Action:: Enter a valid document identifier.

TCM-02039: The document action could not be performed because the document is under records management in the repository.
Category:: Requests/Responses
Cause:: A user attempted a document operation while the document is under records management in the repository.
Action:: Refrain from operating or a records managed document.

TCM-02040: The file timeout {0} is invalid for document operations. The timeout must be greater than or equal to 0.
Category:: Requests/Responses
Cause:: The timeout for document operations must be greater than or equal to 0. The current value is invalid
Action:: Set timeout value to greater than or equal to 0.

TCM-03004: Annotation list is Null
Category:: Requests/Responses
Cause:: Annotation list to search is Null.
Action:: Ensure that annotation list object is not null.

TCM-03012: An error occurred while saving annotations
Category:: Requests/Responses
Cause:: An error occurred while saving annotations.
Action:: A repository-specific exception occurred when saving annotations. Check the repository-specific exception stack for diagnostic details.

TCM-03018: Error reading file {0}
Category:: Requests/Responses
Cause:: An error occurred while reading the file
Action:: Check the file and its permissions

TCM-03024: An annotation cannot be accepted due to the lack of permission.
Category:: Requests/Responses
Cause:: An annotation cannot be accepted due to the lack of permission.
Action:: Ensure that all annotations' security settings are compatible with the user's permission set.

TCM-03029: Invalid document Id saving/retrieving document annotations: {0}
Category:: Requests/Responses
Cause:: Invalid document Id when saving/retrieving document annotations.
Action:: Supply a valid document Id.

TCM-03035: User does not have sufficient annotation permission in the destination application.
Category:: Requests/Responses
Cause:: User does not have sufficient annotation permission in the destination application.
Action:: Ensure that the user has sufficient annotation permissions in the destination application for any annotations to be applied.

TCM-03036: An error occurred retrieving annotations for the document.
Category:: Requests/Responses
Cause:: Annotations for the specified document could not be retrieved.
Action:: A repository-specific exception occurred when saving annotations. Check the repository-specific exception stack for diagnostic details.

TCM-03037: Error saving annotations to a document version that is not the current version.
Category:: Requests/Responses
Cause:: An attempt was made to save annotations to a document version that is not the current version.
Action:: Annotations cannot be saved to previous versions of a document.

TCM-04001: A valid Input name or ID must be specified for the operation to complete.
Category:: Requests/Responses
Cause:: The requested Name and ID of the input to be deleted is invalid.
Action:: Provide a valid Name or ID for the Input to delete

TCM-04002: No Input definitions found for the input name {0}, ID {1}.
Category:: Requests/Responses
Cause:: The specified Input could not be found in the system.
Action:: Recheck the Input name or ID.

TCM-04003: Multiple Input definitions found for input name {0}, ID {1}.
Category:: Requests/Responses
Cause:: The name or ID provided has multiple Input Definitions associated with it.
Action:: Examine the system for data integrity.

TCM-04004: Input name is empty
Category:: Requests/Responses
Cause:: The name of the Input is invalid
Action:: Make sure the Input name is not missing, blank or only strings

TCM-04005: Invalid Input properties
Category:: Requests/Responses
Cause:: The properties section of the Input Definition was invalid.
Action:: Make sure that the Input properties section is not missing.

TCM-04006: Input source must be set
Category:: Requests/Responses
Cause:: The Input Definition is missing the input source
Action:: Provide a valid input source

TCM-04008: The Input's Source Properties section is invalid
Category:: Requests/Responses
Cause:: The Input Source Properties section of the Input definition is invalid.
Action:: Check to make sure the properties are set and have valid values.

TCM-04009: The specified data source is invalid.
Category:: Requests/Responses
Cause:: The Data Source in the Input Source Properties was invalid.
Action:: Make sure that the data source is specified and has a valid value.

TCM-04010: The Input Source in the definition is invalid
Category:: Requests/Responses
Cause:: The Input Source is invalid.
Action:: Check the Input Source and make sure it's valid.

TCM-04012: The Input does not define any mappings, or one or more mappings are invalid
Category:: Requests/Responses
Cause:: The Input Mappings section of the Input definition is invalid.
Action:: Check to make sure mappings have been set and map between valid fields.

TCM-04013: The provided StateUpdates are invalid.
Category:: Requests/Responses
Cause:: No valid values were provided for updating the input's state.
Action:: Ensure that the Input.StateFlags provided for all updates are valid.

TCM-04014: The specified input's state cannot be updated
Category:: Requests/Responses
Cause:: Updating the current state for the specified input failed.
Action:: Ensure that the specified input exists, and that the new state settings are valid.

TCM-04015: The specified input definition cannot be updated
Category:: Requests/Responses
Cause:: Updating the provided sections of the input definition failed.
Action:: Ensure values have been properly provided for all of the definition sections you are attempting to update

TCM-04016: The provided Input object is null
Category:: Requests/Responses
Cause:: The Input object provided is null.
Action:: Provide a valid Input, with appropriate sections completed.

TCM-04017: Cannot find the configuration file for the local Input Server settings.
Category:: Requests/Responses
Cause:: The configuration file specified could not be found.
Action:: Ensure that the specified file exists, and that the user has the correct permissions

TCM-04018: An error was encountered loading the configuration file
Category:: Requests/Responses
Cause:: The configuration file couldn't be opened.
Action:: Ensure that the specified file exists, and that the user has the correct permissions

TCM-04019: Failed to get the Input Source list
Category:: Requests/Responses
Cause:: Could not get a listing of available Input Sources
Action:: Check the jar configuration files and make sure they are defined correctly

TCM-04020: The Input Path for CSV filings has not been configured properly.
Category:: Requests/Responses
Cause:: The Input Path is missing from the CSV configuration file.
Action:: Check the CSV configuration file to make sure it exists and is correct.

TCM-04021: Input Source {0} cannot be found
Category:: Requests/Responses
Cause:: The requested Input Source was not found
Action:: Check the /META-INF/input-agent-config.properties file of Input Source jar and make sure it's correct.

TCM-04022: Error loading Input Source Plugin
Category:: Requests/Responses
Cause:: An error occurred while trying to load the input source
Action:: Check the class path to make sure the input source can be loaded.

TCM-04023: The stage path cannot be initialized for processing
Category:: Requests/Responses
Cause:: The stage directory could not be initialized.
Action:: Check the permissions to the Input Directory.

TCM-04024: The file {0} cannot be moved to the directory {1}
Category:: Requests/Responses
Cause:: The input file could not be properly staged for processing.
Action:: Check the input file and stage path for proper permissions.

TCM-04025: the configuration folder path cannot be found
Category:: Requests/Responses
Cause:: The configuration file wasn't found
Action:: Make sure all the configuration files are in place and are correct.

TCM-04027: One or more of the Input Fields are mapped to multiple Application or system fields
Category:: Requests/Responses
Cause:: One of the input mappings is assigned to multiple locations.
Action:: Remove all duplicate mappings from the definition

TCM-04028: The requested input field isn't mapped to an application field
Category:: Requests/Responses
Cause:: The requested mapping wasn't found in the index
Action:: Pass in the correct input field name

TCM-04029: The parser has not been initialized, call StartFiling
Category:: Requests/Responses
Cause:: Start Filing wasn't called on the parser
Action:: Call start filing

TCM-04030: The input file cannot be properly closed
Category:: Requests/Responses
Cause:: A file error closing the input file
Action:: Check file permissions and input file

TCM-04032: The specified data range is invalid
Category:: Requests/Responses
Cause:: Start and end positions for examining the data source are invalid
Action:: Request a valid range

TCM-04033: Date value does not conform to the short, medium or long format type for the current locale, date cannot be parsed.
Category:: Requests/Responses
Cause:: Date format does not parse to a valid date
Action:: Pass in a date value that conforms to the locales short, medium or long format

TCM-04034: Cannot get the local machine name
Category:: Requests/Responses
Cause:: The host could not be determined.
Action:: Check the error code.

TCM-04035: Application {0}({1}) cannot be found. Verify that the application exists and you have permissions to it.
Category:: Requests/Responses
Cause:: The application that the mapping is pointing to could not be found
Action:: Check to make sure that you have access to that Application or that the Application is still valid.

TCM-04036: The mapping for input section {0} is invalid
Category:: Requests/Responses
Cause:: The application field specified in the Input mapping is invalid.
Action:: Check to make sure that the specified application field ID is set and exists in the target application

TCM-04038: Application "{0}" cannot be loaded. Verify that the application exists and you have permissions to it.
Category:: Requests/Responses
Cause:: The Application specified could not be loaded
Action:: Check to make sure that the Application exists and you have access to it.

TCM-04039: The Sample Path for CSV filings has not been configured correctly.
Category:: Requests/Responses
Cause:: The sample path is not configured correctly
Action:: Make sure the sample path configuration value is set to a valid location

TCM-04040: The sample path {0} cannot be initialized for processing
Category:: Requests/Responses
Cause:: The sample path could not be created
Action:: Make sure the sample path is valid, accessible by the server and has the correct permissions

TCM-04041: The get contents request for data source {0} cannot be processed because it is not a sample source.
Category:: Requests/Responses
Cause:: User attempted to get sample data for a data source that wasn't a sample source.
Action:: Use only sample sources when requesting source contents.

TCM-04045: The Input {0} has {1} unfinished batches open against it and cannot be deleted
Category:: Requests/Responses
Cause:: There is an open batch against the Input
Action:: Wait for the filing to finish before deleting the Input

TCM-04046: Input {0} has active or pending jobs and cannot be deleted
Category:: Requests/Responses
Cause:: There are queued jobs for the Input
Action:: Wait for all the work to finish before deleting the Input

TCM-04047: The Input Agent service cannot be accessed to process commands.
Category:: Requests/Responses
Cause:: The Input Agent could not be found to communicate with.
Action:: Validate that the Imaging.ear is started and running properly.

TCM-04048: Content cannot be read from the data source {0}
Category:: Requests/Responses
Cause:: The data source content could not be read
Action:: Examine the inner exception for more information

TCM-04049: The StateUpdate value passed to the ModifyState call is invalid
Category:: Requests/Responses
Cause:: The state update object passed to the API request is invalid
Action:: Check the StateUpdate object to make sure it's properly formed

TCM-04050: No Application is specified in the Input Mapping section
Category:: Requests/Responses
Cause:: The input definition does not have the destination application id set
Action:: Set the Application Id in the Input mapping section

TCM-04051: The input file locale has already been set and cannot be changed
Category:: Requests/Responses
Cause:: A locale has already been specified for the input file and cannot be changed
Action:: Remove the extra locale command from the input file

TCM-04052: The locale identifier {0} is not a valid locale identifier
Category:: Requests/Responses
Cause:: The locale parameter specified in the locale command is invalid
Action:: Specify a valid locale

TCM-04053: The locale command can only be used at the beginning of the input file
Category:: Requests/Responses
Cause:: The locale command was used after the start of the file
Action:: Only use the locale command at the top of the input file

TCM-04054: The start position {0} or range {1} specified are invalid. Make sure that the start position and range values are positive and that the range is greater than the start.
Category:: Requests/Responses
Cause:: The start position or range values are invalid.
Action:: Examine the calling code and ensure that the start position and range are greater than 0 and that the range is greater than the start position

TCM-04055: The value {0} provided for the Input Server state update is the wrong type or is out of range.
Category:: Requests/Responses
Cause:: The value provided to the StateFlag request was invalid.
Action:: Check to make sure the correct type has been passed for the StateFlag and that the value is in the correct range.

TCM-05003: The UOA Repository search failed
Category:: Requests/Responses
Cause:: No Search was found matching the selected search id
Action:: Re-list the available searches

TCM-05004: The Search Definition supplied was null
Category:: Requests/Responses
Cause:: A null value was provided for the search.
Action:: Provide a non-null search.

TCM-05005: The Search Name supplied was null or empty
Category:: Requests/Responses
Cause:: Search name was null or empty
Action:: Provide a valid search name.

TCM-05006: The search supplied has a results formatting structure that is null.
Category:: Requests/Responses
Cause:: The search formatting structure was null or empty.
Action:: Provide a valid search formatting structure.

TCM-05007: The requested search, {0}, was not found.
Category:: Requests/Responses
Cause:: The search requested does not exist. The user does not have access to the search.
Action:: Check the requested search name or ID for correctness. Check the user's access to the requested search.

TCM-05009: A required search parameter, {0}, was missing.
Category:: Requests/Responses
Cause:: A required parameter was missing for this search
Action:: Resubmit the search with the required parameter(s).

TCM-05012: Invalid operator used in search parameter
Category:: Requests/Responses
Cause:: An invalid operator was used in the search parameter
Action:: Use an operator defined in the operator picklist.

TCM-05013: A Search Argument was provided that was not defined in the search
Category:: Requests/Responses
Cause:: A search argument was provided that was not defined in the search
Action:: Provide only those arguments defined in the search.

TCM-05014: The search argument contains a value for a read-only parameter
Category:: Requests/Responses
Cause:: A search argument was provided containing a value for a read-only parameter
Action:: Remove the read only parameter from the search arguments.

TCM-05015: There are multiple search arguments for a single parameter.
Category:: Requests/Responses
Cause:: Multiple search arguments were provided for a single parameter.
Action:: Verify that the number of the search arguments matches the number of parameters.

TCM-05016: The type for the search argument does not match the search parameter type.
Category:: Requests/Responses
Cause:: A search argument with an incorrect type was provided for a search parameter.
Action:: Use an argument with a type that matches the search parameter type.

TCM-05017: The entered value, {0}, is < 1. The default maximum rows returned value must be >= 1.
Category:: Requests/Responses
Cause:: A value less than 1 was entered for the defalut value for the maximum number of rows to be returned from a search.
Action:: Use a value that is greater than or equal to 1.

TCM-05018: The entered value, {0}, is invalid for panel placement. Enter 1, 2, or 3.
Category:: Requests/Responses
Cause:: An invalid value is entered for placement of a panel.
Action:: Enter 1, 2, or 3

TCM-05019: Entered value, {0}, for zoom level in not valid, is < 1. Pick values from 1,2,3,20,50,100,150,200.
Category:: Requests/Responses
Cause:: An invalid value is entered for zoom level.
Action:: Pick values from 1,2,3,20,50,100,150,200.

TCM-06001: Unable to retrieve Role: {0}
Category:: Requests/Responses
Cause:: The role specified was not found.
Action:: Add the role to the security provider or use a defined role.

TCM-06002: Access is denied.
Category:: Requests/Responses
Cause:: User does not have access to the requested information.
Action:: Update the user's permissions.

TCM-06004: Unable to locate the security member specified.
Category:: Requests/Responses
Cause:: The security member does not exist.
Action:: Add the security member to the security provider.

TCM-06009: Unable to locate the system group: {0}
Category:: Requests/Responses
Cause:: The specific system group was not found.
Action:: Add the system group using the security provider.

TCM-06010: Agent users are only allowed to log in through the agent services.
Category:: Requests/Responses
Cause:: An agent user was used to attempt a log in.
Action:: Log in using a different user.

TCM-06011: Users assigned the 'admin' group either directly or indirectly are not allowed to log into WebCenter Content: Imaging.
Category:: Requests/Responses
Cause:: Users assigned the 'admin' group are not allowed to log in because the repository attaches special meaning to this group.
Action:: Log in using a different user or remove the 'admin' group association with this user.

TCM-06012: The User {0} does not exist in the policy store.
Category:: Requests/Responses
Cause:: The security provider was unable to locate the user specified.
Action:: Enter the user into the security provider.

TCM-06013: Unable to locate the default policy store.
Category:: Requests/Responses
Cause:: Unable to load the policy store.
Action:: The default policy store has not been configured correctly.

TCM-06014: The user's principal does not contain a subject.
Category:: Requests/Responses
Cause:: The principal object was not found in the user token.
Action:: Make sure the principal exists within the user token.

TCM-06015: The Group {0} does not exist in the policy store.
Category:: Requests/Responses
Cause:: The authentication provider was unable to locate the group specified.
Action:: Enter the group into the authentication provider.

TCM-06016: Access to modify the security of this definition is denied.
Category:: Requests/Responses
Cause:: The user was unable to modify the security of this definition.
Action:: Update the user permissions with the modify permission.

TCM-06017: Access to modify the document security of this definition is denied.
Category:: Requests/Responses
Cause:: The user was unable to modify the document security of this definition.
Action:: Update the user permissions to include the modify document security permission.

TCM-06018: Unable to create resource in policy store for: {0}
Category:: Requests/Responses
Cause:: Unable to create resource in policy store for: {0}
Action:: The default policy store has not been configured correctly.

TCM-06019: Bad principal type returned by Policy Store for "{0}": {1}
Category:: Requests/Responses
Cause:: Bad principal type returned by Policy Store for "{0}": {1}
Action:: The default policy store has not been configured correctly.

TCM-06020: No Security Profile was found during system startup.
Category:: Requests/Responses
Cause:: No Security Profile was found during system startup.
Action:: The system has not been configured correctly to use a security profile.

TCM-06021: The Security Profile failed to initialize during system startup: {0}
Category:: Requests/Responses
Cause:: The Security Profile failed to initialize during system startup: {0}
Action:: The system has not been configured correctly to use the security profile.

TCM-07001: Requested output format does not support multiple pages
Category:: Requests/Responses
Cause:: An output format was requested that does not support multiple pages.
Action:: Choose a different output format, or restrict the output request to a single page.

TCM-07002: Invalid Document reference in render request
Category:: Requests/Responses
Cause:: The supplied documentObject parameter is null
Action:: Provide a valid Document object reference when calling RenderManager.render().

TCM-07003: Invalid input stream in render request
Category:: Requests/Responses
Cause:: The supplied sourceStream parameter is null
Action:: Provide a valid InputStream object reference when calling RenderManager.render().

TCM-07004: No render options in render request
Category:: Requests/Responses
Cause:: The supplied options parameter is null
Action:: Provide a valid RenderOptions object reference when calling RenderManager.render().

TCM-07008: This document contains annotations that prevent the user from accessing this document in its raw format
Category:: Requests/Responses
Cause:: This document contains annotations that prevent the user from accessing this document in its raw format.
Action:: Export to TIFF with the annotations burned in or contact your administrator for access to the native format.

TCM-07009: The mime-type of "{0}" is not supported.
Category:: Requests/Responses
Cause:: An unsupported mime-type was requested.
Action:: Correct the document content (mime) type.

TCM-07011: An I/O error occurred during image translation.
Category:: Requests/Responses
Cause:: An I/O error occurred during image translation.
Action:: Check permissions and free space in the server temp directory.

TCM-07012: An error occurred when loading an image for translation.
Category:: Requests/Responses
Cause:: An error occurred when loading an image for translation.
Action:: Image handling components failed to load the image. Check nested exception details for diagnostic information.

TCM-07013: There was an error reading TIFF headers. The file may be corrupt.
Category:: Requests/Responses
Cause:: There was an error reading TIFF headers. The file may be corrupt.
Action:: Check permissions and free space in the server temp directory.

TCM-07014: An error occurred when processing image manipulation commands during save.
Category:: Requests/Responses
Cause:: An error occurred when processing image manipulation commands during save.
Action:: Image handling components failed to load the image. Check nested exception details for diagnostic information.

TCM-07016: An I/O error occurred creating the output for this request.
Category:: Requests/Responses
Cause:: An I/O error occurred creating the output for this request.
Action:: Check for nested exceptions, permissions and free space in the server temp directory.

TCM-07017: No document specified when burning annotations into image
Category:: Requests/Responses
Cause:: No document specified when burning annotations into image.
Action:: Specify a valid document path to the document source.

TCM-07019: The requested scale is not within the allowed value range; {0}-{1}
Category:: Requests/Responses
Cause:: The requested scale is not within the allowed value range.
Action:: Provide a scale factor value within the supported range.

TCM-07020: The requested fit rectangle is empty
Category:: Requests/Responses
Cause:: The requested fit rectangle cannot be empty.
Action:: Provide a non-null, non-empty rectangle.

TCM-07021: Unable to get annotation permissions from document
Category:: Requests/Responses
Cause:: Annotation permissions could not be determined.
Action:: Contact the system administrator.

TCM-07022: The supplied document object is null
Category:: Requests/Responses
Cause:: The cache was given a null document object.
Action:: Contact the system administrator.

TCM-07023: A cache exception occurred. {0}
Category:: Requests/Responses
Cause:: A RenderPageCache exception occurred: {0}
Action:: Check the cache exception code and nested exception details for diagnostic information.

TCM-07024: A RenderPageCache object was not found
Category:: Requests/Responses
Cause:: An error occurred retrieving an object from the cache.
Action:: Check the directory and nested exception details for diagnostic information.

TCM-07025: Page number must be a positive value.
Category:: Requests/Responses
Cause:: Page number must be a positive value.
Action:: Provide page number values greater than zero.

TCM-07026: Bounding rectangle specified is empty.
Category:: Requests/Responses
Cause:: Bounding rectangle specified is empty.
Action:: Provide a non-empty rectangle definition.

TCM-07027: The supplied outputType parameter is null.
Category:: Requests/Responses
Cause:: The supplied outputType parameter is null.
Action:: Provide a value for the outputType parameter.

TCM-07028: An invalid argument was provided to method {0}({1}).
Category:: Requests/Responses
Cause:: An invalid argument was provided to a method call.
Action:: Provide non-null values. Page specifications must be > 0.

TCM-07029: Cannot burn the annotations into the destination file {0}.
Category:: Requests/Responses
Cause:: An error occurred while burning annotations into the destination tiff.
Action:: Check the embedded exception for the specific cause of the error.

TCM-07030: An invalid path was specified. Provide a non-null, non-empty string or an existing directory path.
Category:: Requests/Responses
Cause:: An invalid path was set for the render CacheLocation.
Action:: Provide an empty value or an existing directory path.

TCM-07031: An invalid value was specified. Check spelling and character case.
Category:: Requests/Responses
Cause:: An invalid value was specified.
Action:: Check spelling and character case.

TCM-07033: An invalid value was specified. Enter a value from 0 to 100.
Category:: Requests/Responses
Cause:: An invalid value was specified.
Action:: Enter a value from 0 to 100.

TCM-07036: An error occurred during document translation.
Category:: Requests/Responses
Cause:: An error occurred during document translation.
Action:: Check nested exception details for diagnostic information.

TCM-07037: An error occurred retrieving a rendition to create a copy with.
Category:: Requests/Responses
Cause:: An error occurred retrieving a rendition to create a copy with.
Action:: The rendering system was unable to generate a rendition of the document. Check the nested exception details for diagnostic information.

TCM-07038: The requested page number is beyond the document page range.
Category:: Requests/Responses
Cause:: The requested page number is beyond the document page range.
Action:: Specify a valid page number that is within the range of document pages.

TCM-07039: This document content is sealed. IRM content cannot be rendered.
Category:: Requests/Responses
Cause:: This document content is sealed. IRM content cannot be rendered.
Action:: Download the native document and use Oracle IRM Desktop to access this file content.

TCM-07040: RenderAgent is not initialized. Requests cannot be processed.
Category:: Requests/Responses
Cause:: RenderAgent is not initialized. Requests cannot be processed.
Action:: RenderAgentBean initialization failed. Check the nested exception details for diagnostic information.

TCM-07041: The specified viewer cache days value of {0} is invalid. The number of days must be greater than or equal to 0 and less than or equal to 30.
Category:: Requests/Responses
Cause:: The cache days value that was given is invalid.
Action:: Check the cache days parameter sent to the MBean is in the valid range of 0-30.

TCM-07042: The credential for storing the encryption key was not found. It must exist prior to enabling viewer cache encryption.
Category:: Requests/Responses
Cause:: The credential for storing the encryption key was not found.
Action:: Verify the credential exists prior to turning on cache encryption.

TCM-07043: An error occurred while queuing the cache request. The Oracle WebCenter Content: Imaging Viewer Cache application (imaging-vc) was not found.
Category:: Requests/Responses
Cause:: The viewer cache application deployment was not found.
Action:: Check the domain configuration an verify that the viewer cache application is properly deployed.

TCM-08001: System folder "{0}" is not found
Category:: Installation
Cause:: A UOA system folder was not found.
Action:: Ensure proper UOA system installation.

TCM-08005: User does not have create permissions.
Category:: Requests/Responses
Cause:: An attempt was made to create documents in an application where the user does not have create permission.
Action:: Ensure user is granted create permission or refrains from creating documents.

TCM-08006: User does not have delete permissions.
Category:: Requests/Responses
Cause:: An attempt was made to delete documents in an application where the user does not have delete permission.
Action:: Ensure user is granted delete permission or refrains from deleting documents.

TCM-08008: User does not have permission to access the "{0}" system folder.
Category:: Requests/Responses
Cause:: An attempt was made to access a system folder, but the user does not have the proper permission.
Action:: Ensure user is granted the proper permission or refrains from accessing the folder

TCM-08009: Workspace "{0}" is not found.
Category:: Installation
Cause:: A workspace in UOA was not found.
Action:: Ensure proper UOA system installation.

TCM-08010: Interrupted during login retry. Stopping further login attempts.
Category:: Requests/Responses
Cause:: An agent thread was interrupted while attempting to log in.
Action:: Check to see if the thread was shut down.

TCM-08011: Unable to log in to the WebCenter Content: Imaging system
Category:: Requests/Responses
Cause:: An error was encountered while logging in to the imaging system.
Action:: Check the imaging logs and any inner exception for details on why the login failed.

TCM-09010: An error occurred trying to list storage policy volumes.
Category:: Requests/Responses
Cause:: An error occurred trying to obtain a list of storage volumes from a repository.
Action:: Ensure that the repository is running and functioning correctly.

TCM-09011: An error occurred trying to determine the default storage policy volume.
Category:: Requests/Responses
Cause:: An error occurred trying to determine the default volume for a repository.
Action:: Ensure that the repository is running and functioning correctly.

TCM-09012: An error occurred trying to list retention policies.
Category:: Requests/Responses
Cause:: An error occurred trying to list retention policies for a repository.
Action:: Ensure that the repository is running and functioning correctly.

TCM-09013: An error occurred trying to validate a volume.
Category:: Requests/Responses
Cause:: An error occurred trying to validate a volume for a repository.
Action:: Ensure that the repository is running and functioning correctly.

TCM-09014: An error occurred trying to validate a storage group.
Category:: Requests/Responses
Cause:: An error occurred trying to validate a storage group for a repository.
Action:: Ensure that the repository is running and functioning correctly.

TCM-09015: An error occurred trying to validate a retention policy.
Category:: Requests/Responses
Cause:: An error occurred trying to validate a retention policy for a repository.
Action:: Ensure that the repository is running and functioning correctly.

TCM-09016: An error occurred trying to find a retention policy.
Category:: Requests/Responses
Cause:: An error occurred trying to find a retention policy in a repository.
Action:: Ensure that the repository is running and functioning correctly.

TCM-09017: An error occurred trying to discover lifecycle policies.
Category:: Requests/Responses
Cause:: An error occurred trying to find lifecycle policies in a UOA repository.
Action:: Ensure that UOA is running and functioning correctly.

TCM-09018: An error occurred trying to create a storage policy.
Category:: Requests/Responses
Cause:: An error occurred trying to create a storage policy in a UOA repository.
Action:: Ensure that UOA is running and functioning correctly.

TCM-09019: An error occurred trying to delete a storage policy.
Category:: Requests/Responses
Cause:: An error occurred trying to delete a storage policy in a UOA repository.
Action:: Ensure that UOA is running and functioning correctly.

TCM-09020: An error occurred trying to load action specifications.
Category:: Requests/Responses
Cause:: An error occurred trying to load action specifications in a UOA repository.
Action:: Ensure that UOA is running and functioning correctly.

TCM-09021: An error occurred trying to load date rule specifications.
Category:: Requests/Responses
Cause:: An error occurred trying to load date rule specifications in a UOA repository.
Action:: Ensure that UOA is running and functioning correctly.

TCM-09030: Error connecting to workflow system.
Category:: Requests/Responses
Cause:: An error occurred trying to connect to a workflow server.
Action:: Ensure that the workflow server is running and functioning correctly.

TCM-09032: Error determining workflow composite services. The composite DN is {0}.
Category:: Requests/Responses
Cause:: An error occurred trying to determine services for a composite.
Action:: Ensure that the workflow server is running and functioning correctly.

TCM-09033: Error getting workflow system components.
Category:: Requests/Responses
Cause:: An error occurred trying to determine components for a workflow server.
Action:: Ensure that the workflow server is running and functioning correctly.

TCM-09034: Error reading workflow service WSDL document {0}
Category:: Requests/Responses
Cause:: An error occurred trying to read the workflow service WSDL document.
Action:: Ensure that the workflow server is running and functioning correctly. If WSDL protocol is HTTPS, ensure SSL configurations for both imaging and workflow server are correct.

TCM-09035: Error accessing credential key ''{0}''
Category:: Requests/Responses
Cause:: An error occurred access a credential key in the credential store.
Action:: Ensure that the correct key was provided and the credentials are properly configured in the credential store.

TCM-09036: Unsupported workflow service. Service definition exceeds hierarchical depth of {0}.
Category:: Requests/Responses
Cause:: Workflow service Definition exceeded the maximum hierarchical depth given in the error message.
Action:: Select a different workflow service operation.

TCM-09037: Unsupported workflow service. Service definition contains choice elements.
Category:: Requests/Responses
Cause:: Workflow service definition contains unsupported choice elements.
Action:: Select a different workflow service operation.

TCM-09038: Unable to map one or more values to workflow payload nodes for document {0}. The missing nodes are: {1}.
Category:: Requests/Responses
Cause:: Workflow payload may have changed after worflow was configured.
Action:: Reconfigure the workflow.

TCM-09040: Unable to obtain a Subject that is required to enable sending tenant information to a workflow server.
Category:: Requests/Responses
Cause:: No Subject was found or created.
Action:: Contact your system administrator and review the server logs for any related information.

TCM-09041: Unable to obtain an ApplSession that is required to enable sending tenant information to a workflow server.
Category:: Requests/Responses
Cause:: No ApplSession was created.
Action:: Contact your system administrator and review the server logs for any related information.

TCM-09042: Unable to find the required libraries to create an ApplSession.
Category:: Requests/Responses
Cause:: The required Appl Core libraries could not be found.
Action:: Contact your system administrator and review the server's deployment libraries.

TCM-09043: The ImagingTenant configuration setting is empty or has a bad value.
Category:: Requests/Responses
Cause:: The ImagingTenant configuration setting is empty or has a bad value.
Action:: Set the ImagingTenant configuration setting to a valid tenant identifier.

TCM-09044: There is no user name configured to create an ApplSession.
Category:: Requests/Responses
Cause:: There is no user name configured to create an ApplSession.
Action:: Change the application workflow configuration to set a csf.key.

TCM-09045: There is no csf.key mapping in an application's workflow configuration.
Category:: Requests/Responses
Cause:: There is no csf.key mapping in an application's workflow configuration.
Action:: Change the application workflow configuration to set a csf.key.

TCM-10001: An error was encountered while searching the repository for closed batches
Category:: Requests/Responses
Cause:: An error occurred while searching the CDB repository for closed batches
Action:: Check the associated exception and CDB log files for errors

TCM-10002: Batch ID {0} for Application {1} has been closed and cannot be indexed into, operation aborted
Category:: Requests/Responses
Cause:: The user requested to index a document into a batch that has been closed
Action:: Check the calling code to determine why the batch was committed too early

TCM-10003: Batch ID {0} for Application {1} has already been committed
Category:: Requests/Responses
Cause:: The user attempted to commit a batch that was already closed
Action:: Check the calling code to determine why the batch was committed twice

TCM-10004: No Batches found for the Batch Name {0}, ID {1}.
Category:: Requests/Responses
Cause:: The Batch could not be found in the CDB system
Action:: Check the NameId passed to the API and make sure it exists

TCM-10005: The target application specified in the Batch object is invalid
Category:: Requests/Responses
Cause:: The target application specified in the Batch object is invalid
Action:: Check the Batch object and ensure that the target application is valid

TCM-10006: No Batches found for Batch ID {0}
Category:: Requests/Responses
Cause:: The Batch could not be found in the CDB system
Action:: Check the NameId passed to the API and make sure it exists

TCM-10007: The Batch provided is null
Category:: Requests/Responses
Cause:: The specified Batch is null
Action:: Pass a valid Batch object to the API call

TCM-10008: The requested Batch ID {0} has documents indexed into it and cannot be removed.
Category:: Requests/Responses
Cause:: The requested batch could not be deleted because it had documents indexed to it.
Action:: Double check that the correct batch was requested and verify that it is empty.

TCM-11001: Turning on or off the auditing configuration failed
Category:: Requests/Responses
Cause:: An FDK Exception was generated by the UOA system when attempting to set the auditing configuration.
Action:: Correct the underlying UOA repository configuration.

TCM-11002: The search of the audit history failed.
Category:: Requests/Responses
Cause:: The search of the repository for auditing data resulted in a repository exception.
Action:: Correct the error identified in the underlying repository exception.

TCM-14000: The provided URL ticket is invalid.
Category:: Requests/Responses
Cause:: The provided URL ticket was determined to be invalid.
Action:: Pass a valid ticket to the API call.

TCM-14001: The URL ticket is set to expire but does not have an expiration time set.
Category:: Requests/Responses
Cause:: The URL ticket was set to expire, but did not have an expiration time set.
Action:: Turn off the expiration or set the expiration time for the ticket.

TCM-14002: No parameters exist in the provided URL ticket.
Category:: Requests/Responses
Cause:: No parameters were specified in the URL ticket.
Action:: Add at least 1 parameter to the URL ticket.

TCM-14003: The parameter for value {0} in the URL ticket is missing a name.
Category:: Requests/Responses
Cause:: The ticket parameter did not have a name defined.
Action:: Assign a name to the ticket parameter.

TCM-14004: The parameter {0} does not have a value assigned to it.
Category:: Requests/Responses
Cause:: Ticket parameter did not have a value defined.
Action:: Assign a value to the parameter.

TCM-14005: The provided ticket identifier is invalid.
Category:: Requests/Responses
Cause:: The ticket identifier was invalid.
Action:: Specify a valid ticket identifier.

TCM-14006: A ticket with the identifier {0} cannot be found.
Category:: Requests/Responses
Cause:: The provided ticket identifier could not be found in the system.
Action:: Verify that the ticket identifier is correct.

TCM-14007: The ticket agent is not processing requests.
Category:: Requests/Responses
Cause:: The ticket agent service could not be located.
Action:: Verify that the imaging ear deployment is valid and is running.

TCM-14008: A create ticket request that is set to expire has an invalid expiration date.
Category:: Requests/Responses
Cause:: An attempt was made to create a ticket with an expiration date in the past.
Action:: Fix the create request so that the ticket has a date in the future.

TCM-14009: The ticket parameter name {0} is longer than the maximum allowed name length of 200.
Category:: Requests/Responses
Cause:: An attempt was made to create a ticket parameter with a name that is too long.
Action:: Shorten the parameter name to be less than 200 characters.

TCM-14010: The ticket parameter value {0} is longer than the maximum allowed value length of 200.
Category:: Requests/Responses
Cause:: An attempt was made to create a ticket parameter with a value that is too long.
Action:: Shorten the parameter value to be less than 200 characters.

TCM-15000: The provided Connection object is null
Category:: Requests/Responses
Cause:: No Connection was provided
Action:: Call the method with a valid Connection object

TCM-15001: Failed to remove the connection as it has the following application dependencies: {0}.
Category:: Requests/Responses
Cause:: Connection is still in use
Action:: Remove the dependent applications prior to removing the connection

TCM-15002: Attempting to create or modify a connection with the following details: {0}.
Category:: Requests/Responses
Cause:
Action:

TCM-15003: Connection successfully created or modified.
Category:: Requests/Responses
Cause:
Action:

TCM-15004: An error occurred during an attempt to create or modify a connection. {0}.
Category:: Requests/Responses
Cause:: An error occurred creating a connection.
Action:: See the log for details of the error and correct the problem before trying again.

TCM-16001: The import data supplied is null.
Category:: Requests/Responses
Cause:: Data supplied for the import operation was null.
Action:: Verify the import data is valid and not null.

TCM-16002: Import/Export requires administrator privileges in order to run.
Category:: Requests/Responses
Cause:: The user supplied does not have the proper permissions.
Action:: Verify the user is an administrator.

TCM-70007: The specified Input Source {0} cannot be found.
Category:: Requests/Responses
Cause:: An Input Source name was provided that does not match any sources that the Input Server has loaded.
Action:: Check the Input Source name.

TCM-70008: The server interval setting is missing from the configuration file.
Category:: Requests/Responses
Cause:: The server interval configuration is missing from the configuration file.
Action:: Check the configuration file.

TCM-70009: The Input Definition is invalid.
Category:: Requests/Responses
Cause:: The Input parameter was null.
Action:: Supply a valid Input to the call.

TCM-70010: No data was provided for the mapped document file section.
Category:: Requests/Responses
Cause:: A document file was not provided.
Action:: Add a patch to the desired document image file to the input file.

TCM-70013: Cannot find the field {0}, id {1} in the Application, check the Application and Input for proper mappings.
Category:: Requests/Responses
Cause:: The application field for a section mapping couldn't be found
Action:: Check to make sure the application field hasn't been deleted and examine the Input field mappings

TCM-70015: The Batch {0} given to Input Agent is marked closed and cannot be used to add objects to.
Category:: Requests/Responses
Cause:: The Batch that Input Agent was assigned to file to is marked as closed
Action:: Restart the entire input file as a new filing.

TCM-70016: A check interval setting of {0} is invalid. Specify a value between 1 and 60.
Category:: Requests/Responses
Cause:: An invalid check interval was provided.
Action:: Set the interval between 1 and 60.

TCM-70017: An error occurred while manipulating the Input Filing Queue
Category:: Requests/Responses
Cause:: An error occurred while trying to browse the input queue
Action:: Check the embedded error for more details

TCM-70018: The value {0} is too large or small to fit in a numeric field.
Category:: Requests/Responses
Cause:: The value that was parsed was outside the valid range for a numeric type.
Action:: Fix the value so that it is inside the numeric data type range.

TCM-70020: The retry count setting {0} is invalid, enter a value between 1 and 100
Category:: Requests/Responses
Cause:: An invalid retry count was set into the MBean
Action:: Try using a retry value between 1 and 100

TCM-70021: The input value {0} could not be converted to a date. It does not conform to a short, medium or long date format for the current locale.
Category:: Requests/Responses
Cause:: An invalid date string was parsed from the input file
Action:: Correct the value so that it is in the correct date format

TCM-70022: The input value {0} could not be converted to a number.
Category:: Requests/Responses
Cause:: An invalid decimal string was parsed from the input file
Action:: Correct the value so that it is a valid number

TCM-70023: The input value {0} could not be converted to a decimal.
Category:: Requests/Responses
Cause:: An invalid date string was parsed from the input file
Action:: Correct the value so that it is a valid decimal

TCM-70024: An existing set of state information was found for the job {0} for Input {1} and cannot be duplicated. Input Agent is ignoring this request.
Category:: Requests/Responses
Cause:: Existing filing State information was found for the data source and Input and cannot be added twice.
Action:: Clear out all filings for the Input and allow the server to remove the extra state information.

TCM-70025: There is no valid document id to run the command on.
Category:: Requests/Responses
Cause:: The command could not be executed because the last document failed to index and no document id was specified.
Action:: Either fix the indexing error for the last document in the file or specify a document id to apply the command to.

TCM-70026: The supporting content key value was not found in the command.
Category:: Requests/Responses
Cause:: No key value was specified for the supporting content command.
Action:: Add a supporting content key to the supporting content command.

TCM-70027: The supporting content file path was not found in the command.
Category:: Requests/Responses
Cause:: The supporting content file name was not found.
Action:: Add the supporting content's full path to the command.

TCM-70028: The annotation file path was not found in the command.
Category:: Requests/Responses
Cause:: The annotation file name was not found.
Action:: Add the annotation file's full path to the command.

TCM-70029: The file cleanup expire days {0} is invalid. The number of days must be greater than or equal to 0 and less than or equal to 30.
Category:: Requests/Responses
Cause:: An invalid file cleanup expire day count was provided.
Action:: Provide an integer value in the range from 0 to 30 days.

TCM-70030: The tenant {0} is not valid
Category:: Requests/Responses
Cause:: An invalid tenant name was given.
Action:: Call the MBean with a valid tenant name that is not empty.

TCM-70031: The specified directory {0} is not a valid input directory.
Category:: Requests/Responses
Cause:: An invalid input directory was provided.
Action:: Provide a directory that is in the input directories list.

TCM-70032: The specified directory {0} is not one of the current Input Directories.
Category:: Requests/Responses
Cause:: The input directory that was provided is not in the current set of Input Directories.
Action:: Specify an Input Directory that is currently in the Input Directory set.

TCM-70033: The Input Directory {0} already has tenant {1} associated with it. Only one tenant can be associated with a directory at one time
Category:: Requests/Responses
Cause:: The input directory that was provided is already associated with a tenant.
Action:: Either delete the existing tenant first or associate the tenant with a different directory.

TCM-70034: Tenant {0} is currently assigned to input directory {1}. A tenant can only be associated with one directory.
Category:: Requests/Responses
Cause:: The tenant name provided is already associated with an input directory.
Action:: Either delete the existing tenant association or provide a unique tenant for the directory.

TCM-71002: The input source cannot set up the stage path correctly.
Category:: Requests/Responses
Cause:: The plugin encountered an error trying to set up the stage path.
Action:: Check to make sure the plugin can get to the machine name.

TCM-71003: Encountered error {0} while writing to the error file {1}
Category:: Requests/Responses
Cause:: An error occurred while writing to the error file.
Action:: Check the disk, path, and user permissions.

TCM-71004: The failed path {0} cannot be initialized for processing.
Category:: Requests/Responses
Cause:: The failed directory could not be initialized.
Action:: Check the permissions to the Input Directory and subdirectories.

TCM-71005: The file mask {0} is invalid because it contains path information in addition to the file mask. Remove the additional path information.
Category:: Requests/Responses
Cause:: The file mask has at least a partial path in it, which is not supported.
Action:: Remove the path portion of the file mask

TCM-71006: Cannot lock the input file {0} for processing.
Category:: Requests/Responses
Cause:: The input file could not be locked for processing.
Action:: Make sure another program isn't accessing the file.

TCM-71007: Cannot save file {0} since a file with the same name already exists there
Category:: Requests/Responses
Cause:: The user tried to upload a sample file with a name that already exists in the directory
Action:: Specify a unique name before uploading to the sample directory

TCM-71008: Cannot save the given file to the sample directory. Error message provided is: {0}.
Category:: Requests/Responses
Cause:: The sample file could not be saved to the sample directory.
Action:: Check the embedded exception for more details.

TCM-71009: The state file {0} cannot be created.
Category:: Requests/Responses
Cause:: The state file could not be created.
Action:: Check the stage directory to make sure that it has enough space and the correct permissions.

TCM-71010: The state file {0} cannot be updated.
Category:: Requests/Responses
Cause:: The state file could not be updated.
Action:: Check the stage directory to make sure that it has enough space and the correct permissions.

TCM-71011: No instances of the delimiter {0} were found in the current line of the input file
Category:: Requests/Responses
Cause:: The delimiter is missing for the input file line
Action:: Check the delimiter in the Input Definition and make sure it's the correct one for the input file

TCM-71012: The file {0} is 0 bytes in length and cannot be processed.
Category:: Requests/Responses
Cause:: An attempt was made to process an input file that has 0 bytes.
Action:: Process a file with data in it.

TCM-71013: The file state information cannot be loaded for data source {0}
Category:: Requests/Responses
Cause:: Error loading the filing state for the input file
Action:: Examine the database and any inner exceptions to determine the cause of the load error

TCM-71014: The filing state information cannot be found for data source {0}.
Category:: Requests/Responses
Cause:: The filing state could not be found for the input file
Action:: Check the database to make sure that the filing state entry still exists

TCM-90001: Conversation ID not found: {0}
Category:: Session
Cause:: Conversation identifier was not found in current session.
Action:: Start over, if the problem persists, contact your system administrator.

TCM-90002: Task Context is unavailable.
Category:: Session
Cause:: Workflow Task Context was not available.
Action:: Start over. If the problem persists, contact your system administrator.

TCM-90003: Invalid Task ID: {0}
Category:: Session
Cause:: Task ID provided was not available in request or in cache.
Action:: Start over, if the problem persists, contact your system administrator.

TCM-90004: Task {0} already acquired by {1}
Category:: Session
Cause:: The chosen workflow task has already been acquired by another user.
Action:: Select another task and try again.

TCM-90005: Username cannot be changed.
Category:: Session
Cause:: Username cannot be changed without changing sessions.
Action:: Logout and log in with the desired user.

TCM-90006: Username cannot be null.
Category:: Session
Cause:: Username passthrough is set to TRUE. Username is required with this setting.
Action:: Provide a valid username and try again.

TCM-91000: An unexpected system error occurred. Contact your system administrator for support.
Category:: Programmatic
Cause:: An error has occurred.
Action:: Contact Oracle Support Services for help determining the cause.

TCM-91001: SolutionParameter not found for: SolutionNamespace={0}, CommandNamespace={1}, ConfigurationNamespace={2}, ParameterKey={3}
Category:: Configuration
Cause:: SolutionParameter was not found in "AXF_SOLUTION_PARAMETERS" table for the provided SolutionNamespace, CommandNamespace, ConfigurationNamespace, ParameterKey.
Action:: Verify that the "AXF_SOLUTION_PARAMETERS" table contains this value.

TCM-91002: SystemParameter not found for: Namespace={0}, ParameterType={1}, ParameterKey={2}
Category:: Configuration
Cause:: SystemParameter was not found in "AXF_SYSTEM_PARAMETERS" table for the provided SolutionNamespace, ParameterType, ParameterKey.
Action:: Verify that the "AXF_SYSTEM_PARAMETERS" table contains this value.

TCM-91003: There was an error with the supplied XPath: {0}
Category:: Configuration
Cause:: There was an error with the provided XPath
Action:: Verify XPATH configuration in "AXF_XPATH_ATTRIBUTE" table

TCM-91004: SolutionNamespace cannot be modified in an existing Conversation
Category:: Programmatic
Cause:: SolutionNamespace cannot be modified in an existing Conversation identifier.
Action:: Start a new Conversation identifier for the new SolutionNamespace.

TCM-91005: SolutionNamespace not configured: {0}
Category:: Configuration
Cause:: Provided SolutionNamespace was not configured in the "AXF_SOLUTIONS" table.
Action:: Ensure the SolutionNamespace entered has a matching entry in the "AXF_SOLUTIONS" table.

TCM-91006: System cache failure
Category:: Process
Cause:: The system cache failed.
Action:: Contact Oracle Support Services with all log information, and restart your server.

TCM-91007: Unable to load command {0} using configured command class {1}
Category:: Configuration
Cause:: Failed to create the instance of command provided in the "AXF_COMMANDS" table
Action:: Check configuration entry in "AXF_COMMANDS" table and verify that the matching class has been loaded in the application server

TCM-91008: Unable to find command "{0}" in the database.
Category:: Configuration
Cause:: Unable to find the provided command in "AXF_COMMANDS" table
Action:: Check the command entry in "AXF_COMMANDS" table

TCM-91009: Unable to create named connection: {0}
Category:: Configuration
Cause:: Failed to find the workflow connection information from the Imaging system
Action:: Check configuration entry in "AXF_SOLUTION_ATTRIBUTE" table and the corrresponding entry in "CONNECTION_DETAILS" table.

TCM-91010: Unable to create named connection without a provider specified
Category:: Configuration
Cause:: Failed to create named connection without a provider specified
Action:: Check configuration entry in "AXF_SOLUTION_ATTRIBUTE" table and the corrresponding entry in "CONNECTION_DETAILS" table.

TCM-91014: Solution Parameter Key {0} has an invalid value of {1} for Solution Namespace = {2} -- Command Namespace = {3} -- Configuration Namespace = {4}
Category:: Configuration
Cause:: The Solution Parameter Key has an invalid value in "AXF_SOLUTION_PARAMETERS" for the provided SolutionNamespace, ParameterType, ParameterKey.
Action:: Verify the configuration parameter in "AXF_SYSTEM_PARAMETERS" table for the Redirect Command.

TCM-91015: Error executing pl/sql procedure: {0} using connection: {1} for conversation: {2}
Category:: Configuration
Cause:: Failed to execute pl/sql procedure in UpdateTaskFromProcedureCommand.
Action:: Verify the configuration parameter in "AXF_SYSTEM_PARAMETERS" table for UpdateTaskFromProcedureCommand.

TCM-91016: Unable to retrieve database connection using JNDI name: {0}
Category:: Configuration
Cause:: Failed to retrieve the JNDI name from Application Server.
Action:: Verify the configuration parameter in "AXF_SYSTEM_PARAMETERS" table and ensure that JNDI is setup correctly in application server.

TCM-91017: Unable to retrieve the web root context from the application server.
Category:: Configuration
Cause:: Failed to retrieve the web root context from the application server.
Action:: Contact Oracle Support Services for help determining cause.

TCM-91018: SolutionNamespace attribute not found for: Namespace={0}, ParameterKey={1}
Category:: Configuration
Cause:: SolutionNamespace attribute was not found in the "AXF_SOLUTION_ATTRIBUTES" table for the BPEL_CONNECTION key.
Action:: Check the "AXF_SOLUTION_ATTRIBUTES" Table for the missing configuration.

TCM-91019: Command Parameter Key {0} has an invalid value of {1} for Solution Namespace = {2}, Command Namespace = {3}
Category:: Configuration
Cause:: Command Parameter Key is missing, invalid or empty for Solution Namespace.
Action:: Check the request parameters for command.

TCM-91020: Unable to decode the value in URL {0}
Category:: Configuration
Cause:: This encoding is not supported.
Action:: Check the encoding URL value.

TCM-91021: UCM unable to process the request - {0}
Category:: Configuration
Cause:: UCM is unable to process the request.
Action:: Check the UCM configuration.

TCM-91022: Please login as Admin user to perform the grant operation.
Category:: Session
Cause:: You are trying to perform the operation as a normal user. Only admin user can perform this operation.
Action:: Login as Admin user to perform this operation.

TCM-91023: Error accessing credential from CSF having key {0}
Category:: Configuration
Cause:: An error occurred while accessing a credential key in the credential store.
Action:: Ensure that the correct key was provided and the credentials are properly configured in the credential store.

TCM-91201: Unable to create sorts for workflow
Category:: Configuration
Cause:: Got the workflow exception while creating ordering
Action:: Check permission for workflow user and workflow log

TCM-91202: Unable to create predicates for workflow
Category:: Configuration
Cause:: Got the workflow exception while creating predicate
Action:: Check permission for workflow user and workflow log

TCM-91203: Payload column is not supported for filtering
Category:: Configuration
Cause:: Payload column is not supported for filtering
Action:: Remove payload from column filtering

TCM-91204: Attributes list is null or empty
Category:: Configuration
Cause:: Attributes list was null or empty
Action:: Supply at least one attribute

TCM-91205: Unable to find the value specified by xpath : {0}
Category:: Configuration
Cause:: Xpath found no matching element in the workload payload.
Action:: Verify the xpath value in "AXF_XPATH_ATTRIBUTES" table and that the workflow payload has a corresponding entry.

TCM-91206: Workflow admin userid is missing
Category:: Configuration
Cause:: Failed to get the workflow admin userid.
Action:: Check the workflow admin userid in CSF of application server for the matching alias key in "CONNECTION_DETAILS" table.

TCM-91207: Workflow admin password is missing
Category:: Configuration
Cause:: Failed to get the workflow admin password.
Action:: Check the workflow admin password in CSF of application server for the matching alias key in "CONNECTION_DETAILS" table.

TCM-91208: Workflow provider url is missing
Category:: Configuration
Cause:: Failed to get the workflow provider url.
Action:: Check the host and port in "CONNECTION_DETAILS" database table

TCM-91209: Unable to authenticate from workflow
Category:: Configuration
Cause:: Failed to authenticate with workflow server.
Action:: Check the workflow password in CSF of application server for the matching alias key in "CONNECTION_DETAILS" table.

TCM-91210: Unable to locate the security member specified
Category:: Configuration
Cause:: Failed to locate the security policy store.
Action:: Check the application server security configuration for authentication.

TCM-91211: Unable to locate the security store identity
Category:: Configuration
Cause:: Failed to locate the security store identity.
Action:: Check the application server security configuration for authentication.

TCM-91212: User {0} does not exist in the policy store.
Category:: Configuration
Cause:: User did not exist in the policy store.
Action:: Validate the user in the policy store.

TCM-91213: Unable to find the users in the policy store.
Category:: Configuration
Cause:: Failed to find the users in the policy store.
Action:: Verify that users exist in the policy store.

TCM-91214: Unable to find the roles in the policy store.
Category:: Configuration
Cause:: Failed to find the roles in the policy store
Action:: Check the application server security configuration for authentication

TCM-91215: Unable to find the policies in the policy store
Category:: Configuration
Cause:: Unable to find the policies in the policy store
Action:: Check the application server security configuration for authentication

TCM-91216: Unable to get the payload value for {0}
Category:: Configuration
Cause:: Failed to find an element in workflow payload using xpath
Action:: Verify the xpath value in "AXF_XPATH_ATTRIBUTES" table and the workflow payload has it

TCM-91217: Unable to load XML file '{0}' into XML Document
Category:: Configuration
Cause:: Failed to load XML file into XML Document to create the views.
Action:: Check the XML file permissions, format, and location on disk.

TCM-91218: View name is blank. It must be set to create a view. XML = {0}
Category:: Configuration
Cause:: View name was blank in the provided XML file.
Action:: Ensure that the view name is not empty in the XML file and node tag is /workflowSet/FFMSet/FFMDefinition/[<view name>]/FFMDetail/name.

TCM-91219: User name is blank. It must be set to create a view. XML = {0}
Category:: Configuration
Cause:: User name was blank, it must be set to create a view.
Action:: Ensure that the user name is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]//userList/user[<user>].

TCM-91220: User name or realm is blank. It must be set to create a view. XML = {0}
Category:: Configuration
Cause:: User name or realm was blank.
Action:: Ensure that the user name or realm is blank in the XML file.

TCM-91221: View Filter Column name is blank. It must be set to create a view. XML = {0}
Category:: Configuration
Cause:: View filter Column name was blank.
Action:: Ensure that the View Filter Column name is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]//userViewDetail/viewPredicate/clause[<position>]/column.

TCM-91222: Filter Operation is blank. It must be set to create a view. XML = {0}
Category:: Configuration
Cause:: Filter operation was blank.
Action:: Ensure that the Filter Operation is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]//userViewDetail/viewPredicate/clause[<position>]/operator.

TCM-91223: Filter Value is blank. XML = {0}
Category:: Configuration
Cause:: Filter value was blank.
Action:: Ensure that the Filter Value is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]//userViewDetail/viewPredicate/clause[<position>]/value.

TCM-91224: View Ordering column name is blank. XML = {0}
Category:: Configuration
Cause:: View ordering column name was blank.
Action:: Ensure that the View ordering column name is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]/userViewDetail/viewOrdering/clause[<position>]/column.

TCM-91225: View Ordering sort order is blank. XML = {0}
Category:: Configuration
Cause:: View ordering sort order was blank.
Action:: Ensure that the View ordering sort order is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]/userViewDetail/viewOrdering/clause[<position>]/sortOrder

TCM-91226: View Creation failed. XML = {0}
Category:: Configuration
Cause:: Failed to create the workflow View
Action:: Check user permissions to create the view and also check the workflow server log

TCM-91227: View Column name was blank. XML = {0}
Category:: Configuration
Cause:: View column name was blank, it must be set to create a view
Action:: View Column name is blank in the XML fileand node tag is /workflowSet/viewSet/viewDefinition/[<view name>]/userViewDetail/viewColumns/column[<position>]

TCM-91228: Unable to get the next task
Category:: Configuration
Cause:: Failed to retrieve the next task from workflow.
Action:: There may be no tasks for this user in workflow. Check the workflow server log.

TCM-91229: Unable to get list of tasks
Category:: Configuration
Cause:: Failed to get list of tasks
Action:: Workflow server may be not running or password is not correct in CSF. Check the workflow server log

TCM-91230: Unable to get list of views
Category:: Configuration
Cause:: Failed to get list of views
Action:: Workflow server may be not running or password is not correct in CSF. Check the workflow server log

TCM-91231: Unable to acquire task id {0} for user {1}
Category:: Configuration
Cause:: Failed to acquire task id from workflow.
Action:: The task may be already acquired by another user. Check the workflow server log.

TCM-91232: got the stale object from workflow
Category:: Configuration
Cause:: The task from workflow is out of date.
Action:: Log out from the application and try again.

TCM-91233: Unable to release task id {0} for user {1}
Category:: Configuration
Cause:: Failed to release task id from workflow.
Action:: Verify that the task can be acquired by the current user. Check the workflow server log.

TCM-91234: Unable to get the task detail for {0}
Category:: Configuration
Cause:: Failed to get the task detail from workflow.
Action:: Verify that the task is not already completed or purged in workflow.

TCM-91235: Task ID is null
Category:: Configuration
Cause:: Task Id was invalid or null.
Action:: Logout from application and try again.

TCM-91236: Unable to update the task for {0}
Category:: Configuration
Cause:: Failed to update the task in workflow.
Action:: Verify that the task may be acquired to update the payload. Check the workflow server log.

TCM-91237: Unable to update outcome for {0}
Category:: Configuration
Cause:: Failed to update the outcome in workflow.
Action:: Verify that the task may be acquired to update and that the outcome is valid. Check the workflow server log.

TCM-91238: Unable to acquire next available task for {0}
Category:: Configuration
Cause:: Failed to acquire next available task in workflow.
Action:: There may be no task for this user in the workflow. Check the workflow server log.

TCM-91239: Unable to update transaction ID in workflow payload
Category:: Configuration
Cause:: Failed to update transaction ID in workflow payload.
Action:: Verify Transaction field exists in the workflow payload.

TCM-91240: Unable to get comments
Category:: Configuration
Cause:: Failed to get comments from workflow.
Action:: Check the user's permission to get comments. Check the workflow server log.

TCM-91241: Comment is null.
Category:: Configuration
Cause:: The value of Comment was null.
Action:: Contact your system administrator.

TCM-91242: Unable to update comment in workflow
Category:: Configuration
Cause:: Failed to update the comment in workflow.
Action:: User may not have permission to update the comment. Check the workflow server log.

TCM-91243: Invalid URL for identity search URL
Category:: Configuration
Cause:: Received URL was Invalid for identity search
Action:: Check the URL for identity search in the database

TCM-91244: Unable to open the connection for identity search URL
Category:: Configuration
Cause:: Failed to open the connection for identity search URL.
Action:: Verify that the Web service is available for identity search.

TCM-91245: Unable to parse the XML date received from identity search URL
Category:: Configuration
Cause:: Failed to parse XML date received from identity search URL
Action:: Check the XML format of input file as it may be invalid. There may be some invalid tag in the file

TCM-91246: Unable to acquire the task. Task is not assigned to the group or is assigned to a different user.
Category:: Configuration
Cause:: Either the task was not assigned to the group or it was assigned to a different user.
Action:: Select another task from the list.

TCM-91247: Invalid Task attribute Key {0}
Category:: Configuration
Cause:: Received Invalid Task attribute Key.
Action:: Check your configuration or command for the attribute Key value

TCM-92002: Access is denied.
Category:: Requests/Responses
Cause:: User does not have access to the requested information.
Action:: Ensure user is defined with proper permissions.

TCM-92501: Duplicate annotation IDs exist
Category:: Requests/Responses
Cause:: Duplicate annotation IDs exist.
Action:: Ensure that each annotation has a unique id. Annotations cannot be added more than once.

TCM-92502: Null or empty annotation Id specified
Category:: Requests/Responses
Cause:: Null or empty annotation Id specified.
Action:: Ensure that annotation id is not null or empty.

TCM-92503: Null annotation object specified
Category:: Requests/Responses
Cause:: Invalid annotation object specified.
Action:: Ensure that annotation object is not null and has a valid Id.

TCM-92504: Annotation list is Null
Category:: Requests/Responses
Cause:: Annotation list to search is null.
Action:: Ensure that annotation list object is not Null.

TCM-92505: Annotation requires at least three points
Category:: Requests/Responses
Cause:: This annotation requires at least three points.
Action:: Provide three points, or use a LineAnnot object.

TCM-92506: There was an error deserializing an annotation file for this document.
Category:: Requests/Responses
Cause:: There was an error deserializing an annotation file for this document.
Action:: Check the nested exception details for diagnostic information.

TCM-92507: There was an error serializing an annotation file for this document.
Category:: Requests/Responses
Cause:: There was an error serializing an annotation file for this document.
Action:: Check the nested exception details for diagnostic information.

TCM-92508: An annotation list cannot be merged with itself
Category:: Requests/Responses
Cause:: An annotation list cannot be merged with itself.
Action:: Specify a unique list of annotations.

TCM-92509: A null value was supplied where an AnnotPoint object is expected.
Category:: Requests/Responses
Cause:: A null value was supplied where an AnnotPoint object is expected
Action:: Provide a valid AnnotPoint object

TCM-92510: The requested scale is not within the allowed value range; {0}-{1}
Category:: Requests/Responses
Cause:: The requested scale is not within the allowed value range.
Action:: Provide a proper scale value within the supported range.

TCM-92511: Page number must be a positive value.
Category:: Requests/Responses
Cause:: Page number must be a positive value.
Action:: Provide a page number that is greater than zero.

TCM-92512: Bounding rectangle specified is empty.
Category:: Requests/Responses
Cause:: Bounding rectangle specified is empty.
Action:: Supply a non-null, non-empty rectangle definition.

TCM-92513: The Document Store provider {0} cannot be loaded
Category:: Requests/Responses
Cause:: The specified Document Store could not be loaded
Action:: Make sure the provided class is correct and that it exists in the classpath

TCM-92514: Redact annotation cannot be assigned HIDDEN security.
Category:: Requests/Responses
Cause:: Redact annotation cannot be assigned HIDDEN security.
Action:: Use a different security setting.

TCM-92515: The page annotations include at least one annotation from another page.
Category:: Requests/Responses
Cause:: An attempt was made to replace page annotations with at least one annotation from a different page.
Action:: Supply only annotations for the page specified.

TCM-92516: Error deserializing annotations. InputStream is null.
Category:: Requests/Responses
Cause:: Error deserializing annotations. InputStream is null.
Action:: Supply a serialized annotation stream.

TCM-92517: Transformation process returned error code {0}.
Category:: Requests/Responses
Cause:: Transformation process returned an error code.
Action:: See the transformation process return code for diagnostic information.

TCM-92518: There was an error launching the external transformation process: {0} {1}
Category:: Requests/Responses
Cause:: There was an error launching the external transformation process
Action:: The transformation process failed unexpectedly. Check nested exception details for diagnostic information.

TCM-92521: The path specified for GdFontPath configuration is invalid.
Category:: Requests/Responses
Cause:: The path specified for GdFontPath configuration is invalid.
Action:: Provide a valid path to a directory containing True Type Fonts.

TCM-92522: There was an error reading TIFF headers. The file may be corrupt.
Category:: Requests/Responses
Cause:: There was an error reading TIFF headers. The file may be corrupt.
Action:: Check permissions and free space in the server temp directory.

TCM-92523: There was an error authenticating the user. Please login and retry.
Category:: Requests/Responses
Cause:: There was an error authenticating the user.
Action:: Check the nested exception details for diagnostic information.

TCM-92524: There was an error getting the document annotations. Please verify the document ID.
Category:: Requests/Responses
Cause:: There was an error getting the document annotations. Please verify the document ID.
Action:: Check the nested exception details for diagnostic information.

TCM-92525: There was an error getting the document. Please verify the document ID.
Category:: Requests/Responses
Cause:: There was an error getting the document. Please verify the document ID.
Action:: Check the nested exception details for diagnostic information.

TCM-92700: The cache config file can not be found
Category:: Requests/Responses
Cause:: The cache configuration file was not found.
Action:: Inspect the Cache jar and verify that the CacheConfig.xml file exists.

TCM-92701: The cache storage configuration is not in the config file
Category:: Requests/Responses
Cause:: The configuration for the cache storage adaptor could not be found.
Action:: Add a valid storage adaptor to the cache config file.

TCM-92702: The cache configuration file cannot be read for processing
Category:: Requests/Responses
Cause:: The cache configuration file could not be read.
Action:: Please examine the inner exception to determine why the read operation failed.

TCM-92703: The cache storage adaptor could not be found
Category:: Requests/Responses
Cause:: The storage adaptor implementation could not be found.
Action:: Check the cache config file and verify that the storage adaptor is correct.

TCM-92704: The cache storage adaptor could not be instantiated
Category:: Requests/Responses
Cause:: The storage adaptor could not be loaded.
Action:: Examine the adaptor code and verify it has a parameterless constructor.

TCM-92705: Error writing to Lock file {0}.
Category:: Requests/Responses
Cause:: There was a problem writing to a file.
Action:: Check the inner exception to determine the cause of the error.

TCM-92706: A lock could not be acquired on lock file {0}.
Category:: Requests/Responses
Cause:: The lock file could not be locked and validated.
Action:: Check the inner exception to determine the cause of the error.

TCM-92707: The directory {0} could not be created.
Category:: Requests/Responses
Cause:: The specified directory could not be created.
Action:: Examine the path to make sure it is not full and that the server account has write privileges to it.

TCM-92708: The Document ID {0} is not valid.
Category:: Requests/Responses
Cause:: The Document ID that was specified is not valid.
Action:: Pass in a valid Document ID to the cache service.

TCM-92709: An error occurred while queuing the cache request for processing.
Category:: Requests/Responses
Cause:: An exception was raised while attempting to queue the cache request.
Action:: Look at the inner exception to get details on the cause of the error.

TCM-92710: The cache repository interface configuration value was not found.
Category:: Requests/Responses
Cause:: The configuration for the repository interface could not be found.
Action:: Add a valid repository interface to the cache config file.

TCM-92711: The configuration string for the repository interface could not be parsed.
Category:: Requests/Responses
Cause:: The configuration information for the repository interface is not valid.
Action:: Look at the repository configuration and make sure that the values are separated by semicolons.

TCM-92712: The viewer cache imaging repository interface could not be initialized.
Category:: Requests/Responses
Cause:: The viewer cache imaging repository interface could not be initialized for processing.
Action:: Examine the inner exception to get specifics on why the initialization failed.

TCM-92713: The viewer cache repository could not retrieve requested document {0}.
Category:: Requests/Responses
Cause:: The requested document could not be retrieved from the viewer cache repository.
Action:: Examine the inner exception to get specifics on why the operation failed.

TCM-92714: The viewer cache repository interface {0} could not be found.
Category:: Requests/Responses
Cause:: The cache repository implementation could not be found.
Action:: Check the cache config file and verify that the repository configuration is correct.

TCM-92715: An instance of the viewer cache repository {0} could not be created.
Category:: Requests/Responses
Cause:: The cache repository could not be loaded.
Action:: Examine the inner exception and repository implementation to determine the load error.

TCM-92716: The viewer cache repository could not get the annotations for document {0}.
Category:: Requests/Responses
Cause:: The requested annotation set could not be retrieved from the viewer cache repository.
Action:: Examine the inner exception to get specifics on why the operation failed.

TCM-92717: The file {0} can not be found for processing.
Category:: Requests/Responses
Cause:: The requested file could not be found for processing.
Action:: Determine if the file exists and has the correct permissions.

TCM-92718: {0} is not a valid document page.
Category:: Requests/Responses
Cause:: The requested page to retrieve from cache is invalid.
Action:: Check the cache request and verify the requested page is greater than 0.

TCM-92719: The requested page range of {0} to {1} is not valid.
Category:: Requests/Responses
Cause:: The requested cache page range is invalid.
Action:: Check the end page of the cache request and verify that it is greater than the start page.

TCM-92720: The cache directory for object {0} could not be locked for processing
Category:: Requests/Responses
Cause:: The cache lock file failed verification.
Action:: Check to make sure that the imaging services have full access to the directory and it is not shared with other imaging systems.

TCM-92721: A failure occurred while attempting to get configuration values from imaging.
Category:: Requests/Responses
Cause:: An error was encountered while trying to look up the configuration data.
Action:: Look at the nested error to get the exact cause of the error.

TCM-92722: Page number {0} is invalid, document {1} only has {2} pages.
Category:: Requests/Responses
Cause:: The requested page is not in the document.
Action:: Request a page number that is in the document's page range.

TCM-92723: Processing was aborted while waiting for results.
Category:: Requests/Responses
Cause:: The operation was stopped while waiting for the operations results.
Action:: Check the logs to see if an operation was forcibly stopped.

TCM-92724: An error was encountered while trying to read or write to the image stream.
Category:: Requests/Responses
Cause:: A failure occurred while reading or writing from an image.
Action:: Check the inner exception to determine the cause of the error.

TCM-92725: The image could not be converted to a PNG stream because the image writer could not be found or have its options set.
Category:: Requests/Responses
Cause:: The PNG image writer could not be loaded or could not have its options set.
Action:: Check the Java installation and verify all the libraries are installed.

TCM-92726: Could not get the annotation security for document {0}.
Category:: Requests/Responses
Cause:: The document's annotation security could not be determined.
Action:: Check the inner exception to determine the cause of the error.

TCM-92727: This document contains annotations that prevent the user from accessing this document in its raw format
Category:: Requests/Responses
Cause:: This document contains annotations that prevent the user from accessing this document in its raw format.
Action:: Export to TIFF with the annotations burned in or contact your administrator for access to the native format.

TCM-92728: The image information for document {0}, page {1} could not be read.
Category:: Requests/Responses
Cause:: The image information could not be read.
Action:: Check the inner exception to determine the cause of the error.

TCM-92729: Error loading the document properties for document {0}
Category:: Requests/Responses
Cause:: Failed to get the document properties.
Action:: Check the inner exception to determine the cause of the error.

TCM-92730: The rendering cache is disabled and not accepting requests.
Category:: Requests/Responses
Cause:: The rendering cache feature is disabled.
Action:: Set the ViewerCacheDays and ViewerCachePath configuration values in the configuration MBean to enable caching.

TCM-92731: Document {0} failed image conversion and cannot be stored in the cache at this time. Please review the server log for details on the cause of the error.
Category:: Requests/Responses
Cause:: The requested document could not be converted to the appropriate image format.
Action:: Examine the log files to determine the cause of the conversion errors.

TCM-92732: The credential for storing the encryption key was not found.
Category:: Requests/Responses
Cause:: The credential for storing the encryption key was not found.
Action:: Verify the credential for the encryption key is available.

TCM-92733: A failure occurred while encrypting the document.
Category:: Requests/Responses
Cause:: A failure occurred while encrypting the document.
Action:: Check the inner exception to determine the cause of the error.

TCM-92734: A failure occurred while generating the encryption key.
Category:: Requests/Responses
Cause:: A failure occurred while generating the encryption key.
Action:: Check the inner exception to determine the cause of the error.

TCM-92735: A failure occurred while retrieving the encryption key.
Category:: Requests/Responses
Cause:: A failure occurred while retrieving the encryption key.
Action:: Check the inner exception to determine the cause of the error.

TCM-92736: A failure occurred while storing the encryption key.
Category:: Requests/Responses
Cause:: A failure occurred while storing the encryption key.
Action:: Check the inner exception to determine the cause of the error.

TCM-92737: A failure occurred while generating the encryption cipher.
Category:: Requests/Responses
Cause:: A failure occurred while generating the encryption cipher.
Action:: Check the inner exception to determine the cause of the error.

TCM-92738: A failure occurred while using the cipher for encryption.
Category:: Requests/Responses
Cause:: A failure occurred while using the cipher for encryption.
Action:: Check the inner exception to determine the cause of the error.

TCM-92739: A failure occurred while using the cipher for decryption.
Category:: Requests/Responses
Cause:: A failure occurred while using the cipher for decryption.
Action:: Check the inner exception to determine the cause of the error.

TCM-92740: No priority value was specified for the add to cache request.
Category:: Requests/Responses
Cause:: A priority was not specified for the add request.
Action:: Call the add request with a priority value.

TCM-92741: An error occurred while queuing the cache request. The Oracle WebCenter Content: Imaging Viewer Cache application (imaging-vc) was not found.
Category:: Requests/Responses
Cause:: The viewer cache application deployment was not found.
Action:: Check the domain configuration an verify that the viewer cache application is properly deployed.

TCM-92742: This document content is sealed. IRM content cannot be rendered.
Category:: Requests/Responses
Cause:: This document content is sealed. IRM content cannot be rendered.
Action:: Download the native document and use Oracle IRM Desktop to access this file content.

TCM-92999: An error occurred in a subsystem. {0}
Category:: Requests/Responses
Cause:: An error occurred in a rendering subsystem.
Action:: Review the logs for the error. You may need to contact Oracle Support Services to resolve the issue.

TCM-99001: The repository definition identifier, {0}, is not valid.
Category:: Requests/Responses
Cause:: An attempt was made to add a repository configuration with a duplicate identifier.
Action:: Use a unique identifier.

TCM-99002: The repository definition name, {0}, is not valid.
Category:: Requests/Responses
Cause:: An attempt was made to add a repository configuration with a duplicate name.
Action:: Use a unique name.

TCM-99003: The repository definition identifier, {0}, is not unique.
Category:: Requests/Responses
Cause:: An attempt was made to add a repository configuration with a duplicate identifier.
Action:: Use a unique identifier.

TCM-99004: The repository definition name, {0}, is not unique.
Category:: Requests/Responses
Cause:: An attempt was made to add a repository configuration with a duplicate name.
Action:: Use a unique name.

TCM-99005: A system repository definition already exists.
Category:: Requests/Responses
Cause:: An attempt was made to add a system repository configuration when one already exists.
Action:: Remove the existing system repository first.

TCM-99006: The destination repository is read only and does not support this operation.
Category:: Requests/Responses
Cause:: An attempt was made to copy or move a document to a repository that is not writeable.
Action:: Change the destination repository to one that is writeable.

TCM-99007: The destination repository is not the same as the source repository.
Category:: Requests/Responses
Cause:: An attempt was made to move a document to a different repository.
Action:: Ensure that the source and destination repositories are the same.

TCM-99008: The destination repository is not the same type as the source repository.
Category:: Requests/Responses
Cause:: An attempt was made to move a document to a different type of repository.
Action:: Ensure that the source and destination repositories are the same type.

TCM-99009: The repository must be initialized to support WebCenter Content: Imaging prior to creating a connection.
Category:: Requests/Responses
Cause:: An attempt was made to create a connection to a system that is not yet configured.
Action:: Ensure that target UCM system is configured prior to creating a connection.