Known problems in IBM eDiscovery Manager Version 2.2 Fix Pack 3

News


Abstract

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

Content

1. Testing the connection to a directory server before creating a search template fails

If you try to test the connection to a directory server (by using the Test Connection button on the LDAP Configuration pane of the Administration page) before you create a search template, the following error is written to the IBM WebSphere Application Server log file:

com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet action in application EDMClient. Exception created : javax.servlet.ServletException: java.lang.NullPointerException
    at org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
    at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
.
.

Caused by: java.lang.NullPointerException
    at com.ibm.icm.chl.console.config.actions.TestLdapCfgAction.execute(TestLdapCfgAction.java:140)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
.
.

Workaround: Create and save a search template before testing the connection to a directory server.

2. Searches on values that include an @ sign can return 0 results

In environments that use IBM Legacy Content Search Engine and that have object stores with English locales, entering search terms that include an @ sign can return 0 (zero) results. For example, searching the Sender field with a value of employee@example.com can return 0 search results.

Update: This problem is fixed in IBM Content Collector Version 2.1.1 Fix Pack 4 and IBM Content Collector Version 2.2 Fix Pack 2. After upgrading to one of these releases, follow the instructions in the "Verity style sets" section of the readme to change the style set for the object store.

3. Scheduled searches that are manually restarted are synched to the restart date

After manually restarting a scheduled search, subsequent searches run on a schedule that is relative to the restart date instead of the original start date. If you see this problem, contact IBM Support for assistance.

4. Exporting Lotus Notes email that contains rich text content to PDF does not always work

In a small number of cases, when Lotus Notes email that contains rich text content is exported, it is not properly converted to Portable Document Format (PDF).

This is a problem in software that is supplied by a third party. IBM reported the problem to the responsible vendor and is waiting for a fix.

5. Some Microsoft Word 2002 documents cannot be exported to PDF

Microsoft Word 2002 files that contain macros might fail to export to PDF. When this happens, you can see errors like the following one in the Task Error Details window:


    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.

This is a problem in software that is supplied by a third party. IBM reported the problem to the responsible vendor and is waiting for a fix.

6. Some Microsoft PowerPoint 2002 documents cannot be exported to HTML or PDF

Microsoft PowerPoint 2002 documents might fail to export to HTML and PDF. When this happens, you can see errors like the following ones in the Task Error Details window:

    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.
    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: file is corrupt.

This is a problem in software that is supplied by a third party. IBM reported the problem to the responsible vendor and is waiting for a fix.

**************************************

Several problems that were discovered in earlier releases of eDiscovery Manager continue to exist in eDiscovery Manager Version 2.2 Fix Pack 3. For more information, see the following technotes:


Change history

History Date Change
Released December 2011

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

eDiscovery Manager

Software version:

2.2.0.3

Operating system(s):

AIX, Windows 2003 server, Windows 2008 server

Reference #:

1571294

Modified date:

2011-12-12

Translate my page

Machine Translation

Content navigation