LAW 6.9.112 - September 30, 2015

Enhancements

Deduplication

Hash values can be generated for non-email items in Outlook PST files via ED Loader.

ED Loader

The current case name is now displayed in ED Loader.

Endorsing

Word wrap can be configured on endorsements via the Header/Footer dialog box.

Export

The Text Encoding list has been added to the Text Options dialog to provide additional encoding options, including addition of a byte order mark.

Import

A _GUID field is added to LAW PreDiscovery and a Global Unique ID is assigned to new records.  _GUID records on existing LAW PreDiscovery cases can be populated using the "Generate document GUIDs" option on the Tools menu.

Licensing

Software product keys can now be refreshed or deactivated from the License Manager application.

OCR

LAW PreDiscovery cases created in version 6.9.x and later will store OCR text files in a consolidated folder to avoid issues with long path names.

Known Issues

ED Loader

•The “Wrong OS or OS version for application” automation error occurs when attempting to import documents using ED Loader if a 64-bit version of Microsoft Office is installed on the same machine.  LAW PreDiscovery does not currently support 64-bit versions of Microsoft Office. Installing a 32-bit version of Microsoft Office on the machine resolves the issue.

•When adding a duplicate custodian using different letter cases in the name (uppercase/lowercase letters), the system displays an error message.

•Password encrypted archives are not being extracted when using the password file.

•7zip processing is much slower than the current archive processing due to limitations of the toolkit used for extraction.

•Decompression of JPEG images in ZIPX archives is not supported. Decompression of JPEG images in ZIPX archives is not supported.  Warnings are logged for the affected files during the import process. Users can then perform the extraction manually (or with another tool) outside of LAW PreDiscovery.

•The issue of MIME headers (e.g. “Date: Wed, 06 Aug 2014 08:47:49 -0700”) being visible (in certain viewers) when saving emails to MHTML during ED Loader imports was resolved in LAW PreDiscovery version 6.7; however, this issue still occurs with “Note” Microsoft Outlook items.  This issue is caused by a third-party component used by LAW PreDiscovery.

•"Object variable width block not set" error occurs when attempting to load OST files created with Microsoft Outlook 2013.  Due to the lack of a specification, the 3rd party component used to process OST does not support OST files created with Microsoft Outlook 2013.  As a workaround, convert the OST file to PST using third-party component and then process as PST.

Endorsing

When endorsing PDF files with comments, the comments may be lost.

Export

When exporting a load file with the “Export as single page text" option selected in the Text Options dialog box, text files are not exported properly.

Import

•Images over 2GB in size may fail to import.  This issue is due to a limitation of a 3rd party component. To correct the issue, reduce the file size utilizing a 3rd party application that supports images over 2GB prior to importing.

•Unable to import OST files created with Microsoft Outlook 2013. Due to the lack of a specification, the 3rd party component used to process OST does not support OST files created with Microsoft Outlook 2013. As a workaround, convert the OST file to PST using third-party component and then process as PST.

Installation

ABBYY is not available in LAW PreDiscovery after installing ABBYY FineReader 11 on a clean workstation.  Once the customer creates a Law50.ini file and moves the data in that file to C:\ProgramData\LexisNexis\LAW PreDiscovery, ABBYY is available in LAW PreDiscovery.

Licensing

•When more than one product key is activated and the product keys contain licenses for the same features, some licenses may be missing after activation.  

•When more than one product key is activated and the product keys contain licenses for the same features, some licenses may be missing after deactivation.  

PDF Support

•The PDF conversion process may fail on certain Microsoft Office documents on supported 64-bit operating systems (Windows 7 and Windows Server 2008 R2) with 32-bit Office 2010.  Currently, the workaround is to run the conversion using an alternate system configuration (32- or 64-bit operating system with Office 2007 or 32-bit operating system with Office 2010).

•Markup (e.g., comments, arrows, lines) existing in (raw image) imported PDFs will not be viewable in the LAW PreDiscovery image viewer and will not appear in the output when printed.  As an alternative, the PDFs can be imported using ED Loader and, if needed, converted to TIFF or PDF.

Scanning

•The File Type scanner output value may become “stuck” (cannot be changed from drop-down list) in certain scenarios when using the scan toolbar.  As a workaround, close and re-open the scan toolbar to resolve the issue.

•LAW will close unexpectedly when the Edit > Insert > Scanned Document function is selected if a scanner is not configured in LAW PreDiscovery.  As a workaround, ensure a scanner is properly configured in LAW prior to accessing this scan function.

Software Licensing

The LAW Management Console (LMC) may improperly report negative license counts when the license server is set to localhost.  As a workaround, install product keys on one single server and point all machines to that server.

TIFF/PDF Conversion and E-printing

The LAW PreDiscovery Image Drivers are renamed when upgrading to version 6.7 to resolve an issue with a “This printer is currently set to black and white mode” pop-up error message that halted the conversion process. If the drivers are not renamed during the upgrade (e.g. permissions issue arises), please use the workaround if this error was a problem for you in previous versions or to avoid the issue should it arise in the future.

The two image drivers can be renamed manually, provided the user permissions are sufficient. The new names are “LexisNexis Image Driver” (no quotes – formerly “LexisNexis Image Driver 5.0) and “LexisNexis Image Driver 300 DPI” (no quotes – formerly “LexisNexis Image Driver 5.0 (300 DPI)”). If a second set of image drivers are added during the upgrade, simply remove the original set which include the “5.0” in the driver names.