IBM Support

Known problems in IBM eDiscovery Manager Version 2.2 Fix Pack 4



This technote contains brief descriptions of problems in IBM eDiscovery Manager Version 2.2 Fix Pack 4 that were discovered before the product shipped. Where applicable, workarounds are provided.


1. Any collection or search template that has an existing ID in the collection or template definition will, when imported, overwrite the existing definitions.
Before importing the collections or templates, follow these steps:

    a. Back up both the collections and the templates and make copies of both.
    b. View the ID value of the collection or template file being imported. Ensure that the ID is unique and not used in any collections or templates, unless you explicitly intend to replace the existing collection or template.
    c. Import the new collection or template file from the user interface.

2. The document count for the folder contents export task differs from the document count for the search results export task.

Important: This information is relevant only for sites that have FileNet P8 object classes that are hierarchical and only when exporting documents from child object classes and their parent object class.

The total and successful document counts for the following export tasks differ:
  • Exporting the contents of a folder that contains documents from both the parent object class and its subclasses (for example, a folder that contains both files (the parent object class) and SharePoint documents (the subclass))
  • Searching that same folder for all documents and then exporting the search results

For example, if a folder contains 80 files and 20 SharePoint documents, the Total count for the folder content export task is 100 and the Successful count is also 100. In contrast, the Total count for the search results export task is 120 and the Successful count is 100.

The discrepancy in the latter scenario is because eDiscovery Manager searches for and returns the SharePoint documents twice, first as files and then as SharePoint documents. Thus, the search result set count is 120 ((80 + 20) + 20). When the user exports the search results, eDiscovery Manager correctly processes all 120 documents in the result set and it exports only the 100 unique documents.

3 . When deleting multiple folders in parallel, tasks sometimes fail with a message stating "REPOSITORY_UNAVAILBLE". The exception in the log states "DB Lock request timeout exceeded".

Perform one of the following tasks:
  • Restart the failed folder deletion tasks until tasks have completed.
  • Work with the DBA to increase the database lock timeout.

4. The export fails and the count is wrong when searching from an advanced case.

When exporting results obtained by selecting the Case or Folders radio buttons and using the Select All option on the search results panel, the following count mismatch error may occur if there are duplicate items in folders returned from the search:

"PMDYRS5036E: The export completed, but the Total and Successful item counts do not match. This error can occur if the eDiscovery Manager server is stopped while an export task is running. Although the item counts are different, the export results might still be valid.
Verify whether the export produced the expected results. If you did not get the results that you expected, retry the export."

The export results total includes duplicates, whereas the number of successful documents does not include duplicates. For example, if you export 6 documents and all 6 have duplicate documents in other folders, then the Total count will be 12 and the Successful count will be 6. This behavior may be improved in a future release.

5. In scheduled searches, parent tasks do not correctly display failed sub-tasks.

In a scheduled search, after a sub-task has failed during the setup phase, the parent task is still shown as complete, and does not display a failed run (in the "Failed runs" statistics section) correctly.

6. Folder operations may not automatically resume after the repository connection recovers from previous problems.

Currently, the eDiscovery Manager folder operations may not automatically resume after the content repository connection is restored from previous problems (for example, if the Content Manager library server is down, the Content Manager resource manager is down, the FileNet P8 Content Engine is down, or the database is down).

7. A search done with a large number of terms fails on CM when the query string exceeds 4096 bytes in length. The Net Search Extender (NSE) query engine in CM has query length limit of 4096 bytes.

When a large number of search terms is given, eDM returns a generic error message:
The search could not be performed. This error can occur for several reasons including:
- One of the content servers was not available.
- The connection to a content server was dropped.

Workaround: Retry the search. If it is unsuccessful a second time, try logging out of eDiscovery Manager, then logging back in and retrying the search. Doing so re-establishes the content server connections.

The edmapp#.log file, stored in the logs subdirectory of the eDiscovery Manager installation directory, will contain a more detailed description of the problem, indicating that the query limit of 4096 bytes was reached:

    [2012-04-02 11:40:53.755] [4334 ] [SEVERE ] [41 ] [METHOD ] [] [getCursor ] The text Search query string may be longer than 4096 bytes. NSE function contains-text() only supports maximum 4096 bytes per query
    [2012-04-02 11:40:53.770] [4338 ] [SEVERE ] [41 ] [METHOD ] [] [hasNextResult ] QUERY_FETCH_RESULT_FAILED: Debug Message: State errcode 7015 Id 4 Event IDStr

8. Scheduled search creation failed with large query string if NotInCase=TRUE option specified on P8.

If you use FileNet P8 as your content repository and specify the NotInCase=TRUE option while creating scheduled searches with a large query string (for example, create scheduled searches with a large amount of query data, or create scheduled searches in a case with many folders), your scheduled search creation might fail, and you might encounter one or both of the following error conditions:
  • You receive a SQLCODE: -101, SQLSTATE: 54001 error. As a temporary workaround, you might increase the STMTHEAP of database.
  • You might receive a unrecoverable error if the number of your scheduled searches get too big.

