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

90 UCM-CS-000001 to UCM-CS-050023

UCM-CS-000001: general exception
Cause: An exception occurred in the content server.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000002: Error:
Cause: An error occurred in the content server.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000003: Unknown system error encountered.
Cause: An error occurred in the content server.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000004: Unknown error encountered.
Cause: The system encountered an unknown error.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000005: Null pointer is dereferenced.
Cause: A null pointer exception occurred in the content server.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Logging

UCM-CS-001001: The NativeOsUtils class is not loaded.
Cause: The required library 'NativeOsUtils' was not successfully loaded.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001002: Native file operations are disabled.
Cause: The system's ability to do native file operations has been disabled.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001003: The platform {0} is not supported.
Cause: The specified operating system does not supported.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001004: The platform {0} is not supported for this operation.
Cause: The specified operating system did not support the specified operation.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001005: The argument {0} is missing.
Cause: The method or service was missing the required argument.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001006: {0} is missing from {1}.
Cause: The method or service was missing the required argument.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001007: Unable to load database queries in table {0} for component {1}. The table does not exist.
Cause: An error was encountered while loading the queries for the named component.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001008: The feature {0} is not installed.
Cause: The required feature has not been installed.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001009: The feature {0} is at level {1}, but level {2} is required.
Cause: An error was encountered while validating features. The requested feature is not supported.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001010: Incompatibility with feature {0} at level {1} has been detected.
Cause: The specified feature was incompatible with a feature provided either by the system or another component.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001011: The feature {0} does not match feature {1}.
Cause: The feature did not match an already installed feature.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001012: The feature {0} is installed at level {1}, but is also provided at level {2}.
Cause: The feature already existed at a later version.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-005001: Unable to copy the file {0} to {1}.
Cause: An error occurred while copying files.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005002: Unable to rename the file {0} to {1}.
Cause: An error occurred while renaming files.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005003: Unable to open {0}.
Cause: An error occurred while opening the named file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005004: Unable to read {0}.
Cause: An error occurred while accessing a file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005005: Unable to write {0}.
Cause: An error occurred while writing a file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005006: The file is missing.
Cause: The specified file was missing.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005007: The file {0} does not exist.
Cause: The specified file did not exist.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005008: The file {0} already exists.
Cause: The file already existed in the system.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005009: The file {0} already exists in {1} directory.
Cause: The file already existed in the named directory.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005010: File I/O error encountered while reading from file.
Cause: An error occurred while reading the file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005011: File I/O error encountered while writing to file.
Cause: An error occurred while writing the specified file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005012: Unable to delete {0}.
Cause: An error occurred while deleting the specified file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005013: Could not create the file {0}.
Cause: An error occurred while creating the specified file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005014: File I/O error encountered while saving to file {0}.
Cause: An error occurred while saving the specified file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005015: The file path {0} is invalid.
Cause: The specified file path was invalid.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005016: Unable to find the file {0}. This may be a problem with the virtual machine.
Cause: The system expected a file at the specified location, but it was missing.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005017: Unable to find the file {0}.
Cause: The system was unable to locate the file at the specified location.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005018: Error encountered while creating long-term lock {1} on directory {0}.
Cause: An error occurred while creating the long term lock.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005019: Unable to create the directory.
Cause: An error occurred while creating the directory.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005020: Unable to create directory {0}.
Cause: An error occurred while creating the specified directory.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005021: Directory {0} does not exist.
Cause: The system was unable to locate a directory at the specified location.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005022: File {0} does not exist.
Cause: The system was unable to locate a file at the specified location.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005023: Directory {0} cannot be accessed.
Cause: An error occurred while accessing the directory.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005024: File {0} cannot be accessed.
Cause: An error occurred while accessing the specified file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005025: Directory {0} is read-only.
Cause: A read-only directory was specified.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005026: File {0} is read-only.
Cause: A read-only file was specified.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005027: Directory {0} has an invalid path.
Cause: The system tried to access an invalid directory path.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005028: File {0} has an invalid path.
Cause: The system tried access an invalid file path.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005029: Accessing the directory {0} caused a system error.
Cause: An error was encountered while accessing the directory.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005030: File {0} caused a system error when accessed.
Cause: An error was encountered while accessing the file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005031: Unable to rename the file {0} to {1}.
Cause: An error was encountered when trying to rename the specified file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005032: The source file does not exist.
Cause: The specified file did not exist.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005033: The target file cannot be accessed.
Cause: The system was unable to access the specified file path.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005034: Unable to copy the file {0} to {1}. The source file does not exist.
Cause: An error was encountered while copying the file. The source file did not exist.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005035: Unable to copy the file {0} to {1}.
Cause: An error was encountered while copying the file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005037: File is locked by another process.
Cause: The file was locked by another process.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005038: File {0} cannot be deleted. It may be locked by another process.
Cause: An error was encountered while deleting the file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-005039: Long-term lock {0} cannot be created for agent {1}.
Cause: An error was encountered while attempting to create a long-term lock.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Files

