Error and warning messages for Content Integrator core functions cover services, the viewer and view services, Enterprise Java Beans, and integration.
COEM0006W:
Unable to log to file {0}.
Explanation: The specified
ResourceEntry is not defined.
COEM0007W: Required property
{0} is not defined.
Explanation: The specified property
is not defined.
COEM0008E: Error while loading properties
from file {0}.
Explanation: An input/output error occurred
while loading the specified property file.
User Response:
Turn on debug level, troubleshoot the errors based on error information,
and try again.
COEM0009W: File {0} does not exist. Configuring
services using JVM system properties.
Explanation: The
specified property file does not exist. The JVM system properties
will be used.
COEM0010W: No system property {0} specified.
Configuring services using JVM system properties.
Explanation:
The given system property was not specified. The JVM system properties
will be used.
COEM0012E: Port {0} specified by property {1}
is not a valid RMI port number.
Explanation: The port
number specified by the given property is not a valid RMI port number.
User
Response: Turn on debug level, troubleshoot the errors based on error
information, and try again.
COEM0013W: Service {0} is already
stopped.
Explanation: The specified service has already
stopped.
COEM0015E: Error stopping {0}.
Explanation:
Error occurred while stopping the specified service.
User
Response: Turn on debug level, troubleshoot the errors based on error
information, and try again.
COEM0016E: Error stopping registry.
Explanation:
Error occurred while stopping the registry.
User Response:
Turn on debug level, troubleshoot the errors based on error information,
and try again.
COEM0017E: Service {0} was never initialized.
Call init(Properties props) first.
Explanation: The specified
service was not initialized. Please call init(Properties props) first.
User
Response: Call call init(Properties props) first, and try again.
COEM0018W:
Service {0} is already started.
Explanation: The specified
service has already started.
COEM0020E: Error starting the
RMI registry on port {0}.
Explanation: Error occurred
while starting the RMI registry on the specified port.
User
Response: Turn on debug level, troubleshoot the errors based on error
information, and try again.
COEM0022E: Unable to change RMI
registry port to {0}. Please restart the Services Monitor.
Explanation:
The RMI registry port cannot be changed to the specified port number
because the RMI registry had been started on different port.
User
Response: Please restart the Services Monitor.
COEM0023E:
Error starting {0}.
Explanation: Error occurred while
starting the specified service.
User Response: Turn on
debug level, troubleshoot the errors based on error information, and
try again.
COEM0024W: {0} is not started.
Explanation:
The specified service name was not started.
COEM0025W: Parameter
{0} was not defined.
Explanation: The specified parameter
was not defined.
COEM0029E: No single sign-on server URL specified.
Explanation:
The system property "vbr.sso.server.rmiurl" is required to define
the SSOServer.
User Response: Ensure that the system
property "vbr.sso.server.rmiurl" is defined and valid.
COEM0030E:
No single sign-on authenticator specified.
Explanation:
The system property "vbr.sso.authenticator" is required to define
the SSOServer.
User Response: Ensure that the system
property "vbr.sso.authenticator" is defined and valid.
COEM0037W:
Error while shutting down session pool server {0}.
Explanation:
Error occurred while shutting down the specified session Pool Server.
User
Response: Turn on debug level, troubleshoot the errors based on error
information, and try again.
COEM0038W: Error while unbinding
session pool server {0}.
Explanation: Error occurred
while unbinding the specified session Pool Server.
User
Response: Turn on debug level, troubleshoot the errors based on error
information, and try again.
COEM0039W: Error while unexporting
session pool server {0}.
Explanation: Error occurred
while unexporting the specified session Pool Server.
User
Response: Turn on debug level, troubleshoot the errors based on error
information, and try again.
COEM0040E: Error while parsing
the polling period.
Explanation: Error occurred while
parsing polling period
User Response: Turn on debug level,
troubleshoot the errors based on error information, and try again.
COEM0041E: Explicit URLs specified, but the names and URL lists do not match.
COEM0042E: Either {0} or {1} must be specified.
{0},
{1} = property name
Explanation: It requires either
"vbr.services.registryport" or "vbr.session.pool.urls" property to
be specified to initialize the session pool.
User Response:
Provide the correct properties and try again.
COEM0047E: No
logging server URL specified.
Explanation: The system
property "vbr.log.server.rmiurl" is required to define the logging
server.
User Response: Ensure that the system property
"vbr.log.server.rmiurl" is defined and valid.
COEM0050E: No
configuration server URL specified.
Explanation: The
system property "vbr.configuration.server.rmiurl" is required to define
the configuration Server.
User Response: Ensure that
the system property "vbr.configuration.server.rmiurl" is defined and
valid.
COEM0051E: No configuration file name specified.
Explanation:
The system property "vbr.configuration.server.filename" is required
to define the configuration Server.
User Response: Ensure
that the system property "vbr.configuration.server.filename" is defined
and valid. COEM0052W: The specified configuration file {0} does not
exist.
COEM0054E: No RMI bridge server URL specified
Explanation:
The system property "vbr.ejb.bridge.rmibridge.rmiurl" is required
to define the RMI bridge Server.
User Response: Ensure
that the system property "vbr.ejb.bridge.rmibridge.rmiurl" is defined
and valid.
COEM0069E: The value for the property {0} should be specified as a numerical value. The value was specified as {1}. The default value of 0 will be used.
COEM0070W:
A stream server host was not specified for this RMI bridge. A default
value: "{0}" will be used.
Explanation: A stream server
host was not specified in the RMI bridge script.
User
Response: To specify a host, set the system property "vbr.ejb.bridge.rmibridge.streamserver.host".
COEV0002E: The viewer could not log
in to the repository: {0}
User Response: The user should
verify that the repository name/id is correct, and that it is being
populated correctly on the request.
COEV0003E: Not logged
in.
User Response: User should check that the repository
user and password are correct in the location it must be defined for
the specific instance.
COEV0004E: An error occurred while displaying image for cached content: {0}
COEV0005E: An error occurred while displaying the image.
COEV0006E: An error occurred while saving viewer annotations.
COEV0007E: An error occurred while logging out of the repository.
COEV0008E: An error occurred
while displaying the image for content ID: {0}
Explanation:
This error is shown if there was an error displaying NON-cached content.
User
Response: The user should make sure that content id and repository
information is correct. There may be a problem with repository retrieval
if this persists.
COEV0010E: An error occurred in the Servlet:
{0}
Explanation: A Servlet being used for processing
in the viewer did not process correctly.
User Response:
The user should verify that the backing server instance of IBM Content
Integrator is currently up and able to handle Servlets.
COEV0011E:
The Servlet response did not have the correct object format, which
is an object type of ViewerMessage.
Explanation: The
Servlet did not return the expected response in the form of a Viewer
Message, but the mimeType of "application/octet-stream" was correct.
User
Response: This points to an underlying integration problem with all
servlet responses. An administrator should be contacted.
COEV0012E: The Servlet response was invalid.
COEV0045E: The viewer could
not find a viewable file in the image cache: {0}
Explanation:
Either the file is not an image file or the file has been deleted
off the temporary location
User Response: Make sure that
the file is an image file. If it is, you need to reload it.
COEV0046E:
The viewer could not create a temporary directory at the following
location: {0}
Explanation: the user of the client machine
may have incorrect security rights to change the specified directory.
User
Response: User should contact an administrator in order to identify
if the problem is with the client machine.
COEV0047E: The viewer could not create local temporary image cache at the following location: {0}
COEV0051E: Servlet could not locate the cached
repository object in session with key: {0}
Explanation:
Either the repository information given was incorrect, or the repository
is unavailable.
User Response: Check the repository
information and/or status of repository availability.
COEV0052E:
Servlet could not locate the cached content object in session with
key: {0}
Explanation: Either the content id information
given was incorrect, or the content is unavailable.
User
Response: Check the content id and ensure it is correct and exists.
COEV0053E: Servlet could not find cached user object.
Explanation:
User object is unavailable because it was either deleted or does not
exist.
User Response: Ensure the Content Integrator server
is up and that the user with the given id exists.
COEV0054E:
Servlet could not retrieve repository {0} from the cached user object.
Explanation: Either the repository information given
was incorrect, or the repository is unavailable.
User
Response: Check the repository information and/or status of repository
availability.
COEV0057E: Servlet was missing the repository
parameter that is required for login.
User Response:
The user or application invoking this Servlet must include a repository
parameter.
COEV0059E: Servlet could not find temporary file.
Explanation:
This Servlet (ViewTempFile) did not have a valid temporary file specified.
User
Response: Make sure that correct permissions are set so that the process
putting the temp file location has read/write access to do it.
COEV0060E:
Servlet could not send file. {0}
Explanation: There was
an IOException that occurred when writing the file to the Servlet
response stream. Parameter is the detailed exception message.
User
Response: Either try same process again, or resolve IO conflicts that
may be inhibiting the Servlet from processing.
COEV0061E:
The system property vbr.home must be set to a valid installation directory.
Servlet cannot locate a session temporary directory.
Explanation:
There was an IOException that occurred when writing the file to the
Servlet response stream. Parameter is the detailed exception message.
User
Response: Either try same process again, or resolve IO conflicts that
may be inhibiting the Servlet from processing.
COEV0062E:
Cannot locate a session temporary directory. {0} does not exist.
Explanation:
There was an IOException that occurred when writing the file to the
Servlet response stream. Parameter is the detailed exception message.
User
Response: Either try same process again, or resolve IO conflicts that
may be inhibiting the Servlet from processing.
COEV0063E:
Servlet could not find the file: {0}.
Explanation: The
file does not exist.
User Response: Either try same process
again, or resolve IO conflicts that may be inhibiting the Servlet
from processing.
COEV0081E: Could not set system default font. Accessibility may be affected.
COEV0082E: Error updating open button title.
COEV0083E: Error getting annotation stream.
COEV0084E: Unsupported Content Integrator annotation encountered.
COEV0085E: A MIME type is not defined for the content. If the content is in a repository, set the MIME type property in the repository. If the content is in the file system, set the filename extension.
COEV5001E: The compressed
native content for {0} did not contain a file named {1}.
Explanation:
{0} is a content id and {1} is the file that is to be converted name.
User
Response: Ensure that the compressed content is valid. If so, internal
error has occurred.
COEV5002E: An error occurred while writing
the native content {0} to {1}.
Explanation: {0} is content
id and {1} is the file that is to be converted name.
User
Response: Check permissions on the file system that this native content
is being written.
COEV5003E: The content converter returned
a null file when trying to convert the content in file {0}.
Explanation:
The converter returned a null because the file was not properly converted.
{0} is the name of the file that was to be converted.
User
Response: Check that the content is valid. If so, internal error has
occurred.
COEV5004E: An error occurred while compressing the
content in {0}.
Explanation: {0} is the conversion directory.
User Response: Check that the directory was not deleted
or unavailable.
COEV5005E: An unexpected error occurred. Check
the information logs for stack trace information.
Explanation:
This is a catch-all type exception.
User Response: Should
contact administrator who will have access to the exception logs.
COEV5006E: {0} is not a valid image processor filter.
Explanation:
{0} is a filter name.
User Response: Make sure this is
a valid image processor. Have Administrator ensure the settings in
the View Services configuration are correct.
COEV5007E: No
temporary directory is specified in the View Services configuration.
Explanation:
The temp directory property is not properly set in the Admin tool.
User
Response: User will have to contact the Administrator of View Services
and have a temporary directory put in place.
COEV5008E: The
temporary directory name provided for View Services is not valid.
The temporary directory path is: {0}.
Explanation: The
temp directory property is set to an invalid temp directory in the
Admin tool.
User Response: User will have to contact
the Administrator of View Services and have a valid temporary directory
put in place.
COEV5009E: Cannot write to the temporary directory
for View Services. The temporary directory path is: {0}.
Explanation:
The temp directory property is set to atemp directory that has inadequate
security permissions set in the Admin tool.
User Response:
User will have to contact the Administrator of View Services and have
writable access provided on the temp directory.
COEV5010E:
No default content converter specified in the View Services configuration.
Explanation:
No default converter was specified in the View Services configuration.
User
Response: User will have to contact the Administrator of View Services
to understand if a default converter can be provided.
COEV5011E:
Could not find a valid View Services configuration for content converter
{0}.
Explanation: {0} is the converter name.
User
Response: Make sure this is a valid content converter. Have Administrator
ensure the settings in the View Services config are correct.
COEV5012E:
Converter {0} does not have a valid license. Contact an IBM sales
representative or IBM technical support for more information.
Explanation:
The converter trying to be used is not properly licensed.
User
Response: Contact an IBM sales representative or technical support
for more information.
COEV5013E: No content converter factory
class is available for content converter {0}.
Explanation:
This is probably a View Services configuration problem.
User
Response: Contact Administrator to set up the proper factory class
and relay that information back to the user.
COEV5014E: The
content converter factory class {0} does not implement the com.venetica.vbr.ejb.view.IConverterFactory
interface.
Explanation: This is programming error. {0}
is the factory class name.
User Response: Administrator
should know who created the converter. Converter should be developed
according to the interface guidelines.
COEV5015E: View Services
could not create an instance of content converter factory class {0}.
Explanation:
{0} is the factory class name.
User Response: Administrator
should know who created the converter. Converter should be developed
according to the interface guidelines.
COEV5016E: View Services
could not create an instance of content converter factory class {0}.
The class was not found.
Explanation: {0} is the factory
class name.
User Response: Administrator should know
who created the converter. Converter should be developed according
to the interface guidelines.
COEV5017E: No image processor
was provided for the MIME type {0}.
Explanation: This
is going to be a configuration problem. {0} is the mime type.
User
Response: Have Administrator check that the mime type shown has an
image processor assigned to it.
COEV5018E: Could not find
a valid View Services configuration for image processor {0}.
Explanation:
{0} is the image processor name.
User Response: Make
sure this is a valid image processor. Have Administrator ensure the
settings in the View Services config are correct.
COEV5019E:
Processor {0} does not have a valid license. Contact an IBM sales
representative or IBM technical support for more information.
Explanation:
The image processor trying to be used is not properly licensed.
User
Response: Contact an IBM sales representative or technical support
for more information.
COEV5020E: No image processor factory
class was provided for image processor {0}.
Explanation:
This is probably a View Services configuration problem.
User
Response: Contact Administrator to set up the proper factory class
and relay that information back to the user.
COEV5021E: Image
processor factory class {0} does not implement the com.venetica.vbr.ejb.view.IImageProcessorFactory
interface.
Explanation: This is programming error. {0}
is the factory class name.
User Response: Administrator
should know who created the image processor. The image processor should
be developed according to the interface guidelines.
COEV5022E:
View Services could not create an instance of content converter factory
class {0}. See information log for exception details.
Explanation:
{0} is the factory class name.
User Response: Administrator
should know who created the image processor. The image processor should
be developed according to the interface guidelines.
COEV5023E:
View Services could not create an instance of content converter factory
class {0}. The class was not found.
Explanation: {0}
is the factory class name.
User Response: Administrator
should know who created the converter. Converter should be developed
according to the interface guidelines.
COEV5024E: An error
occurred while trying to convert {0}.
Explanation: {0}
is the name of the file being converted.
User Response:
This is a catch-all type exception and should be investigated by an
Administrator.
COEV5025E: An error occurred while trying
to read the file {0}.
Explanation: {0} is the name of
the file being read.
User Response: The file may be corrupt.
If no identifiable error is found, contact an Administrator.
COEV5026E:
An error occurred while trying to scale the image to gray. Error code:
{0}.
Explanation: {0} is the error code from the underlying
API call.
User Response: This is an internal error with
the image processor and in unresolvable by the user.
COEV5027E:
An error occurred while trying to scale the image. Error code: {0}.
Explanation:
{0} is the error code from the underlying API call.
User
Response: This is an internal error with the image processor and in
unresolvable by the user.
COEV5028E: An error occurred while
trying to rotate the image. Error code: {0}.
Explanation:
{0} is the error code from the underlying API call.
User
Response: This is an internal error with the image processor and in
unresolvable by the user.
COEV5029E: An error occurred while
trying to adjust the image brightness. Error code: {0}.
Explanation:
{0} is the error code from the underlying API call.
User
Response: This is an internal error with the image processor and in
unresolvable by the user.
COEV5030E: An error occurred while
saving the converted file {0}. Error code: {1}
Explanation:
{0} is the converted file name. {1} is the internal error code thrown
from the underlying API call.
User Response: Administrator
should examine stack trace information and error code in order to
diagnose and resolve the issue.
COEV5031E: An error occurred
while trying to determine the maximum image dimensions.
Explanation:
This would happen if the max image height or width integers are invalid.
User
Response:
User Response: Administrator must ensure that
the maxImageHeight & maxImageWidth are set to valid values in
the View Services configuration.
COEV5032E: An error occurred
while trying to process {0}.
Explanation: {0} is the
name of the file being processed. This file could not be processed
correctly.
User Response: Make sure that the file that
was passed is a valid file. If it is, then there must be an internal
image processor error.
COEV5033E: The image processor could
not find maxImageWidth property.
Explanation: (self-explanatory)
"maxImageWidth" is a property whose name will not translate. It must
remain as-is.
User Response: Administrator must ensure
that the maxImageWidth is set in the View Services configuration.
COEV5034E:
The image processor could not find maxImageHeight property.
Explanation:
(self-explanatory) "maxImageWidth" is a property whose name will not
translate. It must remain as-is.
User Response: Administrator
must ensure that the maxImageHeight is set in the View Services configuration.
COEV5035E: The initialization file provided for property {0}
does not exist or could not be read.
Explanation: {0}
is the name of the property for the initialization file.
User
Response: View Services administrator must provide a valid initialization
file.
COEV5036E: No HTML converter was provided for property
{0}.
Explanation: The HTML converter specified in the
property {0} was empty or invalid.
User Response: View
Services administrator must provide a valid initialization file.
COEV5037E:
The HTML converter provided for property {0} does not exist.
Explanation:
A property {0} needed to determine the HTML converter location is
not present.
User Response: View Services administrator
must provide a valid initialization file.
COEV5038E: No PDF
converter was provided for property {0}.
Explanation:
The PDF converter specified in the property {0} was empty or invalid.
User
Response: View Services administrator must provide a valid initialization
file.
COEV5039E: The PDF converter provided for property {0}
does not exist.
Explanation: A property {0} needed to
determine the PDF converter location is not present.
User
Response: View Services administrator must provide a valid initialization
file.
COEV5040E: An error occurred while converting {0}.
Explanation:
{0} is the file being converted.
User Response: User
should contact an administrator.
COEV5041E: The HTML converter
did not produce an output HTML file from file {0}.
Explanation:
For some reason the file {0} could not be converted to an HTML ready
format.
User Response: This is an internal converter
error that could have many causes. An Administrator should be contacted.
COEV5042E: The HTML converter cannot process images.
Explanation:
This means that the processContent() API method cannot be handled
by this converter.
User Response: View Services administrator
should specify an image processor for the image.
COEV5043E:
The PDF converter did not produce an output PDF file from file {0}.
Explanation:
For some reason the file {0} could not be converted to a PDF format.
User
Response: This is an internal converter error that could have many
causes. An Administrator should be contacted.
COEV5044E: The
PDF converter cannot process images.
Explanation: This
means that the processContent() API method cannot be handled by this
converter.
User Response: View Services administrator
should specify an image processor for the image.
COEV5045E:
The configuration file for content converter cannot be read.
Explanation:
An internal error signifying that the content converter configuration
file is unreadable.
User Response: This is not administered
by the View Services administrator, and may require a reinstallation
of IBM Content Integrator if this file has been corrupted.
COEV5046E:
An internal PDF converter error occurred: {0} {1}.
Explanation:
This is a generic message that is used to catch any errors not known
at design time.
Parameter:{0} is the status code returned
from the PDFConverter. {1} is a placeholder for any other needed variable.
COEV5047E: An internal HTML converter error occurred: {0}
{1}.
Explanation: This is a generic message that is used
to catch any errors not known at design time.
Parameter:{0}
is the status code returned from the HTMLConverter. {1} is a placeholder
for any other needed variable.
COEJ0002E: A remote exception occurred.
COEJ0003E: An unexpected error occurred.
COEJ0004E:
The repository {0} is not configured.
Parameter {0} :
Name of the repository
COEJ0005E: The query object is null.
COEJ0006E: The federated content query object is null.
COEJ0007E: The federated content query object does not contain any repositories.
COEJ0011E: An error occurred while instantiating an internal federated content query agent.
COEJ0012E: An error occurred while running the federated content query agent.
COEJ0013E: The root folder returned from the repository {0} with logon ID {1} was null.
COEJ0014E: The root work queue returned from the repository {0} with logon ID {1} was null.
COEJ0015E: Result {0} was null.
Parameter
{0}: Result number
COEJ0016E: Null content was returned from folder {0} of repository {1}.
COEJ0017E: The item finder object is null.
COEJ0018E: The content ID returned from creating a new item in repository {0} is null or empty.
COEJ0019E: The URL returned is null or empty.
COEJ0020E: A null result was returned when getting folder IDs in which content {0} is located from the repository {1}.
COEJ0021E: A null result was returned when getting property descriptions for content {0} from the repository {1}.
COEJ0022E: A null result was returned when getting annotations for content {0} from the repository {1}.
COEJ0023E: Data Map
{0} was not found.
Parameter {0} = Name of Data Map
COEJ0024E: The repository {0} is not used in the data map {1}.
COEJ0030E: The logon ID is null.
COEJ0031E: Logon ID {0} does not exist.
Parameter
{0} = URL for Configuration Server
COEJ0035E: The method Serializable customAction(Serializable) cannot be located on the connector instance.
COEJ0036E: An error occurred while executing the method Serializable customAction(Serializable) on the connector instance.
COEJ0037E: An error occurred while initializing the connector.
COEJ0038E: The user must be logged into the repository to perform this action.
COEJ0040E: An error occurred while initializing EJB {0}.
COEJ0042E: The query thread for repository {0} reported an error: {1}.
COEJ0043E: Attempted to set column data types with null array.
COEJ0044E: The column data types are set with arrays of different lengths.
COEJ0045E: The second argument to sort(int, Serializable) must implement java.util.Comparator.
COEJ0046E: Attempted to sort the result set with NULL comparator.
COEJ0047E: Bad bucket parameters are provided. You must have 0 <= starting Row <= ending Row <= maximum. The actual values are 0 <= {0} <= {1} <= {2}.
COEJ0048E: One or more null arguments were passed to the basic federated content query agent.
COEJ0049E: The query on repository {0} returned an exception: {1}.
COEJ0050E: An error occurred while loading the federated query transformer class {0}.
COEJ0051E: An error occurred when creating an instance of federated query transformer class {0}.
COEJ0052E: Class {0} is not a valid implementation of the federated query transformation SPI.
COEJ0053E: The federated query transformer class {0} instance is null.
COEJ0084E: This comparator can be used only to compare valid strings: first argument: {0}; second argument: {1}.
COEJ0085E: No logging information was defined.
COEJ0086E: The message {0} cannot be logged. No Logging Server URL was specified.
COEJ0087E: The message {0} cannot be logged to the logging server at {1}. The following error occurred: {2}.
COEO0001E: An error occurred
while initializing the Blowfish cipher.
Explanation:
A cipher that uses the Blowfish algorithm requires for initialization
either the name of the class containing the Blowfish encryption/decryption
key, or a byte array containing the Blowfish encryption/decryption
key.
User Response: Check the exception stack for details.
COEO0002E: The Blowfish initialization properties must include
either {0} or {1}.
Parameter {0}: "vbr.crypto.cipher.key.bytes"
(key bytes)
Parameter {1}: "vbr.crypto.cipher.key.file"
(relative or absolute key file path)
Explanation: The
initialization properties for this cipher are not valid. It must include
either "vbr.crypto.cipher.key.bytes" property for the key bytes or
"vbr.crypto.cipher.key.file" property for the key file.
COEO0003E:
An error occurred while processing bytes through the given cipher.
User
Response: Check the exception stack for details.
COEO0004E:
The class {0} cannot be loaded.
Parameter {0}: class
name
COEO0005E: The {0} method cannot be accessed.
Parameter
{0}: method name
COEO0006E: The {0} method cannot be invoked.
Parameter
{0}: method name
COEO0007E: Property {0} is not defined.
COEO0008E: An error occurred while initializing cipher class {0}.
COEO0009E: An error occurred while initializing digest class {0}.
COEO0010E:
The cipher class {0} cannot be found by using the current class loader
or context class loader.
Parameter {0}: class name
COEO0011E: An error occurred while creating MD5 digest. MD5Digest is a class name.
COEO0012E: A Blowfish cipher cannot be initialized by
using an instance of {0}.
Parameter {0}: the given object
class name.
Explanation: The specified object must be
either a string naming the Blowfish key class or a byte array containing
the key.
User Response: Ensure that the given object
is valid, and try again.
COEO0013E: Asymmetric ciphers are not supported.
COEO0014E: The specified key file {0} does not exist.
COEO0015E: The specified key file {0} cannot be opened.
COEO0016E:
A null input stream was passed to method {0}.
Parameter
{0}: a method name.
COEO0017E: An error occurred while reading the key.
COEO0018E: An error occurred while creating digest.
COEO0019E: HMACMD5 algorithm is not found.
COEO0030E: An error occurred while creating the access controller.
COEO0031E: An error occurred while initializing class {0}.
COEO0032E: {0} argument cannot
be null.
Parameter {0}: name of an input argument
COEO0040E: The object value cannot be converted to a Boolean value because the object is null.
COEO0041E: The object value {0} cannot be converted
to a boolean value. Specified object value must be either true or
false.
Explanation: The specified object value must be
either "true" or "false" to be converted to a boolean.
User
Response: Ensure that the given object value is valid, and try again.
COEO0042E: The object value cannot be converted to a Boolean data type because the data type is incompatible.
COEO0043E: The object value cannot be converted to an integer data type because the value is null.
COEO0044E: The object value {0} cannot be converted to an integer.
COEO0045E: The object value cannot be converted to an integer because the data type is incompatible.
COEO0046E: The object value cannot be converted to a float data type because the value is null.
COEO0047E: The object value {0} cannot be converted to a float data type.
COEO0048E: The object value cannot be converted to a float data type because the data type is incompatible.
COEO0049E: The object value cannot be converted to a double data type because the value is null.
COEO0050E: The object value {0} cannot be converted to a double data type.
COEO0051E: The object value cannot be converted to a double data type because the data type is incompatible.
COEO0052E: The object value cannot be converted to a long data type because the value is null.
COEO0053E: The object value {0} cannot be converted to a long data type.
COEO0054E: The object value cannot be converted to a long data type because the data type is incompatible.
COEO0055E: The string value {0} cannot be converted to a date.
COEO0056E: The object value cannot be converted to a date data type because the data type is incompatible.
COEO0057E: Key {0} does not exist in this category.
COEO0058E: Provide
the {0} or the {1} property.
Parameter {0}, {1}: property
name
COEO0059E: The {0} property value is not an instance
of {1}.
Parameter {0}: property name, {1}= class name
COEO0060E: The operation {0} is not supported.
COEO0061E: An error occurred
while loading properties from file {0}.
Parameter {0}:
file name
COEO0062E: The properties file {0} does not exist.
COEO0063E: The object value cannot be converted to a {0} data type because the data types are incompatible.
COEO0064E: The value {0} cannot be converted to type {1}.
COEO0101E: The entry from the LDAP search result cannot be created.
COEO0102E: The entry to LDAP cannot be added.
COEO0103E: The entry from LDAP cannot be removed.
COEO0104E: Attribute {0} cannot be updated in the LDAP entry.
COEO0105E: Attribute {0} cannot be added to the LDAP entry.
COEO0106E: Attribute {0} cannot be removed from the LDAP entry.
COEO0107E: The existence of this entry cannot be verified in LDAP.
COEO0108W: The value for attribute {0} cannot be retrieved.
COEO0109E: Cannot log in to LDAP server.
COEO0110W: The directory context cannot be closed.
COEO0111E: Cannot look up the entry in LDAP.
COEO0112E: The LDAP entry cannot be added. Ensure that your LDAP schema is set up correctly.
COEO0113E: The LDAP entry cannot be retrieved. Ensure that your LDAP schema is set up correctly.
