Activities error messages
Use the codes included in the error messages generated by HCL Connections™ to identify and correct problems with the Activities application.
| 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 that the directory and file information is correct. |
| CLFRA0014E: unable to create file upload directory <directoryName>. | The directory given in oa-config.xml for the element property name "root.directory" either could not be found or created. This directory is used for file uploads to the Activities content store. | Check that the directory exists; create it if it does not exist. |
| CLFRA0015E: error encountered deleting content: <directoryName> <fileName>. | An error occurred while deleting the contents of a file from the Activities content store. Additional information relating to the failure may be found in the SystemOut.log file. | Verify that the directory and file information is correct. |
| CLFRA0016E: unable to upload file: <directoryName> <fileName>. | An error occurred while retrieving or uploading a file to the Activities content store. Additional information relating to the failure may be found in the SystemOut.log file. | Verify that the directory and file information is correct. |
| CLFRA0017E: Error closing statistics file. | A file system error occurred closing one of the files used for Activities statistics persistence. | Verify that the file system directory containing the statistics files is writable and has available space. |
| CLFRA0019E: Error creating statistics file. | A file system error occurred creating one of the files used for Activities statistics persistence. | Verify that the file system directory containing the statistics files is writable and has available space. |
| CLFRA0020E: Error parsing statistics file. | The format of one of the files used for Activities statistics persistence is inconsistent with the expected format. | Remove the existing files in the file system directory containing the statistics files. |
| CLFRA0021E: Activities statistics persistence cannot create directory <directory>. | A file system error occurred creating the file system directory <directory> for containing the Activities statistics files. | Verify that the server level 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 that the file system directory containing the statistics files is writable and has available space. |
| CLFRA0023E: Error saving summary information. | A file system error occurred saving data one of the files used for Activities statistics persistence. | Verify that the file system directory containing the statistics files is writable and has available space. |
| CLFRA0026E: Error fetching profiles. | The MemberService wsadmin object received an exception executing a fetchMembers command. | Verify that the parameter to the fetchMembers command is valid. Additional information relating to the failure may be found in the SystemOut.log file. |
| CLFRA0027E: Error deleting profile | ||
| CLFRA0028E: Error updating access control list. | The AccessControlService wsadmin object received an exception executing an access modification command. | Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file. |
| CLFRA0029E: Error fetching activities. | The ActivityService wsadmin object received an exception executing a command to fetch Activities. | Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file. |
| CLFRA0030E: Error fetching access control list. | The AccessControlService wsadmin object received an exception executing a fetchAccess command. | Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file. |
| CLFRA0031E: Error locating Scheduler. cannot create Scheduler MBean. | ||
| CLFRA0032E: Error updating profile. | The MemberService wsadmin object received an exception executing a updateMember command. | Verify that the parameter to the updateMember command is valid. Additional information relating to the failure may be found in the SystemOut.log file. |
| CLFRA0033E: Error purging trash. | The TrashCollectionService wsadmin object received an exception executing a purgeTrash command. | Verify that the parameter to the purgeTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file. |
| CLFRA0034E: Error fetching trash. | The TrashCollectionService wsadmin object received an exception executing a fetchTrash command. | Verify that the parameter to the fetchTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file. |
| CLFRA0035E: Error undeleting trash. | The TrashCollectionService wsadmin object received an exception executing a undeleteTrash command. | Verify that the parameter to the undeleteTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file. |
| CLFRA0036E: Error locating MBeanServer, no Activity Administration MBeans registered. | An exception was generated when Activities tried to locate MBean server needed to register the Activities Administration MBeans. | Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file. |
| 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 that the <objectStore> configuration information in oa-config.xml is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident. |
| CLFRA0071E: {0} DaoException while updating node content ref uuid=<uuid>. | An error occurred while updating the content of the specified activity. | Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process. |
| CLFRA0072E: activities object store did not start: <className>. | The Activities Object Store service implemented by <className> did not start. Additional information relating to the failure may be found in the SystemOut.log file. | Verify that the <objectStore> configuration information in oa-config.xml is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident. |
| CLFRA0073E: {0} Destination ObjectStore ID="<id>" not found in ObjectStore registry. Double-check the oa-config.xml file. | An error occurred while transferring Activities content from one content store to another. The requested destination object store identifier was not found. | Check the spelling of the ID used and compare it with the available object stores listed in the oa-config.xml file. |
| CLFRA0074E: ObjectStoreFilter error during activities object store content filtering "<error>". | An error occurred while processing Activities content. Additional information relating to the failure may be found in the SystemOut.log file. | Depending on the additional error information given, it may be possible to correct the data and re-process it. |
| CLFRA0075E: Premature invocation before transfer is complete. Check busy() method or listen for completion event. | An error occurred while transferring Activities content from one content store to another. The transfer utility may already be carrying out a transfer. | Attempt this operation after the other transfer is complete. |
| CLFRA0076E: <error> Exception while retrieving activities collection. | An error occurred while transferring Activities content from one content store to another. | Check that the content stores are available and accessible. |
| CLFRA0077E: ObjectStoreConfigLoader: the class "<className>" could not be instantiated. | An error occurred while processing the Activities content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. | Verify that the <objectStore> configuration information in oa-config.xml is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident. |
| CLFRA0078E: Source ObjectStore ID="<id>" not found in ObjectStore registry. Double-check the oa-config.xml file. | An error occurred while transferring Activities content from one content store to another. The requested source object store identifier was not found. | Check the spelling of the ID used and compare it with the available object stores listed in the oa-config.xml file. |
| CLFRA0079E: {0} error initializing adapter: classname= "{1}" Double-check the config settings for this specific adapter for correct/valid values. | An error occurred while processing the Activities content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. | Verify that the configuration information for the object store is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident. |
| CLFRA0080E: ObjectStoreConfigLoader: missing id for activities object store class "<className>". | An error occurred while loading the Activities content store configuration. | Verify that the configuration information for the object store is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident. |
| CLFRA0081E: EventBrokerConfigLoader: the class "<className>" was not found. Check the configuration file, under the class attribute of the service for the correct Java classname. Or, check the classpath to make sure the class is visible. | An error occurred while processing the Activities content store configuration. Additional information relating to the failure may be found in the SystemOut.log file. | Verify that the configuration information for the object store is correct. If the problem persists after restarting the Activities application, contact Customer Support to report the incident. |
| CLFRA0082E: Unable to access content reference for ACTIVITYUUID=<uuid>, NODEUUID=<uuid>, CONTENTREFUUID=<uuid>. | An error occurred while transferring the content of the specified activity from one content store to another. | Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process. |
| CLFRA0084E: error terminating activities object store. | An error occurred while terminating the Activities content store. Additional information relating to the failure may be found in the SystemOut.log file. | If the problem persists after restarting the Activities application, contact Customer Support to report the incident. |
| CLFRA0085E: Activities Schema Version Mismatch. Current® database schema version is <version>. Activities requires version <version>. | The system is expecting a certain schema version on the database. However, the database is reporting it has a different version. | Upgrade the Activities' codebase, or upgrade the database schema to match. |
| CLFRA0087E: The content of mime type: "<type>" or filename: "<fileName>" you tried to upload exceeded the size limit of <integer> bytes. Talk to your administrator about increasing the permitted upload size. | The administrator set a size limit for the type of content a user tried to upload, either by mime type or by filename. | Change the upload limits in the <sizeLimits> element in oa-config.xml or upload something smaller. |
| CLFRA0088E: A profile provider error has occurred. <error> | Activities received an error querying the directory (i.e. LDAP) for a user or group. | Ensure that the LDAP server configured for the 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 the LotusConnections-config.xml file (in <App server home>/profiles/<name>/config/cells/<cell name>/LotusConnections-config) 2. Make sure the files exists and is readable by the 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 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 that 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 that the mail service is configured properly. Additional information relating to the failure can be found in the SystemOut.log file. |
| CLFRA0367E: The date {0} is invalid; see documentation for acceptable date formats | The date supplied as a parameter is invalid. This date was supplied to the request to fix up the content store after a restore from backup. This is a WSAdmin command task. | Enter a date that is valid according to one of the documented acceptable formats. |
| CLFRA0368E: The folder {0} does not exist | The folder path which was supplied as a parameter is invalid. | Enter the path of a folder that exists. |
| CLFRA0369E: The attempt to fix up the content store failed : {0} | An error occurred while attempting to fix up the contents of the file store after a restore from backup. | Verify that the command was used properly and that the file system is accessible. Additional information relating to the failure can be found in the SystemOut.log file. |
| CLFRA0371E: Creation of the orphan folder {1} failed | An error occurred while attempting to create the specified folder for orphaned files. | Verify that the path for the folder exists and that the file system is accessible. Also verify that the user has write access to the file system. Additional information relating to the failure can be found in the SystemOut.log file. |
| 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 that 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. | Using 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. |
| 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. | Using 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 that you want 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 HCL 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 HCL 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 HCL 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 HCL 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 HCL 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 HCL 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 HCL 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 HCL 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 HCL 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 HCL 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 HCL 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. |
| CLFRA0828E: An incorrect event type was sent to the audit event processor. | Error publishing event : {0} | Check oa-config.xml (eventBroker) tag. |
| CLFRA0829E: Error purging items. | An error with the server or database. For example, this might denote that the database server is down or that there is an authorization issue. | Check the SystemOut.log file to find the cause. |
| CLFRA0830I: Purging, fetched {0} items for current batch. | Denotes number of items to delete during purge. | This is an informational message only; no action is required. |
| CLFRA0831E: Error fetching items to purge. | An error with the server or database. For example, this might denote that the database server is down or that there is an authorization issue. | Check the SystemOut.log file to find the cause. |
| CLFRA0832W: Number of items to purge is either not specified or invalid ({0}). Defaulting to {1} items. | Invalid or missing maxNumberOfDeletionPerCall value in EventLogPurgeJob task. | Correct the value for maxNumberOfDeletionPerCall in the EventLogPurgeJob task in oa-config.xml. |
| CLFRA0833I: Number of new event log entries added since last execution at {0} : {1} | Denotes number of entries in log since last event purge. | This is an informational message only; no action is required. |
| CLFRA0834I: Number of event log entries purged {0} for the current batch. | Denotes number of entries deleted from log for current purge. | This is an informational message only; no action is required. |
| CLFRA0835I: Total number of event log entries purged {0}. | Denotes total number of entries deleted from log. | This is an informational message only; no action is required. |
| CLFRA0836I: Number of event log entries purged {0}, number of new event log entries added {1}. | Denotes number of entries deleted from log and number of entries added to log. | This is an informational message only; no action is required. |
| CLFRA0837I: The number of event log entries purged is less than the number of event log entries added. | Fewer entries were removed from the log than added. consider changing purge settings. | This is an informational message only; no action is required. Consider adjusting the retentionInDays and maxNumberOfDeletionPerCall values in the EventLogPurgeJob task in oa-config.xml. |
| CLFRA0825I: Total number of followers purged: {0}. | Denotes number of followers removed. The followers removed are users who are still in the activity's follower list but should not be. | This is an informational message only; no action is required. |
| CLFRA0826I: Found {0} deletable followers for the current batch. | Denotes the number of followers to be deleted. This number matches the number of followers mentioned in CLFRA0825I. | This is an informational message only; no action is required. |
| CLFRA0827E: Error getting LogEntries for a date range: {0}. | An error occurred with the database. | Check the SystemOut.log file to find the cause. |
| CLFRA0839E: The content store type : {0} was not found. | Invalid content store type is specified in oa-config.xml . | For this store type, verify that the objectStore specified in the oa-config.xml includes a valid id attribute and directory mapping. |
| CLFRA0840E: Error getting Invitations for member: {0}. | An error occurred with the database. | Check the SystemOut.log file to find the cause. |
| CLFRA0841E: Error inserting MemberProfile; no login names are available. | The data Activities retrieved from the name directory (Profiles or LDAP) does not have a login name assigned to the user. This might be caused by an invalid user profile. | Fix the problem on the name directory. |
| CLFRA0842E: Error inserting MemberProfile; no login names are available. | The data Activities retrieved from the name directory (Profiles or LDAP) does not have a login name assigned to the user. This might be caused by an invalid user profile. | Fix the problem on the name directory. |
Parent topic:Error message reference
Related information