<< Click to Display Table of Contents >>
Category |
Issue |
Fixed In Version |
Administration |
•Fixed link to online LAW User Guide PDF. |
|
•"Check For Update" process fails after application of 10/15/2018 Software Licensing patch. |
||
•Changes to the default case template for field visibility are not being applied. |
||
API |
•Addressed an API issue for long custodian names in Turbo Import cases. |
|
Batch processing |
•We have corrected an issue related to splitting PDF files by bookmarks. CloudNine™ LAW was displaying TIFF files in the image extension column but not retaining the TIFF image. Image extensions are now cleared after splitting PDFs based on bookmarks and the TIFF images are retained. •ICS body content is now captured during the batch TIFF process. •CloudNine™ LAW no longer places "UNKNOWN" in the header during the batch TIFF process for MSG files. •The batch TIFF process can now produce TIFF images of VCF files that contain Chinese characters. |
|
Case Management |
•Fixed an issue where opening the case properties for an older case would auto migrate the case without prompting. •Addressed an issue where LAW did not properly indicate migration was needed for 6.18 or older cases. |
|
•Fixed an issue where deleting an ED Loader case from LAW did not remove it from EdaCaseListings. |
7.5.51 |
|
•Fixed issue where DateLastOpened was not properly updated when a previously opened case is detached. |
||
•Case schema migrations could silently fail in the background, causing the application to stick on "Case Migration In Progress." Migration never finishes. |
7.3.229 |
|
•When a project has been created in an earlier version of LAW, Users are unable to update the project after upgrading and migrating to a SQL caselist. •Case to Case Import does not carry over Natives or Extracted/Printed Text whenever a file has been brought in from an CloudNine™ Explore direct export, and Tiff/OCRed in LAW prior to case to case transfer |
||
Deletion |
•When emails were deleted from CloudNine™ LAW, the body of the email was not being removed. This issue has been corrected. |
|
Document Analysis |
•Document Analysis for pdfs is not detecting nor splitting on bookmarks. |
|
ED Loader |
•Corrected an issue where ED Loader used the wrong zip attachment filename in PST when the preceding item filename was too long to be extracted. •Updated 3rd party library to address a bug where certain email message bodies appeared empty during import. |
|
•Fixed an issue where ED Source was being prepended with "\\?\UNC" when adding sources via an Outlook folder. |
7.5.51 |
|
•Addressed a run time error that occurred when using the "Detect comments for MS Word/Excel/PowerPoint and PDF files" option selected and processing an MSG with ZIP attachment. |
||
•Session Size in ED Loader resets to 0 after performing a "Safe Cancel". •Added support for the RAR5+ file type for file extraction. |
||
•Importing loose EML with DOCX attachment corrupts attachment. •Due to an internal third party application, in limited situations MHT files are imported into CloudNine™ Explore as Excels. We worked with the vendor to resolve this. •The Passwords settings in ED Loader will generate an error message if entering case sensitive password variations for example: ABC123, abc123, Abc123. •During the File Type Management SQL migration process, the file engine is not being updated with newer file types, causing the sourceapp value not to be assigned correctly for some case records. |
||
•During the ingestion process, the source files are being incorrectly marked for cleanup; this is causing ED Loader to delete the source files during its cleanup process. •Some PDF portfolios are being incorrectly treated as standard PDFs, and are not extracting correctly. As a result, some PDF files would display 'For the best experience, open this PDF Portfolio in Acrobat X..’ in the image viewer after import through ED Loader. |
||
•ED Loader will generate an error if closed or canceled with no changes made. The error is "CloudNine™ LAW ED Loader has stopped working". Click Close Program to exit the error dialogue box. •Body text is not being extracted from EML files. •Attachments for failed HTML-converted MSG items are not being copied to $Repository, for reprocessing workflow. •Windows folder order is not being respected, causing LAW to not assign DocID consecutively (according to folder order). •Certain ICS files error when imported via ED Loader. |
||
•ED Loader fails to import MS Word documents containing embedded objects (created by inserting a new object package). •Embedded Images are not displaying correctly in natives/tiffs when MSGs are processed as HTML or MHTML. •Unicode characters within < > brackets are incorrectly extracted - LAW now utilizes unicode SMTP address if present. *NOTE - This may result in hash changes for emails with a unicode recipient list. •In certain scenarios, not all documents were being extracted from password-protected PST files. •Lines in extracted text could become incorrectly merged together when MSG file is imported as MSG •ED Loader errors when users attempt to process macro-enabled office files with extended metadata options enabled. •Organization field containing Unicode characters is corrupted on import. •Importing a NIST Excluded file as part of a family may cause attachpid for family records to be incorrect. •Mailstores contained within archive files are incorrectly processed as an edoc. |
6.17.096 |
|
•Improved ED Loader performance when scanning for mailstores in zip files •Added support to extract text from smart art shape in PowerPoint files. |
6.16.054 |
|
•Added functionality in ED Loader to sort OST items based on sent date •Author metadata was not being extracted from certain files •Title metadata containing Unicode characters was being incorrectly extracted •Author metadata containing Unicode characters was being incorrectly extracted •Improved ED Loader handling for zip file extraction - corrected an issue that misidentified specific zip file formats, which prevented successful extraction •OST mailstores could potentially be ingested as eDocs •Converting MSGs to MHT or RTF could result in a blank email body on the native copy •Improved PDF Portfolio processing to better handle newer PDF formats, and corrected an issue that was preventing PDF Portfolio extraction |
||
•Improved PDF Portfolio processing to better handle newer PDF structures, and corrected an issue that was preventing PDF Portfolio extraction |
6.14.67 |
|
•Certain emails were not extracting attachments properly |
||
•We have corrected an issue that was preventing ED Loader from properly processing EML files. |
||
Endorsement |
•Error thrown when endorsement is attempted on images with no specified DPI value. |
|
•Endorsements were being cut off after a hard return •LAW crashes when user attempts to paste unexpected characters into Header\Footer form fields |
||
E-Print |
•Fixed an issue where date/time was printed on PowerPoint files when "Do not print date/time stamps" was selected. |
7.5.51 |
Export |
•Issue fixed where re-exporting documents incremented the export numbering seed for each document. |
7.5.51 |
•Fixed an issue where LAW Direct Export (Explore) users were unable to modify assigned SourceApp values in LAW. This issue also caused SourceApp field values to show as blanks in the Grid View. |
||
•Color TIFF native files export as Black & White instead of Color. |
||
•Turbo export fails when certain conditions are added through query builder UI |
6.17.096 |
|
•Selecting 'Include Native for Tagged Documents Only" would result in text only being exported for documents in the export set that were tagged •Overflow error was displayed while performing a check on the certain values contained in the field. •Regenerate Load File process would not complete on large record sets •0 kb files were being excluded from export when "Include placeholder file when text is missing" is checked in the Export Utility's Text Options •Export process would incorrectly produce Unicode characters in XML load files |
||
•"Overflow error" caused while performing a check on the certain values contained in the field. •Corrected an issue where 0 kb files were being excluded from export when "Include placeholder file when text is missing" is checked in the Export Utility's Text Options •Selecting 'Include Native for Tagged Documents Only" would result in text only being exported for documents in the export set that were tagged |
6.14.67 |
|
•When exporting data from CloudNine™ LAW to a Summation DII, tokens are not exported to the DII load file. This issue only affects data obtained from an Early Data Analysis LAW Direct export. •When exporting a PDF with at least one attachment using the PDF Conversion and Combine Parents/Attachments options, the attachments are now correctly merged. •When the exported text exceeds the Concordance Desktop allowable limit of 12 MB for a field, the excess text will be entered into the next incremental field up to a maximum of six fields. For example, if the first text field is LAW_OCR_01, the first 12 MB of text goes into that field. The next 12 MB of text goes into LAW_OCR_02 and so forth until LAW_OCR_06. If there is still text to be stored, an error message is logged indicating that the text size exceeded maximum space available and data was truncated. •The @FULLTEXT DOC token is placed below the first line in Summation DII, which may cause issues upon import in Summation. •We have corrected an issue that occurred if one of the fields imported from CloudNine™ Explore via LAW Direct Export into CloudNine™ LAW included a null string terminator. Data in SQL Server fields is no longer truncated due to the way SQL Server handles null string terminators. •When exporting a PDF with at least one attachment using the PDF Conversion and Combine Parents/Attachments options, the attachments are now correctly merged. |
||
•We have addressed an issue that caused an error when exporting raw images with LZW compression. •Text encoding settings have been improved to prevent Unicode settings from corrupting files in CloudNine™ LAW. |
||
Extraction |
•Embedded/Inline images not extracted from NSF emails (saved as HTML). |
7.3.229 |
•ZIPX files currently do not extract properly. Contents are not extracted and there is no error message to indicate that the contents are missing. •By default, CloudNine™ LAW does not retain the PDF portfolio container. However, you can extract a PDF portfolio container file by going to the EDLoader.case.config.ini file and changing the OLE_IncludePDFPortfolioContainer property value to 1. Then run ED Loader with either the Enable compound document extraction on all supported file types or the Restrict compound document extraction to PDF portfolios option selected. •PowerPoint files created with older versions of PowerPoint for Mac and have Excel and/or PowerPoint for Mac files embedded in them now extract as expected. |
||
•Documents embedded in RTF files are now extracted upon ingestion. •We have corrected an issue that caused random text files to be generated in the $EDD folder. •If there are issues when extracting RAR files that have embedded ZIP files, an error message will be displayed. |
||
Fields/Metadata |
•_PS_EMBED field is not being correctly updated when embedded images in emails are detected. |
|
Grid View |
•Fixed an issue with Validate OCR Status available from the Tools menu. Documents with valid OCR files now properly show "C" for the OCR status after running this tool. |
|
Hashing |
•Turbo Import normalizes whitespace in the body of emails when generating hashes on new Turbo Import cases. This change may result in email hashes in cases created with LAW 7.1 to be different than prior versions. As a result, duplicates may not be identified when using the Inter-Case Deduplication Utility and deduplicating across cases that were created with different LAW versions. |
|
•Version 6.11.108 of CloudNine™ LAW included an update to dtSearch from 7.79 to 7.83. The update to dtSearch can cause hash values for a specific type of email ingested into older versions of CloudNine™ LAW (version 6.10 and earlier) to not match the hash values from CloudNine™ LAW 6.11 and higher. This issue occurs only for emails with no content in the body and only if the file is re-ingested into a case after upgrading from version 6.10 or earlier to 6.11 or higher. If you experience this issue, contact Support for a run command that identifies the affected files. |
||
•The contents of the Attach field have been corrected. It now points to the correct filename and path. This correction resolves an issue that was affecting the MD5 hash for NSF files with inline attachments. |
||
Import |
•Fixed an issue that resulted in missing extracted text when importing an EDRM 2.0 load file. |
|
•Fixed an issue that causes RAR5 archive files to fail in ED Loader imports. |
7.3.229 |
|
•When imported with the Identify Hidden Text functionality enabled, some edocs were incorrectly encoded to ANSI instead of UTF-8. This intermittent issue has been corrected. |
||
•We have corrected an issue that was preventing import when the regional locale was set to Japan. •Importing emails with HTML into CloudNine™ LAW no longer converts the email to a webpage. The native format of the email is now maintained. |
||
Ingestion |
•Decompression process fails when importing uncompressed image files into LAW. |
|
Installation |
•Resolved an installation issue resulting in the error "Your version of MSCOMCTL.OCX" may be outdated. This was due to a missing MSOLEDBSQL driver. •Added registration of LawPageXtractor.dll to address "Error occurred initializing the page count extraction server". •Fixed "another version of this product is already installed" error that can occur when installations have different versions of Visual C++ redistributable packages than the ones LAW installs. •Added registration of .dlls to address "Unknown error occurred while opening report" in ED Loader Summarize Queue. |
|
•Fixed an installation issue that resulted in the error "Unable to detect workstation configuration settings. Please run the LAW Configuration Utility" after upgrading and proper configuration. |
7.5.56 |
|
•Updated LAW to support fully disabling TLS 1.0 in Windows Registry. LAW now runs with only TLS 1.2 enabled. |
||
•Fixed an issue where after installation, local system would automatically reboot without prompting the user. •Fixed several 7.2 installer issues that prevented core DLL files from being properly installed and registered - these issues caused problems with endorsement and image manipulation. The installation process as a whole has been improved, with recovery processes to enhance the deployment process. |
7.3.229 |
|
•Installing LAW in a location other than the default system drive, resulted in an error during the LAW Configuration Utility being configured. |
||
•Corrected an issue where print drivers were not signed, causing install files to be detected as malware. |
||
•Upgraded InstallShield to 2015 and updated VC++ 2015 redistributable to latest version to ensure successful user installs. |
||
•Install the correct version of Microsoft Visual C++ before installing CloudNine™ LAW. See the Microsoft Knowledge Base article "Update for Universal C Runtime in Windows" for the download and instructions. Be aware that the CloudNine™ LAW installer attempts to install all Microsoft Visual C++ prerequisites, including: oMicrosoft Visual C++ 2008 SP1 (x86) oMicrosoft Visual C++ 2010 SP1 (x86) oMicrosoft Visual C++ 2010 SP1 (x64) - on 64-bit machines only oMicrosoft Visual C++ 2012 Update 4 (x86) oMicrosoft Visual C++ 2012 Update 4 (x64) - on 64-bit machines only oMicrosoft Visual C++ 2015 Update 2 (x86) oMicrosoft Visual C++ 2015 Update 2 (x64) - on 64-bit machines only The CloudNine™ LAW installer may hang when it attempts to install "Microsoft Visual C++ 2015 Update 2 Redistributable Package (x86)" or Microsoft Visual C++ 2015 Update 2 Redistributable Package (x64)" even if you have installed it prior to the CloudNine™ LAW installation. If this occurs, abort the installation, reinstall the update from the Microsoft Knowledge Base article "Update for Universal C Runtime in Windows", and rerun the CloudNine™ LAW installer. |
||
•The MSXML.DLL has been removed from the installer and Profile Manager. |
||
Inter-Case Deduplication |
•ICD processing could, with a specific workflow, cause duplicates to incorrectly receive a "parent" value |
|
LAW Case Import |
•OCR text for native records was not being migrated when running a case-to-case import |
6.14.67 |
LAW Configuration Utility |
•Addressed issue that can result in "No valid NIST files were found at the supplied location" error during NIST configuration. |
|
•Running the Configuration Utility on a machine that has incomplete and/or malformed FTM or Nist configuration properties causes an exception that forces the application to stop. •Fixed an issue that could cause File Type Manager configuration to fail during Configuration in Configuration Utility. |
7.3.229 |
|
•Custom SQL accounts cannot read the NIST database if it differs from the LAW5_Management connection string. |
||
•Database information entered in the Management DB tab is now persisted to the File Type Management tab for usability. •Updated several Configuration Utility text labels for clarity. •Revised the wording from “Local Service Account” to “Local System Account” in several areas of Configuration Utility to avoid confusion when configuring user accounts. |
||
LAW Management Console |
•LMC and the License Manager showing inconsistent license counts. |
|
•Batches created in the LMC remains in the database even after canceling and removing the job in the LMC. |
||
•The font selected for endorsments on the LAW Management Console host computer may revert to the default font on worker computers. |
6.14.49 |
|
LAW Service |
•When certain characters (% ^ & < >) are used in the password during the LAW Service configuration, the LAW Service is not installed. |
|
Licensing |
•Fixed "error occurred while updating key from file" when refreshing hardware key licenses from the internet in the LAW Profile Manager. |
|
•If maintenance on a perpetual software license is expired, users cannot open LAW. |
||
•We have corrected an issue that caused an error when you changed the license server in the LAW Profile Manager. •The option to refresh the license from the internet is no longer enabled under the server key menu when you are connecting through a software license. |
||
Near Dupe and Email Threading |
•Running a "purge" via Near Dupe\Email Threading on a case, where ND\ET has not been run, causes an unhandled exception. |
|
•ND\ET process would timeout, causing an "Execution Timeout Expired" error. Users can now extend ND\ET timeout values via the LAW50.ini file. Contact Support for more details. |
6.17.096 |
|
OCR |
•Fixed issue that resulted in an error when OCRing large files (greater than 200 pages). |
|
•When OCRing to create a Searchable PDF, using the Create PDF Thumbnail option causes OCR to timeout. Disabling the Create PDF Thumbnail resolves this. Abbyy doesn't have this issue. |
||
•Batch OCR with Expervision on encrypted images files without prior tiffing generated an error. |
||
•A new line and text are added in OCR output files while performing OCR with ABBY 11 engine for CSV files. |
6.17.096 |
|
Processing |
•Scenarios where multiple Agents attempt to process a single NSF file may cause an exception. To bypass this exception, users can temporarily restrict processing to one agent and reprocess the NSF source, and then remove the agent restriction for regular imports. This will be addressed in a future release. |
7.5.56 |
•Corrected an issue where where workstations would not properly join a batch TIFF/OCR job when errors occurred. •Addressed a SQL timeout exception during Explore or Turbo Import under heavy load in a single machine environment. |
7.5.51 |
|
•Fixed rare issue where email thread parent/child relationships were not properly identified when an email poster replies or forwards his/her own email and also changes the address list |
||
•When one of the services in a multi-client Explore export is stopped, the entire Explore would cancel. We've changed the approach to where Explore exports will now continue, and services/agents on other boxes/VMs will continue to work on the export uninterrupted. Similarly, when a case is suspended during export, the export itself will not be flagged as canceled. •In a specific scenario, an NSF with an invalid email item failed to process post-inventory. Improved ED Loader to log the file error and continue processing the NSF. |
7.3.229 |
|
Reports |
•The time on ED Loader Session Reports is displayed in UTC format. This release updates the time format to display in local time. |
|
Run Commands |
•Text Extractor and UpgradeOCRRepository run commands have been fixed. |
|
•TextPathExtractor has been removed from installed run commands. |
||
Scanning |
•Users unable to scan in color when Black Border, Noise and/or Hole Filters are enabled. |
6.17.096 |
•Improved "Detect Barcode" functionality - feature will now detect barcodes for any type of scan (b&w, gray or color ) |
||
TIFF/PDF Conversion |
•Fixed an issue where the user was unable to save an image after manual TIFF conversion from the "Image Acquired" dialog window. |
7.5.51 |
•Fixed an issue where default tiff settings were not being saved to the tiffopts.ini in the Law case folder, preventing them from saving for the next Tiff process. |
7.3.229 |
|
•The ability to save Default Tiff settings is disabled. •The LexisNexis image drivers were rebranded as LAW Image Driver and LAW Image Driver 300 DPI. |
||
•Highlighted text on MSG and HTML files does not show when imaged via IE. |
||
•In very rare circumstances, when a license reconnect happens during tiffing, LAW will send next document to print even before the previous document is processed completely. This fix addresses the error to ensure the impacted document is properly tiffed. |
||
•When converting a document with text hidden in color to TIFF format with Reveal hidden text and Normal mode enabled, the hidden text is not shown. |
||
Turbo Import |
•Corrected an issue for Turbo Import where data population was blocked from starting during file deletion. •Fixed a Turbo Import issue where suspending embedded containers for multi-agent processing would create duplicate records. |
|
•The Turbo Import page refresh rate was increased to prevent unresponsiveness when working with large data sets. •Fixed an issue where DupeStatus was not properly updated after deleting duplicate documents. |
||
•Fixed an issue where some PDF files were not being decrypted even when the correct password was provided. |
7.6.279 |
|
•Fixed an issue where Turbo Import would close if a second instance of LAW and Turbo Import were opened. •Corrected a SQL "Execution Timeout Expired" error that can happen when running multiple large import sets. •Updated Turbo Import to use the same ED Folder path structure used by ED Loader for email archive attachments. •Added retry logic to address a SQL deadlock exception that occurred when importing more than 1 million documents. •Updated error handling to properly log deduplication and indexing process errors. •Corrected an issue causing some cases to stall when encountering critical errors during native file extraction. •Fixed an issue where compound documents were identified as duplicate when a child document was duplicate. |
||
•Fixed an issue where multiple export items were assigned an identical Export Number. •Addressed an issue causing the DupCustPaths field to contain the path of the current file instead of the dupe. •Fixed an issue resulting in duplicate DocId values when errors occur during population. •Fixed an issue where the document delete process would run too many times when attempting to delete a large number of documents. •Fixed an issue when adding a single source file results in incorrect DupCustPath and DupParentPath values. |
7.5.89, 7.6.279 |
|
•Issue addressed that caused invalid parent IDs during case migration. •Issue addressed that caused some document numbering to be off due to archive files. •Addressed an issue where the Turbo Import Report was not updating after a delete. •Turbo Import custodian names are automatically updated to remove leading and trailing spaces to avoid export failures. •Issue fixed for LAW folders not being deleted after a Turbo Import delete. •Addressed an issue causing Turbo Import deletes to be slow. •Fixed an issue that preventing a user from queuing another source import while a delete is running. |
||
•Added support for the RAR5+ file type for file extraction. •Turbo Import processing fails when folder paths exceeded 255 characters. •If deduplication filter in Turbo Import was not enabled, imported files would not have a hash value populated to the MD5/SHA-1 fields in LAW. Turbo Import now populates the MD5/SHA-1 hash value to the LAW fields, irrespective of the deduplication filter state. •When reprocessing documents, in some cases the documents are imported into LAW in reverse order. |
||
User Interface |
•Corrected a few issues introduced with the 7.4+ UI Refresh work, including font display and scrollbar functionality on a few dialogs. |
|
Virus Detection |
•We have removed a signature in a file that was being flagged by McAfee Antivirus as a potential issue. The signature was verified as harmless and removed from the file to prevent further warnings from McAfee. |
Copyright © 2023 CloudNine™. All rights reserved.
CloudNine™ LAW | CloudNine™ Explore | CloudNine™ Explore Web | CloudNine™ Concordance® |