UCM-CS-010001: Cannot end string with {0}.
Cause: During the parsing of a string, an illegal end character was encountered.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010002: Encountered an unterminated quote ({0}) at {1} in {2}.
Cause: During the parsing of a string, the parser found an unclosed quoted string.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010003: Error encountered converting data with {0} character encoding.
Cause: An encoding error was encountered while converting the data.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010004: Error encountered converting data with the default character encoding.
Cause: The system encountered an error while converting data with the default character encoding.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010005: An error occurred decoding the stream.
Cause: An error was encountered while decoding the data.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010006: Cannot find the parameter {0}.
Cause: The system could not find the named parameter.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010007: The table does not exist.
Cause: The named table did not exist or was not loaded into the resource container.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010008: The column {0} does not exist in this table.
Cause: The specified column did not exist in the table.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010009: Parameter {0} is not present.
Cause: The parameter was not defined in the current data set.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010010: Unable to parse result set {0}.
Cause: An error was encountered while parsing the result set.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010011: Unable to parse properties. Name-value pair {0} is missing an equal sign (=).
Cause: An error was encountered while parsing a property name-value pair.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010012: Error decoding the string. The string is badly formatted: {0}
Cause: An error was encountered while decoding the badly formatted string.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010013: A name-value pair is missing the name in GET or POST syntax.
Cause: An error was encountered while parsing the request.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010014: The input terminated before being able to read the line.
Cause: An error was encountered while reading the input stream.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010015: The stream terminated before being able to read HTTP protocol line.
Cause: An error was encountered while reading the input stream.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010016: Unable to parse data; the request method was not specified.
Cause: An error was encountered while parsing the input stream. The request method has not been specified.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010017: The POST request did not send sufficient data.
Cause: An error was encountered while parsing the request.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010018: Unable to read the stream to determine the format.
Cause: An error was encountered while processing the server request.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010019: Unable to read additional bytes.
Cause: An error was encountered while processing the server file request.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-010020: Client terminated the upload of file {0}.
Cause: The client terminated the upload of the file.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-050001: illegal state
Cause: Something put the system into an unexpected error; this is a generic error.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050002: The transaction listener {0} failed to close.
Cause: The transaction failed to close when performing the service request.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050003: Database table does not exist.
Cause: An error was encountered while performing a database activity.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050004: Cannot bind all parameters in query {0}.
Cause: An error was encountered while creating the SQL query. The number of parameters required was inconsistent with the number of parameters provided.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050005: Unable to initialize the database {0}.
Cause: An error was encountered while the system was initializing the database connections.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050006: Unable to create database connection for {0}.
Cause: An error was encountered while trying to create a database connection for the named server instance.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050007: Server busy. Unable to obtain a connection to the database.
Cause: The server was unable to establish a connection to the database.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050008: Unable to execute query {0}.
Cause: An error was encountered while executing the specified query.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050009: Unable to execute callable query {0}.
Cause: An error was encountered while executing the named callable query.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050010: Unable to create the result set for query {0}.
Cause: An error was encountered while creating the results for the specified query.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050011: Unable to execute SQL statement {0}.
Cause: An error was encountered while executing the given SQL statement.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050012: Unable to determine the database type.
Cause: An error was encountered while determining the database type.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050013: Error occurred while closing connection: ({0}).
Cause: An error was encountered while closing the database connection.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050014: Cannot begin the transaction. JDBC Error:
Cause: An error was encountered while beginning a database transaction.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050015: Cannot commit the transaction. JDBC Error:
Cause: An error was encountered while committing a database transaction.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050016: Failed to find indexable webviewable for content item {0} with revlabel {1} and dID {2}.
Cause: An error was encountered while indexing the specified content item.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050017: Text conversion of the file {0} failed.
Cause: An error was encountered while indexing the specified content item.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050018: Indexing failed.
Cause: An error was encountered while indexing the specified content item.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050019: The creation date ({0}) of the new revision is not later than the creation date ({1}) of the latest revision in the system.
Cause: An error was encountered while importing the content item. The create date for the new revision must be later than the older revision.
Action: The Archiver uses dates to validate the correct order of revisions. By default, it uses the dCreateDate, but this can be configured to use the dInDate by setting the configuration parameter UseRevisionCreateDate to true.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050020: The release date ({0}) of the new revision is not later than the release date ({1}) of the latest revision in the system.
Cause: An error was encountered while importing the content item. The in date for the new revision must be later than the older revision.
Action: The Archiver uses dates to validate the correct order of revisions. By default, it uses the dCreateDate, but this can be configured to use the dInDate by setting the configuration parameter UseRevisionCreateDate to true.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050021: UCM Server failed to initialize inside its servlet environment.
Cause: An error was encountered during initialization of the servlet environment./td>
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050022: Active index ({0}) is not valid for the indexer engine ({1}).
Cause: The currently active search index was invalid for the configured indexer engine.
Action: A rebuild of the search collection is required.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050023: An error occurred during indexing.
Cause: The system encountered an error while indexing a document.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

Level: 1

Type: ERROR

Impact: Programmatic