Event log messages
The following sections contain a complete listing of all ERROR, INFO, and WARN event-log messages that appear in the Event Log of the IBM® StoredIQ® console.
ERROR event log messages
The following table contains a complete listing of all ERROR event-log messages, reasons for occurrence, sample messages, and any required customer action.
| Event number | Reason | Sample message | Required customer action |
|---|---|---|---|
| 1001 | Harvest was unable to open a socket for listening to child process. | Harvest could not allocate listen port after <number> attempts. Cannot kickstart interrogators. (1001) | Log in to UTIL and restart the application server. Restart the data server. Contact customer support. |
| 9083 | Unexpected error while it is exporting a volume. | Exporting volume 'dataserver:/mnt/demo-A' (1357) has failed (9083) | Contact Customer Support. |
| 9086 | Unexpected error while it is importing a volume | Importing volume 'dataserver:/mnt/demo-A' (1357) failed (9086) | Contact Customer Support. |
| 15001 | No volumes are able to be harvested in a job. For instance, all of the mounts fail due to a network issue. | No volumes harvested. (15001) | Make sure IBM StoredIQ still has appropriate permissions to a volume. Verify that there is network connectivity between the data server and your volume. Contact Customer Support. |
| 15002 | Could not mount the volume. Check permissions and network settings. | Error mounting volume <share><start-dir> on server <server-name>. Reported <reason>. (15002) | Make sure that the data server still has appropriate permissions to a volume. Verify that there is network connectivity between the data server and your volume. Contact Customer Support. |
| 15021 | Error saving harvest record. | Failed to save HarvestRecord for qa1:auto-A (15021) | Contact Customer Support. This message occurs due to a database error. |
| 17501 | Generic retention discovery failed in a catastrophic manner. | Generic retention discovery fatal failure: <17501> | Contact Customer Support. |
| 17503 | Generic retention discovery creates volume sets associated with primary volumes. When that fails, IBM StoredIQ sends this message. This failure likely occurred due to database errors. | Error creating/loading volumeset for <server>:<share> | Contact Customer Support. |
| 17505 | Unable to query object count for a discovered volume due to a database error. | Unable to determine object count for <server>:<share> | Contact Customer Support. |
| 17506 | Generic retention discovery could not create discovered volume. | Error creating volume <server>:<share:> | Contact Customer Support. |
| 18001 | SMB connection fails. | Windows Share Protocol Exception when connecting to the server <server-name> : <reason>. (18001) | Make sure IBM StoredIQ still has appropriate permissions to a volume. Verify that there is network connectivity between the data server and your volume. Contact Customer Support. |
| 18002 | The SMB volume mount failed. Check the share name. | Windows Share Protocol Exception when connecting to the share <share-name> on <server-name> : <reason>. (18002) | Verify the name of the server and volume to make sure that they are correct. If this message persists, then contact Customer Support. |
| 18003 | There is no volume manager. | Windows Share Protocol Exception while initializing the data object manager: <reason>. (18003) | Contact Customer Support. |
| 18006 | Grazer volume crawl threw an exception. | Grazer._run : Unknown error during walk. (18006) | Verify the user that mounted the specified volume has permissions equivalent to your current backup solution. If this message continues, contact Customer Support. |
| 18021 | An unexpected error from the server prevented the harvest to reach the end of the activity stream on the NewsGator data source that is harvested. The next incremental harvest attempts to pick up from where the current harvest was interrupted. | Unable to fetch trailing activity stream from NewsGator volume. Will retry in next harvest. (18021) | Check to ensure the NewsGator server has sufficient resources (disk space, memory). It is likely that this error is transient. If the error persists across multiple harvests, contact Customer Support. |
| 18018 | Start directory has escape characters, and the data server is configured to skip them. | Cannot graze the volume, root directory Nunez has escape characters (18018) | Consider turning off escape character checking. |
| 19001 | An exception occurred during interrogator initialization. | Interrogator._init __exception: <reason>. (19001) | Contact Customer Support. |
| 19002 | An unknown exception occurred during interrogator initialization. |
Interrogator.__ init __exception: unknown. (19002) |
Contact Customer Support. |
| 19003 | An exception occurred during interrogator processing. |
Interrogator.process exception (<volumeid>, <epoch>): <reason>. (19003) |
Contact Customer Support. |
| 19004 | An unknown exception occurred during interrogator processing. |
Interrogator.process exception (<volumeid>, <epoch>). (19004) |
Contact Customer Support. |
| 19005 | An exception occurred during viewer initialization. | Viewer.__init__: Exception - <reason>. (19005) | Contact Customer Support. |
| 19006 | An unknown exception occurred during viewer initialization. | Viewer.__init__: Unknown exception. (19006) | Contact Customer Support. |
| 33003 | Could not mount the volume. Check permissions and network settings. | Unable to mount the volume: <error reason> (33003) | Verify whether user name and password that are used for mounting the volume are accurate. Check the user data object for appropriate permissions to the volume. Make sure that the volume is accessible from one of the built-in protocols (NFS, Windows Share, or Exchange). Verify that the network is properly configured for the appliance to reach the volume. Verify that the appliance has appropriate DNS settings to resolve the server name. |
| 33004 | Volume could not be unmounted. | Unmounting volume failed from mount point : <mount point>. (33004) | Restart the data server. If the problem persists, then contact Customer Support. |
| 33005 | Data server was unable to create a local mounting point for the volume. | Unable to create mount_point using primitive.thread-Safe-Makedirs(). (33005) | Restart the data server. If the problem persists, then contact Customer Support. |
| 33010 | Failed to make SMB connection to Windows Share server. | Mounting Windows Share volume failed with the error : <system error message>. (33010) | Verify user name and password that is used for mounting the volume are accurate. Check the user data object for appropriate permissions to the volume. Make sure that the volume is accessible from one of the built-in protocols (Windows Share). Verify that the network is properly configured for the data server to reach the volume. Verify that the data server has appropriate DNS settings to resolve the server name. |
| 33011 | Internal error. Problem accessing local /proc/mounts | Unable to open /proc/mounts. Cannot test if volume was already mounted. (33011) | Restart the data server. If the problem persists, then contact Customer Support. |
| 33012 | Database problems when a volume was deleted. | An exception occurred while working with HARVESTS_ TABLE in Volume._delete(). (33012) | Contact Customer Support. |
| 33013 | No volume set was found for the volumes set name. | Unable to load volume set by its name. (33013) | Contact Customer Support. |
| 33014 | System could not determine when this volume was last harvested. | An error occurred while performing the last_harvest operation. (33014) | Contact Customer Support. |
| 33018 | An error occurred mounting the Exchange share. | Mounting Exchange Server failed : <reason>. (33018) | Verify user name and password that is used for mounting the share are accurate. Check for appropriate permissions to the share. Make sure that the share is accessible. Verify that the network is properly configured for the data server to reach the share. Verify that the data server has appropriate DNS settings to resolve the server name. |
| 33027 | The attempt to connect and authenticate to the IBM FileNet server failed. | Mounting IBM FileNet volume failed : <reason>. (33027) | Ensure the connectivity, credentials, and permissions to the FileNet volume and try again. |
| 33029 | Failed to create the volume as the number of active volume partitions exceeds the limit of 500. | Exceeded maximum number of volume partitions (33029). | Contact Customer Support. |
| 34002 | Could not complete the copy action because the target disk was full. | Copy Action aborted as the target disk has run out of space (34002) | Verify that there is space available on your policy destination and try again. |
| 34009 | Could not complete the move action due to full target disk. | Move Action aborted as the target disk has run out of space.(34009) | Verify that there is space available on your policy destination, then run another harvest before you run the policy. When the harvest completes, try running the policy again. |
| 34015 | The policy audit could not be deleted for some reason. | Error Deleting Policy Audit: <error message> (34016) | Contact Customer Support. |
| 34030 | Discovery export policy is started since it detected the target disk is full. | Production Run action aborted because the target disk has run out of space. (34030) | Create sufficient space on target disk and run discovery export policy again. |
| 34034 | The target volume for the policy could not be mounted. The policy is started. | Copy objects failed, unable to mount volume: QA1.COMPANY. COM:SHARE. (34034) | Ensure the connectivity, login credentials, and permissions to the target volume for the policy and try again. |
| 41004 | The job is ended abnormally. | <job-name> ended unexpectedly. (41004) | Try to run the job again. If it fails again, contact Customer Support. |
| 41007 | Job failed. | [Job name] has failed (41007). | Look at previous messages to see why it failed and refer to that message ID to pinpoint the error. Contact Customer Support. |
| 42001 | The copy action could not run because of parameter errors. | Copy data objects did not run. Errors occurred:<error-description>. (42001) | Contact Customer Support. |
| 42002 | The copy action was unable to create a target directory. | Copy data objects failed, unable to create target dir:<target-directory-name>. (42002) | Check permissions on the target. Make sure the permissions that are configured to mount the target volume have write access to the volume. |
| 42004 | An unexpected error occurred. | Copy data objects terminated abnormally. (42004) | Contact Customer Support. |
| 42006 | The move action could not run because of parameter errors. | Move data objects did not run. Errors occurred:<error-description>. (42006) | Contact Customer Support. |
| 42007 | The move action was unable to create a target directory. | Move data objects failed, unable to create target dir:<target-directory-name>. (42007) | Check permissions on the target. Make sure the permissions that are configured to mount the target volume have write access to the volume. |
| 42009 | An unexpected error occurred. | Move data objects terminated abnormally. (42009) | Contact Customer Support. |
| 42017 | An unexpected error occurred. | Delete data objects terminated abnormally. (42017) | Contact Customer Support. |
| 42025 | The policy action could not run because of parameter errors. | Policy cannot execute. Attribute verification failed. (42025) | Contact Customer Support. |
| 42027 | An unexpected error occurred. | Policy terminated abnormally. (42027) | Contact Customer Support. |
| 42050 | The data synchronizer could not run because of an unexpected error. | Content Data Synchronizer synchronization of <server-name>: <volume-name> failed fatally. | Contact Customer Support. |
| 42059 | Invalid set of parameters that are passed to discovery export policy. | Production Run on objects did not run. Errors occurred: The following parameters are missing: action_limit. (42059) | Contact Customer Support. |
| 42060 | Discovery export policy failed to create target directory for the export. | Production Run on objects (Copying native objects) failed, unable to create target dir: production/10. (42060) | Verify that the discovery export volume has write permission and re-execute policy. |
| 42062 | Discovery export policy was ended abnormally. | Production Run on objects (Copying native objects) terminated abnormally. (42062) | Contact Customer Support. |
| 42088 | The full-text optimization process failed; however, the index is most likely still usable for queries. | Full-text optimization failed on volume <volume-name> (42088) | Contact Customer Support. |
| 45802 | A full-text index is already being modified. | Time allocated to gain exclusive access to in-memory index for volume= 1357 has expired (45802) | Contact Customer Support. |
| 45803 | The index for the specified volume does not exist. This message can occur under normal conditions. | Index '/deepfs/full-text/volume_index/volume_1357' not found. (45803) | No user intervention is required. |
| 45804 | Programming error. A transaction was never initiated or was closed early. | Transaction of client: node.client.com_ FINDEX_ QUEUE_ 1357_117251522 _3_ 2 is not the writer (45804) | Contact Customer Support. |
| 45805 | The query is not started or expired. The former is a programming error. The latter is normal. | Query ID: 123 does not exist (45805) | No user intervention is required. |
| 45806 | The query expression is invalid or not supported. | Failed to parse 'dog pre\3 bar' (45806) | Revise your full-text query. |
| 45807 | Programming error. A transaction was already started for the client. | Client: node.client.com_ FINDEX_QUEUE _1357_1172515 222_3_2 is already active (45807) | Contact Customer Support. |
| 45808 | A transaction was never started or expired. | No transaction for client: node.client.com_ FINDEX_ QUEUE_1357_ 1172515222_3_2 (45808) | No user intervention is required. The system handles this condition internally. |
| 45810 | Programming error. | Invalid volumeId. Expected: 1357 Received:2468 (45810) | Contact Customer Support. |
| 45812 | A File I/O error occurred while the system was accessing index data. | Failed to write disk (45812). | Try your query again. Contact Customer Support for more assistance if necessary. |
| 45814 | The query expression is too long. | Query: 'a* b* c* d* e*' is too complex (45814) | Refine your full-text query. |
| 45815 | The file that is being indexed is too large or the query expression is too complex. The engine temporarily ran out of memory. | Java heap exhausted while indexing node with ID: '10f4179cd5ff22f 2a6b 79a1bc3aef247 fd94ccff' (45815) | Check the skipped file list in the audit log for files that failed to load due to their sizes. Revise your query expression and try again. |
| 46023 | Tar command failed while it persists full-text data to Windows Share or NFS share. | Failed to back up full-text data for server:share. Reason: <reason>. (46023) | Check disk space and permissions. |
| 46024 | Unhandled unrecoverable exception while persisting full-text data into a .tgz file. | Exception <exception> while backing up fulltext data for server:share (46024) | Contact Customer Support. |
| 46025 | Was not able to delete partial .tgz file after a failed full-text backup. | Failed to unlink incomplete backup image. Reason: <reason>. (46025) | Check permissions. |
| 47002 | Synchronization failed on a query. | Synchronization failed for query '<query-name>' on volume '<server-and-volume> (47002) | Contact Customer Support. |
| 47101 | An error occurred during the query of a full-text expression. | Cannot process full-text expression (Failed to read from disk (45812) (47101) | Restart services and contact Customer Support. |
| 47203 | No more database connections are available. | Database connections exhausted (512/511) (47203) | Contact Customer Support. |
| 47207 | User is running out of disk space. | Disk usage exceeds threshold. (%d) | Contact Customer Support. In rare cases, this message can indicate a program error leaking disk space. In most cases, however, disk space is almost full, and more storage is required. |
| 47212 | Interrogator failed while the system processed a file. The current file is missing from the volume cluster. | Harvester 1 Does not exist. Action taken : restart. (47212) | If the problem persists (that is, the system fails on the same file or type of files), contact Customer Support. |
| 47214 | SNMP notification sender is unable to resolve the trap host name. | Unable to resolve host name nomachine.no where.com (47214) | Check spelling and DNS setup. |
| 50011 | The DDL/DML files that are required for the database versioning were not found in the expected location on the data server. | Database version control SQL file not found. (50011) | Contact Customer Support. |
| 50018 | Indicates that the pre-upgrade database restoration failed, which was attempted as a result of a database upgrade failure. | Database restore is unsuccessful. Contact Customer Support. (50018) | Contact Customer Support. |
| 50020 | Indicates that the current database requirements do not meet those requirements that are specified for the upgrade and cannot proceed with the upgrade. | Versions do not match! Expected current database version: <dbversion>. (50020) | Contact Customer Support. |
| 50021 | Indicates that the full database backup failed when the system attempts a data-object level database backup. | Database backup failed. (50021) | Contact Customer Support. |
| 61003 | Discovery export policy failed to mount volume. | Production policy failed to mount volume. Aborting. (61003) | |
| 61005 | The discovery export load file generation fails unexpectedly. The load files can be produced correctly, but post-processing actions like updating audit trails and generating report files might not complete. | Production load file generation failed. Load files may be produced, but post-processing may be incomplete. (61005) | Contact Customer Support. |
| 61006 | The discovery export load file generation was interrupted because the target disk is full. | Production load file generation interrupted. Target disk full. (61006) | Free up space on the target disk, void the discovery export run and run the policy again. |
| 68001 | The gateway and data server must be on the same version to connect. | Gateway connection failed due to unsupported data server version. | Update your data server to the same build number as the gateway and restart services. If your encounter issues, contact Customer Support. |
| 68003 | The data server failed to connect to the gateway over an extended period. | The data-server connection to the gateway cannot be established. | Contact Customer Support. |
| 8002 | The system failed to open a connection to the database. | Failed to connect to the database (80002) | The "maximum database connections" configuration parameter of the database engine might need to be increased. Contact Customer Support. |
INFO event log messages
The following table contains a complete listing of all INFO event-log messages.
| Event number | Reason | Sample message | Required customer action |
|---|---|---|---|
|
9001 |
No conditions were added to a query. |
Harvester: Query <query name> cannot be inferred because no condition for it has been defined (9001). |
Add conditions to the specified query. |
|
9002 |
One or more conditions in a query were incorrect. |
Harvester: Query < query name> cannot be inferred because of regular expression or other condition error (9002). |
Verify that regular expressions are properly formed. |
|
9003 |
Volume Harvest is complete and explorers are being calculated. |
Volume statistics computation started (9003). |
No user intervention is required. |
|
9004 |
Explorer calculations are complete. |
Volume statistics computation completed (9004). |
No user intervention is required. |
|
9005 |
Query membership calculations started. |
Query inference will be done in <number> steps (9005). |
No user intervention is required. |
|
9006 |
Query membership calculations progress information. |
Query inference step <number> done (9006). |
No user intervention is required. |
|
9007 |
Query membership calculations completed. |
Query inference completed (9007). |
No user intervention is required. |
|
9012 |
Indicates the end of dumping the content of the volume cache. |
Dump of Volume cache(s) completed (9012). |
No user intervention is required. |
|
9013 |
Indicates the beginning of the load process. |
Postprocessing for volume 'Company Data Server:/mnt/demo-A' started (9013). |
No user intervention is required. |
|
9067 |
Indicates load progress. |
System metadata and tagged values were successfully loaded for volume 'server:volume' (9067). |
No user intervention is required. |
|
9069 |
Indicates load progress. |
Volume 'data server: /mnt/demo-A': System metadata, tagged values and full-text index were successfully loaded (9069). |
No user intervention is required. |
|
9084 |
The volume export finished. |
Exporting volume 'data server:/mnt/demo-A' (1357) completed (9084) |
No user intervention is required. |
|
9087 |
The volume import finished. |
Importing volume 'dataserver:/mnt/demo-A' (1357) completed (9087) |
No user intervention is required. |
|
9091 |
The load process was ended by the user. |
Load aborted due to user request (9091). |
No user intervention is required. |
|
15008 |
The volume load step was skipped, per user request. |
Post processing skipped for volume <server>:<vo-lume>. (15008) |
No user intervention is required. |
|
15009 |
The volume load step was run but the harvest step was skipped, per user request. |
Harvest skipped for volume <server>:<vol-ume>. (15009) |
No user intervention is required. |
|
15012 |
The policy that ran on the volume is complete and the volume load can now proceed. |
Volume <volume> on server <server> is free now. Proceeding with load. (15012) |
No user intervention is required. |
|
15013 |
The configured time limit on a harvest was reached. |
Harvest time limit reached for server:share. Ending harvest now. (15013) |
No user intervention is required. |
|
15014 |
The configured object count limit on a harvest was reached. |
Object count limit reached for server:share. Ending harvest now. (15014) |
No user intervention is required. |
|
15017 |
checkbox is selected for nightly load job. |
Deferring post processing for volume server:vol (15017) |
No user intervention is required. |
|
15018 |
Harvest size or time limit is reached. |
Harvest limit reached on server:volume. Synthetic deletes will not be computed. (15018) |
No user intervention is required. |
|
15019 |
User stops harvest process. |
Harvest stopped by user while processing volume dpfsvr:vol1. Rest of volumes will be skipped. (15019) |
No user intervention is required. |
|
15020 |
The harvest vocabulary changed. Full harvest must run instead of incremental. |
Vocabulary for dpfsvr:jhaide-A has changed. A full harvest is recommended (15020). |
Full harvest must be run instead of an incremental harvest. |
|
15022 |
The user is trying to run an ACL-only harvest on a volume that is not a Windows Share or SharePoint volume. |
Permission-only harvest: permission checks not supported for <server>:<share> |
No action is needed as the volume is skipped. |
|
15023 |
The user is trying to run an ACL-only harvest on a volume that was assigned a user list. |
Permission-only harvest: volume <server>:<share> has no associated user list. |
No action is needed as the volume is skipped. |
|
17507 |
Limit (time or object count) reached for generic retention discovery. |
Retention discovery limit reached for <server>:<share> |
Contact Customer Support. |
|
17508 |
Generic retention discovery found no new items for this volume. |
No new items discovered. Post-processing skipped for volume <server>:<share> |
No user intervention is required unless the user is certain that new items must be discovered. |
|
17509 |
Generic retention discovery created a new volume. |
Created new discovered volume <server>:<share> in volume set <autodis-covered volume set name>. |
No user intervention is required. |
|
18004 |
Job was stopped. |
Walker._process File: Grazer Stopped. (18004) |
No user intervention is required. |
|
18005 |
Grazer queue was closed. |
Walker._processFile: Grazer Closed. (18005) |
No user intervention is required. |
|
18016 |
Displays the list of top-level directories that are selected by matching the start directory regular expression. Displays at the beginning of a harvest. |
Choosing top-level directories: <directories> (18016) |
No user intervention is required. |
|
34001 |
Marks current progress of a copy action. |
<volume>: <count> data objects processed by copy action. (34001) |
No user intervention is required. |
|
34004 |
Marks current progress of a delete action. |
<volume>: <count> data objects processed by delete action. (34004) |
No user intervention is required. |
|
34008 |
Marks current progress of a move action. |
<volume>: <count> data objects processed by move action. (34008) |
No user intervention is required. |
|
34014 |
A policy audit was deleted. |
Deleting Policy Audit # <audit id> <policy name> <start time> (34014) |
No user intervention is required. |
|
34015 |
A policy audit was deleted. |
Deleted Policy Audit # <audit id> <policy name> <start time> (34015) |
No user intervention is required. |
|
34031 |
Progress update of the discovery export policy, every 10000 objects processed. |
Winserver:top share : 30000 data objects processed by production action. (34031) |
No user intervention is required. |
|
41001 |
A job was started either manually or was scheduled. |
<jobname> started. (41001) |
No user intervention is required. |
|
41002 |
The user stopped a job that was running. |
<jobname> stopped at user request (41002) |
No user intervention is required. |
|
41003 |
A job is completed normally with or without success. |
<jobname> completed. (41003) |
No user intervention is required. |
|
41006 |
Rebooting or restarting services on the controller or compute node causes all jobs to stop. |
Service shutdown. Stopping outstanding jobs. (41006) |
Rerun jobs after restart if you want the jobs to complete. |
|
41008 |
Database compactor (vacuum) job cannot run while there is database activity. |
Database compactor was not run because other jobs are active (41008). |
Set the database compactor's job schedule so that it does not conflict with long-running jobs. |
|
42005 |
The action completed or was ended. Shows results of copy action. |
Copy complete: <number> data objects copied,<number> collisions found. (42005) |
No user intervention is required. |
|
42010 |
The action completed or was ended. Shows results of move action. |
Move complete: <number> data objects moved,<number > collisions found. (42010) |
No user intervention is required. |
|
42018 |
The action completed or was ended. Shows results of deleted action. |
Copy data objects complete: <number> data objects copied,<number> collisions found. (42018) |
No user intervention is required. |
|
42024 |
The synchronizer was completed normally. |
Content Data Synchronizer complete. (42024) |
No user intervention is required. |
|
42028 |
The action completed or was ended. Shows results of policy action. |
Policy completed (42028). |
No user intervention is required. |
|
42032 |
The action completed or was ended. Shows results of report action. |
<report name> completed (42032). |
No user intervention is required. |
|
42033 |
The synchronizer started automatically or manually with the GUI button. |
Content Data Synchronizer started. (42033) |
No user intervention is required. |
|
42048 |
Reports that the synchronizer is skipping a volume if synchronization is determined not to be required. |
Content Data Synchronizer skipping <server-name>:<volume-name> as it does not need synchronization. 42048) |
No user intervention is required. |
|
42049 |
Reports that the synchronizer started synchronization of a volume. |
Content Data Synchronizer starting synchronization for volume <server-name>:<volume-name> |
No user intervention is required. |
|
42053 |
The policy that was waiting for participant volumes to be loaded before it continues, is now starting. |
Proceeding with execution of <policy-name>. |
No user intervention is required. |
|
42063 |
Report on completion of discovery export policy execution phase. |
Production Run on objects (Copying native objects) completed: 2003 data objects copied, 25 duplicates found. (42063) |
No user intervention is required. |
|
42065 |
A discovery export policy that was held up for want of resources, is now done waiting, and begins execution. |
Proceeding with execution of 'Production case One'. (42065) |
No user intervention is required. |
|
42066 |
A new discovery export run started. |
New run number 10 started for production Production Case 23221. (42066) |
Note the new run number to tie the current run with the corresponding audit trail. |
|
42067 |
Discovery export policy is preparing the audit trail in XML format. It might take a few minutes. |
Production Run producing Audit Trail XML. (42067) |
No user intervention is required. |
|
42074 |
A query or tag was replicated to a member data server successfully. |
Successfully sent query 'Custodian: Joe' to member data server San Jose Office (42074) |
No user intervention is required. |
|
46001 |
The backup process began. Any selected backups in the system configuration screen are run if necessary. |
Backup Process Started. (46001) |
No user intervention is required. |
|
46002 |
The backup process did not complete all its tasks successfully. One or more backup types did not occur. |
Backup Process Failed: <error-description>. (46002) |
Check your backup volume. |
|
46003 |
The backup process completed attempting all the necessary tasks successfully. Any parts of the overall process add their own log entries. |
Backup Process Finished. (46003) |
No user intervention is required. |
|
46004 |
The Application Data backup, as part of the overall backup process, needed to run but did not succeed. |
Application Data backup failed. (46004) |
Check your backup volume. Look at the setup for the Application Data backup. If backups continue to fail, contact Customer Support. |
|
46005 |
The Application Data backup, as part of the overall backup process, needed to run and succeeded. |
Application Data backup finished. (46005) |
No user intervention is required. |
|
46006 |
The Application Data backup, as part of the overall backup process, was not configured. |
Application Data backup not configured, skipped. (46006) |
No user intervention is required. |
|
46007 |
The Harvested Volume Data backup, as part of the overall backup process, needed to run but did not succeed. |
Harvested Volume Data backup failed. (46007) |
Check your backup volume. Look at the setup for the Harvested Volume Data backup. If backups continue to fail, contact Customer Support. |
|
46008 |
The Harvested Volume Data backup, as part of the overall backup process, needed to run and succeeded. |
Harvested Volume Data backup finished. (46008) |
No user intervention is required. |
|
46009 |
The Harvested Volume Data backup, as part of the overall backup process, was not configured. |
Harvested Volume Data backup not configured, skipped. (46009) |
No user intervention is required. |
|
46010 |
The System Configuration backup, as part of the overall backup process, needed to run but did not succeed. |
System Configuration backup failed. (46010) |
Check your backup volume. Look at the setup for the System Configuration backup. If backups continue to fail, contact Customer Support. |
|
46011 |
The System Configuration backup, as part of the overall backup process, needed to run and succeeded. |
System Configuration backup finished. (46011) |
No user intervention is required. |
|
46012 |
The System Configuration backup, as part of the overall backup process, was not configured. |
System Configuration backup not configured, skipped. (46012) |
No user intervention is required. |
|
46013 |
The Audit Trail backup, as part of the overall backup process, needed to run but did not succeed. |
Policy Audit Trail backup failed. (46013) |
Check your backup volume. Look at the setup for the Audit Trail backup. If back-ups continue to fail, contact IBM support. |
|
46014 |
The Audit Trail backup, as part of the overall backup process, needed to run and succeeded. |
Policy Audit Trail backup finished. (46014) |
No user intervention is required. |
|
46015 |
The Audit Trail backup, as part of the overall backup process was not configured. |
Policy Audit Trail backup not configured, skipped. (46015) |
No user intervention is required. |
|
46019 |
Volume cluster backup failed. |
Indexed Data backup failed: <specific error> (46019) |
Contact Customer Support. |
|
46020 |
Volume cluster backup finished. |
Indexed Data backup finished. (46020) |
No user intervention is required. |
|
46021 |
Volume is not configured for indexed data backups. |
Indexed Data backup not configured, skipped. (46021) |
No user intervention is required. |
|
46022 |
Full-text data was successfully backed up. |
Successfully backed up full-text data for server:share (46022) |
No user intervention is required. |
|
47213 |
Interrogator was successfully restarted. |
Harvester 1 is now running. (47213) |
No user intervention is required. |
|
60001 |
The user updates an object on the system. It includes any object type on the data server, including the updating of volumes. |
Query cities was updated by the administrator account (60001). |
No user intervention is required. |
|
60002 |
The user creates an object. It includes any object type on the data server, including the creation of volumes. |
Query cities was created by the administrator account (60002). |
No user intervention is required. |
|
60003 |
The user deletes an object. It includes any object type on the data server, including the deletion of volumes. |
Query cities was deleted by the administrator account (60003). |
No user intervention is required. |
|
60004 |
The user publishes a full-text query set or a query. |
Query cities draft was published by the administrator account (60004). |
No user intervention is required. |
|
60005 |
The user tags an object. It includes a published query, a draft query, or tag. |
Query tagging for cities class was started by the administrator account (60005). |
No user intervention is required. |
|
60006 |
A user restarted services on the data server. |
Application services restart for all data servers was requested by the administrator account (60006). |
No user intervention is required. |
|
61001 |
Concordance discovery export is now preparing the load files. |
Preparing for upload of load file(s). (61001) |
No user intervention is required. |
|
61002 |
Concordance discovery export is ready to upload the load files. |
Load file(s) ready for upload. (61002) |
No user intervention is required. |
|
65000 |
The log file finished downloading. |
Log file download complete (65000) |
No user intervention is required. |
WARN event log messages
The following table contains a complete listing of all WARN event-log messages, reasons for occurrence, sample messages, and any required customer action.
| Event number | Reason | Sample message | Customer action |
|---|---|---|---|
|
1002 |
An Interrogator process failed because of an unknown error. The data object that was processing is skipped. A new process is created to replace it. |
Processing could not be completed on object, interrogator died : <data object name>. (1002) |
Classify the document manually and Contact Customer Support. |
|
1003 |
Interrogator child process did not properly get started. There might be problems to access the volume to be harvested. |
Interrogator terminated before accessing data objects. (1003) |
Try to readd the volume that is harvested. If that fails, contact Customer Support. |
|
1004 |
Interrogator child process was ended because it was no longer responding. The data object that was processing is skipped. A new process is created to replace it. |
Processing was not completed on object, interrogator killed : <data object name>. (1004) |
Contact Customer Support. |
|
6001 |
A user email might not be sent. The mail server settings are incorrect. |
Failed to send an email to user <email address>; check mail server configuration settings (6001). |
Verify that your SMTP server is configured correctly. Make sure that the IP address that is configured for the data server can relay on the configured SMTP server. |
|
8001 |
The database needs to be vacuumed. |
The Database is approaching an operational limit. Please run the Database maintenance task using the Console interface (8001) |
Run the database maintenance task to vacuum the database. |
|
9068 |
Tagged values were loaded, but full-text index loading failed. |
System metadata and tagged values were loaded successfully for volume 'server:volume', but loading the full-text index failed (9068) |
Contact Customer Support. |
|
9070 |
Tagged values and full-text index loading failed. |
Loading system metadata, tagged values and the full-text index failed for volume 'server:volume' (9070) |
Contact Customer Support. |
|
15003 |
The volume mount appeared to succeed, but the test for mount failed. |
Volume <volume name> on server <server name> is not mounted. Skipping. (15003) |
Contact Customer Support. |
|
15004 |
A component cleanup failure on stop or completion. |
[<component>] Cleanup failure on stop. (15004) |
Contact Customer Support. |
|
15005 |
There was a component run failure. |
[<component>] Run failure. (15005) |
Contact Customer Support. |
|
15006 |
Cleanup failed for component after a run failure. |
[<component>] Cleanup failure on abort. (15006) |
Contact Customer Support. |
|
15007 |
A component that is timed out needs to be stopped. |
Component [<component>] unresponsive; autostopping triggered. (15007) |
Try your action again. If this error continues, contact Customer Support. |
|
15010 |
The same volume cannot be harvested in parallel. The harvest is skipped and the next one, if any are in queue, started. |
Volume <volume-name> on server <server-name> is already being harvested. Skipping. (15010) |
No user intervention is required. You might want to verify that the volume harvest is complete. |
|
15011 |
A volume cannot be harvested if it is being used by another job. The harvest continues when the job is complete. |
Volume <volume-name> on server <server-name> is being used by another job. Waiting before proceeding with load. (15011) |
No user intervention is required. |
|
15015 |
Configured harvest time limit is reached. |
Time limit for harvest reached. Skipping Volume v1 on server s1. 1 (15015) |
Reconfigure harvest time limit. |
|
15016 |
Configured harvest object count limit is reached. |
Object count limit for harvest reached. Skipping Volume v1 on server s1 (15016) |
Reconfigure harvest data object limit. |
|
17008 |
Query that ran to discover Centera items ended unexpectedly. |
Centera External Iterator : Centera Query terminated unexpectedly (<error description>). (17008) |
Contact Customer Support. |
|
17011 |
Running discovery on the same pool in parallel is not allowed. |
Pool Jpool appears to have another discovery running. Skipping. (17011). |
Make sure that two jobs are not running at the same time that discovers the same pool. |
|
17502 |
Generic retention discovery is already running for this volume. |
Volume <server>:<share> appears to have another discovery running. Skipping. |
No user intervention is required as the next step, if any, within the job is run. |
|
17504 |
Sent when a retention discovery is run on any volume other than a Windows Share retention volume. |
Volume <server>:<share> is not supported for discovery. Skipping. |
Contact Customer Support. |
|
18007 |
Directory listing or processing of data object failed in Grazer. |
Walker._walktree: OSError - <path><rea-son> (18007) |
Make sure that the appliance still has appropriate permissions to a volume. Verify that there is network connectivity between the appliance and your volume. Contact Customer Support. |
|
18008 |
Unknown error occurred while processing data object or listing directory. |
Walker._walktree: Unknown exception - <path>. (18008) |
Contact Customer Support. |
|
18009 |
Grazer timed out processing an object. |
Walker._process File: Grazer Timed Out. (18009) |
Contact Customer Support. |
|
18010 |
The skipdirs file is either not present or not readable by root. |
Unable to open skipdirs file: <filename>. Cannot skip directories as configured. (18010) |
Contact Customer Support. |
|
18011 |
An error occurred reading the known extensions list from the database. |
Grazer._run: couldn't read extensions - <reason>. (18011) |
Contact Customer Support. |
|
18012 |
An unknown error occurred reading the known extensions list from the database. |
Grazer._run: couldn't read extensions. (18012) |
Contact Customer Support. |
|
18015 |
NFS initialization warning that NIS is not available. |
NIS Mapping not available. (18015) |
User name and group names might be inaccurate. Check that your NIS server is available and properly configured in the data server. |
|
18019 |
The checkpoint that is saved from the last harvest of the NewsGator data source failed to load. Instead of conducting an incremental harvest, a full harvest is run. |
Unable to load checkpoint for NewsGator volume. A full harvest will be performed instead. (18019) |
If the message repeats in subsequent harvests, contact Customer Support. |
|
18020 |
The checkpoint noted for the current harvest of the NewsGator data source might not be saved. The next incremental harvest of the data source is not able to pick up from this checkpoint. |
Unable to save checkpoint for NewsGator harvest of volume. (18020) |
If the message repeats in subsequent harvests, contact Customer Support. |
|
33016 |
System might not unmount this volume. |
Windows Share Protocol Session teardown failed. (33016) |
Server administrators can see that connections are left hanging for a predefined time. These connections will drop off after they time out. No user intervention required. |
|
33017 |
System encountered an error while it tries to figure out what query uses this volume. |
An error occurred while retrieving the query instances pointing to a volume. (33017) |
Contact Customer Support. |
|
33028 |
The tear-down operation of the connection to a FileNet volume failed. Some connections can be left open on the FileNet server until they time out. |
IBM FileNet tear-down operation failed. (33028) |
None |
|
34003 |
Skipped a copy data object because disk full error. |
Copy action error :- Target disk full, skipping copy : <source volume> to <target volume>. (34003) |
Verify that there is space available on your policy destination and try again. |
|
34010 |
Skipped a move data object because disk full error. |
Move action error :- Target disk full, skipping copy : <source volume> to <target volume>. (34010) |
Verify that there is space available on your policy destination. After verifying that space is available, run another harvest before you run your policy. Upon harvest completion, try running the policy again. |
|
34029 |
Discovery export policy detects the target disk is full and skips production of an object. |
Discovery export Run action error: Target disk full, skipping discovery export:
|
Create sufficient space on target disk and run discovery export policy again. |
|
34032 |
The policy that was run has no volumes in scope that is based on the configured query and scoping. The policy cannot be run. |
No volumes in scope for policy. Skipping policy execution. (34032) |
Check policy query and scoping configuration, and re-execute policy. |
|
34035 |
If the global hash setting for the system is set to not compute data object hash, no hash can be computed for the target objects during a policy action. |
Copy objects : Target hash will not be computed because Hashing is disabled for system. (34035) |
If target hashes need to be computed for the policy audit trail, turn on the global hash setting before you run the policy. |
|
34036 |
The policy has no source volumes in scope, which means that the policy cannot be run. |
The policy has no source volume(s) in scope. Wait for the query to update before executing the policy. (34036) |
Confirm that the query used by the policy has one or more volumes in scope. |
|
42003 |
The job in this action is stopped by the user. |
Copy data objects stopped at user request. (42003) |
No user intervention is required. |
|
42008 |
The job in this action is stopped by the user. |
Move data objects stopped at user request. (42008) |
No user intervention is required. |
|
42016 |
The job in this action is stopped by the user. |
Delete data objects stopped at user request. (42016) |
No user intervention is required. |
|
42026 |
The job in this action is stopped by the user. |
Policy stopped at user request. (42026) |
No user intervention is required. |
|
42035 |
When the job in this action is stopped by the user. |
Set security for data objects stopped at user request. (42035) |
No user intervention is required. |
|
42051 |
Two instances of the same policy cannot run at the same time. |
Policy <policy-name> is already running. Skipping. (42051) |
No user intervention is required. |
|
42052 |
Policies cannot be run until after volumes are loaded, if those volumes are participants to the policy by virtue of being in the query. |
One or more volume(s) needed by policy <policy-name> are being loaded. Waiting for the bulk load(s) to finish. (42052) |
No user intervention is required. |
|
42061 |
Discovery export policy was stopped by user. |
Discovery export run on objects (Copying native objects) stopped at user request. (42061) |
No user intervention is required. |
|
42064 |
Discovery export policy execution is delayed because a conflicting discovery export run is in progress. |
A Discovery export run related to policy 'Discovery export case One' is in progress. Waiting for it to finish. (42064) |
The discovery export policy execution is held up for required resources. Execution must begin as soon as resource becomes available. |
|
42068 |
Policy failed to set appropriate permissions on the target directory. Objects that are created from the policy might not have appropriate permissions set. |
Copy objects warning, unable to set permissions on target directory: share-1/saved. (42068) |
Policy might not be able to set appropriate permissions on the objects it creates. If it is not acceptable, verify that target volume has appropriate write permissions and re-execute. |
|
42069 |
If the “Copy data objects modified since last harvest” option is selected for a discovery export policy, it is valid only if the discovery export itself is defined to act on the original file/email archive, as opposed to their members. If it is not true, the warning tells the user that modified objects are skipped. |
Discovery export DAT_Export is configured to act on members of containers, and cannot act on objects modified after the last harvest. Discovery export run X will skip modified objects. (42069) |
If the modified objects need to be acted upon, either use a discovery export action only on the original file/email archive, or conduct an incremental harvest on the source volumes. |
|
46026 |
Volume is being harvested or policies are running against it. If there are other full-text indexes to be backed up, the system works on those actions. Try this volume again. |
Volume volume:share is in use. Unable to back up full-text index. Will retry later. (46026) |
Rerun backup when volume is not in use. |
|
47201 |
Database connections are down to a normal level. |
Database connections at normal level again (512/100) (47201) |
No user intervention is required. |
|
47202 |
The system is starting to run low on database connections. This situation is abnormal. An indication of process restarts and connections are not being cleared. |
Database connections usage seems excessive (512/415) (47202) |
Contact Customer Support. |
|
47215 |
Someone internally or externally is trying (and failing) to SSH into the data server. |
SSHD: Failed password for root from 172.17.18.185 port 57982. (47125) |
Contact your local IT manager. It might be either a mistyped password by a legitimate user or in the worst case scenario, a genuine break-in attempt. |
|
61003 |
One of the load files cannot be uploaded because the compute node might not be accessed to obtain. |
Failed to mount transaction cache dump '/deepfs/postgres/pro-duction_cache'. (61003) |
Some of the load files will be missing after the discovery export completes. These load files are reproduced on a new run. If problem persists across runs, Contact Customer Support. |
|
61004 |
Warns the user that one of the transaction cache memory dump processes encountered an error. If a discovery export runs, it means that the discovery export fails to produce one of the load files. Note: If multiple memory dumps fail, there is one warning per failed memory dump. |
Transaction Cache Dump failed with error - Validation failed during creation of load file. (61004) |
Run the discovery export policy that saw the error again. If the error persists, and you cannot find any cluster/data server configuration issues, contact Customer Support. |