Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1.5.0)

Part Number E10113-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

86 TCM-00006 to TCM-99009

TCM-00006: The NameId for the request is not valid.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00007: The Id for the request is not valid.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Programmatic

TCM-00009: No session has been established.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-00012: Unable to log in to the UOA repository
Cause: IPM could not log in to the UOA system.
Action: Check to make sure the UOA system is up and running properly.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Configuration

TCM-00015: Unable to find file {0}
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00016: Unable to open file {0}
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00021: This session is already established.
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.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00026: The requested definition is not found.
Cause: The user does not have access to the definition.
Action: Check the user's access to the requested definition.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00027: User does not have permission to access this page.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00028: The definition arrays supplied are empty.
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.

Level: 1

Type: ERROR

Impact: Programmatic

TCM-00029: The {0} section is read-only and cannot be modified.
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.

Level: 1

Type: ERROR

Impact: Programmatic

TCM-00040: Encountered exception initializing regions.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00041: Cache is Ready = {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00042: Cache Distributed = {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00043: Imaging region exists.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00044: Cache failed during initialization and may be disabled.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00106: Workflow agent processing fault recorded for document {0}.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00107: Workflow agent cannot record fault for document {0}. Returning to workflow agent queue for retry.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00110: Constructed Input Agent Bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00111: Destroyed Input Agent Bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00112: Input Agent encountered an error during shutdown.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00115: Beginning Input Agent initialization.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00116: Input Agent initialization is complete.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00120: Input Agent time interval is not set. Cannot continue.
Cause: Input Agent time interval is not set.
Action: Update the Check Interval setting to a valid value in the IPM config MBean.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00122: An error occurred checking for work.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00126: Beginning Input Agent servlet initialization.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00127: Input Agent servlet initialization is complete.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00129: Input Agent is checking for work.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00150: Constructed Input Filing MDB.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00151: Destroyed Input Filing MDB.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00160: Input Filing MDB failed to log out.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00162: Failed to load Batch for new filing.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00163: An error occurred while completing a batch.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00164: Input Agent cannot find WLS Runtime MBean server.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00170: Constructed Ticket Agent MDB.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00171: Destroyed Ticket Agent MDB.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00172: Beginning Ticket Agent servlet initialization.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00173: Ticket Agent servlet initialization is complete.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00177: Beginning Ticket Agent initialization.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00178: Ticket Agent initialization is complete.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00179: Encountered an error while attempting to clean up expired tickets from the IPM system
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00196: Encountered an error while logging out of IPM system
Cause:
Action:

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00199: IPM API error encountered, attempting restart.
Cause: An IPM API error was encountered.
Action: Review the server logs for further information.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00777: A database error occurred.
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.

Level: 1

Type: ERROR

Impact: Data

TCM-00787: A repository error occurred.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00788: The following error is reported by the repository: {0}
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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.
Cause: The Content Server was shut down in the middle of a request
Action: Check to make sure the Content Server is still up and running.

Level: 1

Type: ERROR

Impact: Configuration

TCM-00790: UOA shared libraries are not properly deployed and targeted to this IPM server.
Cause: The UOA shared libraries have not been properly deployed and targeted to this IPM server. This occurs most often when UOA is not installed at the same time as IPM from configuration wizard.
Action: Ensure that the UOA shared libraries are deployed and targeted to the IPM Managed Server instances.

Level: 1

Type: ERROR

Impact: Configuration

TCM-00791: The Content Server does not have a defined document profile field.
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00998: Multiple errors in a subsystem. {0}
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00999: Error in a subsystem. {0}
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01017: Unable to update application. User does not have proper permissions.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01018: Unable to delete application. The application contains documents.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01025: The NameId for the application does not contain a name or an identifier.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01027: Lifecycle policy action specification, {0}, is not found.
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-01028: Lifecycle policy date rule specification, {0}, is not found.
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-01031: Missing a closing delimiter near "{0}".
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.

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01039: The document is not allowed to be updated. It is read-only.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-02009: Primary application category not found.
Cause: Primary application category not found in UOA.
Action: Verify that the UOA system has been initialized correctly for IPM.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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.
Cause: An invalid file name was provided for the document.
Action: Enter a valid file name. Do not include any path information.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02017: Document replacement is not allowed for this document.
Cause: Document cannot be replaced because it is not locked out.
Action: Check out document and try again.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02039: The document action could not be performed because the document is under records management in the repository.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02040: The file timeout {0} is invalid for document operations. The timeout must be greater than or equal to 0.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03012: An error occurred while saving annotations
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03024: An annotation cannot be accepted due to the lack of permission.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03035: User does not have sufficient annotation permission in the destination application.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03036: An error occurred retrieving annotations for the document.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03037: Error saving annotations to a document version that is not the current version.
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-04001: A valid Input name or ID must be specified for the operation to complete.
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04008: The Input's Source Properties section is invalid
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04009: The specified data source is invalid.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04012: The Input does not define any mappings, or one or more mappings are invalid
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-04014: The specified input's state cannot be updated
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04015: The specified input definition cannot be updated
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04020: The Input Path for CSV filings has not been configured properly.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04021: Input Source {0} cannot be found
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04022: Error loading Input Source Plugin
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-04026: The specified Input Source "{0}" cannot be found
Cause: The given Input Source name does not match any sources that the Input Server has loaded.
Action: Check the Input Source name.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-04033: Date value does not conform to the short, medium or long format type for the current locale, date cannot be parsed.
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04035: The application({0},{1}) specified in the mapping cannot be found. Verify that the application exists and you have permissions to it.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04036: The mapping for input section {0} is invalid
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04040: The sample path {0} cannot be initialized for processing
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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04041: The get contents request for data source {0} cannot be processed because it is not a sample source.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04051: The input file locale has already been set and cannot be changed
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04053: The locale command can only be used at the beginning of the input file
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04055: The value {0} provided for the Input Server state update is the wrong type or is out of range.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05007: The requested search, {0}, was not found.
Cause: The user does not have access to the search.
Action: Check the user's access to the requested search.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05016: The type for the search argument does not match the search parameter type.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05017: The entered value, {0}, is < 1. The default maximum rows returned value must be >= 1.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06011: Users assigned the 'admin' group either directly or indirectly are not allowed to log into IPM.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06017: Access to modify the document security of this definition is denied.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07001: Requested output format does not support multiple pages
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07008: This document contains annotations that prevent the user from accessing this document in its raw format
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07012: An error occurred when loading an image for translation.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07014: An error occurred when processing image manipulation commands during save.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07016: An I/O error occurred creating the output for this request.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07037: An error occurred retrieving a rendition to create a copy with.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07038: The requested page number is beyond the document page range.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07039: This document content is sealed. IRM content cannot be rendered.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Installation

TCM-08005: User does not have create permissions.
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.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-08006: User does not have delete permissions.
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.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-08008: User does not have permission to access the "{0}" system folder.
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Installation

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-08011: Unable to log in to the IPM system
Cause: An error was encountered while logging in to the IPM system.
Action: Check the IPM logs and any inner exception for details on why the login failed.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09010: An error occurred trying to list storage policy volumes.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09034: Error reading workflow service WSDL document {0}
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 IPM and the workflow server are correct.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09035: Error accessing credential key ''{0}''
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10002: Batch ID {0} for Application {1} has been closed and cannot be indexed into, operation aborted
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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10003: Batch ID {0} for Application {1} has already been committed
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

Level: 1

Type: WARNING

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10008: The requested Batch ID {0} has documents indexed into it and cannot be removed.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14001: The URL ticket is set to expire but does not have an expiration time set.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14008: A create ticket request that is set to expire has an invalid expiration date.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14009: The ticket parameter name {0} is longer than the maximum allowed name length of 200.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14010: The ticket parameter value {0} is longer than the maximum allowed value length of 200.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70007: The specified Input Source {0} cannot be found.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70013: Cannot find the field {0}, id {1} in the Application, check the Application and Input for proper mappings.
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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70015: The Batch {0} given to Input Agent is marked closed and cannot be used to add objects to.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70018: The value {0} is too large or small to fit in a numeric field.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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.
Cause: An invalid date string was parsed from the input file
Action: Correct the value so that it is in the correct date format

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70025: There is no valid document id to run the command on.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71002: The input source cannot set up the stage path correctly.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71005: The file mask {0} is invalid because it contains path information in addition to the file mask. Remove the additional path information.
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71007: Cannot save file {0} since a file with the same name already exists there
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71009: The state file {0} cannot be created.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71010: The state file {0} cannot be updated.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71011: No instances of the delimiter {0} were found in the current line of the input file
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71013: The file state information cannot be loaded for data source {0}
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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71014: The filing state information cannot be found for data source {0}.
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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: WARNING

Impact: Session

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

Level: 1

Type: WARNING

Impact: Session

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

Level: 1

Type: WARNING

Impact: Session

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

Level: 1

Type: WARNING

Impact: Session

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

Level: 1

Type: ERROR

Impact: Programmatic

TCM-91001: SolutionParameter not found for: SolutionNamespace={0}, CommandNamespace={1}, ConfigurationNamespace={2}, ParameterKey={3}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91002: SystemParameter not found for: Namespace={0}, ParameterType={1}, ParameterKey={2}
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Programmatic

TCM-91005: SolutionNamespace not configured: {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Process

TCM-91007: Unable to load command {0} using configured command class {1}
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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91009: Unable to create named connection: {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91010: Unable to create named connection without a provider specified
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91014: Solution Parameter Key {0} has an invalid value of {1} for Solution Namespace = {2} -- Command Namespace = {3} -- Configuration Namespace = {4}
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91016: Unable to retrieve database connection using JNDI name: {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91018: SolutionNamespace attribute not found for: Namespace={0}, ParameterKey={1}
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91205: Unable to find the value specified by xpath : {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91206: Workflow admin userid is missing
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91207: Workflow admin password is missing
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91209: Unable to authenticate from workflow
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91216: Unable to get the payload value for {0}
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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91218: View name is blank. It must be set to create a view. XML = {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91219: User name is blank. It must be set to create a view. XML = {0}
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>].

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91221: View Filter Column name is blank. It must be set to create a view. XML = {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91222: Filter Operation is blank. It must be set to create a view. XML = {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91223: Filter Value is blank. XML = {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91224: View Ordering column name is blank. XML = {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91225: View Ordering sort order is blank. XML = {0}
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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91227: View Column name was blank. XML = {0}
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>]

Level: 1

Type: ERROR

Impact: Configuration

TCM-91228: Unable to get the next task
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91229: Unable to get list of tasks
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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91230: Unable to get list of views
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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91233: Unable to release task id {0} for user {1}
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91236: Unable to update the task for {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91237: Unable to update outcome for {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

TCM-91238: Unable to acquire next available task for {0}
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91245: Unable to parse the XML date received from identity search URL
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

Level: 1

Type: ERROR

Impact: Configuration

TCM-91246: Unable to acquire the task. Task is not assigned to the group or is assigned to a different user.
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.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92515: The page annotations include at least one annotation from another page.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92999: An error occurred in a subsystem. {0}
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99006: The destination repository is read only and does not support this operation.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

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

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99008: The destination repository is not the same type as the source repository.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99009: The repository must be initialized to support IPM prior to creating a connection.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses