IBM Connections 4: Troubleshooting and Mobile Support

Troubleshoot checklist

The following questions can help you to identify the source of a problem:

  1. Is your configuration supported?

    Review the IBM Connections system requirements topic.

    Refer to the Deployment options topic for information about the supported deployment scenarios.

  2. Have any error messages been issued? See Error codes for a list of possible error messages and descriptions. Review the issues listed in the Troubleshoot tips section to see if the problem you are having is addressed there.

  3. Have you applied the latest product fixes? See Get product fixes for more details.

  4. Have you searched knowledge bases for a related problem report? See Search knowledge bases for more details.

  5. If the checklist does not guide you to a resolution, collect additional diagnostic data to send to IBM Support. This data is necessary for IBM Support to effectively troubleshoot and assist you in resolving the problem. Do one of the following:

    • Use the IBM Support Assistant (ISA) workbench or ISA Lite tool to quickly gather the correct diagnostic data. See Resolve a problem.

    • If you do not want to use the ISA tools, see Collect data.
      Tip: It is easier and more efficient to use ISA to complete this task.

Get product fixes

A product fix might be available to resolve your problem.

To determine which version of the product is currently installed, access one of the IBM Connections applications from a web browser, and then click the About link in the page footer. The version information is on the About page. You can get fixes by following these steps:

  1. Determine which fix you need. Review the IBM Connections fix list by going to the following external web site: http://www.ibm.com/support/docview.wss?uid=swg27019738

  2. Download the fix to install. See Downloading fixes.

  3. Install the fix. See Installing fixes.

Search knowledge bases

You can often find solutions to problems by searching IBM knowledge bases. Learn how to optimize your results by using available resources, support tools, and search methods and how to receive automatic updates.


Available technical resources

In addition to this product documentation, the following technical resources are available to help you answer questions and resolve problems:


Search with support tools

The following tools are available to help you search IBM knowledge bases:


Search tips

The following resources describe how to optimize search results:


Receive automatic updates

You can receive automatic updates in the following ways:

Troubleshoot tips

Review the topics in this section to see if your issue is addressed. Or consult the error logs to find information about the error you are seeing.


IBM Connections log file

IBM Connections writes messages to the SystemOut.log file. Refer to this file if you encounter errors after installing an IBM Connections application or if you encounter unexpected behavior in an application.

The SystemOut.log file is stored in the following directory:

Messages written to the log use the following syntax:

 <Application prefix><Error code><Message level code>

...where:

For example:

CLFRA0299I
CLFRA identifies the message as coming from the Activities application; 0299 is the error code; I indicates that the message is an Info level message.


Error codes

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


Activities error messages

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

The following Activities error messages are generated by IBM Connections:

Table 3. Activities error messages

Message Cause Solution
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 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 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 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 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 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 the server level WebSphere Application Server 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 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 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 the parameter to the fetchMembers command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0027E: Error deleting profile    
CLFRA0028E: Error updating access control list. The AccessControlService wsadmin object received an exception executing an access modification command. Verify 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 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 the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
CLFRA0031E: Error locating Scheduler. cannot create Scheduler MBean.    
CLFRA0032E: Error updating profile. The MemberService wsadmin object received an exception executing a updateMember command. Verify 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 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 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 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.
CLFRA0037E: Error initializing Activities JMX support: failed to register {0}    
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 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 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 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 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 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 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 WebSphere Application Server 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 WebSphere Application Server 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 Security > Global security > JAAS > J2C authentication data in the WebSphere Application Server 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 WebSphere Application Server.

  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 WebSphere Application Server.
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 WebSphere Application Server 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 LotusConnections-config.xml (in <App server home>/profiles/<name>/config/cells/<cell name>/LotusConnections-config)

  2. Make sure the files exists and is readable by the WebSphere Application Server 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 WebSphere Application Server.
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 WebSphere Application Server.
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 WebSphere Application Server Integrated Solutions 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 WebSphere Application Server.

  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.
CLFRA0296E: Error performing UTF-8 character validation: {0}    
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 WebSphere Application Server.
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 WebSphere Application Server.
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 WebSphere Application Server.
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.
CLFRA0323E: Duplicate member profile with secondary key "{0}" has been found, no sync operation was taken.    
CLFRA0324E: Member profile with secondary key "{0}" has not been found in the "{1}".    
CLFRA0326E: More than one member profile matches the search for {0}.    
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.
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.
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.
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.
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.
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.
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.
CLFRA0347E: Error exporting activity UUID={0}. An error occurred while trying to export the activity with the given UUID. Check previous log messages for the actual cause of the export failure. Resolve the error and re-run the export.
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.
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 profile for the referenced user and ensure that the spelling of the supplied look-up field matches.
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.
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).
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.
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 the mail service is configured properly. Additional information relating to the failure can be found in the SystemOut.log file.
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 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 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 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.
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 remaining 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 remaining 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 remaining 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 remaining 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.
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.
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 remaining 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 remaining 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.
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.
CLFRA0392E: The path "{0}" is not a directory or it does not exist. The path given was not a directory path Provide a correct directory path
CLFRA0393E: Error. The value given for "{0}" in LotusConnections-config.xml is invalid. An error occurred while retrieving the specified value from Lotusconnections-config.xml. Check that the config file has a suitable value for the parameter.
CLFRA0394E: Access control for community activities cannot be altered. Update the membership in the community instead. Activity UUID = {0} Tried to update the ACL on a community activity By design, the ACL for a community activity should be changed in the Community directly not thru Activities
CLFRA0395E: Community pseudo groups are not valid members. They may not be used for access control operations. Attempted to use a pseudo-group as an ACL object By design, the ACL for a community activity should be changed in the Community directly not thru Activities
CLFRA0396E: Error updating last login time for {0} An error occurred updating the last login time for the indicated user. Check Systemout.log for additional information.
CLFRA0399E: Error {0} received accessing Communities server The Communities is down or unresponsive Check that the server is correctly configured with a valid URL to Communities, and that the Communities server is up and running
CLFRA0403E: Error: An error occurred while updating the login names for user "{0}". The internal error is {1} Additional details of the error are given in the error message. 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.
CLFRA0406E: An error occurred while propagating an event. The Activities application 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.
CLFRA0407E: Error writing ''{0}''. Generic error writing a file to the filesystem Usually, this error will be followed by a more specific message about an exact problem writing the file
CLFRA0408E: Could not create the directory for writing ''{0}''. Could not write the directory to the filesystem Check the given path points to a location the system has the appropiate permissions to write to
CLFRA0409E: Error closing streams when writing SyncedResourceInfo.xml Generic error writing a file to the filesystem Usually results in problems when files are locked or deleted by another process
CLFRA0410E: The given path ''{0}'' is a directory. Please specify a filename. The given path is a directory Make sure to specify a path pointing to a file and not a directory
CLFRA0411E: Could not write ''{0}''; The directory or given path is not writable. The given path is not a writable directory. Make sure to specify a directory path pointing to a directory for which the user has write access.
CLFRA0439I: Processing ''remote.app.transfer'' community event from old community ExId: ''{0}'', to new community ExId: ''{1}'' This message is used for logging purpose when moving a set of activities from one community to another (as is the case for a 'sync' event) if debugging/logging is enabled. N/A
CLFRA0442E: A fatal error occurred while sending a notification message.    
CLFRA0445E: unable to download the file: {0} {1}. An error occurred while downloading a file attachment. The specified file could not be found or an error occurred while it was being read.
CLFRA0446E: Unknown sync event type: "{0}" A communities event was not recognized by the Acitvities server. Check that Activities is not subscribed to listen to events it does not support
CLFRA0447E: The communities service is currently unavailable. Check that it is running. This message is logged when fetching communities by name and directory service is not available. Need to make sure that the directory service is available.
CLFRA0449E: The user with external ID "{0}" is not authorized to access the Activity with UUID {1}. This error message is thrown with access control exception because of the user with a given external Id does not have access to the activity. Access to the activity must be granted to the user.
CLFRA0450E: An internal error occurred during the AntiVirus scan of Activities object store content item "{0}". Make sure that the AntiVirus server is running and that you can access it, and then try to upload the item again. An error occurred while attempting to virus-scan a file being uploaded. Verify the AV server is running. Check the SystemOut.log file for additional failure details.
CLFRA0455E: The file {0} contains a virus. Remove the virus before attempting to upload the file. Informational message. The AV scanner processed an uploaded file and found a virus in the file. Remove the virus from the file before attempting to upload it to Activities.
CLFRA0456E: The internal identifier {0} is invalid and cannot be used to retrieve content from the database. The identifier in the URL for downloading a file is not valid. Check the identifier in the URL for correctness; if it is correct, the content has been removed and is no longer accessible.
CLFRA0457E: Error {0} received accessing the Organization server The service that supplies a person's organization is not responding. Ensure that the directory services extension configuration for Organizations is correctly configured.
CLFRA0458E: The user {0} could not upload the file with size: {1} because their quota of size {2} would be exceeded. The specified user attempted to upload a file to Activities but the file exceeded the allowable file size. The user may either reduce the size of the file or the system administrator can increase the quota size.
CLFRA0461E: The file with size: {0} could not be uploaded because your quota of size {1} would be exceeded. The current user attempted to upload a file to Activities but the file exceeded the allowable file size. The user may either reduce the size of the file or the system administrator can increase the quota size.
CLFRA0462E: Unable to instantiate file upload quota checker {0}; received error {1}; using default implementation The file upload quota extension is not configured with an accessible class. Provide the name of a class accessible to the Activities service for checking file upload quotas.
CLFRA0463E: The command cannot be processed because another user has this key value: {0} The person's profile data cannot be updated because another person already has been assigned their unique identifer. Resolve issues with the directory so that different users are not assigned the same unique identifer.
CLFRA0464E: The user with id {0} could not be found. The identifier provided in the transfer assets command does not resolve to a unique identifier for a person in the directory. Provide a unique identifier for a person in the directory in the transfer command.
CLFRA0465E: Unknown command: {0} The provisioning command received was not recognized. None.
CLFRA0466E: An unexpected error occurred while processing command {0}: {1} The provisioning or user lifecycle event failed. Resolve the error included in the message and reissue the event.
CLFRA0470E: Unable to instantiate configured cacheExtensionPoint {0}; received error {1}; using default implementation The class providing an alternative implementation to the default Activities cache could not be instantiated. Correctly configure the extenstion point for the alternative cache implementation in oa-config.xml.
CLFRA0471E: The community by external ID "{0}" could not be found. Thus, this community activity will not be imported. If Activities cannot find the given Community, it cannot import the archive. See if the community still exists in the Communities Server using the same ID.
CLFRA0472E: The membership model can only be changed on community activities. This message is thrown if an error occurs when changing the membership type of the community. Make sure the activity is a community activity.
CLFRA0473E: Error locating profile: EXID mismatch, but email matches. name={0}, directory EXID={1}, db EXID={2} A collision arose between two users who have the same email address but different LDAP Ids. Use the logged identification information. The system administrator can fix up the user data in LDAP and in the Activities database tables, ensuring that each unique user has a different email address and different LDAP Ids.
CLFRA0475E: Error on user lifecycle getByInternalId of: {0} Generic error occurred while running the sync command *byMemberId. Use the server logs to identify why command failed to run.
CLFRA0476E: Error on user lifecycle getByEmail Generic error occurred while running the sync command *byEmail. Use the server logs to identify why command failed to run.
CLFRA0477E: Error on user lifecycle getByLogin of: {0} Generic error occurred while running the sync command *byLogin. Use the server logs to identify why command failed to run.
CLFRA0478E: Error on user lifecycle update of internalId: {0} Generic error occurred while running the sync command *byMemberId. Use the server logs to identify why command failed to run.
CLFRA0480E: Error on user lifecycle getByExternalId of: {0} Generic error occurred while running the sync command *byExtId. Use the server logs to identify why command failed to run.
CLFRA0481E: All of the owners of the Activity cannot be removed. This message is thrown when removing all of the owners of the activity from the activity's member list is requested. At least one owner of the activity must remain as the owner in order to avoid an orphan activity.
CLFRA0482E: Member {0} tried to modify the permissions of the business owner of Activity {1} A person tried to change the access of the business owner of the activity. None . the business owner's permissions cannot be changed by a member.
CLFRA0483E: The permissions of the business owner of the Activity cannot be modified A person tried to change the access of the business owner of the activity. None . the business owner's permissions cannot be changed by a member.
CLFRA0484E: Unable to find the selected library. Please try again. Contact your administrator if this problem persists. This error message is thrown from Quickr® server when the selected Quickr library from Activities Picker is no longer found. Make sure the selected Quickr library is found in Quickr server. If the problem still persists, contact Quickr server adminstrator.
CLFRA0485E: The same file already exists in the selected library. This error message is thrown from Quickr server when a file with the same file name already exists in the selected library. N/A
CLFRA0486E: Unable to connect to the service. Please try again. Contact your administrator if this problem persists. This error message is thrown when Activities back-end API client is unable to connect to Quickr server. Make sure the Quickr server is up and running and the connection is set up correctly.
CLFRA0487E: Could not perform the request Unknown error occurs when publishing a file to Quickr server. Make sure the Activities picker is set up correctly to connect to a specified Quickr server.
CLFRA0488E: There is a problem with the server. Please try again. Contact your administrator if this problem persists. This error message is thrown from Quickr server when there is an internal server issue. Make sure the Quickr server being connected to is up and running and set up correctly.
CLFRA0489E: You are not authorized to publish to this location. This error message is thrown when a user tries to publish a file to a Quickr library but doesn't have the author access. N/A
CLFRA0490E: You are not allowed to perform the action. This error message is thrown from Quickr server when publishing a file to the Quickr server and the user is not allowed to publish the file to a selected library. N/A
CLFRA0491E: You have no access. This error message is thrown from Quickr server when publishing a file to the Quickr server and the user is not allowed to publish the file to a selected library. N/A
CLFRA0492E: There was a problem with your request. Please try again. Contact your administrator if this problem persists. This error message is thrown if a problem occurs when publishing a file to a selected Quickr library. N/A
CLFRA0493E: The file type you are trying to publish is not allowed in this location. This error message is thrown if the file type being published to a Quickr library is not allowed. Check with the Quickr server administrator to find out the allowed file types.
CLFRA0494E: Invalid Atom date Bad Atom date format is used. Correct Atom date format: <updated>2009-01-02T20:45:07Z</updated> <published>2009-01-02T20:45:07Z</published>
CLFRA0495E: Invalid Atom date Bad Atom date format is used. <updated>2009-01-02T20:45:07Z</updated> <published>2009-01-02T20:45:07Z</published>
CLFRA0496E: Unexpected Markup\t\t{0} Invalid markup used in the atom entry document. Remove invalid XML/Atom markup tags.
CLFRA0497E: Unsupported Document Element Unsupported Atom/XML element is used in the atom entry document. Remove unsupported Atom entry document elements.
CLFRA0498E: Invalid Visibility: {0} Obsolete . this is used internally for Activities m3 release. Not used in 3.0. N/A
CLFRA0499E: Invalid Role: {0} Obsolete N/A
CLFRA0500E: Unsupported element Lotus® Live specific error. When creating an activity, if .Public. is entered, then this error message is thrown.  
CLFRA0501E: Malformed xml:base Malformed xml:base value is used. Use valid xml:base value.
CLFRA0502E: Unacceptable element Unacceptable element is used in the atom entry document. Remove invalid XML/Atom markup tags.
CLFRA0503E: Invalid Compound Atom Document When parsing multipart POST and PUT input stream, if the Atom entry is formatted invalid, the error message will be thrown. Send a valid multipart POST/PUT input request and make sure the first input request body is a well-formatted Atom entry document.
CLFRA0504E: atom:id is null The required atom:id element is null. When sending a PUT request to modify an existing entry, make sure to set the atom:id and its value.
CLFRA0505E: Invalid Due Date: {0} Invalid snx:duedate value is used. Use Atom Date construct to set the value.
CLFRA0506E: BadInputStream HTTP POST/PUT request input stream is bad. Send a valid input request stream.
CLFRA0507E: Invalid Priority: {0} Invalid Activities' priority value is found in the Atom entry document. N/A
CLFRA0508E: Atom: in-reply-to ref is null The required threading extension, .in-reply-to. element's .ref. attribute value is null. Be sure to include the value of .ref. attribute when setting or changing the parent entry using the in-reply-to threading extension. Correct use of in-reply-to. <thr:in-reply-to xmlns:thr="http://purl.org/syndication/thread/1.0" ref="urn:lsid:ibm.com:oa:793G09219C73CC5C30A4F106B852AD00012F" type="application/atom+xml" href="http://activities.dulcinea.enterprise.com/service/atom2/activitynode? activityNodeUuid=793G09219C73CC5C30A4F106B852AD00012F" source="urn:lsid:ibm.com:oa:793G09219C73CC5C30A4F106B852AD00012F"> </thr:in-reply-to>
CLFRA0509E: Invalid component Invalid value is entered for .component. attribute in the member entry document. Use the correct Activities component.<snx:role component="http://www.ibm.com/xmlns/prod/sn/activities">
CLFRA0510E: This implementation does not allow markup in title elements Invalid markup is used to set the atom:title element's value. Use text type for atom:title value.
CLFRA0511E: Invalid Status: {0} Invalid activity's status value is entered. Use .completed. or .not-completed. as the flag value.
CLFRA0512E: This entry type is not supported in the 2.0 API When an entry of type=.entry. is used in the 2.0 Atom API. Don't use .entry. type in the 2.0 Atom API.
CLFRA0513E: Unrecognized Feed Type This is internal use only. N/A
CLFRA0514E: Required element snx:role is null When creating or modifying an activity member, snx:role is required, but it's not sepcified in the member entry document. Use a correct snx:role and value: To add an owner, <snx:role component="http://www.ibm.com/xmlns/prod/sn/activities">owner</snx:role>
CLFRA0515E: atom:content: unsupported type Not used in the server code. N/A N/A
CLFRA0516E: unable to create file upload directory {0} When uploading a file, there was a problem with the file upload directory. Contact system administrator.
CLFRA0517E: unable to upload file: {0} {1} This error message is thrown if a problem occurs when uploading a file to the server. Make sure the file size doesn't exceed the upload file size limit and the file type is accepted to the server.
CLFRA0518E: Could not send SameTime notification N/A in server code N/A
CLFRA0519E: A URL must be specified via {0} N/A in server code N/A
CLFRA0520E: Error starting Activities UserLifecycle SPI. Generic error initializing the User Lifecycle SPI engine. Use the server logs to identify why the SPI engine failed to start.
CLFRA0523E: Error inserting Tree Entry: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0524E: Error purging MemberProfile: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0525E: Error getting ContentReference: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0526E: Error creating or saving a section because it was not a direct descendant of its activity An error occurred adding a section. Provide the correct UUID for the parent of the section in the API.
CLFRA0527E: Error updating NodeMember: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0528E: Error removing node: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0529E: Error updating AclEntry: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0530E: Profile ID: {0} does not exist. A Member could not be retrieved from the database using the provided member identifier. Provide the correct member identifer for a person in the API.
CLFRA0531E: Error updating Statement (property): {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0532E: Exporter/Importer cannot delete: {0} Unable to delete a filesystem resource. Check for permission errors writing to the filesystem and verify the given user can read the directory.
CLFRA0533E: Error getting related libraries of a selected file entry {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0534E: Required parameter MemberID was not specified The person's memberid was not specified in the Hashtable used as input to the updateMember wsadmin command. Provide a memberid in the Hashtable and reissue the command.
CLFRA0535E: Error getting related activities: {0} An error occurred retrieving an entry to the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0536E: Error inserting EventLogEntry: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0537E: Error getting LogEntries for an activity: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0538E: Error purging a selected publish library {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0540E: Error getting Statements: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0541E: Error loading configuration settings to determine if external email exposure is enabled: {0} An error occurred reading a value from LotusConnections-config.xml. Check the SystemOut.log on server startup to determine the syntax error in LotusConnections-config.xml; resolve the syntax error.
CLFRA0542E: Error inserting Node: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0543E: Bad configuration. Config section defines more properties than values, or vice versa. Possible errant <property> element(s) without a "name" attribute(s) A property in LotusConnections-config.xml or oa-config.xml has too many or not enough values. Provide the correct number of values for the listed property in LotusConnections-config.xml or oa-config.xml.
CLFRA0544E: Importer error accessing the directory {0} Error accessing the given archive directory. Check for permission errors writing to the filesystem and verify the given user can read the directory.
CLFRA0545E: Error updating a selected publish library {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0546E: Exporter/Importer destination/source is not a directory: {0} The path given is not a directory path. Check the directory argument actually points to a path that is a directory.
CLFRA0547E: no default content store defined A default content store has not been configured in oa-config.xml. Designated a default content store in oa-config.xml. See the infocenter topic on .Managing uploaded files. for details
CLFRA0548E: Error inserting Schema Version: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0549E: Error getting nodes: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0550E: Error purging node: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0551E: Error inserting NodeMember: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0552E: cannot disable security; user is not an administrator A person tried to assume administrator privileges. None . Activities will not allow a person to assume administrator privileges.
CLFRA0554E: Error creating thumbnail for {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added
CLFRA0555E: Error getting descendent uuids: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0556E: Failed to initialize {0} The Activities database layer configuration file dao.xml has been corrupted. Update the Activities Enterprise Application from backup in the WebSphere Application Server Integrated Solutions Console.
CLFRA0557E: Error getting MemberProfile: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved
CLFRA0558E: Error getting activities: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0559E: Error inserting Tags: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0560E: Error inserting a new publish library {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0561E: Error getting all LogEntries for a user: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0562E: Error when reparenting node - You cannot reparent a node to one of its descendants. An API program tried to move a entry to an incorrect location. Check the logic of the move entry logic in the API program.
CLFRA0563E: Error creating or saving a {0} because it was a child of an invalid node type {1} An API program tried to save a entry to an incorrect location. Check the parenting logic in the API program.
CLFRA0564E: Importer error accessing the directory {0} The wsadmin ArchiveService does not have access to the directory containing the Activities to be imported. Check that the correct directory has been specified; if so, ensure that the permissions on the directory allow the WebSphere Application server to read it.
CLFRA0565E: Error getting AclEntries for a user: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0566E: Error updating Node: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0567E: Error purging Tag: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed
CLFRA0568E: Error undeleting node: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0569E: getting children for node: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved
CLFRA0570E: Cannot change position, the max number of children ({0}) has been exceeded for node = {1} An error occurred updating an entry in the database. None . the maximum number of children for the activity or entry has been reached.
CLFRA0571E: Could not locate MBean Server An error occurred trying to register the Activities Mbeans with the WebSphere Application Server. Check the SystemOut.log for WebSphere errors on server startup regarding Mbeans and resolve those errors.
CLFRA0572E: Error inserting a publish history entry {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0573E: Error, you cannot convert a node template to another type An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0574E: Error updating Schema Version: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0575E: Error, entry type conversion from and to activity is not allowed An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0576E: Error, entry type conversion from and to section is not allowed An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0579E: Error updating ContentReference: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0580E: Error getting ancestors: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0581E: Error purging a selected publish history entry {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0582E: Error inserting MemberProfile: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0583E: Error getting a selected publish history entry {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0584E: Error purging NodeMember: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0585E: Error getting publish history entries of a selected file entry An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0586E: Error auto completing activities: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0587E: Error getting related people: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0588E: Error updating Tag: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0589E: Exporter error creating the directory {0} Generic error creating the archive directory. Check for permission errors writing to the filesystem and verify the given user can create a directory in a given path.
CLFRA0590E: Error getting AclEntries for an activity: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0591E: cannot create MemberProfile. Profile ({0}) already exists. A person could not be added to Activities because their unique identifier or email address matched with another person's in the database. Use the information provided in the error, run the wsadmin ActivitiesMemberService.syncMemberExtIdByLogin() command for the person already in the Activity's database.
CLFRA0592E: The email address={0} was not found in the directory! Unable to process their message! An error occurred trying to send an email notification to a person who does not have an email address. The notification will be sent to the person's Home page.
CLFRA0593E: Error inserting ContentReference: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0594E: Error getting Tags for a member: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0595E: Schema Version Mismatch The version of the Activities database Activities is connecting to is the wrong version. Upgrade the Activities data to the correct versions either with the database wizard or upgrade scripts.
CLFRA0596E: Error getting Tags from a node: {0} An error occurred retrieving an entry in the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0598E: Error getting a selected publish library {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0599E: Unable to add email "{0}" to the membership of the activity because the email address was not recognized either as a person or a group    
CLFRA0600E: Error updating a selected publish history entry {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0601E: Error purging Statement: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0602E: Error purging Tree Entry: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0603E: Error getting ancestor uuids: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0604E: Error getting NodeMember: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0605E: Error getting activities tags: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0606E: Unable to process event "{0}" . An exception was thrown: An error occurred sending an email notification. Refer to addition information in the message regarding the cause.
CLFRA0607E: Error purging EventLogEntry: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0608E: Error finding groups that start with ({0}) : {1} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0609E: Error creating icon for {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0610E: Unrecognized multipart type={0} An error occurred processing an email being added to Activities. Ensure that the API program adding email to Activities does no try to include unsupported MIME types.
CLFRA0611E: Error getting activities named ( {0}) : {1} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0612E: Error getting EventLogEntry by member and node: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0613E: Error inserting AclEntry: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0614E: Error, invalid date type specification, {0} An error occurred trying to use the dates provided in a database query. Ensure that the API program requesting Activities by dates provides valid dates.
CLFRA0615E: Error updating Statement: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0616E: Exporter/Importer error creating the directory {0} Error creating the archive directory. Check for permission errors writing to the filesystem and verify the given user can create a directory in a given path.
CLFRA0617E: Error getting NodeSummary: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0618E: Exporter/Importer destination/source directory is not readable: {0} The directory in the filesystem is not readable. Check for permission errors writing to the filesystem and verify the given user can read the directory.
CLFRA0619E: {0} - All passed AclEntrys must refer to the passed object An error occurred trying to process the data for performing an Membership change. Ensure that the data provided by API program requesting the Membership change is appropriate.
CLFRA0620E: Error updating Tree Entry: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0621E: Error getting activities nodesummary: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0622E: Error purging Schema Version: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0623E: Error getting related libraries of a selected activity {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0624E: 'subscriber' cannot be empty. An error occurred retrieving an entry in the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0625E: Error updating MemberProfile: {0} An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0626E: Error getting activities total: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0627E: Error purging AclEntry: {0} An error occurred removing an entry from the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0628E: Error finding activities that start with ( {0}) : {1} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0630E: Error getting publish history entries of a selected activity {0} An error occurred retrieving an entry in the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0631E: Unrecognized content type at the beginning of the email={0}, instanceof={1} An error occurred trying to add an email to Activities. Modify the API program trying to add the email to only provide supported data types.
CLFRA0632E: Error getting Node: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0634E: Error getting publish history entries of a selected node entry {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0636E: Error getting Statement: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0637E: Error purging ContentReference: {0} An error occurred removing an entry in the database. Check the database logs and resolve the condition preventing the entry from being removed.
CLFRA0638E: Error getting Tree Entry: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0639E: Error getting AclEntry by uuid: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0641E: EmailNotifier: initialize method does not allow null properties. Check the config file to see if it includes all the required settings    
CLFRA0642E: Error moving node, activities/reply typed nodes cannot be re-parented. An error occurred updating an entry in the database. Check the database logs and resolve the condition preventing the entry from being updated.
CLFRA0643E: Invalid event class: {0} An error occurred processing the <eventBroker> entry in oa-config.xml. Restore the default <eventBroker > entry in oa-config.xml.
CLFRA0644E: Error getting EventLogEntry by uuid: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0645E: Error getting AclEntry by member and node: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0646E: Error getting LogEntries for a user: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0648E: Error getting nodes in activity: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0649E: Error getting Schema Version: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0650E: Error getting autocompleted activity candidates: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0651E: No such Sort Key - {0} The sort key provided for sorting entries returned from a query is null. Modify the API program requesting sorted entries to provide a sort key.
CLFRA0652E: No thumbnail exists for {0} The thumbnail image for an attachment could not be found. None . a default image will be used.
CLFRA0653E: NOT IMPLEMENTED The function being requested from the Activities service is not available. None.
CLFRA0655E: Error getting ancestor tree entries: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0656E: Error getting getMemberProfilesByName: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0657E: Error getting Tag: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0658E: Error getting all nodes: {0} An error occurred retrieving an entry from the database. Check the database logs and resolve the condition preventing the entry from being retrieved.
CLFRA0660E: Stream is not Open An error occurred trying to feed user input data through the Active Content filter. Caused by a temporary lack of resources, retry the operation.
CLFRA0661E: Error inserting Statement: {0} An error occurred adding an entry to the database. Check the database logs and resolve the condition preventing the entry from being added.
CLFRA0662E: unknown permission: {0} An error occurred processing the list of permissions being given to a Member of an activity. Ensure that the API program adding the permissions only uses those defined.
CLFRA0665E: Error closing the Admin Execution Context An error occurred during the completion of a user lifecycle event. Check the additional information provided in the message for the cause.
CLFRA0668E: The community activity UUID={0} has been deleted by its Community. Thus, it will not be exported. The administrator tried to export an activity that references a community that has been deleted. (When a community is deleted, its activities are soft-deleted, which means they are still potentially available for export.) However, the implementation policy does not allow for the export of such activities.  
CLFRA0669E: Cannot set External to {0} in activity UUID {1} due to heterogeneous organizations in the membership of the activity. The activity cannot be made internal because some of the current members of the activity have an organization that is different from the organization of the business owner. Remove the members of the activity who have a different organization from the business owner, then retry the Access Change action.
CLFRA0671E: Cannot set External to {0} in activity UUID {1} because the Community member {2} is external. The activity cannot be made internal because one of the current community members is external. Remove the external community from the Members list, then retry the Access Change action.
CLFRA0672E: The external Community {0} could not be added as a member to the internal activity with UUID {1}. The selected community cannot be added to the internal activity because the community is external. Set the community access to be internal, then retry the Add Member action.
CLFRA0683E: The file {0} does not exist. The attachment to remove is not in the file system. No action necessary.
CLFRA0684E: {0} does not have organization member uuid. The selected member cannot be added to an activity because the member does not belong to an organization. Contact customer support to report the incident.
CLFRA0685E: Error inserting Invitation: {0}. The operation to add an invitation to the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities, contact IBM customer support to report the incident.
CLFRA0686E: Error updating Invitation: {0}. The operation to update an invitation in the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities, contact IBM customer support to report the incident.
CLFRA0687E: Error getting Invitation by activity and member: {0}. The operation to select an invitation from the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities, contact IBM customer support to report the incident.
CLFRA0688E: Error updating profile: extId = {0} exception = {1}. The operation to update a member in the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities, contact IBM customer support to report the incident.
CLFRA0689E: Error adding profile: extId = {0} exception = {1}. The operation to add a member to the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities, contact IBM customer support to report the incident.
CLFRA0690E: Error purging Invitation: {0}. The operation to delete an invitation from the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities, contact IBM customer support to report the incident.
CLFRA0691E: Error getting Invitation by uuid: {0}. The operation to select an invitation from the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities feature, contact IBM customer support to report the incident.
CLFRA0692E: Error getting Invitations for an activity: {0}. The operation to select Invitations from the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities feature, contact IBM customer support to report the incident.
CLFRA0779E: The organization {0} cannot be removed. It is in use by subscriber(s) : {1} The organization cannot be deleted because at least one subscriber in the Activities database is a member of the organization. Remove all subscribers from the organization before removing the organization.
CLFRA0780E: Cannot add member {0} to activity UUID {1} because they are not a member of Community UUID {2}. The member could not be added to the community activity because they are not a member of the community. Add the member to the community then retry the Add Member action.
CLFRA0781E: The Activity or Activity Entry with UUID {0} is not present in the Activities database. The operation to select an activity or activity entry from the Activities database failed. The activity or entry referenced by the URL is no longer present in the Activities database. No action necessary.
CLFRA0782E: The time zone "{1}" for user "{0}" is not valid; using default time zone for user''s locale. You should not see this error message. The feature is not enabled. You should not see this error message. The feature is not enabled
CLFRA0783E: Error getting total number of AclEntries: {0}. The operation to select then number of Activity Members from the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities, contact IBM customer support to report the incident.
CLFRA0786E: Error checking access permission for user {0} on activity {1}. The operation to check a member's access to an activity in the Activities database failed. Ensure any database issues reported in the SystemOut.log file are resolved. If the problem persists after restarting Activities, contact IBM customer support to report the incident.
CLFRA0787E: Unable to instantiate requested cache {0} from DynaCache; received error {1}; using default implementation. Errors are being returned when Activities is trying to access the WebSphere cache implementation. Contact IBM customer support to report the incident.
CLFRA0788E: Unable to instantiate configured timezoneExtensionPoint {0}; received error {1}; using default implementation. You should not see this error message. The feature is not enabled You should not see this error message. The feature is not enabled


Related

  • Administer Activities


    Anti-virus error codes

    Use the codes included in the error messages generated by IBM Connections to identify problems with the Anti-Virus service plug-in and find their solutions.

    The following error messages are generated by the Anti-virus service plug-ins:

    Table 4. Anti-Virus service plug-in error messages

    Message Cause Solution
    CLFAQ0001E: Unable to access file {0} The plug-in cannot find the file to scan. Verify the file name and then try again.
    CLFAQ0002E: Error raised communicating with virus scanner: {0} The plug-in could not connect to the scanner. For example: my.scanner.com. Verify that the scanner is running and the network connection is good.
    CLFAQ0003E: Property {0} missing from scanner initialisation data A required property, identified by {0}, is not in the <avFilter> XML block of the configuration file. Add the property to the to the <avFilter> XML block in LotusConnections-config.xml.
    CLFAQ0004E: ICAP error processing content: {0} There was a problem processing the content of the ICAP header. Make sure you are providing the appropriate content in the header.
    CLFAQ0005E: Unknown Host: {0} The code was unable to find the antivirus server. First, check that the antivirus server is online and reachable by the Lotus connections Server. Secondly, check the DNS server to ensure that the hostname/domain used for the antivirus server is pointing to the correct machine. Also ensure that the antivirus machine is running.
    CLFAQ0006E: ICAP error null response The antivirus server did not return any response at all. Indicates a possible connection problem and/or anti-virus server problem. The virus scanner might have crashed, for example.
    CLFAQ0007E: ICAP error first read timeout: {0} Indicates that the anti-virus server is a bit slow or overloaded or there is some sort of network issue. If you see this error once in a while, it is OK to ignore it. However, if the logger has a lot of timeouts and virus scanning fails, then there is a problem. In this case, check to make sure that the antivirus server is actually running and reachable by the IBM Connections servers.
    CLFAQ0008E: General error with connecting to a server: {0} A generic error that is displayed when the code is unable to connect to the antivirus server due to some unexpected error. First, check that the antivirus server is online and reachable by the Lotus connections Server. Secondly, check the DNS server to ensure that the hostname/domain used for the antivirus server is pointing to the correct machine. Also ensure that the antivirus machine is running.
    CLFAQ0009E: ICAP error second read timeout: {0} Indicates that the anti-virus server is a bit slow or overloaded or there is some sort of network issue. If you see this error once in a while, it is OK to ignore it. However, if the logger has a lot of timeouts and virus scanning fails, then there is a problem. In this case, check to make sure that the antivirus server is actually running and reachable by the IBM Connections servers.
    CLFAQ0010E: ICAP error incomplete response: {0} The antivirus server did return something, but the response was incomplete. Check to make sure that the antivirus server is actually running and reachable by the IBM Connections servers.
    CLFAQ0011E: Unsupported connection type: [tls] The current code does not support connecting to the antivirus scanner using TLS. Disable TLS.
    CLFAQ0012I: ICAP Headers: {0} This informational message is provided for debugging, since the code can sometimes misinterpret the ICAP headers. Use this message to secure a log of what the headers actually are so you can figure out what happened.


    Blogs error messages

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

    The following Blogs error messages are generated by IBM Connections:

    Table 5. 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 WebSphere Application Server 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.
    CLFRS1777E: Error updating entries Not identifiable without more information. Report this problem to Customer Support.
    CLFRS1775E: Error in UploadFileFormAction.getWebsite Not identifiable without more information. Report this problem to Customer Support.
    CLFRS1774E: Fail to update user information. User information data in Database is not update-to-date. (User Id: {0}, Login Name: {1}) Not identifiable without more information. Report this problem to Customer Support.
    CLFRS1773E: Failed to add new user. A user with the same email address [{0}] already exists. Not identifiable without more information. Report this problem to Customer Support.
    CLFRS1776W: NullPointerException occurred when preparing website list for display. Possible cause: corrupted ROLLER_USER_PERMISSIONS data. [ perm.id = ''{0}'' ] Not identifiable without more information. Report this problem to Customer Support.
    CLFRS1778W: Fail to send entry updated notification to entry creator. Not identifiable without more information. Report this problem to Customer Support.


    Bookmarks error messages

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

    The following Bookmarks error messages are generated by IBM Connections:

    Table 6. Bookmarks error messages

    Message Cause Solution
    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 following 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 Application Server 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 following this error message 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 following 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 following this error massages in the log file to find the root cause.
    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 following this error massages in the log file to find the root cause.
    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 following 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 following 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 Application Server 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 following 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 Application Server 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 following 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.
    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 following 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 Application Server 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 section of the product documentation 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 section of the product documentation for help determining that location. If the problem still continues, check disk permissions for the WebSphere Application Server process, also check the detailed exception message following 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 section of the product documentation. 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 following 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 following 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 Application Server 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 following 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 following 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 Application Server 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 following 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 Application Server to verify the database connection.
    CLFRL0049I: Retrieve 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 following this error massages in the log file to find the root cause.
    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 following 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 Application Server 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 following 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 Application Server 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 following 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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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.
    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-cell.xml or try to restart the node. If the warning persists, reset the favicons storage.
    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 following 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 Application Server 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 WebSphere Application Server process, also check the detailed exception message following 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 following 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 following 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 Application Server 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 following 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 Application Server 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 following 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.
    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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 section of the product documentation for help determining that location. If the problem still continues, check disk permissions for the WebSphere Application Server process, also check the detailed exception message following 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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 section of the product documentation for help determining that location. If the problem still continues, check disk permissions for the WebSphere Application Server process, also check the detailed exception message following 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 section of the product documentation for help determining that location. If the problem still persists, check disk permissions for the WebSphere Application Server process, also check the detailed exception message following 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 following 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 Application Server 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 following this error message in the log file to find the root cause.
    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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 following this error message in the log file to find the root cause. Ensure the administrative process has proper file permissions.
    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 following 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 Application Server 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-cell.xml. When this error occurs, Bookmarks creates temp favicons store location in the temp folder. Open <WAS_Home>\profiles\<profile>\config\cells\<cell>\LotusConnections-config\dogear-config-cell.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 following 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.
    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 <privateIntranetAllocationTable>

    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 following 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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 WebSphere Application Server. If this is likely a downstream error, scroll to the beginning 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 following 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 Application Server 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 following 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 following this error massages in the log file to find the root cause.
    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 following this error message in the log file to find the root cause.
    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 following this error message in the log file to find the root cause.
    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 following 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 Application Server 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 following this error message in the log file to find the root cause.
    CLFRL0135I: Retrieve 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 following 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 Application Server 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 following this error message in the log file to find the root cause.
    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 following 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 Application Server 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 following this error message in the log file to find the root cause.
    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 WebSphere Application Server Integrated Solutions 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 WebSphere Application Server 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 following 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.
    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 following 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 Application Server 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 following 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 Application Server 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 following this error message in the log file to find the root cause.
    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 following 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 Application Server 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 following 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 Application Server 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 following 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.
    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 following 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.
    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 following this error message in the log file to find the root cause.
    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 following 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 Application Server 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 WebSphere Application Server process, also check the detailed exception message following this error message in the log file to find the root cause.
    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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 following this error message in the log file to find the root cause.
    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 following 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 Application Server 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 configuration file to fix the error.
    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 following 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 Application Server 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 following 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.
    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 following 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 Application Server 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 following 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.
    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 WebSphere Application Server process, also check the detailed exception message following 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 following this error message in the log file to find the root cause.
    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 following 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 Application Server 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 following 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 Application Server 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 following 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 Application Server 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 following 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.
    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 following this error message in the log file to find the root cause.
    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.
    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.
    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.
    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 following this error massages in the log file to find the root cause.
    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.
    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 following this error message in the log file to find the root cause.
    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.
    CLFRL0243E: One or both files are not directories: [" {0} "] [" {1} "]" This error is encountered when load the local files if the files specified are not directory. Check the detailed exception message to find the exact file path, check the file path on server to see if there is any duplicate filenames.
    CLFRL0244E: Directories have different number of files: [" {0} "] has " {1} " files [" {2} "] has " {3} " files This error is encountered when comparing two directories if there are different number of files. Check the detailed exception message before this error to find if there is any other error messages.Usually there should be file create fail or delete fail exceptions.
    CLFRL0245E: Files do not both exist: [" {0} "] [" {1} "] This error is encountered when one or both specified files are not existing. Check the detailed exception message before this error, usually there should be file create fail exceptions.
    CLFRL0246E: Could not get canonical path for {0} This error is encountered when trying to get the canonical path of system temp directory. Check the detailed exception message to find the root cause, and check your system to make sure it is correctly configured.
    CLFRL0247E: One is a directory, the other isn''t: [" {0} "] [" {1} "] This error is encountered when comparing two files but one of the specified files is a directory. Check the detailed exception message to find the root cause.
    CLFRL0248E: Files have different names: [" {0} "] [" {1} "] This error is encountered when comparing two files but the files specified have different names. Check the detailed exception message before this error to find the root cause, there should be file create fail exceptions.
    CLFRL0249E: File contents are different: [" {0} "] [" {1} "]" This error is encountered when comparing two files but the files specified have different contents. Check the detailed exception message before this error to find the root cause, there should be file create fail or delete fail exceptions.
    CLFRL0250E: Directories do not both exist: [" {0} "] ["{1} "] This error is encountered when one or both specified files are not existing. Check the detailed exception message before this error to find the root cause, there should be file create fail exceptions.
    CLFRL0251E: Error deleting received notifications of person {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0252E: Error deleting notifications sent by person {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0254E: Error saving notifications. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0255E: Error retrieving full links by URL and date for {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0256E: Error getting the notification with id {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0257E: Error deleting notifications on link {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0258E: Error sending notifications from {0} to {1} on bookmarks {2} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0260E: Invalid link id from user: {0}, link id: {1} This error is encountered if the link id provided can't mapped to any exiting links belong to the current user, or an unexpected exception occurs when querying database. Check the link id provided is correct. Check the detailed exception message following 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.
    CLFRL0262E: Error deleting the notification with id {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0263E: Error parsing email addresses when sending notifications. Emails: {0} This error is encountered if the email address is invalid or an unexpected exception occurs. Check the detailed exception message following this error message in the log file to find the root cause. Find out if there is a wrong email address, if yes then correct it.
    CLFRL0264E: Error sending notifications as user {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0265E: Error recording the notification from person {0} to person {1} on link {2} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0266E: Error getting most visited links. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0267E: Error getting notifications on link {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    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. 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 following this error message in the log file to find the root cause. Check the configure file is correct.
    CLFRL0272E: 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 following this error message in the log file to find the root cause. 
    CLFRL0273E: Failed to check bookmarklet installer. This error is encountered if an unexpected exception occurs when checking the installer.  Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRL0275E: Failed to update the bookmarklet installer. This error is encountered if an IOException occurs when updating the installer. Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRL0276E: Failed to parse IBM Connections configure file. IBM Connections configuration file has something wrong Check the detailed exception message following this error message in the log file to find the root cause. Check the configure file is correct.
    CLFRL0278E: Unable to find configure file for bookmarklet installer. The error is encountered if the configure file is not created. Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRL0279E: Failed to get and parse the profile for user {0}. This error is encountered if an unexpected exception occurs when getting user photo from profiles. Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRL0280E: Error getting recently received notifications of user {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0282E: Error getting the number of received notifications of user {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0283E: Error getting received notifications of user {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0285E: Error sending notification from {0} to {1} on bookmarks {2} This error is encountered if an unexpected exception occurs when sending notifications. Check the detailed exception message following 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.
    CLFRL0286E: Error parsing email addresses when sending notifications. Emails: {0} This error is encountered if the email address is invalid or an unexpected exception occurs. Check the detailed exception message following this error message in the log file to find the root cause. Find out if there is a wrong email address, if yes then correct it.
    CLFRL0287E: Invalid link id from user: {0}, linkid: {1} This error is encountered if the link id provided can't mapped to any exiting links belong to the current user, or an unexpected exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0289E: Error getting schema version from database. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0291E: Error updating person {0} with new locale {1} User locale is saved when he/she logs on. This error is encountered if a SQL exception occurs when writing database. Check the detailed exception message following 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.
    CLFRL0302E: Error: failed to update ContentTypes with the ones from the configuration file. This error is encountered if a SQL exception occurs when executing update command. Check the detailed exception message following 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.
    CLFRL0303E: Error getting the number of ContentTypes in the most notified links. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0306E: Error deleting all ContentTypes from database. This error is encountered if a SQL exception occurs when deleting data from database. Check the detailed exception message following 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.
    CLFRL0308E: Error getting received notifications of user {0}, filtered by tag union. Tags: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0309E: Error creating ContentType URL mappings for URL: {0} This error is encountered if a SQL exception occurs when inserting records into database. Check the detailed exception message following 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.
    CLFRL0310E: Error getting the number of ContentTypes in received notifications of user {0}, filtered by tag union. Tags: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0311E: Error getting the number of received notifications of user {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0312E: Error getting count of content types. This error is encountered if an unexpected SQL exception occurs when trying to get count of content types Check the detailed exception message following 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.
    CLFRL0313E: Error getting received notifications of user {0}, filtered by tag intersection. Tags: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0314E: Error getting tag counts of received notifications for {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0316E: Error getting person counts of received notifications for {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0317E: Error querying all ContentTypes from database. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0318E: Error: failed to get count of ContentTypes from database. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0319E: Error getting the number of ContentTypes in received notifications of user {0}, filtered by tag intersection. Tags: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0320E: Error deleting all ContentType URL mappings from database when updating the mappings. This error is encountered if a SQL exception occurs when deleting data from database. Check the detailed exception message following 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.
    CLFRL0320E: Error deleting all URL-ContentType mappings from database when updating URL-ContentType mappings. This error is encountered if a SQL exception occurs when deleting data from database. Check the detailed exception message following 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.
    CLFRL0321E: Error getting count of content types for person {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0322E: Error getting the number of ContentTypes in received notifications of user {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0323E: Error deleting all ContentType URL mappings from database. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0327E: Error: failed to get specified ContentType from database. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0328E: Error getting count of content types for subscriptions {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0329E: Error getting the number of received notifications of user {0}, filtered by tag union. Tags: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0331E: Error getting the number of ContentTypes in received notifications of user {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0332E: Error: failed to delete URL mappings of a ContentType from database. This error is encountered if a SQL exception occurs when deleting data from database. Check the detailed exception message following 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.
    CLFRL0334E: Error: failed to create ContentType URL mapping. This error is encountered if a SQL exception occurs when inserting record into database. Check the detailed exception message following 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.
    CLFRL0335E: Error getting the number of the most notified links. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0336E: Error getting links for full-text index queue, startpos This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0337E: Error: failed to insert a ContentType record. This error is encountered if a SQL exception occurs when inserting record into database. Check the detailed exception message following 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.
    CLFRL0338E: Failed to verify request. This error is encountered if a SQL exception occurs when inserting record into database. Check the detailed exception message following 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.
    CLFRL0339E: Error: failed to get links count by ContentType. This error is encountered if a SQL exception occurs when inserting record into database. Check the detailed exception message following 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.
    CLFRL0342E: Error getting intersection count of content types for tags {0} and person {1} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0343E: Error getting count of content types for URL {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0344E: Error getting notifications by URL and date. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0345E: Error getting the number of received notifications of user {0}, filtered by tag intersection. Tags: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0346E: Error: failed to record the click on Link {0} This error is encountered if there is a SQLException when updating the click count of a Link. Check the detailed exception message following 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.
    CLFRL0347E: Error writing ServiceConfigs to feed. This error is encountered if there is an unexpected exception occurred when output the server configuration to a feed document. Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRL0349E: Error getting structured tag counts for person {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0350E: Error getting number of unique URLs last modified since {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0352E: Error getting tag counts of sent notifications for {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0354E: Error getting structured tag counts of received notifications for {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0355E: Error sending the notification on broken URL from {0} to {1} on bookmark {2} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0356E: Error getting notifications sent by user {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0357E: Error getting person counts of notifications sent by {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0358E: Error getting URLs last modified since {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0359E: Error getting the number of notifications sent to user {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0360E: Error getting the number of the notifications sent to user {0}, filtered by tag intersection. Tag: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0361E: Error getting the number of the notifications sent to user {0}, filtered by tag union. Tag: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0362E: Error getting tag counts for hover text, tag is {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0363E: Error getting structured tag counts of sent notifications for {0} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0364E: Error getting the notifications sent to user {0}, filtered by tag intersection. Tag: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0365E: Error: failed to record the click on Link {0} by Person {1} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0366E: Error getting the notifications sent to user {0}, filtered by tag union. Tag: {1}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0367E: Error getting tag counts for hover text for person {0}, tag is {1} This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0368E: Error parsing email address when sending broken URL notifications. Email: {0} This error is encountered when the email address specified is invalid. Check the detailed exception message following this error message in the log file to find the root cause. Maybe need to correct the email address saved in LDAP.
    CLFRL0369E: Error getting login names for person id {0}. This error is encountered if a sqlexception is occurred when getting login names from database Check the detailed exception message following 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.
    CLFRL0371E: Error getting person for login name {0}  This error is encountered if a sqlexception is occurred when getting login names from database Check the detailed exception message following 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.
    CLFRL0373E: Internal error updating login name by the provided id {0} This error is encountered if a sqlexception is occurred when updating the login name for person specified Check the detailed exception message following 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.
    CLFRL0374E: Attempt by {0} to subscribe to Anonymous User. This error is encountered if someone wants to subscribe a user who is not existing. Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRL0379E: Internal error updating login names from file with member id {0} {1} This error is encountered if a sqlexception is occurred when updating the login name for person specified Check the detailed exception message following 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.
    CLFRL0387E: Error getting person profile from LDAP for id: {0} This error is encountered if an unexpected exception is occurred when getting the people information for LDAP Check the detailed exception message following 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.
    CLFRL0388E: Error deleting login names for person id {0}. This error is encountered if an unexpected exception is occurred when getting the login information for LDAP Check the detailed exception message following 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.
    CLFRL0390E: Unable to find person matching the provided id {0} This error is encountered if an unexpected exception is occurred when getting the people information for LDAP Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRL0392E: Error getting person profile from LDAP for email: {0} This error is encountered if an unexpected exception is occurred when getting the people information for LDAP Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRL0394E: Error updating login names for person id {0}. This error is encountered if a sqlexception is occurred when updating login name for person Check the detailed exception message following 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.
    CLFRL0397E: Internal error retrieving user by member id {0} This error is encountered if a sqlexception is occurred when getting the person information from database Check the detailed exception message following 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.
    CLFRL0398E: Error getting tags for constraints {0} This error is encountered if a sqlexception is occurred when getting recent tags Check the detailed exception message following 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.
    CLFRL0400E: Error getting deleted links. This error is encountered if a sqlexception is occurred when getting the deleted bookmarks. Check the detailed exception message following 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.
    CLFRL0403E: The term of category is not correct. This error is encountered if the category specified in the notification feed entry is not correct Check the code used to generate the entry to correct the value of category, the correct value is 'notification'
    CLFRL0404E: No category specified in the post entry. This error is encountered if there is no category specified in the notification feed entry.  Check the code used to generate the entry to correct the value of category, the correct value is 'notification''
    CLFRL0405E: Notification body only supports text format. This error is encountered if the content type of the notification content is not correct  Check the code used to generate the entry to correct the value of the content type of the notification body, the correct value is 'text'
    CLFRL0406E: Unable to parse Notification Atom post entry sent by user {0} This error is encountered if the notification feed is not correct. Check the detailed message following this error message to find the root cause. 
    CLFRL0407E: Dogear Notification API only supports http post method. This error is encountered if the http method used to send the notification is not 'Post'  Check the code used to send the notification, currently you can only use post method to send the notification.
    CLFRL0408E: Links in the atom are private or deleted. This error is encountered if the notification is sent on a deleted or private bookmark  Check the detailed error message to following this error to find the root cause.
    CLFRL0409E: Recipients in the atom cannot be found. This error is encountered if the recipients specified in the notification feed is not existing or no recipients specified in the feed document. Check the detailed error message to following this error to find the root cause, and check the code used to send the notification.
    CLFRL0410E: Content type is not correct. Current ContentType is: {0} This error is encountered if the content type of the feed document is not correct. Check the code used to send the notification, the correct content type of the feed document is 'application/atom+xml'
    CLFRL0411E: Error updating last login time {0} for person {1} This error is encountered if a sqlexception is occurred when updating the login time for specified person  Check the detailed exception message following 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.
    CLFRL0412E: An error occurred while firing search request to Global Search service This error is encountered if an unexpected exception is occurred when firing search request to Global Search Check the detailed exception message following this error message in the log file to find the root cause
    CLFRL0413E: Error getting the number of new and unique URLs posted in the last {0} days This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0414E: Error getting the number of users who have more than {0} bookmarks This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0415E: Error getting number of users logged on in the last {0} days. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0416E: Error getting the number of bookmarks that have at least 1 tag This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0417E: Error getting the number of users who received notifications in the past {0} days. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0418E: Error getting the number of new bookmarks posted in the last {0} days This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0419E: Error getting the number of users who submit bookmarks in the last {0} days This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0420E: Error getting the number of users who sent notifications in the past {0} days. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0421E: Error getting the number of tags posted in the last {0} days This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0422E: Error getting the number of users who have not logged in for more than {0} days. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0423E: Error getting the number of new tags posted in the last {0} days This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
    CLFRL0424E: Error getting person counts for bookmarks with request parameters {0}. This error is encountered if a SQL exception occurs when querying database. Check the detailed exception message following 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.
         
    CLFRL0475E: Error sending broken URL notifications to owners of URL {0}. Failed to send the broken URL notifications to all the owners of an URL Check the detailed exception following this message to find the root cause.
    CLFRL0491E: Error generating an event when the administrator deletes bookmarks in batch. Unexpected exception occurred when asynchronize the batch delete bookmark event Check the detailed exception following this message to find the root cause.
    CLFRL0469E: LinkService MBean ::: Failed to delete bookmark(s) with URL {0} unexpected exception occurred when delete links by url Check the detailed exception following this message to find the root cause. The file encoding may not be correct.
    CLFRL0471E: LinkService MBean ::: Failed to delete bookmark(s) with URLs loaded from file {0} unexpected exception occurred when delete links by urls, the urls are loaded from file Check the detailed exception following this message to find the root cause. The file encoding may not be correct.
    CLFRL0513E: Failed to synchronize person by the given newExtId {0} and oldExtId {1} unexpected exception occurred when synchronizing person by external ID Check the detailed exception following this message to find the root cause.
    CLFRL0510E: Failed to synchronize all persons by ExtId. unexpected exception occurred when synchronizing people by external ID Check the detailed exception following this message to find the root cause.
    CLFRL0494E: Error generating an event when recalculating the IP address of all URLs unexpected exception occurred when generating the event of recalculating the IP address of all URLs Check the detailed exception following this message to find the root cause.
    CLFRL0498E: Error generating an event when recalculating the IP address of URLs loaded from file unexpected exception occurred when generating the event of recalculating the IP address of URLs from a given file Check the detailed exception following this message to find the root cause. The file encoding may not be correct.
    CLFRL0493E: Error generating an event when recalculating the IP address of a URL Unexpected exception occurred when generating the event of recalculating the IP address of a given URL Check the detailed exception following this message to find the root cause.
    CLFRL0485E: Error generating an event when reprocessing the intranet flag for all URLs Unexpected exception occurred when generating the event of reprocessing the intranet flag for all URLs Check the detailed exception following this message to find the root cause.
    CLFRL0482E: Error generating an event when reprocessing the intranet flag for URLs loaded from file Unexpected exception occurred when generating the event of reprocessing the intranet flag for URLs from a given file Check the detailed exception following this message to find the root cause. The file encoding may not be correct.
    CLFRL0483E: Error generating an event when reprocessing the intranet flag for a URL Unexpected exception occurred when generating the event of reprocessing the intranet flag for a given URL Check the detailed exception following this message to find the root cause.
    CLFRL0497E: Error generating an event when replacing URLs Unexpected exception occurred when generating the event of replacing URLs Check the detailed exception following this message to find the root cause.
    CLFRL0487E: Error generating an event when replacing a URL Unexpected exception occurred when generating the event of replacing an URL Check the detailed exception following this message to find the root cause.
    CLFRL0442E: Failed to find URL {0}. The URL does not exist. The given URL is not found in Bookmarks DB records Check the specified URL and make sure it is correct.
    CLFRL0449E: Failed to find or create the target URL {0}. The URL can not be found in Bookmarks DB Check the detailed exception following this message to find the root cause.
    CLFRL0472E: Failed to send broken URL notifications to owners of URL {0}. Unexpected exception occurred when sending broken URL notifications to owners of an URL Check the detailed exception following this message to find the root cause.
    CLFRL0460W: No bookmark is found on URL {0}. No email notifications will be sent. No links related to the specified URL exist in the Bookmarks database. The links might have been deleted.
    CLFRL0461E: Failed to run the Notify command. Unexpected exception occurred when running the notify command. Check the detailed exception following this message to find the root cause.
    CLFRL0443E: Failed to open the file {0} Unexpected exception occurred when reading the file Check the file path. The file might be invalid, or the encoding may not be correct.
    CLFRL0462W: The original URL {0} and the substitute URL {1} are equal. The related bookmarks will not be updated. The two URLs are the same, no need to replace.
    CLFRL0438E: Failed to replace URL {0} to {1} Failed to replace the URL Check the detailed exception following this message to find the root cause.
    CLFRL0456W: Invalid content found in file {0}, {1} The file content is invalid Correct the file content.
    CLFRL0450E: Failed to run the FindURLsToReplace command Unexpected exception occurred when running the FindURLsToReplace command. Check the detailed exception following this message to find the root cause.
    CLFRL0454E: Failed to run the ReplaceURL command Unexpected exception occurred when running the ReplaceURL command. Check the detailed exception following this message to find the root cause.
    CLFRL0480E: Error generating an event when updating a member ID Unexpected exception occurred when updating a member id Check the detailed exception following this message to find the root cause.
    CLFRL0499E: Error generating an event when updating member IDs from file Unexpected exception occurred when updating member IDs, the IDs come from a file Check the detailed exception following this message to find the root cause.
    CLFRL0495E: Error generating an event when updating all member IDs Unexpected exception occurred when updating all member IDs Check the detailed exception following this message to find the root cause.
    CLFRL0429E: There is an inconsistent login name {0} in the Bookmarks member profile table for the member with display name {1}. The login name is inconsistent change the login in LDAP or IBM Connections Profiles Check the detailed exception following this message to find the root cause.
    CLFRL0486E: Error generating an event after populating the login names Unexpected exception occurred when populating the login names Check the detailed exception following this message to find the root cause.
    CLFRL0055E: Error getting URLs in batch Exception was thrown when getting the URLs in batch Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0506E: Error getting the most popular bookmarks Unexpected SQL exception was thrown when getting the most popular bookmarks Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0507E: Error getting person for id {0} Unexpected SQL exception was thrown when getting person with given ID Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0504E: Error getting the number of public bookmarks Unexpected SQL exception was thrown when getting the number of public bookmarks Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0503E: Error getting the number of private bookmarks Unexpected SQL exception was thrown when getting the number of private bookmarks Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0502E: Error getting the number of bookmarks which have description Unexpected SQL exception was thrown when getting the number of bookmarks which has description Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0463E: Error getting the number of most visited bookmarks Unexpected SQL exception was thrown when getting the number of most visited bookmarks Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0163E: Error getting link count for person {0} and URL {1} Unexpected SQL exception was thrown when getting the link count filtered by person and URL Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0097E: Error getting links for person {0} and URL {1} Unexpected SQL exception was thrown when getting the links filtered by person and URL Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0466E: Error getting all bookmarks on URL {0} Unexpected SQL exception was thrown when getting the links filtered URL Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0432E: Error updating the modified time of bookmarks on URL {0} Unexpected SQL exception was thrown when updating the modified time of a URL Check the detailed exception log following this message to find the root cause. It might be a database issue or a problem with the time format.
    CLFRL0479E: Error updating the modified time of bookmark {0} Unexpected SQL exception was thrown when updating the modified time of a bookmark Check the detailed exception log following this message to find the root cause. It might be a database issue or a problem with the time format.
    CLFRL0435E: Error changing URL ID from {0} to {1} Unexpected SQL exception was thrown when updating the URL ID Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0431E: Error getting the number of public bookmarks on URL {0} Unexpected SQL exception was thrown when getting the number of public bookmarks filtered by URL Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0464E: Error getting verbiage for links {0} Unexpected sql exception was thrown when getting the description of a bookmark Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0477E: Error generating an event after creating a new bookmark. Unexpected exception occurred when creating a bookmark Check the detailed exception following this message to find the root cause.
    CLFRL0489E: Error generating an event when editing a bookmark. Unexpected exception occurred when editing a bookmark Check the detailed exception following this message to find the root cause.
    CLFRL0500E: Error generating an event when deleting a bookmark. Unexpected exception occurred when deleting a bookmark Check the detailed exception following this message to find the root cause.
    CLFRL0492E: Error generating an event when purging deleted bookmarks. Unexpected exception occurred when purging deleted bookmarks. Check the detailed exception following this message to find the root cause.
    CLFRL0476E: Error generating an event after adding a person to watchlist. Unexpected exception occurred when adding a person to watchlist. Check the detailed exception following this message to find the root cause.
    CLFRL0488E: Error generating an event when removing a person from watchlist. Unexpected exception occurred when removing a person from watchlist. Check the detailed exception following this message to find the root cause.
    CLFRL0478E: Error generating an event after adding a tag to watchlist. Unexpected exception occurred when adding a tag to watchlist Check the detailed exception following this message to find the root cause.
    CLFRL0501E: Error generating an event when removing a tag from watchlist. Unexpected exception occurred when removing a tag from watchlist. Check the detailed exception following this message to find the root cause.
    CLFRL0043E: Error getting tag counts for person {0} and URL {1} Unexpected SQL exception was thrown when getting the tag counts for person and URL Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0005E: Error getting structured tag counts for person {0} and URL {1} Unexpected SQL exception was thrown when getting the structured tag counts for person and URL Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0490E: Error generating an event when importing bookmarks Unexpected exception occurred when importing bookmarks. Check the detailed exception following this message to find the root cause.
    CLFRL0475E: Error sending broken URL notifications to owners of URL {0}. Failed to send the broken URL notifications to all the owners of an URL Check the detailed exception following this message to find the root cause.
    CLFRL0481E: Error generating an event when sending broken URL notifications. Unexpected exception occurred when sending broken URL notifications. Check the detailed exception following this message to find the root cause.
    CLFRL0496E: Error generating an event when sending email notifications. Unexpected exception occurred when sending email notifications. Check the detailed exception following this message to find the root cause.
    CLFRL0505E: Error getting the number of visited bookmarks in the past {0} days Unexpected SQL exception was thrown when getting the structured tag counts filtered person and URL Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0511E: Error getting person with email {0} Unexpected SQL exception was thrown when getting the structured tag counts for filtered person and URL Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0512E: Error getting person with external ID {0} Unexpected exception occurred when getting person with external ID Check the detailed exception following this message to find the root cause.
    CLFRL0509E: Error getting person with internal ID {0} Unexpected exception occurred when getting person with internal ID Check the detailed exception following this message to find the root cause.
    CLFRL0514E: Error getting person with login name {0} Unexpected exception occurred when getting person with login name Check the detailed exception following this message to find the root cause.
    CLFRL0508E: Error updating record for person {0} Unexpected SQL exception was thrown when updating a person record Check the detailed exception log following this message to find the root cause. It might be a database issue.
    CLFRL0515E: Error initializing the User Life Cycle listener for Bookmarks Failed to initialize the User Life Cycle listener Check the detailed exception following this message to find the root cause.


    Common directory integration service error messages

    Use the codes included in the error messages generated by IBM Connections to identify problems with the common directory integration service and find their solutions.

    Table 7. Common directory integration service error messages with codes

    Message Cause Solution
    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 Set up federated repositories. If you edited the wimconfig.xml file, revert to the original copy of the file.
    CLFRK0003E: ID for '{0}' is not available The directory cannot find user profile data from backend services such as LDAP or the Profiles database, perhaps because the records have been deleted.

    1. Identify the missing records and make sure they are available in the backend services: either LDAP or the Profiles database.

    2. Resynchronize the records based on an email or login attribute value key for all of the services.
    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.


    Communities error messages

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

    The following Communities error messages are generated by IBM Connections:

    Table 8. Communities error messages

    Message Cause Solution
    CLFRM####E: A JNDI naming exception was caught, probably the result of a deployment error. An error occurred while accessing the scheduling EJB. Restart the Communities server. If problems persist, uninstall and reinstall the Communities application.
    CLFRM0001E: Communities https service url is malformed: {0}. The web address specified is in an invalid URL syntax. Correct the URL syntax.
    CLFRM0002W: SubjectHelper.cloneSubject was called with null subject. There is a problem with the authenticated user resulting in null information. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0003E: Communities http service url is malformed: {0}. The web address specified is in an invalid URL syntax. Correct the URL syntax.
    CLFRM0004I: Executing {0} request. The specified request is being executed. Informational message; no solution is needed.
    CLFRM0005E: Error executing update community name for {0}. Could not update specified community. Check the database connection. See the SystemOut.log file for more information about the error.
    CLFRM0006I: Executing create community. Community name: {0}. Create the specified community. Informational message; no solution is needed.
    CLFRM0007E: Error registering mbean. An exception was generated when registering the MBeans. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0008E: Error executing remove tags from {0}. Could not remove tags from specified community. Check the database connection. See the SystemOut.log file for more information about the error.
    CLFRM0009E: Unknown role assignment in createCommunity call: role must be either OWNER or MEMBER. Invalid role parameter used in administrative command. Correct the syntax and retry the command.
    CLFRM0010I: Executing add members to {0}. Add members to the specified community. Informational message; no solution is needed.
    CLFRM0011E: Error initializing Communities JMX support: failed to register {0}. The web address specified is in an invalid URL syntax. Correct the URL syntax.
    CLFRM0012I: Executing remove tags from {0}. Executing the specified command. Informational message; no solution is needed.
    CLFRM0013E: Error purging index. An error occurred while purging the full text index. Shut down and restart the server. If the error persists, report this problem to Customer Support.
    CLFRM0014E: Error locating MBeanServer, no Community Administration MBeans registered. An exception was generated when locating the MBean server needed to register the MBeans. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0015E: User {0} was not found. The specified user was not found in the directory. The command cannot be executed. Check the spelling of the user name and the directory configuration.
    CLFRM0016E: Error executing {0}. There was an error executing the specified request. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0017E: Error executing update community description for {0}. The description of the specified community could not be updated. Check the database connection. See the SystemOut.log file for more information about the error.
    CLFRM0018I: Executing update community name. Changing {0} to {1}. Update community name as specified. Informational message; no solution is needed.
    CLFRM0019E: Error initiating indexing operation. An error initializing the full text index. Shut down and restart the server. If the error persists, report this problem to Customer Support.
    CLFRM0020E: Error executing add members to {0}. Could not add members to specified community. Check the database connection. See the SystemOut.log file for more information about the error.
    CLFRM0021E: Error executing remove references by URI from {0}. Could not remove references from specified community. Check the database connection. See the SystemOut.log file for more information about the error.
    CLFRM0022E: Error executing create community. Community name: {0} Could not create a community with specified name. Check the database connection. See the SystemOut.log file for more information about the error.
    CLFRM0023I: Executing start indexing request. The index is being started. Informational message; no solution is needed.
    CLFRM0024I: Executing remove references by URI from {0}. Remove requested references from specified community. Informational message; no solution is needed.
    CLFRM0025I: Executing purge index request. The index is being purged. Informational message; no solution is needed.
    CLFRM0026I: Executing update community description for {0}. The community description is being updated. Informational message; no solution is needed.
    CLFRM0027E: Community not found: {0}. The community specified was not found. Informational message; no solution is needed.
    CLFRM0028E: Cannot create reference with duplicate URI: {0}. Cannot create a reference with the specified name. A reference with the specified name already exists within this community and cannot be duplicated. Please select a different name and execute the command again.
    CLFRM0029E: Error executing update all member external ids, profiles. The update member external IDs process encountered an error. Additional information relating to the failure can be found in the SystemOut.log file. If the problem persists after restarting the Communities application, contact Customer Support to report the incident.
    CLFRM0029I: Finished writing index at: {0}. The full text index task finished updating the index at the specified time. Informational message; no solution is needed.
    CLFRM0030E: Error: Index may be corrupted. Please re-run the indexing task to build a new index. The full text index may be corrupted. Full text search will not function. Use the administrative tasks to purge and reload the index.
    CLFRM0031E: Error retrieving IndexWriter. The server cannot update the full text index. If the error persists, stop, and then restart the server.
    CLFRM0032E: Error deleting community documents from the index. The server was unable to delete the documents from the full text index. Try again to delete the documents or use the administrative tasks to purge and reload the full text index.
    CLFRM0033E: There is no directory profile associated with this email address <mail address> The wsadmin command could not be performed because the specified email address did not match any entries in the directory. Correct the email address or use a login name to specify the user.
    CLFRM0033I: Initializing Communities Management. The communities management application is initializing. Informational message; no solution is needed.
    CLFRM0034E: Error writing last update to {0}. The server encountered an error when writing the full text index last update time to the file system. If the error persists, stop and then restart the server.
    CLFRM0035E: Severe error executing update member id, profile in batch mode. Processing will terminate. The update member external IDs process encountered an error. Additional information relating to the failure can be found in the SystemOut.log file. Investigate any additional errors that can be found in the SystemOut.log file.
    CLFRM0035I: Full-text search was started at: {0}. The full text search was started at the specified time. Informational message; no solution is needed.
    CLFRM0036E: Unable to find reference with id: {0}. A reference with the specified identifier was not found. Check the parameter value and try again. If the problem persists, check the database connection. See the SystemOut.log file for more information about the error.
    CLFRM0037E: User is not authorized to perform the indexing task on communities. The indexing task is not running under an authorized user account. Stop and then restart the server. If the error persists, report the problem to Customer Support.
    CLFRM0038E: Error retrieving the last update from {0}. The server encountered an error when retrieving the full text index last update time from the file system. If the error persists, stop and then restart the server.
    CLFRM0040E: The list argument passed to updateMemberIdBatch was null or empty No IDs were passed into the updateMemberIdBatch wsadmin command. Supply one or more IDs when using the updateMemberIdBatch command.
    CLFRM0039E: Internal error. An internal error has occurred. See the SystemOut.log file for more information about the error.
    CLFRM0040I: Starting to write the index at: {0}. The full text index task started to update the index at the specified time. Informational message; no solution is needed.
    CLFRM0041E: Unable to find community with id: {0}. The community with the specified identifier was not found. Check the parameter value and try again. If the problem persists, check the database connection. See the SystemOut.log file for more information about the error.
    CLFRM0042E: Schema Version Mismatch. The database schema does not match the application version. Upgrade the database using the specified procedure.
    CLFRM0043E: Cannot create community with duplicate name: {0}. Cannot create a community with the specified name. A community with the specified name already exists and cannot be duplicated. Please select a different name and execute the command again.
    CLFRM0044E: Error retrieving the full-text index. Stopping scheduled full-text indexing for Communities. The server could not initialize the full text indexing service. The indexing service is disabled. Stop, and then restart the server. If the error persists, report the problem to Customer Support.
    CLFRM0045E: Error parsing the search query. The search query syntax was invalid. Correct the syntax and issue the command again.
    CLFRM0046E: Error loading application plugins. A problem occurred while trying to load the Lotus Quickr connector. Additional information relating to the failure can be found in the SystemOut.log file. Examine the additional error messages in the log. If no straightforward fix can be determined, then reinstall the errant connector.
    CLFRM0046I: Stopping Communities Management. The communities management application is stopping. Informational message; no solution is needed.
    CLFRM0047E: User passed NULL directory member profile to getCurrentMemberProfile() method. The member profile parameter is invalid; a non-null value is required. Specify appropriate parameters for the request.
    CLFRM0048E: Error retrieving communities for indexing. An error occurred searching the full text index. Stop and then restart the server. If the error persists, report the problem to Customer Support.
    CLFRM0049E: NOT IMPLEMENTED. This function is not implemented. See the SystemOut.log file for more information about the error.
    CLFRM0050E: Cannot find credentials for <alias name> The J2C Authentication alias <alias name> could not be found. In the WebSphere Application Server Integrated Solutions Console, expand Security, select Global security, then expand Java Authentication and Authorization Service and select J2C authentication data, 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 WebSphere Application Server.

    2. Edit the security.xml file in the following directory: APPServer_HOME/profiles/AppSrv01/config/cells/cell

    3. Find the authDataEntries entry with an alias that includes <name>.

      For example:

      <authDataEntries alias="text/name"> 3.0.1

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

    5. Save the security.xml file.

    6. Restart the WebSphere Application Server. 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.
    CLFRM0050E: Error sending member added or member removed mail notification A mail notification alerting users that they have been added or removed from a community was not sent. Additional information relating to the failure can be found in the SystemOut.log file. Ensure that the SMTP and DNS servers configured in the notifications-config.xml are reachable.
    CLFRM0052E: Failed to create worker thread for the event queue. A background process failed to create a thread to handle additional work. If the problem persists after restarting the Communities application, contact Customer Support to report the incident.
    CLFRM0053E: Error adding application. A problem occurred while trying to load the Lotus Quickr connector. Additional information relating to the failure can be found in the SystemOut.log file. Examine the additional error messages in the log. If no straightforward fix can be determined, then reinstall the errant connector.
    CLFRM0054E: Error parsing communities-policy.xml: {0} The communities-policy.xml file is not in a valid format. Correct any minor syntax issues in the file or obtain a copy of this file from a clean install.
    CLFRM0055E: Error fetching Member list. Not identifiable without more information. Report this problem to Customer Support. Not identifiable without more information. Report this problem to Customer Support.
    CLFRM0056E: Error fetching Community Data. Not identifiable without more information. Report this problem to Customer Support. Not identifiable without more information. Report this problem to Customer Support.
    CLFRM0057E: Unable to get application list. Not identifiable without more information. Report this problem to Customer Support. Not identifiable without more information. Report this problem to Customer Support
    CLFRM0058E: Error adding application: {0} A problem occurred while trying to load the Lotus Quickr connector. Additional information relating to the failure should be found in the SystemOut.log file. Examine the additional error messages in the log. If no straightforward fix can be determined, then reinstall the errant connector.
    CLFRM0059E: Error fetching links and bookmarks. A problem occurred while running CommunitiesService.fetchReference() Ensure that all passed in community uuids are valid.
    CLFRM0066E: Error adding member, who has name: {0}, email: {1}, and member uuid: {2}, to community, which has name: {3}, and its community uuid: {4}. This error message may show if adding a person as a community member when the person is already a member or owner. Check to see if the person is now a member. If not, try to re-add the person. If problems persist, contact Customer Support.
    CLFRM0070E: Error updating property values in a link. Error while updating a managed application property value. Validate the specified link is valid.
    CLFRM0072E: Cannot find application "{0}" for community "{1}". A managed application could not be found for the specified community. Validate the managed application type and community uid are correct.
    CLFRM0073E: Unknown application <managed application name>. The specified <managed application name> could not be found. Correct the specified name.
    CLFRM0077E: Error caused by an invalid input. An invalid number of parameters or empty string parameters were passed to a wsadmin command for managed applications. See Communities administrative commands for the correct parameters to pass.
    CLFRM0078E: Error updating URI links in an application for a community. An error occurred while attempting to update a managed application link. Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0079E: Error fetching application link list. An error occurred while attempting to fetch managed application links. Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0081E: Error creating application link. An error occurred while attempting to create a managed application link. Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0082E: Error deleting application link. An error occurred while attempting to delete a managed application link. Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0083E: Error fetching application properties. An error occurred while attempting to fetch a managed application's properties. Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0084E: Error during initializing VenturaConfigurationHelper The server could not retrieve or successfully parse a LotusConnections-config.xml configuration file from the LotusConnections-config folder hierarchy. Correct any syntax errors in the file. If problems persist report this problem to Customer Support.
    CLFRM0085E: There is something wrong with VenturaConfigHelper The server could not retrieve or successfully parse a LotusConnections-config.xml configuration file from the LotusConnections-config folder hierarchy. Correct any syntax errors in the file. If problems persist report this problem to Customer Support.
    CLFRM0087E: The current database schema version for Communities is {0}, but the application expects {1}. Please update the schema version to match. The database scripts to migrate the Communities database schema to the current version need to be run. See Updating DBs for more information.
    CLFRM0088E: Error accessing database. An error occurred while doing a query on a database. Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0092E: There is no directory profile associated with this login name <login name> The wsadmin command could not be performed because the specified login name did not match any entries in the directory. Correct the login name or use an email address to specify the user.
    CLFRM0093E: Failed to delete bookmarks or feeds associated with deleted widget. <root cause> A bookmarks or feeds widget was deleted but the associated bookmarks and feed entries could not be deleted. Report this problem to Customer Support.
    CLFRM0095E: Error loading Communities Scheduler settings 'communities-config.xml'. Please check the validity of your IBM Connections Communities installation. The server could not retrieve or successfully parse the communities-config.xml configuration file from the LotusConnections-config folder hierarchy. Check the validity of the communities-config.xml file.
    CLFRM0097E: Error running Communities LifecycleRetryQueuedEvents scheduled task An error occurred while running the task that periodically retries failed life-cycle events. Ensure that all IBM Connections application are running.
    CLFRM0106E: Communities eventLog scheduled cleanup task The supplied task name was not recognized. Task names of .LifecycleRetryQueuedEvents., .EventLogCleanup., .ForumPurgeTrash. should be used.
    CLFRM0114E: JNDI naming exception caught. Connections Communities application has been incorrectly deployed. An error occurred while accessing the scheduling EJB. Restart the Communities server. If problems persist, uninstall and reinstall the Communities application.
    CLFRM0115E: Create task for task {0} failed to complete successfully. An error occurred while accessing the scheduling EJB. Restart the Communities server. If problems persist, uninstall and reinstall the Communities application.
    CLFRM0116E: Update task for task {0} failed to complete successfully. An error occurred while accessing the scheduling EJB. Restart the Communities server. If problems persist, uninstall and reinstall the Communities application.
    CLFRM0117E: Remove task for task {0} failed to complete successfully. An error occurred while accessing the scheduling EJB. Restart the Communities server. If problems persist, uninstall and reinstall the Communities application.
    CLFRM0119E: Create task for task {0} failed to complete successfully. A scheduled task has task information that is not valid. Report this problem to Customer Support.
    CLFRM0120E: Task is not valid and cannot be fired. A scheduled task has task information that is not valid. Report this problem to Customer Support.
    CLFRM0121E: Create task for task {0} failed to complete successfully. A scheduled task has task information that is not valid. Report this problem to Customer Support.
    CLFRM0122E: Create task for task {0} failed to complete successfully. The WebSphere Application Server scheduler was not available. Report this problem to Customer Support.
    CLFRM0123E: Update task for task {0} failed to complete successfully. The WebSphere Application Server scheduler was not available. Report this problem to Customer Support.
    CLFRM0124E: Remove task for task {0} failed to complete successfully. The WebSphere Application Server scheduler was not available. Report this problem to Customer Support.
    CLFRM0125E: Create task for task <task> failed to complete successfully. The interval settings for the <task> task were not valid. Correct the interval setting for the <task> task in the communities-config.xml file.
    CLFRM0126E: Update task for task {0} failed to complete successfully. The interval settings for the <task> task were not valid. Correct the interval setting for the <task> task in the communities-config.xml file.
    CLFRM0127E: Create task for task {0} failed to complete successfully. The interval settings for the <task> task were not valid. Correct the interval setting for the <task> task in the communities-config.xml file.
    CLFRM0128E: Update task for task {0} failed to complete successfully. The interval settings for the <task> task were not valid. Correct the interval setting for the <task> task in the communities-config.xml file.
    CLFRM0129E: Create task for task {0} failed to complete successfully. The interval settings for the <task> task were not valid. Correct the interval setting for the <task> task in the communities-config.xml file.
    CLFRM0130E: Update task for task {0} failed to complete successfully. The interval settings for the <task> task were not valid. Correct the interval setting for the <task> task in the communities-config.xml file.
    CLFRM0131E: Create task for task {0} failed to complete successfully. The notification sink for the scheduling EJB was invalid. Report this problem to Customer Support.
    CLFRM0132E: Update task for task {0} failed to complete successfully. The notification sink for the scheduling EJB was invalid. Report this problem to Customer Support.
    CLFRM0133E: Create task for task {0} failed to complete successfully. A notification exception occurred for the <task> task. Report this problem to Customer Support.
    CLFRM0134E: Update task for task {0} failed to complete successfully. A notification exception occurred for the <task> task. Report this problem to Customer Support.
    CLFRM0135E: Remove task for task {0} failed to complete successfully. A notification exception occurred for the <task> task. Report this problem to Customer Support.
    CLFRM0137E: Create task for task <task> failed to complete successfully. A remote exception occurred while completing <task> task. Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0138E: Update task for task <task> failed to complete successfully. The task is pending and cannot be paused or resumed. See the system error log for more detail about the exception. Report this problem to Customer Support.
    CLFRM0139E: Remove task for task {0} failed to complete successfully. A task pending exception occurred for the <task> task. Report this problem to Customer Support.
    CLFRM0140E: Create task for task <task> failed to complete successfully. The scheduled task <task> has task information that is not valid. Report this problem to Customer Support.
    CLFRM0141E: Update task for task {0} failed to complete successfully. The scheduled task <task> has task information that is not valid. Report this problem to Customer Support.
    CLFRM0142E: Remove task for task {0} failed to complete successfully. The scheduled task <task> has task information that is not valid. Report this problem to Customer Support.
    CLFRM0143E: Task named <task> is not one of the configured tasks. Note that the task names in communities-config.xml cannot be changed. The supplied task name <task> was not recognized. Task names of .LifecycleRetryQueuedEvents., .EventLogCleanup., .ForumPurgeTrash. should be used.
    CLFRM0144E: An exception occurred updating member id {0}, display name: {1}. The external id has not been updated. The attempt to update the member's external ID failed. Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0145E: There is a discarded login name <login name> in the Communities member profile table for the member with display name <display name>. This login name will be removed. The communities database has the <login name> for the person <display name> but the directory no longer has that login name. No action required. This message is just informational. The Communities database will be automatically updated to remove the previous login name.
    CLFRM0146E: There is an inconsistent login name <login name> in the Communities member profile table for the member with display name <display name>. For this member two or more login names resolve to different profiles in the directory. The external id has not been updated. The login name <login name> is assigned to multiple people in the directory. Update the directory to make login names unique, which is a prerequisite for IBM Connections.
    CLFRM0151E: An error occurred while updating last login time-stamp for <user> A problem occurred while updating the last login time for the user. Examine the additional error messages in the log.
    CLFRM0152E: An unexpected exception has occurred. The command failed to complete successfully. See the system error log (normally SystemErr.log) for more detail about the exception. An unexpected exception has occurred. The command failed to complete successfully. See the system error log (normally SystemErr.log) for more detail about the exception Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0153E: The specified task is not one of the known tasks. You cannot change the task name in communities-config.xml. The communities-config.xml file contains an unrecognized task name. Task names of .LifecycleRetryQueuedEvents., .EventLogCleanup., .ForumPurgeTrash. should be used.
    CLFRM0154E: The specified task is not registered with the Communities scheduler. The specified task is not registered with the Communities scheduler. Task names of .LifecycleRetryQueuedEvents., .EventLogCleanup., .ForumPurgeTrash. should be used.
    CLFRM0155E: JNDI naming exception caught. Connections Communities application has been incorrectly deployed. See the system error log (normally SystemErr.log) for more detail about the exception. An error occurred while accessing the scheduling EJB. Restart the Communities server. If problems persist, uninstall and reinstall the Communities application.
    CLFRM0156E: The IBM Connections Communities scheduler is not available, probably the result of a deployment error. See the system error log (normally SystemErr.log) for more detail about the exception. The IBM Connections Communities scheduler is not available, probably the result of a deployment error. See the system error log (normally SystemErr.log) for more detail about the exception Examine the additional error messages in the log. If no straightforward fix can be found, contact Customer Support to report the incident.
    CLFRM0158E: Task is not valid and status cannot be retrieved. See the system error log for more detail about the exception. A scheduled task has task information that is not valid. Report this problem to Customer Support.
    CLFRM0159E: The Notification Sink object failed to fire, probably the result of a deployment error. See the system error log (normally SystemErr.log) for more detail about the exception. The notification sink for the scheduling EJB was invalid. Report this problem to Customer Support.
    CLFRM0160E: The task is pending and cannot be paused or resumed. See the system error log for more detail about the exception. A scheduled task is pending and cannot be paused or resumed. See the system error log for more detail about the exception. Report this problem to Customer Support.
    CLFRM0161E: The task is not valid and cannot be paused or resumed. See the system error log for more detail about the exception. A scheduled task is invalid and cannot be paused or resumed. See the system error log for more detail about the exception. Report this problem to Customer Support.
    CLFRM0162E: Failure notifying remote widget applications of a community change: <root error message> Communities was not able to notify remote applications of a community change. Report this problem to Customer Support.
    CLFRM0163E: Failure retrieving values for a lifecycle event: <root error message> Communities was not able to notify remote applications of a community change. Report this problem to Customer Support.
    CLFRM0173E: Error inserting EventLogEntry: {0} Event data could not be saved to the database. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0174E: Error updating EventLogEntry: {0} Event data could not be saved to the database. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0175E: Error purging EventLogEntry: {0} Old event data could not be deleted. Not a problem in the short term - old event data will be purged when the task runs the next time. For a continual problem, report to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0176E: Error getting LogEntries: {0} Event data could not be read from the database. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0177E: Failed to locate authenticated user, {0}, in user directory. If WPI is enabled, the user could not be found in Profiles; the user may be missing, have an incorrect login name or be inactive in the Profiles database. If WPI is not enabled, the user could not be found in the LDAP directory. Update Profiles or the LDAP directory to have a valid entry for the user.
    CLFRM0178E: Cannot create community with duplicate handle: {0} A non-unique value was entered for the community's web address. Ensure the value entered for the community web address is unique.
    CLFRM0179E: Cannot create community with handle that is a reserved word: {0} A number of words in web addresses are reserved for potential future use by Communities. Use a different word in the web address for the community.
    CLFRM0180E: Cannot create community with handle that needs to be character-escaped in the URL: {0} An attempt was made to update a community web address with a value that contains invalid characters. Use only the letters A-Z, numbers 0-9, at sign (@), underscore (_), period (.), and hyphen (-) characters.
    CLFRM0181E: Cannot create community with handle that is in GUID format: {0} Web addresses are not allowed to use a format of XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where X is 0 - 9 or a-f. Use a different value for the web address of the community.
    CLFRM0182E: The community handle is too long. The value for the web address for the community is too long. Use a shorter value for the web address of the community.
    CLFRM0183E: Cannot locate the parent community from database by the community uuid: {0}. A subcommunity refers to a parent community that cannot be found. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0184E: Cannot locate the community from database, by the handle hierarchy: {0}. A community could not be located by the web address. Correct the requested web address.
    CLFRM0185E: The handle hierarchy, {0}, is too long. A web address was requested that had handles for more than one parent community. Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
    CLFRM0186E: The search service is unavailable at this time. A search could not be performed because the search service is unavailable. Examine the log files for errors specific to the search service and address any reported issues. Start the Search application.
    CLFRM0192E: Cannot create the specified directory {0}. An invalid directory path was passed as a parameter to a wsadmin command or Connections did not have rights to create the path. Pass in a valid path to an existing directory.


    Communities widget error messages

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

    The following error messages are generated by Communities widgets:

    Table 9. Communities widget error messages

    Message Cause Solution
    CLFWZ0001E: Failed to initialize widget lifecycle event propagater. The widget life-cycle framework failed to initialize. Validate widgets-config.xml settings. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFWZ0002E: Failed to handle posted lifecycle event. An application that maintains widget data failed to process a change in the containing community. Examine the logs for further information. If no resolution is evident, report this problem to Customer Support.
    CLFWZ0003E: Failed to post event notification to remote widget application handler: {0} Communities was unable to notify a remote application of a community change. Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
    CLFWZ0004E: Event '{0}' sent to remote lifecycle handler at {1} returned bad response: {2} Communities was unable to notify a remote application of a community change. Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
    CLFWZ0005E: Failed to propagate event to widget application handler: {0} Communities was unable to notify a remote application of a community change. Communities will automatically retry to send the event at a later time. Check log files for any blocking problems in the remote application.
    CLFWZ0006E: Local widget application handler failed: {0} Communities was unable to notify forums, bookmarks, or feeds of a community change. Examine the logs for further information. If no resolution is evident, report this problem to Customer Support.
    CLFWZ0011E: Failed to load widgets-config.xml: {0} The application was unable to read widgets-config.xml. Ensure the widgets-config.xml file exists in the LotusConnections-config directory, and ensure that it has the file permissions set so that the IBM WebSphere Application Server process can read it.
    CLFWZ0012E: Failed to queue event for replay: {0} A remote application could not be notified of a change in a community. The widget framework could not write an event record for this change so that it can be replayed in the future. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFWZ0013E: Add new {0} content is blocked until processing of prior content has completed for resource {1}. Try adding the content at a later time. A community owner tried to add a new widget to a community but the framework blocked the action because a prior widget of the same type has unprocessed life-cycle events. Process the life-cycle events for that community. For more information about processing the life-cycle events that occur within a community, see Administering community queued events. Once the queued events for that community have been processed or cleared, the new widget can be added.
    CLFWZ0014E: The remote application {0} does not support being reassigned or transferred to another resource A wsadmin command for transferring a remote applications was run on a remote application that does not support that function. The transfer commands are only supported for the Blogs, Activities, Files, and Wikis remote applications.
    CLFWZ0015E: No widget definition found with a definition id of '{0}' A wsadmin command was run with an invalid definition ID specified. Rerun the command with the correct definition ID - these IDs are case sensitive.
    CLFWZ0016E: Can not assign to resource with id {0}. Resource already has its unique instance of {1}. A wsadmin command for transferring a remote application was run that would result in two unique widget instances contained in the same community. Choose a different community as the destination or delete the blocking unique instance widget.
    CLFWZ0017E: Resource with id {0} was not found. A wsadmin command was run with an invalid community UUID specified. Rerun the command with the correct community UUID.
    CLFWZ0018E: Widget with instance id {0} was not found. A wsadmin command was run with an invalid widget instance ID specified. Rerun the command with the correct widget instance ID.
    CLFWZ0019E: Only one instance of that widget content can be added. A second instance of widget was added for a widget type that only allows one widget per community. Make use of the existing widget or use a different community if necessary.
    CLFWZ0020E: Operation failed because the user is no longer logged in. A widget action failed because the user is no longer logged in. Log in and repeat the action.
    CLFWZ0021E: Operation failed because the user lacks the permissions to perform that change. A widget action failed because the user lacks privileges. Ask a community owner to make you an owner or to perform the action for you.
    CLFWZ0022E: Operation failed because a remote system was not available. A widget action failed because a remote application that hosts widget content is not running or otherwise available. Contact a system administrator to have the remote application restarted.


    Core error messages

    Use the codes included in the error messages generated by IBM Connections to identify problems with IBM WebSphere Portal infrastructure and IBM HTTP Server and find solutions.

    The following error messages are generated by WebSphere Portal infrastructure and IBM HTTP Server:

    Table 10. WebSphere Portal infrastructure error messages

    Message Cause Solution
    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 11. 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 WebSphere Application Server plug-in. The WebSphere Application Server SSL certificate might not be trusted by the WebSphere Application Server plug-in configured for the IBM HTTP Server. If this error occurs, check both your IBM HTTP Server and WebSphere Application Server 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, Configuring the IBM HTTP Server for SSL.


    Forums error messages

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

    The following forum error messages are generated by IBM Connections:

    Table 12. Forum error messages

    Message Cause Solution
    CLFRV0001E: Error getting server URL for {0}. There was an error reading the server URL for the specified service.

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

    2. Make sure that the files exists and is readable by the IBM WebSphere Application Server process.

    3. Make sure that the files contain the correct entry for the specified service.
    CLFRV0002E: Cannot find config variable directory {0}. 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 WebSphere Application Server.
    CLFRV0003E: Error validating configuration file {0}. 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.
    CLFRV0004E: Cannot find {0} for config variables. There was a problem opening a file getting configuration variables. Make sure that the file exists and is readable by the WebSphere Application Server.
    CLFRV0006W: Missing system setting for {0}. Error locating the indicated configuration variable. Make sure that the file exists and is readable by the WebSphere Application Server. This is most likely a variable that should be in an IBM Connections configuration file, such as forum-config.xml. Replace the current copy with a backup copy of the file.
    CLFRV0007E: Error loading config variables from {0}. There was a failure parsing variables in file.

    1. Make sure the file exists and is readable by the WebSphere Application Server.

    2. Replace the current copy with a backup copy of the file.
    CLFRV0008E:Error, unable to find object with uuid: {0} Unable to locate an object with the specified UUID. The context of the error should indicate what type of object is in question. It is typically a forum, topic, or reply. The administrator can ensure that the object with this UUID is in the database. Be aware that soft-deleted objects are usually ignored and treated as missing by mainline functionality.
    CLFRV0009I: Using DynaCache for user subjects This message is informational only. No action is required.
    CLFRV0010I: Using simple cache for user subjects This message is informational only. No action is required.
    CLFRV0011E: {0}: 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. Check settings in forum-config.xml.
    CLFRV0016E: Unable to refresh cached list of groups The 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 Forums application, contact Customer Support to report the incident.
    CLFRV0020I: Initializing Forums management. This message is informational only. No action is required.
    CLFRV0025E: Error purging trash The TrashCollectionService wsadmin object received an exception executing a purgeTrash command. Verify the parameter to the purgeTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0026E: Error fetching trash The TrashCollectionService wsadmin object received an exception executing a fetchTrash command. Verify the parameter to the fetchTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0027E: Error updating profile An error occurred while updating a member profile. If this was via a wsadmin 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.
    CLFRV0028E: Error fetching profiles An error occurred while retrieving a member profile. If this was via a wsadmin 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.
    CLFRV0029E: Error undeleting trash The TrashCollectionService wsadmin object received an exception executing a undeleteTrash command. Verify the parameter to the undeleteTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0030E: Error locating MBeanServer, no Forums Administration MBeans registered An exception was generated when the forum tried to locate the MBean server needed to register the Forums Administration MBeans. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0031E: Error initializing Forums JMX support: failed to register {0} An error occurred while registering the MBeans used for wsadmin commands. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0032E: {0} 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.
    CLFRV0033E: subscriber did not start: {0}. 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.
    CLFRV0034E: could not inform a subscriber of event: {0}. 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.
    CLFRV0035E: Error getting server URL for {0}. There was an error reading the server URL for the specified service.

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

    2. Make sure that the files exists and is readable by the WebSphere Application Server process.

    3. Make sure that the files contain the correct entry for the specified service.
    CLFRV0036E: Cannot find config variable directory {0}. 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 WebSphere Application Server.
    CLFRV0037E: 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.
    CLFRV0038E: Cannot find {0} for config variables. There was a problem opening a file getting configuration variables. Make sure that the file exists and is readable by the WebSphere Application Server.
    CLFRV0040W: Missing system setting for {0}. The specified configuration variable was requested but not found during a configuration initialization. If the configuration file is known (for example, if it was edited), check the property name. Otherwise contact Customer Support.
    CLFRV0041E: Error loading config variables from {0}. There was a failure parsing variables in file.

    1. Make sure the file exists and is readable by the WebSphere Application Server.

    2. Replace the current copy with a backup copy of the file.
    CLFRV0042E: 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 forum. Ensure the version property of the <config> element in forum-config.xml matches the version expected by the forum.
    CLFRV0043E: ExecutionContext leak detected The Forums application has detected a resource leak. Restart the Forums application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0044I: Forums application context is {0} This message is informational only. No action is required.
    CLFRV0045E: Internal Error, EC Count is null The Forums application has detected a resource leak. Restart the Forums application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0046E: Error publishing event {0} The Forums 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 Forums application, contact Customer Support to report the incident.
    CLFRV0047E:Error fetching deleted items to purge. The scheduled TrashAutoPurge job received an exception fetching the items to purge. Restart the Forums application. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0050I: {0}: Job started. The specified job was started. Informational only; no action is required.
    CLFRV0051I: Purge stopped. The forum purge task has stopped. Informational only; no action is required.
    CLFRV0053W: Purge expiration period (days) either not specified or invalid ({0}). Defaulting to {1} days. The forum purge expiration date in forum-config.xml is either missing or not set, and the default value is used. Check settings in the forum-config.xml file.
    CLFRV0054I: {0}: Job stopped. The specified forum job has stopped. Informational only; no action is required.
    CLFRV0055I: Purge started. This message is informational only. No action is required.
    CLFRV0058E: unable to upload the file: {0} {1}. An error occurred while retrieving or uploading a file to the forum content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify the directory and file information is correct.
    CLFRV0060E: The file does not exist. A file (for example, an attachment or thumbnail) was to be deleted but was not found. Ensure that the Forums content store exists and that it is configured properly using WebSphere Application Server environment variables.
    CLFRV0061E: error encountered while purging content: {0} {1}. An error occurred while deleting the contents of a file from the forum content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify the directory and file information is correct.
    CLFRV0063E: unable to create the file upload directory: {0}. The directory given in the forum-config.xml file for the element property name "root.directory" either could not be found or created. This directory is used for file uploads to the forum content store. Check that the directory exists; create it if it does not exist.
    CLFRV0065E: unable to delete the file: {0}. An error occurred while deleting a file from the forum content store. Additional information relating to the failure may be found in the SystemOut.log file. Verify the directory and file information is correct.
    CLFRV0067E: The file is read only. A file (for example, an attachment or thumbnail) was to be deleted but is protected. Check privileges on the forum content store files and directories.
    CLFRV0069E: unable to purge file {0} {1}. An error occurred while purging a file (for example, an attachment or thumbnail). Ensure that the Forums content store exists and that it is configured properly using WebSphere Application Server environment variables and is accessible.
    CLFRV0072E: forums object store did not start: {0}. The Forums Object Store service implemented by {0} did not start. Additional information relating to the failure may be found in the SystemOut.log file. Verify the <objectStore> configuration information in forum-config.xml is correct. If the problem persists after restarting the Forums feature, contact Customer Support to report the incident.
    CLFRV0081E: error terminating forums object store. An error occurred while terminating the Forums content store. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0083E: Profile ID: {0} does not exist. The member profile with the indicated memberId was not found in the Forums database. Check the Forums database for this memberId. Also, check the Systemout.log file for any precursor errors that may have lead to this error.
    CLFRV0085E: Error getting AclEntries for an activity: {0} An error occurred retrieving the ACL entries for the indicated forum. Check the forum database to see if ACL entries exist for this forum. Also, check the Systemout.log file for any precursor errors that may have lead to this error.
    CLFRV0086E: Unable to process event "{0}" . An exception was thrown: An error occurred while processing the specified internal event. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0088E: Invalid event type An invalid or unrecognized life-cycle event was received by the Forums life-cycle handler. The IBM Connections configuration file widgets-config.xml declares the Forums life-cycle events. If this error is valid and persists after restarting the Forums application, contact your system administrator.
    CLFRV0091E: Error getting Node: {0} An error occurred accessing a node. See Systemout.log for more information.
    CLFRV0093E: {0} the class "{1}" 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.
    CLFRV0096E: Error getting Tag: {0} An error occurred while retrieving tags. Check Systemout.log for additional information.
    CLFRV0097E: Error purging AclEntry: {0} An error occurred while purging ACL entries. Check Systemout.log for additional information.
    CLFRV0098E: Error deleting subscription(s) {0} An error occurred while deleting a subscription. Check Systemout.log for additional information.
    CLFRV0099E: Error getting ContentReference: {0} An error occurred while retrieving file (attachment, thumbnail) information. Check Systemout.log for additional information.
    CLFRV0100E: Error updating Node: {0} An error occurred while updating a node. Check Systemout.log for additional information.
    CLFRV0101E: Invalid initiatorUserId or initiatorEmail The Forums life-cycle handler was unable to build an internal subject for the provided external ID or email for a user. Check Systemout.log for any precursor errors. Ensure that the user information exists in the Communities database. User information should also appear in the Forums database.
    CLFRV0102E: Error inserting AclEntry: {0} An error occurred inserting a forum ACL entry. Check Systemout.log for additional information.
    CLFRV0104E: Error updating Tag: {0} An error occurred while updating a tag. Check Systemout.log for additional information.
    CLFRV0105E: Error purging ContentReference: {0} An error occurred while purging a content reference, which is a record to file storage. Check Systemout.log for additional information.
    CLFRV0106E: Error removing forums by a given containerUuid An error occurred while removing forums. Check Systemout.log for additional information.
    CLFRV0107E: Error updating Schema Version: {0} An error occurred while updating the specified schema version. Check Systemout.log for additional information.
    CLFRV0108E: Error getting AclEntry by member and node: {0} An error occurred while retrieving a member's ACL entries on a forum. Check Systemout.log for additional information.
    CLFRV0109E: Error getting nodes: {0} An error occurred retrieving nodes. Check Systemout.log for additional information.
    CLFRV0113E: Error retrieving forum count for container {0} An error occurred retrieving the forum count within a container or community. Check Systemout.log for additional information.
    CLFRV0114E: Error purging node: {0} An error occurred purging a node. Check Systemout.log for additional information.
    CLFRV0115E: Required parameter MemberID was not specified An invalid memberId was encountered. Review input parameters and ensure that the memberId is specified.
    CLFRV0117E: Schema Version Mismatch The system is expecting a certain schema version on the database. However, the database is reporting it has a different version. Upgrade the Forums codebase, or upgrade the database schema to match.
    CLFRV0118E: No such Sort Key - {0} The specified value is not a valid sort key. This is typically an internal error. If this error was encountered via the forum feed API, ensure that your feed URL has a valid sorting option as documented in the Developing section of the documentation.
    CLFRV0120E: Error inserting EventLogEntry: {0} An error occurred while inserting an event log entry. Check Systemout.log for additional information.
    CLFRV0121E: Bad configuration. Config section defines more properties than values, or vice versa. Possible errant <property> element(s) without a "name" attribute(s) An invalid configuration file was encountered. Check for possible errant <property> elements without a name attribute.
    CLFRV0122E: Error purging Tag: {0} An error occurred while purging a tag. Check Systemout.log for additional information.
    CLFRV0125E: Error retrieving topic count for forum {0} An error occurred while retrieving the topic count in a forum. Check Systemout.log for additional information.
    CLFRV0127E: Error getting Schema Version: {0} An error occurred while retrieving the forum schema version. Check Systemout.log for additional information.
    CLFRV0128E: Error adding a new forum by a given containerUuid A life-cycle handler error occurred while adding a new forum Check Systemout.log for additional information.
    CLFRV0129E: Error loading configuration settings to determine if external email exposure is enabled: {0} An error occurred while determining if the expose email option is enabled or disabled. Check that the property exists in LotusConnections-config.xml.
    CLFRV0130E: {0} - All passed AclEntrys must refer to the passed object The inserted ACL entries do not refer to the input object. This is likely an internal error or any external
    CLFRV0131E: No thumbnail exists for {0} No thumbnail exists for the indicated content ID. Ensure that the Forums file storage is properly configured.
    CLFRV0132E: Error purging MemberProfile: {0} An error occurred while purging a member profile record. Check Systemout.log for additional information.
    CLFRV0134E: {0} the class "{1}" 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 indicated class could not be instantiated. Investigate whether something is wrong with the classloader or the class specified in the <eventBroker> configuration itself. Additional information relating to the failure can be found in the SystemOut.log file.
    CLFRV0135E: Error removing node: {0} An error occurred removing a node. Look in Systemout.log for additional information.
    CLFRV0137E: Error inserting ContentReference: {0} An error occurred while inserting a reference to data stored on the files system. Check Systemout.log for additional information.
    CLFRV0138E: Error getting all nodes: {0} An error occurred retrieving all nodes with specified sort options. Check Systemout.log for additional information.
    CLFRV0139E: Error inserting a subscription An error occurred inserting a subscription. Check Systemout.log for additional information.
    CLFRV0140E: Error purging description spillover: {0} An error occurred while purging description spillover. Check Systemout.log for additional information.
    CLFRV0142E: Error retrieving reply count for topic {0} An error occurred retrieving the number of replies in a topic. Check Systemout.log for additional information.
    CLFRV0143E: Error getting NodeSummary: {0} An error occurred retrieving node summary information. Check Systemout.log for additional information.
    CLFRV0144I: {0} parsing done. Configuration file parsing has completed. Informational only; no action is required.
    CLFRV0145E: Error updating the topic count for forum {0} An error occurred while updating the topic count in a forum. Check Systemout.log for additional information.
    CLFRV0149E: Error updating AclEntry: {0} An error occurred while updating a forum ACL entry. Check Systemout.log for additional information.
    CLFRV0150E: Can not create MemberProfile. Profile ({0}) already exists. A member profile cannot be added as the supplied (internal forum) member ID is already assigned. If an insert was issued via wsadmin commands, check the input parameters.
    CLFRV0152E: Can not disable security; user is not an administrator The current user cannot alter security settings. This is an internal error.
    CLFRV0153E: Error inserting Schema Version: {0} An error occurred while updating the Forums schema number. Check Systemout.log for additional information.
    CLFRV0155E: no default content store defined No default content store was found in the forum-config.xml file. Verify the <objectStore> configuration information in forum-config.xml is correct. If the problem persists after restarting the Forums feature, contact Customer Support to report the incident.
    CLFRV0156E: {0} illegal access exception for the class "{1}". A Java IllegalAccessException occurred while attempting to parse configuration files. Ensure that the application is running with an account that has access to the indicated file.
    CLFRV0158E: Error updating MemberProfile: {0} An error occurred while updating a member profile. Check Systemout.log for additional information.
    CLFRV0159E: Error updating the reply count for topic {0} An error occurred while updating a topic's reply count. Check Systemout.log for additional information.
    CLFRV0160E: content ref uuid: {0} An error occurred while opening a content reference Check Systemout.log for additional information.
    CLFRV0161E: Error undeleting node: {0} An error occurred while undeleting (removing a soft-deleted designation) a node. Check Systemout.log for additional information.
    CLFRV0162E: Null resourceName The Forums life-cycle handler received a request with no resource name. This is an internal error.
    CLFRV0164E: Could not locate MBean Server An exception was generated when the forum tried to locate the MBean server needed to register the Forums Administration MBeans. Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0166E: Null resourceId The Forums life-cycle handler received a request with no resource ID. This is an internal error.
    CLFRV0167E: Failed to initialize {0} An error occurred initializing IBATIS configuration. The most probable issue is the inability to connect to the target database.
    CLFRV0168E: Error purging EventLogEntry: {0} An error occurred while purging event log entries. Check Systemout.log for additional information.
    CLFRV0171E: Error creating thumbnail for {0} An error occurred while creating a thumbnail. Verify that the forums content store is properly configured. Check Systemout.log for additional information.
    CLFRV0172E: Error getting MemberProfile: {0} An error occurred while retrieving member profile. Check Systemout.log for additional information.
    CLFRV0173E: Error updating number of posts count for forum: {0}, member: {1} An error occurred updating the number of posts in a forum. Check Systemout.log for additional information.
    CLFRV0174E: Error retrieving subscriptions for topic {0} An error occurred retrieving a subscription. Check Systemout.log for additional information.
    CLFRV0176E: Error getting Tags from a node: {0} An error occurred while retrieving tags for the indicated node. Check Systemout.log for additional information.
    CLFRV0178E: Error getting AclEntry by uuid: {0} An error occurred retrieving an ACL entry with the indicated UUID. Check Systemout.log for additional information.
    CLFRV0181E: Error inserting Node: {0} An error occurred inserting a node. Check Systemout.log for additional information.
    CLFRV0182E: Cannot create the acl entries for the activity because an owner entry was required but not found An error occurred creating ACLs when creating a forum because an owner was not found. Possible causes include a configuration that is preventing communities from including proper membership roles.
    CLFRV0184E: Error inserting Tags: {0} An error occurred while inserting tags. Check Systemout.log for additional information.
    CLFRV0186E: {0} error initializing adapter: classname 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.
    CLFRV0187E: Error inserting description spillover: {0} An error occurred while inserting description spillover (clob data) for a node. Check Systemout.log for additional information.
    CLFRV0189E: Error retrieving forum ids for container {0} An error occurred while retrieving forum IDs in a container or community. Check Systemout.log for additional information.
    CLFRV0190E: Stream is not Open An error occurred while writing a file. Check Systemout.log for additional information.
    CLFRV0191E: Error inserting MemberProfile: {0} An error occurred while inserting a member profile record. Check Systemout.log for additional information.
    CLFRV0192E: Error getting getMemberProfilesByName: {0} An error occurred while retrieving a member profile for the indicated name. Check Systemout.log for additional information.
    CLFRV0195E: Error starting the active content filter. The active content filter received an error on start up. Contact Customer Support to report the incident.
    CLFRV0196E: 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.
    CLFRV0197E: Unable to refresh cached list of groups An error occurred refreshing an internal group cache. Restart the Forums application. Additional information relating to the failure can be found in the SystemOut.log file. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0199E: Error locating member profile for {0}, search type {1} Forum could not locate a member profile matching the input identifier and type (either login name, email, or memberid). Restart the Forums application. Additional information relating to the failure can be found in the SystemOut.log file. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0200E: Unable to refresh cached list of groups An error occurred while refreshing an internal group cache. Restart the Forums application. Additional information relating to the failure can be found in the SystemOut.log file. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0201E: Profile provider error: {0} A Directory Service error was encountered. Check Systemout.log for additional information.
    CLFRV0202E: Error locating member profile for {0}, search type {1} Forum could not locate a member profile matching the input identifier and type (either login name, email, or memberid). Restart the Forums application. Additional information relating to the failure can be found in the SystemOut.log file. If the problem persists after restarting the Forums application, contact Customer Support to report the incident.
    CLFRV0204E: Error, attempt to purge a node that is not a topic nor a forum. Node id: {0} An request was made to purge a node that is neither a topic nor a forum. Check the input node UUID and ensure that it identifies an existing forum or topic.
    CLFRV0206E: Error, attempt to purge a forum, but node is not a forum. Node id: {0} A request was made to purge a forum, but the supplied node UUID does not identify a forum. Check the input node UUID and ensure that it identifies an existing forum or topic.
    CLFRV0208E: A MemberProfile cannot be null. A member profile that is null, or which has a null external ID was attempted to be updated. Check Systemout.log for additional information.
    CLFRV0209E: The content of mime type: "{0}" or filename: "{1}" you tried to upload is not allowed by your administrator. The indicated MIME type is not allowed for downloads as configured in forum-confg.xml. Check the objectStore configuration in the forum-config.xml file for allowed MIME types.
    CLFRV0210I: Forums Schema being used is {0}. This reports the forum schema version (number) in the currently deployed database. Informational only; no action is required.
    CLFRV0211E: Error, attempt to purge a topic, but node is not a topic. Node id: {0} A request was made to purge a topic, but the supplied node UUID does not identify a topic. Check the input node UUID and ensure it identifies an existing topic.
    CLFRV0212E: Error locating profile: EXID mismatch, but email matches. There was an attempt to create or update a member profile but the email is the same as an existing member profile. Ensure that the member being created does not attempt to use a previously assigned email.
    CLFRV0213E: The profile provider could not find information for member {0}. Could not locate a member with the supplied member ID. Determine if the member exists in the directory service. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0214E: More than one member profile matches the search for {0}. More than one member profile matches the search for by name and type. Ensure that members are uniquely defined in directory services.
    CLFRV0215E: Error updating last login time for {0} An error occurred while updating the last login time for the indicated user. Check Systemout.log for additional information.
    CLFRV0216I: Access Violation: CALLER [{0}]: OBJECT [{1}]: OBJECT_PERMISSIONS[{2}]: REQUESTED[{3}]. General access violation report. The requestor does not have sufficient privileges. This error might occur if the user's participation (as member or owner) in a community cannot be established. This may ultimately be an LDAP and community configuration problem.
    CLFRV0217E: The file "{0}" cannot be uploaded as it is a 0-byte file. Zero byte files are not downloaded. Informational only; no action is required.
    CLFRV0218E: Cannot update non-matching MemberProfiles. {0} is not {1}. An attempt was made to update a profile and a mismatched member id was provided. Check that the command to update a member is accurate. Forums is reporting that its persisted member ID does not match the supplied value.
    CLFRV0219E: A profile provider error has occurred. {0} A Directory Service error was encountered. Check Systemout.log for additional information. This may be indicative of a Directory Service configuration issue.
    CLFRV0220I: Updated MemberProfile from LDAP for EXID {0} (user={1}). A member profile record was updated. Informational only; no action is required.
    CLFRV0221E: The content of mime type: "{0}" or filename: "{1}" you tried to upload exceeded the size limit of {2} 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. Check the upload limits in the <sizeLimits> element in forum-config.xml or upload something smaller.
    CLFRV0223E: An error occurred while propagating an event. The Forums application generated an exception. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure can be found in the SystemOut.log file.
    CLFRV0224E: Forums Schema Version Mismatch. Current database schema version is {0}. Forums requires version {1}. The system is expecting a certain schema version on the database. However, the database is reporting it has a different version. Upgrade the Forums codebase, or upgrade the database schema to match.
    CLFRV0226E: Error: the group profile "{0}" could not be located in the Forums database. This error is encountered during LDAP synchronization. The group could not be located in the Forums database. Check the spelling of the group name.
    CLFRV0227E: 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 Forums database could not be located in LDAP. Check the spelling of the group name.
    CLFRV0228I: The user with external ID "{0}" does not have a login name. This error is encountered during LDAP synchronization. The member with the indicated external ID does not have a login name. Check the LDAP registry.
    CLFRV0229I: The group profile "{0}" has been synchronized with the directory services changing the external id from {1} to {2}. A group profile record was updated. Informational only; no action is required.
    CLFRV0230E: Error: the member profile "{0}" could not be located in the Forums database. This error is encountered during LDAP synchronization. The person could not be located in the Forums database. Check the profile for the referenced user and ensure that the spelling of the supplied look-up field matches.
    CLFRV0231I: Processing login names table for {0} profiles. This message is informational only. No action is required.
    CLFRV0232I: The member profile "{0}" has been synchronized with the directory services changing the external id from {1} to {2}. This message is informational only. No action is required.
    CLFRV0233I: Processed login names table for {0} profiles; {1} were updated. This message is informational only. No action is required.
    CLFRV0234I: The member profile "{0}" matches the directory service with external id {1}. This message is informational only. No action is required.
    CLFRV0235E: internal error The forum generated an exception. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0236I: The user "{0}" does not have any login names. This is an informational message that might appear during population of the member login table. It notes that the member being processed does not have any login names. Informational only; no action is required.
    CLFRV0237E: 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.
    CLFRV0238E: 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.
    CLFRV0239I: The user "{0}" does not have an email address This message is informational only. Informational only; no action is required.
    CLFRV0240E: Error: An error occurred while updating the login names for user "{0}". The internal error is {1} Additional details of the error are given in the error message. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure can be found in the SystemOut.log file.
    CLFRV0241I: The group profile "{0}" matches the directory service with external id {1}. This message is informational only. Informational only; no action is required.
    CLFRV0242E: profile provider error The forum received an error querying the directory (i.e. LDAP) for a user or group. Ensure that the LDAP server configured for the WebSphere Application Server is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
    CLFRV0243E: 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. Try to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
    CLFRV0244E: exception while executing JTidy on node: {0} 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. Try to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
    CLFRV0245E: output from JTidy execution: {0} 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.
    CLFRV0246E: internal error while executing JTidy on node: {0} 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. Try to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
    CLFRV0247I: Using DynaCache for user subjects This message is informational only. Informational only; no action is required.
    CLFRV0248E: Unable to locate the dynacache {0} : {1} An internal error occurred while attempting to locate the dynamic cache with the specified name. Additional details of the error are given in the error message. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0249I: Using simple cache for user subjects This message is informational only. Informational only; no action is required.
    CLFRV0250E: {0}: Bad configuration. Config section defines more properties than values, or vice versa. Possible errant <property> element(s) without a "name" attribute(s) An error occurred while reading values from the forum-config.xml configuration file. Check that the configuration file has suitable values for the parameters.
    CLFRV0252I: Total password changes made: {0} Should not see this error message. Application is not enabled. Informational only; no action is required.
    CLFRV0255E: Unable to refresh cached list of groups An error occurred while synchronizing group membership. Additional details of the error are given in the error message.
    CLFRV0258E: Error initializing the Notification service for {0}. No notification messages will be sent. Error details : {1}. An error occurred while initializing the Notification service. Additional details of the error are given in the error message.
    CLFRV0263I: The Notification service for {0} is disabled in the configuration. No notification messages will be sent. This message is informational only. No action is required.
    CLFRV0264E: Error parsing administrator email address. {0} The administrator email address configured in forum-config.xml is badly formatted. Edit notification-config.xml and provide an administrator email address in the correct format in the sender element.
    CLFRV0266E: Error. The value given for "{0}" in LotusConnections-config.xml is invalid. An error occurred while retrieving the specified value from LotusConnections-config.xml. Check that the configuration file has a suitable value for the parameter.
    CLFRV0267E: Unable to find a member profile for the email "{0}". This user will not be added to the forum membership. Should not see this error message. Application is not enabled. Should not see this error message. Application is not enabled.
    CLFRV0278E: Error sending notification message to {0}. Error when trying to send an email notification. Additional details of the error are given in the error message.
    CLFRV0281E: Error determining subscription {0} An error occurred while determining if a member is subscribed to a topic. Additional details of the error are given in the error message.
    CLFRV0282E: A fatal error occurred while sending a notification message. Error when trying to send an email notification. Additional details of the error are given in the error message.
    CLFRV0283I: See the embedded description for more details : {0} Error when trying to send an email notification. Additional details of the error are given in the error message.
    CLFRV0285E: Error getting posts in forum: {0} An error occurred while retrieving forum posts from the database. Additional details of the error are given in the error message.
    CLFRV0286E: Error reading subscription {0} An error occurred while retrieving forum topic subscription details from the database. Additional details of the error are given in the error message.
    CLFRV0287E: unable to download the file: {0} {1}. An error occurred while downloading a file attachment. The specified file could not be found or an error occurred while it was being read.
    CLFRV0288E: Error: An error occurred while initializing the News propagation service. The internal error is : {0} The Forums application generated an exception. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0289E: Error setting delete reason: {0} Error while setting the delete reason in the database. Additional details of the error are given in the error message.
    CLFRV0293W: Forum can not determine host name Forums was unable to determine the host name during its start-up sequence. Restart the Forums application. If the problem persists, contact Customer Support.
    CLFRV0295I: Forum Notification service started This message is informational only. No action is required.
    CLFRV0301E: Forum Notification service initialization error: {0} Error while initializing the forum notification service. Additional details of the error are given in the error message.
    CLFRV0303E: Error executing event notification. The forum generated an exception. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0304E: 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. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0305E: 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. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0306E: 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. If the problem persists after restarting the Forums application, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0307E: Error initializing Discussion Forums The Forums application encountered an error while trying to start. The cause of the error will be found in the SystemOut.log. Correct the error cause and restart the Forums application.
    CLFRV0309E: Error cannot post to a locked node: {0} The topic or forum is locked and cannot accept a post. Informational only; no action is required.
    CLFRV0310E: Error deleting a page hierarchy entry: {0} An error occurred while deleting the category's descendant information. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0311E: Error inserting a page: {0} An error occurred while creating a category. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0312E: Error retrieving page descendant: {0} An error occurred while retrieving a category descendant. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0313E: Error incrementing page position: {0} This message is displayed if an error occurs when updating category data from the database. This issue is usually caused by a database problem. Check any SQL exceptions in the SystemOut.log file and fix according to the error message.
    CLFRV0314E: Maximum number of attachments have been added to this post: {0} This error occurs when the number of attachments exceeds the limitation defined by the administrator. To increase the number of attachments per post, follow the instructions for editing the Forums configuration file, forum-config.xml. in the topic, Set the maximum number of attachments.
    CLFRV0315E: Error retrieving a reply or set of replies: {0} An error occurred while retrieving a reply or a set of replies. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0316E: Error incrementing page level in tree : {0} An error occurred while incrementing a category's level in the category tree. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0317E: Error creating attachment for node: {0}, file name: {1} This message displays if an error occurs when creating the attachment for a topic or a reply. Check any exception from the SystemOut.log file and fix it according to the error message. Make sure that the file name exists in the path.
    CLFRV0318E: Error locking a node: {0} An error occurred while locking a forum or topic. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0319E: Error removing page: {0} An error occurred while removing a category. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0320E: Error updating page: {0} An error occurred while updating a category. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0321E: Error inserting page tree entry: {0} An error occurred wile creating category tree information. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0322E: Error inserting page hierarchy entry: {0} An error occurred wile creating category descendant information. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0323E: Error updating page tree entry: {0} An error occurred while updating category tree information. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0324E: Error retrieving page tree entry: {0} An error occurred while retrieving category tree information. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0325E: Error retrieving page position: {0} An error occurred while retrieving a category position. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0326E: Error retrieving a forum or set of forums: {0} An error occurred retrieving a reply or a set of replies. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0327E: Error retrieving page: {0} An error occurred retrieving a category. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0328E: Error unlocking a node: {0} An error occurred while unlocking a forum or topic. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0329E: Error retrieving page ancestor: {0} An error occurred while retrieving a category ancestor. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0330E: Illegal move of category {0} to parent {1}. A category cannot be made a child of the specified parent. Typical causes include:

    1. A category cannot be made a child of a descendant category.

    2. Cannot move special categories, such as the root category and the category that contains community forums.
    No action is required.
    CLFRV0332E: Error retrieving page descendant count: {0} An error occurred while retrieving a category's child count. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0333E: Invalid entry {0} in configuration file {1}. Check the configuration file."}) An invalid entry was detected in a configuration file. Check the specified configuration file.
    CLFRV0334E: Error updating node state: {0} An error occurred while updating a node's state. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0335E: Error inserting flag content: {0} An error occurred while creating a flag record. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0346E: Error updating node question state: {0} An error occurred while updating a topic's question state. This error is usually caused by a database problem. Check for SQL exceptions in the SystemOut.log file and fix according to the error message.
    CLFRV0357E: Seedlist state is not the correct state for this operation. Forums seedlist error. When retrieving an updated forum document, an invalid ACL change state was passed for seedlist logging. Only topics and forums ACL change states are valid.
    CLFRV0358W: Problem creating a forum document to represent the forum with id {0}. Forums seedlist error. When getting all forums, an invalid forum document was found. This can happen when there a BaseNode Object retrieved from the Forum API missing mandatory attributes that are needed for a seedlist entry, such as an ID/Link/Title. The entry is skipped. If this happens regularly, contact Customer Support.
    CLFRV0359E: Problem retrieving replies for the topic with id {0}. This message is displayed if an error occurs when retrieving the seedlist. This problem is usually caused by an internal forum service. Check any exceptions from the SystemOut.log file and fix them according to the error message.
    CLFRV0360W: There is a null value in the NodeCollection. This is a warning message that occurs when retrieving the seedlist. This error only occurs if the Forums API returns a null value in a NodeCollection. If this happens regularly, contact Customer Support.
    CLFRV0361W: The last modified date is not available for the Topic with this ID {0}. Forums seedlist error. When processing topic ACL updates, the current topic being processed does not have the last modified date. If this happens regularly, contact Customer Support.
    CLFRV0362E: Problem retrieving the configuration details for the Forums feature. Forums seedlist error. A problem occurred when retrieving the Forums component. Verify that the Lotus-Connections-config.xml file is valid. There should be other errors in the log if that is the case.
    CLFRV0363W: Problem creating a forum document to represent the forum topic with id {0}. Forums seedlist error. A problem occurred when creating a forum document for the topic with the specified ID. This can happen when there a BaseNode Object (used to represent forums or topics) retrieved from the Forum API missing mandatory attributes that are needed for a seedlist entry, such as an ID/Link/Title. The entry is skipped. If this happens regularly, contact Customer Support.
    CLFRV0364W: Problem constructing URI for Topic with the following Topic Id {0}. A problem occurred constructing the link URI for the seedlist entry corresponding to the topic with the specified ID. Verify the values of the sloc:href element in LotusConnections-config.xml for the Forums sloc:serviceReference element. For more information, see Common configuration properties.
    CLFRV0366W: Problem retrieving forum documents to represent forum categories. Forums seedlist error. A problem occurred when retrieving forum documents for forum categories. This can happen when there a Page Object (used to represent categories) retrieved from the Forum API missing mandatory attributes that are needed for a seedlist entry, such as an ID/Link/Title. The entry is skipped. If this happens regularly, contact Customer Support.
    CLFRV0367W: The last modified date is not available for the Forum with this ID {0}. Forums seedlist error. When processing topic ACL updates, the current forum being processed does not have the last modified date. If this happens regularly, contact Customer Support.
    CLFRV0368I: Skipping including this forum with id {0} in the crawling phase for ACL updates as it will have been included in an earlier phase. The visibility of the forum was updated since the last crawl, however, the record for the forum was also updated in a manner that means that a seedlist entry representing the update in the forum was included in an earlier phase of the current crawl. Informational only; no action is required.
    CLFRV0369W: Exception thrown when converting a forum ,topic, or page node. Forums seedlist error. A problem occurred when converting a forum, topic, or page node. If this happens regularly, contact Customer Support.
    CLFRV0373W:Problem constructing URI for Category with the following Category Id {0}. A problem occurred while constructing the link URI for the seedlist entry corresponding to the category with the specified ID. Verify the values of the sloc:href element in LotusConnections-config.xml for the Forums sloc:serviceReference element. See Common configuration properties for more information.
    CLFRV0374W: The retrieved nodes from the Forums API are missing either a valid ID,title or link. The values for id,link and title are as follows {0},{1},{2} Forums seedlist error. A problem occurred when converting nodes to forum documents, invalid ID, title, or link is found. If this happens regularly, contact Customer Support.
    CLFRV0375I: Skipping including this topic with id {0} in the crawling phase for ACL updates as it will have been included in an earlier phase. This message is informational. Informational only; no action is required.
    CLFRV0376E: Problem retrieving tags for the topic with id {0}. Forums Seedlist error. A problem occurred when retrieving tags for the topic with the specified ID.

    This error is ogged if there a problem calling the Forums API. This root cause is ForumsException, which will also be logged.

    Check the logs to determine the root cause and take appropriate action. For example, if it is a database connection issue, verify the connection to the Forums database.
    CLFRV0377E: Cannot move topic from a forum in community {0} to a forum in community {1}. Topics in community forums can only be moved to forums in the same community. Cannot move forums between communities. Informational only; no action is required.
    CLFRV0378E: Cannot create a non-community forum in the community forum category. Cannot move forums between communities. Informational only; no action is required.
    CLFRV0379E: Error updating the category count for category {0} An error occurred updating a category's child count. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0380E: Error deleting counts by category {0} An error occurred while deleting counters (for example, number of children, number of forums) for a page. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0381E: Error deleting counts by forum {0} An error occurred while deleting counters (for example, number of topics, number of posts) for a forum. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0382E: Cannot unlock topic {0}, forum {1} is locked A topic cannot be unlocked because the containing forum is locked. Informational only; no action is required.
    CLFRV0383E: Error deleting counts by topic {0} An error occurred while deleting counters (for example, number of posts) for a topic. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0384I: Received user lifecycle update on internalId: {0} A generic error occurred while running the synchronization command *byMemberId. Use the server logs to identify why the command failed to run.
    CLFRV0386E: Error on user lifecycle getByInternalId of: {0} A generic error occurred while running the synchronization command *byMemberId. Use the server logs to identify why the command failed to run.
    CLFRV0387E: Error on user lifecycle getByEmail A generic error occurred while running the synchronization command *byEmail. Use the server logs to identify why the command failed to run.
    CLFRV0388E: Error on user lifecycle getByLogin of: {0} A generic error occurred while running the synchronization command *byLogin. Use the server logs to identify why the command failed to run.
    CLFRV0389E: An unexpected error occurred while processing command {0}: {1} A generic error occurred while running the specified command. Investigate the server logs to identify more detailed causes of the error.
    CLFRV0390E: Error on user lifecycle update of internalId: {0} Informational message about receiving a user life-cycle event to update all users. Informational only; no action is required.
    CLFRV0391I: Received user lifecycle request to update all users Informational message about receiving a user life-cycle event to update all users. Informational only; no action is required.
    CLFRV0392E: Unknown command: {0} The specified command was not recognized. Check that the command name is typed correctly.
    CLFRV0393E: The command can not be processed because another user has this key value: {0} The command could not execute because another user had the specified key value. Check that the specified key is valid and that you are not trying to duplicate key entries in the database.
    CLFRV0394E: Error on user lifecycle getByExternalId of: {0} A generic error occurred while running the synchronization command *byExtId. Use the server logs to identify why the command failed to run.
    CLFRV0395E: The user with id {0} could not be found. The user with the specified ID was not found in Forums. Check that the ID is valid and that Forums has actually used this user before.
    CLFRV0396E: Invalid AclEntry: {0} Encountered an invalid ACLEntry during creation. For example, a non-community role was assigned to a community forum, or vice versa. Informational only; no action is required.
    CLFRV0397I: Done initializing Discussion Forums UserLifecycle SPI. Informational message stating that the user life-cycle SPI engine started correctly. Informational only; no action is required.
    CLFRV0398I: Initializing Discussion Forums UserLifecycle SPI. Informational message \stating that the user life-cycle SPI engine is starting. Informational only; no action is required.
    CLFRV0399E: Error initializing Discussion Forums UserLifecycle SPI. Generic error initializing the user life-cycle SPI engine. Use the server logs to identify why the SPI engine failed to start.
    CLFRV0400E: Forums mismatch for forum-policy.xml. Current version: {0} Required version: {1}. Make sure you are not trying to use an old config file on a newer server or vice-versa. The version number in forum-policy.xml does not match the version required by the enterprise application. This error indicates that the Forums .ear file was not updated in conjunction with the configuration files.
    CLFRV0401E: Community category cannot have children categories. The category that holds community forums cannot have sub-categories. Informational only; no action is required.
    CLFRV0402E: Illegal attempt to move a forum {0}: community:{1} category: {2} to community: {3} category:{4} The specified forum could not be moved. Informational only; no action is required.
    CLFRV0403W: Problem constructing URI for Forum with the following Forum Id {0}. A problem occurred constructing the link URI for the seedlist entry corresponding to the forum with the specified ID. Verify the values of the sloc:href element in LotusConnections-config.xml for the Forums sloc:serviceReference element. See Common configuration properties for more information.
    CLFRV0416E: Import error: Topic UUID={0} A problem occurred while importing a topic in to the database. Check any exceptions in the SystemOut.log file and fix them according to the error message. Check the forum, topic, and reply's dependency and verify the data.
    CLFRV0421I: *********** Finished import for Reply UUID={0} Informational message that displays when importing a reply. Informational only; no action is required.
    CLFRV0423E: The version of the archive you tried to import does not match the current DB schema. The import file database schema version does not match the database schema. Check the database schema version in the Category_Forum.xml file.
    CLFRV0425E: Import error: Reply UUID={0} A problem occurred when importing the reply to the database. Check the forum, topic, and reply's dependency, and verify the data.
    CLFRV0427W: 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. A problem occurred while synchronizing the member profile with the LDAP directory. Make sure that the member information defined in the Category_Forum.xml file exists in the LDAP directory and the database.
    CLFRV0430I: The archive "{0}" does not exist in the file system. Nothing will be done. A problem occurred while unpacking the import's data. Make sure that the .zip file is in the specified system path.
    CLFRV0431E: The ArchiveService cannot create the directory={0} for exporting forums. A problem occurred when the directory could not be created. Verify the file path of the export.
    CLFRV0434E: Error unpacking the archive A problem occurred while unpacking the import's data. Check the import .zip file.
    CLFRV0435E: The ArchiveService cannot export forums to the directory={0} as it is not writable. A problem occurred and the directory cannot be written to. Verify the file path of the export and check that the directory can be written to.
    CLFRV0437E: Import error: Forum UUID={0} A problem occurred while importing the forum to the database. Check the forum, topic, and reply's dependency, and verify the data.
    CLFRV0438E: The ArchiveService cannot export forums to the directory={0} as it is not a directory. A problem occurred and the Forums directory could not be created. Verify the file path of the exported forums.
    CLFRV0440E: Error setting community page: {0} A problem occurred when the category could not be set to the community category. This error is usually caused by a database problem. Check any SQL exceptions in the SystemOut.log file and fix them according to the error message.
    CLFRV0441E: Error retrieving page forum count: {0} A problem occurred when counting the forums of the category. This error is usually caused by a database problem. Check any SQL exceptions in the SystemOut.log file and fix them according to the error message.
    CLFRV0442I: Forums policy-config.xml version: {0} This information records what version of the forums-policy.xml file is being used. Informational only; no action is required.
    CLFRV0443I: Terminating Discussion Forums Following service. Informational message. The following service for Forums is shutting down. Informational only; no action is required.
    CLFRV0444I: Initializing Discussion Forums Following service. Informational message. The following service for Forums is initializing. Informational only; no action is required.
    CLFRV0445I: Discussion Forums Following service initialized. Informational message. The following service for Forums has successfully initialized. Informational only; no action is required.
    CLFRV0446E: Discussion Forums Following service failed to initialize. The following service for Forums failed to initialize. This might indicate a configuration problem. See the SystemOut.log file for additional details.
    CLFRV0459E: Error getting attachments total size: {0} A problem occurred when getting the size of all the attachments. This error is usually caused by a database problem. Check any SQL exceptions in the SystemOut.log file and fix them according to the error message.
    CLFRV0460E: Error getting attachments total number: {0} A problem occurred when getting the number of all the attachments. This error is usually caused by a database problem. Check any SQL exceptions in the SystemOut.log file and fix them according to the error message.
    CLFRV0461E: Error fetching topics A problem occurred when fetching the topics by date. Verify the format of the date.
    CLFRV0462E: Could not write to "{0}"; The directory or given path is not writable A problem occurred when the directory could not be written to. Verify the file path of the export and whether the directory has write permissions.
    CLFRV0465E: Error member id do not specified A problem occurred when updating member by memberID. Make sure that the member ID is not null.
    CLFRV0467E: Error creating directory "{0}" A problem occurred when the directory could not be created. Verify the file path of the export and make sure that you have create permissions on the specified path.
    CLFRV0468E: Error get member profile A problem occurred when getting the member by member name. This problem is usually caused by a database problem. Check any SQL exceptions in the SystemOut.log file and fix them according to the error message.
    CLFRV0471E: Cannot re-parent reply node {0}. A reply cannot be re-parented. Ensure that calling code is not selecting replies for re-parent operations.
    CLFRV0472E: Followed resources for user "{0}" could not be retrieved. An attempt to retrieve a followed resource failed. This resource does not exist in Forums. Check the input parameters to the service request. See the SystemOut.log file for additional details.
    CLFRV0474I: Total time elapsed: {0} hours {1} minutes {2} seconds \n Informational message that displays when the export or import is finished. Informational only; no action is required.
    CLFRV0475I: Import process started and will take some time to complete, please be patient as the total execution time depends on the entire data set that you selected to import, you can refer to log file for the importing detail. Informational message that displays when the import process starts. Informational only; no action is required.
    CLFRV0476I: Export process completed successfully, following are the statistics:\n Informational message that displays when the export finishes. Informational only; no action is required.
    CLFRV0477I: Total time elapsed: {0} milliseconds \n Informational message that displays when the export finishes. Informational only; no action is required.
    CLFRV0478I: Total Imported replies: {0} Informational message that displays when the export finishes. Informational only; no action is required.
    CLFRV0479I: Total exported replies : {0}\n Informational message that displays when the export finishes. Informational only; no action is required.
    CLFRV0480I: Total exported forums : {0}\n Informational message that displays when the export finishes. Informational only; no action is required.
    CLFRV0481E: Error exporting forum UUID={0} The Forums contain some data that is incorrect. Verify the attachments of the exported forums's xml file.
    CLFRV0482I: Total time elapsed: {0} Informational message that displays when the export or import finishes. Informational only; no action is required.
    CLFRV0483I: importing topic ({0}) to forum uuid={1} Informational message that displays when importing a topic in to a forum. Informational only; no action is required.
    CLFRV0484I: Total time elapsed: {0} seconds \n Informational message that displays when the export or import finishes. Informational only; no action is required.
    CLFRV0485I: Total exported topics : {0}\n Informational message that displays when the export or import finishes. Informational only; no action is required.
    CLFRV0486I: Total Imported attachments: {0} , total size: {1} Informational message that displays when the import finishes. Informational only; no action is required.
    CLFRV0487I: Import process completed, following are the statistics: Informational message that displays when the import finishes. Informational only; no action is required.
    CLFRV0488I: Total Imported forums: {0} Informational message that displays when the import finishes. Informational only; no action is required.
    CLFRV0489I: Exporting forum uuid={0} Informational message that displays when the export finishes. Informational only; no action is required.
    CLFRV0490E: The attachment of topic {0} does not exist\n The topic's attachments do not exist. Verify the attachments for the specified topic.
    CLFRV0491I: Total exported attachments : {0},total size: {1}\n Informational message that displays when the export finishes. Informational only; no action is required.
    CLFRV0492I: Total exported categories : {0}\n Informational message that displays when the export finishes. Informational only; no action is required.
    CLFRV0493E: Import error: Invalid for created or modified A problem occurred when importing a category, forum, topic, or reply. Check that the members in the Category_Forum.xml file match the database.
    CLFRV0494I: Total Imported categories: {0} Informational message that displays when the import finishes. Informational only; no action is required.
    CLFRV0495E: The attachment of reply {0} does not exist\n The attachments do not exist for the specified reply. Verify the attachments for the specified reply.
    CLFRV0496I: Total time elapsed: {0} minutes {1} seconds\n Informational message that displays when the export or import finishes. Informational only; no action is required.
    CLFRV0497I: importing forum uuid={0} Informational message that displays when importing a forum. Informational only; no action is required.
    CLFRV0498I: Total Imported topics: {0} Informational message that displays when the import finishes. Informational only; no action is required.
    CLFRV0499I: Exporting topic ({0}/{1}) from forum uuid={2} Informational message about exporting the forums. Informational only; no action is required.
    CLFRV0500I: The requested user profile {0} was not found in Forums. Nothing to be done. Informational message stating that the user life-cycle SPI engine is starting. Informational only; no action is required.
    CLFRV0502E: The path is a directory. Please specify a file path. The export file path does not exist. Verify the file path of the export.
    CLFRV0503I: Access Violation: CALLER[{0}]: OBJECT [{1}]: REQUESTED[{2}] on locked node. General access violation report. The requestor does not have sufficient privileges for the indicated action and object. If this error occurs during community forum creation, it is indicative of a Directory Services configuration problem as Forums cannot establish a user's membership in a community.
    CLFRV0504E: No container information for forum {0} Expected run time information for a forum cannot be located. Check the input node UUID and ensure that it identifies an existing topic.
    CLFRV0505E: Can not delete category "{0}" which still contain forums or sub-categories. This message is thrown when trying to delete category that is not empty. You cannot delete a category that is not empty. To delete the category, ensure that all the subcategories and forums are deleted first.
    CLFRV0506E: Error inserting reply An error occurred while creating a reply. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0507E: Exceeded maximum number of retries inserting reply An error occurred while creating a reply. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0508E: Error retrieving sub category count for container {0} This message is thrown if an error occurs when getting the category count number data from database. This issue is usually caused by a database problem. Check any SQL exceptions from the SystemOut.log file and fix them according to the error message.
    CLFRV0509E: No container information for topic {0} Expected run time information for a topic cannot be located. Check the input node UUID and ensure that it identifies an existing forum.
    CLFRV0510E: Cannot move topic from a public forum to a forum in community {0}. Topics in public forums can only be moved to other public forums. A topic cannot be moved from a public forum to a community forum Informational only; no action is required.
    CLFRV0511E: Error opening nodes This message is thrown if an error occurs when opening node data. Check any exceptions from the SystemOut.log file and fix them according to error prompt. Ensure that you have the permission to access that node data.
    CLFRV0512E: Unknown member type {0} This is an internal error that should not occur. Report this problem to Customer Support.
    CLFRV0513E: Requested tumbler value has exceeded maximum An error occurred while inserting a reply. This error will occur only if a topic has an extremely large number of replies. Performance issues will occur before this error is induced.
    CLFRV0514E: Error transferring forums to the specified community An error occurred while transferring community resources in response to the communities transferRemoteApplication command. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0515E: Cannot flag the same post multiple times A user cannot flag a post multiple times. Informational only; no action is required.
    CLFRV0516E: Error getting flag count for node {0} An error occurred while retrieving the flag count for a node. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0517E: Error retrieving tumbler information An error occurred while creating a reply. Additional information relating to the failure may be found in the SystemOut.log file.
    CLFRV0518E: Error retrieving container information Expected run time information for a forum cannot be located. Check the input node UUID and ensure that it identifies an existing topic.
    CLFRV0519E: Error purging thumbnail for content with reference uuid {0} This message is thrown if an error occurs when purging thumbnail data from the database. This issue is usually caused by a database problem. Check any SQL exceptions from the SystemOut.log file and fix them according to the error message.
    CLFRV0521E: Error updating thumbnail for content with reference uuid {0} This message is thrown if an error occurs when updating thumbnail data from the database. This issue is usually caused by a database problem. Check any SQL exceptions from the SystemOut.log file and fix them according to the error message.
    CLFRV0522E: Error getting thumbnail for content with reference uuid {0} This message is thrown if an error occurs when getting thumbnail data from the database. This issue is usually caused by a database problem. Check any SQL exceptions from the SystemOut.log file and fix them according to the error message.
    CLFRV0523E: Error retrieving forum overview Expected run time information for a forum cannot be located. Check the input node UUID and ensure that it identifies an existing topic.
    CLFRV0524E: Error inserting thumbnail for content with reference uuid {0} This message is thrown if an error occurs when getting thumbnail data from the database. This issue is usually caused by a database problem. Check any SQL exceptions from the SystemOut.log file and fix them according to the error message.
    CLFRV0525E: Node {0} had an invalid state change from {0} to {1} An illegal state change was attempted on the specified node. Informational only; no action is required.


    Files and Wikis error messages

    Use the codes included in the error messages generated by IBM Connections to identify problems with Files and Wikis.


    Files and Wikis error messages

    The following error messages are generated by IBM Connections:

    Table 13. Files and Wikis error messages

    Message Cause Solution
    EJPVJ9000E: An unknown error has occurred. Explanation: An unknown error occurred, and a more detailed error is not available. User Response: Please report this error to a system administrator and include any details available.
    EJPVJ9001E: Invalid media id: {0} Explanation: The provided media id is not valid. User Response: Supply a valid media id.
    EJPVJ9002E: Unable to get the media additional file with id {0}. Explanation: An error occurred while attempting to get the media additional file with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9003E: Unable to get media additional files for the media with id {0}. Explanation: An error occurred while attempting to get the media additional files for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9016E: Unable to get all libraries. Explanation: An error occurred while attempting to get all the libraries. This may be due to an underlying system error. User Response: Examine the nested exception and determine if action is needed, or if failure was expected due to a system error.
    EJPVJ9018E: Unable to update download count for media with id {0}. Explanation: An error occurred while attempting to update the download count for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9022E: Unable to get the media with id {0}. Explanation: An error occurred while attempting to get the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9027E: Unable to get the media for the library with id {0}. Explanation: An error occurred while attempting to get the media for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9029E: Unable to get media. Explanation: An error occurred while attempting to get the media. This may be due to an underlying system error. User Response: Examine the nested exception and determine if action is needed, or if failure was expected due to a system error.
    EJPVJ9037E: Unable to add media. Explanation: An error occurred while attempting to add the media. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9039E: Unable to edit the media with id {0}. Explanation: An error occurred while attempting to edit the media with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9040E: Unable to get the revisions for the media with id {0}. Explanation: An error occurred while attempting to get the revisions for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9055E: Unable to get one or more of the item(s) with id(s) {0}. Explanation: An error occurred while attempting to get the item(s) with the listed id(s). User Response: No action is required, unless the item is expected to exist, in which case the item may need to be located in a backup.
    EJPVJ9063W: Unable to get the user from the cache with id {0} Explanation: An error occurred while attempting to get the user from the cache with the specified id. A system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9067E: Unable to get the user with directory id {0}. Explanation: An error occurred while attempting to get the user with the specified directory id. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9070E: Unable to logon the user with the J2EE principal {0}. Explanation: An error occurred while attempting to logon the user with the specified J2EE principal. The user may not be in the directory, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the user is not in the directory, or a system error occurred).
    EJPVJ9076E: Unable to get the DynaCache with JNDI name {0}. Explanation: An error occurred while attempting to get the DynaCache instance with the specified JNDI name. It may not be bound, or may not be accessible in this context. User Response: Verify the specified DynaCache instance exists, or that the J2EE bindings are correctly specified.
    EJPVJ9077W: Unable to get information from cache for {0} user(s). Explanation: An error occurred while attempting to get users from the cache. The user(s) may not be valid, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the user(s) were not valid, or a system error occurred).
    EJPVJ9078W: Unable to get the user with id {0}. Explanation: An error occurred while attempting to get the user with the specified id. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9080W: Unable to get user(s) from cache, as the collection type {0} is not supported. Explanation: An internal error occurred while looking up users from the cache, as the collection type was not recognized. User Response: Report this error, as it is unexpected.
    EJPVJ9082W: Unable to get all users, {0} were not found. Explanation: An error occurred while attempting to get users from the cache. The items may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the items do not exist, or a system error occurred).
    EJPVJ9098E: Unable to read configuration from directory {0}. Explanation: The configuration directory specified is not readable by the application. User Response: Ensure that the configuration directory specified exists, and that the user the application server runs at has permission to it.
    EJPVJ9099I: Loading configuration from directory {0}. Explanation: The application configuration will be loaded from the directory specified. User Response: No action required, unless a different directory was expected.
    EJPVJ9100E: Unable to load required configuration branch {0}. Explanation: The specified configuration branch could not be found in the application configuration. User Response: Ensure that the correct configuration files are in the specified configuration directory.
    EJPVJ9102E: Unable to construct a connection factory Explanation: An error occurred while attempting to construct a database connection factory. User Response: Ensure that the database drivers needed by the specified dialect are on the classpath for the application server.
    EJPVJ9103E: Unable to request initial context with factory {0}. Explanation: An error occurred while requesting the J2EE initial context with the specified factory. User Response: Ensure that a supported application server is installed and correctly configured.
    EJPVJ9104E: Unable to initialize application platform. Explanation: An error occurred while initializing the platform that this application was built on. No services will be available. User Response: Examine the nested exception and determine the appropriate action. Often configuration is missing or incorrect, or the install was not properly completed.
    EJPVJ9106E: Unable to add comment. Explanation: An error occurred while attempting to add a comment. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9107E: Unable to edit the comment with id {0}. Explanation: An error occurred while attempting to edit the comment with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9109E: Unable to get the comment with id {0}. Explanation: An error occurred while attempting to get the comment with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9110E: Unable to get the comments for the item with id {0}. Explanation: An error occurred while attempting to get the comments for the item with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9112E: Unable to get the statistics. Explanation: An error occurred while attempting to get the statistics. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9113E: Unable to update statistics data. Explanation: An error occurred while attempting to update the statistics data. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expect (a system error occurred).
    EJPVJ9114E: Unable to get the statistics between {0} and {1}. Explanation: An error occurred while attempting to get the statistics between the specified start and end dates. The items may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (not accessible to the user, or a system error occurred).
    EJPVJ9115E: Unable to get the number of statistics records available. Explanation: An error occurred while attempting to get the number of statistics records available. The items may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (not accessible to the user, or a system error occurred).
    EJPVJ9123I: The task {0} has begun execution at {1}. Explanation: The task with the specified name has begun execution, and will complete momentarily. User Response: No action is required.
    EJPVJ9130W: Unable to start transaction, as it has already been started. Explanation: A transaction start was attempted, but cannot be completed as one is already active. User Response: Report this error, as this exception should not occur.
    EJPVJ9131W: Unable to rollback transaction. Explanation: A transaction was not able to be rolled back, as an underlying system error has occurred. User Response: Examine the nested exception and determine if action is needed.
    EJPVJ9144W: Unable to update profile status for user with directory id {0}. Explanation: An error occurred while attempting to update the user with the specified directory id. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9145E: Unable to get user information from directory to do user updates after {0} attempts. Further updates will be aborted. Explanation: Repeated errors occurred when querying the directory during the update user task. This is likely a connectivity or configuration issue, so further updates were aborted. User Response: Examine the nested exceptions and determine if action is needed, or if the failure was expected (a system error occurred). If this exception repeats, users may not be properly updated.
    EJPVJ9146E: Unable to run WorkItem. Explanation: An error occurred when attempting to run a work item, which was caused by an internal error. User Response: Report this error, as it should not occur.
    EJPVJ9148E: Unable to execute task {0}. Explanation: An error occurred while attempting to execute the specified task. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9150E: Unable to get additional file count for the media with id {0}. Explanation: An error occurred while attempting to get the additional file count for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9153E: Unable to delete the media with id {0}. Explanation: An error occurred while attempting to delete the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9154E: Unable to delete the comment with id {0}. Explanation: An error occurred while attempting to delete the comment with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9155E: Unable to perform the action {1} on item {2} as the user {0} does not have permission. Explanation: An error occurred while attempting to perform the specified action on the specified item as the specified user does not have permission. They might not have ever had permission, or the permission may have been removed. User Response: No action is required, unless the user should have permission.
    EJPVJ9157E: Unable to edit email options for the user with id {0}. Explanation: An error occurred while attempting to edit email options for the user with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9158E: Unable to edit the preferred page size for the user with id {0}. Explanation: An error occurred while attempting to edit the preferred page size for the user with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9159E: Unable to edit the preferred view size for the user with id {0}. Explanation: An error occurred while attempting to edit the preferred view for the user with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9160E: Unable to find the item with id {0}. Explanation: The item with the specified id could not be found. It may have never existed or have been deleted. User Response: No action is required.
    EJPVJ9161E: Unable to add, edit or delete additional files for the media with the id {0}. Explanation: An error occurred while attempting to add, edit, or delete additional files for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9163E: Unable to get library count. Explanation: An error occurred while attempting to get the library count. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9164E: Unable to add library. Explanation: An error occurred while attempting to add a library. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9165E: Unable to edit the library with id {0}. Explanation: An error occurred while attempting to edit the library with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9166E: Unable to delete the library with id {0}. Explanation: An error occurred while attempting to delete the library with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9169E: Unable to delete revisions older than {1} for the media with id {0}. Explanation: An error occurred while attempting to delete the revisions older than the specified number for the media with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9170E: Unable to get the media revision with the id {0}. Explanation: An error occurred while attempting to get media revision with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9178E: Unable to add a share for the media with id {0}. Explanation: An error occurred while attempting to add a share for the media with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9179E: Unable to delete all the shares for the media with id {0} to the user with id {1}. Explanation: An error occurred while attempting to delete all the shares for the media with the specified id for the specified user id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9180E: Unable to delete all the shares for the media with the id {0}. Explanation: An error occurred while attempting to delete all the shares for the media with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9181E: Unable to edit the permission to view for all the shares for the media with id {0} to the user {1}. Explanation: An error occurred while attempting to edit the permission to view for all the shared for the media with the specified id for the specified user id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9182E: Unable to get the users the media with id {0} was shared with. Explanation: An error occurred while attempting to get the users the media with the specified id was shared with. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9183E: Unable to get the share graph for the media with id {0}. Explanation: An error occurred while attempting to get the share graph for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9184E: Unable to get the share involvement for the media with id {0}. Explanation: An error occurred while attempting to get the share involvement for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9185E: Unable to get the media share with the group id {0}. Explanation: An error occurred while attempting to get the media share with the specified group id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9186E: Unable to get the media shared with this user. Explanation: An error occurred while attempting to get the media shared with this user. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9187E: Unable to get the count of media shared with this user. Explanation: An error occurred while attempting to get the count of media shared with this user. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9188E: Unable to get the media shared by this user. Explanation: An error occurred while attempting to get the media shared by this user. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9189E: Unable to get the count of media shared by this user. Explanation: An error occurred while attempting to get the count of media shared by this user. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9190E: Unable to add a media notification. Explanation: An error occurred while attempting to add a media notification. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9191E: Unable to process the request to the following interface, not enough details provided for source {0}, type {1}, user {2}. Explanation: An error occurred while attempting to follow an item. The item or user are not specified or can not be found, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9192E: An unexpected error occured for source {0}, id {1}, user {2}. Explanation: An unexpected error occurred while processing a following command. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9193E: Unable to delete the notification for this user and the media with id {0}. Explanation: An error occurred while attempting to delete the notification for this user and the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9196E: Unable to get the count of the notifications for the media with id {0}. Explanation: An error occurred while attempting to get the count of the notifications for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9197E: Unable to get the notifications for the media with id {0}. Explanation: An error occurred while attempting to get the notifications for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9198E: Unable to get existing tag entries by tag names. Explanation: An error occurred while attempting to get the existing tag entries by tag names. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure is expected (a system error occurred).
    EJPVJ9200E: Unable to add new tag entries. Explanation: An error occurred while attempting to add new tag entries. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure is expected (a system error occurred).
    EJPVJ9201E: Unable to get the tag ids to add for the item with id {0}. Explanation: An error occurred while attempting to get the tag ids to add for the item with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9202E: Unable to add tags for the item with id {0} and type {1}. Explanation: An error occurred while attempting to add tags for the item with the specified id and type. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9204E: Unable to delete the tags {0} for the item with id {1}. Explanation: An error occurred while attempting to delete the specified tags from the item with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9205E: Unable to get the media tags for the library with the id {0}. Explanation: An error occurred while attempting to get the media tags for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9206E: Unable to get the tags for the item with id {0}. Explanation: An error occurred while attempting to get the tags for the item with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9207E: Unable to add a policy. Explanation: An error occurred while attempting to add a policy. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9208E: Unable to edit the policy with id {0}. Explanation: An error occurred while attempting to edit the policy with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9209E: Unable to delete the policy with id {0}. Explanation: An error occurred while attempting to delete the policy with the specified id. The user may not have permission to perform this action, the policy may be a default policy or in use, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, the policy is a default policy or in use, or a system error occurred).
    EJPVJ9210E: Unable to get the policy with the id {0}. Explanation: An error occurred while attempting to get the policy with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9211E: Unable to get all policies. Explanation: An error occurred while attempting to get all the policies. The item may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item is not accessible to the user, or a system error occurred).
    EJPVJ9212E: Unable to add data to the library with id {0}. Explanation: An error occurred while attempting to add data to the library with the specified id. The maximum size of the policy in use may have been met, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the maximum size of the policy has been met, or a system error occurred).
    EJPVJ9214E: Unable to get the count of policies. Explanation: An error occurred while attempting to get the count of policies. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9220E: Unable to get the media with the label {0} in the library with id {1}. Explanation: An error occurred while attempting to get the media with the specified label in the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9221E: Unable to get the count for media in the library with the id {0}. Explanation: An error occurred while attempting to get the count for media in the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9222E: Unable to get the additional file with the label {0} for the media with id {1}. Explanation: An error occurred while attempting to get the additional file with the specified label for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9223E: Unable to add a recommendation for the item with id {0}. Explanation: An error occurred while attempting to add a recommendation for the item with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9224E: Unable to delete the recommendation with the id {0}. Explanation: An error occurred while attempting to delete the recommendation with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9225E: Unable to get the recommendations for the media with id {0}. Explanation: An error occurred while attempting to get the recommendations for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9226E: Unable to get the count for the recommendations for the media with id {0}. Explanation: An error occurred while attempting to get the count for the recommendations for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9227E: Unable to get the recommendations for the user with id {0} across the libraries with ids {1}. Explanation: An error occurred while attempting to get the recommendations for the user with the specified id within the specified set of library ids. The items may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the items were not accessible to the user, or a system error occurred).
    EJPVJ9229E: Unable to get the recommendation status for the user with the id {1} for the media with the id {0}. Explanation: An error occurred while attempting to get the recommendation status for the user with the specified id for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9230E: Unable to get the revision with the number {0} for the media with id {1}. Explanation: An error occurred while attempting to get the revision with the specified number for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9237E: Unable to get the notification for this user for the media with id {0}. Explanation: An error occurred while attempting to get the notification for this user for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9238E: Unable to send a notification of type {0} to the user(s) {1}. Explanation: An error occurred while attempting to send the notification of the specified type to the specified users. a system error may have occurred, possibly caused by a notification configuration error. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9240E: Unable to get the tags across the specified scope. Explanation: An error occurred while attempting to get the tags across the specified scope. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9242E: Unable to get the media tag count for the library with the id {0}. Explanation: An error occurred while attempting to get the media tag count for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9243E: Unable to get tag count for the specified scope. Explanation: An error occurred while attempting to get the tag count for the specified scope. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9244E: Unable to get the users with the ids {0}. Explanation: An error occurred while attempting to get the users with the specified ids. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9245E: Unable to publish the media draft with the id {0}. Explanation: An error occurred while attempting to publish the media draft with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9246E: Unable to query the directory service by field {0} for {1}. Explanation: An error occurred while attempting to query the directory service by the specified field for the specified value. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9257E: Unable to add a user with directory id {0}. Explanation: An error occurred while attempting to add a user with the specified directory id. A constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a constraint violation occurred, or a system error occurred).
    EJPVJ9258E: Unable to create, read, or write to the content storage directory {0}. Explanation: An error occurred while attempting to initialize the content storage directory. If located, it could not be read from or written to, or if not present it could not be created. User Response: Examine the nested exception and ensure the storage directory specified in the configuration file is correct. Ensure that the user the application server runs as has full permissions on the directory.
    EJPVJ9259I: The content storage directory was initialized successfully and is set to {0}. Explanation: The specified directory will be used as the root folder for binary data storage. At initialization time, the root directory was both readable and writable. User Response: No action is required.
    EJPVJ9260E: Unable to delete the expired search deletion history for Additional Files. Explanation: An error occurred while attempting to delete the expired search deletion history for Additional Files. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9261E: Unable to delete the expired search deletion history. Explanation: An error occurred while attempting to delete the expired search deletion history. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9262E: Unable to get access control information for media on the seedlist. Explanation: An error occurred while attempting to get the access control information for media on the seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9263E: Unable to get the media for the seedlist. Explanation: An error occurred while attempting to get the media for the seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9264E: Unable to get the updated media for the seedlist. Explanation: An error occurred while attempting to get the updated media for the seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9265E: Unable to get additional media data for the seedlist. Explanation: An error occurred while attempting to get additional media data for the seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9266E: Unable to set the user name and display link for the seedlist. Explanation: An error occurred while attempting to set the user name and display link for the seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9268E: Unable to get the range of available statistics. Explanation: An error occurred while attempting to get the range of available statistics. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9270E: Unable to get the tags for the media for the seedlist. Explanation: An error occurred while attempting to get the tags for the media for the seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9271E: Unable to get the users with the directory ids {0}. Explanation: An error occurred while attempting to get the users with the specified directory ids. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9272E: Unable to get the groups with the directory ids {0}. Explanation: An error occurred while attempting to get the groups with the specified directory ids. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9273E: Unable to get the group with the directory id {0}. Explanation: An error occurred while attempting to get the group with the specified directory id. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9275E: Unable to add a group with the directory id {0}. Explanation: An error occurred while attempting to add the group with the specified directory id. A constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a constraint violation occurred, or a system error occurred).
    EJPVJ9277E: Unable to get the expired groups to update for the update group task. Explanation: An error occurred while attempting to get the expired groups to update for the update group task. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred). If this error persists, group names may not be properly updated.
    EJPVJ9278I: Updating {0} group entries. Explanation: The update group task is about to update the names and state for the specified number of groups, which will make that many directory calls and database updates. User Response: No action is required.
    EJPVJ9281W: Unable to edit the group with the id {0} during the group update task. Explanation: An error occurred while attempting to edit the group with the specified id during the group update task. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9282E: Unable to get group information from directory to do group updates after {0} attempts. Further updates will be aborted. Explanation: Repeated errors occurred when querying the directory during the update group task. This is likely a connectivity or configuration issue, so further updates were aborted. User Response: Examine the nested exceptions and determine if action is needed, or if the failure was expected (a system error occurred). If this exception repeats, groups may not be properly updated.
    EJPVJ9284E: Unable to get the groups from the directory for the user with directory id {0}. Explanation: An error occurred while attempting to get the groups from the directory for the user with the specified directory id. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9285E: Unable to get the groups for the user with the id {0}. Explanation: An error occurred while attempting to get the groups for the user with the specified id. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9286E: Unable to synchronize the groups for the user with the id {0}. Explanation: An error occurred while attempting to synchronize the groups for the user with the specified id. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9288E: Unable to get the role assignments for the library with the id {0}. Explanation: An error occurred while attempting to get the role assignments for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9289E: Unable to assign a role for the library with id {0} to the user with the id {1}. Explanation: An error occurred while attempting to assign a role for the library with the specified id to the user with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9290E: Unable to assign a role for the library with id {0} to the group with the id {1}. Explanation: An error occurred while attempting to assign a role for the library with the specified id to the group with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9291E: Unable to assign roles for the library. Explanation: An error occurred while attempting to assign roles for the library. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9292E: Unable to delete the role for the library with id {0} to the user with the id {1}. Explanation: An error occurred while attempting to delete the role for the library with the specified id to the user with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9293E: Unable to delete the role for the library with id {0} to the group with the id {1}. Explanation: An error occurred while attempting to delete the role for the library with the specified id to the group with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9298E: Unable to get the library with the id {0}. Explanation: An error occurred while attempting to get the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9299E: Unable to get library with the label {0} and the type {1}. Explanation: An error occurred while attempting to get the library with the specified label and of the specified type. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9305E: Unable to get the drafts for the media with id {0} which the user with the id {1} can view. Explanation: An error occurred while attempting to get the drafts for the media with the specified id which the user with the specified id can view. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9306E: Unable to get the media drafts that the user with the id {0} can view. Explanation: An error occurred while attempting to get the drafts that the user with the specified id can view. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9307E: Unable to get the count of the drafts for the media with id {0} which the user with the id {1} can view. Explanation: An error occurred while attempting to get the count of the drafts for the media with the specified id which the user with the specified id can view. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9308E: Unable to get the count of the media drafts that the user with the id {0} can view. Explanation: An error occurred while attempting to get the count of the drafts that the user with the specified id can view. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9309E: Unable to get the total size of the additional file drafts. Explanation: An error occurred while attempting to get the total size of the additional file drafts. The items may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the items were removed, not accessible to the user, or a system error occurred).
    EJPVJ9310E: Unable to add a media draft. Explanation: An error occurred while attempting to add a media draft. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9311E: Unable to edit the media draft with the id {0}. Explanation: An error occurred while attempting to edit the media draft with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9312E: Unable to delete the media draft with the id {0}. Explanation: An error occurred while attempting to delete the media draft with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9313E: Unable to get the media drafts created by the user with the id {0} for the media with the id {1}. Explanation: An error occurred while attempting to get the media drafts created by the user with the specified id for the media with the specified id. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9314E: Unable to get the media draft with the id {0}. Explanation: An error occurred while attempting to get the media draft with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9315E: Unable to add the additional file drafts for the media draft with the id {0}. Explanation: An error occurred while attempting to add the additional file drafts for the media draft with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9316E: Unable to delete the additional file drafts for the media draft with the id {0}. Explanation: An error occurred while attempting to delete the additional file drafts for the media draft with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9317E: Unable to edit the additional file drafts for the media draft with the id {0}. Explanation: An error occurred while attempting to edit the additional file drafts for the media draft with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9318E: Unable to get the additional file draft with the id {0}. Explanation: An error occurred while attempting to get the additional file draft with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9319E: Unable to get the additional file draft with the label {0} for the media draft with the id {1}. Explanation: An error occurred while attempting to get the additional file draft with the specified label for the media draft with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9320E: Unable to get the additional file drafts for the media draft with the id {0}. Explanation: An error occurred while attempting to get the additional file drafts for the media draft with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9321E: Unable to get the additional file drafts for the media draft with the id {0}. Explanation: An error occurred while attempting to get the additional file drafts for the media draft with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9322E: Unable to get the permissions for the user with id {0} for the media draft with the id {1}. Explanation: An error occurred while attempting to get the permissions for the user with the specified id for the media draft with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9324E: Unable to get the Community with the directory id {0}. Explanation: An error occurred while attempting to get the community with the specified directory id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9325E: Unable to synchronize the Communities for the user with the id {0}. Explanation: An error occurred while attempting to synchronize the Communities for the user with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9326W: Unable to synchronize the Communities for the user with id {0} because the remote service was not available. Explanation: An error occurred while attempting to synchronize the Communities for the user with the specified id. The Communities service was not reachable. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the Communities server is being maintained).
    EJPVJ9327W: Unable to synchronize the groups for the user with id {0} because the remote service was not available. Explanation: An error occurred while attempting to synchronize the groups for the user with the specified id. The LDAP service was not reachable. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the LDAP server is being maintained).
    EJPVJ9340E: The required file identified by id {0} (referenced in table {1} column {2}) was not found at {3}. Explanation: A file referenced in the database by the specified id (from the specified table and column) was not found at the specified location. This error will occur when a referenced file is missing from the file system. User Response: Restore previous back-ups to locate the file, or remove the referencing item.
    EJPVJ9341E: The data integrity check failed and the database and file system are not consistent. {0} required files were not found or differ in expected size. Explanation: The data integrity check could not be completed as files were missing or differ in expected size. User Response: Restore previous back-ups to locate the file, or remove the referencing item.
    EJPVJ9342I: An unused file was found at {0}. It will be moved to {1}. Explanation: The specified file was not referenced in the database and can be removed. User Response: No action is required, but you may want to keep the unused files for future restoration.
    EJPVJ9343I: The data integrity check succeeded and the database and file system are consistent. {0} unused file(s) were moved to {1}. Explanation: The data integrity check completed successfully, potentially with unused files moved out of the content directory. User Response: No action is required, but you may want to keep the unused files for future restoration.
    EJPVJ9344E: The data integrity check failed and the database and file system are not consistent. Explanation: An error occurred while attempting to complete the data integrity check. a system error may have occurred. User Response: Examine the nested exception and determine what action is needed.
    EJPVJ9345W: An unused file was found at {0} but this is not a valid file path for data. Explanation: The specified file was found in the data directory, but does not correspond to the format used by the application to store data on disk. User Response: Examine the file and ensure that no other applications are writing to the content directory.
    EJPVJ9346E: Unable to assign the policy with the id {0} to the library with the id {1}. Explanation: An error occurred while attempting to assign the policy with the specified id to the library with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9347E: The metric key {0} is not valid. Explanation: The specified metric key is not recognized by the system. User Response: Refer to the administration guide for a list of valid metric keys.
    EJPVJ9348E: Unable to fetch the metrics of type {0} for keys {1} for the dates between {2} and {3}. Explanation: An error occurred while attempting to get the metrics for the specified keys between the specified dates. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9349E: Unable to list the date range of available metrics for the type {0}. Explanation: An error occurred while attempting to list the date range of available metrics for the specified type. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9350E: Unable to get the personal library for the user which the id {0}. Explanation: An error occurred while attempting to get the personal library for the user with the specified id. An internal system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9351E: Unable to get the file path for the file id {0}. Explanation: An error occurred while attempting to get the file path for the file with the specified id. An internal system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9352E: Unable to export the object with ID {0} to the file named {1}. Explanation: An error occurred while attempting to export the specified object type to the specified file. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9353E: Unable to parse the object type import file named {0}. Explanation: An error was encountered while parsing the specified object type import file. User Response: Correct the XML in the specified import file and retry the operation.
    EJPVJ9354E: Element {0} is missing the required attribute {1}. Explanation: The specified element is missing a required attribute. User Response: Correct the XML in the specified import file and retry the operation.
    EJPVJ9355E: Property type specified ({0}) does not match the type specified in the property definition element. Explanation: The type specified in the property definition element does not match the type specified in the nested type element. User Response: Correct the XML in the specified import file and retry the operation.
    EJPVJ9356E: The nesting for element {0} is invalid. Explanation: The specified element is not nested inside the expected element. User Response: Correct the XML in the specified import file and retry the operation.
    EJPVJ9357E: The attribute {0} is invalid for the property type {1}. Explanation: The specified attribute is not valid for the specified property type. User Response: Correct the XML in the specified import file and retry the operation.
    EJPVJ9358E: The value "{0}" is invalid or unsupported for element {1}. Explanation: An invalid or unsupported value was provided for the specified element. User Response: Correct the XML in the specified import file and retry the operation.
    EJPVJ9359E: Unable to import the object type from the file named {0}. Explanation: An error occurred while attempting to import an object type from the specified file. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9360E: Unable to get the collection with the external container id {0} and type {1}. Explanation: An error occurred while attempting to get the collection with the specified external container id and type. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9362I: Unable to delete the library with id {0} because it does not exist. Explanation: Unable to delete the library with the specified id because it does not exist. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (deleted library does not exist).
    EJPVJ9363W: Unable to delete the library with id {0}. Explanation: An error occurred while attempting to delete the library with the specified id. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9365E: Unable to retrieve search results from Search EJB Explanation: An error occurred while attempting to retrieve search results from Search EJB. a system error may have occurred. User Response: Ensure that the Search EJB is properly installed, the node where Search is installed is accessible on the newtork and the WebSphere naming service is running.
    EJPVJ9366I: The task {0} has finished at {1}. Explanation: The task with the specified name has finished executing at the specified time. User Response: No action is required.
    EJPVJ9367E: Unable to associate the login id {0} to the user id {1}. Explanation: The login id is already in use by another user, so it cannot be assigned to the specified user. User Response: Check the directory configuration and ensure that two users are not assigned to the same login id. You may need to run the user synchronization commands to fix the problem, or remove problem login ids on inactivate users.
    EJPVJ9368E: Unable to add a collection notification. Explanation: An error occurred while attempting to add a collection notification. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9369E: Unable to delete the notification for this user and the collection with id {0}. Explanation: An error occurred while attempting to delete the notification for this user and the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9370E: Unable to get the count of the notifications for the collection with id {0}. Explanation: An error occurred while attempting to get the count of the notifications for the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9371E: Unable to get the notifications for the collection with id {0}. Explanation: An error occurred while attempting to get the notifications for the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9372E: Unable to get the notification for this user for the collection with id {0}. Explanation: An error occurred while attempting to get the notification for this user for the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9373E: Unable to get the users to be notified for the collection with the id {0}. Explanation: An error occurred while attempting to get the users to be notified for the collection with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9374E: Unable to handle event of type {0} Explanation: An internal error occurred while attempting to handle the specified event. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9375W: Unable to get information about service. Explanation: An error occurred while attempting to get the configuration information for Connections Component. User Response: Examine the Connections component configuration files.
    EJPVJ9376E: Unable to remove the media with id {0}. Explanation: An error occurred while attempting to remove the media with the specified id. The item may no longer exist or be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed or is not accessible to the user, or a system error occurred).
    EJPVJ9377E: Unable to get the removed media with id {0}. Explanation: An error occurred while attempting to get the removed media with the specified id. The item may no longer exist or be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed or is not accessible to the user, or a system error occurred).
    EJPVJ9378E: Unable to delete the removed media with id {0}. Explanation: An error occurred while attempting to delete the removed media with the specified id. The item may no longer exist or be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed or is not accessible to the user, or a system error occurred).
    EJPVJ9379E: Unable to restore the removed media with id {0}. Explanation: An error occurred while attempting to restore the removed media with the specified id. The item may no longer exist or be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed or is not accessible to the user, or a system error occurred).
    EJPVJ9380W: Unable to remove user with id {0} from cache. Explanation: An error occurred while attempting to remove the user with the specified id from the user cache. This may cause inaccurate user data to be displayed. User Response: Examine the nested exception and determine if action is needed to correct the DynaCache configuration for user information.
    EJPVJ9382E: Unable to get the user with the email {0}. Explanation: An error occurred while attempting to get the user with the specified email. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9383E: Unable to get JTA user trasaction with JNDI name {0}. Explanation: An error occurred while attempting to look-up the JTA user transaction from the JNDI context. User Response: Ensure that these resources exist and are bound correctly.
    EJPVJ9384E: Unable to get Websphere extended JTA transaction with JNDI name {0}. Explanation: An error occurred while attempting to look-up the Websphere extended JTA transaction from the JNDI context. User Response: Ensure that these resources exist and are bound correctly.
    EJPVJ9385E: Unable to get Websphere unit of work manager with JNDI name {0}. Explanation: An error occurred while attempting to look-up the Websphere unit of work manager from the JNDI context. User Response: Ensure that these resources exist and are bound correctly.
    EJPVJ9386E: Unable to get timer manager with JNDI name {0}. Explanation: An error occurred while attempting to look-up the timer manager from the JNDI context. User Response: Ensure that these resources exist and are bound correctly.
    EJPVJ9387E: Unable to get work manager with JNDI name {0}. Explanation: An error occurred while attempting to look-up the work manager from the JNDI context. User Response: Ensure that these resources exist and are bound correctly.
    EJPVJ9388E: Unable to get media count. Explanation: An error occurred while attempting to get the media count for specified user. This may be due to an underlying system error. User Response: Examine the nested exception and determine if action is needed, or if failure was expected due to a system error.
    EJPVJ9389E: Unable to browse media. Explanation: An error occurred while attempting to browse media for specified user. This may be due to an underlying system error. User Response: Examine the nested exception and determine if action is needed, or if failure was expected due to a system error.
    EJPVJ9390E: Unable to get default sender of type {0}. Explanation: An error occurred while attempting to get sender of specified type.This may be caused by incorrect configuration in notification config file. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (incorrect configuration, or a system error occurred).
    EJPVJ9391W: Unable to remove library with id or label {0} from cache. Explanation: An error occurred while attempting to remove library with specified id or label from cache.This may cause the library information cannot be updated in cache. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the library was removed, or a system error occurred).
    EJPVJ9392E: Unable to transfer media with id {0} to the library with id {1}. Explanation: An error occurred while attempting to transfer the specified media to the specified library. The item may no longer exist or not be accessible to the user, the transfer may not be valid (quota exceeded or other constraint violated), or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, constraint violated, or a system error occurred).
    EJPVJ9393E: Unable to set media lock on media with id {0}. Explanation: An error occurred while attempting to set the lock type of the specified media. The item may no longer exist or be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed or is not accessible to the user, or a system error occurred).
    EJPVJ9394E: Unable to initialize the file manager. Explanation: An error occurred while attempting to initialize the file manager. A mis-configuration or internal error prevented this initialization, and the exploiting component will not be functional. User Response: Examine the nested exception and fix the configuration issue or report the internal error.
    EJPVJ9395E: Unable to get the trashed media for the library with id {0}. Explanation: An error occurred while attempting to get the trashed media for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9396E: Unable to get the count for the trashed media in the library with the id {0}. Explanation: An error occurred while attempting to get the count for the trashed media in the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9397E: Unable to delete all the trashed media in the library with the id {0}. Explanation: An error occurred while attempting to delete all the trashed media in the library with the specified id. The item may no longer exist or be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed or is not accessible to the user, or a system error occurred).
    EJPVJ9398E: Unable to create an event {0} of type {1}. Explanation: An error occurred while attempting to create an event. User Response: Examine the nested exception and determine if action is needed.
    EJPVJ9399E: Unable to send an event {0} of type {1}. Explanation: An error occurred while attempting to send an event of the specified type. User Response: Examine the nested exception and determine if action is needed. An internal error may have occurred, or configuration changes may be needed.
    EJPVJ9400E: Unable to add the collection with the id {0} to user favorites. Explanation: An error occurred while attempting to add a collection to the favorites of the specified user. The user may not have permission to store any preferences, the item may not be visible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, the item was not visible, or a system error occurred).
    EJPVJ9401E: Unable to delete the collection with the id {0} from user favorites. Explanation: An error occurred while attempting to delete the specified collection from user favorites. The user may not have permission to perform this action, the item may not exist anymore, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, the item did not exist, or a system error occurred).
    EJPVJ9402E: Unable to initialize scheduler EJB. Explanation: An error occurred while attempting to initialize the scheduler EJB. The scheduler may not be properly installed or configured. User Response: Please ensure that the JNDI binding is properly specified in the WebSphere administration console and that it is properly configured.
    EJPVJ9404E: Unable to move the collection with the id {0} in user favorites. Explanation: An error occurred while attempting to move the specified collection in user favorites. The user may not have permission to perform this action, the item may not exist anymore, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, the item did not exist, or a system error occurred).
    EJPVJ9405E: Unable to delete the media revisions with the id {0}. Explanation: An error occurred while attempting to delete the media revision with the the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9406E: Unable to add the media with the id {0} to user favorites. Explanation: An error occurred while attempting to add a media to the favorites of the specified user. The user may not have permission to store any preferences, the item may not be visible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, the item was not visible, or a system error occurred).
    EJPVJ9407E: Unable to delete the media with the id {0} from user favorites. Explanation: An error occurred while attempting to delete the specified media from user favorites. The user may not have permission to perform this action, the item may not exist anymore, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, the item did not exist, or a system error occurred).
    EJPVJ9408E: Unable to get favorite media ids. Explanation: An error occurred while attempting to get favorite media ids. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9409E: Unable to get favorite media. Explanation: An error occurred while attempting to get favorite media. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9410E: Unable to get the count for favorite media. Explanation: An error occurred while attempting to get the count for favorite media. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9411E: Unable to get share with community ids for media for the seedlist. Explanation: An error occurred while attempting to get share with community ids for media for the seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9412E: Unable to get favorite collection ids. Explanation: An error occurred while attempting to get favorite collection ids. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9413E: Unable to edit the preferred columns for the user with id {0}. Explanation: An error occurred while attempting to edit the preferred columns for the user with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9414E: Unable to synchronize community shares. Explanation: An error occurred while synchronizing community shares. A system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9416E: Unable to synchronize all community shares, as remote error limit of {0} was exceeded. Explanation: Repeated errors occurred while synchronizing community shares. This is likely a connectivity or configuration issue, so further actions were aborted. User Response: Examine the nested exceptions and determine if action is needed, or if the failure was expected (a system error occurred). Synchronization must complete without this error before the system is consistent.
    EJPVJ9417I: The community {0} no longer exists, so the corresponding collection {1} and all the associated shared files have been deleted. Explanation: During community share synchronization, the specified community was no longer found so all of the underlying sharing associations were removed by deleting the specified collection. User Response: No action is required.
    EJPVJ9418E: The collection {0} has been synchronized to community {1} which now has visibility {2} and name {3}. Explanation: During community share synchronization, the specified collection was out of synch with the specified community so it was updated. User Response: No action is required.
    EJPVJ9421E: Unable to add a library notification. Explanation: An error occurred while attempting to add a library notification. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9422E: Unable to delete the notification for this user and the library with id {0}. Explanation: An error occurred while attempting to delete the notification for this user and the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9423E: Unable to get the count of the notifications for the library with id {0}. Explanation: An error occurred while attempting to get the count of the notifications for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9424E: Unable to get the notifications for the library with id {0}. Explanation: An error occurred while attempting to get the notifications for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9425E: Unable to get the notification for this user for the library with id {0}. Explanation: An error occurred while attempting to get the notification for this user for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9426E: Unable to get the users to be notified for the library with the id {0}. Explanation: An error occurred while attempting to get the users to be notified for the library with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9428E: Unable to get or create the collection of type {0} with external container id {1}. Explanation: An error occurred while attempting to get or create the collection of the specified type with the specified external container id. The external container may no longer exist or be available, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed or is unavilable, or a system error occurred).
    EJPVJ9429E: Unable to get the person with the email {0} via user life cycle. Explanation: An error occurred while attempting to get the person with the specified email via user life cycle. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9430E: Unable to get the person with the external id {0} via user life cycle. Explanation: An error occurred while attempting to get the person with the specified external id via user life cycle. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9431E: Unable to get the person with the internal id {0} via user life cycle. Explanation: An error occurred while attempting to get the person with the specified internal id via user life cycle. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9432E: Unable to get the person with the login {0} via user life cycle. Explanation: An error occurred while attempting to get the person with the specified login via user life cycle. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9433E: Unable to update the person with the internal id {0} via user life cycle. Explanation: An error occurred while attempting to update the person with the specified internal id via user life cycle. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9434E: Unable to update all users via user life cycle. Explanation: An error occurred while attempting to update all users via user life cycle. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected.
    EJPVJ9435E: Unable to get the user with the login {0}. Explanation: An error occurred while attempting to get the user with the specified login. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9436E: Unable to get full user information. Explanation: An error occurred while attempting to get full user information. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected.
    EJPVJ9437E: Unable to edit user with id {0}. Explanation: An error occurred while attempting to edit user with the specified id. The user may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the user was removed, or a system error occurred).
    EJPVJ9438E: Unable to get the login ids of the user with id {0}. Explanation: An error occurred while attempting to get the login ids of the user with the specified id. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9439E: Unable to set the state of the comment with id {0}. Explanation: An error occurred while attempting to set the state of the comment with the specified id. The item may no longer exist, a constraint violation may have occured, the user may not have moderation permission, moderation may not be supproted or enabled on this library type, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, a constraint violation occurred, the user is not a moderator, moderation is not supported or enabled on this library type, or a system error occurred).
    EJPVJ9440E: Unable to get the comments in moderation state {0}. Explanation: An error occurred while attempting to get the comments of the specified moderation state. This action may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the action was not accessible to the user, or a system error occurred).
    EJPVJ9441E: Unable to copy the media with id {0} to the library with id {1}. Explanation: An error occurred while attempting to copy the media with the specified id to the library with the specified id. The item may no longer exist or not be accessible to the user, a constraint violation may have occurred, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, a constraint was in violation, or a system error occurred)
    EJPVJ9442E: Unable to add flag of type {0}. Explanation: An error occurred while attempting to add a flag of the specified type. The user may not have permission to perform this action, a constraint violation may have occurred, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint was in violation, or a system error occurred).
    EJPVJ9443E: Unable to resolve all the flags of type {0} for the item with id {1}. Explanation: An error occurred while attempting to resolve all the flags with the specified type for the item with the specified type id. The user may not have permission to perform this action, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, or a system error occurred)
    EJPVJ9444E: Unable to get the flag of type {0} with the id {1}. Explanation: An error occurred while attempting to get the flag with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9445E: Unable to get the flags of type {0} for the item with id {1}. Explanation: An error occurred while attempting to get the flags with the specified type for the item with the specified id. The user may not have permission to perform this action, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, or a system error occurred).
    EJPVJ9446E: Unable to get the flag count of type {0} for the item with id {1}. Explanation: An error occurred while attempting to get the count of the flags with the specified type for the item with the specified id. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9447E: Unable to get the flagged media comments. Explanation: An error occurred while attempting to get the flagged media comments. The item may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was not accessible to the user, or a system error occurred).
    EJPVJ9448E: Unable to get the count of the flagged items of type {0}. Explanation: An error occurred while attempting to get the count of the flagged items. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9449E: Unable to get collections by additions. Explanation: An error occurred while attempting to get the collections by additions, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred)
    EJPVJ9450E: Unable to get the count of the collections by additions. Explanation: An error occurred while attempting to get the count of the collections by additions. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9451E: Unable to get the library notifications for the user with id {0} Explanation: An error occurred while attempting to get the library notifications for the user with the specified id. The items may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the items were not accessible to the user, or a system error occurred).
    EJPVJ9452E: Unable to get the count of the library notifications for the user with id {0}. Explanation: An error occurred while attempting to get the count of the library notifications for the user with the specified id. The item may no longer exist or not be accessible, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9453E: Unable to get the media notifications for the user with id {0} Explanation: An error occurred while attempting to get the media notifications for the user with the specified id. The items may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the items were not accessible to the user, or a system error occurred).
    EJPVJ9454E: Unable to get the count of the media notifications for the user with id {0}. Explanation: An error occurred while attempting to get the count of the media notifications for the user with the specified id. The item may no longer exist or not be accessible, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9455E: Unable to get the collection notifications for the user with id {0} Explanation: An error occurred while attempting to get the collection notifications for the user with the specified id. The items may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the items were not accessible to the user, or a system error occurred).
    EJPVJ9456E: Unable to get the count of the collection notifications for the user with id {0}. Explanation: An error occurred while attempting to get the count of the collection notifications for the user with the specified id. The item may no longer exist or not be accessible, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9457E: Unable to get the flagged media. Explanation: An error occurred while attempting to get the flagged media. The item may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was not accessible to the user, or a system error occurred).
    EJPVJ9458E: Unable to get the media in moderation state {0}. Explanation: An error occurred while attempting to get the media in the specified moderation state. This action may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the action was not accessible to the user, or a system error occurred).
    EJPVJ9459E: Unable to get the count of the media in moderation state {0}. Explanation: An error occurred while attempting to get the count of the media in the specified moderation state. This action may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the action was not accessible to the user, or a system error occurred).
    EJPVJ9460E: Unable to get the count of the comments in moderation state {0}. Explanation: An error occurred while attempting to get the count of the comments in the specified moderation state. This action may not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the action was not accessible to the user, or a system error occurred).
    EJPVJ9461E: Unable to synchronize all members by external id. Explanation: An error occurred while running synchronize all members by external id via the MembershipServices MBean. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9462E: Unable to synchronize all members by external id due to validation failure. Please use true or false as parameter. Explanation: An error occurred while running synchronize for all members by external id due to a validation failure. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9463E: Unable to synchronize a member by external id. Explanation: An error occurred while running synchronize for a member by external id via the MembershipServices MBean. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9464E: Unable to set the state of the media with id {0}. Explanation: An error occurred while attempting to set the state of the media with the specified id. The item may no longer exist, a constraint violation may have occured, the user may not have moderation permission, moderation may not be supproted or enabled on this library type, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, a constraint violation occurred, the user is not a moderator, moderation is not supported or enabled on this library type, or a system error occurred).
    EJPVJ9470E: Unable to add object type Explanation: An error occurred while adding an object type User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9471E: Unable to browse object types Explanation: An error occurred while browsing object types User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9472E: Unable to delete object type {0} Explanation: An error occurred while deleting an object type User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9473E: Unable to update object type {0} Explanation: An error occurred while updating an object type User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9474E: Unable to update object type property for object type {0} Explanation: An error occurred while updating an object type property User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9475E: Unable to delete object type property choice for object type {0} Explanation: An error occurred while deleting an object type property choice User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9476E: Unable to edit object type {0} Explanation: An error occurred while editing an object type User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9477E: Unable to get object type {0} Explanation: An error occurred while getting an object type User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9478E: Unable to get object type count Explanation: An error occurred while counting object types User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9479E: Unable to add object type property {0} Explanation: An error occurred while adding an object type property User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9480E: Unable to add object type property choice Explanation: An error occurred while adding an object type property choice User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9481E: Unable to get object type properties for types {0} Explanation: An error occurred while getting type properties User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9482E: Unable to get object type property {0}. Explanation: An error occurred while getting an object type property. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9520E: UNABLE_TO_GET_COUNT_FOR_RELATIONSHIP_2=EJPVJ9520E: Unable to get the count for relationships between the item with id {0} and external resource with type {1}. Explanation: An error occurred while attempting to get the count for relationships between the item and the specified external resource type. An underlying system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9651E: Unable to read atom handler registries from file {0}. Explanation: An error occurred while attempting to read atom handler registries. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the file does not exist, or a system error occurred).
    EJPVJ9652E: Unable to find atom handler mapping file {0}. Explanation: An error occurred while attempting to read atom handler mapping file. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the file does not exist, or a system error occurred).
    EJPVJ9653E: Unable to find class with name {0}. Explanation: An error occurred while attempting to find class file. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the class file does not exist, or a system error occurred).
    EJPVJ9540E:UNABLE_TO_CHANGE_MEDIA_OBJECT_TYPE_1=EJPVJ9540E: Unable to change object type for the media with id {0}. Explanation: An error occurred while attempting to change object type for the media with specified id. The user may not have permission to perform this action, a constraint may be in violation, or an underlying system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected. Examples of expected action include the action was not accessible to the user, a constraint violation occurred, or a system error occurred.
    EJPVJ9654E: Unable to initialize class with name {0}. Explanation: An error occurred while attempting to initialize class. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9655E: Unable to access class with name {0} or its constructor. Explanation: An error occurred while attempting to access class or its constructor due to insufficient authority. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected.
    EJPVJ9656E: Unable to instantiate class with name {0}. Explanation: An error occurred while attempting to instantiate class.It is either an interface, abstract class or does not have the appropriate constructor. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected.
    EJPVJ9657E: The community type {0} is not valid. Explanation: The community type is not valid. One of public, private, or publicInviteOnly is expected. User Response: Please correct the community type.
    EJPVJ9658E: One or more of the required Community fields are missing: id, name, acting user Explanation: One or more of the Community fields required by the lifecycle API are missing, so the request cannot be completed. User Response: Please refer to the lifecycle implementation and specify all required API fields.
    EJPVJ9659E: The requested object to transfer is of type {0}, but requested via the wrong endpoint for that type. Explanation: The requested object to transfer is requested via the wrong endpoint for that type. User Response: Please ensure the transfer request is completed over the correct lifecycle endpoint for that type.
    EJPVJ9660E: The specified community id must be provided and valid. Explanation: The specified community id is not provided or not in UUID format. User Response: Please make sure the community id is correct.
    EJPVJ9661E: The specified request is either not atom format or structured incorrectly. Explanation: The request could not be parsed because it is not a valid atom document. User Response: Please check the content in the request, and make sure it is in proper atom format.
    EJPVJ9662E: The specified atom attribute {0} in element {1} is required. Explanation: The specified atom attribute in the specified element was missing, but is required. User Response: Please add the specified atom attribut in the element as it is required.
    EJPVJ9663E: The event type {0} is unsupported or invalid. Explanation: An event of the specified type was received, but could not be processed as the system does not support it. User Response: Please only use supported event types.
    EJPVJ9664E: Unable to handle community event. Explanation: An error occurred while attempting to handle a community lifecycle event. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9665E: Parameter {0} must be specified in lifecycle handler. Explanation: An internal error occurred while attempting to handle a community lifecycle event due to missing required parameters. User Response: Please provide the nested exception and details to the support team.
    EJPVJ9666E: Properties {0} cannot be null in lifecycle request. Explanation: The properties specified in the list cannot be null and must be specified with a lifecycle request. User Response: Please provided the specified properties with correct values when making a lifecycle API call.
    EJPVJ9667W: Unable to synchronize communities for widget adder {0}. Explanation: An error occurred while attempting to synchronize communities for the user who was adding a widget. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9700E: Unable to load MIME configuration from file {0}. Explanation: An error occurred while attempting to read the MIME configuration from the specified file. Either the file does not exist or the file contains erronious information. User Response: Examine the file and ensure it is in the correct location and the entries conform to the schema.
    EJPVJ9710W: Unable to delete the file pending deletion at {0}. Explanation: An error occurred while attempting to delete the specified file, which is pending deletion. Either the file does not exist or an I/O error occurred. User Response: Examine the nested exception and determine if action is needed, or if the file was already removed.
    EJPVJ9711E: Unable to delete all files from the file system. Explanation: An error occurred while attempting to delete files, which were pending deletion. Either the files did not exist or an I/O error occurred. User Response: Examine the nested exception and determine if action is needed, or if the files were already removed. If this error occurs repeatedly, the file system may contain a lot of deleted content.
    EJPVJ9712E: Unable to get the page position for the comment with id {0} and the type {1}. Explanation: An error occurred while attempting to get the page position for the comment with the specified id and type. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9713E: The database dialect {0} is invalid. The expected values are: "DB2®", "Oracle", "SQL Server" Explanation: An error occurred while reading the database dialect. One of the supported values must be specified. User Response: Examine the application configuration and ensure the value is properly specified and restart the application.
    EJPVJ9900E: Unable to get the download information for the item with the id {0}. Explanation: An error occurred while attempting to get the download information for the item with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9901E: Unable to get the download information for the media with the id {0} and the revision {1}. Explanation: An error occurred while attempting to get the download information for the media with the the specified id and revision. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9903E: Unable to edit the download information for the type {0}. Explanation: An error occurred while attempting to edit the download information for the specified type. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9904E: Unable to revert media to the revision with the id {0}. Explanation: An error occurred while attempting to revert the media to the revision with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9906E: Unable to get the download count for the item with id {0}. Explanation: An error occurred while attempting to get the download count for the item with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9907E: Unable to add a navigation element. Explanation: An error occurred while attempting to add a navigation element. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9908E: Unable to edit the navigation element with the id {0}. Explanation: An error occurred while attempting to edit the navigation element with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9909E: Unable to delete the navigation element with the id {0}. Explanation: An error occurred while attempting to delete the navigation element with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9910E: Unable to get the navigation element with the id {0}. Explanation: An error occurred while attempting to get the navigation element with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9911E: Unable to get the navigation elements for the library with the id {0}. Explanation: An error occurred while attempting to get the navigation elements for the library with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9912E: Unable to add a wiki link. Explanation: An error occurred while attempting to add a wiki link. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9913E: Unable to get the links for the label {0}. Explanation: An error occurred while attempting to get the links for the specified label. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9914E: Unable to get the links from the specified page. Explanation: An error occurred while attempting to get the links from the specified page. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9915E: Unable to delete the link at the specified location {0}. Explanation: An error occurred while attempting to delete the link at the specified location. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9916E: Unable to get the places for the seedlist. Explanation: An error occurred while attempting to get the places for the search seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9917E: Unable to get the updated places for the seedlist. Explanation: An error occurred while attempting to get the updated places for the search seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9918E: Unable to complete the action because the feature {0} is not enabled. Explanation: An action was attempted that could not be completed because the specified feature was not enabled. This feature may be disabled via configuration, or it might not be supported for the specific application or library type. User Response: If the feature is desired, check the configuration guide to see how to enable the specified feature.
    EJPVJ9919E: Unable to delete the expired search deletion history for libraries. Explanation: An error occurred while attempting to delete the expired search deletion history for libraries. The task to clear the search deletion history could not execute properly, and a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred). If this exception occurs repeatedly, extra data may be retained in the deleted library table.
    EJPVJ9920E: Unable to set the user name and display link for the places seedlist. Explanation: An error occurred while attempting to set the user name and display link for the places seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9921E: Unable to add a collection. Explanation: An error occurred while attempting to add a collection. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9922E: Unable to edit the collection with the id {0}. Explanation: An error occurred while attempting to edit the collection with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9923E: Unable to delete the collection with the id {0}. Explanation: An error occurred while attempting to edit the collection with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9924E: Unable to add the media with the id {0} to the collection with the id {1}. Explanation: An error occurred while attempting to add the media with the specified id to the collection with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9925E: Unable to delete the media with the id {0} to the collection with the id {1}. Explanation: An error occurred while attempting to delete the media with the specified id to the collection with the specified id. The user may not have permission to perform this action, a constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, a constraint violation occurred, or a system error occurred).
    EJPVJ9926E: Unable to get the collection with the id {0}. Explanation: An error occurred while attempting to get the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9927E: Unable to get the collections. Explanation: An error occurred while attempting to get the collections. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9928E: Unable to get the collections for the media with the id {0}. Explanation: An error occurred while attempting to get the collections for the media with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9929E: Unable to get the media for the collection with id {0}. Explanation: An error occurred while attempting to get the media for the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9930E: Unable to get the count of the collections. Explanation: An error occurred while attempting to get the count of the collections. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9931E: Unable to get the count of the media for the collection with id {0}. Explanation: An error occurred while attempting to get the count of the media for the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9933E: Unable to get the role assignments for the collection with the id {0}. Explanation: An error occurred while attempting to get the role assignments for the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9934E: Unable to assign a role for the collection with id {0} to the user with the id {1}. Explanation: An error occurred while attempting to assign a role for the collection with the specified id to the user with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9935E: Unable to assign a role for the collection with id {0} to the group with the id {1}. Explanation: An error occurred while attempting to assign a role for the collection with the specified id to the group with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9936E: Unable to assign roles for the collection. Explanation: An error occurred while attempting to assign roles for the collection. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9937E: Unable to delete the role for the collection with id {0} to the user with the id {1}. Explanation: An error occurred while attempting to delete the role for the collection with the specified id to the user with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9938E: Unable to delete the role for the collection with id {0} to the group with the id {1}. Explanation: An error occurred while attempting to delete the role for the collection with the specified id to the group with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9939E: Unable to get the count of the media in the collection with the id {0}. Explanation: An error occurred while attempting to get the count of the media in the collection with the specified id. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9940E: Unable to get the libraries with the specified ids. Explanation: An error occurred while attempting to get the libraries with the specified ids. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9941W: A virus was found in the uploaded file {0}. This file has been removed. Explanation: A virus was found in a file uploaded by a user, and has been removed to prevent security issues. User Response: No action is required, unless the user who uploaded the file must be contacted.
    EJPVJ9942W: A virus found in uploaded file {0}. This file could not be removed. Explanation: A virus was found in a file uploaded by a user, but could not be removed. User Response: You must manually remove the file.
    EJPVJ9943E: Unable to virus scan the uploaded file {0}. Explanation: An error occurred while attempting to virus scan the specified file. The item may not longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the file was removed, or a system error occurred).
    EJPVJ9944W: A virus that could be cleaned was found in the uploaded file {0}. The infected file has been removed and the cleaned version will be used instead. Explanation: A virus was found in a file uploaded by a user, but the file could safely be cleaned. The infected file has been removed to prevent security issues. User Response: No action is required, unless the user who uploaded the file must be contacted.
    EJPVJ9945W: A virus that could be cleaned was found in the uploaded file {0}. The infected file could not be removed. Explanation: A virus was found in a file uploaded by a user, but the file could safely be cleaned. The infected file could not be removed. User Response: You must manually remove the file.
    EJPVJ9949E: Unable to execute the event work item. Explanation: An error occurred while attempting to execute the event work item. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9951E: Unable to load the file {0}. Explanation: An error occurred while attempting to load the specified file. The file may not be accessible. User Response: Examine the nested exception and determine why the specified file is not accessible.
    EJPVJ9952E: Unable to synchronize the listed users by email. Explanation: An error occurred while running synchronize for a list of users by email via the MembershipServices MBean. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9954W: Unable to get the the user from the directory with the email {0}. Explanation: An error occurred while attempting to get the user from the directory with the specified email. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9956I: The user {0} has been updated successfully. Explanation: The specified user was properly updated during a synchronization command. User Response: No action is required.
    EJPVJ9957E: Unable to synchronize the user with email {0}. Explanation: An error occurred while attempting to synchronize the user with the specified email. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9958E: Unable to get product version information. Explanation: An error occurred while attempting to get the product version information from the database. a system error may have occurred. User Response: Examine the nested exception. If the database could not be reached, please check configuration. Otherwise, please ensure you have correctly installed a product and that the "PRODUCT" table contains a record.
    EJPVJ9959E: Unable to validate the schema version. The schema version detected is {0}, but the application version is {1}. Explanation: An error occurred during schema validation. The schema and application code do not match. User Response: Examine the versions and see which is out of date. It is likely that a prior upgrade failed, or that the schema or the application still needs upgrading.
    EJPVJ9960E: Unable to get the library with the external id {0} and the type {1}. Explanation: An error occurred while attempting to get the library with the specified id and type. The item may no longer exist or not be accessible to the user, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, not accessible to the user, or a system error occurred).
    EJPVJ9961E: Unable to get the library in mode {0}. Explanation: An error occurred while attempting to get the library with the specified mode. This exception should not occur. User Response: Report this exception.
    EJPVJ9962E: Unable to synchronize the user with login id {0}. Explanation: An error occurred while attempting to synchronize the user with the specified login id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9963E: Unable to synchronize the listed users by login id. Explanation: An error occurred while running synchronize for a list of users by login id via the MembershipServices MBean. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9964E: Unable to synchronize all of the users by login id. Explanation: An error occurred while running synchronize for all users by login id via the MembershipServices MBean. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9966I: Deleting {0} unused file(s) Explanation: The delete pending files task is about to delete unused files from the file system, which will make this many updates to the database if all items can be removed. User Response: No action is required.
    EJPVJ9967I: Updating the tag frequency data for {0} tag(s) in {1} segment(s). Explanation: The update tag frequency data task is about to update the application frequency data for all tags using as many queries as there are segments. Each segment will contain roughly an equal amount of the total tags. User Response: No action is required.
    EJPVJ9968E: Unable to update tag frequency data. Explanation: An error occurred while running the update tag frequency task. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred). If this exception occurs repeatedly, tag clouds may be out-of-date.
    EJPVJ9969E: Unable to get the users to be notified for the media with the id {0}. Explanation: An error occurred while attempting to get the users to be notified for the media with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9970E: Unable to get the public personal media. Explanation: An error occurred while attempting to get the public personal media. A constraint may have been violated, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a constraint was violated, or a system error occurred).
    EJPVJ9971E: Unable to get the count for the public personal media. Explanation: An error occurred while attempting to get the count for the public personal media. A constraint may have been violated, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a constraint was violated, or a system error occurred).
    EJPVJ9972E: Unable to get the user with the id {0}. Explanation: An error occurred while attempting to get the user with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9973E: Unable to get the user with the login id {0}. Explanation: An error occurred while attempting to get the user with the specified id. The item may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item was removed, or a system error occurred).
    EJPVJ9974E: The MIME configuration is invalid. The "mimeType" {0} is already mapped to the "mediaType" {1}. Explanation: An error occurred while attempting to load the MIME configuration. The specified "mimeType" has more than one entry in the MIME configuration. User Response: Examine the MIME configuration and remove the duplicate "mimeType" mapping.
    EJPVJ9975E: The MIME configuration is invalid. The "extension" {0} is already mapped to the "mimeType" {1}. Explanation: An error occurred while attempting to load the MIME configuration. The specified "extension" appears in more than one entry in the MIME configuration. User Response: Examine the MIME configuration and remove the duplicate "mimeType" entry.
    EJPVJ9976E: The MIME configuration is invalid. The "mediaType" {0} is not a recognized value. Explanation: An error occurred while attempting to load the MIME configuration. The specified "mediaType" is not one of the allowed values. User Response: Examine the MIME configuration and correct the "mediaType" by specifying an allowed value from the administration guide.
    EJPVJ9977E: Unable to get additional media data for the Community document seedlist. Explanation: An error occurred while attempting to get additional media data for the Community document seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9978E: Unable to get additional media data for the personal document seedlist. Explanation: An error occurred while attempting to get additional media data for the personal document seedlist. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9980E: Unable to delete the media with the id {0} from the collections which the user with id {1} cannot see. Explanation: An error occurred while attempting to delete the media with the specified id from the collections which the user with the specified id cannot see. The user may not have permission to perform this action, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (user was not permitted, or a system error occurred).
    EJPVJ9981W: Unable to initialize search. Explanation: An error occurred while attempting to initialize the search EJB. The search component may not be properly installed or configured, or search may be disabled. User Response: If search is enabled, ensure that the JNDI binding is properly specified in the WebSphere administration console and that it is properly configured.
    EJPVJ9982I: The unused file at {0} could not be moved to {1} and should manually be moved or removed. Explanation: An error occurred while attempting to move the specified file to the specified location during a data integrity check. A disk failure may have occurred. User Response: You should manually move or remove the file, as it is not needed.
    EJPVJ9983E: Unable to get the users this user has shared with. Explanation: An error occurred while attempting to get the users this user has shared with. a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a system error occurred).
    EJPVJ9984E: The size of the file {0} on disk is different from the size stored in the database. Explanation: File size on disk may vary when files are copied between operating systems or when altered by another process or procedure such as restoration. User Response: Check that the contents of the file have not been corrupted. To see all conflicting sizes, run the data integrity service.
    EJPVJ9985E: Unable to edit the preferred locales for the user with id {0}. Explanation: An error occurred while attempting to edit the preferred locales for the user with the specified id. The user may no longer exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the user was removed, or a system error occurred).
    EJPVJ9986E: The size of file identified by id {0} (referenced in table {1} column {2}) is not the same as the size in the database. Explanation: The size of the specified file on disk was found to be different from the size in the database. This indicates a data corruption, caused by an incorrect restoration or other data loss. User Response: Restore previous back-ups to locate the file, or remove the referencing item.
    EJPVJ9987E: Unable to get user from database or add a new user with email {0}. Explanation: An error occurred while attempting to get user from database or add a user with the specified email. A constraint may be in violation, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a constraint violation occurred, or a system error occurred).
    EJPVJ9988E: Unable to get the user with the email {0}. Explanation: An error occurred while attempting to get the user with the specified email. The item may not exist, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (the item does not exist, or a system error occurred).
    EJPVJ9989E: Unable to create a transactional file at {0}. Explanation: An error occurred while attempting to create a transactional file at the specified path. A virus scan issue may have prevented it, or a system error may have occurred. User Response: Examine the nested exception and determine if action is needed, or if the failure was expected (a virus scan issue exists, or a system error occurred).
    EJPVJ9990E: Unexpected data was returned from the directory for the user {0}. Explanation: When retrieving data from the directory, unexpected data was provided and so the user could not be stored. This can include missing required data or fields that are too long. User Response: Ensure that none of the directory fields used exceed the supported lengths found in the installation documentation, and that all required fields are populated.
    EJPVJ9999E: Invalid extension validation configuration. Explanation: The extension validation settings are invalid. User Response: Ensure that the extension validation configuration contains valid settings.


    Home page error messages

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

    The following Home page error messages are generated by IBM Connections:

    Table 14. Home page error messages

    Message Cause Solution
    CLFRQ0002E: Failure to retrieve all enabled widgets in catalog. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the IBM WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0003W: Missing id or display name for third party application. id = {0}, displayName = {1} A third-party application registration was found, but did not have necessary information to add it as a filter in activity streams. Review registered third-party applications and ensure that both an ID and a display name are provided.
    CLFRQ0004E: Failure to delete auxiliary information for widget with key {0}. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0004E: An error occurred getting list of third party applications. Unable to resolve the list of third-party applications that are registered for activity stream integration. Any third-party application will not be added to the filters in activity streams. Check for nested or prior exceptions in log.
    CLFRQ0005E: The transaction could not be started. There is a severe problem in your database manager. Transactions cannot be started.

    1. Verify the database server is properly installed and running.

    2. Check the database connection configuration in the WebSphere Application Server installation.

    3. Verify the database HOMEPAGE has been properly installed.

    4. Check in the database server documentation for any configuration needed to handle transactions correctly.
    CLFRQ0007E: Failure to retrieve enabled widget with identifier {0} There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0010E: The transaction could not be rolled back. There is a severe problem in your database manager. Transactions cannot be rolled back.

    1. Verify the database server is properly installed and running.

    2. Check the database connection configuration in the WebSphere Application Server installation.

    3. Verify the database HOMEPAGE has been properly installed.

    4. Check in the database server documentation for any configuration needed to handle transactions correctly.
    CLFRQ0012E: Failure to disable widget with key {1} in catalog. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0013E: The transaction could not be committed. There is a severe problem in your database manager. Transactions cannot be committed.

    1. Verify the database server is properly installed and running.

    2. Check the database connection configuration in the WebSphere Application Server installation.

    3. Verify the database HOMEPAGE has been properly installed.

    4. Check in the database server documentation for any configuration needed to handle transactions correctly.
    CLFRQ0014E: Failure to enable widget with key {1} in catalog. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0016E: Failure to retrieve auxiliary information for widget with key {0}. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0019E: The widget with identifier {0} cannot be removed because it is a system widget. Default widgets shipped with an IBM Connections Home Page installation cannot be removed.

    1. Verify the IBM Connections Home Page installation finished successfully.

    2. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0020E: An error occurred while attempting to retrieve a list of all widgets. The Home Page data access object cannot retrieve information for available widgets.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0021E: A null value was provided as a parameter. A null parameter has been provided to a Home Page server-side service.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0022E: The widget with identifier {0} could not be updated. A widget with a specific identifier was not found in the Home Page widget catalog.

    1. Verify the IBM Connections Home Page installation finished successfully.

    2. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0023E: The widget with identifier {0} could not be removed. A widget with a specific identifier was not found in the Home Page widget catalog.

    1. Verify the IBM Connections Home Page installation finished successfully.

    2. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0024E: A new widget cannot be added with identifier {0}. There is a problem with adding a new widget, as that would duplicate a primary key.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0026E: The widget with identifier {0} could not be enabled. A widget with a specific identifier was not found in the Home Page widget catalog.

    1. Verify the IBM Connections Home Page installation finished successfully.

    2. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0027E: An error occurred while attempting to retrieve a list of all available widgets. The Home Page data access object cannot retrieve information for available widgets.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0028E: The widget with identifier {0} could not be disabled. A widget with a specific identifier was not found in the Home Page widget catalog.

    1. Verify the IBM Connections Home Page installation finished successfully.

    2. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0029E: An error occurred while attempting to retrieve the widget with identifier {0}. The Home Page data access object cannot retrieve information for available widgets.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0030E: The widget with identifier {0} could not be retrieved. A widget with a specific identifier was not found in the Home Page widget catalog.

    1. Verify the IBM Connections Home Page installation finished successfully.

    2. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0031E: The database transaction could not be rolled back. There is a severe problem in your database manager. Transactions cannot be rolled back.

    1. Verify the database server is properly installed and running.

    2. Check the database connection configuration in the WebSphere Application Server installation.

    3. Verify the database HOMEPAGE has been properly installed.

    4. Check in the database server documentation for any configuration needed to handle transactions correctly.
    CLFRQ0033E: Data access object factory cannot be retrieved. The configuration for the data access object cannot be retrieved correctly.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0035E: The widget catalog administration service could not be retrieved. The IBM Connections Home Page administration service is not available.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0040E: An error occurred while querying by primary key at table {0} using this primary key: {1}. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0042E: An error occurred while loading configuration for data access object from this file: {0}. The configuration for the data access object cannot be retrieved correctly.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0043E: An error occurred while updating table {0} using this object: {1}. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0044E: An error occurred while initializing the data access object manager using this file: {0}. The configuration for the data access object cannot be retrieved correctly.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0047E: An error occurred while retrieving the user with this email: {0}. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0050E: An error occurred while selecting all entries of table: {0}. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0053E: An error occurred while deleting from table {0} using this primary key: {1}. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0055E: An error occurred while initializing the following data access object: {0}. The configuration for the data access object cannot be retrieved correctly.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0056E: An error occurred while inserting to table {0} using this primary key: {1}. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0057E: The position parameter is not specified for this user: {0} The IBM Connections Home Page web application received incorrect information to retrieve or set user preferences. Verify the Home Page application has been installed correctly.
    CLFRQ0060E: An error occurred while attempting to apply new widget settings with this information: {0} There is a problem in trying to configure IBM Connections Home Page preferences for a specific user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0064I: There are no available widgets in the catalog. The IBM Connections Home Page widget catalog is empty.

    1. Verify the Home Page application has been installed correctly.

    2. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0065I: User preferences are not specified for the user: {0} There are no preferences available for the specified user.

    1. Verify the Home Page application has been installed correctly.

    2. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0066E: Could not retrieve details for the user with login ID: {0} due to an exception. The exception occurred when retrieving the details via the virtual member manager directly: {1} There is a problem in accessing information for the specified user.

    1. Verify the IBM Connections directory service is installed correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the database for the directory service has been installed correctly.
    CLFRQ0067E: The widget identifier is not specified for this user: {0} The IBM Connections Home Page web application received incorrect information to retrieve or set user preferences. Verify the Home Page application has been installed correctly.
    CLFRQ0068E: The email or the user identifier is null. These are the values retrieved: email {0}, user identifier {1}. There is a problem in accessing information for the specified user.

    1. Verify the IBM Connections directory service is installed correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the database for the directory service has been installed correctly.
    CLFRQ0069E: An error occurred while deleting the position for this user: {0}. The user is trying to remove the widget with identifier {1} to the side palette. The IBM Connections Home Page web application received incorrect information to retrieve or set user preferences. Verify the Home Page application has been installed correctly.
    CLFRQ0071E: An error occurred while retrieving the Profile Provider: Profile Provider is null. There is a problem with the IBM Connections directory service.

    1. Verify the IBM Connections directory service is installed correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the database for the directory service has been installed correctly.
    CLFRQ0073E: An error occurred while retrieving the Member Profile: Member Profile is null. There is a problem with the IBM Connections directory service.

    1. Verify the IBM Connections directory service is installed correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the database for the directory service has been installed correctly.
    CLFRQ0074E: The action is not specified for this REST call. The IBM Connections Home Page web application received incorrect information to retrieve or set user preferences. Verify the Home Page application has been installed correctly.
    CLFRQ0075E: The current user session is not valid. Information about the current session was lost in an irregular manner. Check your WebSphere Application Server install.
    CLFRQ0076E: The user e-mail attribute is missing from the session. Information about the current session was lost in an irregular manner. Check your WebSphere Application Server install.
    CLFRQ0077E: Action: {0} is not valid for this REST call. The IBM Connections Home Page web application received incorrect information to retrieve or set user preferences. Verify the Home Page application has been installed correctly.
    CLFRQ0078E: An error occurred while retrieving the available widgets information. The Home Page data access object cannot retrieve information for available widgets.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0084E: An error occurred while retrieving the total number of enabled widgets. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0085E: An error occurred while retrieving widget usage statistics. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0086E: An error occurred while retrieving the total number of widgets. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0087E: An error occurred while retrieving the total number of people registered in the database. There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0088E: An error occurred while retrieving the number of unique visits between these dates: {0}, {1} There is an error in accessing the Home Page database. Next error in the log should provide more information about the specific action causing this error.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0089E: An error occurred while updating the last visit information for this user: {0} There is a problem in saving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0090E: An error occurred in the catalog configuration service. The Home Page data access object cannot retrieve information for available widgets.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0091E: An input-output error occurred while the widget descriptor was responding to client. The content of the XML description is this: {0} The URL specified for a new widget is incorrect or not available to the IBM Connections Home Page application.

    1. Verify the widget is located in a URL accessible from the Home Page application.

    2. Make sure that the URL points to a correct location for an XML descriptor.
    CLFRQ0100E: No name was provided for resource bundle containing build version. Information about the current version of Home Page was not provided correctly. Verify the Home Page application has been installed correctly.
    CLFRQ0104E: The resource bundle containing the build version does not exist. Information about the current version of Home Page was not provided correctly. Verify the Home Page application has been installed correctly.
    CLFRQ0106E: Wrong data type for build version. Information about the current version of Home Page was not provided correctly. Verify the Home Page application has been installed correctly.
    CLFRQ0113E: Failure to access IBM Connections configuration service. The IBM Connections configuration information is not available for Home Page tasks.

    1. Verify the installation of IBM Connections finished successfully.

    2. Verify the LotusConnections-config files have been deployed correctly for the configuration.

    3. Verify LotusConnections-config.xml has not been modified incorrectly and validates with the proper XML schema.
    CLFRQ0114E: An error occurred while rolling back database transaction. There is a severe problem in your database manager. Transactions cannot be rolled back.

    1. Verify the database server is properly installed and running.

    2. Check the database connection configuration in the WebSphere Application Server installation.

    3. Verify the database HOMEPAGE has been properly installed.

    4. Check in the database server documentation for any configuration needed to handle transactions correctly.
    CLFRQ0123E: Protocol not supported for {0} A non-supported protocol was specified in the URL of a new widget.

    1. Change the widget preferences using the administration page.

    2. Specify an absolute URL using the HTTP protocol, or specify a URL relative to the Home Page application.
    CLFRQ0125E: An error occurred while creating a new user for the Home page with email {0} and identifier {1}. There is a problem in trying to configure IBM Connections Home Page preferences for a specific user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0126E: An error occurred while retrieving widget preference information for user identified by {0} widget identified by {1}, tab instance identified by {2} There is a problem in trying to configure IBM Connections Home Page preferences for a specific user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0128E: An error occurred while creating a user with this information: {0} There is a problem while accessing Home Page preferences for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0131E: An error occurred while retrieving user information with this e-mail: {0} There is a problem while accessing Home Page preferences for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0132E: An error occurred while changing settings for a widget with this information: {0},{1} There is a problem while accessing Home Page preferences for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0133E: An error occurred while retrieving user information with this identifier: {0} There is a problem while accessing Home Page preferences for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0134E: An error occurred while retrieving the number of users registered in the database. There is a problem while accessing Home Page preferences for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0137W: An error occurred while updating the welcome mode for a user with this information:{0},{1} There is a problem in saving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0138E: An error occurred while changing the position for a widget with this information: {0},{1},{2},{3} There is a problem while accessing Home Page preferences for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0139W: An error occurred while updating the last visit for a user with this information: {0},{1} There is a problem in saving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0141E: A property was specified as translatable in the widget catalog with key {0}, but no equivalent translated property was found in the resource bundle. The character % in the first position of a widget title or description has a special meaning for Home Page services.

    1. Edit any widget that contains a character % in the first position of its title or description.

    2. Remove the character % from the first position of any title or description.
    CLFRQ0179E: The database connection cannot be initialized. The configuration for the data access object cannot be retrieved correctly.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0183E: An error occurred while attempting to retrieve a list of enabled widgets. The Home Page data access object cannot retrieve information for available widgets.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0184E: The list of installed IBM Connections applications could not be retrieved. IBM Connections configuration information is not available for Home Page tasks.

    1. Verify the installation of IBM Connections finished successfully.

    2. Verify the LotusConnections-config files have been deployed correctly for the configuration.

    3. Verify LotusConnections-config.xml has not been modified incorrectly and validates with the proper XML schema.
    CLFRQ0185E: An error occurred while attempting to retrieve a list of disabled widgets. The Home Page data access object cannot retrieve information for available widgets.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0186E: The widget with identifier {0} was not found in the database. A widget with a specific identifier was not found in the Home Page widget catalog.

    1. Verify the IBM Connections Home Page installation finished successfully.

    2. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0187E: The title of widget with identifier {0} could not be updated. A widget with a specific identifier was not found in the Home Page widget catalog.

    1. Verify the IBM Connections Home Page installation finished successfully.

    2. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0188E: Administration test mode could not be enabled for user with e-mail {0}. There is a problem while configuring Administrator's privileges for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0189E: Administration test mode could not be disabled for user with e-mail {0}. There is a problem while configuring Administrator's privileges for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0190E: Current status of administration's test mode could not be retrieved for user with e-mail {0}. There is a problem while retrieving Administrator's privileges for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0191E: An error occurred while creating persistence bean for user with e-mail {0}. There is a problem in trying to configure IBM Connections Home Page preferences for a specific user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0192E: The widget with identifier {0} could not be enabled. There is a problem while accessing properties for a particular widget.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0193E: The widget with identifier {0} could not be retrieved from the catalog. There is a problem while accessing properties for a particular widget.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0194E: The new widget could not be added to the catalog. The following data was provided: {0} There is a problem while accessing properties for a particular widget.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0195E: The widget with identifier {0} could not be removed. There is a problem while accessing properties for a particular widget.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0196E: The widget could not be updated in the catalog. The following data was provided: {0} There is a problem while accessing properties for a particular widget.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0197E: An error occurred when setting administration test mode to {0} for user with email {1}. There is a problem while configuring Administrator's privileges for a particular user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0198E: A widget identifier was not provided as a parameter. A null parameter was provided to the IBM Connections Home Page administration service. Verify the Home Page application has been installed correctly.
    CLFRQ0199E: An error occurred while loading customization for user with e-mail {0} and widget with identifier {1}. There is a problem in trying to configure IBM Connections Home Page preferences for a specific user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0200E: It was not possible to check preferences related to administration test mode for user with e-mail {0}. There is a problem in trying to configure IBM Connections Home Page administration preferences for a specific user.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0201E: The widget with identifier {0} could not be disabled. There is a problem while accessing properties for a particular widget.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the HOMEPAGE database has been properly installed.
    CLFRQ0218E: An error occurred while accessing the directory services: {0} There was an error while trying to retrieve information from the IBM Connections directory service. Enclosed error will give more information about it.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.

    4. Check the server log for more information.
    CLFRQ0219E: File [{0}] does not exist. The specified file does not exist. Provide a correct path with a list of emails for administration configuration task.
    CLFRQ0220E: An error occurred while accessing the database: {0} There was an error while trying to retrieve information from the IBM Connections Home Page database. Enclosed error will give more information about it.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.

    4. Check the server log for more information.
    CLFRQ0221E: Reference to directory services could not be retrieved. It was not possible to access IBM Connections directory services while running an administration configuration task.

    1. Verify the IBM Connections directory service is installed correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the database for the directory service has been installed correctly.
    CLFRQ0222E: An error occurred while trying to read file [{0}]: {1} There is a problem in the provided file. Verify the file is available and has a proper format.
    CLFRQ0223E: A reference to the data access object factory could not be retrieved. The configuration for the data access object cannot be retrieved correctly.

    1. Check the database connection configuration in the WebSphere Application Server installation.

    2. Verify the Home Page application has been installed correctly.

    3. Verify the database HOMEPAGE has been properly installed.
    CLFRQ0224I: Update was completed successfully. Information was successfully saved in Home page's database. This is an informational message only.
    CLFRQ0225W: User with e-mail [{0}] was not found in the directory service. A user was not found when searched in the directory service. Possibly the user was removed from LDAP or equivalent service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0226W: Not all users were found in either the Home Page database or the IBM Connections directory service. Please check server logs for details. A user was not found when searched in the directory service. Possibly the user was removed from LDAP or equivalent service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0227E: The user with e-mail [{0}] is not registered in the Home Page database. A user does not exist in Home page's database. Possibly their email has been changed, but a synchronization has not been performed.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.

    4. If email fields were updated, a synchronization needs to be performed.
    CLFRQ0230E: An error occurred while disabling administration test mode for the user with identifier {0}. There is a problem in saving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0231E: Failure to retrieve all disabled widgets in catalog. List of disabled widgets was not retrieved correctly.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0232E: An error occurred while enabling administration test mode for the user with identifier {0}. There is a problem in saving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0233E: Failure to retrieve disabled widget with identifier {0}. A widget could not be retrieved from Home page's database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0234E: An error occurred while updating the widget title for this object: {0} There is a problem in saving a widget preference in Home page's database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0235E: An error occurred while closing the Home Page statistics file. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0236E: The file used in the metrics service is not valid. The name of the file is [{0}]. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0237I: Hash table is seeded. This is an informational message only. This is an informational message; no action is required.
    CLFRQ0238E: The value of the number of visits in the past hour could not be retrieved. There is a problem in gathering statistics from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0239E: File [{0}] cannot be read. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0240I: The timeout has been correctly changed to this value: [{0}] There was a problem collecting usage metrics for the Home page. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0241I: Set timeout to {0} minutes. This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0242E: An error occurred while writing the Home Page statistics file. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0243E: An error occurred when registering the Home page MBean. Administration facilities may not be available. There was a problem in starting up Home page's administration facilities. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0244I: File [{0}] can be read. This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0245E: The value of the field key is wrong. There was a problem collecting usage metrics for the Home page. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0246E: MBean server could not be located. There was a problem in starting up Home page's administration facilities. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0247E: The value of the cache timeout is not valid. It is either less than 0 or more than 1440 minutes. There was a problem collecting usage metrics for the Home page. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0248E: File [{0}] already exists. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0249E: The value of the number of visits in the past 24 hours could not be retrieved. There is a problem in gathering statistics from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0250I: The metrics service is using this separator: [{0}] This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0251E: The value of the total number of widgets could not be retrieved. There is a problem in gathering statistics from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0252E: An error occurred while parsing the Home Page statistics file. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0253E: An error occurred while creating the Home Page statistics file. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0254E: The length of the separator is wrong. It is longer than one character. There was a problem collecting usage metrics for the Home page. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0255E: File or directory {0} does not exist. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0256I: File or directory [{0}] exists. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0257I: Name of property: {0}, value of property: {1} This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0258E: The value of the total number of enabled widgets could not be retrieved. There is a problem in gathering statistics from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0259E: Creation of file [{0}] failed. A file system error has occurred.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that the file system where the server is running has space available and does not have any low-level error.
    CLFRQ0260E: A directory was specified, but not a file. There was a problem collecting usage metrics for the Home page. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0261E: The value of the sample count is not valid. There was a problem collecting usage metrics for the Home page. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0262I: File [{0}] created successfully. This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0263E: The value of the total number of open widgets could not be retrieved. There is a problem in gathering statistics from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0264I: Testing if file or directory [{0}] exists. This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0265E: The value of the number of widgets used could not be retrieved. There is a problem in gathering statistics from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0266E: The data type of the field key is wrong. There was a problem collecting usage metrics for the Home page. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0267E: The value of the total number of users could not be retrieved. There is a problem in gathering statistics from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0268I: Path [{0}] is a file, not a directory. This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0269E: An error occurred when unregistering the Home page MBean. There was a problem in setting up Home page's administration facilities. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0271E: An error occurred when trying to retrieve the IBM Connections service to check this URL: {0} An error ocurred while loading the specified URL. This error message is produced when checking URL's for third-party widgets added to the Home page.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that any URL specified for a third-party widget exists and that can be reached from the Home page server.
    CLFRQ0273W: An error occurred when trying to check this URL: {0} An error occurred while loading the specified URL. This error message is produced when checking URL's for third-party widgets added to the Home page.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Make sure that any URL specified for a third-party widget exists and that can be reached from the Home page server.
    CLFRQ0275E: The widget catalog service could not be retrieved. There is a problem in setting up service to retrieve available widgets.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0276E: The user preferences service could not be retrieved to update welcome mode. There is a problem in setting up service to update user preferences.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0277E: There is no dictionary available in memory. Either the dictionary failed to load or there may be a problem with the configuration. Check the detailed exception message following this error message in the log file to find the root cause.
    CLFRQ0284E: An error occurred while retrieving the user UI setting for the user referenced by this ID {0}. There is a problem in retrieving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0291E: An error occurred while retrieving widget preferences with this identifier: {0} There is a problem in retrieving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0292E: An error occurred when creating a widget for the user: {0}. Here is the widget information that the system is not able to store. Widget ID: {1}, Order: {2}, Container: {3}, IsToggled: {4}, PagePanel id {5}, Widget Sets: {6} There is a problem in saving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0295E: An error occurred while retrieving the widget instances for the user: {0} related to this page panel {1} and this widget ID {2} There is a problem in retrieving Home page preferences for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0296I: Redirecting the browser to {0} after form based authentication challenge detected on an asynchronous request This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0297E: Error generating the search results feed. An error occurred while generating the search results feed. Ensure that the search service has been started and indexing has been completed.
    CLFRQ0298W: A Directory Services error occurred while retrieving groups for user {0}. Information about a user could not be retrieved from the directory service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0299I: No Homepage cookie detected after form-based authentication challenge on asynchronous request, redirecting to Homepage context path root by default Information message when a user is redirected to the login page after a form is detected on an asynchronous request. This is an informational message only.
    CLFRQ0300E: An error occurred while getting the homepage context root URL from the configuration files The context root for the Home page application could not be determined.

    1. Verify the IBM Connections Home page is installed correctly.

    2. If changes have been made to the IBM Connections configuration, make sure that those changes have been validated correctly.
    CLFRQ0301E: JNDI naming exception caught. Connections Home page application has been incorrectly deployed. A JNDI look up could not be performed. Possibly, the Home page application was not correctly installed or deployed. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0311E: An error occurred while retrieving notifications sent by user referenced by this ID {0}. There is a problem in retrieving Home page information for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0312E: An error occurred while retrieving notifications received for user referenced by this ID {0}. There is a problem in retrieving Home page information for a user.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0314E: An error occurred while creating a notification with this information: {0} An error occurred while persisting the notification.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0315E: An error occurred while retrieving the number of unique visit starting from this date: {0} There is a problem in gathering statistics from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0318E: An IO error occurred while retrieving the widget descriptor located at {0}. See nested exception for more details. A widget descriptor could not be retrieved. The problem could be in a local or remote location, depending on the settings of the widget.

    1. Verify the IBM Connections Home page is installed correctly.

    2. If the widget has been configured with a local path, verify that the file exists and that it is accessible from the server.

    3. If the widget has been configured with a remote path, verify that the URL points to a valid location and that it can be reached from the server.
    CLFRQ0319E: An error occurred while reading the returned widget descriptor located at {0}. See nested exception for more details. A widget descriptor could not be retrieved. The problem could be in a local or remote location, depending on the settings of the widget.

    1. Verify the IBM Connections Home page is installed correctly.

    2. If the widget has been configured with a local path, verify that the file exists and that it is accessible from the server.

    3. If the widget has been configured with a remote path, verify that the URL points to a valid location and that it can be reached from the server.
    CLFRQ0320E: An error occurred while reading the widget descriptor file located at {0}. See nested exception for more details. A widget descriptor could not be retrieved. The problem could be in a local or remote location, depending on the settings of the widget.

    1. Verify the IBM Connections Home page is installed correctly.

    2. If the widget has been configured with a local path, verify that the file exists and that it is accessible from the server.

    3. If the widget has been configured with a remote path, verify that the URL points to a valid location and that it can be reached from the server.
    CLFRQ0321E: An HTTP error occurred while retrieving the widget descriptor located at {0}. See nested exception for more details. A widget descriptor could not be retrieved from a remote location.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the widget URL points to a valid location and that it can be reached from the server.
    CLFRQ0322E: An error occurred while retrieving the widget descriptor located at {0}. Returned error code was {1} A widget descriptor could not be retrieved. The problem could be in a local or remote location, depending on the settings of the widget.

    1. Verify the IBM Connections Home page is installed correctly.

    2. If the widget has been configured with a local path, verify that the file exists and that it is accessible from the server.

    3. If the widget has been configured with a remote path, verify that the URL points to a valid location and that it can be reached from the server.
    CLFRQ0323E: An error occurred while adding the descriptor for widget {0} to in-memory caching. See nested exception for full details. Homepage tried to fetch the XML descriptor for a Widget but failed. This can happen at application startup and when adding a new widget in the Homepage administration interface.

    1. Check that the URL to the XML descriptor is correct in the Administration page of the Home page.

    2. Check that the XML descriptor file is accessible from the Home page server (for example, check firewall configuration on the remote server hosting the widget descriptor).

    3. Check the nested exception in the logs to see the exact cause of the problem.
    CLFRQ0325E: An error occurred while updating the descriptor for widget {0} to in-memory caching. See nested exception for full details. Homepage tried to fetch the XML descriptor for a Widget but failed. Similar to CLFRQ0323E, except that this happens when the administrator clicks the "Refresh cache" button in the admin interface.

    1. Check that the URL to the XML descriptor is correct in the Administration page of the Home page.

    2. Check that the XML descriptor file is accessible from the Home page server (for example, check firewall configuration on the remote server hosting the widget descriptor).

    3. Check the nested exception in the logs to see the exact cause of the problem.
    CLFRQ0332W: User with ID [{0}] was not found in the directory service. Information about a user could not be retrieved from the directory service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0333E: An empty DSObject was sent as a parameter. Directory service is not available or configured incorrectly.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0334E: E-mail [{0}] already exists in the database. User identified with login name [{0}] cannot be added to the database. A new Home page user has the same email as another user. If there is no duplication, a change has occurred in the user directory and has not been synchronized.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.

    4. Make sure that there is no duplication in emails in the directory service.

    5. Synchronize Home page users using the NewsMemberService.
    CLFRQ0335W: User with login name [{0}] was not found in the directory service. Information about a user could not be retrieved from the directory service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0336E: E-mail [{0}] already exists in the database. User identified with external ID [{0}] cannot be added to the database. A new Home page user has the same email as another user. If there is no duplication, a change has occurred in the user directory and has not been synchronized.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.

    4. Make sure that there is no duplication in emails in the directory service.

    5. Synchronize Home page users using the NewsMemberService.
    CLFRQ0338E: An error has occurred during the retrieval of all the widget information using this ID {0} There is a problem in setting up service to retrieve available widgets.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0339E: An error has occurred during the deletion of all the records with this ID {0} There is a problem in removing records from the Home page database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0340I: Home Page service is running with Profiles Directory Service Extension enabled. This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0341E: Could not retrieve details for the user with login ID: {0} due to an exception. The exception occurred when retrieving the details via Profiles Directory Service Extension: {1} Information about a user could not be retrieved from the directory service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0342E: No user details were returned for the user with login ID: {0}. Attempted to retrieve details via Profiles Directory Service Extension. The user may not be a valid user in Profiles. Information about a user could not be retrieved from the directory service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0343I: Home Page service is running with Profiles Directory Service Extension disabled. This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0344E: No user details could were returned for the user with login ID: {0}. Attempted to retrieve details via the virtual member manager directly. The user may not be a valid user in the user registry. Information about a user could not be retrieved from the directory service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0345E: An error occurred when creating a tab instance for user ID {0}. Check nested exception for details. Home page preferences for a user could not be saved in database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0347E: Could not roll back a transaction when creating tab instances for user ID {0}. Check nested exception for more details. Home page preferences for a user could not be saved in database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0348E: An error occurred while getting the tab instance with ID {0}. Check nested exception for more details. Home page preferences for a user could not be retrieved from database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0349E: An error occurred while updating the number of columns for tab instance {0}. Check nested exception for more details. Home page preferences for a user could not be saved in database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0350E: An error when getting the list of tab instances for user {0}. See nested exception for more details. Home page preferences for a user could not be retrieved from database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0351I: No existing widget instances for user {0} and tab instance {1}, creating default set This is an informational message only. This is an informational message only; no action is required.
    CLFRQ0352E: An error occurred while getting a tab instance for user {0}. See nested exception for more details Home page preferences for a user could not be retrieved from database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0353E: An error occurred while parsing the layout JSON string {0}. See nested exception for details This error can occur when the user changes the layout of the page (add, remove or change the location of a widget). The layout of the page is translated into a JSON string sent to the server to persist it across user sessions. The page layout is not persisted for the user. Most likely cause of the problem is that the user tried to craft a custom JSON string manually and sent it to the server using a the POST HTTP method.
    CLFRQ0354E: An error occurred while setting the request parameter containing the number of column for tab instance {0}. Check nested exception for more Home page preferences for a user could not be retrieved from database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0355E: It is not possible to retrieve the tab instance ID. An error occurred while getting the internal ID of the authenticated user from the session. Information about a user could not be retrieved from the directory service.

    1. Verify the IBM Connections directory service is configured correctly.

    2. Check that the LDAP server for the configuration is available (if you choose to use one).

    3. Verify the Home page database has been installed correctly.
    CLFRQ0356E: The panel service could not be retrieved Error during the initialization of Home page's services.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0357E: An error occurred while updating the number of columns from the tab ID {0} Home page preferences for a user could not be saved in database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0380E: An error occurred while retrieving the count of notifications received since last login for the user referenced by this ID {0}. Home page information for a user could not be retrieved from database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0381W: An error occurred while updating the last visit field for user with this identifier: {0} Home page preferences for a user could not be saved in database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0382E: An error occurred while invoking a remote interface (EJB) for fetching news stories for person ID {0}. Check nested exception for more details. News stories cannot be retrieved. This error is due to problems in the News repository application.

    1. Verify the Home page has been installed correctly.

    2. Verify the News repository has been installed correctly.

    3. Verify the Home page database has been installed correctly.
    CLFRQ0382W: Invalid page size ({0}) passed as request parameter. Using default page size value: {1}. User is {2} A request is trying to retrieve more stories per page than allowed. The default page size will be used instead. Verify the Home page has been installed correctly.
    CLFRQ0383E: An error has occurred during the retrieval of the widgets using this ID {0} There is a problem while retrieving a widget.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0383E: An error occurred while invoking a remote interface (EJB) for marking or unmarking the news story with id {0} as saved. Check nested exception for more details. News stories cannot be marked or unmarked for saving. This error is due to problems in the News repository application.

    1. Verify the Home page has been installed correctly.

    2. Verify the News repository has been installed correctly.

    3. Verify the Home page database has been installed correctly.
    CLFRQ0384A: An error occurred while updating the welcome note for this internal ID: {0} Error occurred when a user dismissed the Welcome box for Homepage. Could be an issue accessing or updating the database, or a problem retrieving user details.

    1. Check for nested exceptions, or prior exceptions in the logs related to database access.

    2. Check that members are synchronized for the Homepage database, using the NewsMemberService.
    CLFRQ0384E: An error occurred while creating a remote interface (EJB) to the news repository. Check the logs for more details. News stories cannot be retrieved. This error is due to problems in the News repository application.

    1. Verify the Home page has been installed correctly.

    2. Verify the News repository has been installed correctly.

    3. Verify the Home page database has been installed correctly.
    CLFRQ0384E: An error occurred while creating a user with this internal ID: {0} A new Home page user cannot be created.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0385E: An error occurred during the result retrieving. An error happened when connecting to the search service to retrieve results. Ensure that the search service has been started and that nothing is blocking communication between the Home page and search services.
    CLFRQ0386E: An error occurred while initializing the icon to URL map used for the sprites in the river of news (update page). See nested exception for more details The file containing the mapping between the News stories and their corresponding icons is corrupted. This could happen if an administrator touched the file manually on the running application. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0387E: An error occurred when retrieving the descriptor for widget {0} from the in-memory cache. See nested exception for more details. See CLFRQ0323E. See CLFRQ0323E.
    CLFRQ0388E: The reference to the property file used (web.xml) for the sprite icons in the river of news is undefined. Check the value for the init parameter named {0} The web.xml file for the Home page is corrupted. This could happen if the administrator touched the file manually on the running application. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0389E: An instance of the widget descriptor in-memory caching service could not be retrieved. See nested exception for more details See CLFRQ0323E. See CLFRQ0323E.
    CLFRQ0390E: An error occurred while initializing the widget descriptor in-memory caching service with the list of available widgets. See nested exception for more details. Error during the initialization of Home page's services.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0391E: An error occurred in the security service layer while attempting to execute an operation related to the database. See nested exception for more details. A command to change the layout of a page belonging to another user was detected. It is very likely that an authenticated user tried to send a custom command over one of the AJAX servlets to modify the layout of another user. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0392E: A request to modify the information related to the widget instance {0} was received. However the current authenticated user {1} does not have ownership on this widget instance. A user is trying to modify preferences for another user. This is not a normal error, and might indicate a unauthorized use of the Home page. This is not a regular error message and might indicate a non-authorized request is being made to the Home page application. Verify the Home page has been installed correctly.
    CLFRQ0393E: A request to modify the information related to the tab instance {0} was received. However the current authenticated user {1} does not have ownership on this tab instance. A user is trying to modify preferences for another user. This is not a normal error, and might indicate a unauthorized use of the Home page. This is not a regular error message and might indicate a non-authorized request is being made to the Home page application. Verify the Home page has been installed correctly.
    CLFRQ0394E: An error occurred while fetching information from the database when checking security constraints for saving the layout information. See nested exception for more details. A command to fetch the layout of a page belonging to another user was detected. It is very likely that an authenticated user tried to send a custom command over one of the AJAX servlets to modify the layout of another user. Verify the IBM Connections Home page is installed correctly.
    CLFRQ0395E: A request to add a widget {0} to the tab instance {1} was made. However, this widget is not allowed on this tab by the administrator. Authenticated user was {2} There was an error when adding a widget to the current page. This is not a normal error, and might indicate a unauthorized use of the Home page. This is not a regular error message and might indicate a non-authorized request is being made to the Home page application. Verify the Home page has been installed correctly.
    CLFRQ0396W: An error occurred while storing descriptor for widget {0} in a batching process. See nested exception for more details. Batching processing continuing. A widget could not be stored in the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0397E: An error occurred when fetching the list of all the tab instances for the user ID {0}. Check nested exception for details. Home page preferences for a user could not be retrieved from database. Nested exception should have more detailed information about this problem.

    1. Check nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0398W: An error occurred while updating the language for a user with this information: {0},{1} Home page preferences for a user could not be saved in database. Nested exception should have more detailed information about this problem.

    1. Check if there is any nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0399E: An error occurred while deleting the widget instance with this primary key: {0} A widget instance could not be removed from the database.

    1. Verify the IBM Connections Home page is installed correctly.

    2. Verify the Home page database is available and has been installed correctly.

    3. Check the database configuration in the WebSphere Application Server installation.
    CLFRQ0400E: The search index is missing. The Search service cannot load the index.

    1. Make sure the Search is correctly installed and started.

    2. Make sure indexing has occurred.

    3. Check that you can access the Search index directory.
    CLFRQ0401E: An error occurred while invoking a remove interface (EJB). See nested exception for more details. There was a problem calling an EJB. Possibly, the News repository application is not available or not installed correctly.

    1. Verify the Home page has been installed correctly.

    2. Verify the News repository has been installed correctly.

    3. Verify the Home page database has been installed correctly.
    CLFRQ0402E: An error occurred while getting an instance to the EJB reference. There was a problem calling an EJB. Possibly, the News repository application is not available or not installed correctly.

    1. Verify the Home page has been installed correctly.

    2. Verify the News repository has been installed correctly.

    3. Verify the Home page database has been installed correctly.
    CLFRQ0403E: An error occurred while retrieving the tab UI with this name: {0} Home page information for a user could not be retrieved from database. Nested exception should have more detailed information about this problem.

    1. Check if there is a nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0404E: An error occurred while retrieving the tabs related to the user with this internal ID: {0} Home page information for a user could not be retrieved from database. Nested exception should have more detailed information about this problem.

    1. Check if there is a nested exception in server logs for more details about this problem.

    2. Verify the IBM Connections directory service is configured correctly.

    3. Check that the LDAP server for the configuration is available (if you choose to use one).

    4. Verify the Home page database has been installed correctly.
    CLFRQ0408W: The current database schema version for Homepage is {0}, but the application expects {1}. Please update the schema version to match. The schema version of the Homepage database does not match the level expected by the installed application. This could be as a result of connecting to an older database, or an issue migrating the database to the latest version.

    1. Check that the data source and credentials for the Homepage database are correct.

    2. Check for nested exceptions, or prior exceptions in the logs related to database access.

    3. Check migration logs if this is a newly migrated database.
    CLFRQ0413E: A registered pre event handler threw an exception during a Home Page transaction for the event named {0} The transaction has failed. There was an error when Home page tried to send an event to the News application.

    1. Check if there is a nested exception in the server logs for more details about this problem.

    2. Verify the messaging bus is configured correctly.
    CLFRQ0414E: An error occurred when handling a call to the service configuration API. See nested exception for full details. There was an error when getting the configuration information from the configuration files. Verify the configuration files are present and properly formatted. These files are located under the LotusConnections-Config directory for each application server.
    CLFRQ0415E: An error occurred while executing the action. See nested exception for more details. There was an error when executing an action handling an HTTP request. Verify that Home page is installed correctly and that no file in the WebSphere Application Server deployment of Home page have been compromised.
    CLFRQ0416E: A registered event handler stopped the tag {0} from being added There was an error when a user tried to add a subscription to a tag in Home page.

    1. Check if there is a nested exception in the server logs for more details about this problem.

    2. Verify the messaging bus is configured correctly.
    CLFRQ0417E: Cannot find title key '{0}' in a bundle '{1}' There was an error when locating a translated string in a resource bundle.

    1. Verify that Home page is installed correctly and that no file in the WebSphere Application Server deployment of Home page have been compromised.

    2. If you use customized resource bundles, check that the corresponding key is present.
    CLFRQ0418E: A registered event handler stopped the tag {0} from being removed There was an error when a user tried to remove a subscription to a tag in Home page.

    1. Check if there is a nested exception in the server logs for more details about this problem.

    2. Verify the messaging bus is configured correctly.
    CLFRQ0419E: A registered event handler stopped the person with ID {0} from being added There was an error when a user tried to add a subscription to a person in Home page.

    1. Check if there is a nested exception in the server logs for more details about this problem.

    2. Verify the messaging bus is configured correctly.
    CLFRQ0420E: A registered event handler stopped the person with ID {0} from being removed There was an error when a user tried to remove a subscription to a person in Home page.

    1. Check if there is a nested exception in the server logs for more details about this problem.

    2. Verify the messaging bus is configured correctly.
    CLFRQ0421I: System metrics are not available yet or the administrator has disabled them. Please contact your administrator for information. This is an informational message only. Informational message; no action is required.
    CLFRQ0422E: A registered post event handler threw an exception during a Home Page transaction for the event named {0} The transaction has failed. There was an error when Homepage tried to send an event to the News application. The event might have been sent correctly.

    1. Check if there is a nested exception in the server logs for more details about this problem.

    2. Verify the messaging bus is configured correctly.


    IBM Connections events service error messages

    Use the codes included in the error messages generated by IBM Connections to identify problems related to the events service of the Home page application and find solutions to those problems.

    The following events service error messages are generated by IBM Connections:

    Table 15. IBM Connections events service error messages

    Message Cause Solution
    CLFWY0001E: The Source field was null or empty when creating a new event record. The Source field must contain a valid value. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0005E: An attempt was made to register a null event consumer for the Source {0} This is an internal error. Contact IBM Support.
    CLFWY0006E: The Event Name field was null or empty when creating a new event record. The Event Name field must contain a value. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0007E: An invalid JSON string was provided This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0008E: The Source field value {0} is not a known, valid source. The event record cannot be created. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0009E: The ACL Feed URL field was null or empty when creating a new event record. The ACL Feed URL field must contain a value. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0011E: The Event Name field was null or empty when sending an event record for source {0}. The Event Name field must be supplied before the event is sent! This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0014E: The Container ID field was null or empty when creating a new event record. The Container ID field must contain a value. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0015E: The input set to add to was provided as null.. A valid set must be provided. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0017E: The Source field was null or empty when registering a new event record consumer. Events will not be sent to the consumer. This is an internal error. Contact IBM Support.
    CLFWY0019E: The following class could not be instantiated as an event transport: {0} but was specified as the default transport. Events cannot be propagated to the News Repository. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0020E: The following class is not a valid event transport: {0} but was specified as the default transport. Events cannot be propagated to the News Repository. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0022E: A JMS Exception occurred when consuming an event record. The event record will be retried and eventually be placed on the system exception queue if unsuccessful. An event could not be consumed from the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances. Check the configuration of JMS resources in WebSphere. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
    CLFWY0024E: JMS QueueConnectionFactory for sending the ACL event record with ID {0} from source {1} were not available. QueueConnectionFactory may not be defined. JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances. Check the IBM Connections installer log for any errors during install. Also check the IBM WebSphere Application Server JMS Resources to check if any QueueConnectionFactory objects are defined. If not, the installer failed to create them. Attempt a reinstall or contact IBM Support.
    CLFWY0025E: JMS QueueConnectionFactory for sending the event record with ID {0} from source {1} were not available. QueueConnectionFactory may not be defined. JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances. Check the IBM Connections installer log for any errors during install. Also check the WebSphere Application Server JMS Resources to check if any QueueConnectionFactory objects are defined. If not, the installer failed to create them. Attempt a reinstall or contact IBM Support.
    CLFWY0026E: A JMS exception occurred when attempting to sent the event record ID {0} from source {1}. Check the nested exception for more details. An event could not be propagated onto the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances. Check the configuration of JMS resources in WebSphere Application Server. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
    CLFWY0027E: A JMS exception occurred when attempting to sent the ACL event record ID {0} from source {1}. Check the nested exception for more details. An event could not be propagated onto the JMS queue used by the event infrastructure. This will result in news stories not displaying in Home Page in some circumstances. Check the configuration of JMS resources in WebSphere Application Server. Also check that the Service Integration Bus is configured to allow access to the user defined in the connectionsAdmin authentication alias. The nested exception provides more details.
    CLFWY0028E: An EJB instance for the Event Record Transport implementation could not be created. Check nested exception for more details. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Check the nested exception for any details, and resolve any obvious configuration issue. Contact IBM Support.
    CLFWY0029E: The EJB Home for the Event Record Transport implementation could not be looked up. Check nested exception for more details. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Check the nested exception for any details, and resolve any obvious configuration issue. Contact IBM Support.
    CLFWY0030E: An error occurred when creating a JMS message due to an invalid session. The event will not be sent. Restarting the application may resolve this issue. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. This error may happen due to temporary configuration of infrastructure reasons. Restart the application. If this error persists or requires regular restarts, contact IBM support.
    CLFWY0031E: An unexpected implementation class for an ACL event record was received. The event will not be sent. The class was {0} This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0032E: A JMS message could not be created for the event record ID {0} from source {1}. The event will not be sent. Check the nested exception for more details. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0033E: An unexpected implementation class for an event record was received. The event will not be sent. The class was {0} This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0037E: An error occurred while fetching the News Repository EJB. Check the logs for more details. The News Repository EJB could not be looked up. This will result in news stories not displaying on the Home Page Updates page. The nested exception will contain exact details of the error. Refer to the error message for the nested exception.
    CLFWY0038E: Impossible to get the bootstrap and port information for the remote EJB from LotusConnections-Config.xml The LotusConnections-config.xml file could not be read to obtain the bootstrapHost and bootstrapPort values for the News service. Validate that LotusConnections-config.xml is correct and that the bootstrapHost defined for the News service points to the application server running News, and that the bootstrapPort points to the correct Bootstrap Port for that server. Fix the file and restart the application.
    CLFWY0039E: The JMS QueueConnectionFactory or Queue could not be looked up. Check the QCF and Queue is defined in WebSphere and bound to the application. Check the nested exception for more details. JMS resources required by the event infrastructure could not be looked up. This will result in news stories not displaying in Home Page in some circumstances. Check the IBM Connections installer log for any errors during install. Also check the WebSphere Application Server JMS Resources to check if any QueueConnectionFactory and Queue objects are defined. If not, the installer failed to create them. Attempt a reinstall or contact IBM Support.
    LFWY0056E: The scheduled task service mbean needed to run tasks is not registered for application ''{0}''. Verify that the component is running. If it is there is an internal error. Call IBM Customer Support in this case.    
    CLFWY0057E: The task named ''{0}'' is not one of the configured tasks. Possibly a task name accidently was changed in the component configuration file. If not, Call IBM Customer Support. The task you specified cannot be found. Determine whether a task name was changed in the application's configuration file. If that is not the cause, contact IBM support.
    LFWY0058E: Update task for task ''{0}'' failed to complete successfully. Internal error: The calendar period is invalid. Call IBM Customer Support. The calendar period is invalid. Determine whether a calendar period is defined correctly in the application's configuration file. If that is not the cause, contact IBM support.
    CLFWY0059E: Update task for task ''{0}'' failed to complete successfully. Internal error: The scheduler is not available. Call IBM Customer Support. The scheduler is not available. Try restarting Websphere Application Server. If this fails, contact IBM support.
    CLFWY0060E: Update task for task ''{0}'' failed to complete successfully. Internal error: The notification sink is invalid. Call IBM Customer Support.    
    CLFWY0061E: Local task ''{0}'' failed to start on the cluster servers for reason given above.    
    CLFWY0062E: Create task for task ''{0}'' failed to complete successfully. Internal error: A notification exception occurred. Call IBM Customer Support.    
    CLFWY0063E: Remove task for task ''{0}'' failed to complete successfully. Internal error: A JNDI naming exception occurred. Call IBM Customer Support.    
    CLFWY0064E: Remove task for task ''{0}'' failed to complete successfully. Internal error: The scheduler is not available. Call IBM Customer Support. The scheduler is not available. Try restarting Websphere Application Server. If this fails, contact IBM support.
    CLFWY0065E: Task ''{0}'' failed to start or complete normally. Possibly the task class is incorrect. Inspect the task configuration settings.    
    CLFWY0066E: Remove task for task ''{0}'' failed to complete successfully. Internal error: the created task is not valid. Call IBM Customer Support.    
    CLFWY0067E: An error occurred while calling remote method for task {0}. Internal error. Call IBM Customer Support.    
    CLFWY0068E: Create task for task ''{0}'' failed to complete successfully. Internal error: the created task is not valid. Verify the task configuration settings, and then call IBM Customer Support.   Verify the task configuration settings, and then contact IBM support.
    CLFWY0069E: Internal error: The default user calendar is not valid. Call IBM Customer Support.   Contact IBM support.
    CLFWY0070E: Create task for task ''{0}'' failed to complete successfully. Internal error: The calendar specifier is invalid. Call IBM Customer Support. The calendar specifier is invalid. Determine whether a calendar specifier is defined correctly in the application's configuration file. If that is not the cause, contact IBM support.
    CLFWY0071E: The task {0} is not valid and cannot be accessed. Internal error. Call IBM Customer Support.    
    CLFWY0072E: The local scheduled task ''{0}'' failed to start due to failure to get the connectionsAdmin alias or password. Check the Connections Admin alias''s. If they are ok this is an internal error; call IBM Customer Support.    
    CLFWY0073E: Create task for task ''{0}'' failed to complete successfully. Internal error: The notification sink is invalid. Call IBM Customer Support.    
    CLFWY0075E: Error loading scheduler settings for component with config id {0}. Call IBM Customer Support. Please check the validity of your IBM Connections installation configuration files. Then call IBM Customer Support.    
    CLFWY0076E: Task configuration is not available for task ''{0}''. The application may not have started properly. Try restarting the application. If this fails, call IBM Customer Support.    
    CLFWY0077E: The local scheduled task ''{0}'' failed to start due to failure to get the deployment manager admin client. Verify the dmgr is started.    
    CLFWY0078E: The local scheduled task ''{0}'' failed to start due to failure to get the deployment manager node name. Internal error. Call IBM Customer Support.    
    CLFWY0079E: Internal error: A JNDI naming exception was caught. {0} Call IBM Customer Support.    
    CLFWY0080E: Create task for task ''{0}'' failed to complete successfully. Internal error: A JNDI naming exception occurred. Call IBM Customer Support.   Contact IBM support.
    CLFWY0081E: Internal error: The calendar specifier is not valid. Call IBM Customer Support. The calendar specifier is invalid. Determine whether a calendar specifier is defined correctly in the application's configuration file. If that is not the cause, contact IBM support.
    CLFWY0082E: Update task for task ''{0}'' failed to complete successfully. The task is pending. Try again later. The task is pending. Try again later.
    CLFWY0083E: The local scheduled task ''{0}'' failed to start due to failure to get the deployment manager host name or SOAP port. Internal error. Call IBM Customer Support.    
    CLFWY0084E: Internal error: The Notification Sink object failed to fire. Call IBM Customer Support.   Contact IBM support.
    CLFWY0085E: Update task for task ''{0}'' failed to complete successfully. Internal error: A notification exception occurred. Call IBM Customer Support.    
    CLFWY0086E: Create task for task ''{0}'' failed to complete successfully. Internal error: The calendar is invalid. Call IBM Customer Support. The calendar is invalid. Determine whether a calendar is defined correctly in the application's configuration file. If that is not the cause, contact IBM support.
    CLFWY0087E: Update task for task ''{0}'' failed to complete successfully. Internal error: A JNDI naming exception occurred. Call IBM Customer Support.   Contact IBM support.
    CLFWY0088E: Create task for task ''{0}'' failed to complete successfully. Internal error: A remote exception occurred. Call IBM Customer Support.    
    CLFWY0089E: The local scheduled task ''{0}'' failed to start due to failure to get the connectionsAdmin alias or password, or the deployment manager host name or SOAP port. Internal error. Call IBM Customer Support.    
    CLFWY0091E: Update task for task ''{0}'' failed to complete successfully. Internal error: The calendar specifier is invalid. Call IBM Customer Support. The calendar specifier is invalid. Determine whether a calendar specifier is defined correctly in the application's configuration file. If that is not the cause, contact IBM support.
    CLFWY0092E: For task {0}, the specified ''interval='' attribute is not a valid ''cron'' schedule. Correct the cron string. An invalid value is being used as the cron string for the interval attribute. Correct the syntax of the cron string.
    CLFWY0093E: The IBM Connections component for task ''{0}'' scheduler is not available. The component appears to be stopped. The application is not available. Make sure the application is started. If not, start it. If that is not the cause, contact IBM support.
    CLFWY0094E: Create task for task ''{0}'' failed to complete successfully. Internal error: the created TaskInfo object is not valid. Verify the task configuration settings, and then call IBM Customer Support. The TaskInfo object is invalid. Verify the task configuration settings, and then contact IBM support.
    CLFWY0095E: The task named ''{0}'' with an unknown type of ''{1}'' has fired, and is being ignored. Inspect the task configuration settings. You might have inadvertently changes the task type in the configuration file. Correct the configuration settings.
    CLFWY0096E: Internal error: The scheduled tasks will not fire. Call IBM Customer Support.    
    CLFWY0097E: Remove task for task ''{0}'' failed to complete successfully. The task is pending. Try again later. The task is pending. Try again later.
    CLFWY0098E: The task {0} is already pending. The task you are trying to schedule is already scheduled. No further action is required.
    CLFWY0099E: The local scheduled task ''{0}'' failed to start, could not invoke mbean on remote server in cluster. Internal error. Call IBM Customer Support.    
    CLFWY0101E: Internal error: This is probably due to a deployment error. Call IBM Customer Support.    
    CLFWY0102E: Remove task for task ''{0}'' failed to complete successfully. Internal error: A notification exception occurred. Call IBM Customer Support.    
    CLFWY0103E: The local scheduled task ''{0}'' failed to start due to failure to get the list of remote servers. Internal error. Call IBM Customer Support.    
    CLFWY0104E: Update task for task ''{0}'' failed to complete successfully. Internal error: A remote exception occurred. Call IBM Customer Support.    
    CLFWY0105E: Update task for task ''{0}'' failed to complete successfully. Internal error: The calendar is invalid. Call IBM Customer Support. The calendar is invalid. Determine whether a calendar is defined correctly in the application's configuration file. If that is not the cause, contact IBM support.
    CLFWY0106E: Update task for task ''{0}'' failed to complete successfully. The created task is not valid. Verify the task configuration settings, and then call IBM Customer Support. The created task is not valid. Verify the task configuration settings, and then contact IBM support.
    CLFWY0107E: Create task for task ''{0}'' failed to complete successfully. Internal error: The calendar period is invalid. Call IBM Customer Support. The calendar period is invalid. Determine whether a calendar period is defined correctly in the application's configuration file. If that is not the cause, contact IBM support.
    CLFWY0108E: Create task for task ''{0}'' failed to complete successfully. Internal error: The scheduler is not available. Call IBM Customer Support. The scheduler is not available. Try restarting Websphere Application Server. If this fails, contact IBM support.
    CLFWY0109E: Task ''{0}'' failed to start. The Mbean name is ''{1}''. Possibly the task mbean or method name (''{2}'') argument is incorrect.    
    CLFWY0110E: Internal error: The scheduler is not available. Try restarting Websphere. If this fails, call IBM Customer Support. The scheduler is not available. Try restarting Websphere Application Server. If this fails, contact IBM support.
    CLFWY0112E: Internal Error: The specified notification sink class is not valid. Call IBM Customer Support.    
    CLFWY0113E: Internal error: JNDI naming exception caught. Connections component has been incorrectly deployed. Call IBM Customer Support The application was incorrectly deployed. Contact IBM support.
    CLFWY0135E: The default event enable implementation class {0} does not implement the EventEnable interface Internal error. Events may not be generated and the IBM Connections Home Page Updates page may be empty as a result. Contact IBM support.
    CLFWY0136E: Could not instantiate an instance of the default event enable class {0} Internal error. Events may not be generated and the IBM Connections Home Page Updates page may be empty as a result. Contact IBM support.
    CLFWY0138E: The source, type, scope and name of an event must always be set. This is an internal error. This will result in news stories not displaying in Home Page in some circumstances. Contact IBM Support.
    CLFWY0140E: The following class is not a valid async event invoker: {0} but was specified as the default invoker. Events cannot be propagated asynchronously. Internal error. Events may not be generated and the IBM Connections Home Page Updates page may be empty as a result. Contact IBM support.
    CLFWY0141E: The following class could not be instantiated as an async event invoker: {0} but was specified as the default transport. Events cannot be propagated asynchronously. Internal error. Events may not be generated and the IBM Connections Home Page Updates page may be empty as a result. Contact IBM support.
    CLFWY0143E: An exception occurred when trying to send the event {0} with ID {1} asynchronously. No asynchronous event consumers will receive this event. Check nested exception for more details. An asynchronous event could not be sent. This will result in data not appearing in the IBM Connections Home Page Updates page, or being available to third party event consumers. Check the nested exception for more details. Check that a CLFWX0186I message is generated when the News application starts up. Contact IBM support.
    CLFWY0144E: An invalid JSON string was provided: {0} Internal error. As a result of this error, an event cannot be sent. Contact IBM support.
    CLFWY0145E: The input set to add to was provided as null.. A valid set must be provided. Internal error. As a result of this error, an event cannot be sent. Contact IBM support.
    CLFWY0146E: An EJB instance for the event implementation could not be created. Check nested exception for more details. Internal error. Events may not be sent. Restart the application. If the problem persists, contact IBM support.
    CLFWY0147E: The EJB Home for the event implementation could not be looked up. Check nested exception for more details. Internal error. Events may not be sent. Restart the application. If the problem persists, contact IBM support.
    CLFWY0148E: Could not obtain an event connection Internal error. Events may not be sent. Restart the application. If the problem persists, contact IBM support.
    CLFWY0149E: An outgoing event due to be consumed by News could not be augmented. It will not be consumed by News. An event could not be augmented for delivery to the News application. This is an internal error. Contact IBM support.
    CLFWY0150E: Could not obtain the event topic connection factory Internal error. Events may not be sent. Check the IBM Connections install log for any errors. Check the nested exception for any errors, then contact IBM support.
    CLFWY0151E: A JMS Exception occurred when publishing an event with ID {0} to topic {1} Internal error. Events may not be sent. If the exception only happens once, it could be a temporary connectivity issue. Otherwise restart the application. If the problem persists, contact IBM support.
    CLFWY0152E: An outgoing event due to be consumed by Communities could not be augmented. It will not be consumed by Communities. An event could not be augmented for delivery to the Communities application. This is an internal error. Contact IBM support.
    CLFWY0153E: Could not create a JMS MapMessage Internal error. Events may not be sent. Contact IBM support.
    CLFWY0154E: The Map object does not contain all mandatory event data: ID, Timestamp, Source, Type, Scope, Name Internal error. As a result of this error, an event cannot be sent. Contact IBM support.
    CLFWY0155E: The Map object provided is not an event map, or is not the correct version. Internal error. As a result of this error, an event cannot be sent. Contact IBM support.
    CLFWY0156E: The events-config.xml configuration appears not to be an XML configuration file. The events-config.xml configuration file is not a valid XML file. This means that registered event handlers will not be invoked. Examine the events-config.xml file and fix any errors.
    CLFWY0159E: events-config.xml failed validation. Check the file and correct any XML errors. The events-config.xml file contains invalid XML that does not match the schema in events-config.xsd. This means that registered event handlers will not be invoked. Examine the events-config.xml file and fix any errors.
    CLFWY0161E: An exception occurred when trying to load events-config.xml. Event handlers will not be run. The events-config.xml configuration file could not be loaded. This means that registered event handlers will not be invoked. Examine any nested exception for the cause. Ensure the events-config.xml file exists in the LotusConnections-config directory and fix any errors.
    CLFWY0170E: An exception occurred when invoking the event handler named: {0} with the event: {1} The named event handler could not be invoked for the named event. Check the nested exception for more details and resolve any errors.
    CLFWY0171E: Could not load event handler configuration. Registered event handlers will not run. Check nested exception for more details. The event handler configuration could not be loaded. This means that registered event handlers will not be invoked. Examine the nested exception for the cause and resolve any problems.
    CLFWY0172E: The event handler named {0} could not be created because the handler class {1} could not be instantiated. The handler will not run. The class for the named event handler could not be instantiated. This handler will not be run. Examine any nested exception for more details. Ensure the handler class provides a default public constructor.
    CLFWY0173E: Could not set the property named {1} on handler {0}. The property value may not be mappable to the property type. This handler may not initialize correctly. The named property of the named event handler could not be set. This may cause the handler to fail to initialize. Check the handler definition in events-config.xml and check that the defined properties match the properties of the handler class exactly.
    CLFWY0174E: The event handler named {0} could not be created because the handler class {1} could not be loaded. The handler will not run. The class for the named event handler could not be loaded. This handler will not be run. Ensure the event handler Jar is defined in a shared library, and that the shared library is referenced by all IBM Connections applications in the WebSphere Application Server administrative console.
    CLFWY0175E: The event handler named {0} could not be created because the handler class {1} could not be accessed. The handler will not run. The class for the named event handler could not be accessed. This handler will not be run. Examine any nested exception for more details and resolve any problems.
    CLFWY0176E: The event handler named {0} did not initialize correctly. Check the handler configuration in events-config.xml. The handler will not run. The named event handler failed to initialize correctly. This handler will not be run. Examine any nested exception for more details. Check that all required properties of the handler are defined in events-config.xml.
    CLFWY0177E: The event handler named {0} is not a valid event handler class: {1} The handler will not run. The named event handler is implemented by a class which is not a valid event handler class. This handler will not be run. Examine the configuration of the event handler in events-config.xml and inspect the source of the event handler class to ensure it correctly implements the Event SPI.
    CLFWY0178E: An outgoing command due to be consumed by other applications could not be augmented. It may not be consumed by other applications. A platform command event could not be augmented for delivery to command consumers. This is an internal error. Contact IBM support.
    CLFWY0179E: Could not load the set of event names to be consumed by river of news. Events may not display in the river of news. The set of events that need to be consumed by the News application could not be loaded. This will result in no events being sent to News, and the IBM Connections Home Page Updates page will be empty as a result. If you have made any customization changes to the JAR file lc.events.internal.jar then revert these changes, otherwise contact IBM support.
    CLFWY0183E: The invocation of the asynchronous event point for the event named {0} with ID {1} failed. The event was not sent. An asynchronous event could not be sent. This will result in data not appearing in the IBM Connections Home Page Updates page, or being available to third-party event consumers. Check the nested exception for more details. Check that a CLFWX0186I message is generated when the News application starts up. Contact IBM support.
    CLFWY0185E: A null internal event subscriber object was supplied. Internal error. Contact IBM support.
    CLFWY0187E: The invocation of the synchronous post-commit event point for the event named {0} with ID {1} failed. The event was not sent. A synchronous event could not be sent. Check the nested exception for more details. Contact IBM support.
    CLFWY0188E: The invocation of the synchronous pre-commit event point for the event named {0} with ID {1} failed. The event was not sent. A synchronous event could not be sent. Check the nested exception for more details. Contact IBM support.
    CLFWY0190E: A JMS exception occurred when consuming an event in an internal consumer. Check nested exception for more details. Internal error. An event cannot be consumed. If the exception only happens once, it could be a temporary connectivity issue. Otherwise restart the application. If the problem persists, contact IBM support.
    CLFWY0192E: task config error, task name is the empty string. Task is skipped. Inspect the task config.    
    CLFWY0193E: task config error, for task name ''{0}'' mbean method name cannot be empty due to type. Task is skipped. Inspect the task config.    
    CLFWY0194E: task config error, for task name ''{0}'' task type not valid. Task is skipped. Inspect the task config.    
    CLFWY0195E: task config error, task name ({0}) enabled not true or false. Task is skipped. Inspect the task config.    
    CLFWY0196E: task config error, for task name ''{0}'' startby cannot contain punctuation characters. Task is skipped. Inspect the task config.    
    CLFWY0197E: task config error, task name ({0}) defined more than once. Duplicates skipped. Task is skipped. Inspect the task config.    
    CLFWY0198E: task config error, for task name ''{0}'' scope value not valid. Task is skipped. Inspect the task config.    
    CLFWY0199E: task config error, for task name ''{0}'' interval cannot contain punctuation characters. Task is skipped. Inspect the task config.    
    CLFWY0200E: task config error, task config is out of date. Task is skipped. Inspect the task config.    
    CLFWY0201E: task config error, task name ({0}) cannot contain punctuation characters. Task is skipped. Inspect the task config.    
    CLFWY0202E: The event handler named {0} threw an exception when handling an event. Check nested exception for more details. The named event handler threw an exception when handling an event. Examine any nested exception for more details. Check any logs that the event handler keeps.
    CLFWY0203E: The event handler named {0} encountered an initialization exception and will not receive events. It may be mis-configured. Check nested exception for more details. The named event handler failed to initialize correctly. This handler will not be run. Examine any nested exception for more details. Check that all required properties of the handler are defined in events-config.xml.
    CLFWY0204E: Error when lookup with asynchronous event handler work manager. Check nested exception for more details. Could not look up the asynchronous event handler work manager in the News application. Asynchronous event handlers may not work. Check the nested exception for more details and check the IBM Connections install log for any errors when installing the News application.
    CLFWY0205E: Error creating asynchronous subscriber for event handler named {0} and subscription {1}. This handler will not receive events. Could not register a subscription for the named asynchronous event handler. This handler may not receive all events it expects to. Check the subscription defined for the handler in events-config.xml and correct any issue.
    CLFWY0206E: Error when reading event handler configuration in events-config.xml whilst creating asynchronous event handlers. Check nested exception for more information. Could not configure an asynchronous event handler due to a configuration issue in events-config.xml. Check the nested exception for more details. Check events-config.xml and correct any issues.
    CLFWY0222E: An outgoing news cleanup event could not be augmented. A deletion event could not be augmented for delivery. Any existing updates for the item the event represents will not be removed from the IBM Connections Home Page Updates page. This is an internal error. Contact IBM support.
    CLFWY0233E: The event handler named {0} encountered an unexpected exception when handling an event. Check nested exception for more details. The named event handler threw an unexpected exception when handling an event. Examine any nested exception for more details. Check any logs that the event handler keeps.
    CLFWY0234E: Cannot build a path to the filesystem using a base location: {0} and relative path: {1} Internal error. A path location in an event cannot be resolved to an absolute path. Event consumers may not work correctly if they depend on this. Check the base location in the error message and then check the value of the corresponding WebSphere Application Server variable.
    CLFWY0235E: A deferred event with ID {0} could not be retrieved. This event will not be sent. Internal error. Events may not be sent. Contact IBM support.
    CLFWY0236E: A deferred event is not of type MapMessage. Internal error. Events may not be sent. Contact IBM support.
    CLFWY0237E: A JMS exception occurred when processing deferred event with ID {0}. This event will not be sent. Check nested exception for more details. Internal error. Events may not be sent. If the exception only happens once, it could be a temporary connectivity issue. Otherwise restart the application. If the problem persists, contact IBM support.
    CLFWY0238E: A JMS Exception occurred when publishing a deferred event with ID {0} to temporary topic {1} Internal error. Events may not be sent. If the exception only happens once, it could be a temporary connectivity issue. Otherwise restart the application. If the problem persists, contact IBM support.
    CLFWY0267E: An outgoing notification event could not be augmented. The notification may not be successful. A notification event could not be augmented for delivery. This notification will not be processed and recipients will not get emails. This is an internal error. Contact IBM support.
    CLFWY####E: Could not load event content store location for feature {0}. Check events-config.xml for errors. Internal error. Could not retrieve the base file system location of the content store for the named application. Check the definition of the base location variable in events-config.xml and then check that the corresponding WebSphere Application Server variable has a valid value.


    IBM Connections notification and ReplyTo error messages

    Use the codes included in the error messages generated by IBM Connections to identify problems related to the notification and ReplyTo services of the Home page application, and find solutions to those problems.

    The following notifications error messages are generated by IBM Connections:

    Table 16. IBM Connections notifications error messages

    Message Cause Solution
    CLFRR0002E: An error occurred when creating the channel handler for channel {1}. The channel handler class {0} could not be loaded. The channel handler class defined for the named notification channel defined in notification-config.xml cannot be loaded. The default handler classes for the event and email channels should not be modified unless directed by IBM Support. Validate that the notification-config.xml properties element contains a property with name corresponding to the channel specified in the message, that the value is a valid class and that the class is loadable.
    CLFRR0006E: Notification delivery failed as the channel handler for channel {0} could not be found. Check that the channel handler class is defined in notification-config.xml There is no channel handler class defined for the named notification channel defined in notification-config.xml The default handler classes for the event and email property should not be modified unless directed by IBM Support. Validate that the notification-config.xml properties element contains a property with name corresponding to the channel specified in the message, that the value is a valid class and that the class is loadable.
    CLFRR0007E: An error occurred during the initialization of the JavaMail session. Check that a JavaMail session with the JNDI name mail/notification is defined. The IBM WebSphere Application Server Mail Session object could not be looked up. Check the WebSphere Application Server configuration and define a mail session object if one is not defined, following instructions in the topic, Sending mail from a dedicated mail server.
    CLFRR0008E: An error occurred when delivering an email notification via SMTP. Notification will not be recieved by recipients. The configured SMTP server returned an error when an email was sent to it for delivery. Check the nested exception from the SMTP server for details about the exact error. Resolve the issue and try again.
    CLFRR0010E: The email configuration could not be loaded. The notification-config.xml file may be missing. Email delivery of notifications will fail. The email configuration could not be read from notification-config.xml. Check that there is a valid emailChannelConfig element defined in notification-config.xml that defines one of either: useJavaMailProvider or smtpJNDILookup
    CLFRR0011E: The notification has no sender defined and will not be sent. A notification was attempted to be sent, but no sender was specified and therefore no notification sent This is an abnormal situation. Contact IBM Support.
    CLFRR0012E: The notification has no recipients defined and will not be sent. A notification was attempted to be sent, but no recipients were specified and therefore no notification sent Check if the sender intended or expected to send this notification to specific recipients.
    CLFRR0013E: Could not connect to any of the available SMTP servers. Notification will not be recieved by recipients. None of the SMTP servers from a DNS MX record lookup could be contacted. Validate that the MX record lookup is correct and expected to return valid SMTP servers. This problem may be intermittent of due to a network issue.
    CLFRR0014E: An error occurred when obtaining the SMTP server list from the DNS lookup: {0}. No SMTP servers were found and notifications will not be sent. Please check that the DNS lookup is correct. No SMTP servers were returned from the specified DNS MX record lookup. Reconfigure notification-config.xml to use a DNS MX record lookup that will return at least one valid SMTP server and then restart the application.
    CLFRR0016E: An error occurred when trying to locate SMTP servers in DNS. Email delivery of notifications will fail. The lookup of DNS MX records could not be made. Validate that the DNS MX lookup URL defined in notification-config.xml is valid. If not, modify the URL and restart the application.
    CLFRR0017E: An error occurred during a search for MX records in the DNS lookup table. It is not possible to retrieve the MX records for the DNS lookup: {0}. Please check that the DNS lookup is correct. The lookup of DNS MX records did not return any MX records. Validate that the DNS MX lookup URL defined in notification-config.xml is valid. If not, modify the URL and restart the application.
    CLFRR0018E: The reply to email address: {0} could not be parsed. Notification will not be sent. The reply to address defined for the notification is not a valid email address according to RFC2882. The reply to address may be a user email obtained from the LDAP directory, or a sender address defined in notification-config.xml Identify the sender and validate that their email address is correct.
    CLFRR0019E: Could not locate any available SMTP servers. Notification will not be received by recipients. No SMTP servers were returned from the specified DNS MX record lookup. Reconfigure notification-config.xml to use a DNS MX record lookup that will return at least one valid SMTP server and then restart the application.
    CLFRR0021E: The notification has no body defined and will not be sent. An empty notification message was attempted to be sent. This is only possible if the template for an existing notification has been modified incorrectly. Validate that any template modifications are valid.
    CLFRR0022E: It is not possible send a null notification message. An empty notification message was attempted to be sent. This is only possible if the template for an existing notification has been modified incorrectly. Validate that any template modifications are valid.
    CLFRR0024E: The sender email address: {0} could not be parsed. Notification will not be sent. The sender address defined for the notification is not a valid email address according to RFC2882. The sender address may be a user email obtained from LDAP, or a sender address defined in notification-config.xml Identify the sender and validate that their email address is correct.
    CLFRR0027E: Error loading notification-config.xml file. Check that the file exists. The notification-config.xml file could not be loaded because the file was not found, or the contents of the file were not valid. Validate that a notification-config.xml file exists in the LotusConnections-config directory, and check that the contents of the file are valid according to the schema. The nested exception will contain more details. Fix the file and restart the application.
    CLFRR0029E: The handler configuration in notification-config.xml is invalid. Check the configuration. The contents of the handler element in notification-config.xml are not valid. Inspect the handler element and validate that the contents are correct according to the schema. Fix the file and restart the application.
    CLFRR0030E: An error occurred during email channel configuration. Please check the email channel configuration in notification-config.xml. Only one of useJavaMailProvider or smtpJNDILookupURL should be defined. The emailChannelConfig section of notification-config.xml is incorrectly defined. Check that only one of the useJavaMailProvider and smtpJNDILookupURL elements are defined. Fix the file and restart the application.
    CLFRR0031E: Error instantiating notification configuration provider {0} This is an internal error. Contact IBM support.
    CLFRR0032E: The template configuration in notification-config.xml is invalid. Check the configuration. The contents of the templates element in notification-config.xml are not valid. Inspect the templates element and validate that the contents are correct according to the schema. Fix the file and restart the application.
    CLFRR0033E: An error occurred during the loading of the configuration properties at {0} The properties element of notification-config.xml is not valid. It is likely that a defined property has a name but no value. Inspect the properties element and validate that the contents are correct according to the schema. Fix the file and restart the application.
    CLFRR0034E: An error occurred when retrieving the sender email address for the notification. Source: {0}, Type: {1}, Channel: {2} The notification-config.xml file does not contain a valid top-level config element. Inspect and fix the notification-config.xml then restart the application.
    CLFRR0035E: Error setting the authentication properties for the SMTP server. One of either <authentry> or the <user> and <password> elements should be specified. The smtpJNDILookup element in notification-config.xml contains both an authEntry as well as user and password elements. Either an authEntry element specifying a J2C Authentication Alias should be defined, or user and password elements should be defined, but not both. Fix the notification-config.xml file and restart the application.
    CLFRR0036E: Cannot find config variable directory {0}. The location of notification-config.xml is not valid when trying to load the file. Contact IBM Support.
    CLFRR0037E: Error setting the java mail properties An error was encountered when trying to read the contents of the javamail element in notification-config.xml. The nested exception will contain exact details of the error. Fix the javamail section in notification-config.xml and restart the application.
    CLFRR0038E: Error getting server URL for {0}. A URL for the named service could not be retrieved from LotusConnections-config.xml. Validate the service entry for the named service in LotusConnections-config.xml. Fix any issue and restart the application.
    CLFRR0039E: Error loading config variables from {0}. The notification-config.xml file could not be loaded because the file was not found at the location specified. Validate that a notification-config.xml file exists in the specified location. The nested exception will contain more details. Fix the file and restart the application.
    CLFRR0042E: Cannot find {0} for config variables. The notification-config.xml file could not be loaded because the file was not found at the location specified, or it is not a valid file. Validate that a notification-config.xml file exists in the specified location. The nested exception will contain more details. Fix the file and restart the application.
    CLFRR0043E: Invalid notification-config.xml file. Check the XML format and ensure that all required settings are complete. The notification-config.xml file does not pass schema validation. Check that any modifications to notification-config.xml do not violate the schema in notification-config.xsd. Use an XML parsing tool to validate the file. Fix the file and restart the application.
    CLFRR0046E: Either notifications are globally disabled, or notifications are disabled for the notification source: {0}. An attempt was made to send a notification when either notifications are globally disabled, or notifications for the application are disabled. If you believe that notifications should be enabled for this application, check notification-config.xml and ensure that the enabled attribute of the config element is true, and that the enabled attribute of the source element for the application is true. If either of these is false and you see this error message, then contact IBM Support as notifications should not be sent in this situation.
    CLFRR0047E: Could not retrieve the community group with id {0} and community name {1} The membership of the named community with the named ID could not be retrieved. Members of this community will likely not receive this notification. Check that the community exists and is valid. Also validate that the Community Directory Service extension is enabled in LotusConnections-config.xml.
    CLFRR0048E: Could not retrieve members for LDAP group: {0} The membership of the named LDAP group could not be retrieved. Members of this group will likely not receive this notification. Check that the LDAP group exists and is valid. Also validate that WebSphere Application Server Virtual Member Manager is correctly configured to retrieve group information from your LDAP server.
    CLFRR0049E: Could not retrieve the LDAP group with id: {0} and group name: {1} The LDAP group definition could not be retrieved. Members of this group will likely not receive this notification. Check that the LDAP group exists and is valid. Also validate that WebSphere Application Server Virtual Member Manager is correctly configured to retrieve group information from your LDAP server.