Error messages 

Use the codes included in the error messages generated by IBM Connections to identify problems and find their solutions.

The following error messages are generated by IBM Connections:

Table 1. IBM Connections error messages with codes

Message Cause Solution
CLFRPE: The installation of application {0} failed while creating WAS Variables. The installation failed while creating WAS Variables.

  1. Check the detailed error message in the log file.

  2. Find the root cause of error then try to fix it.

  3. Run the uninstaller to uninstall the application and then install the application again.

CLFRPE: The installation of application {0} failed while creating datasource. The installation failed while creating while creating datasource.

  1. Check the detailed error message in the log file.

  2. Find the root cause of error then try to fix it.

  3. Run the uninstaller to uninstall the application and then install the application again.

CLFRPE: The installation of application {0} failed while deploying application. The installation failed while deploying application.

  1. Check the detailed error message in the log file.

  2. Find the root cause of error then try to fix it.

  3. Run the uninstaller to uninstall the application and then install the application again.

CLFRPE: The installation of application {0} failed while doing server configuration. The installation failed while doing server configuration.

  1. Check the detailed error message in the log file.

  2. Find the root cause of error then try to fix it.

  3. Run the uninstaller to uninstall the application and then install the application again.

CLFRPE: The uninstallation of application {0} failed while removing WAS Variables. The uninstallation failed while removing WAS Variables.

  1. Check the detailed error message in the log file to find the root cause.

  2. Try to fix it and then uninstall the application.

CLFRPE: The uninstallation of application {0} failed while removing datasource. The uninstallation failed while removing datasource.

  1. Check the detailed error message in the log file to find the root cause.

  2. Try to fix it and then uninstall the application.

CLFRPE: The uninstallation of application {0} failed while uninstalling application. The uninstallation failed while uninstalling application.

  1. Check the detailed error message in the log file to find the root cause.

  2. Try to fix it and then uninstall the application.

CLFRPE: The uninstallation of application {0} failed while doing server configuration. The uninstallation failed while doing server configuration.

  1. Check the detailed error message in the log file to find the root cause.

  2. Try to fix it and then uninstall the application.

CLFNF6001E: Could not store portlet preferences. The portlet failed to save preferences to portal preferences store. It may be caused by incorrect permission settings granted by the administrator. Check if the user has permission to store preferences.
CLFNF6002E: Error storing slot id. The portlet failed to store user credentials in the portal credential vault. Check your portal credential vault configuration.
CLFNF6003E: There was an error with a name. Caused by: javax.naming.

NamingException when the portlet is trying to lookup Portal services (i.e. Puma service or Identification service).

Check your portal configuration to make sure Puma services and Portal Identification service are available.
CLFNF6004E: JSONTranslator could not modify portlet preferences. The portlet failed to save preferences to portal preferences store. It may be caused by incorrect permission settings granted by the administrator. Check if the user has permission to store preferences.
CLFNF6005E: There was an error with the portlet service. The server encountered an error when using Portal Puma services. Check your portal configuration to make sure puma services function correctly.
CLFNF6006E: Error creating credential. The portlet failed to create a private credential slot. Check your portal credential vault configuration.
CLFNF6007E: Name not found. The portlet failed to locate portal services. (i.e. Puma or Identification) Check your portal configuration to make sure puma services and Portal Identification are available.
CLFNF6008E: There was an error serializing an id. The portlet failed to serialize portlet window ID. Reinstall the portlet instance on the page, if the problem is consistent, check your portal configuration.
CLFNF6009E: Could not get custom views. The portlet failed to change the value for a read-only preference attribute. Check if the user has permission to store preferences.
CLFNF6010E: Query was stored in a bad format: {0}. The user used the character “|” in a custom search query or in a custom tag filter. Do not use “|” in a custom search query or in a custom tag filter.
CLFNF6011E: Error getting user credentials. The portlet encountered an error when attempting to retrieve user credentials from the Portal credential vault. Check the portal credential vault configuration.
CLFRA0001E: Viral content replaced. The virus scanner removed a virus from added content. No action necessary.
CLFRA0003E: Virus detected - <error>. The virus scanner received the error <error> scanning content. No action necessary. The content was not added to Activities.
CLFRA0006E: Unable to find CMAPI provider "<providerName>". Unable to find a suitable CMAPI provider. Check the <objectStore> settings in oa-config.xml and provide a correct <providerName> for the class property of the store element.
CLFRA0013E: unable to delete file <fileName>. An error occurred while deleting a file from the Activities content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the directory and file information is correct.
CLFRA0014E: unable to create file upload directory <directoryName>. The directory given in oa-config.xml for the element property name "root.directory" either could not be found or created. This directory is used for file uploads to the Activities content store. Check that the directory exists; create it if it does not exist.
CLFRA0015E: error encountered deleting content: <directoryName> <fileName>. An error occurred while deleting the contents of a file from the Activities content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the directory and file information is correct.
CLFRA0016E: unable to upload file: <directoryName> <fileName>. An error occurred while retrieving or uploading a file to the Activities content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the directory and file information is correct.
CLFRA0017E: Error closing statistics file. A file system error occurred closing one of the files used for Activities statistics persistence. Verify that the file system directory containing the statistics files is writable and has available space.
CLFRA0019E: Error creating statistics file. A file system error occurred creating one of the files used for Activities statistics persistence. Verify that the file system directory containing the statistics files is writable and has available space.
CLFRA0020E: Error parsing statistics file. The format of one of the files used for Activities statistics persistence is inconsistent with the expected format. Remove the existing files in the file system directory containing the statistics files.
CLFRA0021E: Activities statistics persistence cannot create directory <directory>. A file system error occurred creating the file system directory <directory> for containing the Activities statistics files. Verify that the server level WAS variable ACTIVITIES_STATS_DIR is set to a valid directory location on the server's file system; create the directory <directory> on the file system.
CLFRA0022E: Error saving to statistics file. A file system error occurred saving data one of the files used for Activities statistics persistence. Verify that the file system directory containing the statistics files is writable and has available space.
CLFRA0023E: Error saving summary information. A file system error occurred saving data one of the files used for Activities statistics persistence. Verify that the file system directory containing the statistics files is writable and has available space.
CLFRA0026E: Error fetching profiles. The MemberService wsadmin object received an exception executing a fetchMembers command. Verify that the parameter to the fetchMembers command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0028E: Error updating access control list. The AccessControlService wsadmin object received an exception executing an access modification command. Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0029E: Error fetching activities. The ActivityService wsadmin object received an exception executing a command to fetch Activities. Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0030E: Error fetching access control list. The AccessControlService wsadmin object received an exception executing a fetchAccess command. Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0032E: Error updating profile. The MemberService wsadmin object received an exception executing a updateMember command. Verify that the parameter to the updateMember command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0033E: Error purging trash. The TrashCollectionService wsadmin object received an exception executing a purgeTrash command. Verify that the parameter to the purgeTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0034E: Error fetching trash. The TrashCollectionService wsadmin object received an exception executing a fetchTrash command. Verify that the parameter to the fetchTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0035E: Error undeleting trash. The TrashCollectionService wsadmin object received an exception executing a undeleteTrash command. Verify that the parameter to the undeleteTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0036E: Error locating MBeanServer, no Activity Administration MBeans registered. An exception was generated when Activities tried to locate MBean server needed to register the Activities Administration MBeans. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0038E: Error registering mbean. An exception was generated when Activities tried to register the Activities Administration MBeans. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0042E: <className> error parsing generic properties into a Properties object. An exception was generated when the Event Broker tried to parse its configuration from oa-config.xml. Ensure the properties and elements for the <eventBroker> element in oa-config.xml are valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0043E: subscriber did not start: <className>. The Event Broker service is attempting to initialize a subscriber to server-generated events, but the subscriber initialization process failed. Check that the <eventBroker> configuration specified in oa-config.xml for the subscriber reporting this error is valid. Additionally, you may want to pursue the exception thrown by the subscriber in the SystemOut.log file.
CLFRA0044E: {0} the class "<className>" was not found. Check the configuration file, under the class attribute of the service for the correct Java™ classname. Or, check the classpath to make sure the class is visible. The Event Broker service tried to load a Java class that did not exist in the current classpath. Check to see whether the class specified in the <eventBroker> configuration has been spelled correctly. Also check to see that the class file is visible in the current classpath scope. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0045E: {0} the class "<className>" could not be instantiated. The classloader could not instantiate the class requested by the Event Broker service. Investigate whether something is wrong with the classloader or the class specified in the <eventBroker> configuration itself. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0046E: {0} illegal access exception for the class "<className>". The Event Broker service is trying to access fields or methods in the class discovered via reflection that it can't normally see. Additional information relating to the failure may be found in the SystemOut.log file. Examine the class for methods that should be exposed have been hidden.
CLFRA0047E: {0} error initializing adapter: classname= "{1}" Double-check the config settings for this specific adapter for correct/valid values. The Event Broker service is attempting to initializer a subscriber to server-generated events, but the subscriber initialization process failed. Check that the <eventBroker> configuration specified in oa-config.xml for the subscriber reporting this error is valid. Additionally, you may want to pursue the exception thrown by the subscriber in the SystemOut.log file.
CLFRA0048E: could not inform a subscriber of event: <eventName>. The Event Broker service passed an event to a subscriber of that event, and the subscriber issued an exception. To fix this class of exception, you need to determine what is failing in this particular subscriber. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0050E: Invalid oa-config.xml file. Check the XML format and ensure that all required settings are complete. The format of oa-config.xml does not have correct XML syntax. Load the oa-config.xml into a browser or editor that will display syntax errors; fix the error and save the file.
CLFRA0051E: Error decoding passwords. If passwords are encoded, some functionality may fail. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0068E: {0} OpenActivitiesException while updating node content ref uuid. An error occurred while updating the content of the specified activity. Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
CLFRA0070E: Illegal access exception for the class "<className>". An error occurred while processing the Activities content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the <objectStore> configuration information in oa-config.xml is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0071E: {0} DaoException while updating node content ref uuid=<uuid>. An error occurred while updating the content of the specified activity. Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
CLFRA0072E: activities object store did not start: <className>. The Activities Object Store service implemented by <className> did not start. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the <objectStore> configuration information in oa-config.xml is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0073E: {0} Destination ObjectStore ID="<id>" not found in ObjectStore registry. Double-check the oa-config.xml file. An error occurred while transferring Activities content from one content store to another. The requested destination object store identifier was not found. Check the spelling of the ID used and compare it with the available object stores listed in the oa-config.xml file.
CLFRA0074E: ObjectStoreFilter error during activities object store content filtering "<error>". An error occurred while processing Activities content. Additional information relating to the failure may be found in the SystemOut.log file. Depending on the additional error information given, it may be possible to correct the data and re-process it.
CLFRA0075E: Premature invocation before transfer is complete. Check busy() method or listen for completion event. An error occurred while transferring Activities content from one content store to another. The transfer utility may already be carrying out a transfer. Attempt this operation after the other transfer is complete.
CLFRA0076E: <error> Exception while retrieving activities collection. An error occurred while transferring Activities content from one content store to another. Check that the content stores are available and accessible.
CLFRA0077E: ObjectStoreConfigLoader: the class "<className>" could not be instantiated. An error occurred while processing the Activities content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the <objectStore> configuration information in oa-config.xml is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0078E: Source ObjectStore ID="<id>" not found in ObjectStore registry. Double-check the oa-config.xml file. An error occurred while transferring Activities content from one content store to another. The requested source object store identifier was not found. Check the spelling of the ID used and compare it with the available object stores listed in the oa-config.xml file.
CLFRA0079E: {0} error initializing adapter: classname= "{1}" Double-check the config settings for this specific adapter for correct/valid values. An error occurred while processing the Activities content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the configuration information for the object store is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0080E: ObjectStoreConfigLoader: missing id for activities object store class "<className>". An error occurred while loading the Activities content store configuration. Verify that the configuration information for the object store is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0081E: EventBrokerConfigLoader: the class "<className>" was not found. Check the configuration file, under the class attribute of the service for the correct Java classname. Or, check the classpath to make sure the class is visible. An error occurred while processing the Activities content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the configuration information for the object store is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0082E: Unable to access content reference for ACTIVITYUUID=<uuid>, NODEUUID=<uuid>, CONTENTREFUUID=<uuid>. An error occurred while transferring the content of the specified activity from one content store to another. Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
CLFRA0084E: error terminating activities object store. An error occurred while terminating the Activities content store. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0085E: Activities Schema Version Mismatch. Current database schema version is <version>. Activities requires version <version>. The system is expecting a certain schema version on the database. However, the database is reporting it has a different version. Upgrade the Activities' codebase, or upgrade the database schema to match.
CLFRA0087E: The content of mime type: "<type>" or filename: "<fileName>" you tried to upload exceeded the size limit of <integer> bytes. Talk to your administrator about increasing the permitted upload size. The administrator set a size limit for the type of content a user tried to upload, either by mime type or by filename. Change the upload limits in the <sizeLimits> element in oa-config.xml or upload something smaller.
CLFRA0088E: A profile provider error has occurred. <error> Activities received an error querying the directory (i.e. LDAP) for a user or group. Ensure that the LDAP server configured for the WAS is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
CLFRA0090E: profile provider error. Activities received an error querying the directory (i.e. LDAP) for a user or group. Ensure that the LDAP server configured for the WAS is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
CLFRA0091E: internal error. Activities generated an exception. If the problem persists after restarting the Activities application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0092E: A short description could not be generated because the entry contains invalid HTML. Clicking on [more] will display the full description. The service tried to clean up user-submitted HTML rich text input using the JTidy library. The HTML was so malformed that JTidy could not clean it, and produced a null result. This error is a message printed to the user that indicates the service could not truncate the input HTML to produce a summary for display in the entry. The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
CLFRA0093E: exception while executing JTidy on node: <uuid>. The service tried to clean up user-submitted HTML rich text input using the JTidy library. JTidy failed to finish executing on this HTML code before throwing an exception. The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
CLFRA0094E: output from JTidy execution: <html>. This is a trace message that explains why JTidy failed to process some HTML input. This exception trace will inform you on how JTidy failed and whether it could be fixed.
CLFRA0095E: internal error while executing JTidy on node: <uuid>. The service tried to clean up user-submitted HTML rich text input using the JTidy library. The HTML was so malformed that JTidy could not clean it, and produced a null result. The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
CLFRA0096E: Error fetching deleted items to purge. The scheduled TrashAutoPurge job received an exception fetching the items to purge. Restart the Activities application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0102E: Error closing email connections. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0105E: Error purging deleted items. The scheduled TrashAutoPurge job received an exception purging items. Restart the Activities application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0106E: Error sending notify message. Error when trying to send an email notification. Ensure that SMTP server configuration in the <email> element of notification-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0107E: Error composing HTML email message. Error received when trying to create an outbound email message from the server. Restart the Activities application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0108E: EmailNotifier: problems sending email. The most probable cause is due to using an invalid recipient email address. Or, the connection to the host is down. Or, there could also be authentication problems. Check the username and password settings. Error received when trying to send outbound emails. Ensure that SMTP server configuration in the <email> element of notification-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0109E: Malformed email template, url=<url>. The web address specified is in an invalid URL syntax/format. Check oa-config.xml, email/outbound/templates/url and make sure the URLs are valid. You can validate them by typing the URLs directly into a browser.
CLFRA0110E: Error sending error message. Error received when trying to send an email error notification. Ensure that SMTP server configuration in the <email> element of notification-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0111E: Unable to connect to any of the <number> SMTP servers found on the MX records of the DNS server. The SMTP server is down, unreachable, or not responding. Ensure that the SMTP and DNS servers configured in the <email> element of notification-config.xml are reachable.
CLFRA0112E: Unable to get email template from url= <url>. Error trying to retrieve an email template from the given URL. Check oa-config.xml, email/outbound/templates/url and make sure the URLs are valid. You can validate them by typing the URLs directly into a browser.
CLFRA0114E: The email from "<sender>" with subject "<subject>" did not match either the create or add-to matching address expressions. The email will be deleted and not processed. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0115E: The email address="<emailAddress>" was not found in the directory. Unable to process the message. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0116E: Unable to find a member profile for the email "<emailAddress>". This user will not be added to the activity membership. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0117E: The activity you tried to email into (id=<uuid>) is deleted or no longer exists. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0118E: You need to update your configuration file version. Make sure you are not trying to use an old config file on a newer server or vice-versa. The version of oa-config.xml on the server differs from the version expected by the Activities Application. Ensure the version property of the <config> element in oa-config.xml matches the version expected by the Activities Application.
CLFRA0119E: ExecutionContext leak detected. The Activities application has detected a resource leak. Restart the Activities application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0120E: Internal Error, EC Count is null. The Activities application has detected a resource leak. Restart the Activities application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0121E: Error publishing event <event>. The Activities application received an error from the Event Broker service. Check that the <eventBroker> configuration specified in oa-config.xml is valid. Correct an invalid configuration. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0122E: Cannot find credentials for <name>. The system is configured to use J2C Authentication Aliases to store authentication data. The entry for <name> is missing. Go to Secure administration, applications, and infrastructure -> JAAS -> J2C authentication data in the WAS Integrated Solutions Console, and check whether there is an entry for <name>. If there is no entry, create an Authentication Alias for <name> by completing these steps:

  1. Shut down the WAS.

  2. Edit the security.xml file in <APPServer_HOME>/profiles/AppSrv01/config/cells/<cell>

  3. Find the authDataEntries entry with an alias that includes <name>. For example: <authDataEntries alias="text/name"> 2.5

  4. Replace "text/name" with "name"

  5. Save the security.xml file.

  6. Restart the WAS.

If there is an entry for <name>, verify that the user credentials are correct. If these steps do not fix the problem, then contact Customer Support.

CLFRA0123E: Profile provider error. Activities received an error querying the directory (i.e. LDAP) for a user or group. Ensure that the LDAP server configured for the WAS is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
CLFRA0127W: Activities cannot determine host name. An error occurred while initializing the Statistics collection service. There was a problem with the server host name. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0131E: Activities Task Scheduler initialization error: <error>. Reason: An error occurred while initializing the Quartz scheduler. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0135E: Error executing event notification. Error received in the event broker. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0136E: Exiting the Async Notification Thread: event processing has been halted. Error received when the event broker thread is halted. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0137E: Error encountered processing events. Error received in the event broker when dispatching events. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0138E: The invoker should not be interrupted. Another thread interrupted the internal event broker. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0142E: Incorrect number of arguments. Please specify the configuration file to process. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0143E: Cannot locate configuration file {0}. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0144E: ConfigurationParser: Bad configuration. Config section defines more properties than values, or vice versa. Possible errant <property> element(s) without a "name" attribute(s). A configuration element in oa-config.xml or oa-jobs.xml is invalid. Enable debug tracing for com.ibm.openactivities.util, restart the application, and determine the invalid element from the trace.log output. Correct the element and restart the Activities application.
CLFRA0146E: Unable to refresh cached list of groups. Activities received an exception refreshing its group cache. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0147E: Error initializing Activities. The Activities application received an error trying to start. The cause of the error will be found in the SystemOut.log file. Correct the error cause and restart the Activities application.
CLFRA0270E: Error getting server URL for <name>. There was an error reading the server URL for the <name> service.

  1. Find the LotusConnections-config.xml file (in <App server home>/profiles/<name>/config/cells/<cell name>/LotusConnections-config)

  2. Make sure the files exists and is readable by the WAS process.

  3. Make sure the files contains the correct entry for the <name> service.

CLFRA0271E: Cannot find config variable directory <directory>. There was a problem reading variables that can be used in the oa-config.xml file. Make sure the directory exists and is readable by the WAS.
CLFRA0272E: Cannot find <file> for config variables. There was a problem opening a file getting configuration variables. Make sure the file exists and is readable by the WAS.
CLFRA0273W: Missing system setting for <name>. The IBM Connections configuration cannot find a definition for a variable named "name". Either, check the installation documentation for the variable to find the correct value for the variable, or add the variable with its correct value in the WAS admin console, Environment/websphere Variables page.
CLFRA0275E: Error loading config variables from <file>. There was a failure parsing variables in file.

  1. Make sure the file exists and is readable by the WAS.

  2. Replace the current copy with a back-up copy of the file.

CLFRA0276E: Too many errors occurred while sending Activity auto-completion notices. The auto-complete operation was aborted. The server has given up trying to keep sending any more auto complete email notices. Ensure that SMTP server configuration in the <email> element of notification-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0277W: Warning, invalid parameter specified for the Activity Auto Completion notification max errors ({0}). Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRA0278E: An error occurred while generating the list of activities eligible for auto completion. Error received querying the database to obtain a list of activities that qualify to be autocompleted. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0279E: Error sending auto-complete notification for activity UUID <uuid>. Error received when sending email about an auto complete notification. Additional information relating to the failure may be found in the SystemOut.log file. Ensure that SMTP server configuration in the <email> element of notification-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0280E: Error initializing the Activities Administrator email address. Some email functionality will not be available. No administrator email address was configured in oa-config.xml. Edit notification-config.xml and provide an administrator email address for the globalSenderEmailAddress property and optionally provide additional email addresses for different types of Activities notifications.
CLFRA0281E: The content of mime type: "<mimeType>" or filename: "<fileName>" you tried to upload is not allowed by your administrator. The administrator set a size limit of zero bytes for the type of content a user tried to upload, either by mime type or by filename. Change the upload limits in the <sizeLimits> element in oa-config.xml.
CLFRA0282E: The profile provider could not find information for member <uuid>. The Activities profile application did not find a member by the given member ID. Contact Customer Support to report the incident.
CLFRA0285W: Purge expiration period (days) either not specified or invalid (<integer>). Defaulting to {1} days. The trashRetentionInDays configured for the TrashAutoPurgeJob in oa-jobs.xml is invalid. Add a value greater than 0 for the trashRetentionInDays configuration. Otherwise, trash older than 1 day will be purged when the job runs.
CLFRA0286E: Error sending activity auto completion notification. Error received when trying to send an email auto-completion notification. Ensure that SMTP server configuration in the <email> element of notification-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0287E: Error parsing administrator email address. The administrator email address configured in oa-config.xml is badly formatted. Edit notification-config.xml and provide an administrator email address in the correct format in the <globalSenderEmailAddress> element.
CLFRA0288E: No Activities Administrator email address has been configured. You must specify a value for "globalSenderEmailAddress" or "sender" in the notification configuration file. The administrator email address configured in oa-config.xml is empty. Edit notification-config.xml and provide an administrator email address in the correct format in the <globalSenderEmailAddress> element.
CLFRA0289W: Content removed by active content filter. The active content filter removed active content from user input. No action necessary.
CLFRA0290E: Error starting the active content filter. The active content filter received an error on start up. Contact Customer Support to report the incident.
CLFRA0291E: Error encountered with the active content filter. The active content filter received an error trying to filter text. Contact Customer Support to report the incident.
CLFRA0292W: Warning, it appears the ACF inserted an invalid character mid stream (<filteredText>). The active content filter inserted an invalid character in the filteredText as part of a filtering operation. No action necessary. The Activities application fixes up the invalid character.
CLFRA0293E: A MemberProfile cannot be null. The data in a request to update a member profile in the database is null; possibly via a bad API request. Contact Customer Support to report the incident.
CLFRA0295E: Cannot update non-matching MemberProfiles. <uuid> is not <uuid>. In a request to one member profile with a new one, the member IDs do not match. Contact Customer Support to report the incident.
CLFRA0300E: The ArchiveService cannot export activities to the directory=<directory>; it is not writable. The exportActivities command of ArchiveService wsadmin object tried to archive Activities to a directory that is not writable. Ensure that <directory> exists and that it is writable by the WAS.
CLFRA0301E: The required zip file "Activity-<uuid>.zip" was not found. This activity will not be imported, or a related activity link will be broken. The ArchiveService was requested to import activity with uuid <uuid>. However, the directory path that was also given to the ArchiveService does not contain the file Activity-<uuid>.zip. Ensure that the directory specified in an ArchiveService importActivities or createActivities command contains the archives for the desired Activities.
CLFRA0304E: The version of the archive you tried to import does not match the current DB schema. One cannot import activities into servers that are using different DB schemas Migrate the archive to the matching schema version and then import the migrated archive.
CLFRA0306W: The user by email (or display name if it's a group) <member> was not found in the LDAP or the database! This means the activity being imported has a reference to a user that has changed emails, or has been removed from the LDAP. In other words, this email address is stale, and the activity is carrying around incongruent data. A member that was included in the imported activity cannot be found anymore. This might happen when switching LDAP servers, and the membership list is different. No action necessary. The imported activity will be imported, the missing member email address (or display name if a group) will be rewritten to "NOT_FOUND_<original emal>". If this behavior is unexpected, you might want to investigate why members are missing in the new LDAP.
CLFRA0309E: The ArchiveService cannot export activities to the directory=<directory>; it is not a directory. The exportActivities command of ArchiveService wsadmin object tried to archive Activities to a directory that is not writable. Ensure that <directory> exists and that it is writable by the WAS.
CLFRA0310E: Error writing activity entry #<uuid> to the database. An ArchiveService import error received at the point where the Node of the Activity is written. Additional information relating to the failure may be found in the SystemOut.log file. If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
CLFRA0312E: Error writing activity node to the database. An ArchiveService import error received at the point where one of the nodes (entries) of the Activity is written. Additional information relating to the failure may be found in the SystemOut.log file. If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
CLFRA0315E: The ArchiveService cannot create the directory=<directory> for exporting activities. In an ArchiveService exportActivities command one specifies a directory where all the archive files will be written. In this case, the system cannot write out the specified directory to the file system. Manually create the <directory> on the file system and ensure it is writable by the WAS.
CLFRA0318E: The related activity with UUID=<uuid> already exists in the system. It is unclear whether the intention is to overwrite that activity with old data or not. Thus, it will be not imported. When an activity has a related activity link in it, the ArchiveService will automatically try to import the related activity. However, if the ArchiveService is being run with "importActivities" which overwrites activities rather than creating copies, then, it is unclear to the system whether the administrator also intentionally meant to overwrite related activities since that related activity it was not explicitly passed in to be imported. If the administrator wishes to overwrite the related activity, he can use the ArchiveService importActivites command to overwrite the related Activity.
CLFRA0319E: Error writing activity content entry "<name>". An ArchiveService import error received at the point where the content (files, attachments, etc) of one of the nodes (entries) of the activity is written. Additional information relating to the failure may be found in the SystemOut.log file. If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
CLFRA0320E: Error importing activity with UUID=<uuid>. An ArchiveService import error. Additional information relating to the failure may be found in the SystemOut.log file. If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
CLFRA0321E: Error unpacking the archive. An ArchiveService import error received when unmarshalling the Zip archive. The Zip archive has been corrupted. If the cause of the corruption cannot be determined, contact Customer Support to report the incident.
CLFRA0327I: Status.
Informational message; no solution is needed.
CLFRA0328W: The <name> scheduler is not enabled in config. Check spelling. An attempt was made to start or stop a scheduler that is not enabled in the oa-config.xml file or is named differently than the name given in oa-config.xml. Enable the scheduler by changing the 'enabled' true/false setting. Ensure the scheduler name is spelled correctly.
CLFRA0329E: The attempt to start the <name> scheduler failed. The Quartz scheduler did not start. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0330W: The <name> scheduler has already been stopped. An attempt was made to stop a scheduler that is already stopped. Ensure that the scheduler is started before attempting to stop it.
CLFRA0331I: The request to resume job {0} has been submitted. The request to resume the specified job has been submitted. Informational message; no solution is needed.
CLFRA0332W: The job <name> is not valid for the {1} scheduler. An attempt was made to carry out an action on a job that is not running. Ensure that the job name is spelled correctly and that the job name is known to the system.
CLFRA0333I: The job {0} was removed. The specified job was removed from the scheduler. Informational message; no solution is needed.
CLFRA0334I: The {0} scheduler is running. The specified job is running. Informational message; no solution is needed.
CLFRA0335W: The job <name> is already running on the {1} scheduler. An attempt was made to resume a job that is already running on a scheduler. Ensure that the job is paused before attempting to resume it.
CLFRA0336I: The request to pause job {0} has been submitted. The request to pause the specified job has been submitted. Informational message; no solution is needed.
CLFRA0337W: The <name> scheduler has already been started. An attempt was made to start a scheduler that is already started. Ensure that the scheduler is stopped before attempting to start it.
CLFRA0338I: The {0} scheduler was stopped successfully. The specified scheduler was stopped successfully. Informational message; no solution is needed.
CLFRA0339W: The <name> scheduler is disabled in config. An attempt was made to start or stop a scheduler that is disabled in the oa-config.xml file. Enable the scheduler by changing the 'enabled' true/false setting.
CLFRA0340W: The request to pause job <name> failed. An error occurred while attempting to pause a job. Additional information relating to the failure may be found in the SystemOut.log file. No action is required.
CLFRA0341W: The job <name> has already been paused on the {1} scheduler. An attempt was made to pause a job that is already paused on a scheduler. Ensure that the job is running before attempting to pause it.
CLFRA0342I: The {0} scheduler is in standby mode. The specified scheduler is in standby mode. Informational message; no solution is needed.
CLFRA0343W: The request to resume job <name> failed. An error occurred while attempting to resume a previously paused job. Additional information relating to the failure may be found in the SystemOut.log file. No action is required.
CLFRA0344I: The {0} scheduler was started successfully. The specified scheduler started successfully. Informational message; no solution is needed.
CLFRA0345E: The attempt to stop the <name> scheduler failed. The Quartz scheduler did not stop. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Activities application, contact Customer Support to report the incident.
CLFRA0346I: The job {0} on the {1} scheduler has been paused. The specified job on the specified scheduler has been paused. Informational message; no solution is needed.
CLFRA0347E: Error exporting activity UUID={0}. An error occurred while trying to import the activity with the given UUID. Check previous log messages for the actual cause of the import failure. Resolve the error and re-run the import.
CLFRA0348W: The group "{0}" could not be loaded from LDAP or the database. Or, there might have been multiple matches for the same name in LDAP. This error is encountered when a group name is not found or multiple matches to the name are found in the configured directory. No action necessary. The activity will continue to be imported; an entry for "NOT_FOUND_" + the group name will be added to the member table and the membership list.
CLFRA0349E: Error locating profile: EXID mismatch, but email matches. email={0}, directory EXID={1}, db EXID={2}. This error is encountered when a member entry is found in the Activities database by the given email address, but the external identifier does not match the LDAP record. Determine if the person's record has changed in LDAP and if the two entries are really for the same person. If they are, use the Activities MemberService.

synchMemberExtId (email address) command to update the Activities database with the correct id.

CLFRA0350E: Error: the group profile "{0}" could not be located in the Activities database. This error is encountered during LDAP synchronization. The group could not be located in the Activities database. Check the spelling of the group name.
CLFRA0351E: Error: the group profile "{0}" could not be located in the directory service. This error is encountered during LDAP synchronization. The group found in the Activities database could not be located in LDAP. Check the spelling of the group name.
CLFRA0352I: The group profile "{0}" has been synchronized with the directory services changing the external id from {0} to {1}. This message is encountered during LDAP synchronization. This record in the Activities database has been updated to match LDAP. Informational message; no solution is needed.
CLFRA0353E: Error: the member profile "{0}" could not be located in the Activities database. This error is encountered during LDAP synchronization. The person could not be located in the Activities database. Check the spelling of the email address
CLFRA0354I: The member profile "{0}" has been synchronized with the directory services changing the external id from {0} to {1}. This message is encountered during LDAP synchronization. This record in the Activities database has been updated to match LDAP. Informational message; no solution is needed.
CLFRA0355I: The member profile "{0}" matches the directory service with external id {1}. This message is encountered during LDAP synchronization. This record is already synchronized. Informational message; no solution is needed.
CLFRA0356E: Error: the member profile "{0}" could not be located in the directory service. This error is encountered during LDAP synchronization. The person could not be located in LDAP. There is no match for the person by the given value. Check to see if the person exists in LDAP.
CLFRA0357E: Error: more than one profile was found with the key "{0}". Multiple entries identified by the <user identifier> have been found in the member profile table. One of the entries must be deleted. Contact Customer Support before proceeding.
CLFRA0358I: The group profile "{0}" matches the directory service with external id {1}. This message is encountered during LDAP synchronization. This record is already synchronized. Informational message; no solution is needed.
CLFRA0359E: Error locating member profile for <user identifier>, search type <internal search type>. The user's member profile could not be located in the directory. Verify the LDAP configuration is correct. If this error is limited to a specific user, verify the user can be located in LDAP given the identifier in the error message. The search type indicates what LDAP attribute is searched: 1=login, 2=email, 3=internal Activities member id (not used when searching LDAP).
CLFRA0360I: The {0} scheduler is not running. The specified scheduler is not running. Informational message; no solution is needed.
CLFRA0361E: The file "{0}" cannot be uploaded as it is a 0-byte file. An attempt was made to upload the specified file which has no content (zero bytes in size). Only files which have content may be uploaded. Ensure that the file contains data before uploading.
CLFRA0362E: FileSystem property name="use.historic" was not found in ObjectStore registry. Double-check the oa-config.xml file. The use.historic property is missing from the ObjectStore section of the oa-config.xml file. It must be present and must have a value of either true or false. Check the <objectStore> settings in oa-config.xml file and provide a correct value for the use.historic property of the <store> element.
CLFRA0363I: The Notification service for {0} is disabled in the configuration. No notification messages will be sent. The notification service for Activities is disabled in the configuration. This is an administrator controlled setting that is stored in the notification-config.xml configuration file. No action is required. The message is informational only.
CLFRA0364E: Error initializing the Notification service for {0}. No notification messages will be sent. Error details : {1}. An unexpected error occurred while initializing the notification service for Activities. This is most likely due to a configuration problem with the server or mail service. Verify that the mail service is configured properly. Additional information relating to the failure can be found in the SystemOut.log file.
CLFRA0365I: Activities Notification service started The notification service for Activities started successfully. This is normal. No action is required. The message is informational only.
CLFRA0366E: Activities Notification service initialization error: {0} An unexpected error occurred while initializing the notification service for Activities. This is most likely due to a configuration problem with the server or mail service. Verify that the mail service is configured properly. Additional information relating to the failure can be found in the SystemOut.log file.
CLFRA0367E: The date {0} is invalid; see documentation for acceptable date formats The date supplied as a parameter is invalid. This date was supplied to the request to fix up the content store after a restore from backup. This is a WSAdmin command task. Enter a date that is valid according to one of the documented acceptable formats.
CLFRA0368E: The folder {0} does not exist The folder path which was supplied as a parameter is invalid. Enter the path of a folder that exists.
CLFRA0369E: The attempt to fix up the content store failed : {0} An error occurred while attempting to fix up the contents of the file store after a restore from backup. Verify that the command was used properly and that the file system is accessible. Additional information relating to the failure can be found in the SystemOut.log file.
CLFRA0371E: Creation of the orphan folder {1} failed An error occurred while attempting to create the specified folder for orphaned files. Verify that the path for the folder exists and that the file system is accessible. Also verify that the user has write access to the file system. Additional information relating to the failure can be found in the SystemOut.log file.
CLFRA0372I: {0} content store files were moved to the orphan folder. Details are in the report file {1} in the folder {2}. Informational message. This message is a status report that is provided when the fix up utility task is used. No action is required. The message is for information only.
CLFRA0373E: The value {0} for the content store configuration is invalid. Check oa-config.xml The directory given in oa-config.xml for the <store> element property name root.directory either could not be found or accessed. This directory is used for file uploads to the Activities content store. Check that the directory exists. Create it if it does not exist.
CLFRA0374E: file: {0} already exists. While attempting to mark a file as "purged" for subsequent deletion, the file could not be marked since a file with that name already existed on the file system. This should not ordinarily happen. This is not a critical situation but could lead to extraneous files being left on the file system. The administrator can safely manually remove any files that the purge task fails to mark for deletion. Additional information relating to the failure can be found in the SystemOut.log file.
CLFRA0375E: error encountered while purging content: {0} {1}. An error occurred while attempting to remove content from the file store or mark the file for deletion. Additional information relating to the failure can be found in the SystemOut.log file. If the problem persists after restarting Activities, contact Customer Support to report the incident.
CLFRA0376E: unable to mark file: {0} for deletion. An error occurred while attempting to mark the specified file as "purged" for subsequent deletion. The file could not be marked for deletion from the file system. This should not ordinarily happen. This is not a critical situation but could lead to extraneous files being left on the file system. The administrator can safely manually remove any files that the purge task fails to mark for deletion. Additional information relating to the failure can be found in the SystemOut.log file.
CLFRA0377E: unable to purge file {0} {1}. An error occurred while attempting to mark the specified file as "purged" for subsequent deletion. The file could not be marked for deletion from the file system. This should not ordinarily happen. This is not a critical situation but could lead to extraneous files being left on the file system. The administrator can safely manually remove any files that the purge task fails to mark for deletion. Additional information relating to the failure can be found in the SystemOut.log file.
CLFRA0378E: The attempt to remove redundant files from the content store failed : {0} An error occurred while attempting to remove redundant files from the content store. The files could not be removed from the file system. This should not ordinarily happen. This is not a critical situation but could lead to extraneous files being left on the file system. The administrator can safely manually remove any files that the purge task fails to mark for deletion. Additional information relating to the failure can be found in the SystemOut.log file. Ensure that the referenced file exists and can be accessed. If the problem persists after restarting Activities, contact Customer Support to report the incident.
CLFRA0379I: {0} items were removed from {1} Informational message. This message is a status report that is provided when the historic file purge task is used. It reports how many files were successfully removed from the specified content store. No action is required. The message is informational only.
CLFRA0380E: The content store location is not a valid directory or is missing: {0} The file path specified in the oa-config.xml file for the root.directory property either could not be found or could not be accessed. This directory is used for file uploads to the Activities content store and must exist and be writeable. Check that the directory exists; create it if it does not exist.
CLFRA0381I: Removal of redundant files from content store started. The task that removes previously purged files from the file system has entered the running state. No action is required. The message is informational only.
CLFRA0382E: Unable to delete file {0} from the content store. The system security manager denied file delete access. An error occurred while attempting to delete a file from the content store. The file could not be removed from the file system since delete access to the file was denied by the system security manager. This should not ordinarily happen. Only processes with the appropriate access credentials should be attempting to delete files from the system. Any failure should be investigated by the system administrator to determine which process was attempting the unauthorized access. This is not a critical situation but could lead to extraneous files being left on the file system. Additional information relating to the failure can be found in the SystemOut.log file. Ensure that the referenced file exists and can be accessed. If the problem persists after restarting Activities, contact Customer Support to report the incident.
CLFRA0383E: The content store cleanup job only supports a file system object store. Store is {0}. Check oa-config.xml. The Activities content store must be a file system content store. No other type of content store is supported. Check in the oa-config.xml file for the store type and ensure that it refers to a FileSystemObjectStore.
CLFRA0384W: Unable to delete file {0} from the content store. Skipping this file. An error occurred while attempting to delete a file from the content store. The file could not be removed from the file system since the file delete operation failed. This should not ordinarily happen. This is not a critical situation but could lead to extraneous files being left on the file system. Ensure that the referenced file exists and can be accessed. The administrator can safely manually remove any files that the historic purge task fails to delete. Additional information relating to the failure can be found in the SystemOut.log file. If the problem persists after restarting Activities, contact Customer Support to report the incident.
CLFRA0385I: Removal of redundant files from content store stopped. The task that removes previously purged files from the file system has stopped. All files that are not referenced by the Activities system should now have been completely removed. No action is required. The message is informational only.
CLFRA0386E: The file does not exist. An error occurred while attempting to delete a file from the content store. The file could not be removed from the file system since it does not exist. This should not ordinarily happen. This is not a critical situation. Additional information relating to the failure can be found in the SystemOut.log file. Ensure that the referenced file exists and can be accessed. If the problem persists after restarting Activities, contact Customer Support to report the incident.
CLFRA0387E: The directory is not empty. An error occurred while attempting to remove a directory from the content store. The directory could not be removed from the file system since it contained at least one file. This should not ordinarily happen. This is not a critical situation. Additional information relating to the failure can be found in the SystemOut.log file. Ensure that the referenced directory exists and can be accessed and verify that the files contained in it are no longer needed by the Activities server. If they are no longer used, then files in that directory can be manually removed and the directory can be manually removed. If the problem persists after restarting Activities, contact Customer Support to report the incident.
CLFRA0388E: The file is read only. An error occurred while attempting to delete a file from the content store. The file could not be removed from the file system since it is read only. This should not ordinarily happen. Files in the Activities content store should be read-write so that they can be updated, moved or deleted by the Activities system. This is not a critical situation. Additional information relating to the failure can be found in the SystemOut.log file. Ensure that the referenced file exists and can be accessed. If necessary, change the file access permissions to read-write. If the problem persists after restarting Activities, contact Customer Support to report the incident.
CLFRK0002E: Unable to determine memberUUID for {0}. The federated realm is not configured correctly or the wimconfig.xml file contains errors. Follow the instructions provided in the Installation Guide for Setting up federated repositories. If you edited the wimconfig.xml file, revert to the original copy of the file.
CLFRK0003E: Unable to locate VMM Profile Service {0}. The VMM component is not functioning properly. Ensure that the system is configured as a 'federated realm' by following the instructions provided in the Installation Guide for Setting up federated repositories.
CLFRK0004E: Unable to locate LDAP Profile Service {0}. The LDAP component is not functioning properly. You may be trying to implement a configuration that is not currently supported by IBM Connections. To prevent this error, you would have to configure the system as a 'standalone LDAP user registry,' which is currently not supported.
CLFRK0005E: Unable to locate Persona Profile Service {0}. The Profiles Service Atom feed component is not functioning properly. You may be trying to implement a configuration that is not currently supported by IBM Connections. To prevent this error, you would have to configure the system to rely on the Profiles service Atom feed, which is not currently supported.
CLFRK0006E: Unable to locate Memory Profile Service {0}. The memory model service of the Waltz component is not functioning properly. You may be trying to implement a configuration that is not currently supported by IBM Connections. To prevent this error, you would have to configure Tomcat as the memory model, which is an unsupported configuration.
CLFRK0007E: Unable to access directory settings for IBM Connections {0}. IBM Connections cannot find the LotusConnection-config.xml file. Make sure the LotusConnection-config.xml file is installed on the system.
CLFRL0001E: Error getting person for email <email>. The email tag is used as a key when query person in database. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0003E: Dogear servlet error. This error is encountered when Bookmarks servlet failed to handle the user requests. Check the detailed exception message below this error massages in the log file to find the root cause. If this error occurs for all requests then it is likely a downstream error condition from a previous configuration error. Check the logs from server startup for the first error condition.
CLFRL0006W: Lock slow refresh rate: dt = {0}. This is a utility log message that should not affect the end user for lock file {1}. No action necessary.
CLFRL0011E: Unable to parse atom post entry sent by user <user>. Bookmarks received an Atom Publishing request that we could not parse because of invalid syntax. No action is required if this error does not persist. The requesting client will receive an error 400 code notifying that it sent a bad request. If this error continues, it is likely that a client continues to send bad requests. Examine the HTTP server logs to determine the source of the requests and report the problem to the application developer creating these requests.
CLFRL0014E: Internal error updating memberids from file with email <link_line><message>Check the detailed exception message below this error message in the log file to find the root cause. See the dogear admin guide for more details. This error is encountered if an unexpected exception occurs when updating a batch of memberids by email from a file in administrative service. Check the detailed exception message below this error massages in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0015E: Internal error retrieving task by node id <message>. This error is encountered if an unexpected exception occurs when Bookmarks is trying to retrieve a task in the administrative service. Check the detailed exception message below this error massages in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0016W: Failed to submit for person: <user>. This warning is encountered if an unexpected IO exception occurs when trying to submit browser bookmarks for the specified user. If this warning only occurs on some browser import actions, then no action is required. Check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0019E: Error getting person for member id <member_id>. This error is encountered if an unexpected SQL exception occurs when trying to get the person with the specified member ID from the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0020W: An error occurred while parsing the search query for search spec: {0}. This warning is encountered if the Lucene service is unable to retrieve a search term. No action required.
CLFRL0022E: Error updating url for id <id>. This error is encountered if an unexpected SQL exception occurs when trying to retrieve a web address with the specified ID. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0023E: An error occurred while closing the index modifier during a commit. Bookmarks runs the indexing service as a background task. This error is encountered if an unexpected exception occurs when trying to close the index modifier during a commit. No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error massages in the log file to find the root cause. If restarting the application does not resolve and the index appears corrupt or is unusable you may use the Bookmarks administrative service to reset the indexing task. See the Administering IBM Connections section of the information center for more details.
CLFRL0024E: Error deleting link <link_id>. This error is encountered if an unexpected SQL exception occurs when trying to delete the specified link from the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0026E: Error finding file <file>. This error is encountered if Bookmarks cannot find the specified file when trying to perform batch operations in the administrative service. See the Administering IBM Connections section of the information center for more details on how to specify a file with the administrative service. Ensure the administrative process has proper file permissions.
CLFRL0029E: An error occurred release lock file <file>. This error is encountered if an unexpected IO exception occurs when trying to release the lock file. No action is required if this error does not persist. If this error continues, you may need to stop the affected node, delete the file by hand, and restart the node. This file is located in the same directory as your full text index. See the Administering IBM Connections section of the information center for help determining that location. If the problem still continues, check disk permissions for the WAS process, also check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0030E: Attempt by <user> to create subscription for <subscriber>. This error is encountered when a user is trying to create a watchlist entry as another user. This action is not allowed and the watchlist entry will not get created. If it is a malicious user, you can contact or restrict the user.
CLFRL0032E: Attempt by <user> to update or delete <link>. This error is encountered if a user attempts to delete another user's link. The link will not get deleted. If the delete action was performed for administrative purpose, please see the Administering IBM Connections section of the information center. If it was performed by a malicious user, you can contact or restrict the user.
CLFRL0034E: Failed to rollback <task> will continue to rollback other tasks. Bookmarks runs some background tasks periodically. This error is encountered if an unexpected exception occurs when one is doing a rollback of the specified task. No action is required if this error does not persist. If this error persists, check the detailed exception message below this error massages in the log file to find the root cause.
CLFRL0036E: Error updating subscription <subscription_id>. This error is encountered if an unexpected SQL exception occurs when trying to delete the specified watchlist entry. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0039W: An error occurred loading task <task> , skipping. Bookmarks runs a background link processing task periodically. This error is encountered if an unexpected exception occurs when initializing the link processing task. Check the detailed exception message below this error massages in the log file to find the root cause.
CLFRL0043E: Error getting tag counts for url <url>. This error is encountered if an unexpected SQL exception occurs when trying to get tag counts for the specified URL. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0048E: Error updating Url. This error is encountered if an unexpected SQL exception occurs when trying to update a URL. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0049I: Retrieving batch of url ids. The Bookmarks admin task has retrieved a batch from the database and is about to process them to assign intranet or internet status to them. Informational message; no solution is needed.
CLFRL0050W: Failed to transform URL encoder from <string>. This warning is encountered if UTF-8 encoding is not supported on the server. Bookmarks will use default encoding to encode the strings. Check the encoding settings of the system and make sure UTF-8 is supported by the system.
CLFRL0051E: Internal error deleting link with UID <link_uid>_<message>. This error is encountered if an unexpected exception occurs when Bookmarks is trying to delete a link with the specified UID in the administrative service. Check if the UID provided is correct. Check the detailed exception message below this error massages in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0052E: Error getting subscription on person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get a list of people who have a specified person in their watchlist Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0055E: Error getting url ids. This error is encountered if an unexpected SQL exception occurs when trying to get a batch of URL ids. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0056E: Dogear JSP tag error. Error message: <message>. This error is encountered if an unexpected exception is propagated to the UI tier of the application. Check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0057E: Error getting tag set counts person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get tag set counts for the specified person. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0058E: Error getting link count for person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get link count for the specified person in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0061E: Error getting link count. This error is encountered if an unexpected SQL exception occurs when trying to get link count in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0062E: Error registering MBean. This error is encountered if an unexpected JMX exception occurs when trying to register MBean during Bookmarks application initialization. Check the detailed exception message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0063W: Unable to retrieve a favicon from <icon_location>. This warning is encountered if Bookmarks fails to retrieve a favicon from the specified location. Check the location and make sure the favicon exists. If it does not exists, check your favicon settings in the dogear-config-node.xml or try restart the node. If the warning persists, reset the favicons storage. See the Administering IBM Connections section of the information center for more details.
CLFRL0066E: Error getting inbox links for subscriptions <subscriptions>. This error is encountered if an unexpected SQL exception occurs when trying to get link for a user's watchlist in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0067E: An error occurred marking lock file <file> to keep alive -<error_message>. This error is encountered if an unexpected IO exception occurs when trying to mark the lock file as alive. No action is required if this error does not persist. If the problem still continues, check disk permissions for the WAS process, also check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0068E: Error getting intersection link count for tags <tags> and person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get intersection link count for the specified tags for the specified person in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere: The custom dependency checker rules directory you specified cannot be found, or does not contain all the required files. If you wish to continue, the installer will use the default dependency checker rules directory. Otherwise, cancel the install and supply a different location for the custom dependency checker rules directory. Application Server to verify the database connection.
CLFRL0069E: Error creating url <url>. This error is encountered if an unexpected SQL exception occurs when trying to insert a URL to the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0070E: Error retrieving full links for <link_ids>. This error is encountered if an unexpected SQL exception occurs when trying to get links with the specified ids in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0071E: An error occurred while loading the index searcher for <index_directory>. Bookmarks runs the indexing service as a background task. This error is encountered if an unexpected exception occurs when loading the index searcher from the specified directory. No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error message in the log file to find the root cause. If restarting the application does not resolve and the index appears corrupt or is unusable you may use the Bookmarks administrative service to reset the indexing task. See the Administering IBM Connections section of the information center for more details.
CLFRL0074E: Error getting links for ft index queue, startpos=<start_pos> and count of <count>. This error is encountered if an unexpected SQL exception occurs when trying to get links in the link processing queue from the specified start position with the specified count. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0077E: Error getting tag counts for prefix <prefix> and limit <limit>. This error is encountered if an unexpected SQL exception occurs when trying to get tag counts for the specified prefix with the specified limit. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0080E: Error getting union links for tags <tags> and person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get union links for the specified tags for the specified person in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0081W: Failed to get favicon for host {0}. Use blank image. This warning is encountered if the server had trouble caching a favicon for the specified URL. If this warning only occurs on some URLs, then no action is required - this is normal. If this warning occurs on all URLs, check that the server can make outbound HTTP requests. You may need to setup an outbound proxy if the server is in a protected zone. Also check that the server process can write to the favicon cache storage on disk.
CLFRL0083E: An error occurred detecting or removing an obsolete lock file <file> - <error_message>. This error is encountered if an unexpected IO exception occurs when checking if a lock file is active and/or removing it if obsolete. No action is required if this error does not persist. If this error continues, you may need to stop the effected node, delete the file by hand, and restart the node. This file is located in the same directory as your full text index. See the Administering IBM Connections section of the information center for help determining that location. If the problem still continues, check disk permissions for the WAS process, also check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0084E: Error getting person counts for url. This error is encountered if an unexpected SQL exception occurs when trying to get person counts for a URL. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0085E: Error getting popular tag for url <url>. This error is encountered if an unexpected SQL exception occurs when trying to get popular tags for the specified URL. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0086E: Attempt by <user> to create link for <person>. This error is encountered when a user is trying to create a link for another person. This action is not allowed and the link will not get created. If it is a malicious user, you can contact or restrict the user.
CLFRL0087E: Error updating link <link_id>. This error is encountered if an unexpected SQL exception occurs when trying to update the specified link in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0090E: Error getting intersection links for tags <tags> and person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get intersection links for the specified tags for the specified person in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection. CLFRL0091E: An error occurred while releasing the write lock during a commit. Bookmarks runs the indexing service as a background task. The task requires a write lock to ensure exclusive write access to the index file. This error is encountered if an unexpected exception occurs when trying to release the write lock during a commit. No action is required if this error does not persist. If this error persists, you may need to stop the effected node, delete the file by hand, and restart the node. This file is located in the same directory as your full text index. See the Administering IBM Connections section of the information center for help determining that location. If the problem still continues, check disk permissions for the WAS process, also check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0092E: An error occurred while releasing the write lock during a rollback. Bookmarks runs the indexing service as a background task. The task requires a write lock to ensure exclusive write access to the index file. This error is encountered if an unexpected exception occurs when trying to release the write lock during a rollback. No action is required if this error does not persist. If this error persists, you may need to stop the effected node, delete the file by hand, and restart the node. This file is located in the same directory as your full text index. See the Administering IBM Connections section of the information center for help determining that location. If the problem still persists, check disk permissions for the WAS process, also check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0093E: Error getting subscription for person: <person>. This error is encountered if an unexpected SQL exception occurs when trying to get the watchlist for a specified person. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0095E: Internal error recalculating intranet ranges for url <url> <message>. This error is encountered if an unexpected exception occurs when trying to update the ip address for a URL in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0096E: Error updating memberid <member_id>. This error is encountered if an unexpected SQL exception occurs when trying to update a user's member ID in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0097E: Error getting links for urls <url>. This error is encountered if an unexpected SQL exception occurs when trying to get links for the specified URL in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0098W: Failed to check authentication status of <url>. This warning is encountered when trying to check the authentication status of the specified URL. If this warning only occurs on some URLs, then no action is required - this is normal. If all URLs when bookmarked are producing this warning, check that the server can make outbound HTTP requests. You may need to set up an outbound proxy if the server is in a protected zone.
CLFRL0101E: Error getting link for person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get links for the specified person in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0102E: Error reading file <file>. This error is encountered if an unexpected IO exception occurs when Bookmarks is trying to read the specified file when trying to perform batch operations in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. Ensure the administrative process has proper file permissions. See the Administering IBM Connections section of the information center for more details.
CLFRL0104E: Error getting active tag counts since <since_when>. This error is encountered if an unexpected SQL exception occurs when trying to get active tag counts since the specified time. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0105E: Using default icon cache <favicon_locations>. Bookmarks stores favicons in the location which is determined at installation. This error is encountered when the favicon store location is not defined in dogear-config-node.xml. When this error occurs, Bookmarks creates temp favicons store location in the temp folder. Open <WAS_Home>\profiles\<profile>\config\cells\<cell>\nodes\<node>\LotusConnections-config\dogear-config-node.xml and correct the <property name="favicon.directory"> values in <favIconService>
CLFRL0106E: An error occurred while optimizing the ft index during a commit. Bookmarks runs the indexing service as a background task. This error is encountered if an unexpected exception occurs when the index modifier is optimizing the full text indexing during a commit. No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error message in the log file to find the root cause. If restarting the application does not resolve and the index appears corrupt or is unusable you may use the Bookmarks administrative service to reset the indexing task. See the Administering IBM Connections section of the information center for more details.
CLFRL0107E: ip address <ip_addr> is an unknown or invalid host. Bookmarks has different behavior on intranet bookmarks and on internet bookmarks. The ip range for intranet is defined in dogear-config-cell.xml. This error is encountered if any ip address in the ip range definition is not a valid host. Open <WAS_Home>\profiles\

<profile>\config\cells\<cell>\

LotusConnections-config\

dogear-config-cell.xml and correct

the values in

<privateIntranetAllocation

Table>.

CLFRL0109W: Failed to run import job. This warning is encountered if an unexpected exception occurs when running job to import browser bookmarks. If this warning only occurs on some browser import actions, then no action is required. It is likely the user imported an invalid bookmark file. Check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0110E: Error getting active links. This error is encountered if an unexpected SQL exception occurs when trying to get active links in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0111E: Error creating subscription (<subscribee>,<tag>) for person <subscriber>. This error is encountered if an unexpected SQL exception occurs when trying to create a watch list entry to the subscribee on the specified tag for the subscriber. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0114E: Error creating person <person>. This error is encountered if an unexpected SQL exception occurs when trying to insert the person to the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0116E: Error getting subscribers to tag <tag>. This error is encountered if an unexpected SQL exception occurs when trying to get watchlist entries on the specified tag. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0119E: Error updating person <person_id>. This error is encountered if an unexpected SQL exception occurs when trying to update the specified person in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0120E: Error getting recent tag counts for person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get recent tag counts for the specified person. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0123E: Failed to initialize DaoConfig. Bookmarks uses the IBatis Dao framework. This error is encountered if an unexpected exception occurs when trying to initialize DaoConfig. The cause may be one of the following issues:

  • Bookmarks configuration file is missing or corrupted

  • Database connections is not available

  • A downstream error from a previous initialization problem

Check that directory.profile.xml and directory.profile.xsd are in <WAS_Home>\profiles\<profile>\config\cells\<cell>\\LotusConnections-config\ folder and the files are not corrupted. Check the database connections. Make sure the connection works fine by using "Test Connections" function in WAS. If this is likely a downstream error, scroll to the top of the log file after server startup and identify the first error in the logs.
CLFRL0124E: Error getting tag counts for tags <tags> and person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get associated tag counts for the specified tags and person. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0125E: An exception occurred while processing background tasks. Will continue on next cycle. Bookmarks runs some background tasks periodically. This error is encountered if an unexpected exception occurs when processing a background task, but the task will continue on next cycle. No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0126E: Internal error deleting link <link>. This error is encountered if an unexpected exception occurs when Bookmarks is trying to delete the specified link in the administrative service. Check the detailed exception message below this error massages in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0127E: Internal error retrieving user by email <email>. This error is encountered if an unexpected exception occurs when trying to find a person by email address in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0128E: Internal error updating memberid. This error is encountered if an unexpected exception occurs when updating memberids by email in administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0130E: Error getting active count. This error is encountered if an unexpected SQL exception occurs when trying to get active count in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0133E: Internal error deleting link from file <file>. This error is encountered if an unexpected exception occurs when Bookmarks is trying to delete link from the specified file in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0135I: Retrieving batch of person ids. The admin task has retrieved a batch of users from the database and is about to update their member ids with values from the LDAP. Informational message; no solution is needed.
CLFRL0137E: Error getting link for id <link_id>. This error is encountered if an unexpected SQL exception occurs when trying to get a link with the specified ID in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0138E: Internal error updating url <url> from file <message>. This error is encountered if an unexpected exception occurs when trying to update the ip address for a URL or update its intranet/internet status in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0139E: Error getting tag counts for person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get tag counts for the specified person. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0141E: Error deleting link by person and url <message>. This error is encountered if an unexpected exception occurs when Bookmarks is trying to delete link by person and URL in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0142E: Error loading jndi context for database resource. Bookmarks loads JNDI context for database resource at startup. This error is encountered if the Bookmarks fails to load JNDI. Log in to WAS admin console and verify the JNDI configure for Bookmarks. If settings previously worked, check for an expired password or locked db administrative account. Use the "Test Connections" in WAS to verify the database connection.
CLFRL0144E: An error occurred while closing the index modifier during a rollback. Bookmarks runs the indexing service as a background task. This error is encountered if an unexpected exception occurs when trying to close the index modifier during a rollback. No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error message in the log file to find the root cause. If restarting the application does not resolve and the index appears corrupt or is unusable you may use the Bookmarks administrative service to reset the indexing task. See the Administering IBM Connections section of the information center for more details.
CLFRL0145E: Error retrieving search result links <link_ids>. This error is encountered if an unexpected SQL exception occurs when trying to get search result links with the specified link ids. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0147E: Error getting url for: <url>. This error is encountered if an unexpected SQL exception occurs when trying to retrieve a URL object by URL string. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0148E: An error occurred while processing background tasks. Aborting. Bookmarks runs some background tasks periodically. This error is encountered if an unexpected exception when processing a background task. The task is aborted. Check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0151W: An error occurred loading a task, skipping. Bookmarks runs a background link processing task periodically. This error is encountered if the implement class for this task cannot be loaded. This value should never change from the default value shipped with the product. Open <WAS_Home>\profiles\<profile>\config\cells\<cell>\nodes\<node>\LotusConnections-config\dogear-config-node.xml and check the value of class attribute of <task> in <linkProcessingTasks> to see if it was modified from the default value.
CLFRL0153E: Error creating link for person <person> and url <url>. This error is encountered if an unexpected SQL exception occurs when trying to create a link for the specified person with the specified URL in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0154E: Verbiage size of <length> or html verbiage size of <length> was too large when creating a link for user <person> for <url>. This error is encountered if the verbiage length exceeds the maximum length threshold when trying to create a link for the specified user. Not available
CLFRL0155E: Error getting url intersection counts for people who have same url as <person>. This error is encountered if an unexpected SQL exception occurs when trying to get URL intersection counts for people who have same URL as the person. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0157E: Unable to get ATOM payload from servlet request. Bookmarks was unable to retrieve the payload from a PUT or POST request from the Atom Publishing API. No action is required if this error does not persist. The requesting client will receive an error 400 code notifying that it sent a bad request. If this error continues, it is likely that a client continues to send bad requests. Examine the HTTP server logs to determine the source of the requests and report the problem to the application developer creating these requests.
CLFRL0158E: Error getting person from directory profile for email {0}. Bookmarks uses Waltz to retrieve person information from LDAP server. This error is encountered if an unexpected exception occurs when trying to get person from directory profile with the specified email address. Check the detailed exception message below this error message in the log file to find the root cause and make sure the connection to LDAP server is available and the signer certificate is valid. See the Administering IBM Connections section of the information center for more details.
CLFRL0159E: Error getting person from directory profile for email <email> Bookmarks uses Waltz to retrieve person information from LDAP server. This error is encountered if an unexpected exception occurs when trying to get person from directory profile with the specified email address. Check the detailed exception message below this error message in the log file to find the root cause and make sure the connection to LDAP server is available and the signer certificate is valid. See the Administering IBM Connections section of the information center for more details.
CLFRL0160E: Internal error with task reset <message>. This error is encountered if an unexpected exception occurs when Bookmarks is trying to reset a task in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0163E: Error getting link count for url <url>. This error is encountered if an unexpected SQL exception occurs when trying to get link count for the specified URL in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0165E: An error occurred while obtaining a write lock. Bookmarks runs the indexing service as a background task. The task requires a write lock to ensure exclusive write access to the index file. This error is encountered if an unexpected exception occurs when trying to write this file. No action is required if this error does not persist. If the error continues, check disk permissions for the WAS process, also check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0168W: The value for property <property_name> in the link processing service config was not an integer, skipping config param. Bookmarks runs a background link processing task periodically. Bookmarks defines the task running parameters in configure files. This error is encountered if the value of an integer property is not an integer. Open <WAS_Home>\profiles\<profile>\config\cells\<cell>\nodes\<node>\LotusConnections-config\dogear-config-node.xml and correct the values in <linkProcessingTasks>.
CLFRL0170E: Error deleting links prior to <date>. This error is encountered if an unexpected SQL exception occurs when trying to delete links prior to the specified date from the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0173E: Error getting all people. This error is encountered if an unexpected SQL exception occurs when trying to get all person in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0174W: Failed to get URL string: <url_string>. This warning is encountered if the server is having trouble resolving URL redirects. If this warning only occurs on some URLs, then no action is required - this is normal. If all URLs when bookmarked are producing this warning, check that the server can make outbound HTTP requests. You may need to setup an outbound proxy if the server is in a protected zone.
CLFRL0177E: Error getting most active person counts since <since_when>. This error is encountered if an unexpected SQL exception occurs when trying to list the most active Bookmarks users in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0178E: Internal error retrieving url. This error is encountered if an unexpected exception occurs when trying to get a URL in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0179E: Error getting inbox link count for subscriptions <subscriptions>. This error is encountered if an unexpected SQL exception occurs when trying to get a link count for a user's watchlist in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0180W: Encountered more links with identical timestamp than batch size, increasing batchsize to {0} for this iteration. This warning is encountered if the batch size provided by the user is less than the number of links for the timestamp the processing service is working on. No action is required.
CLFRL0181E: Error init Dogear config. This error is encountered if Bookmarks is unable to properly load all required configuration files. Check the detailed exception message of the exception. It will show which configuration file is corrupted or missing. Edit the configure file to fix the error. See the Administering IBM Connections section of the information center for more details.
CLFRL0182E: Error getting person counts for tag intersection <tags> and person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get person counts for tag intersection for the specified person with the specified tags. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0183E: Error getting person profile from ldap for id: <login_id>. Bookmarks uses Waltz to retrieve person information from LDAP server. This error is encountered if an unexpected exception occurs when trying to get person profile from directory profile with the specified login ID. Check the detailed exception message below this error message in the log file to find the root cause and make sure the connection to LDAP server is available and the signer certificate is valid. See the Administering IBM Connections section of the information center for more details.
CLFRL0185E: Attempt by <user> to update or delete <person>. This error is encountered when a user is trying to update or delete an entry form another user's watchlist. This action is not allowed and the entry will not change. If it is a malicious user, you can contact or restrict the user.
CLFRL0186E: Error getting link for person <person> and url <url>. This error is encountered if an unexpected SQL exception occurs when trying to get a link for a specified user with a specified URL in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0187E: An error occurred reloading the search index during a commit. Bookmarks runs the indexing service as a background task. This error is encountered if an unexpected exception occurs when reloading the index searcher during a commit. No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error message in the log file to find the root cause. If restarting the application does not resolve and the index appears corrupt or is unusable you may use the Bookmarks administrative service to reset the indexing task. See the Administering IBM Connections section of the information center for more details.
CLFRL0190E: An error occurred creating a lock file <file> - <error_message>. This error is encountered if an unexpected IO exception occurs when trying to create the lock file. No action is required if this error does not persist. If the problem still continues, check disk permissions for the WAS process, also check the detailed exception message below this error message in the log file to find the root cause.
CLFRL0191E: Internal error retrieving batch from database <message>. This error is encountered if an unexpected exception occurs when retrieving a batch of URLs when trying to updated their ip addresses or update their intranet/internet settings in administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0193E: Error getting tag counts for subscriptions <subscriptions>. This error is encountered if an unexpected SQL exception occurs when trying to get tag counts for the specified watchlist entries. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0196E: Error getting union link count for tags <tags> and person <person>. This error is encountered if an unexpected SQL exception occurs when trying to get union link count for the specified tags for the specified person in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0197W: Unable to generate UTF-8 bytes. This error is encountered if Bookmarks cannot convert the input strings to UTF-8 encoded bytes. Bookmarks will use default encoding to convert the strings. Check the encoding settings of the system and make sure UTF-8 is supported by the system.
CLFRL0198E: Error getting links. This error is encountered if an unexpected SQL exception occurs when trying to get links in the database. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
CLFRL0201E: An error occurred while shutting down index searcher for <index_directory>. Bookmarks runs the indexing service as a background task. This error is encountered if an unexpected exception occurs when shutting down the index searcher from the specified directory. No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error messages in the log file to find the root cause. If restarting the application does not resolve and the index appears corrupt or is unusable you may use the Bookmarks administrative service to reset the indexing task. See the Administering IBM Connections section of the information center for more details.
CLFRL0216E: Internal error reprocessing intranet address for url <url> <message>. This error is encountered if an unexpected exception occurs when reprocessing intranet address for URL in administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0219W: Authorization failed for <user> while invoking <method> on <servlet_path>, not granted any of the required roles: <role>. This warning is encountered if basic authentication succeeds but the user is not authorized to use the Bookmarks application. Not available.
CLFRL0220W: Basic Authentication failed for <user> while invoking <method> on <servlet_path>. This warning is encountered if basic authentication fails for the user. This is usually a wrong username or password. Not available.
CLFRL0221E: ERROR unable to find url matching url string <url_string> provided. This error is encountered if no URL in database matches the specified URL string when trying to update ip address or update intranet/internet status in the administrative service. Provide a valid URL. See the Administering IBM Connections section of the information center for more details.
CLFRL0222E: Failed to delete task from database table with task id <task_id>. This error is encountered if an attempt is made to delete a non existent task in the administrative service. Get a list of valid task ids and delete the desired task by the correct ID. See the Administering IBM Connections section of the information center for more details.
CLFRL0223E: ERROR Unable to find link matching UID provided. This error is encountered if no link in database matches the specified uid when running administrative service to delete a link. Provide a valid UID. See the Administering IBM Connections section of the information center for more details.
CLFRL0224E: Error deleting line when deleting link by person url from file <message>. This error is encountered if an unexpected exception occurs when Bookmarks is trying to delete link by person and URL in the administrative service. Check the detailed exception message below this error massages in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0225E: ERROR Unable to find link matching email and url provided. This error is encountered if no link in database matches the specified email and URL when running administrative service to delete a link. Provide a URL and email that match an existing link. See the Administering IBM Connections section of the information center for more details.
CLFRL0226E: Internal error updating url from file <message>. This error is encountered if an unexpected exception occurs when trying to update URL from file in the administrative service. Check the detailed exception message below this error message in the log file to find the root cause. See the Administering IBM Connections section of the information center for more details.
CLFRL0227E: ERROR unable to find person matching email provided <email@>. This error is encountered if no person in database matches the specified email when running administrative service. Provide a valid email. See the Administering IBM Connections section of the information center for more details.
CLFRL0243E: One or both files are not directories: [" {0} "] [" {1} "]"

CLFRL0244E: Directories have different number of files: [" {0} "] has " {1} " files [" {2} "] has " {3} " files

CLFRL0245E: Files do not both exist: [" {0} "] [" {1} "]

CLFRL0246E: Could not get canonical path for {0}

CLFRL0247E: One is a directory, the other isn''t: [" {0} "] [" {1} "]

CLFRL0248E: Files have different names: [" {0} "] [" {1} "]

CLFRL0249E: File contents are different: [" {0} "] [" {1} "]"

CLFRL0250E: Directories do not both exist: [" {0} "] ["{1} "]

CLFRL0251E: Error deleting received notifications of person {0}

CLFRL0252E: Error deleting notifications sent by person {0}

CLFRL0254E: Error saving notifications.

CLFRL0255E: Error retrieving full links by URL and date for {0}

CLFRL0256E: Error getting the notification with id {0}

CLFRL0257E: Error deleting notifications on link {0}

CLFRL0258E: Error sending notifications from {0} to {1} on bookmarks {2}

CLFRL0259E: Could not delete bookmarks to {0}

CLFRL0260E: Invalid link id from user: {0}, link id: {1}

CLFRL0262E: Error deleting the notification with id {0}

CLFRL0263E: Error parsing email addresses when sending notifications. Emails: {0}

CLFRL0264E: Error sending notifications as user {0}

CLFRL0265E: Error recording the notification from person {0} to person {1} on link {2}

CLFRL0266E: Error getting most visited links.

CLFRL0267E: Error getting notifications on link {0}

CLFRL0271E: Service {0} is not correctly configured. Bookmarklet can not point to the correct server if attributes "enabled" and "href" are not set in the configure file. Please check IBM Connections configure file.

CLFRL0272E: Unable to load configure file for bookmarklet installer.

CLFRL0273E: Failed to check bookmarklet installer.

CLFRL0275E: Failed to update the bookmarklet installer.

CLFRL0276E: Failed to parse IBM Connections configure file.

CLFRL0278E: Unable to find configure file for bookmarklet installer.

CLFRL0279E: Failed to get and parse the profile for user {0}.

CLFRL0280E: Error getting recently received notifications of user {0}.

CLFRL0282E: Error getting the number of received notifications of user {0}.

CLFRL0283E: Error getting received notifications of user {0}.

CLFRL0285E: Error sending notification from {0} to {1} on bookmarks {2}

CLFRL0286E: Error parsing email addresses when sending notifications. Emails: {0}

CLFRL0287E: Invalid link id from user: {0}, linkid: {1}

CLFRL0289E: Error getting schema version from database.

CLFRL0291E: Error updating person {0} with new locale {1}

CLFRL0302E: Error: failed to update ContentTypes with the ones from the configuration file.

CLFRL0303E: Error getting the number of ContentTypes in the most notified links.

CLFRL0306E: Error deleting all ContentTypes from database.

CLFRL0308E: Error getting received notifications of user {0}, filtered by tag union. Tags: {1}.

CLFRL0309E: Error creating ContentType URL mappings for URL: {0}

CLFRL0310E: Error getting the number of ContentTypes in received notifications of user {0}, filtered by tag union. Tags: {1}.

CLFRL0311E: Error getting the number of received notifications of user {0}.

CLFRL0312E: Error getting count of content types.

CLFRL0313E: Error getting received notifications of user {0}, filtered by tag intersection. Tags: {1}.

CLFRL0314E: Error getting tag counts of received notifications for {0}

CLFRL0316E: Error getting person counts of received notifications for {0}

CLFRL0317E: Error querying all ContentTypes from database.

CLFRL0318E: Error: failed to get count of ContentTypes from database.

CLFRL0319E: Error getting the number of ContentTypes in received notifications of user {0}, filtered by tag intersection. Tags: {1}.

CLFRL0320E: Error deleting all ContentType URL mappings from database when updating the mappings.

CLFRL0320E: Error deleting all URL-ContentType mappings from database when updating URL-ContentType mappings.

CLFRL0321E: Error getting count of content types for person {0}

CLFRL0322E: Error getting the number of ContentTypes in received notifications of user {0}.

CLFRL0323E: Error deleting all ContentType URL mappings from database.

CLFRL0327E: Error: failed to get specified ContentType from database.

CLFRL0328E: Error getting count of content types for subscriptions {0}

CLFRL0329E: Error getting the number of received notifications of user {0}, filtered by tag union. Tags: {1}.

CLFRL0331E: Error getting the number of ContentTypes in received notifications of user {0}.

CLFRL0332E: Error: failed to delete URL mappings of a ContentType from database.

CLFRL0334E: Error: failed to create ContentType URL mapping.

CLFRL0335E: Error getting the number of the most notified links.

CLFRL0336E: Error getting links for full-text index queue, startpos

CLFRL0337E: Error: failed to insert a ContentType record.

CLFRL0338E: Failed to verify request.

CLFRL0339E: Error: failed to get links count by ContentType.

CLFRL0342E: Error getting intersection count of content types for tags {0} and person {1}

CLFRL0343E: Error getting count of content types for URL {0}

CLFRL0344E: Error getting notifications by URL and date.

CLFRL0345E: Error getting the number of received notifications of user {0}, filtered by tag intersection. Tags: {1}.

CLFRL0346E: Error: failed to record the click on Link {0}

CLFRL0347E: Error writing ServiceConfigs to feed.

CLFRL0349E: Error getting structured tag counts for person {0}

CLFRL0350E: Error getting number of unique URLs last modified since {0}

CLFRL0352E: Error getting tag counts of sent notifications for {0}

CLFRL0354E: Error getting structured tag counts of received notifications for {0}

CLFRL0355E: Error sending the notification on broken URL from {0} to {1} on bookmark {2}

CLFRL0356E: Error getting notifications sent by user {0}.

CLFRL0357E: Error getting person counts of notifications sent by {0}.

CLFRL0358E: Error getting URLs last modified since {0}

CLFRL0359E: Error getting the number of notifications sent to user {0}.

CLFRL0360E: Error getting the number of the notifications sent to user {0}, filtered by tag intersection. Tag: {1}.

CLFRL0361E: Error getting the number of the notifications sent to user {0}, filtered by tag union. Tag: {1}.

CLFRL0362E: Error getting tag counts for hover text, tag is {0}

CLFRL0363E: Error getting structured tag counts of sent notifications for {0}

CLFRL0364E: Error getting the notifications sent to user {0}, filtered by tag intersection. Tag: {1}.

CLFRL0365E: Error: failed to record the click on Link {0} by Person {1}

CLFRL0366E: Error getting the notifications sent to user {0}, filtered by tag union. Tag: {1}.

CLFRL0367E: Error getting tag counts for hover text for person {0}, tag is {1}

CLFRL0368E: Error parsing email address when sending broken URL notifications. Email: {0}

CLFRL0369E: Error getting login names for person id {0}.

CLFRL0371E: Error getting person for login name {0}

CLFRL0373E: Internal error updating login name by the provided id {0}

CLFRL0374E: Attempt by {0} to subscribe to Anonymous User.

CLFRL0379E: Internal error updating login names from file with member id {0} {1}

CLFRL0387E: Error getting person profile from LDAP for id: {0}

CLFRL0388E: Error deleting login names for person id {0}.

CLFRL0390E: Unable to find person matching the provided id {0}

CLFRL0392E: Error getting person profile from LDAP for email: {0}

CLFRL0393E: Error getting login names in batch

CLFRL0394E: Error updating login names for person id {0}.

CLFRL0397E: Internal error retrieving user by member id {0}

CLFRL0398E: Error getting tags for constraints {0}

CLFRL0400E: Error getting deleted links.

CLFRL0403E: The term of category is not correct.

CLFRL0404E: No category specified in the post entry.

CLFRL0405E: Notification body only supports text format.

CLFRL0406E: Unable to parse Notification Atom post entry sent by user {0}

CLFRL0407E: Dogear Notification API only supports http post method.

CLFRL0408E: Links in the atom are private or deleted.

CLFRL0409E: Recipients in the atom cannot be found.

CLFRL0410E: Content type is not correct. Current ContentType is: {0}

CLFRL0411E: Error updating last login time {0} for person {1}

CLFRL0412E: An error occurred while firing search request to Global Search service

CLFRL0413E: Error getting the number of new and unique URLs posted in the last {0} days

CLFRL0414E: Error getting the number of users who have more than {0} bookmarks

CLFRL0415E: Error getting number of users logged on in the last {0} days.

CLFRL0416E: Error getting the number of bookmarks that have at least 1 tag

CLFRL0417E: Error getting the number of users who received notifications in the past {0} days.

CLFRL0418E: Error getting the number of new bookmarks posted in the last {0} days

CLFRL0419E: Error getting the number of users who submit bookmarks in the last {0} days

CLFRL0420E: Error getting the number of users who sent notifications in the past {0} days.

CLFRL0421E: Error getting the number of tags posted in the last {0} days

CLFRL0422E: Error getting the number of users who have not logged in for more than {0} days.

CLFRL0423E: Error getting the number of new tags posted in the last {0} days

CLFRL0424E: Error getting person counts for bookmarks with request parameters {0}.

CLFRO0142E: No argument to method may be null. Cannot draw header or footer

CLFRO0143E: NavigationHelper class has not been initialized

0144E: No argument to method may be null. Cannot draw header or footer

CLFRO0145E: NavigationHelper class has not been initialized

CLFRO2001E: Error processing config file: <path>, <filename>. The server encountered an error while parsing the specified configuration file. Ensure that XML configuration files in the LotusConnections-config folders are valid.
CLFRO2002E: Unable to find configuration with id: <config_id>. The server could not retrieve an XML configuration file with the requested ID in the LotusConnections-config folder hierarchy. Report this problem to Customer Support.
CLFRO2003E: Error processing global configuration file The server could not retrieve or successfully parse a LotusConnections-config.xml configuration file from the LotusConnections-config folder hierarchy. Report this problem to Customer Support.
CLFRO2004E: Error: <filename> does not have an id attribute in its config element. The specified XML configuration file does not have a value defined for the required id attribute of the <config> element. Report this problem to Customer Support.
CLFRO2006E: href attribute in <filename> service element The specified XML configuration file does not have a valid value defined for the href attribute; it should be a value that can be converted into a URL. Update the value of the href attribute to be a properly formed URL string.
CLFRO2009E: Entry for service <service_name> does not exist in global config file <file_name>. The global configuration file does not have a service reference for the requested service name. Report this problem to Customer Support.
CLFRO2010E: Cannot locate schema file <filename>. The server cannot find an xsd file required to validate the schema validation in the folder <app_server_profile>/config/cells/ <cell_name>/LotusConnections-config. Report this problem to Customer Support.
CLFRP0001E: IBM Connections cannot use the WAS in: <FileLocation>. Please refer to the following message log for additional information: <LogFileLocation> The WAS is insufficient for IBM Connections. IBM Connections requires specific WAS applications and component levels. Refer to the message log file to determine why the WAS is insufficient for IBM Connections. Apply WAS changes as required to satisfy IBM Connections requirements.
CLFRP0006E: The specified directory is not valid. IBM Connections is already installed in this location. The selected directory already has IBM Connections installed. Choose a different directory or remove IBM Connections from the selected directory.
CLFRP0007E: Operating System prerequisite check failed. Refer to the message log file <LogFileLocation> for additional information. The operating system is not supported. Install IBM Connections on a supported operating system. If your operating system is a newer version of a supported platform, refer to the IBM Connections support site or contact Customer Support to determine if the operating system level is supported.
CLFRP0060E: There were no profiles detected for the installed WAS and managed node selected. There were no profiles detected under the installed WAS. Make sure there are profiles under WAS.
CLFRP0061E: The profile selected cannot be validated. Please refer to the following logs for additional information: <LogFileLocation> <FileLocation> Cannot pass the validation of the selected profile.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Make sure the profile selected is valid and then try again.

CLFRP0061W: WAS security must be enabled. WAS security is not enabled. Make sure WAS security is enabled, then try again.
CLFRP0062E: There were no servers detected for the installed WAS. There were no servers detected under the installed WAS. Make sure there is a server instance under the WAS profile selected.
CLFRP0063E: The server selected cannot be validated. Please refer to the following logs for additional information: <LogFileLocation> <FileLocation> The WebSphere AppServer server is not valid. Make sure the WebSphere AppServer server is valid.
CLFRP0214E: The custom dependency checker rules directory you specified cannot be found, or does not contain all the required files. You must supply a different location for the custom dependency checker rules directory. The installer will now exit. The custom dependency checker rules directory you specified cannot be found, or does not contain all the required files. Check the value you supplied for the custom dependency checker rules directory. Look at the logs for the files that are required by the installer. Also make sure all the required dependency checker files exist in that directory.
CLFRP0251E: Installation of Change Password Application has failed. Failure to install Change Password Application.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue IBM Connections Pilot installation.

  3. After installation is completed, install the file, changePassword.ear from the following directory:

      <LotusConnectionsInstall
      Location>\installable
      Apps\

CLFRP0252E: The selected file does not have a correct format, please select a correct one. The selected file does not have a correct format. Check the format of the user file according to IBM Connections information center, making sure it is correct.
CLFRP0299E: An error occurred installing 6.1.0.0-WS-WAS-IFPK38815.pak, please check log file <LogFileLocation>. Failure to install 6.1.0.0-WS-WAS-IFPK38815.pak.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue IBM Connections installation, referring to WAS information center to install the interim fix 6.1.0.0-WS-WAS-IFPK38815.pak manually once the IBM Connections installation is complete.

CLFRP0300E: An error occurred installing WAS V6.1.0.3. For additional information, refer to the log file <LogFileLocation> or <FileLocation>. Failure to install WAS.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Cancel the IBM Connections installation.

  3. Uninstall WAS and DB2 manually. (Refer to WebSphere and DB2 information centers.)

  4. Try to install IBM Connections Pilot again.

CLFRP0301E: An error occurred installing 6.1.0.3-WS-WAS-IFPK34390.pak. For additional information, refer to the log file <LogFileLocation>. Failure to install 6.1.0.3-WS-WAS-IFPK34390.pak.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue the IBM Connections installation.

  3. Refer to the WAS information center to install the interim fix 6.1.0.3-WS-WAS-IFPK34390.pak manually once the IBM Connections installation is complete.

CLFRP0303E: An error occurred installing WebSphere Update Installer V6.1.0.1. For additional information, refer to the log file <LogFileLocation>. This error is encountered if there is a failure to install WebSphere Update installer.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue the pilot installation.

  3. After installation is completed, try to install WebSphere Update Installer manually. (Refer to the WAS information center.)

  4. Install the 5 interim fixes mentioned in the IBM Connections information center.

CLFRP0305W: WAS administrator passwords must match. WAS administrator passwords don't match. Make sure WAS administrator passwords match.
CLFRP0306W: DB2 Administrator password must match. The DB2 Administrator password doesn't match. Make sure the DB2 Administrator password matches.
CLFRP0307E: A previous version of IBM Connections was found <FileLocation>. This version only requires a Fix Pack to be applied. Refer to IBM Connections information center for instructions on installing Fix Pack <FixPackVersion>. A previous version of IBM Connections was installed on the server. Either run upgrade installer for 1.0.2 or uninstall previous IBM Connections, then run 1.0.2 installer to install again.
CLFRP0308W: DB2 Administrator password field cannot be empty. The Administrator password field is empty. Make sure the DB2 Administrator password field is not empty.
CLFRP0309E: An error occurred while installing IBM DB2 Express Edition fixpack1. For additional information, refer to the log file <LogFileLocation>. Failure to install IBM DB2 Express Edition fixpack 1.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Stop the Lotus Connection Pilot installation and then remove DB2 manually. (Refer to the DB2 information center.)

  3. Try to install Lotus Connection Pilot again.

CLFRP0310E: An error occurred uninstalling WebSphere Update Installer V6.1.0.1. For additional information, refer to the log file <LogFileLocation>. Failure to uninstall IBM WebSphere Update Installer V6.1.0.1.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue uninstalling IBM Connections. Refer to the WAS information center to uninstall WebSphere Update Installer V6.1.0.1 manually after the IBM Connections installation is completed.

CLFRP0311E: <ApplicationName> application already installed. The application has already been installed.

  1. Run the uninstaller guide to uninstall the application.

  2. Try to install the application again.

CLFRP0315E: An error occurred while uninstalling IBM WAS 6.1. For additional information, refer to the log file <LogFileLocation>. Failure to uninstall IBM WAS 6.1.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue uninstalling IBM Connections.

  3. After uninstallation is completed, try to uninstall WAS manually. (Refer to the WebSphere information center.)

CLFRP0316E: An error occurred installing 6.1.0.3-WS-WAS-IFPK37124.pak. For additional information, refer to the log file <LogFileLocation>. Failure to install 6.1.0.3-WS-WAS-IFPK37124.pak.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue installing IBM Connections.

  3. Refer to the WAS information center to install the interim fix 6.1.0.3-WS-WAS-IFPK37124.pak manually after the IBM Connections installation is completed.

CLFRP0317E: An error occurred uninstalling WAS V6.1.0.3. For additional information, refer to the log file <LogFileLocation>. An error occurred while uninstalling WAS V6.1.0.3.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue uninstalling IBM Connections.

  3. Refer to the WAS information center to uninstall WAS V6.1.0.3 manually after the IBM Connections installation is completed.

CLFRP0318W: The WAS administrator User name field cannot be empty. The WAS administrator User name field is empty. Make sure the WAS administrator User name field is not empty.
CLFRP0319W: WAS administrator user name must be 30 characters or less. WAS administrator user name has exceeded 30 characters. Make sure the WAS administrator user name has 30 characters or less.
CLFRP0321E: An error occurred while uninstalling IBM Update Installer for WebSphere Software Installation. For additional information, refer to the log file <LogFileLocation>. An error occurred while uninstalling IBM Update Installer.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Continue the uninstallation.

  3. After uninstallation is completed, try to uninstall WebSphere Update Installer manually. (Refer to the WebSphere information center.)

CLFRP0322E: An error occurred while creating a user. For additional information, refer to the log file <LogFileLocation>. This error is encountered if there is a failure to start WAS or generate a user. Check the detailed exception message below this error message in the log file to find the root cause. Try to fix it and then do the user creation again.
CLFRP0324E: Uninstallation of offerings has failed. An error occurred while uninstalling offerings.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Try to fix it and then uninstall again.

CLFRP1001E: db2jcc_license_cu.jar and db2jcc.jar do not exist in <FileLocation>. The directory you specified does not contain all the required files. Make sure db2jcc_license_cu.jar and db2jcc.jar exist in the specified directory.
CLFRP1002E: ojdbc14.jar does not exist in <FileLocation>. Installer cannot locate ojdbc14.jar. Make sure ojdbc14.jar is in the specified directory.
CLFRP1003E: Cannot connect to database using provided settings, please check again! This error is encountered if the user provided settings are not correct. Input the correct database properties and try again.
CLFRP1004E: At least one application must be selected for uninstall. This error is encountered if no application is selected for uninstall. Make sure at least one application is selected for uninstall.
CLFRP1005E: At least one application must be selected for install. This error is encountered if no application is selected for install. Make sure at least one application is selected for install.
CLFRP1006E: uninstallInfo.txt missing, unable to uninstall this product. Cannot find uninstallInfo.txt under the directory:

<LotusConnectionsInstall
Location>/<component>/
uninstall/profiles/
<profile>

.

Try to recover uninstallInfo.txt, and perform the uninstallation again.
CLFRP1007E: Uninstall of the component: <ComponentName> has failed or this component has already been uninstalled. Failure to uninstall the component.

  1. Check the detailed exception message below this error message in the log file to find the root cause.

  2. Try to fix it and then uninstall again.

CLFRV0001E: Viral content replaced. The virus scanner removed a virus from added content. No action necessary. CLFRV0003E: Virus detected - <error>. The virus scanner received the error <error> scanning content. No action necessary. The content was not added to the discussion forum.
CLFRV0006E: Unable to find CMAPI provider "<providerName>". Unable to find a suitable CMAPI provider. Check the <objectStore> settings in forum-config.xml and provide a correct <providerName> for the class property of the store element.
CLFRV0007E: Unable to store object. URL = <url> HTTP status = <error>. An error occurred while attempting to store the discussion forum's content in the Domino content store. Verify that the Domino server is responding and that the URL is accessible. The HTTP response code may give additional information as to the reason for the failure.
CLFRV0008E: Unrecognized URI: <url> for this ObjectStore: <storeId>. An invalid URL or URL syntax was used to access the Domino content store. Verify that the Domino server is responding and that the URI is accessible. Contact Customer Support for additional information.
CLFRV0009E: Unable to access: <url>, the HTTP response code = <error>. An error occurred while attempting to retrieve a discussion forum's content from the Domino content store. Verify that the Domino server is responding. The HTTP response code may give additional information as to the reason for the failure.
CLFRV0010E: Notes UNID could not be retrieved. Make certain the database has the correct design. An error occurred while attempting to store or update a discussion forum in the Domino content store. Verify that the Domino server is responding. Verify that the Domino object store is using the correct NSF design.
CLFRV0011W: Content does not have a name, the generated name <url> will be used. A warning that the content being saved did not have a name while attempting to store or update a discussion forum in the Domino content store. No action is required. The system has generated a name automatically.
CLFRV0012E: Unable to delete object. URL = <url> HTTP status = <error>. An error occurred while attempting to delete a discussion forum from the Domino content store. Verify that the Domino server is responding and that the URL is accessible. The HTTP response code may give additional information as to the reason for the failure.
CLFRV0013E: Unable to delete file <fileName>. An error occurred while deleting a file from the discussion forum content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the directory and file information is correct.
CLFRV0014E: Unable to create file upload directory <directoryName>. The directory given in forum-config.xml for the element property name "root.directory" either could not be found or created. This directory is used for file uploads to the discussion forum content store. Check that the directory exists; create it if it does not exist.
CLFRV0015E: Error encountered deleting content: <directoryName> <fileName>. An error occurred while deleting the contents of a file from the discussion forum content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the directory and file information is correct.
CLFRV0016E: Unable to upload file: <directoryName> <fileName>. An error occurred while retrieving or uploading a file to the discussion forum content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the directory and file information is correct.
CLFRV0017E: Error closing statistics file. A file system error occurred closing one of the files used for discussion forum statistics persistence. Verify that the file system directory containing the statistics files is writable and has available space.
CLFRV0019E: Error creating statistics file. A file system error occurred creating one of the files used for discussion forum statistics persistence. Verify that the file system directory containing the statistics files is writable and has available space.
CLFRV0020E: Error parsing statistics file. The format of one of the files used for discussion forum statistics persistence is inconsistent with the expected format. Remove the existing files in the file system directory containing the statistics files.
CLFRV0021E: Activities statistics persistence cannot create directory <directory>. A file system error occurred creating the file system directory <directory> for containing the discussion forum statistics files. Verify that the server level WAS variable ACTIVITIES_STATS_DIR is set to a valid directory location on the server's file system; create the directory <directory> on the file system.
CLFRV0022E: Error saving to statistics file. A file system error occurred saving data one of the files used for discussion forum statistics persistence. Verify that the file system directory containing the statistics files is writable and has available space.
CLFRV0023E: Error saving summary information. A file system error occurred saving data one of the files used for discussion forum statistics persistence. Verify that the file system directory containing the statistics files is writable and has available space.
CLFRV0026E: Error fetching profiles. The MemberService wsadmin object received an exception executing a fetchMembers command. Verify that the parameter to the fetchMembers command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0028E: Error updating acl. The AccessControlService wsadmin object received an exception executing an access modification command. Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0029E: Error fetching activities. The ActivityService wsadmin object received an exception executing a command to fetch the discussion forum. Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0030E: Error fetching acl. The AccessControlService wsadmin object received an exception executing a fetchAccess command. Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0032E: Error updating profile. The MemberService wsadmin object received an exception executing a updateMember command. Verify that the parameter to the updateMember command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0033E: Error purging trash. The TrashCollectionService wsadmin object received an exception executing a purgeTrash command. Verify that the parameter to the purgeTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0034E: Error fetching trash. The TrashCollectionService wsadmin object received an exception executing a fetchTrash command. Verify that the parameter to the fetchTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0035E: Error undeleting trash. The TrashCollectionService wsadmin object received an exception executing a undeleteTrash command. Verify that the parameter to the undeleteTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0036E: Error locating MBeanServer, no Activity Administration MBeans registered. An exception was generated when the Discussion Forum tried to locate the MBean server needed to register the Discussion Forum Administration MBeans. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0038E: Error registering mbean. An exception was generated when the Discussion Forum tried to register the Activities Administration MBeans. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0042E: <className> error parsing generic properties into a Properties object. An exception was generated when the Event Broker tried to parse its configuration from forum-config.xml. Ensure the properties and elements for the <eventBroker> element in forum-config.xml are valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0043E: subscriber did not start: <className>. The Event Broker service is attempting to initialize a subscriber to server-generated events, but the subscriber initialization process failed. Check that the <eventBroker> configuration specified in forum-config.xml for the subscriber reporting this error is valid. Additionally, you may want to pursue the exception thrown by the subscriber in the SystemOut.log file.
CLFRV0044E: The class "<className>" was not found. Check the configuration file, under the class attribute of the service for the correct Java classname. Or, check the classpath to make sure the class is visible. The Event Broker service tried to load a Java class that did not exist in the current classpath. Check to see whether the class specified in the <eventBroker> configuration has been spelled correctly. Also check to see that the class file is visible in the current classpath scope. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0045E: The class "<className>" could not be instantiated. The classloader could not instantiate the class requested by the Event Broker service. Investigate whether something is wrong with the classloader or the class specified in the <eventBroker> configuration itself. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0046E: Illegal access exception for the class "<className>". The Event Broker service is trying to access fields or methods in the class discovered via reflection that it can't normally see. Additional information relating to the failure may be found in the SystemOut.log file. Examine the class for methods that should be exposed have been hidden.
CLFRV0047E: {0} error initializing adapter: classname= "{1}" Double-check the config settings for this specific adapter for correct/valid values. The Event Broker service is attempting to initializer a subscriber to server-generated events, but the subscriber initialization process failed. Check that the <eventBroker> configuration specified in forum-config.xml for the subscriber reporting this error is valid. Additionally, you may want to pursue the exception thrown by the subscriber in the SystemOut.log file.
CLFRV0048E: Could not inform a subscriber of event: <eventName>. The Event Broker service passed an event to a subscriber of that event, and the subscriber issued an exception. To fix this class of exception, you need to determine what is failing in this particular subscriber. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0050E: Invalid forum-config.xml file. Check the XML format and ensure that all required settings are complete. The format of forum-config.xml does not have correct XML syntax. Load the forum-config.xml file into a browser or editor that will display syntax errors; fix the error and save the file.
CLFRV0051E: Error decoding passwords. If passwords are encoded, some functionality may fail. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0068E: OpenActivitiesException while updating node content ref uuid=<uuid>. An error occurred while updating the content of the specified discussion forum. Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
CLFRV0070E: Illegal access exception for the class "<className>". An error occurred while processing the discussion forum content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the <objectStore> configuration information in forum-config.xml is correct. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0071E: DaoException while updating node content ref uuid=<uuid>. An error occurred while updating the content of the specified discussion forum. Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
CLFRV0072E: activities object store did not start: <className>. The Discussion Forum Object Store service implemented by <className> did not start. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the <objectStore> configuration information in forum-config.xml is correct. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0073E: Destination ObjectStore ID="<id>" not found in ObjectStore registry. Double-check the forum-config.xml file. An error occurred while transferring discussion forum content from one content store to another. The requested destination object store identifier was not found. Check the spelling of the ID used and compare it with the available object stores listed in the forum-config.xml file.
CLFRV0074E: ObjectStoreFilter: error during activities object store content filtering "<error>". An error occurred while processing discussion forum content. Additional information relating to the failure may be found in the SystemOut.log file. Depending on the additional error information given, it may be possible to correct the data and re-process it.
CLFRV0075E: Premature invocation before transfer is complete. Check busy() method or listen for completion event. An error occurred while transferring discussion forum content from one content store to another. The transfer utility may already be carrying out a transfer. Attempt this operation after the other transfer is complete.
CLFRV0076E: <error> Exception while retrieving activities collection. An error occurred while transferring discussion forum content from one content store to another. Check that the content stores are available and accessible.
CLFRV0077E: ObjectStoreConfigLoader: the class "<className>" could not be instantiated. An error occurred while processing the discussion forum content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the <objectStore> configuration information in forum-config.xml is correct. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0078E: Source ObjectStore ID="<id>" not found in ObjectStore registry. Double-check the forum-config.xml file. An error occurred while transferring discussion forum content from one content store to another. The requested source object store identifier was not found. Check the spelling of the ID used and compare it with the available object stores listed in the forum-config.xml file.
CLFRV0079E: {0} error initializing adapter: classname= "{1}" Double-check the config settings for this specific adapter for correct/valid values. An error occurred while processing the discussion forum content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the configuration information for the object store is correct. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0080E: ObjectStoreConfigLoader: missing id for activities object store class "<className>". An error occurred while loading the discussion forum content store configuration. Verify that the configuration information for the object store is correct. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0081E: EventBrokerConfigLoader: the class "<className>" was not found. Check the configuration file, under the class attribute of the service for the correct Java classname. Or, check the classpath to make sure the class is visible. An error occurred while processing the discussion forum content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. Verify that the configuration information for the object store is correct. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0082E: Unable to access content reference for ACTIVITYUUID=<uuid>, NODEUUID=<uuid>, CONTENTREFUUID=<uuid>. An error occurred while transferring the content of the specified discussion forum from one content store to another. Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
CLFRV0084E: Error terminating activities object store. An error occurred while terminating the discussion forum content store. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0085E: Activities Schema Version Mismatch. Current database schema version is <version>. Activities requires version <version>. The system is expecting a certain schema version on the database. However, the database is reporting it has a different version. Upgrade the discussion forum codebase, or upgrade the database schema to match.
CLFRV0087E: The content of mime type: "<type>" or filename: "<fileName>" you tried to upload exceeded the size limit of <integer> bytes. Talk to your administrator about increasing the permitted upload size. The administrator set a size limit for the type of content a user tried to upload, either by mime type or by file name. Change the upload limits in the <sizeLimits> element in forum-config.xml or upload something smaller.
CLFRV0088E: Profile provider error. The Discussion Forum received an error querying the directory (i.e. LDAP) for a user or group. Ensure that the LDAP server configured for the WAS is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
CLFRV0090E: Profile provider error. The Discussion Forum received an error querying the directory (i.e. LDAP) for a user or group. Ensure that the LDAP server configured for the WAS is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
CLFRV0091E: Internal error. The Discussion Forum generated an exception. If the problem persists after restarting the Communities application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0092E: A short description could not be generated because the entry contains invalid HTML. The service tried to clean up user-submitted HTML rich text input using the JTidy library. The HTML was so malformed that JTidy could not clean it, and produced a null result. This error is a message printed to the user that indicates the service could not truncate the input HTML to produce a summary for display in the entry. The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
CLFRV0093E: Exception while executing JTidy on node: <uuid>. The service tried to clean up user-submitted HTML rich text input using the JTidy library. JTidy failed to finish executing on this HTML code before throwing an exception. The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
CLFRV0094E: Output from JTidy execution: <html>. This is a trace message that explains why JTidy failed to process some HTML input. This exception trace will inform you on how JTidy failed and whether it could be fixed.
CLFRV0095E: Internal error while executing JTidy on node: <uuid>. The service tried to clean up user-submitted HTML rich text input using the JTidy library. The HTML was so malformed that JTidy could not clean it, and produced a null result. The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
CLFRV0096E: Error fetching deleted items to purge. The scheduled TrashAutoPurge job received an exception fetching the items to purge. Restart the Discussion Forum application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0102E: Error closing email connections. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0105E: Error purging deleted items. The scheduled TrashAutoPurge job received an exception purging items. Restart the Discussion Forum application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0106E: Error sending notify message. Error when trying to send an email notification. Ensure that SMTP server configuration in the <email> element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0107E: Error composing HTML email message. Error received when trying to create an outbound email message from the server. Restart the Discussion Forum application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0108E: EmailNotifier: problems sending email. Most probable cause is due to using an invalid recipient email address. Or, the connection to the host is down. Or, there could also be authentication problems - check the user/password settings. Error received when trying to send outbound emails. Ensure that SMTP server configuration in the <email> element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0109E: Malformed email template, url=<url>.CLFRV0109E: Malformed email template, url=<url>. The web address specified is in an invalid URL syntax/format. Check forum-config.xml, email/outbound/templates/url and make sure the URLs are valid. You can validate them by typing the URLs directly into a browser.
CLFRV0110E: Error sending error message. Error received when trying to send an email error notification. Ensure that SMTP server configuration in the <email> element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0111E: Unable to connect to any of the <number> SMTP servers found on the MX records of the DNS server. The SMTP server is down, unreachable, or not responding. Ensure that the SMTP and DNS servers configured in the <email> element of forum-config.xml are reachable.
CLFRV0112E: Unable to get email template from url= <url>. Error trying to retrieve an email template from the given URL. Check forum-config.xml, email/outbound/templates/url and make sure the URLs are valid. You can validate them by typing the URLs directly into a browser.
CLFRV0114E: The email from "<sender>" with subject "<subject>" did not match either the create or add-to matching address expressions. The email will be deleted and not processed. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0115E: The email address="<emailAddress>" was not found in the directory. Unable to process the message. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0116E: Unable to find a member profile for the email "<emailAddress>". This user will not be added to the activity membership. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0117E: The activity you tried to email into (id=<uuid>) is deleted or no longer exists. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0118E: You need to update your configuration file version. Make sure you are not trying to use an old config file on a newer server or vice-versa. The version of forum-config.xml on the server differs from the version expected by the Discussion Forum. Ensure the version property of the <config> element in forum-config.xml matches the version expected by the Discussion Forum.
CLFRV0119E: ExecutionContext leak detected. The Discussion Forum application has detected a resource leak. Restart the Discussion Forum application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0120E: Internal Error, EC Count is null. The Discussion Forum application has detected a resource leak. Restart the Discussion Forum application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0121E: Error publishing event <event>. The Discussion Forum application received an error from the Event Broker service. Check that the <eventBroker> configuration specified in forum-config.xml is valid. Correct an invalid configuration. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0122E: Cannot find credentials for <name>. The system is configured to use J2C Authentication Aliases to store authentication data. The entry for <name> is missing. Go to Secure administration, applications, and infrastructure -> JAAS -> J2C authentication data in the WAS Integrated Solutions Console, and check whether there is an entry for <name>. If there is no entry, create an Authentication Alias for <name> by completing these steps:

  1. Shut down the WAS.

  2. Edit the security.xml file in <APPServer_HOME>/profiles/AppSrv01/config/cells/<cell>

  3. Find the authDataEntries entry with an alias that includes <name>. For example: <authDataEntries alias="text/name"> 2.5

  4. Replace "text/name" with "name"

  5. Save the security.xml file.

  6. Restart the WAS.

If there is an entry for <name>, verify that the user credentials are correct. If these steps do not fix the problem, then contact Customer Support.

CLFRV0123E: Profile provider error. The Discussion Forum received an error querying the directory (i.e. LDAP) for a user or group. Ensure that the LDAP server configured for the WAS is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
CLFRV0127W: Activities cannot determine host name. An error occurred while initializing the Statistics collection service. There was a problem with the server host name. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0131E: Activities Task Scheduler initialization error: <error>. Reason: An error occurred while initializing the Quartz scheduler. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0135E: Error executing event notification. Error received in the event broker. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0136E: Exiting the Aynch Notification Thread: event processing has been halted. Error received when the event broker thread is halted. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0137E: Error encountered processing events. Error received in the event broker when dispatching events. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0138E: The invoker should not be interrupted. Another thread interrupted the internal event broker. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0142E: Incorrect number of arguments. Please specify the configuration file to process. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0143E: Cannot locate configuration file {0}. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0144E: ConfigurationParser: Bad configuration. Config section defines more properties than values, or vice versa. Possible errant <property> element(s) without a "name" attribute(s). A configuration element in forum-config.xml or forum-jobs.xml is invalid. Enable debug tracing for com.ibm.openactivities.util, restart the application, and determine the invalid element from the trace.log output. Correct the element and restart the Discussion Forum application.
CLFRV0146E: Unable to refresh cached list of groups. The Discussion Forum received an exception refreshing its group cache. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0147E: Error initializing Activities. The Discussion Forum application received an error trying to start. The cause of the error will be found in the SystemOut.log file. Correct the error cause and restart the Discussion Forum application.
CLFRV0269E: Unable to connect to Domino database at url= <url> An error occurred while attempting to connect to the Discussion Forum's Domino content store. Verify that the Domino server is responding and that the URL is accessible.
CLFRV0270E: Error getting server URL for <name>. There was an error reading the server URL for the <name> service.

  1. Find the LotusConnections-config.xml file (in <App server home>/profiles/<name>/config/cells/<cell name>/LotusConnections-config)

  2. Make sure that the files exists and is readable by the WAS process.

  3. Make sure that the files contain the correct entry for the <name> service.

CLFRV0271E: Cannot find config variable directory <directory>. There was a problem reading variables that can be used in the forum-config.xml file. Make sure that the directory exists and is readable by the WAS.
CLFRV0272E: Cannot find <file> for config variables. There was a problem opening a file getting configuration variables. Make sure that the file exists and is readable by the WAS.
CLFRV0273W: Missing system setting for <name>. The IBM Connections configuration cannot find a definition for a variable named "name". Either, check the installation documentation for the variable to find the correct value for the variable, or add the variable with its correct value in the WAS admin console, Environment/websphere Variables page.
CLFRV0275E: Error loading config variables from <file>. There was a failure parsing variables in file.

  1. Make sure the file exists and is readable by the WAS.

  2. Replace the current copy with a back-up copy of the file.

CLFRV0276E: Too many errors encountered sending Activity Auto Completion notices, auto complete aborted. The server has given up trying to keep sending any more auto complete email notices. Ensure that SMTP server configuration in the <email> element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0277W: Warning, invalid parameter specified for the Activity Auto Completion notification max errors ({0}). Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
CLFRV0278E: Error generating list of activities eligible for auto completion. Error received querying the database to obtain a list of discussion forums that qualify to be autocompleted. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0279E: Error sending auto complete notification for activity UUID <uuid>. Error received when sending email about an auto complete notification. Additional information relating to the failure may be found in the SystemOut.log file. Ensure that SMTP server configuration in the <email> element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0280E: Error initializing the Activities Administrator email address. Some email functionality will be unavailable. No administrator email address was configured in forum-config.xml. Edit forum-config.xml and provide an administrator email address in the <activities-administrative-email-address> element.
CLFRV0281E: The content of mime type: "<mimeType>" or filename: "<fileName>" you tried to upload is not allowed by your administrator. The administrator set a size limit of zero bytes for the type of content a user tried to upload, either by mime type or by file name. Change the upload limits in the <sizeLimits> element in forum-config.xml.
CLFRV0282E: profile provider could not find member for <uuid>. The Discussion Forum profile application did not find a member by the given member ID. Contact Customer Support to report the incident.
CLFRV0285W: Purge expiration period (days) either not specified or invalid (<integer>). Defaulting to {1} days. The trashRetentionInDays configured for the TrashAutoPurgeJob in forum-jobs.xml is invalid. Add a value greater than 0 for the trashRetentionInDays configuration. Otherwise, trash older than 1 day will be purged when the job runs.
CLFRV0286E: Error sending activity auto completion notification. Error received when trying to send an email auto-completion notification. Ensure that SMTP server configuration in the <email> element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRV0287E: Error parsing administrator email address. The administrator email address configured in forum-config.xml is badly formatted. Edit forum-config.xml and provide an administrator email address in the correct format in the <activities-admin-email-address> element.
CLFRV0288E: No Activities Administrator email address has been configured. You must specify a value for "activities-admin-email-address". The administrator email address configured in forum-config.xml is empty. Edit forum-config.xml and provide an administrator email address in the correct format in the <activities-admin-email-address> element.
CLFRV0289W: Content removed by active content filter. The active content filter removed active content from user input. No action necessary.
CLFRV0290E: Error starting the active content filter. The active content filter received an error on start up. Contact Customer Support to report the incident.
CLFRV0291E: Error encountered with the active content filter. The active content filter received an error trying to filter text. Contact Customer Support to report the incident.
CLFRV0292W: Warning, it appears the ACF inserted an invalid character mid stream (<filteredText>). The active content filter inserted an invalid character in the filteredText as part of a filtering operation. No action necessary. The Discussion Forum application fixes up the invalid character.
CLFRV0293E: MemberProfile cannot be null. The data in a request to update a member profile in the database is null; possibly via a bad API request. Contact Customer Support to report the incident.
CLFRV0295E: Cannot update non-matching MemberProfiles. <uuid> is not <uuid>. In a request to one member profile with a new one, the member IDs do not match. Contact Customer Support to report the incident.
CLFRV0300E: The ArchiveService cannot export activities to the directory=<directory>; it is not writable. The exportActivities command of ArchiveService wsadmin object tried to archive the Discussion Forum to a directory that is not writable. Ensure that <directory> exists and that it is writable by the WAS.
CLFRV0301E: The required zip file "Activity-<uuid>.zip" was not found. This activity will not be imported, or a related activity link will be broken. The ArchiveService was requested to import activity with uuid <uuid>. However, the directory path that was also given to the ArchiveService does not contain the file Activity-<uuid>.zip. Ensure that the directory specified in an ArchiveService importActivities or createActivities command contains the archives for the desired discussion forums.
CLFRV0304E: The version of the archive you tried to import does not match the current DB schema. One cannot import activities into servers that are using different DB schemas. Migrate the archive to the matching schema version and then import the migrated archive.
CLFRV0306W: The user by email (or display name if it's a group) <member> was not found in the LDAP or the database! This means the activity being imported has a reference to a user that has changed emails, or has been removed from the LDAP. In other words, this email address is stale, and the activity is carrying around incongruent data. A member that was included in the imported activity cannot be found anymore. This might happen when switching LDAP servers, and the membership list is different. No action necessary. The imported activity will be imported, the missing member email address (or display name if a group) will be rewritten to "NOT_FOUND_<originalemail>". If this behavior is unexpected, you might want to investigate why members are missing in the new LDAP.
CLFRV0309E: The ArchiveService cannot export activities to the directory=<directory>; it is not a directory. The exportActivities command of ArchiveService wsadmin object tried to archive the Discussion Forum to a directory that is not writable. Ensure that <directory> exists and that it is writable by the WebSphere> Application Server.
CLFRV0310E: Error writing activity entry #<uuid> to the database. An ArchiveService import error received at the point where the Node of the Discussion Forum is written. Additional information relating to the failure may be found in the SystemOut.log file. If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
CLFRV0312E: Error writing activity node to the database. An ArchiveService import error received at the point where one of the nodes (entries) of the Discussion Forum is written. Additional information relating to the failure may be found in the SystemOut.log file. If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
CLFRV0315E: The ArchiveService cannot create the directory=<directory> for exporting activities. In an ArchiveService exportActivities command one specifies a directory where all the archive files will be written. In this case, the system cannot write out the specified directory to the file system. Manually create the <directory> on the file system and ensure it is writable by the WAS.
CLFRV0318E: The related activity with UUID=<uuid> already exists in the system. It is unclear whether the intention is to overwrite that activity with old data or not. Thus, it will be not imported. When a discussion forum has a related discussion forum link in it, the ArchiveService will automatically try to import the related discussion forum. However, if the ArchiveService is being run with "importActivities" which overwrites discussion forums rather than creating copies, then, it is unclear to the system whether the administrator also intentionally meant to overwrite related discussion forums since that related discussion forum was not explicitly passed in to be imported. If the administrator wishes to overwrite the related discussion forum, he can use the ArchiveService importActivites command to overwrite the related discussion forum.
CLFRV0319E: Error writing activity content entry "<name>". An ArchiveService import error received at the point where the content (files, attachments, etc) of one of the nodes (entries) of the discussion forum is written. Additional information relating to the failure may be found in the SystemOut.log file. If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
CLFRV0320E: Error importing activity with UUID=<uuid>. An ArchiveService import error. Additional information relating to the failure may be found in the SystemOut.log file. If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
CLFRV0321E: Error unpacking the archive. An ArchiveService import error received when unmarshalling the Zip archive. The Zip archive has been corrupted. If the cause of the corruption cannot be determined, contact Customer Support to report the incident.
CLFRV0327I: Status.
Informational message; no solution is needed.
CLFRV0328W: The {0} scheduler is not enabled in config. Check spelling. The specified scheduler is not enabled in the forum-config.xml file. Check the forum-config.xml file to make sure that the scheduler is enabled (change the 'enabled' attribute to true) and that the scheduler name is spelled correctly.
CLFRV0329E: The attempt to start the <name> scheduler failed. The Quartz scheduler did not start. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0330W: The {0} scheduler has already been stopped. The specified scheduler has already been stopped. No action required.
CLFRV0331I: The request to resume job {0} has been submitted. The request to resume the specified job has been submitted. Informational message; no solution is needed.
CLFRV0332W: The job {0} is not valid for the {1} scheduler. The job you are trying to run cannot be run on the specified scheduler. Run the job on the appropriate scheduler.
CLFRV0333I: The job {0} was removed. The specified job was removed from the scheduler. Informational message; no solution is needed.
CLFRV0334I: The {0} scheduler is running. The specified job is running. Informational message; no solution is needed.
CLFRV0335W: The job {0} is already running on the {1} scheduler. The specified job is already running on the specified scheduler. No action required.
CLFRV0336I: The request to pause job {0} has been submitted. The request to pause the specified job has been submitted. Informational message; no solution is needed.
CLFRV0337W: The {0} scheduler has already been started. The specified scheduler has already been started. No action required.
CLFRV0338I: The {0} scheduler was stopped successfully. The specified scheduler was stopped successfully. Informational message; no solution is needed.
CLFRV0339W: The {0} scheduler is disabled in config. The specified scheduler is not enabled in the forum-config.xml file. Enable the scheduler by changing the 'enabled' attribute for the scheduler to true in the forum-config.xml file.
CLFRV0340W: The request to pause job <name> failed. An error occurred while attempting to pause a job. Additional information relating to the failure may be found in the SystemOut.log file. No action is required.
CLFRV0341W: The job <name> has already been paused on the {1} scheduler. An attempt was made to pause a job that is already paused on a scheduler. Ensure that the job is running before attempting to pause it.
CLFRV0342I: The {0} scheduler is in standby mode. The specified scheduler is in standby mode. Informational message; no solution is needed.
CLFRV0343W: The request to resume job <name> failed. An error occurred while attempting to resume a previously paused job. Additional information relating to the failure may be found in the SystemOut.log file. No action is required.
CLFRV0344I: The {0} scheduler was started successfully. The specified scheduler started successfully. Informational message; no solution is needed.
CLFRV0345E: The attempt to stop the <name> scheduler failed. The Quartz scheduler did not stop. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum application, contact Customer Support to report the incident.
CLFRV0346I: The job {0} on the {1} scheduler has been paused. The specified job on the specified scheduler has been paused. Informational message; no solution is needed.
CLFRV0347E: Error exporting activity UUID={0}. An error occurred while trying to import the activity with the given UUID. Check previous log messages for the actual cause of the import failure. Resolve the error and re-run the import.
CLFRV0348W: The group "{0}" could not be loaded from LDAP or the database. Or, there might have been multiple matches for the same name in LDAP. This error is encountered when a group name is not found or multiple matches to the name are found in the configured directory. No action necessary. The activity will continue to be imported; an entry for "NOT_FOUND_" + the group name will be added to the member table and the membership list.
CLFRV0349E: Error locating profile: EXID mismatch, but email matches. email={0}, directory EXID={1}, db EXID={2}. This error is encountered when a member entry is found in the Discussion Forum database by the given email address, but the external identifier does not match the LDAP record. Determine if the person's record has changed in LDAP and if the two entries are really for the same person. If they are, use the Discussion Forum MemberService.synchMemberExtId (email address) command to update the Discussion Forum database with the correct id.
CLFRV0350E: Error: the group profile "{0}" could not be located in the Activities database. This error is encountered during LDAP synchronization. The group could not be located in the Discussion Forum database. Check the spelling of the group name.
CLFRV0351E: Error: the group profile "{0}" could not be located in the directory service. This error is encountered during LDAP synchronization. The group found in the Discussion Forum database could not be located in LDAP. Check the spelling of the group name.
CLFRV0352I: The group profile "{0}" has been synchronized with the directory services changing the external id from {0} to {1}. This message is encountered during LDAP synchronization. This record in the Discussion Forum database has been updated to match LDAP. Informational message; no solution is needed.
CLFRV0353E: Error: the member profile "{0}" could not be located in the Activities database. This error is encountered during LDAP synchronization. The person could not be located in the Discussion Forum database. Check the spelling of the email address.
CLFRV0354I: The member profile "{0}" has been synchronized with the directory services changing the external id from {0} to {1}. This message is encountered during LDAP synchronization. This record in the Discussion Forum database has been updated to match LDAP. Informational message; no solution is needed.
CLFRV0355I: The member profile "{0}" matches the directory service with external id {1}. This message is encountered during LDAP synchronization. This record is already synchronized. Informational message; no solution is needed.
CLFRV0356E: Error: the member profile "{0}" could not be located in the directory service. This error is encountered during LDAP synchronization. The person could not be located in LDAP. There is no match for the person by the given value. Check to see if the person exists in LDAP.
CLFRV0357E: Error: more than one profile was found for the key "{0}". Multiple entries identified by the <user identifier> have been found in the member profile table. One of the entries must be deleted. Contact Customer Support before proceeding.
CLFRV0358I: The group profile "{0}" matches the directory service with external id {1}. This message is encountered during LDAP synchronization. This record is already synchronized. Informational message; no solution is needed.
CLFRV0359E: Error locating member profile for <user identifier>, search type <internal search type>. The user's member profile could not be located in the directory. Verify that the LDAP configuration is correct. If this error is limited to a specific user, verify that the user can be located in LDAP given the identifier in the error message. The search type indicates what LDAP attribute is searched: 1=login, 2=email, 3=internal Discussion Forum member id (not used when searching LDAP).
CLFRV0360I: The {0} scheduler is not running. The specified scheduler is not running. Informational message; no solution is needed.
CLFRV0361E: The file "{0}" cannot be uploaded as it is a 0-byte file. An attempt was made to upload the specified file which has no content (zero bytes in size). Only files which have content may be uploaded. Ensure that the file contains data before uploading.
EJPIC0060E: There were no profiles detected for the installed WAS and managed node selected. There must be at least one profile on the existing managed node to continue. Retrieve the install logs for errors and make sure at least one profile exists on the existing managed node. Then try the installer again.

Table 2. Bookmarks error messages

Header Header Header
CLFROE: Error init connections config. IBM Connections configuration file has something wrong, or an unexpected exception occurs when parsing the IBM Connections configuration file. Check the detailed exception message below this error message in the log file to find the root cause. Check the configure file is correct.
CLFROE: Error when handling the multiple bookmarklet user request. This error is encountered if an unexpected exception occurs when handing the request of the common bookmarklet. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Error when parsing atom entry to object instance. The common bookmarklet received an Atom document that we could not parse because of invalid syntax. Usually this error is caused because Bookmarks/Communities/Activities/Blogs is not working. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to get content document from url {0}. Check the detailed exception message below this error message in the log file to find the root cause. Make sure the given url is valid and the remote server is available.
CLFROE: Failed to update the bookmark. This error is encountered if an unexpected exception occurs when updating the bookmark. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to delete the bookmark. This error is encountered if an unexpected exception occurs when deleting a bookmark from Bookmarks. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to post the bookmark to Dogear. This error is encountered if an unexpected exception occurs when adding a bookmark to Bookmarks. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to post the bookmark to one or more Communities. This error is encountered if an unexpected exception occurs when adding a bookmark to Communities. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to post the bookmark to one or more Activities. This error is encountered if an unexpected exception occurs when adding a bookmark to Activities. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to post the bookmark to one or more Blogs. This error is encountered if an unexpected exception occurs when adding a blog entry to Blogs. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to get count of the bookmark, url is: {0} This error is encountered if an unexpected exception occurs when querying the bookmark count from Bookmarks. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to validate the url. When user updates a bookmark, Common Bookmarklet must first validate the url to see if user already has another bookmark with the same url. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Service {0} is not correctly configured. Bookmarklet can not point to the correct server if attributes ""enabled"" and ""href"" are not set in the configure file. Please check IBM Connections configure file. IBM Connections configuration file has something wrong. Check the detailed exception message below this error message in the log file to find the root cause. Check the configure file is correct.
CLFROE: Failed to parse IBM Connections configure file IBM Connections configuration file has something wrong Check the detailed exception message below this error message in the log file to find the root cause. Check the configure file is correct.
CLFROE: Unable to find configure file for bookmarklet installer. The error is encountered if the configure file is not created. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Unable to load configure file for bookmarklet installer. The error is encountered if the configure file is not created or locked by other application. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to update the bookmarklet installer. This error is encountered if an IOException occurs when updating the installer. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to check bookmarklet installer. This error is encountered if an unexpected exception occurs when checking the installer. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: The parameter constraint shouldn't be null. This error is encountered if the given constraint is null. Check the detailed exception message below this error message in the log file to find the root cause. Check the user inputs.
CLFROE: Failed to add Credentials for invoking remote service, remote url is {0} This error is encountered if an URISyntaxException occurs when adding Credentials. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to apply constraints. This error is encountered if an unexpected exception occurs when applying the constraints. Check the detailed exception message below this error message in the log file to find the root cause. Check the user inputs.
CLFROE: Add search text operator or 'ps' or 'page' parameters failed. This error is encountered if an URIException occurs when adding 'ps' or 'page' parameter. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Parse redirect url failed. This error is encountered if an IRISyntaxException occurs when parsing the redirect url Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to build data entry for invoking remote service. The common bookmarklet creates xml document with the user inputs. The common bookmarklet creates xml document with the user inputs. This error is usually caused by the bad user inputs. Check the detailed exception message below this error message in the log file to find the root cause. Check the user inputs.
CLFROE: Failed to invoke remote service {0}, remote server return HTTP code: {1} This error is encountered if the remote service doesn't return the expected http code. Check the detailed exception message below this error message in the log file to find the root cause. Check the remote server is available.
CLFROE: Failed to edit bookmark, url is: {0} This error is encountered if an unexpected exception occurs when updating the bookmark. Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to delete bookmark, url is: {0} This error is encountered if an unexpected exception occurs when deleting a bookmark from Bookmarks . Check the detailed exception message below this error message in the log file to find the root cause.
CLFROE: Failed to publish bookmark via remote service. This error is encountered if an unexpected exception occurs when adding a bookmark to Bookmarks Check the detailed exception message below this error message in the log file to find the root cause.

Table 3. Blogs error messages

Message Cause Solution
Error instantiating <roller_classname>. Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
It appears that your factory does not implement <"CacheFactory interface>. Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
It appears that your mapper does not implement <RequestMapper interface>. Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
rollerversion.properties not found. The Blogs configuration file, “rollerversion.properties,” does not exist. Recover this file or reinstall IBM Connections Blogs.
Unable to instantiate cache factory <classname> falling back on default. Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
Unable to instantiate cache handler <Handler>. Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
Unable to instantiate request mapper <mapper>. Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
Unable to load smileys.properties. Specified file does not exist. Recover this file or reinstall IBM Connections Blogs.
Unable to lookup mail session. Check configuration. Cannot find JavaMail JNDI resource. Check WAS Blogs configuration to make sure the JNDI resource has been configured.



CLFRS0012E: Error processing referrer Not identifiable without more information. Report this problem to Customer Support.
CLFRS0019E: Error deleting the resource Not identifiable without more information. Report this problem to Customer Support.
CLFRS0025E: Error getting weblogs default page Not identifiable without more information. Report this problem to Customer Support.
CLFRS0030E: Content-Type error Not identifiable without more information. Report this problem to Customer Support.
CLFRS0031E: Error processing subscription entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0040E: Error loading model objects for page Not identifiable without more information. Report this problem to Customer Support.
CLFRS0049E: Error updating the resource Not identifiable without more information. Report this problem to Customer Support.
CLFRS0050E: Error retrieving the resource Not identifiable without more information. Report this problem to Customer Support.
CLFRS0055E: WaltzUserAutoProvision.getUserDetailsByLoggedInUser {0} failed. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0057E: Error adding a media-link entry to the collection feed Not identifiable without more information. Report this problem to Customer Support.
CLFRS0059E: Error retrieving accepted content type ranges Not identifiable without more information. Report this problem to Customer Support.
CLFRS0060E: Error getting key ''{0}'' Not identifiable without more information. Report this problem to Customer Support.
CLFRS0062E: Parent association is null Not identifiable without more information. Report this problem to Customer Support.
CLFRS0070E: Error while updating master search index Not identifiable without more information. Report this problem to Customer Support.
CLFRS0071E: Error posting the new entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0074E: Planet cache directory is not writable Not identifiable without more information. Report this problem to Customer Support.
CLFRS0080E: Error writing resource file Not identifiable without more information. Report this problem to Customer Support.
CLFRS0082E: Error processing linkback Not identifiable without more information. Report this problem to Customer Support.
CLFRS0087E: Error ending transaction SQL Transaction commit failed. This could be database SQL execution error. Please wait and try again later.
CLFRS0089E: Parsing exception Not identifiable without more information. Report this problem to Customer Support.
CLFRS0090E: Error during rendering for page {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0091E: Error posting the new media-link entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0101E: Error adding an entry to the collection feed Not identifiable without more information. Report this problem to Customer Support.
CLFRS0102E: Error deleting the blog Not identifiable without more information. Report this problem to Customer Support.
CLFRS0106E: Error checking user authorization level for blog Not identifiable without more information. Report this problem to Customer Support.
CLFRS0107E: Error adding a blog entry to the collection feed Not identifiable without more information. Report this problem to Customer Support.
CLFRS0108E: Error message: {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0112E: Error initializing iBatis SQL Transaction commit failed. This could be database SQL execution error. Please wait and try again later.
CLFRS0113E: Error adding a report entry to the collection feed Not identifiable without more information. Report this problem to Customer Support.
CLFRS0116E: Error deleting the comment Not identifiable without more information. Report this problem to Customer Support.
CLFRS0125E: Unable to create planet cache directory Not identifiable without more information. Report this problem to Customer Support.
CLFRS0131E: Error retrieving the entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0133E: Error deleting the entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0136E: Error looking up website object The blog specified does not exist. Informational message. No solution is needed.
CLFRS0139E: Error updating the entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0140E: Error adding a flagged entry to the collection feed Not identifiable without more information. Report this problem to Customer Support.
CLFRS0143E: Error with the active content filter Not identifiable without more information. Report this problem to Customer Support.
CLFRS0152E: Unexpected exception Not identifiable without more information. Report this problem to Customer Support.
CLFRS0154E: Error retrieving the resource to delete Not identifiable without more information. Report this problem to Customer Support.
CLFRS0160E: NamingException during websphere InitialContext retrieval Not identifiable without more information. Report this problem to Customer Support.
CLFRS0174E: Error retrieving list of collections for user Not identifiable without more information. Report this problem to Customer Support.
CLFRS0176E: Error committing transaction the process will be rolled back Not identifiable without more information. Report this problem to Customer Support.
CLFRS0178E: Error retrieving list of categories for weblog Not identifiable without more information. Report this problem to Customer Support.
CLFRS0191E: Error parsing referrer.robotCheck.userAgentPattern value ''{0}''. Robots will not be filtered. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0192E: Could not find renderer for page {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0195E: Error getting weblog entry data for entry [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0196E: Error fetching most commented weblog entry list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0197E: Error retrieving MonthMap Not identifiable without more information. Report this problem to Customer Support.
CLFRS0199E: Error fetching most recommended weblog list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0200E: Error while processing ping queue Not identifiable without more information. Report this problem to Customer Support.
CLFRS0201E: Error looking up weblog [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0203E: Error in action Not identifiable without more information. Report this problem to Customer Support.
CLFRS0204E: Error initializing calendar tag Not identifiable without more information. Report this problem to Customer Support.
CLFRS0205E: Error scheduling task Not identifiable without more information. Report this problem to Customer Support.
CLFRS0206E: Error getting today's referrers Not identifiable without more information. Report this problem to Customer Support.
CLFRS0207E: Error occurred while attempting to read theme template file [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0209E: Could not read theme template file [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0210E: Error determining site URL Not identifiable without more information. Report this problem to Customer Support.
CLFRS0213E: Error rendering for weblog [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0214E: SQL error occurred when upgrading database to version 3.0.0 Not identifiable without more information. Report this problem to Customer Support.
CLFRS0215E: It appears that the handler does not implement the CacheHandler interface Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0216E: Error occurred when optimizing index Not identifiable without more information. Report this problem to Customer Support.
CLFRS0218E: Error getting page from request Not identifiable without more information. Report this problem to Customer Support.
CLFRS0220E: Error getting weblog category by id from request Not identifiable without more information. Report this problem to Customer Support.
CLFRS0221E: Error removing invalid MediaCast attributes Not identifiable without more information. Report this problem to Customer Support.
CLFRS0222E: Error getting bookmark from request Not identifiable without more information. Report this problem to Customer Support.
CLFRS0223E: Error downloading blacklist Not identifiable without more information. Report this problem to Customer Support.
CLFRS0224E: Error getting child folders Not identifiable without more information. Report this problem to Customer Support.
CLFRS0225E: Unable to instantiate cache factory [{0}], falling back on default Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0226E: Error writing resource file Not identifiable without more information. Report this problem to Customer Support.
CLFRS0227E: Error importing bookmarks Not identifiable without more information. Report this problem to Customer Support.
CLFRS0229E: Error updating comments Not identifiable without more information. Report this problem to Customer Support.
CLFRS0230E: Error in MetaweblogAPIHandler.getCategories Not identifiable without more information. Report this problem to Customer Support.
CLFRS0231E: Error forming Struts URL Not identifiable without more information. Report this problem to Customer Support.
CLFRS0232E: Error getting aggregation Not identifiable without more information. Report this problem to Customer Support.
CLFRS0233E: Error occurred during rendering for page [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0234E: Error occurred when adding document to index Not identifiable without more information. Report this problem to Customer Support.
CLFRS0235E: Error occurred while checking MediaCast URL [{0}]: {1} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0237E: Error during rendering for RSD template Not identifiable without more information. Report this problem to Customer Support.
CLFRS0238E: Unable to parse configured ping variant [{0}]. Skipping this variant. Check your setting of the property [{1}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0239E: Error setting default editor page for weblog Not identifiable without more information. Report this problem to Customer Support.
CLFRS0240E: Error getting folder from request Not identifiable without more information. Report this problem to Customer Support.
CLFRS0241E: HTTP response message [{0}] returns from MediaCast URL Not identifiable without more information. Report this problem to Customer Support.
CLFRS0243E: Error from plugin: {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0244E: Error calling function shutdown() Not identifiable without more information. Report this problem to Customer Support.
CLFRS0245E: Error saving comment rating Not identifiable without more information. Report this problem to Customer Support.
CLFRS0246E: Error occurred when updating last modified date to index Not identifiable without more information. Report this problem to Customer Support.
CLFRS0247E: Error getting entry month map Not identifiable without more information. Report this problem to Customer Support.
CLFRS0248E: It appears that the mapper does not implement the RequestMapper interface Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0249E: Error toggling linkback display Not identifiable without more information. Report this problem to Customer Support.
CLFRS0250E: Error calling function release() Not identifiable without more information. Report this problem to Customer Support.
CLFRS0252E: Could not find renderer for planet RSS Not identifiable without more information. Report this problem to Customer Support.
CLFRS0253E: Error loading model objects for page Not identifiable without more information. Report this problem to Customer Support.
CLFRS0254E: Error fetching weblog tags list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0255E: Error in BloggerAPIHander.getInfo Not identifiable without more information. Report this problem to Customer Support.
CLFRS0256E: RollerSession.synchUserProfile {0} failed. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0257E: Aborting collection of Technorati rankings.\ntechnorati.license not found at root of classpath.\nGet license at http://technorati.com/developers/apikey.html\nPut the license string in a file called technorati.license.\nAnd place that file at the root of Roller's classpath.\nFor example, in the /WEB-INF/classes directory. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0258E: Could not lookup current database version Not identifiable without more information. Report this problem to Customer Support.
CLFRS0259E: Error getting previous entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0260E: Error in BloggerAPIHander.getRecentPosts Not identifiable without more information. Report this problem to Customer Support.
CLFRS0261E: Unable to instantiate editor [{0}] Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0262E: Error setting default editor page for weblog Not identifiable without more information. Report this problem to Customer Support.
CLFRS0263E: Unable to load smileys.properties Specified file does not exist. Recover this file or reinstall IBM Connections Blogs.
CLFRS0264E: Error fetching annoucement weblog entries Not identifiable without more information. Report this problem to Customer Support.
CLFRS0265E: Error occurred when reading theme {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0266E: PingConfig property [{0}] is not an integer value. Using default value: {1} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0267E: Error batch delete documents from index for re-indexing Not identifiable without more information. Report this problem to Customer Support.
CLFRS0268E: Unable to instantiate request mapper [{0}] Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0269E: Forward specified in XML menu file not found: {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0270E: SQL error occurred when upgrading database to version 2.1.0 Not identifiable without more information. Report this problem to Customer Support.
CLFRS0271E: Error fetching users by letter Not identifiable without more information. Report this problem to Customer Support.
CLFRS0272E: Error in BloggerAPIHander.editPost Not identifiable without more information. Report this problem to Customer Support.
CLFRS0273E: Unable to parse configured initial ping target [{0}]. Skipping this target. Check your setting of the property [{1}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0275E: Error during rendering for page [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0277E: Error in action Not identifiable without more information. Report this problem to Customer Support.
CLFRS0279E: SQL error occurred when upgrading database to version 2.0.0 Not identifiable without more information. Report this problem to Customer Support.
CLFRS0280E: Error getting recent entries Not identifiable without more information. Report this problem to Customer Support.
CLFRS0281E: Error saving comment Not identifiable without more information. Report this problem to Customer Support.
CLFRS0282E: Unable to instantiate renderer factory [{0}] Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0284E: Error fetching weblog handle character map Not identifiable without more information. Report this problem to Customer Support.
CLFRS0285E: Internal error validating user Not identifiable without more information. Report this problem to Customer Support.
CLFRS0286E: Exception in tag Not identifiable without more information. Report this problem to Customer Support.
CLFRS0287E: Error occurred during rendering for planet RSS Not identifiable without more information. Report this problem to Customer Support.
CLFRS0288E: Error in MetaweblogAPIHandler.getPost Not identifiable without more information. Report this problem to Customer Support.
CLFRS0290E: Error in blogger.deletePost: {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0292E: Error creating authenticator, using default Not identifiable without more information. Report this problem to Customer Support.
CLFRS0293E: Error ranking subscriptions Not identifiable without more information. Report this problem to Customer Support.
CLFRS0294E: Cannot synchronize websites. Absolute URL not specified in Blogs configuration Not identifiable without more information. Report this problem to Customer Support.
CLFRS0295E: Error occurred when getting ThreadManager Not identifiable without more information. Report this problem to Customer Support.
CLFRS0300E: Error getting ranked blogs Not identifiable without more information. Report this problem to Customer Support.
CLFRS0301E: Error executing job. Thread Not identifiable without more information. Report this problem to Customer Support.
CLFRS0302E: Error fetching username character map Not identifiable without more information. Report this problem to Customer Support.
CLFRS0303E: Error saving entry rating Not identifiable without more information. Report this problem to Customer Support.
CLFRS0304E: Plugin is not found: Emoticons Not identifiable without more information. Report this problem to Customer Support.
CLFRS0305E: Error occurred when initiating messageModel Not identifiable without more information. Report this problem to Customer Support.
CLFRS0306E: Unexpected exception processing ping queue Not identifiable without more information. Report this problem to Customer Support.
CLFRS0307E: Error creating toggle-linkback URL Not identifiable without more information. Report this problem to Customer Support.
CLFRS0308E: Error getting default page Not identifiable without more information. Report this problem to Customer Support.
CLFRS0309E: Error getting next entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0310E: Error fetching user list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0311E: Could not find renderer for page [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0312E: Error creating URL Not identifiable without more information. Report this problem to Customer Support.
CLFRS0313E: SQL error occurred when upgrading database to version 1.3.0 Not identifiable without more information. Report this problem to Customer Support.
CLFRS0314E: Error getting default page for preview Not identifiable without more information. Report this problem to Customer Support.
CLFRS0315E: Error instantiating {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0316E: Error loading model for page Not identifiable without more information. Report this problem to Customer Support.
CLFRS0317E: Database problem occurred when trying to load resource [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0318E: Error getting user in menu model Not identifiable without more information. Report this problem to Customer Support.
CLFRS0319E: Error fetching weblog entries list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0320E: Error in BloggerAPIHander.newPost Not identifiable without more information. Report this problem to Customer Support.
CLFRS0321E: Operation is interrupted. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0322E: Error getting weblog category by name from request Not identifiable without more information. Report this problem to Customer Support.
CLFRS0323E: Error in BloggerAPIHander.getUsersBlogs Not identifiable without more information. Report this problem to Customer Support.
CLFRS0324E: It appears that the factory does not implement the RendererFactory interface Not identifiable without more information. Report this problem to Customer Support.
CLFRS0325E: Error in BloggerAPIHander.setTemplate Not identifiable without more information. Report this problem to Customer Support.
CLFRS0326E: Error fetching notification count Not identifiable without more information. Report this problem to Customer Support.
CLFRS0328E: Error occurred when closing writer Not identifiable without more information. Report this problem to Customer Support.
CLFRS0329E: Error persisting updated hit counts Not identifiable without more information. Report this problem to Customer Support.
CLFRS0330E: Error in BloggerAPIHander.getTemplate Not identifiable without more information. Report this problem to Customer Support.
CLFRS0332E: Error occurred when searching index Not identifiable without more information. Report this problem to Customer Support.
CLFRS0333E: Error with operation [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0334E: Error fetching featured weblog entry list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0335E: Error in action: {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0336E: Error getting total hit count Not identifiable without more information. Report this problem to Customer Support.
CLFRS0336E: Error getting total hit count Not identifiable without more information. Report this problem to Customer Support.
CLFRS0337E: Error getting weblog entry: anchor Not identifiable without more information. Report this problem to Customer Support.
CLFRS0338E: Error fetching most commented weblog list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0339E: Error fetching weblog count Not identifiable without more information. Report this problem to Customer Support.
CLFRS0340E: Error getting recent comments Not identifiable without more information. Report this problem to Customer Support.
CLFRS0342E: Initialization of XML-RPC servlet failed Not identifiable without more information. Report this problem to Customer Support.
CLFRS0343E: Error in MetaweblogAPIHandler.newPost Not identifiable without more information. Report this problem to Customer Support.
CLFRS0344E: Error in MetaweblogAPIHandler.editPost Not identifiable without more information. Report this problem to Customer Support.
CLFRS0346E: Error fetching favorites list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0347E: Error occurred when closing reader Not identifiable without more information. Report this problem to Customer Support.
CLFRS0348E: Unable to instantiate cache handler [{0}] Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0349E: Error occurred when fetching last update time stamp from index Not identifiable without more information. Report this problem to Customer Support.
CLFRS0350E: Error fetching comment list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0351E: Error initializing plugins Not identifiable without more information. Report this problem to Customer Support.
CLFRS0354E: rollerversion.properties is not found The Blogs configuration file, “rollerversion.properties,” does not exist. Recover this file or reinstall IBM Connections Blogs.
CLFRS0355E: Error occurred while checking for referrer Not identifiable without more information. Report this problem to Customer Support.
CLFRS0356E: Unable to find user with email Not identifiable without more information. Report this problem to Customer Support.
CLFRS0357E: It appears that the factory does not implement the CacheFactory interface Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0358E: Could not find renderer for RSD template Not identifiable without more information. Report this problem to Customer Support.
CLFRS0359E: Error in MetaweblogAPIHandler.getRecentPosts Not identifiable without more information. Report this problem to Customer Support.
CLFRS0360E: Error instantiating task Not identifiable without more information. Report this problem to Customer Support.
CLFRS0364E: Error getting managers Not identifiable without more information. Report this problem to Customer Support.
CLFRS0365E: Error parsing runtime configuration definitions Not identifiable without more information. Report this problem to Customer Support.
CLFRS0368E: Error fetching recent notification list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0369E: Unknown exception creating renderer for template [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0370E: Calendar tag exception Not identifiable without more information. Report this problem to Customer Support.
CLFRS0371E: Could not load a blacklist file from anywhere. This means blacklist checking is disabled. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0374E: Error committing referrer Not identifiable without more information. Report this problem to Customer Support.
CLFRS0375E: Error fetching featured weblog list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0376E: Error fetching site tags list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0378E: Error loading weblog custom models Not identifiable without more information. Report this problem to Customer Support.
CLFRS0379E: Error fetching categories Not identifiable without more information. Report this problem to Customer Support.
CLFRS0380E: ThemeResourceLoader Error: {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0381E: PingConfig property [{0}] is outside the required range ({1}, {2}). Use default value: {3} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0382E: Error saving website Not identifiable without more information. Report this problem to Customer Support.
CLFRS0383E: Error fetching weblog list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0385E: Error fetching folder for weblog Not identifiable without more information. Report this problem to Customer Support.
CLFRS0386E: Error creating preview request Not identifiable without more information. Report this problem to Customer Support.
CLFRS0387E: Error fetching most recommended weblog entry list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0388E: Error occurred when deleting document from index Not identifiable without more information. Report this problem to Customer Support.
CLFRS0389E: Notification email not sent due to Blogs configuration or mail server problem. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0391E: Error refreshing entries Not identifiable without more information. Report this problem to Customer Support.
CLFRS0392E: Error sorting folders Not identifiable without more information. Report this problem to Customer Support.
CLFRS0393E: It appears that the editor does not implement the weblogEntryEditor interface Not identifiable without more information. Report this problem to Customer Support.
CLFRS0394E: Error getting weblog entry [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0395E: Notification email not sent. Blogs site URL is malformed. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0395E: Notification email not sent. Blogs site URL is malformed. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0396E: Notification email not sent. Blogs mail session is not configured properly. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0397E: Error fetching categories for path: {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0398E: Error loading runtime configuration definitions file Not identifiable without more information. Report this problem to Customer Support.
CLFRS0399E: Error getting weblog page [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0400E: Error getting comment with id [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0401E: Error updating flagged inappropriate entry Not identifiable without more information. Report this problem to Customer Support.
CLFRS0403E: Error getting weblog category [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0404E: Error getting user object Not identifiable without more information. Report this problem to Customer Support.
CLFRS0405E: Error fetching weblog data Not identifiable without more information. Report this problem to Customer Support.
CLFRS0406E: Error getting decorator[{0}] for template {1} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0408E: Error adding banned IP to file Not identifiable without more information. Report this problem to Customer Support.
CLFRS0409E: Error closing stream Not identifiable without more information. Report this problem to Customer Support.
CLFRS0410E: Error occurred when creating writer Not identifiable without more information. Report this problem to Customer Support.
CLFRS0411E: Unable to get planet manager Not identifiable without more information. Report this problem to Customer Support.
CLFRS0412E: Error getting weblogs default page Not identifiable without more information. Report this problem to Customer Support.
CLFRS0414E: Error looking up theme [{0}] Not identifiable without more information. Report this problem to Customer Support.
CLFRS0415E: Error fetching weblog entry tags list Not identifiable without more information. Report this problem to Customer Support.
CLFRS0416E: Failed to instantiate a cache factory Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0417E: Failed to instantiate the implementation Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0418E: Initialization of ServletContextListener implementation class failed Cannot find specified class. Make sure all libraries are available or reinstall IBM Connections Blogs.
CLFRS0419E: Failed to initialize runtime configuration properties. Please check that the database has been upgraded. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0420E: Fatal message: {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS0421E: The Blogs database version does not match current version of Blogs. Please check the database and make sure to use the correct version. Not identifiable without more information. Report this problem to Customer Support.
CLFRS0422E: Cannot access footer url Not identifiable without more information. Report this problem to Customer Support.
CLFRS1755E: Error connecting remote search EJB Not identifiable without more information. Report this problem to Customer Support.
CLFRS1756E: Error removing community blog. Resource ID {0} Not identifiable without more information. Report this problem to Customer Support.
CLFRS1759E: Error retrieving categories document Not identifiable without more information. Report this problem to Customer Support.
CLFRS1760E: Profile provider is null Not identifiable without more information. Report this problem to Customer Support.
CLFRS1762E: Error performing member update Not identifiable without more information. Report this problem to Customer Support.
CLFRS1765E: Error locating search EJB Not identifiable without more information. Report this problem to Customer Support.
CLFRS1766E: Error creating search EJB Not identifiable without more information. Report this problem to Customer Support.
CLFRS1767E: Error updating community blog visibility. Resource ID {0}, title {1} Not identifiable without more information. Report this problem to Customer Support.
CLFRS1769E: Error getting weblog entry comment with id [{0}] Not identifiable without more information. Report this problem to Customer Support.

Table 4. Installation error messages without codes

Message Cause Solution
At least one application must be selected for install. The installer requires the selection of at least one application for both production and pilot installations. Please choose at least one application.
At least one application must be selected for uninstall. The installer requires the selection of at least one application for both production and pilot uninstallations. Please choose at least one application.
Cannot connect to database using provided settings, please check again! The installer validates a JDBC connection to ensure that the Connections application installed will be able to communicate with the database. This connection has the following requirements:

  1. JDBC Driver Library: A valid path to the jars that provide JDBC connectivity.

  2. Application User Account: A valid user account for the database that hosts the Connections application data. This is the user that the Connections application will use.

  3. Application User Account password: The password for the application user account.

  4. Host: Host name of the machine that has the database server.

  5. Port: Port number used to connect to the database.

  6. Database name: The name of the database.

Make sure the correct values have been provided.
db2jcc_license_cu.jar and db2jcc.jar does not exists in <directory path> The installer validates a JDBC connection to ensure that the Connections application installed will be able to communicate with the database. This error message is stating that a valid JDBC connection is not possible as the required DB2 jars are not located at the location specified. In the install panel requesting JDBC connection information, ensure that the path leading to the db2jcc_license_cu and db2jcc jars is valid.
ojdbc14.jar does not exists in <directory path> The installer validates a JDBC connection to ensure that the Connections application installed will be able to communicate with the database. This error message is stating that a valid JDBC connection is not possible as a required Oracle jar is not located at the location specified. In the install panel requesting JDBC connection information, ensure that the path leading to the ojdbc14.jar is correct.
Uninstall of the component: <Connections offering name> has failed or this component has already been uninstalled. The process of removing a Connections application has failed. Please retrieve the uninstall log, lcuninstalllog.txt, from the temp directory. Locate errors and contact support.
The user did not provide the mandatory input parameter WAS userid in the command line. The update installer will not continue and will print out the command usage help on screen. User has to add userid to the command line.

Table 5. IBM HTTP Server error messages

Message Cause Solution
ERROR: lib_stream: openStream: Failed in r_gsk_secure_soc_init: GSK_ERROR_BAD_CERT(gsk rc = 414) If you see a 500 error when using HTTPS over the IBM HTTP Server to get to an application, HTTPS might not be configured correctly with the WAS plug-in. The WAS SSL certificate might not be trusted by the WAS plug-in configured for the IBM HTTP Server. If this error occurs, check both your IBM HTTP Server and WAS logs to see if there is a GSK_ERROR. If the logs do not contain errors, examine the plug-in logs located in the following directory:

C:\ibm\HTTPServer\Plugins\logs\webserver1\http_plugin.log

To fix this error, follow the instructions in the topic, Configure the IBM HTTP Server for SSL.

Table 6. IBM Lotus Connections Portlets for IBM WebSphere Portal error messages

Message Cause Solution
CLFNF6001E: Could not store portlet preferences

CLFNF6002E: Error storing slot id

CLFNF6003E: There was an error with a name

CLFNF6004E: JSONTranslator could not modify portlet preferences

CLFNF6005E: There was an error with the portlet service

CLFNF6006E: Error creating credential

CLFNF6007E: Name not found

CLFNF6008E: There was an error serializing an id

CLFNF6009E: Could not get custom views

CLFNF6010E: Query was stored in a bad format: {0}

CLFNF6011E: Error getting user credentials

Related concepts
Troubleshooting checklist

Related reference
Communities administrative commands


   

 

});