Use the codes included in the error messages generated by Lotus Connections to identify problems with the Communities feature and find solutions to them.
|
|
|
|
CLFRM0001E: Communities https service url is malformed: {0}.
|
The Web address specified is in an invalid URL syntax.
|
|
CLFRM0002W: SubjectHelper.cloneSubject was called with null subject.
|
There is a problem with the authenticated user resulting in null information.
|
Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
|
CLFRM0003E: Communities http service url is malformed: {0}.
|
The Web address specified is in an invalid URL syntax.
|
|
CLFRM0004I: Executing {0} request.
|
The specified request is being executed.
|
Informational message; no solution is needed.
|
CLFRM0005E: Error executing update community name for {0}.
|
Could not update specified community.
|
Check the database connection. See the SystemOut.log file for more information about the error.
|
CLFRM0006I: Executing create community. Community name: {0}.
|
Creating the specified community.
|
Informational message; no solution is needed.
|
CLFRM0007E: Error registering mbean.
|
An exception was generated when registering the MBeans.
|
Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
|
CLFRM0008E: Error executing remove tags from {0}.
|
Could not remove tags from specified community.
|
Check the database connection. See the SystemOut.log file for more information about the error.
|
CLFRM0009E: Unknown role assignment in createCommunity call: role must be either OWNER or MEMBER.
|
Invalid role parameter used in administrative command.
|
Correct the syntax and retry the command.
|
CLFRM0010I: Executing add members to {0}.
|
Adding members to the specified community.
|
Informational message; no solution is needed.
|
CLFRM0011E: Error initializing Communities JMX support: failed to register {0}.
|
The Web address specified is in an invalid URL syntax.
|
|
CLFRM0012I: Executing remove tags from {0}.
|
Executing the specified command.
|
Informational message; no solution is needed.
|
CLFRM0013E: Error purging index.
|
An error occurred while purging the full text index.
|
Shut down and restart the server. If the error persists, report this problem to Customer Support.
|
CLFRM0014E: Error locating MBeanServer, no Community Administration MBeans registered.
|
An exception was generated when locating the MBean server needed to register the MBeans.
|
Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
|
CLFRM0015E: User {0} was not found.
|
The specified user was not found in the directory. The command cannot be executed.
|
Check the spelling of the user name and the directory configuration.
|
CLFRM0016E: Error executing {0}.
|
There was an error executing the specified request.
|
Report this problem to Customer Support. See the SystemOut.log file for more information about the error.
|
CLFRM0017E: Error executing update community description for {0}.
|
The description of the specified community could not be updated.
|
Check the database connection. See the SystemOut.log file for more information about the error.
|
CLFRM0018I: Executing update community name. Changing {0} to {1}.
|
Updating community name as specified.
|
Informational message; no solution is needed.
|
CLFRM0019E: Error initiating indexing operation.
|
An error initializing the full text index.
|
Shut down and restart the server. If the error persists, report this problem to Customer Support.
|
CLFRM0020E: Error executing add members to {0}.
|
Could not add members to specified community.
|
Check the database connection. See the SystemOut.log file for more information about the error.
|
CLFRM0021E: Error executing remove references by URI from {0}.
|
Could not remove references from specified community.
|
Check the database connection. See the SystemOut.log file for more information about the error.
|
CLFRM0022E: Error executing create community. Community name: {0}
|
Could not create a community with specified name.
|
Check the database connection. See the SystemOut.log file for more information about the error.
|
CLFRM0023I: Executing start indexing request.
|
The index is being started.
|
Informational message; no solution is needed.
|
CLFRM0024I: Executing remove references by URI from {0}.
|
Removing requested references from specified community.
|
Informational message; no solution is needed.
|
CLFRM0025I: Executing purge index request.
|
The index is being purged.
|
Informational message; no solution is needed.
|
CLFRM0026I: Executing update community description for {0}.
|
The community description is being updated.
|
Informational message; no solution is needed.
|
CLFRM0027E: Community not found: {0}.
|
The community specified was not found.
|
Informational message; no solution is needed.
|
CLFRM0028E: Cannot create reference with duplicate URI: {0}.
|
Cannot create a reference with the specified name.
|
A reference with the specified name already exists within this community and cannot be duplicated. Please select a different name and execute the command again.
|
CLFRM0029I: Finished writing index at: {0}.
|
The full text index task finished updating the index at the specified time.
|
Informational message; no solution is needed.
|
CLFRM0030E: Error: Index may be corrupted. Please re-run the indexing task to build a new index.
|
The full text index may be corrupted. Full text search will not function.
|
Use the administrative tasks to purge and reload the index.
|
CLFRM0031E: Error retrieving IndexWriter.
|
The server cannot update the full text index.
|
If the error persists, stop, and then restart the server.
|
CLFRM0032E: Error deleting community documents from the index.
|
The server was unable to delete the documents from the full text index.
|
Try again to delete the documents or use the administrative tasks to purge and reload the full text index.
|
CLFRM0033I: Initializing Communities Management.
|
The communities management feature is initializing.
|
Informational message; no solution is needed.
|
CLFRM0034E: Error writing last update to {0}.
|
The server encountered an error when writing the full text index last update time to the file system.
|
If the error persists, stop and then restart the server.
|
CLFRM0035I: Full-text search was started at: {0}.
|
The full text search was started at the specified time.
|
Informational message; no solution is needed.
|
CLFRM0036E: Unable to find reference with id: {0}.
|
A reference with the specified identifier was not found.
|
Check the parameter value and try again. If the problem persists, check the database connection. See the SystemOut.log file for more information about the error.
|
CLFRM0037E: User is not authorized to perform the indexing task on communities.
|
The indexing task is not running under an authorized user account.
|
Stop and then restart the server. If the error persists, report the problem to Customer Support.
|
CLFRM0038E: Error retrieving the last update from {0}.
|
The server encountered an error when retrieving the full text index last update time from the file system.
|
If the error persists, stop and then restart the server.
|
CLFRM0039E: Internal error.
|
An internal error has occurred.
|
See the SystemOut.log file for more information about the error.
|
CLFRM0040I: Starting to write the index at: {0}.
|
The full text index task started to update the index at the specified time.
|
Informational message; no solution is needed.
|
CLFRM0041E: Unable to find community with id: {0}.
|
The community with the specified identifier was not found.
|
Check the parameter value and try again. If the problem persists, check the database connection. See the SystemOut.log file for more information about the error.
|
CLFRM0042E: Schema Version Mismatch.
|
The database schema does not match the feature version.
|
Upgrade the database using the specified procedure.
|
CLFRM0043E: Cannot create community with duplicate name: {0}.
|
Cannot create a community with the specified name.
|
A community with the specified name already exists and cannot be duplicated. Please select a different name and execute the command again.
|
CLFRM0044E: Error retrieving the full-text index. Stopping scheduled full-text indexing for Communities.
|
The server could not initialize the full text indexing service. The indexing service is disabled.
|
Stop, and then restart the server. If the error persists, report the problem to Customer Support.
|
CLFRM0045E: Error parsing the search query.
|
The search query syntax was invalid.
|
Correct the syntax and issue the command again.
|
CLFRM0046I: Stopping Communities Management.
|
The communities management feature is stopping.
|
Informational message; no solution is needed.
|
CLFRM0047E: User passed NULL directory member profile to getCurrentMemberProfile() method.
|
The member profile parameter is invalid; a non-null value is required.
|
Specify appropriate parameters for the request.
|
CLFRM0048E: Error retrieving communities for indexing.
|
An error occurred searching the full text index.
|
Stop and then restart the server. If the error persists, report the problem to Customer Support.
|
CLFRM0049E: NOT IMPLEMENTED.
|
This function is not implemented.
|
See the SystemOut.log file for more information about the error.
|
Message | Cause | Solution |
CLFRV0001E: Viral content replaced.
|
The virus scanner removed a virus from added content.
|
|
CLFRV0003E: Virus detected - .
|
The virus scanner received the error scanning content.
|
No action necessary. The content was not added to the discussion forum.
|
CLFRV0006E: Unable to find CMAPI provider "".
|
Unable to find a suitable CMAPI provider.
|
Check the settings in forum-config.xml and provide a correct for the class property of the store element.
|
CLFRV0007E: Unable to store object. URL = HTTP status = .
|
An error occurred while attempting to store the discussion forum's content in the Domino content store.
|
Verify that the Domino server is responding and that the URL is accessible. The HTTP response code may give additional information as to the reason for the failure.
|
CLFRV0008E: Unrecognized URI: for this ObjectStore: .
|
An invalid URL or URL syntax was used to access the Domino content store.
|
Verify that the Domino server is responding and that the URI is accessible. Contact Customer Support for additional information.
|
CLFRV0009E: Unable to access: , the HTTP response code = .
|
An error occurred while attempting to retrieve a discussion forum's content from the Domino content store.
|
Verify that the Domino server is responding. The HTTP response code may give additional information as to the reason for the failure.
|
CLFRV0010E: Notes UNID could not be retrieved. Make certain the database has the correct design.
|
An error occurred while attempting to store or update a discussion forum in the Domino content store.
|
Verify that the Domino server is responding. Verify that the Domino object store is using the correct NSF design.
|
CLFRV0011W: Content does not have a name, the generated name will be used.
|
A warning that the content being saved did not have a name while attempting to store or update a discussion forum in the Domino content store.
|
No action is required. The system has generated a name automatically.
|
CLFRV0012E: Unable to delete object. URL = HTTP status = .
|
An error occurred while attempting to delete a discussion forum from the Domino content store.
|
Verify that the Domino server is responding and that the URL is accessible. The HTTP response code may give additional information as to the reason for the failure.
|
CLFRV0013E: Unable to delete file .
|
An error occurred while deleting a file from the discussion forum content store. Additional information relating to the failure may be found in the SystemOut.log file.
|
Verify that the directory and file information is correct.
|
CLFRV0014E: Unable to create file upload directory .
|
The directory given in forum-config.xml for the element property name "root.directory" either could not be found or created. This directory is used for file uploads to the discussion forum content store.
|
Check that the directory exists; create it if it does not exist.
|
CLFRV0015E: Error encountered deleting content: .
|
An error occurred while deleting the contents of a file from the discussion forum content store. Additional information relating to the failure may be found in the SystemOut.log file.
|
Verify that the directory and file information is correct.
|
CLFRV0016E: Unable to upload file: .
|
An error occurred while retrieving or uploading a file to the discussion forum content store. Additional information relating to the failure may be found in the SystemOut.log file.
|
Verify that the directory and file information is correct.
|
CLFRV0017E: Error closing statistics file.
|
A file system error occurred closing one of the files used for discussion forum statistics persistence.
|
Verify that the file system directory containing the statistics files is writable and has available space.
|
CLFRV0019E: Error creating statistics file.
|
A file system error occurred creating one of the files used for discussion forum statistics persistence.
|
Verify that the file system directory containing the statistics files is writable and has available space.
|
CLFRV0020E: Error parsing statistics file.
|
The format of one of the files used for discussion forum statistics persistence is inconsistent with the expected format.
|
Remove the existing files in the file system directory containing the statistics files.
|
CLFRV0021E: Activities statistics persistence cannot create directory .
|
A file system error occurred creating the file system directory for containing the discussion forum 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 on the file system.
|
CLFRV0022E: Error saving to statistics file.
|
A file system error occurred saving data one of the files used for discussion forum statistics persistence.
|
Verify that the file system directory containing the statistics files is writable and has available space.
|
CLFRV0023E: Error saving summary information.
|
A file system error occurred saving data one of the files used for discussion forum statistics persistence.
|
Verify that the file system directory containing the statistics files is writable and has available space.
|
CLFRV0026E: Error fetching profiles.
|
The MemberService wsadmin object received an exception executing a fetchMembers command.
|
Verify that the parameter to the fetchMembers command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0028E: Error updating acl.
|
The AccessControlService wsadmin object received an exception executing an access modification command.
|
Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0029E: Error fetching activities.
|
The ActivityService wsadmin object received an exception executing a command to fetch the discussion forum.
|
Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0030E: Error fetching acl.
|
The AccessControlService wsadmin object received an exception executing a fetchAccess command.
|
Verify that the parameter to the command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0032E: Error updating profile.
|
The MemberService wsadmin object received an exception executing a updateMember command.
|
Verify that the parameter to the updateMember command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0033E: Error purging trash.
|
The TrashCollectionService wsadmin object received an exception executing a purgeTrash command.
|
Verify that the parameter to the purgeTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0034E: Error fetching trash.
|
The TrashCollectionService wsadmin object received an exception executing a fetchTrash command.
|
Verify that the parameter to the fetchTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0035E: Error undeleting trash.
|
The TrashCollectionService wsadmin object received an exception executing a undeleteTrash command.
|
Verify that the parameter to the undeleteTrash command is valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0036E: Error locating MBeanServer, no Activity Administration MBeans registered.
|
An exception was generated when the Discussion Forum tried to locate the MBean server needed to register the Discussion Forum Administration MBeans.
|
Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0038E: Error registering mbean.
|
An exception was generated when the Discussion Forum tried to register the Activities Administration MBeans.
|
Report this problem to Customer Support. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0042E: error parsing generic properties into a Properties object.
|
An exception was generated when the Event Broker tried to parse its configuration from forum-config.xml.
|
Ensure the properties and elements for the element in forum-config.xml are valid. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0043E: subscriber did not start: .
|
The Event Broker service is attempting to initialize a subscriber to server-generated events, but the subscriber initialization process failed.
|
Check that the configuration specified in forum-config.xml for the subscriber reporting this error is valid. Additionally, you may want to pursue the exception thrown by the subscriber in the SystemOut.log file.
|
CLFRV0044E: The class "" 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 configuration has been spelled correctly. Also check to see that the class file is visible in the current classpath scope. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0045E: The class "" 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 configuration itself. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0046E: Illegal access exception for the class "".
|
The Event Broker service is trying to access fields or methods in the class discovered via reflection that it can't normally see. Additional information relating to the failure may be found in the SystemOut.log file.
|
Examine the class for methods that should be exposed have been hidden.
|
CLFRV0047E: {0} error initializing adapter: classname= "{1}" Double-check the config settings for this specific adapter for correct/valid values.
|
The Event Broker service is attempting to initializer a subscriber to server-generated events, but the subscriber initialization process failed.
|
Check that the configuration specified in forum-config.xml for the subscriber reporting this error is valid. Additionally, you may want to pursue the exception thrown by the subscriber in the SystemOut.log file.
|
CLFRV0048E: Could not inform a subscriber of event: .
|
The Event Broker service passed an event to a subscriber of that event, and the subscriber issued an exception.
|
To fix this class of exception, you need to determine what is failing in this particular subscriber. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0050E: Invalid forum-config.xml file. Check the XML format and ensure that all required settings are complete.
|
The format of forum-config.xml does not have correct XML syntax.
|
Load the forum-config.xml file into a browser or editor that will display syntax errors; fix the error and save the file.
|
CLFRV0051E: Error decoding passwords. If passwords are encoded, some functionality may fail.
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0068E: OpenActivitiesException while updating node content ref uuid=.
|
An error occurred while updating the content of the specified discussion forum.
|
Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
|
CLFRV0070E: Illegal access exception for the class "".
|
An error occurred while processing the discussion forum content store configuration. Additional information relating to the failure may be found in the SystemOut.log file.
|
Verify that the configuration information in forum-config.xml is correct. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0071E: DaoException while updating node content ref uuid=.
|
An error occurred while updating the content of the specified discussion forum.
|
Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
|
CLFRV0072E: activities object store did not start: .
|
The Discussion Forum Object Store service implemented by did not start. Additional information relating to the failure may be found in the SystemOut.log file.
|
Verify that the configuration information in forum-config.xml is correct. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0073E: Destination ObjectStore ID="" not found in ObjectStore registry. Double-check the forum-config.xml file.
|
An error occurred while transferring discussion forum content from one content store to another. The requested destination object store identifier was not found.
|
Check the spelling of the ID used and compare it with the available object stores listed in the forum-config.xml file.
|
CLFRV0074E: ObjectStoreFilter: error during activities object store content filtering "".
|
An error occurred while processing discussion forum content. Additional information relating to the failure may be found in the SystemOut.log file.
|
Depending on the additional error information given, it may be possible to correct the data and re-process it.
|
CLFRV0075E: Premature invocation before transfer is complete. Check busy() method or listen for completion event.
|
An error occurred while transferring discussion forum content from one content store to another. The transfer utility may already be carrying out a transfer.
|
Attempt this operation after the other transfer is complete.
|
CLFRV0076E: Exception while retrieving activities collection.
|
An error occurred while transferring discussion forum content from one content store to another.
|
Check that the content stores are available and accessible.
|
CLFRV0077E: ObjectStoreConfigLoader: the class "" could not be instantiated.
|
An error occurred while processing the discussion forum content store configuration. Additional information relating to the failure may be found in the SystemOut.log file.
|
Verify that the configuration information in forum-config.xml is correct. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0078E: Source ObjectStore ID="" not found in ObjectStore registry. Double-check the forum-config.xml file.
|
An error occurred while transferring discussion forum content from one content store to another. The requested source object store identifier was not found.
|
Check the spelling of the ID used and compare it with the available object stores listed in the forum-config.xml file.
|
CLFRV0079E: {0} error initializing adapter: classname= "{1}" Double-check the config settings for this specific adapter for correct/valid values.
|
An error occurred while processing the discussion forum content store configuration. Additional information relating to the failure may be found in the SystemOut.log file.
|
Verify that the configuration information for the object store is correct. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0080E: ObjectStoreConfigLoader: missing id for activities object store class "".
|
An error occurred while loading the discussion forum content store configuration.
|
Verify that the configuration information for the object store is correct. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0081E: EventBrokerConfigLoader: the class "" was not found. Check the configuration file, under the class attribute of the service for the correct Java classname. Or, check the classpath to make sure the class is visible.
|
An error occurred while processing the discussion forum content store configuration. Additional information relating to the failure may be found in the SystemOut.log file.
|
Verify that the configuration information for the object store is correct. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0082E: Unable to access content reference for ACTIVITYUUID=, NODEUUID=, CONTENTREFUUID=.
|
An error occurred while transferring the content of the specified discussion forum from one content store to another.
|
Check that the content stores are available and accessible and that the referenced item exists in the content store. The item may have been deleted by an external process.
|
CLFRV0084E: Error terminating activities object store.
|
An error occurred while terminating the discussion forum content store. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0085E: Activities Schema Version Mismatch. Current database schema version is . Activities requires version .
|
The system is expecting a certain schema version on the database. However, the database is reporting it has a different version.
|
Upgrade the discussion forum codebase, or upgrade the database schema to match.
|
CLFRV0087E: The content of mime type: "" or filename: "" you tried to upload exceeded the size limit of bytes. Talk to your administrator about increasing the permitted upload size.
|
The administrator set a size limit for the type of content a user tried to upload, either by mime type or by file name.
|
Change the upload limits in the element in forum-config.xml or upload something smaller.
|
CLFRV0088E: Profile provider error.
|
The Discussion Forum received an error querying the directory (i.e. LDAP) for a user or group.
|
Ensure that the LDAP server configured for the WebSphere Application Server is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
|
CLFRV0090E: Profile provider error.
|
The Discussion Forum received an error querying the directory (i.e. LDAP) for a user or group.
|
Ensure that the LDAP server configured for the WebSphere Application Server is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
|
CLFRV0091E: Internal error.
|
The Discussion Forum generated an exception.
|
If the problem persists after restarting the Communities feature, contact Customer Support to report the incident. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0092E: A short description could not be generated because the entry contains invalid HTML.
|
The service tried to clean up user-submitted HTML rich text input using the JTidy library. The HTML was so malformed that JTidy could not clean it, and produced a null result. This error is a message printed to the user that indicates the service could not truncate the input HTML to produce a summary for display in the entry.
|
The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
|
CLFRV0093E: Exception while executing JTidy on node: .
|
The service tried to clean up user-submitted HTML rich text input using the JTidy library. JTidy failed to finish executing on this HTML code before throwing an exception.
|
The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
|
CLFRV0094E: Output from JTidy execution: .
|
This is a trace message that explains why JTidy failed to process some HTML input.
|
This exception trace will inform you on how JTidy failed and whether it could be fixed.
|
CLFRV0095E: Internal error while executing JTidy on node: .
|
The service tried to clean up user-submitted HTML rich text input using the JTidy library. The HTML was so malformed that JTidy could not clean it, and produced a null result.
|
The user should attempt to change the HTML input, possibly by copying a different section of rich text to paste into the entry body.
|
CLFRV0096E: Error fetching deleted items to purge.
|
The scheduled TrashAutoPurge job received an exception fetching the items to purge.
|
Restart the Discussion Forum feature. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0102E: Error closing e-mail connections.
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0105E: Error purging deleted items.
|
The scheduled TrashAutoPurge job received an exception purging items.
|
Restart the Discussion Forum feature. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0106E: Error sending notify message.
|
Error when trying to send an e-mail notification.
|
Ensure that SMTP server configuration in the element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0107E: Error composing HTML e-mail message.
|
Error received when trying to create an outbound e-mail message from the server.
|
Restart the Discussion Forum feature. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0108E: EmailNotifier: problems sending e-mail. Most probable cause is due to using an invalid recipient e-mail address. Or, the connection to the host is down. Or, there could also be authentication problems - check the user/password settings.
|
Error received when trying to send outbound e-mails.
|
Ensure that SMTP server configuration in the element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0109E: Malformed e-mail template, url=.CLFRV0109E: Malformed e-mail template, url=.
|
The Web address specified is in an invalid URL syntax/format.
|
Check forum-config.xml, email/outbound/templates/url and make sure the URLs are valid. You can validate them by typing the URLs directly into a browser.
|
CLFRV0110E: Error sending error message.
|
Error received when trying to send an e-mail error notification.
|
Ensure that SMTP server configuration in the element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0105E: Error purging deleted items.
|
The scheduled TrashAutoPurge job received an exception purging items.
|
Restart the Discussion Forum feature. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0106E: Error sending notify message.
|
Error when trying to send an e-mail notification.
|
Ensure that SMTP server configuration in the element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0107E: Error composing HTML e-mail message.
|
Error received when trying to create an outbound e-mail message from the server.
|
Restart the Discussion Forum feature. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0108E: EmailNotifier: problems sending e-mail. Most probable cause is due to using an invalid recipient e-mail address. Or, the connection to the host is down. Or, there could also be authentication problems - check the user/password settings.
|
Error received when trying to send outbound e-mails.
|
Ensure that SMTP server configuration in the element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0109E: Malformed e-mail template, url=.
|
The URL specified is in an invalid URL syntax/format.
|
Check forum-config.xml, email/outbound/templates/url and make sure that the URLs are valid. You can validate them by typing the URLs directly into a browser.
|
CLFRV0110E: Error sending error message.
|
Error received when trying to send an e-mail error notification.
|
Ensure that SMTP server configuration in the element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0111E: Unable to connect to any of the 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 element of forum-config.xml are reachable.
|
CLFRV0112E: Unable to get e-mail template from url= .
|
Error trying to retrieve an e-mail template from the given URL.
|
Check forum-config.xml, email/outbound/templates/url and make sure the URLs are valid. You can validate them by typing the URLs directly into a browser.
|
CLFRV0114E: The e-mail from "" with subject "" did not match either the create or add-to matching address expressions. The e-mail will be deleted and not processed.
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0115E: The e-mail address="" was not found in the directory. Unable to process the message.
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0116E: Unable to find a member profile for the e-mail "". This user will not be added to the activity membership.
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0117E: The activity you tried to e-mail into (id=) is deleted or no longer exists.
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0118E: You need to update your configuration file version. Make sure you are not trying to use an old config file on a newer server or vice-versa.
|
The version of forum-config.xml on the server differs from the version expected by the Discussion Forum.
|
Ensure the version property of the element in forum-config.xml matches the version expected by the Discussion Forum.
|
CLFRV0119E: ExecutionContext leak detected.
|
The Discussion Forum feature has detected a resource leak.
|
Restart the Discussion Forum feature. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0120E: Internal Error, EC Count is null.
|
The Discussion Forum feature has detected a resource leak.
|
Restart the Discussion Forum feature. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0121E: Error publishing event .
|
The Discussion Forum feature received an error from the Event Broker service.
|
Check that the configuration specified in forum-config.xml is valid. Correct an invalid configuration. Additional information relating to the failure may be found in the SystemOut.log file. If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0122E: Cannot find credentials for .
|
The system is configured to use J2C Authentication Aliases to store authentication data. The entry for is missing.
|
Go to Secure administration, applications, and infrastructure > JAAS > J2C authentication data in the WebSphere® Application Server Integrated Solutions Console, and check whether there is an entry for . If there is no entry, create an Authentication Alias for by completing these steps:
1. Shut down the WebSphere Application Server.
2. Edit the security.xml file in /profiles/AppSrv01/config/cells/
3. Find the authDataEntries entry with an alias that includes . For example: 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 , verify that the user credentials are correct. If these steps do not fix the problem, then contact Customer Support. |
|
CLFRV0123E: Profile provider error.
|
The Discussion Forum received an error querying the directory (i.e. LDAP) for a user or group.
|
Ensure that the LDAP server configured for the WebSphere Application Server is accessible and that the bind credentials used to authenticate to the LDAP server (if necessary) are valid.
|
CLFRV0127W: Activities cannot determine host name.
|
An error occurred while initializing the Statistics collection service. There was a problem with the server host name. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0131E: Activities Task Scheduler initialization error: .
|
Reason: An error occurred while initializing the Quartz scheduler. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0135E: Error executing event notification.
|
Error received in the event broker. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0136E: Exiting the Aynch Notification Thread: event processing has been halted.
|
Error received when the event broker thread is halted. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0137E: Error encountered processing events.
|
Error received in the event broker when dispatching events. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0138E: The invoker should not be interrupted.
|
Another thread interrupted the internal event broker. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0142E: Incorrect number of arguments. Please specify the configuration file to process.
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0143E: Cannot locate configuration file {0}.
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0144E: ConfigurationParser: Bad configuration. Config section defines more properties than values, or vice versa. Possible errant element(s) without a "name" attribute(s).
|
A configuration element in forum-config.xml or forum-jobs.xml is invalid.
|
Enable debug tracing for com.ibm.openactivities.util, restart the feature, and determine the invalid element from the trace.log output. Correct the element and restart the Discussion Forum feature.
|
CLFRV0146E: Unable to refresh cached list of groups.
|
The Discussion Forum received an exception refreshing its group cache. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0147E: Error initializing Activities.
|
The Discussion Forum feature received an error trying to start.
|
The cause of the error will be found in the SystemOut.log file. Correct the error cause and restart the Discussion Forum feature.
|
CLFRV0269E: Unable to connect to Domino database at url=
|
An error occurred while attempting to connect to the Discussion Forum's Domino content store.
|
Verify that the Domino server is responding and that the URL is accessible.
|
CLFRV0270E: Error getting server URL for .
|
There was an error reading the server URL for the service.
|
1. Find the LotusConnections-config.xml file (in /profiles//config/cells//LotusConnections-config)
2. Make sure that the files exists and is readable by the WebSphere Application Server process.
3. Make sure that the files contain the correct entry for the service. |
|
CLFRV0271E: Cannot find config variable directory .
|
There was a problem reading variables that can be used in the forum-config.xml file.
|
Make sure that the directory exists and is readable by the WebSphere Application Server.
|
CLFRV0272E: Cannot find for config variables.
|
There was a problem opening a file getting configuration variables.
|
Make sure that the file exists and is readable by the WebSphere Application Server.
|
CLFRV0273W: Missing system setting for .
|
The Lotus 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.
|
CLFRV0275E: Error loading config variables from .
|
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.
|
CLFRV0276E: Too many errors encountered sending Activity Auto Completion notices, auto complete aborted.
|
The server has given up trying to keep sending any more auto complete e-mail notices.
|
Ensure that SMTP server configuration in the element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0277W: Warning, invalid parameter specified for the Activity Auto Completion notification max errors ({0}).
|
Should not see this error message. Feature is not enabled.
|
Should not see this error message. Feature is not enabled.
|
CLFRV0278E: Error generating list of activities eligible for auto completion.
|
Error received querying the database to obtain a list of discussion forums that qualify to be autocompleted. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0279E: Error sending auto complete notification for activity UUID .
|
Error received when sending e-mail 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 element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0280E: Error initializing the Activities Administrator e-mail address. Some e-mail functionality will be unavailable.
|
No administrator e-mail address was configured in forum-config.xml.
|
Edit forum-config.xml and provide an administrator e-mail address in the element.
|
CLFRV0281E: The content of mime type: "" or filename: "" you tried to upload is not allowed by your administrator.
|
The administrator set a size limit of zero bytes for the type of content a user tried to upload, either by mime type or by file name.
|
Change the upload limits in the element in forum-config.xml.
|
CLFRV0282E: profile provider could not find member for .
|
The Discussion Forum profile feature did not find a member by the given member ID.
|
Contact Customer Support to report the incident.
|
CLFRV0285W: Purge expiration period (days) either not specified or invalid (). Defaulting to {1} days.
|
The trashRetentionInDays configured for the TrashAutoPurgeJob in forum-jobs.xml is invalid.
|
Add a value greater than 0 for the trashRetentionInDays configuration. Otherwise, trash older than 1 day will be purged when the job runs.
|
CLFRV0286E: Error sending activity auto completion notification.
|
Error received when trying to send an e-mail auto-completion notification.
|
Ensure that SMTP server configuration in the element of forum-config.xml is valid and that the server is accessible. Additional information relating to the failure may be found in the SystemOut.log file.
|
CLFRV0287E: Error parsing administrator email address.
|
The administrator e-mail address configured in forum-config.xml is badly formatted.
|
Edit forum-config.xml and provide an administrator e-mail address in the correct format in the element.
|
CLFRV0288E: No Activities Administrator email address has been configured. You must specify a value for "activities-admin-email-address".
|
The administrator e-mail address configured in forum-config.xml is empty.
|
Edit forum-config.xml and provide an administrator e-mail address in the correct format in the element.
|
CLFRV0289W: Content removed by active content filter.
|
The active content filter removed active content from user input.
|
|
CLFRV0290E: Error starting the active content filter.
|
The active content filter received an error on start up.
|
Contact Customer Support to report the incident.
|
CLFRV0291E: Error encountered with the active content filter.
|
The active content filter received an error trying to filter text.
|
Contact Customer Support to report the incident.
|
CLFRV0292W: Warning, it appears the ACF inserted an invalid character mid stream ().
|
The active content filter inserted an invalid character in the filteredText as part of a filtering operation.
|
No action necessary. The Discussion Forum feature fixes up the invalid character.
|
CLFRV0293E: MemberProfile cannot be null.
|
The data in a request to update a member profile in the database is null; possibly via a bad API request.
|
Contact Customer Support to report the incident.
|
CLFRV0295E: Cannot update non-matching MemberProfiles. is not .
|
In a request to one member profile with a new one, the member IDs do not match.
|
Contact Customer Support to report the incident.
|
CLFRV0300E: The ArchiveService cannot export activities to the directory=; it is not writable.
|
The exportActivities command of ArchiveService wsadmin object tried to archive the Discussion Forum to a directory that is not writable.
|
Ensure that exists and that it is writable by the WebSphere Application Server.
|
CLFRV0301E: The required zip file "Activity-.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 . However, the directory path that was also given to the ArchiveService does not contain the file Activity-.zip.
|
Ensure that the directory specified in an ArchiveService importActivities or createActivities command contains the archives for the desired discussion forums.
|
CLFRV0304E: The version of the archive you tried to import does not match the current DB schema.
|
One cannot import activities into servers that are using different DB schemas.
|
Migrate the archive to the matching schema version and then import the migrated archive.
|
CLFRV0306W: The user by e-mail (or display name if it's a group) was not found in the LDAP or the database! This means the activity being imported has a reference to a user that has changed e-mails, or has been removed from the LDAP. In other words, this e-mail 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 e-mail address (or display name if a group) will be rewritten to "NOT_FOUND_". If this behavior is unexpected, you might want to investigate why members are missing in the new LDAP.
|
CLFRV0309E: The ArchiveService cannot export activities to the directory=; it is not a directory.
|
The exportActivities command of ArchiveService wsadmin object tried to archive the Discussion Forum to a directory that is not writable.
|
Ensure that exists and that it is writable by the WebSphere> Application Server.
|
CLFRV0310E: Error writing activity entry # to the database.
|
An ArchiveService import error received at the point where the Node of the Discussion Forum is written. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
|
CLFRV0312E: Error writing activity node to the database.
|
An ArchiveService import error received at the point where one of the nodes (entries) of the Discussion Forum is written. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
|
CLFRV0315E: The ArchiveService cannot create the directory= 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 on the file system and ensure it is writable by the WebSphere Application Server.
|
CLFRV0318E: The related activity with UUID= already exists in the system. It is unclear whether the intention is to overwrite that activity with old data or not. Thus, it will be not imported.
|
When a discussion forum has a related discussion forum link in it, the ArchiveService will automatically try to import the related discussion forum. However, if the ArchiveService is being run with "importActivities" which overwrites discussion forums rather than creating copies, then, it is unclear to the system whether the administrator also intentionally meant to overwrite related discussion forums since that related discussion forum was not explicitly passed in to be imported.
|
If the administrator wishes to overwrite the related discussion forum, he can use the ArchiveService importActivites command to overwrite the related discussion forum.
|
CLFRV0319E: Error writing activity content entry "".
|
An ArchiveService import error received at the point where the content (files, attachments, etc) of one of the nodes (entries) of the discussion forum is written. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
|
CLFRV0320E: Error importing activity with UUID=.
|
An ArchiveService import error. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the error reported in the SystemOut.log file cannot be resolved, contact Customer Support to report the incident.
|
CLFRV0321E: Error unpacking the archive.
|
An ArchiveService import error received when unmarshalling the Zip archive.
|
The Zip archive has been corrupted. If the cause of the corruption cannot be determined, contact Customer Support to report the incident.
|
|
|
|
Informational message; no solution is needed.
|
CLFRV0328W: The {0} scheduler is not enabled in config. Check spelling.
|
The specified scheduler is not enabled in the forum-config.xml file.
|
Check the forum-config.xml file to make sure that the scheduler is enabled (change the 'enabled' attribute to true) and that the scheduler name is spelled correctly.
|
CLFRV0329E: The attempt to start the scheduler failed.
|
The Quartz scheduler did not start. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0330W: The {0} scheduler has already been stopped.
|
The specified scheduler has already been stopped.
|
|
CLFRV0331I: The request to resume job {0} has been submitted.
|
The request to resume the specified job has been submitted.
|
Informational message; no solution is needed.
|
CLFRV0332W: The job {0} is not valid for the {1} scheduler.
|
The job you are trying to run cannot be run on the specified scheduler.
|
Run the job on the appropriate scheduler.
|
CLFRV0333I: The job {0} was removed.
|
The specified job was removed from the scheduler.
|
Informational message; no solution is needed.
|
CLFRV0334I: The {0} scheduler is running.
|
The specified job is running.
|
Informational message; no solution is needed.
|
CLFRV0335W: The job {0} is already running on the {1} scheduler.
|
The specified job is already running on the specified scheduler.
|
|
CLFRV0336I: The request to pause job {0} has been submitted.
|
The request to pause the specified job has been submitted.
|
Informational message; no solution is needed.
|
CLFRV0337W: The {0} scheduler has already been started.
|
The specified scheduler has already been started.
|
|
CLFRV0338I: The {0} scheduler was stopped successfully.
|
The specified scheduler was stopped successfully.
|
Informational message; no solution is needed.
|
CLFRV0339W: The {0} scheduler is disabled in config.
|
The specified scheduler is not enabled in the forum-config.xml file.
|
Enable the scheduler by changing the 'enabled' attribute for the scheduler to true in the forum-config.xml file.
|
CLFRV0340W: The request to pause job failed.
|
An error occurred while attempting to pause a job. Additional information relating to the failure may be found in the SystemOut.log file.
|
|
CLFRV0341W: The job has already been paused on the {1} scheduler.
|
An attempt was made to pause a job that is already paused on a scheduler.
|
Ensure that the job is running before attempting to pause it.
|
CLFRV0342I: The {0} scheduler is in standby mode.
|
The specified scheduler is in standby mode.
|
Informational message; no solution is needed.
|
CLFRV0343W: The request to resume job 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.
|
|
CLFRV0344I: The {0} scheduler was started successfully.
|
The specified scheduler started successfully.
|
Informational message; no solution is needed.
|
CLFRV0345E: The attempt to stop the scheduler failed.
|
The Quartz scheduler did not stop. Additional information relating to the failure may be found in the SystemOut.log file.
|
If the problem persists after restarting the Discussion Forum feature, contact Customer Support to report the incident.
|
CLFRV0346I: The job {0} on the {1} scheduler has been paused.
|
The specified job on the specified scheduler has been paused.
|
Informational message; no solution is needed.
|
CLFRV0347E: Error exporting activity UUID={0}.
|
An error occurred while trying to import the activity with the given UUID.
|
Check previous log messages for the actual cause of the import failure. Resolve the error and re-run the import.
|
CLFRV0348W: The group "{0}" could not be loaded from LDAP or the database. Or, there might have been multiple matches for the same name in LDAP.
|
This error is encountered when a group name is not found or multiple matches to the name are found in the configured directory.
|
No action necessary. The activity will continue to be imported; an entry for "NOT_FOUND_" + the group name will be added to the member table and the membership list.
|
CLFRV0349E: Error locating profile: EXID mismatch, but e-mail matches. email={0}, directory EXID={1}, db EXID={2}.
|
This error is encountered when a member entry is found in the Discussion Forum database by the given e-mail address, but the external identifier does not match the LDAP record.
|
Determine if the person's record has changed in LDAP and if the two entries are really for the same person. If they are, use the Discussion Forum MemberService.synchMemberExtId (email address) command to update the Discussion Forum database with the correct id.
|
CLFRV0350E: Error: the group profile "{0}" could not be located in the Activities database.
|
This error is encountered during LDAP synchronization. The group could not be located in the Discussion Forum database.
|
Check the spelling of the group name.
|
CLFRV0351E: Error: the group profile "{0}" could not be located in the directory service.
|
This error is encountered during LDAP synchronization. The group found in the Discussion Forum database could not be located in LDAP.
|
Check the spelling of the group name.
|
CLFRV0352I: The group profile "{0}" has been synchronized with the directory services changing the external id from {0} to {1}.
|
This message is encountered during LDAP synchronization. This record in the Discussion Forum database has been updated to match LDAP.
|
Informational message; no solution is needed.
|
CLFRV0353E: Error: the member profile "{0}" could not be located in the Activities database.
|
This error is encountered during LDAP synchronization. The person could not be located in the Discussion Forum database.
|
Check the spelling of the e-mail address.
|
CLFRV0354I: The member profile "{0}" has been synchronized with the directory services changing the external id from {0} to {1}.
|
This message is encountered during LDAP synchronization. This record in the Discussion Forum database has been updated to match LDAP.
|
Informational message; no solution is needed.
|
CLFRV0355I: The member profile "{0}" matches the directory service with external id {1}.
|
This message is encountered during LDAP synchronization. This record is already synchronized.
|
Informational message; no solution is needed.
|
CLFRV0356E: Error: the member profile "{0}" could not be located in the directory service.
|
This error is encountered during LDAP synchronization. The person could not be located in LDAP.
|
There is no match for the person by the given value. Check to see if the person exists in LDAP.
|
CLFRV0357E: Error: more than one profile was found for thCLFRV0359E: Error locating member profile for , search type . e key "{0}".
|
Multiple entries identified by the have been found in the member profile table.
|
One of the entries must be deleted. Contact Customer Support before proceeding.
|
CLFRV0358I: The group profile "{0}" matches the directory service with external id {1}.
|
This message is encountered during LDAP synchronization. This record is already synchronized.
|
Informational message; no solution is needed.
|
CLFRV0359E: Error locating member profile for , search type .
|
The user's member profile could not be located in the directory.
|
Verify that the LDAP configuration is correct. If this error is limited to a specific user, verify that the user can be located in LDAP given the identifier in the error message. The search type indicates what LDAP attribute is searched: 1=login, 2=e-mail, 3=internal Discussion Forum member id (not used when searching LDAP).
|
CLFRV0360I: The {0} scheduler is not running.
|
The specified scheduler is not running.
|
Informational message; no solution is needed.
|
CLFRV0361E: The file "{0}" cannot be uploaded as it is a 0-byte file.
|
An attempt was made to upload the specified file which has no content (zero bytes in size). Only files which have content may be uploaded.
|
Ensure that the file contains data before uploading.
|