9. File size limitations on exporting non-email documents to PDF or HTML.

Documents greater than 300 MB might not export successfully to PDF or HTML, depending on the content of the document. An error similar to the following might be returned (substitute PDF in place of HTML for PDF exports), even if the default timeout is set to unlimited.

    "DYRS5059E: Item item_identifierwas not exported because the content conversion process for this item took longer than expected."

Try giving the content conversion process more time to complete by increasing the timeout duration for exports to the HTML format. On the Export Formats pane of the Administration page, edit the Extract plug-in point for the HTML export format and increase the value of the Document.conversion.timeout.minutes plug-in parameter. The default is 3 minutes.

1 0. Pau sing queued export tasks fail with 'null' message if the eDiscovery Manager server is shutting down.

While the eDiscovery Manager server is shutting down, if you have multiple export tasks queued and you try to pause them, your export actions might fail with the following error message:
    "DYRS5056E: The export was unsuccessful for the following reason: null. For more information, search the eDiscovery Manager work manager log file for messages or a stack trace near the time that this error occurred. By default, log files are stored in the logs subdirectory of the eDiscovery Manager installation directory, and the default name of the work manager log file is edmworkmgr#.log."

11. Ex port restrictions for some items.

Due to problems in a third-party component of eDiscovery Manager, some items might not be exported to PDF, HTML, or both.

The items that are impacted by this problem include:

  • IBM Content Collector systems only. Some items of type Files - Content Collector or type Microsoft Exchange email (compound) - Content Collector

    These items cannot be exported to PDF or HTML format. If you attempt to export such items to PDF or HTML format, you might receive an error like this in the SystemOut.log file:
    10/4/10 23:28:09:266 PDT] 00000037               E convertFileToFormat Process convertFileToFormat terminated abnormally with exit code 6
    [10/4/10 23:28:09:282 PDT] 00000037               E convertFileToFormat Messages from C++: fileID:1101
    Converting to Image.
    Export process failed: access violation
    EXRunExport() failed: access violation (0x03C1)
  • Microsoft Word 2002 files that contain macros, Microsoft PowerPoint 2002 documents, and some TIF documents.

These items might fail to export to PDF or HTML. When this happens, you can see errors like the following one in the Task Error Details window:

(PDF error message)

    Error occurred in PDF Extract Plugin while converting the document (whose ID is { documentID }) to PDF format. The document conversion component returned this error: Process convertFileToFormat cannot convert file with OIT file id : n  : Export process failed: access violation.

(HTML error message)

    The export plug-in "HTML Extract Plugin" was unsuccessful in converting the item (whose ID is {documentID}) to HTML format. The document conversion component returned this error: Process convertFileToFormat cannot convert file with OIT file id : n  : Export process failed: file is corrupt.

Workaround: Export these items to a format other than PDF or HTML.

12. Delete Case task fails when the eDiscovery Manager server loses connectivity.

When trying to delete a case, if the eDiscovery Manager server loses connectivity to the Content Engine (P8), the delete case task may fail with the following error message:

    "DYRS3102E: The folder "Copy" could not be locked because it is currently being used by another user or process. Try your action again later."

Workaround: When the P8 server regains connectivity, delete the failed task. Log on to FEM, delete both the Case and Children folders from the FEM, then run P8 datamodel utility to clean up any remaining orphan eDiscovery Manager objects.

13. The P8 database loses connectivity while a task is in the setup state.

The task might continue to hang after the P8 database regains connectivity.

Workaround: Delete the hanging task, then resubmit a new task.

14. eDiscovery Manager loses connectivity to the P8 server while a task is in the setup state.

In some cases, the task could hang and the folder remain locked after the P8 server regains connectivity.

Workaround: Delete the hanging task, log on to the FEM and change EDMFolderState of the folder to 1, then resubmit the task.

15. Delete Folder task fails when the P8 server loses connectivity.

When restarting a failed delete folder task after the P8 server regains connectivity, an error may be generated stating:


Workaround: Contact IBM Support.

16. Viewing a document inside a folder in the Full Viewing mode shows a blank screen.

If you are using Internet Explorer and your eDiscovery Manager server is configured with large number of search templates, trying to view a document inside a folder in the Full Viewing mode (by double-clicking the document to open it in a new window) might display an empty window.

This is due to a limitation of Internet Explorer as suggested here:

17. Error received when using Preview or HTML Export on an IBM Connection forum document.

If an IBM Connection forum document contains an ampersand (&) in the content, you might recieve an SAXParseException error when trying to use Preview or HTML Export on it.

Document information

More support for: eDiscovery Manager

Software version:

Operating system(s): AIX, Windows

Software edition: All Editions

Reference #: 1592261

Modified date: 22 March 2013

Translate this page: