Use the codes included in the error messages generated by IBM Lotus Connections to identify problems with the Dogear feature and find solutions to them.
Error messages with the CLFRO prefix pertain to the 4-in-1 bookmark form.
Error messages with the CLFRL prefix pertain to the Dogear feature.
Table 1. Dogear error messages
Error code | Description | Recommendation |
CLFRO0001E: Failed to edit bookmark, url is: {0}
|
This error is encountered if an unexpected exception occurs when updating the bookmark.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0002E: Failed to post the bookmark to Dogear.
|
This error is encountered if an unexpected exception occurs when adding a bookmark to Dogear.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0003E: Failed to build data entry for invoking remote service. The common bookmarklet creates xml document with the user inputs.
|
The common bookmarklet creates xml document with the user inputs. This error is usually caused by the bad user inputs.
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the user inputs.
|
CLFRO0004E: The parameter constraint shouldn't be null.
|
This error is encountered if the given constraint is null.
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the user inputs.
|
CLFRO0005E: Add search text operator or 'ps' or 'page' parameters failed.
|
This error is encountered if an URIException occurs when adding 'ps' or 'page' parameter.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
|
|
|
CLFRO0007E: Failed to get count of the bookmark, url is: {0}
|
This error is encountered if an unexpected exception occurs when querying the bookmark count from Dogear.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0008E: Unable to load configure file for bookmarklet installer.
|
The error is encountered if the configure file is not created or locked by other application.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0009E: Failed to apply constraints.
|
This error is encountered if an unexpected exception occurs when applying the constraints.
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the user inputs.
|
CLFRO0010E: Failed to add Credentials for invoking remote service, remote url is {0}
|
This error is encountered if an URISyntaxException occurs when adding Credentials.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0011E: Failed to invoke remote service {0}, remote server return HTTP code: {1}
|
This error is encountered if the remote service doesn't return the expected http code.
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the remote server is available.
|
CLFRO0012E: Failed to parse Lotus Connections configure file
|
Lotus Connections configuration file has something wrong
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the configure file is correct.
|
CLFRO0013E: Failed to delete the bookmark.
|
This error is encountered if an unexpected exception occurs when deleting a bookmark from Dogear.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
|
|
|
CLFRO0015E: Failed to check bookmarklet installer.
|
This error is encountered if an unexpected exception occurs when checking the installer.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0016E: Failed to publish bookmark via remote service.
|
This error is encountered if an unexpected exception occurs when adding a bookmark to Dogear
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0017E: Failed to post the bookmark to one or more Activities.
|
This error is encountered if an unexpected exception occurs when adding a bookmark to Activities.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0018E: Parse redirect url failed.
|
This error is encountered if an IRISyntaxException occurs when parsing the redirect url
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0019E: Unable to find configure file for bookmarklet installer.
|
The error is encountered if the configure file is not created.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0020E: Error init connections config.
|
Lotus Connections configuration file has something wrong, or an unexpected exception occurs when parsing the Lotus Connections configuration file.
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the configure file is correct.
|
CLFRO0021E: Failed to update the bookmark.
|
This error is encountered if an unexpected exception occurs when updating the bookmark.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0022E: Service {0} is not correctly configured.
|
Bookmarklet can not point to the correct server if attributes ""enabled"" and ""href"" are not set in the configure file. Please check Lotus Connections configure file. Lotus Connections configuration file has something wrong.
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the configure file is correct.
|
CLFRO0023E: Failed to update the bookmarklet installer.
|
This error is encountered if an IOException occurs when updating the installer.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0024E: Failed to post the bookmark to one or more Communities.
|
This error is encountered if an unexpected exception occurs when adding a bookmark to Communities.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0025E: Failed to delete bookmark, url is: {0}
|
This error is encountered if an unexpected exception occurs when deleting a bookmark from Dogear .
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0026E: Failed to validate the url.
|
When user updates a bookmark, Common Bookmarklet must first validate the url to see if user already has another bookmark with the same url.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0027E: Error when parsing atom entry to object instance.
|
The common bookmarklet received an Atom document that we could not parse because of invalid syntax. Usually this error is caused because Dogear/Communities/Activities/Blogs is not working.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0028E: Failed to get content document from url {0}.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
Make sure the given url is valid and the remote server is available.
|
CLFRO0030E: Error when handling the multiple bookmarklet user request.
|
This error is encountered if an unexpected exception occurs when handing the request of the common bookmarklet.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRO0031E: Failed to post the bookmark to one or more Blogs.
|
This error is encountered if an unexpected exception occurs when adding a blog entry to Blogs.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
|
|
|
CLFRL0001E: Error getting person for e-mail .
|
The e-mail tag is used as a key when query person in database. This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0003E: Dogear servlet error.
|
This error is encountered when Dogear servlet failed to handle the user requests.
|
Check the detailed exception message below this error massages in the log file to find the root cause. If this error occurs for all requests then it is likely a downstream error condition from a previous configuration error. Check the logs from server startup for the first error condition.
|
CLFRL0006W: Lock slow refresh rate: dt = {0}.
|
This is a utility log message that should not affect the end user for lock file {1}.
|
|
CLFRL0011E: Unable to parse atom post entry sent by user .
|
Dogear received an Atom Publishing request that we could not parse because of invalid syntax.
|
No action is required if this error does not persist. The requesting client will receive an error 400® code notifying that it sent a bad request. If this error continues, it is likely that a client continues to send bad requests. Examine the HTTP server logs to determine the source of the requests and report the problem to the application developer creating these requests.
|
CLFRL0014E: Internal error updating memberids from file with e-mail Check the detailed exception message below this error message in the log file to find the root cause. See the dogear admin guide for more details.
|
This error is encountered if an unexpected exception occurs when updating a batch of memberids by e-mail from a file in administrative service.
|
Check the detailed exception message below this error massages in the log file to find the root cause. See the Administering Lotus Connections section of the information center for more details.
|
CLFRL0015E: Internal error retrieving task by node id .
|
This error is encountered if an unexpected exception occurs when Dogear is trying to retrieve a task in the administrative service.
|
Check the detailed exception message below this error massages in the log file to find the root cause. See the Administering Lotus Connections section of the information center for more details.
|
CLFRL0016W: Failed to submit for person: .
|
This warning is encountered if an unexpected IO exception occurs when trying to submit browser bookmarks for the specified user.
|
If this warning only occurs on some browser import actions, then no action is required. Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRL0019E: Error getting person for member id .
|
This error is encountered if an unexpected SQL exception occurs when trying to get the person with the specified member ID from the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0020W: An error occurred while parsing the search query for search spec: {0}.
|
This warning is encountered if the Lucene service is unable to retrieve a search term.
|
|
CLFRL0022E: Error updating url for id .
|
This error is encountered if an unexpected SQL exception occurs when trying to retrieve a Web address with the specified ID.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0023E: An error occurred while closing the index modifier during a commit.
|
Dogear runs the indexing service as a background task. This error is encountered if an unexpected exception occurs when trying to close the index modifier during a commit.
|
No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error massages in the log file to find the root cause. If restarting the feature does not resolve and the index appears corrupt or is unusable you may use the Dogear administrative service to reset the indexing task. See the Administering Lotus Connections section of the information center for more details.
|
CLFRL0024E: Error deleting link .
|
This error is encountered if an unexpected SQL exception occurs when trying to delete the specified link from the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0026E: Error finding file .
|
This error is encountered if Dogear cannot find the specified file when trying to perform batch operations in the administrative service.
|
See the Administering Lotus Connections section of the information center for more details on how to specify a file with the administrative service. Ensure the administrative process has proper file permissions.
|
CLFRL0029E: An error occurred release lock file .
|
This error is encountered if an unexpected IO exception occurs when trying to release the lock file.
|
No action is required if this error does not persist. If this error continues, you may need to stop the affected node, delete the file by hand, and restart the node. This file is located in the same directory as your full text index. See the Administering Lotus Connections section of the information center for help determining that location. If the problem still continues, check disk permissions for the WebSphere Application Server process, also check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRL0030E: Attempt by to create subscription for .
|
This error is encountered when a user is trying to create a watchlist entry as another user.
|
This action is not allowed and the watchlist entry will not get created. If it is a malicious user, you can contact or restrict the user.
|
CLFRL0032E: Attempt by to update or delete .
|
This error is encountered if a user attempts to delete another user's link. The link will not get deleted.
|
If the delete action was performed for administrative purpose, please see the Administering Lotus Connections section of the information center. If it was performed by a malicious user, you can contact or restrict the user.
|
CLFRL0034E: Failed to rollback will continue to rollback other tasks.
|
Dogear runs some background tasks periodically. This error is encountered if an unexpected exception occurs when one is doing a rollback of the specified task.
|
No action is required if this error does not persist. If this error persists, check the detailed exception message below this error massages in the log file to find the root cause.
|
CLFRL0036E: Error updating subscription .
|
This error is encountered if an unexpected SQL exception occurs when trying to delete the specified watchlist entry.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0039W: An error occurred loading task , skipping.
|
Dogear runs a background link processing task periodically. This error is encountered if an unexpected exception occurs when initializing the link processing task.
|
Check the detailed exception message below this error massages in the log file to find the root cause.
|
CLFRL0043E: Error getting tag counts for url .
|
This error is encountered if an unexpected SQL exception occurs when trying to get tag counts for the specified URL.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0048E: Error updating Url.
|
This error is encountered if an unexpected SQL exception occurs when trying to update a URL.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0049I: Retrieving batch of url ids.
|
The Dogear admin task has retrieved a batch from the database and is about to process them to assign intranet or internet status to them.
|
Informational message; no solution is needed.
|
CLFRL0050W: Failed to transform URL encoder from .
|
This warning is encountered if UTF-8 encoding is not supported on the server. Dogear will use default encoding to encode the strings.
|
Check the encoding settings of the system and make sure UTF-8 is supported by the system.
|
CLFRL0051E: Internal error deleting link with UID _.
|
This error is encountered if an unexpected exception occurs when Dogear is trying to delete a link with the specified UID in the administrative service.
|
Check if the UID provided is correct. Check the detailed exception message below this error massages in the log file to find the root cause. See the Administering Lotus Connections section of the information center for more details.
|
CLFRL0052E: Error getting subscription on person .
|
This error is encountered if an unexpected SQL exception occurs when trying to get a list of people who have a specified person in their watchlist
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0055E: Error getting url ids.
|
This error is encountered if an unexpected SQL exception occurs when trying to get a batch of URL ids.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0056E: Dogear JSP tag error. Error message: .
|
This error is encountered if an unexpected exception is propagated to the UI tier of the feature.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRL0057E: Error getting tag set counts person .
|
This error is encountered if an unexpected SQL exception occurs when trying to get tag set counts for the specified person.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0058E: Error getting link count for person .
|
This error is encountered if an unexpected SQL exception occurs when trying to get link count for the specified person in the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0061E: Error getting link count.
|
This error is encountered if an unexpected SQL exception occurs when trying to get link count in the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0062E: Error registering MBean.
|
This error is encountered if an unexpected JMX exception occurs when trying to register MBean during Dogear feature initialization.
|
Check the detailed exception message in the log file to find the root cause. See the Administering Lotus Connections section of the information center for more details.
|
CLFRL0063W: Unable to retrieve a favicon from .
|
This warning is encountered if Dogear fails to retrieve a favicon from the specified location.
|
Check the location and make sure the favicon exists. If it does not exists, check your favicon settings in the dogear-config-node.xml or try restart the node. If the warning persists, reset the favicons storage. See the Administering Lotus Connections section of the information center for more details.
|
CLFRL0066E: Error getting inbox links for subscriptions .
|
This error is encountered if an unexpected SQL exception occurs when trying to get link for a user's watchlist in the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0067E: An error occurred marking lock file to keep alive -.
|
This error is encountered if an unexpected IO exception occurs when trying to mark the lock file as alive.
|
No action is required if this error does not persist. If the problem still continues, check disk permissions for the WebSphere Application Server process, also check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRL0068E: Error getting intersection link count for tags and person .
|
This error is encountered if an unexpected SQL exception occurs when trying to get intersection link count for the specified tags for the specified person in the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere: The custom dependency checker rules directory you specified cannot be found, or does not contain all the required files. If you wish to continue, the installer will use the default dependency checker rules directory. Otherwise, cancel the install and supply a different location for the custom dependency checker rules directory. Application Server to verify the database connection.
|
CLFRL0069E: Error creating url .
|
This error is encountered if an unexpected SQL exception occurs when trying to insert a URL to the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0070E: Error retrieving full links for .
|
This error is encountered if an unexpected SQL exception occurs when trying to get links with the specified ids in the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0071E: An error occurred while loading the index searcher for .
|
Dogear runs the indexing service as a background task. This error is encountered if an unexpected exception occurs when loading the index searcher from the specified directory.
|
No action is required if this error does not persist. If this error continues, you may check the detailed exception message below this error message in the log file to find the root cause. If restarting the feature does not resolve and the index appears corrupt or is unusable you may use the Dogear administrative service to reset the indexing task. See the Administering Lotus Connections section of the information center for more details.
|
CLFRL0074E: Error getting links for ft index queue, startpos= and count of .
|
This error is encountered if an unexpected SQL exception occurs when trying to get links in the link processing queue from the specified start position with the specified count.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0077E: Error getting tag counts for prefix and limit .
|
This error is encountered if an unexpected SQL exception occurs when trying to get tag counts for the specified prefix with the specified limit.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0080E: Error getting union links for tags and person .
|
This error is encountered if an unexpected SQL exception occurs when trying to get union links for the specified tags for the specified person in the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0081W: Failed to get favicon for host {0}. Use blank image.
|
This warning is encountered if the server had trouble caching a favicon for the specified URL.
|
If this warning only occurs on some URLs, then no action is required - this is normal. If this warning occurs on all URLs, check that the server can make outbound HTTP requests. You may need to setup an outbound proxy if the server is in a protected zone. Also check that the server process can write to the favicon cache storage on disk.
|
CLFRL0083E: An error occurred detecting or removing an obsolete lock file - .
|
This error is encountered if an unexpected IO exception occurs when checking if a lock file is active and/or removing it if obsolete.
|
No action is required if this error does not persist. If this error continues, you may need to stop the effected node, delete the file by hand, and restart the node. This file is located in the same directory as your full text index. See the Administering Lotus Connections section of the information center for help determining that location. If the problem still continues, check disk permissions for the WebSphere Application Server process, also check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRL0084E: Error getting person counts for url.
|
This error is encountered if an unexpected SQL exception occurs when trying to get person counts for a URL.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0085E: Error getting popular tag for url .
|
This error is encountered if an unexpected SQL exception occurs when trying to get popular tags for the specified URL.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
CLFRL0086E: Attempt by to create link for .
|
This error is encountered when a user is trying to create a link for another person.
|
This action is not allowed and the link will not get created. If it is a malicious user, you can contact or restrict the user.
|
CLFRL0087E: Error updating link .
|
This error is encountered if an unexpected SQL exception occurs when trying to update the specified link in the database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WebSphere Application Server to verify the database connection.
|
|
|
|
CLFRL0251E: Error deleting received notifications of person {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0252E: Error deleting notifications sent by person {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0254E: Error saving notifications.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0255E: Error retrieving full links by url and date for {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0256E: Error getting the notification with id {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0257E: Error deleting notifications on link {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0258E: Error sending notifications from {0} to {1} on bookmarks
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0260E: Invalid link id from user: {0}, linkid: {1}
|
This error is encountered if the link id provided can't mapped to any exiting links belong to the current user, or an unexpected exception occurs when querying database.
|
Check the link id provided is correct. Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0262E: Error deleting the notification with id {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0263E: Error parsing email addresses when sending notifications. Emails: {0}
|
This error is encountered if the email address is invalid or an unexpected exception occurs.
|
Check the detailed exception message below this error message in the log file to find the root cause. Find out if there is a wrong email address, if yes then correct it.
|
CLFRL0264E: Error sending notifications as user {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0265E: Error recording the notification from person {0} to person {1} on link {2}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0266E: Error getting most visited links.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0267E: Error getting notifications on link {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0271E: Service {0} is not correctly configured. Bookmarklet can not point to the correct server if attributes "enabled" and "href" are not set in the configure file. Please check Lotus Connections configure file.
|
Lotus Connections configuration file has something wrong.
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the configure file is correct.
|
CLFRL0276E: Failed to parse Lotus Connections configure file.
|
Lotus Connections configuration file has something wrong
|
Check the detailed exception message below this error message in the log file to find the root cause. Check the configure file is correct.
|
CLFRL0279E: Failed to get and parse the profile for user {0}.
|
This error is encountered if an unexpected exception occurs when getting user photo from profiles.
|
Check the detailed exception message below this error message in the log file to find the root cause.
|
CLFRL0280E: Error getting recently received notifications of user {0}.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0282E: Error getting the number of received notifications of user {0}.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0282E: Error getting the number of received notifications of user {0}.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0283E: Error getting received notifications of user {0}.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0285E: Error sending notification from {0} to {1} on bookmarks {2}
|
This error is encountered if an unexpected exception occurs when sending notifications.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0286E: Error parsing email addresses when sending notifications. Emails: {0}
|
This error is encountered if the email address is invalid or an unexpected exception occurs.
|
Check the detailed exception message below this error message in the log file to find the root cause. Find out if there is a wrong email address, if yes then correct it.
|
CLFRL0287E: Invalid link id from user: {0}, linkid: {1}
|
This error is encountered if the link id provided can't mapped to any exiting links belong to the current user, or an unexpected exception occurs when querying
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0289E: Error getting schema version from database.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0291E: Error updating person {0} with new locale {1}
|
User locale is saved when he/she logs on. This error is encountered if a SQL exception occurs when writing database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0308E: Error getting received notifications of user {0}, filtered by tag union. Tags: {1}.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0313E: Error getting received notifications of user {0}, filtered by tag intersection. Tags: {1}.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0329E: Error getting the number of received notifications of user {0}, filtered by tag union. Tags: {1}.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0335E: Error getting the number of the most notified links
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0336E: Error getting links for full-text index queue, startpos= {0}
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0344E: Error getting notifications by url and date.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|
CLFRL0345E: Error getting the number of received notifications of user {0}, filtered by tag intersection. Tags: {1}.
|
This error is encountered if a SQL exception occurs when querying database.
|
Check the detailed exception message below this error message in the log file to find the root cause and make sure the database connection is ready. Use the “Test Connections” in WAS to verify the database connection.
|