51 UCM-CS-000001 to UCM-CS-800280

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-000006: Trace Message:({0})

Cause: A general trace message from 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: NOTIFICATION

Impact: Logging

UCM-CS-000007: Out of memory exception

Cause: An out of memory 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: INCIDENT_ERROR

Impact: Logging

UCM-CS-000008: service exception

Cause: A service 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-000009: data exception

Cause: A data 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-001013: The instance name {0} is not valid.

Cause: The instance name specified contained illegal characters.

Action: The instance name needs to be configured to be a valid name. Please check documentation for how to configure.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001014: {0} component, version {1}, requires missing feature(s). {2}

Cause: For the specified component to function correctly it needs the listed features.

Action: The components that provide the listed features need to be installed.

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

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.

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

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.

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

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.

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

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.

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: INCIDENT_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: INCIDENT_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: Oracle WebCenter Content 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

UCM-CS-050024: Search collection is not up-to-date.

Cause: The system has determined that the search indexing collection configuration has been modified.

Action: A rebuild of the search collection is recommended.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050025: Commit is called by thread {0} in auto-commit mode.

Cause: A database commit call was made in a thread configured to be in auto-commit mode.

Action: The stack trace can be examined to determine which component or feature tried to perform the commit.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050026: Database running out of tablespace

Cause: The database system is running out of tablespace.

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: INCIDENT_ERROR

Impact: Programmatic

UCM-CS-050027: Possible database connection failure encountered. Error message: ({0}).

Cause: The system has encountered a database connection failure.

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: INCIDENT_ERROR

Impact: Programmatic

UCM-CS-050028: Unable to create database connection for the database {0} with connection string {1}. Please make sure that the connection string, user and password are correct.

Cause: The system has encountered an issue with creating a 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: INCIDENT_ERROR

Impact: Programmatic

UCM-CS-060000: Starting the service {0} version {1} PID {2}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060001: {0} component, version {1}, provides {2} feature(s)

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060002: Server ready and waiting for connection on port {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060003: Event generated by user {0} at host {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060004: User {0} changed the following entry in config.cfg on server {1}:

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060005: Restarting rebuild of the search index.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060006: Starting rebuild of the search index.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060007: Finished rebuilding the search index with a total of {0} files successfully indexed. A total of {1} files had a full text index.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060008: Finished rebuilding the search index with a total of {0} files successfully indexed. A total of {1} files had a full text index and {2} failed to index.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060009: Indexing aborted.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060010: Text index {0} is optimized.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060011: Started monitoring.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060012: Event {0} has finished

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060013: Shutting down server connections.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060014: Trace is verbose.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060015: Trace sections list has been updated to {0}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060016: Referred to by {0}.\&lf;

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Files

UCM-CS-060017: User agent is {0} and request method is {1}.\&lf;

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Files

UCM-CS-060018: The refresh activity '{0}' has completed {1} out of {2} links with {3} errors.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060019: The fsconfig.hda file has been created in the data/filestore/config directory.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060020: Added:

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060021: Modified:

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060022: Removed:

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060023: Trace is not verbose.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-100001: Oracle WebCenter Capture URL has not been configured. Please contact the Administrator.

Cause: ODDCURLPath environment variable is not set.

Action: Set the ODDCURLPath to point to ODDC server.

Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-100002: Unable to detach Oracle WebCenter Content document from siebel entity.

Cause: Database delete operation failed since the row does not exist if the document is already detached.

Action: Refresh the Managed Attachments window.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-100003: Error: siebelEntityField and siebelEntityValue are mandatory Parameters.

Cause: One of the parameters SiebeleEntityField OR SiebeleEntittyValue is missing.

Action: Make sure the URL has the parameters SiebeleEntityField AND SiebeleEntittyValue.

Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-100101: User '{0}' does not have sufficient access privileges to perform this operation. Access privileges may have expired, requiring the user to re-select Managed Attachments from the Oracle E-Business Suite Zoom Menu.

Cause: User does not have sufficient access privileges to perform this operation.

Action: Contact Administrator for getting appropriate Roles for Access.

Level: 1

Type: ERROR

Impact: Configuration

Cause: Access privileges may have expired.

Action: User needs to re-select Managed Attachments from the Oracle E-Business Suite Zoom Menu.

UCM-CS-100102: Failed to detach document '{0}'

Cause: Document detach operation failed because the document is already detached or deleted.

Action: Refresh Managed Attachments page and try this operation again.

Level: 1

Type: ERROR

Impact: Data

UCM-CS-100103: User '{0}' does not have sufficient access privileges to perform this operation. Access privileges may have expired, requiring the user to re-access Managed Attachments from the PeopleSoft User Interface.

Cause: User does not have sufficient access privileges to perform this operation.

Action: Contact Administrator for getting appropriate Roles for Access.

Level: 1

Type: ERROR

Impact: Configuration

Cause: Access privileges may have expired.

Action: User needs to re-select Managed Attachments from the Oracle E-Business Suite Zoom Menu.

UCM-CS-800001: Cannot load archive.

Cause: Cannot load archive.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800002: Cannot build archive.

Cause: Cannot build archive.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800003: No value was provided and no default value is set for the metadata field

Cause: No value was provided and no default value is set for the metadata field

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800004: The form '{0}' already contains a field named '{1}'.

Cause: The form already contains a field of the same name.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800005: Dashboard error occured while saving as new dashboard

Cause: Dashboard error occured while saving as new dashboard

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800006: Workflow approve action does not work for non-existent item.

Cause: Workflow approve action does not work for non-existent 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800007: Unable to load from RSS URL location. Check RSS dashboard options in edit view.

Cause: Unable to load from RSS URL location. Check RSS dashboard options in edit view.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800008: Unable to update the configuration information.

Cause: Unable to update the configuration information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800009: Unable to update the data source information.

Cause: Unable to update the data source information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800010: Unable to export the report type xml data.

Cause: Unable to export the report type xml 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800011: Unable to check in report.

Cause: Unable to check in report.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800012: Unable to run the scheduled report.

Cause: Unable to run the scheduled report.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800013: Unable to checkout default reports.

Cause: Unable to checkout default reports.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800014: The report template is missing.

Cause: The report template is 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800015: Unable to get the service data source parameters.

Cause: Unable to get the service data source parameters.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800016: Unable to get the query data source parameters.

Cause: Unable to get the query data source parameters.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800017: The BL Publisher RTF processor failed.

Cause: The BL Publisher RTF processor failed.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800018: Unable to get the related content.

Cause: Unable to get the related content.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800019: Unable to get the related content types.

Cause: Unable to get the related content types.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800020: The related type ID is missing.

Cause: The related type is missing a field.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800021: The related type name '{0}' does not exist.

Cause: The related type name does 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800022: The related type name '{0}' already exists.

Cause: The related type name already exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800023: The related type class ID is missing.

Cause: The related type class ID is 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800024: The supersede related type cannot be edited. Related content currently exists.

Cause: The supersede related type cannot be edited. Related content currently exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800025: The content ID (dID) is missing.

Cause: The content ID is 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800026: No external sources were found. Check to see if the 'ExternalHelper' component is installed and enabled.

Cause: No external sources were found. Check to see if the 'ExternalHelper' component is installed and enabled.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800027: More than one superseded content links selected. Please remove excess superseded links.

Cause: More than one superseded content links selected. Please remove excess superseded links.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800028: URMAgent or RetentionManager components are disabled. Please click ok to enable the components. Then, restart the server and configure UrmAgent source.

Cause: URMAgent or RetentionManager components are disabled. Please click ok to enable the components. Then, restart the server and configure UrmAgent source.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800029: {0} disposition action is not defined in DispositionActionsList

Cause: Disposition Action is not specified for this dDispostion.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800030: Error while checking setup requirements for new component install.

Cause: Error while checking setup requirements for new component install.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800031: Cannot checkout content item: Not Revisionable.

Cause: Cannot checkout content item: Not Revisionable.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800032: Cannot edit content item: Not Editable.

Cause: Cannot edit content item: Not Editable.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800033: Cannot delete content item: Not Deletable.

Cause: Cannot delete content item: Not Deletable.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800034: User does not have access to folders(or parent folders) or folder does not exists.

Cause: User does not have access to folders(or parent folders) or folder does not exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800035: Error retrieving information about category '{0}'

Cause: Error retrieving information about the category

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800036: Error retrieving information about folder '{0}'

Cause: Error retrieving information about the folder

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800037: Error retrieving information about series '{0}'

Cause: Error retrieving information about the series

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800038: Error creating category named '{0}': category with specified id exists

Cause: Error creating item, item with specified id exists

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800039: Unable to get screening results for categories

Cause: Unable to get screening results

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800040: Unable to prepare the HDA edit form.

Cause: Unable to prepare the HDA edit form.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800041: Unable to notify pending event actions

Cause: Unable to notify pending event actions

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800042: Unable to Mark Reviewed

Cause: Unable to Mark Reviewed

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800043: Unable to supersede content or records.

Cause: Unable to supersede content or records.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800044: Access denied - cutoff items are readonly

Cause: Access denied - cutoff items are readonly

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800045: Failed to delete metadata history.

Cause: Failed to delete metadata history.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800046: Disposition contains unprocessed content or record.

Cause: Disposition contains unprocessed content or record.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800047: Unable to find log or report information.

Cause: Unable to find log or report information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800048: Failed to process report.

Cause: Failed to process report.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800049: Cannot edit frozen content or folder

Cause: Cannot edit frozen content or folder

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800050: Unable to run batch services for notifications

Cause: Unable to run batch services

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800051: Unable to list scheduled freezes

Cause: Unable to list scheduled freezes

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800052: Cannot delete frozen content.

Cause: Cannot delete frozen content.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800053: Unable to Notify Process Monitoring Alerts

Cause: Unable to Notify Process Monitoring Alerts

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800054: Unable to reset performance process monitoring

Cause: Unable to reset performance process monitoring

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800055: Unable to reset performance process monitoring alerts

Cause: Unable to reset performance process monitoring alerts

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800056: Unable to parse category dispositions information

Cause: Unable to parse category dispositions information

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800057: The field {0} requires an integer entry.

Cause: The field requires an integer entry.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800058: System derived cutoff must be first action

Cause: System derived cutoff must be first action

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800059: Invalid Trigger Event: first disposition rule has no preceding action

Cause: Invalid Trigger Event: first disposition rule has no preceding action

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800060: Delete Revision action is forbidden in permanent categories

Cause: Delete Revision action is forbidden in permanent categories

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800061: Destroy or Delete Revision action is forbidden in permanent categories

Cause: Destroy or Delete Revision action is forbidden in permanent categories

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800062: Destroy action is forbidden in permanent categories

Cause: Destroy action is forbidden in permanent categories

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800063: The first character of the Name field must be alphabetic

Cause: The first character of the Name field must be alphabetic

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800064: The Name field contains invalid character

Cause: The Name field contains invalid character

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800065: User does not have all matching Supplemental Markings.

Cause: User does not have all matching Supplemental Markings.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800066: User does not have Security Markings.

Cause: User does not have Security Markings.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800067: User does not have group(alias)/user permissions (ACL-based collaboration security privilege).

Cause: User does not have group(alias)/user permissions (ACL-based collaboration security privilege).

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800068: Performance process monitoring time exceeded max limit

Cause: Performance process monitoring time exceeded max limit

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800069: This class can only contain classes

Cause: This class can only contain classes

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800070: This class can only contain files

Cause: This class can only contain 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800071: This class can only contain content items (or volumes)

Cause: This class can only contain content items (or volumes)

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800072: This class can contain classes, files, or content items

Cause: This class can contain classes, files, or content items

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800073: This file can only contain sub-files

Cause: This file can only contain sub-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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800074: This file can only contain content items (or volumes)

Cause: This file can only contain content items (or volumes)

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800075: This file can contain sub-files or content items

Cause: This file can contain sub-files or content items

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800076: This sub-file can only contain content items (or volumes)

Cause: This sub-file can only contain content items (or volumes)

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800077: This volume can only contain content items

Cause: This volume can only contain content items

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800078: There was an internal error in submitting the form

Cause: There was an internal error in submitting the form

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800079: There was an internal error in reseting the form

Cause: There was an internal error in reseting the form

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800080: Error initiating connection or retrieving HTTP response code.

Cause: Error initiating connection or retrieving HTTP response code.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800081: Unable to get response stream from HTTP request.

Cause: Unable to get response stream from HTTP 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800082: Http request needs a response rule to be specified is requesting agent a browser or an application

Cause: Http request needs a response rule to be specified is requesting agent a browser or an application

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800083: Unable to initiate connection.

Cause: Unable to initiate 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800084: The connection is currently not available.

Cause: The connection is currently not available.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800085: Credential map data was not successfully loaded.

Cause: Credential map data 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800086: Credentials map table {0} is missing.

Cause: Credentials map table is 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800087: Error creating charge type '{0}'.

Cause: Error creationg charge 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800088: Error editing charge type '{0}'.

Cause: Error editing charge 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800089: Error deleting charge type '{0}'.

Cause: Error deleting charge 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800090: Error retrieving information about charge type '{0}'.

Cause: Error retrieving information about charge 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800091: Charge type '{0}' already exists.

Cause: Error creating charge type: charge type with specified id exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

Cause: Charge type already exists.

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 entriesthat are part of this message stack.

UCM-CS-800092: Invalid adjustment amount. Adjustment amount cannot make the invoice amount less than zero.

Cause: Invalid adjustment amount. Adjustment amount cannot make the invoice amount less than zero.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800093: Error creating payment type '{0}'.

Cause: Error creationg payment 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800094: Error editing payment type '{0}'.

Cause: Error editing payment 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800095: Error deleting payment type '{0}'.

Cause: Error deleting payment 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800096: Error retrieving information about payment type '{0}'.

Cause: Error retrieving information about payment 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800097: Payment type '{0}' already exists.

Cause: Error creating payment type: charge type with specified id exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

Cause: Payment type already exists.

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 entriesthat are part of this message stack.

UCM-CS-800098: Error creating customer '{0}'.

Cause: Error creationg customer.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800099: Error editing customer '{0}'.

Cause: Error editing customer.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800100: Error deleting customer '{0}'.

Cause: Error deleting customer.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800101: Error retrieving information about customer '{0}'.

Cause: Error retrieving information about customer.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800102: Customer '{0}' already exists.

Cause: Error creating customer: customer with specified id exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800103: Payment type '{0}' already exists.

Cause: Error creating payment type: charge type with specified id exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

Cause: Payment type already exists.

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 entriesthat are part of this message stack.

UCM-CS-800104: Charge type '{0}' already exists.

Cause: Error creating charge type: charge type with specified id exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

Cause: Charge type already exists.

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 entriesthat are part of this message stack.

UCM-CS-800105: Error creating charge transaction '{0}'.

Cause: Error creating charge 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800106: Error browsing charge transactions for invoice '{0}'.

Cause: Error browsing charge transactions.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800107: Object Type is missing. You must provide an object type for charges with actions (Creation, Destruction or Reservation).

Cause: Object Type is missing. You must provide an object type for charges with actions (Creation, Destruction or Reservation).

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800108: Invalid object type. The charge types object type does not match the external items object type

Cause: Invalid object type. The charge types object type does not match the external items object 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800109: Invalid media type. The charge types media type does not match the external items media type

Cause: Invalid media type. The charge types media type does not match the external items media 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800110: Invalid external item. The specific external item does not exist.

Cause: Invalid external item. The specific external item does 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800111: Cannot delete a paid transaction.

Cause: Cannot delete a paid 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800112: Unable to retrieve transaction results.

Cause: Unable to retrieve transaction results.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800113: External Item is missing. You must provide an ID or Name for the external item you wish to add a transaction for.

Cause: External Item is missing. You must provide an ID or Name for the external item you wish to add a transaction for.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800114: Must select one or more charge periods for calculation and indicate a number for charge increments. (Days, Weeks, etc).

Cause: Must select one or more charge periods for calculation and indicate a number for charge increments. (Days, Weeks, etc).

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800115: Must indicate a number for charge increments for each selected charge period.

Cause: Must indicate a number for charge increments for each selected charge period.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800116: Must select a department client for processing.

Cause: Must select a department client for processing.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800117: Error Processing Storage Charges.

Cause: Error Processing Storage Charges.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800118: Cannot delete charge type '{0}' is being used by charge transactions.

Cause: Cannot delete charge type, it is being used by charge transactions.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800119: Cannot delete customer '{0}' is being used by charge invoices.

Cause: Cannot delete customer, they are is being used by charge invoices.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800120: Error creating storage item.

Cause: Error creating storage 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800121: Error deleting storage '{0}'

Cause: Error deleting storage 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800122: Storage item is unavailable

Cause: Storage item is unavailable

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800123: Storage item is blocked

Cause: Storage item is blocked

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800124: Storage item is reserved

Cause: Storage item is reserved

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800125: Storage '{0}' is not empty.

Cause: Storage item is not empty.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800126: Unable to block storage item(s). One or more storage item(s) contains an external content item(s).

Cause: Unable to block storage item(s). One or more storage item(s) contains an external content item(s).

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800127: Unable to reserve storage item(s). One or more storage item(s) contains an external content item(s) or is reserved.

Cause: Unable to reserve storage item(s). One or more storage item(s) contains an external content item(s) or is reserved.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800128: Unable to delete storage item(s). One or more storage item(s) contains an external content item(s).

Cause: Unable to delete storage item(s). One or more storage item(s) contains an external content item(s).

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800129: Error updating storage availability.

Cause: Error updating storage availability.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800130: Unable to get storage items for export.

Cause: Unable to get storage items for export.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800131: Error editing storage types.

Cause: Error editing storage types.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800132: Error retrieving information about storage type '{0}'.

Cause: Error retrieving information about storage 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800133: Error creating storage type '{0}': storage type with specified id exists.

Cause: Error creating storage type: storage type with specified id exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800134: Error creating object type '{0}': object type with specified id exists.

Cause: Error creating object type: object type with specified id exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800135: Object Type is Linked to another object type.

Cause: Object Type is Linked to another object 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800136: Error creating media type '{0}': media type with specified id exists.

Cause: Error creating media type: media type with specified id exists.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800137: Media type '{0}' is being used by external content.

Cause: Media type is being used by external content.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800138: Error editing request.

Cause: Error editing 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800139: Cannot complete requests that have not been processed

Cause: Cannot complete requests that have not been processed

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800140: Cannot update a checked out request with any other status than completed

Cause: Cannot update a checked out request with any other status than completed

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800141: Cannot update a non-processed request with status of returned

Cause: Cannot update a non-processed request with status of returned

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800142: Check out date cannot be less than request date

Cause: Check out date cannot be less than request date

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800143: Error rejecting reservation items.

Cause: Error rejecting reservation items.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800144: Error processing reservation content workflow.

Cause: Error processing reservation content workflow.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800145: Unable to get reservation items for export.

Cause: Unable to get reservation items for export.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800146: The external item is already pending or checked out.

Cause: The external item is already pending or checked out.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800147: Record already checked out with another item. Cannot check this item out at this time.

Cause: Record already checked out with another item. Cannot check this item out at this time.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800148: Notify Requestors of Overdue Requests

Cause: Notify Requestors of Overdue Requests

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800149: Item duplicated within request. Item maybe contained within another requested item.

Cause: Item duplicated within request. Item maybe contained within another requested 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800150: Failed to check in content item for reservation.

Cause: Failed to check in content item for reservation.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800151: Requested item has been destroyed. Cannot reserve.

Cause: Requested item has been destroyed. Cannot reserve.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800152: Reservation items belonging to this group still exist in the system.

Cause: Reservation items belonging to this group still exist 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800153: The external item '{0}' does not exist.

Cause: The external item does 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800154: Item inside of a non record container must be a non record

Cause: Item inside of a non record container must be a non record

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800155: Access denied by manager

Cause: Access denied by manager

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800156: An error occurred writing the audit.

Cause: An error occurred writing the audit.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800157: Not authorized to perform action.

Cause: Not authorized to perform action.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800158: Error processing user label.

Cause: Error processing user label.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800159: Error processing storage label.

Cause: Error processing storage label.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800160: Unable to get user label.

Cause: Unable to get user label.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800161: There are no users selected that contain barcode values. Cannot print labels.

Cause: There are no users selected that contain barcode values. Cannot print labels.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800162: There is no user(s) selected to print barcode labels for. Please select/input user(s) to print barcodes for.

Cause: There is no user(s) selected to print barcode labels for. Please select/input user(s) to print barcodes for.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800163: Content items location does not match the storage location being imported.

Cause: Content items location does not match the storage location being imported.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800164: Error moving storage item, cannot move storage items into 'Other' type storage items

Cause: Error moving storage item, cannot move storage items into 'Other' type storage items

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800165: Error moving storage item, cannot move storage items of type 'Root'.

Cause: Error moving storage item, cannot move storage items of type 'Root'.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800166: Error moving storage item, cannot move storage items of type 'Other'.

Cause: Error moving storage item, cannot move storage items of type 'Other'.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800167: Error moving storage item, storage item already exists within the selected storage item.

Cause: Error moving storage item, storage item already exists within the selected storage 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800168: Error moving storage item, cannot move storage item into itself.

Cause: Error moving storage item, cannot move storage item into itself.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800169: There is a badly defined table element in the web form. The block has been defined as repeating, but it has no table assigned to it.

Cause: There is a badly defined table element in the web form. The block has been defined as repeating, but it has no table assigned to it.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800170: Encountered an unexpected end of the table. Cannot find close for repeat block.

Cause: Encountered an unexpected end of the table. Cannot find close for repeat block.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800171: An unmatched closing tag was encountered. The advanced element {0} is not properly closed by {1}.

Cause: An unmatched closing tag was encountered. The advanced element is not properly closed.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800172: An IO error was encountered during the generation of the web form.

Cause: An IO error was encountered during the generation of the web form.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800173: There is no content for the web form file.

Cause: There is no content for the web form 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800174: Unable to access native web form file.

Cause: Unable to access native web form 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800175: Content '{0}' file name does not match with previous revisions.

Cause: Content file name does not match with previous revisions.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800176: Unable to access system folders.

Cause: Unable to access system folders.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800177: Unable to force security on moved folder or content.

Cause: Unable to force security on moved folder or content.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800178: Unable to retrieve folder information.

Cause: Unable to retrieve folder information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800179: Unable to retrieve folder.

Cause: Unable to retrieve folder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800180: Unable to update columns.

Cause: Unable to update columns.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800181: Unable to retrieve columns.

Cause: Unable to retrieve columns.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800182: Unable to retrieve administration configuration.

Cause: Unable to retrieve administration configuration.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800183: Unable to update administration configuration.

Cause: Unable to update administration configuration.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800184: Virtual folder name specifies invalid characters.

Cause: Virtual folder name specifies invalid characters.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800185: Unable to move items.

Cause: Unable to move items.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800186: Unable to delete items.

Cause: Unable to delete items.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800187: Unable to copy items.

Cause: Unable to copy items.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800188: Unable to create shortcut.

Cause: Unable to create shortcut.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800189: Unable to create virtual folder.

Cause: Unable to create virtual folder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800190: Unable to display virtual folder information.

Cause: Unable to display virtual folder information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800191: Unable to update virtual folder.

Cause: Unable to update virtual folder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800192: Unable to remove all content.

Cause: Unable to remove all content.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800193: Unable to restore items.

Cause: Unable to restore items.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800194: Unable to retrieve specified fields.

Cause: Unable to retrieve specified fields.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800195: Unable to update specified fields.

Cause: Unable to update specified fields.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800196: Unable to retrieve specified field defaults.

Cause: Unable to retrieve specified field defaults.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800197: Unable to update specified field defaults.

Cause: Unable to update specified field defaults.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800198: Unable to retrieve specified virtual folder.

Cause: Unable to retrieve specified virtual folder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800199: Unable to update specified virtual folder.

Cause: Unable to update specified virtual folder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800200: Unable to edit specified virtual folder.

Cause: Unable to edit specified virtual folder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800201: Unable to display virtual folder information.

Cause: Unable to display virtual folder information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800202: Unable to open folder.

Cause: Unable to open folder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800203: Unable to get reference.

Cause: Unable to get reference.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800204: Unable to move, destination is a subfolder.

Cause: Unable to move, destination is a subfolder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800205: Unable to add shortcut.

Cause: Unable to add shortcut.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800206: Unable to move shortcut.

Cause: Unable to move shortcut.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800207: Unable to copy shortcut.

Cause: Unable to copy shortcut.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800208: Reference is a ancestor of shortcut.

Cause: Reference is a ancestor of shortcut.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800209: Unable to load environment.

Cause: Unable to load environment.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800210: Unable to change login

Cause: Unable to change login

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800211:

Cause: Local Folder and Directory already 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800212:

Cause: Directory not empty.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800213: Unable to archive.

Cause: Unable to archive.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800214: The folder structure is locked.

Cause: The folder structure is locked.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800215: This folder cannot currently be changed.

Cause: This folder cannot currently be changed.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800216: Search Name could not be found

Cause: Search Name could not be found

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800217: Search text could not be found for validation

Cause: Search text could not be found for validation

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800218: Cannot perform an empty search

Cause: Cannot perform an empty search

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800219: SES does not support left-truncated wildcards

Cause: SES does not support left-truncated wildcards

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800220: SES does not support different criteria conjunctions

Cause: SES does not support different criteria conjunctions

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800221: SES does not support the '{0}' operator

Cause: SES does not support that operator

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800222: Permission denied to freeze federated items

Cause: Permission denied to freeze federated items

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800223: Archive does not contain a file for item '{0}'

Cause: Archive does not contain a file for that 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800224: 'xCategoryID' and 'xFolderID' cannot both be specified for item '{0}'

Cause: 'xCategoryID' and 'xFolderID' cannot both be specified for the 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800225: Cannot assign folder IDs to a non-record for item '{0}'

Cause: Cannot assign folder IDs to a non-record for the 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800226: Cannot edit frozen item

Cause: Cannot edit frozen 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800227: Cannot delete frozen item

Cause: Cannot delete frozen 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800228: Cannot delete frozen item or item is in frozen folders.

Cause: Cannot delete frozen item or item is in frozen folders.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800229: The external item was successfully deleted

Cause: The external item was successfully deleted

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800230: Unable to get external item information.

Cause: Unable to get external item information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800231: Unable to get external batch status details information.

Cause: Unable to get external batch status details information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800232: Unable to reset external batch status information.

Cause: Unable to reset external batch status information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800233: Notify External Batch Status Alerts

Cause: Notify External Batch Status Alerts

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800234: Unable to run external report

Cause: Unable to run external report

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800235: Error checking or creating WebDAV locks cache file.

Cause: Error checking or creating WebDAV locks cache 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800236: Not allowed to lock this folder through WebDAV.

Cause: Not allowed to lock this folder through WebDAV.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800237: Unable to perform lock. Lock request did not send owner information.

Cause: Unable to perform lock. Lock request did not send owner information.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800238: Unable to lock file. All locks must be requested as exclusive.

Cause: Unable to lock file. All locks must be requested as exclusive.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800239: Unable to lock file. Bad request.

Cause: Unable to lock file. Bad 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800240: Unable to undo checkout during lock cleaning cycle.

Cause: Unable to undo checkout during lock cleaning cycle.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800241: The requested location does not exist.

Cause: The requested location does 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800242: Infinity is not allowed. Please upgrade your web filter and restart the Content Server.

Cause: Infinity is not allowed. Please upgrade your web filter and restart 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800243: Unable to lock file at this path. Please use the tip-revision path.

Cause: Unable to lock file at this path. Please use the tip-revision 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800244: Unable to unlock file at this path. Please use the tip-revision path.

Cause: Unable to unlock file at this path. Please use the tip-revision 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800245: Unable to put file at this path. Please only use the tip-revision path of an existing file.

Cause: Unable to put file at this path. Please only use the tip-revision path of an existing 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800246: Unable to delete file at this path. Please use the tip-revision path.

Cause: Unable to delete file at this path. Please use the tip-revision 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800247: Could not send WebDAV XML to client.

Cause: Could not send WebDAV XML to client.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800248: Error getting owner from lock {0}. Please ensure that your XML libraries are properly installed.

Cause: Error getting owner from lock. Please ensure that your XML libraries are properly 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800249: Could not parse incoming WebDAV XML request.

Cause: Could not parse incoming WebDAV XML 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800250: Could not create WebDAV input stream from the DataBinder.

Cause: Could not create WebDAV input stream from the DataBinder.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800251: Could not get bytes from input stream.

Cause: Could not get bytes from 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800252: Folio item {0} not found

Cause: Folio item not found

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800253: Could not write folio {0}

Cause: Could not write folio

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800254: Unable to save changes.

Cause: Unable to save changes.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800255: Unable to edit folio template.

Cause: Unable to edit folio template.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800256: Unable to create new folio.

Cause: Unable to create new folio.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800257: Unable to create new folio template.

Cause: Unable to create new folio template.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800258: Unable to create new template folio.

Cause: Unable to create new template folio.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800259: Unable to load folio node.

Cause: Unable to load folio node.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800260: Unable to load temporary folio node.

Cause: Unable to load temporary folio node.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800261: Unable to load folio edit page.

Cause: Unable to load folio edit page.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800262: Unable to generate unique ids.

Cause: Unable to generate unique ids.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800263: Unable to create folio snapshot.

Cause: Unable to create folio snapshot.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800264: Unable to lock folio.

Cause: Unable to lock folio.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800265: Unable to load archived folio.

Cause: Unable to load archived folio.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800266: Previous revision of the folio does not exist.

Cause: Previous revision of the folio does 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800267: Unable to checkin archived folio item.

Cause: Unable to checkin archived folio 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800268: Unable to create folio from basket.

Cause: Unable to create folio from basket.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800269: Unable to clone folio.

Cause: Unable to clone folio.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800270: Folio parent node data missing.

Cause: Folio parent node data 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800271: This service cannot edit folio templates.

Cause: This service cannot edit folio templates.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800272: Could not add folio to archive.

Cause: Could not add folio definition to archive.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800273: Unable to edit locked folio.

Cause: Unable to edit locked folio.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800274: Error indexing folio links.

Cause: Error indexing folio links.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800275: Declassify On Date is not a valid date

Cause: Declassify On Date is not a valid date

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800276: Publication Date is not a valid date

Cause: Publication Date is not a valid date

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800277: Failed to check in '{0}' freeze audit information. Please reference '{1}' audit log.

Cause: Failed to check in freeze audit information. Please reference audit log.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800278: Unable to run disposition action.

Cause: Unable to run disposition action.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800279: Installing the RelatedContent component...

Cause: Installing the RelatedContent 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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error

UCM-CS-800280: Offsite FTP cannot change to the directory '{0}'. Please make sure it exists on the FTP site.

Cause: Offsite FTP cannot change direcotry.

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 entriesthat are part of this message stack.

Level: 1

Type: ERROR

Impact: Error