Home
Search error messages
Use the codes included in the error messages generated by IBM Lotus Connections to identify problems with search and find solutions. The following search error messages are generated by Lotus Connections:
Search error messages
Message Cause Solution CLFRW0001I: Attempting to load dictionaries from this path {0} Dictionaries are being loaded from the specified path. Informational message; no solution is needed. CLFRW0002E: An error occurred during JFrostAnalyzer returning tokenStream. Analyzing content for indexing or for a search query failed. Check that the file system where the search dictionaries are installed is still intact and that all the enabled dictionaries are available. CLFRW0003E: An error occurred while loading a dictionary with this information: locale {0}, location {1} The dictionary could not be loaded from the specified location. Check that the dictionary exists at the specified location. If not, check configuration settings in the search-config.xml file. CLFRW0004E: There is no dictionary available in memory. Failed to load IBM LanguageWare dictionary. Check the search-config.xml file to ensure that the configuration is correct, and check that the dictionaries are installed in the specified CLFRW0005E: An error occurred when trying to get language ID A LanguageWare exception has been thrown. An error occurred while identifying the language, content will be indexed in the default language. Check that the LanguageWare dictionaries and resources are available. CLFRW0006E: An error occurred during initialization of JFrostTokenizer. The analysis of content for indexing or for a search query failed. Check that the file system where the search dictionaries are installed is still intact and that all the enabled dictionaries are available. CLFRW0007I: using the StandardTokenizer for the TokenStream The analysis of content for indexing or for a search query failed. Check that the file system where the search dictionaries are installed is still intact and that all the enabled dictionaries are available. CLFRW0009E: Error during createStd function when parsing the content An error has occurred during the lemmatization process, which runs during the parsing of index terms when going through the analyzer. If you encounter this error message frequently, contact Customer Support. CLFRW0010I: using the JFrostTokenizer for the TokenStream The custom analyzer is using a special tokenizer written for search that is used during indexing for extracting index terms from text. Informational message; no action is required. However, if this message occurs frequently, contact Customer Support. CLFRW0012E: An error occurred during identifying languages A LanguageWare exception has been thrown. An error occurred when identifying the search language, content will be indexed in the default language. Check that the LanguageWare resources are available. CLFRW0013I: The following dictionary {0} has been cached to memory. The specified dictionary has been saved in memory. Informational message only; no action is required. CLFRW0014I: This current session belonging to the user with login id {0}, has expired. The user session has become invalid. Log in again. Informational message only; no action is required. CLFRW0015I: Creating a new session for user with login id {0} A new session has been created for the specified user. Informational message only; no action is required. CLFRW0016E: Could not retrieve details for the user with login ID: {0} due to an exception. The exception occurred when retrieving the details via the virtual member manager directly: {1} There was a problem retrieving details for the user with the specified login ID from services. Check that services is configured correctly. CLFRW0017E: An error occurred when handling a call to the service configuration API. See nested exception for full details. The LotusConnections-config.xml file might be corrupted. Check that LotusConnections-config.xml file is valid and correctly formatted. CLFRW0018I: The maximum index size was not specified. Defaulting to a maximum index size {0} A maximum index size was not specified. The maximum index size is being set to the default. Informational message; no solution is needed. CLFRW0019I: Skipping indexing the {0} service. Is this service configured and running? The specified service was not indexed. Check that the specified service is configured and running. CLFRW0020E: Task cannot be fired as it is already pending. A scheduling error occurred because two tasks are trying to fire at the same time. Check the task configuration. CLFRW0021E: The specified user calendar is not valid. The IBM WebSphere Application Server installation might be corrupt. Check that WebSphere Application Server has been correctly installed. Check the fix pack level. CLFRW0022E: Error loading security.xml to retrieve J2C authentication aliases. The security.xml file could not be loaded to retrieve J2C authentication aliases. This error occurs if Java™ 2 security is enabled. Check if Java 2 is enabled, and disable it if it is. CLFRW0023E: Internal Error: Search indexer creation failed. The specified indexing class could not be found or has an error. Reinstall the search feature. CLFRW0024I: Lotus Connections indexing task is an Indexing operation The indexing task that is starting is an indexing operation. Informational message; no solution is needed. CLFRW0025I: Dictionaries successfully loaded. The LanguageWare dictionaries specified in the config.xml file have loaded successfully. Informational message; no solution is needed. CLFRW0026E: Internal Error: The specified notification sink class is not valid. The specified notification sink class is not valid. This error is thrown by internal WebSphere Application Server code. Check that the search application has been correctly installed. CLFRW0027E: Error Indexing component {0} for search. Search was unable to crawl the seedlist for the specified application. Check that the specified application is available and that the seedlist can be authenticated against using the Lotus Connections admin alias. CLFRW0029E: The user calendar specifier is not valid. Scheduling intervals are calculated using a Cron-based scheme. A cron-based interval is formatted as a list of term expressions, separated by spaces or tabs, with each term representing an element of the time. The element describes the valid values for that term. This error occurs if the calendar period uses values that are not valid. Check that the scheduling intervals are specified correctly. CLFRW0030I: Finishing index optimization. Index optimization is being completed. Informational message; no action is required. CLFRW0031I: Finishing indexing service. Indexing has completed. Informational message; no action is required. CLFRW0032E: The Notification Sink object failed to fire. Check that the Lotus Connections Search application has been installed correctly. The Notification Sink object did not start up. This error message is encountered if JNDI names have been changed on the server. Check that the search application has been correctly deployed. CLFRW0033W: Error closing the index. Lock may still be active. An error occurred while releasing the lock on the index This should be resolved next time indexing commences. However, if the problem persists, contact your administrator. CLFRW0034E: Error reading or writing to the index Please check permissions and capacity. Error reading or writing to the index The disk might be full or there might be problems with the permissions. Check permissions and capacity. CLFRW0035E: Task is not valid and cannot be fired. A scheduling error occurred because the task is not valid. Check that the task is configured correctly. CLFRW0036E: Error loading the password for the J2C authentication alias {0}. Please check that the alias is correctly configured. The J2C authentication alias is used when connecting to other Lotus Connections services for authenticating when indexing content. This error occurs when the alias has not been correctly configured. Check the security settings in the WAS admin console to verify that the J2C credentials supplied for the admin user are correctly configured. CLFRW0038E: Error loading Search settings 'search-config.xml'. Please check the validity of your Lotus Connections Search installation. The settings contained in the search-config.xml file could not be loaded or found. Check that the search application has been correctly installed. CLFRW0039I: Lotus Connections indexing task is an Optimize operation The indexing task that is starting is an optimize operation. Informational message; no action is required. CLFRW0040I: Starting index optimization. Index optimization is starting. Informational message; no action is required. CLFRW0041E: The specified calendar period is not valid. Scheduling intervals are calculated using Cron-based calendar periods. A cron-based interval is formatted as a list of term expressions, separated by spaces or tabs, with each term representing an element of the time. The element describes the valid values for that term. This error occurs if the calendar period uses values that are not valid. Check that the calendar period is valid. CLFRW0043E: Error loading dictionary exception {0} The specified dictionary could not be found or loaded. Check the dictionary settings for the specified language in the search-config.xml file and make sure that a dictionary for the specified language exists. CLFRW0044I: Using standard analyzer The standard analyzer is being used. Informational message; no action is required. CLFRW0045E: An error occurred while calling remote method. An error occurred while calling the task EJB. Check the log files for more details. CLFRW0046W: Error adding facet information for document {0}. An error occurred with one of the index subdirectories. It might have been deleted or moved. Check that there is a called facet in the index If not, your index has become invalid and you need to restore the backup of the index. CLFRW0047W: There are no services installed and properly configured to index. All of your indexing services have been uninstalled. Check that your services are enabled and available to index. CLFRW0048E: The search index has become corrupt. Please check the index The index could not be loaded. Check that the where the index is located can be reached. You might need to delete and recreate your index or reload a backup. CLFRW0049E: Internal Error: The created TaskInfo object is not valid. The task information object created is not valid. This is an internal error thrown by WebSphere Application Server. Check that the search application has been correctly installed. CLFRW0050I: Starting indexing service. Indexing has begun. Informational message; no action is required. CLFRW0051E: The Lotus Connections search scheduler is not available. A scheduler resource called LotusConnectionsScheduler needs to be created on the Search server. This error message is encountered when the scheduler resource cannot be found. Check under Resources/Schedulers in the WAS admin console to verify that the LotusConnectionsScheduler resource has been created. CLFRW0052I: Search indexing task {0} successfully created/updated. A new search indexing task has been created. Informational message; no action is required. CLFRW0053E: JNDI naming exception caught. Connections Search application has been incorrectly deployed. The Lotus Connections Search application has been incorrectly deployed. One of the Enterprise Java Beans could not be found using its JNDI name. Redeploy the Lotus Connections Home page application. If the problem persists, contact your system administrator. CLFRW0054W: There is an unknown WPLC field type: {0} The WPLC field is not known. The information in the WPLC field will not be indexed. Contact Customer Support. CLFRW0055W: Tag {0} in entry {1} is empty The tag in the specified entry is empty. Informational message; no action is required. CLFRW0056E: Error in XML parser for this URL: {0} There is an error in the XML feed generated by the specified URL. Check the log files for errors generated by the specified URL. CLFRW0058E: Fatal error in XML parser for this URL: {0} There is a fatal error in the XML feed generated by the specified URL. Check the log files for errors generated by the specified URL. CLFRW0059W: Warning in XML parser for this URL: {0} There is a warning in the XML feed generated by the specified URL. Check the log files for warnings generated by the specified URL. CLFRW0060E: Input-output exception with this URL: {0} An error occurred with the specified URL. Check that you have added a user with the admin role for this component, and that you have provided correct J2C credentials for this user. Also, verify that the specified URL is accessible from this machine. CLFRW0061I: Parsed {0} entries from feed. The specified number of entries were parsed.in the last seedlist. Informational only; no action is required. CLFRW0062W: There is an unknown WPLC field identifier: {0} The seedlist is invalid. It contains a WPLC field with no identifier. Report this problem to Customer Support. CLFRW0063E: SAX parser error. An error occurred while parsing the seedlist. Check that the seedlist is available and that the user credentials are correct. Also, verify that there is no firewall between the search server and the service being indexed. CLFRW0064W: An error occurred while parsing this query: {0} The search query might contain invalid characters or have an unusual format. Report this problem to Customer Support. CLFRW0065E: An error occurred while loading dictionary from "{0}" with locale "{1}". The dictionary for the specified locale could not be loaded from the specified location. Verify that the dictionary for the corresponding locale exists and that it exists in the specified location. CLFRW0067W: An error occurred trying to open the sorted document collector, continuing with the default collector. There was a problem with the sorted document collector. Documents will be returned sorted by default relevance rather than custom sort. If this problem persists, contact Customer Support. CLFRW0068W: A Directory Services error occurred while retrieving groups for user {0}. There was a problem retrieving groups for the specified user from services. Check the logs to see if there is a problem with services. Also check that your LDAP is up and running. CLFRW0069E: An error occurred while loading the search index from {0}. The index is missing or corrupt. Restore a backup index or delete your index and reindex. CLFRW0070W: An error occurred while trying to retrieve the URL for service {0} The person business card is not available for search results. Check the LotusConnections-config.xml file to ensure that the person tag service is enabled. Verify that the Profiles service is running. CLFRW0071W: An error occurred while retrieving groups and communities for user {0} from services. There was a problem retrieving groups and communities for the specified user from services. Check the logs to see if there is a problem with services. CLFRW0072I: The user with login id {0} , has an existing session. The user already has an existing session. Informational only; no action is required. CLFRW0073E: Problem parsing retrieved maximum index size {0}.Defaulting to a maximum index size {1} The maximum index size is not valid. Check the maximum index size specified in the search-config.xml file. CLFRW0083E: The Search scheduler was not found. If you intend to use the search server for scheduled indexing, and you see this message, scheduled indexing will not work. Reinstall or refederate your node. CLFRW0087E: An error occurred instantiating search task service. There is a problem starting some services that are associated with the search MBean. Check for errors earlier in the logs for details. CLFRW0089I: The following optimize task has been successfully added.{0} The task defined in wsadmin has been added to the schedule. Informational only; no action is required. CLFRW0091I: The task with the name {0} was unsuccessfully deleted. The deletion of the specified task did not succeed. Ensure that you have the correct task name, then retry the command. CLFRW0092I: The following optimize task was not successfully added.{0} The optimize task defined by the user was not successfully scheduled. Check the log for additional errors or warnings that indicate why the task was not added. CLFRW0093I: The following indexing task has been successfully added.{0} The indexing task specified by the user was added to the schedule. Informational only; no action is required. CLFRW0094I: The task with the name {0} was successfully deleted. The task specified by the user has been successfully removed from the schedule. Informational only; no action is required. CLFRW0095E: An error occurred in the search task persistence service. A general error occurred when attempting a database operation on the Home page database. Check the logs for specific database errors. CLFRW0096I: The following indexing task was not successfully added.{0} The indexing task specified by the user was not added to the schedule. Check that there isn't already an existing task with the same name, then try again. CLFRW0097E: An error occurred while accessing database. The search service encountered an error while connecting to its backend database. Check the logs for SQL errors. Test the connection using the WebSphere Administration Server Integrated Solutions Console, and refer to the system out log for additional information regarding database errors. CLFRW0098E: Problem retrieving scheduled task definitions. There was a problem reading from the WebSphere Application Server scheduled task definition tables for search. Refer to the stack trace. Check your J2C authentication credentials. CLFRW0111W: Attempted to index an entry with no link. Entry Id was {0}. A seedlist entry was generated with no link to the content. The entry will not be indexed. If this happens frequently, contact Customer Support. CLFRW0112W: Failed to delete entries from the index for the url {0}. A deletion request was made for the specified entry but that entry was not found in the index. If this happens frequently, contact Customer Support. CLFRW0113E: No response to this seedlist URL {0}. Check the Lotus-Connections-config.xml interservice URLs or search-config.xml seedlist URL override. If the URLs are correct , verify that the target server is running. An error occurred when trying to connect to the specified URL. Check that the URL is correct. For more information, see Verifying search seedlists. CLFRW0114E: Unexpected response code to the secured seedlist servlet request using this URL {0}. The code returned was {1}. An error occurred when connecting to the given URL. The response code returned by the server was not recognized. Make sure that the service you were trying to connect to is up and running. For more information, see Verifying search seedlists. CLFRW0115E: Access to the secured seedlist servlet using this URL {0} is not permitted for the specified user .Check that either the connectionsAdmin J2C authentication alias details (or the feature''s search J2C authentication alias override if it is used) identifies the user mapped to the searchAdmin user for the Connections feature application serving the seedlist. The specified user does not have access to the secured seedlist servlet using the specified URL. Check the connectionsAdmin J2C authentication alias details (or the feature‘s search J2C authentication alias override, if it is used) to confirm that it identifies the user mapped to the searchAdmin user for the feature serving the seedlist. For more troubleshooting information, refer to Verifying search seedlists. CLFRW0116I: The response code returned is HTTP OK. The seedlist request is working. This means that the inter-service HTTP communication necessary for indexing for this specific feature is currently working. (This message is only logged if the logging is set to finest for a particular class.) Informational message; no action is required. CLFRW0117E: Failed to authenticate against a secured seedlist servlet using this URL {0}. Check the connectionsAdmin J2C authentication alias details (or the feature‘s search J2C authentication alias override if it is used). An authentication error occurred while requesting information from one of the other services. The specified seedlist URL could not be reached because of an authentication error. Attempt to go to the URL in a browser. When challenged for authentication credentials, use the J2C authentication for the connectionsAdmin. If that does not work, fix your J2C connectionsAdmin authentication alias. CLFRW0118E: An error occurred while retrieving facets from a facet collector. There was a problem reading the part of the index that handles social facet information (related tags, people, dates, and features). Ensure that the index can be read. If the problem persists, you might have to delete the index and reindex. CLFRW0119W: JNDI naming exception caught when performing a lookup for resource with JNDI name {0}. This is not a fatal error. See subsequent log entries for details. This exception typically occurs when the search application could not find specified resources, usually a scheduler resource, which means that the search server is unable to perform indexing. Your deployment might have been configured with advanced custom configurations for search indexing. CLFRW0120W: XML Task definitions migration failed. Check logs for detailed explanation. There was a problem migrating the previous search schedule defined in the migrated configuration file. Recreate your indexing schedule using the appropriate search service commands. CLFRW0121W: Could not find the WebSphere scheduler resource with JNDI name {0}. Scheduled indexing of Lotus Connections services will not run on this server. This exception typically occurs when the search application could not find specified resources, usually a scheduler resource, which means that the search server is unable to perform indexing. Your deployment might have been configured with advanced custom configurations for search indexing. CLFRW0123W: Could not find the WebSphere scheduler resource with JNDI name {0}. Scheduled indexing of Lotus Connections services will not run on this server. Skipping schedule task definitions pre-processing steps. This is a warning issued on startup to indicate that the preparation of search task definitions is skipped because the Search Scheduler cannot be found. Informational only; no action is required. CLFRW0124I: The indexing task with name {0}, was not disabled successfully. The disable indexing command did not work for the specified task. Ensure that the specified indexing task exists. Check the logs for further information. CLFRW0125I: All tasks successfully migrated from search-config.xml to search database. The migration of your previous indexing schedule from 2.0.1 has been successful. Informational only; no action is required. CLFRW0126I: The indexing task with name {0}, was not enabled successfully. The enable indexing command for the specified task was not successful. Ensure that the specified indexing task exists. Check the logs for further information. CLFRW0127I: The indexing task with name {0}, was disabled successfully. The disable indexing command for the specified task was successful. Informational only; no action is required. CLFRW0128I: No tasks to be migrated from search-config.xml to search database. There are no task definitions found in the search-config.xml file that have to be migrated to the Home page database. Informational only; no action is required. CLFRW0129W: None of the tasks defined in the search-config.xml were successfully to the search database. This is a warning message. Informational only; no action is required. CLFRW0130I: The indexing task with name {0}, was enabled successfully. The enable indexing command for the specified task was successful. Informational only; no action is required. CLFRW0131W: Some tasks were not successfully migrated from search-config.xml to the search database. This is a warning message. Informational only; no action is required. CLFRW0132I: Stopping crawl of seedlist because the current indexing task {0} has been disabled. This message is displayed in response to the SearchService.disableIndexingTask command. The indexing operation will shortly be complete. Informational only; no action is required. CLFRW0133E: Problem accessing services. There is a problem looking up the user details, user groups, or the user communities. Check the logs for Profiles and Communities if they are installed. Check that the LDAP is up and running. Check communication between the search feature and the Profiles and Communities features. CLFRW0135W: An error occurred while retrieving user {0} from services. There was a problem when attempting to get information for the specified user from Profiles or the LDAP. Ensure that Profiles is up and running, and that the LDAP is up and running. CLFRW0136E: An error occurred setting up the Wikis ACL parser, private wikis will not be shown in the search results for any user. There was a problem loading the Wikis ACL parser. Restart the search server. If this happens again, contact Customer Support. CLFRW0137E: IOException thrown when instantiating a FacetsCollector object. There was an error reading or writing to the facets index. Check permissions on the Check that the index is readable. This message is accompanied by a stack trace with more details about the error. CLFRW0138W: An error occurred while retrieving communities for user {0} from services. There was a problem when attempting to get information for the specified user from Communities. Ensure that Communities is up and running. Check the Communities log for errors. CLFRW0139E: InvalidCategoryException thrown when instantiating a FacetsCollector object. Your facets index has become corrupt. Delete the index and start again. CLFRW0140W: A Directory Services error occurred while retrieving Communities for user {0}. Communities is not installed or configured properly. Check the system.out log for your Communities server for relevant errors. CLFRW0144W: Document Conversion Service was unable to download file {0}. The file with the specified ID could not be downloaded. Check the logs for errors. Ensure that the connectionsAdmin alias or search Files alias has the correct permissions. There might also be an issue with the Files service. CLFRW0146E: Problem re-enabling all task definitions on application startup. It is the designed behavior of the search application that all previously disabled indexing tasks are enabled on restart. Try to explicitly re-enable the tasks one-by-one. If this does not work, try deleting and recreating the scheduler. If the problem persists, check the logs. Otherwise, contact Customer Support. CLFRW0150E: CorruptIndexException thrown when closing open resources. On closing open resources, search found that the index has been corrupted. Delete your index and start again. CLFRW0151E: Cannot access search configuration file from this class {0} The search configuration provider could not load the search-config.xml or LotusConnections-config.xml files. Ensure that the configuration XML files exist and are readable. CLFRW0154E: IOException thrown when closing open resources. There was an error reading or writing to the file system while closing the indexes. Ensure that you can read and write to the index directory. Ensure that the file system has adequate disk space. CLFRW0156W: HTTP Error encountered while trying to download {0} for the Document Conversion Service. A HTTP error occurred when trying to download a file for conversion. Check the file server. CLFRW0157E: The version of the index does not match the release version of Search The index version is not compatible with the version of search. Delete and rebuild your index. CLFRW0158I: Stopping the indexing task with name {0} because it has been disabled. Logged in response to the administrator running the SearchService.disableIndexingTask command. Informational only; no action is required. CLFRW0159W: Document Conversion Service has detected out of date files in {0}, deleting from folder. The document conversion service has determined that some temporary files have been left on the file system during file content indexing, and they will be deleted. No solution is currently available. CLFRW0160I: Document Conversion Service skipping conversion of file {0}, file exceeds maximum attachment size. Logged when a file attachment in Files exceeds the threshold for a file that can be downloaded and indexed. Informational only. The maximum size is configurable via the search configuration administrative interface using the SearchCellConfig.setMaximumAttachmentSize command. CLFRW0163E: Unable to download the file for conversion. The file could not be downloaded. Check the file service. If the problem persists, contact Customer Support. CLFRW0167W: Document Conversion Service has encountered a database error. A database error has occurred. Check your database connection. CLFRW0168W: Document Conversion Service has encountered that the {0} service does not appear to be running. Suppressing further warning messages. The specified service does not appear to be running, the document conversion service will end, and try again when the specified service is indexed again. Check that the named service is running. CLFRW0175E: Unable to convert the file. File could not be converted. Ensure that all allowed MIME types are valid. If the problem persists, contact Customer Support. CLFRW0185I: Not starting indexing as the task {0} has been disabled. A scheduled task will not run because an administrator has disabled the specified indexing task. Informational message; no action is required. CLFRW0186E: Error when attempting to retrieving the list of installed Connections components. The LotusConnections-config.xml file may have become corrupted. Check the Lotus Connections configuration files. This may require a backup or restore of a previous Lotus Connections configuration. CLFRW0189E: Unable to read the file for conversion. The file could not be read for conversion. Check the file service. If the problem persists, contact Customer Support. CLFRW0190E: Unable to locate DCS. Unable to read the variable that contains the location of Stellent binaries. Reinstall. The WebSphere Application Server variable is not set up properly. CLFRW0194W: Document Conversion Service: Service has been released, and will be started again at next index. The document conversion service has stopped, and will resume at next index. Informational message; no action is required.
Related tasks
Configure file attachment indexing settings