Current Version | Enhancements | Known Issues | Resolved Issues | History

Analysis

•Fixed an issue causing a SQL timeout during email threading with cases having more than 1 million documents.

7.8.169

•Estimated Time Remaining in the Global Dashboard for Analysis now displays the correct estimated time.

7.7.102

•Digitally signed emails can now be opened and read by Explore.  *Note:  Encrypted emails are still not able to be read because they require a certificate to decrypt the message.

•Reprocessing documents with custom properties causes a duplicate key Critical Analysis Failure.

•Addressed SQL issues that can occur when importing an extremely large number of files.  These issues caused inventory errors.

•Added retry logic to address a SQL deadlock exception that can occur when importing more than 1 million documents.  

•Updated error handling to properly log deduplication process errors and indexing process errors.

•Corrected an issue causing a DuplicateKeyException to occur when multiple indexing jobs are queued by Analysis agents.  This exception also caused the indexing to re-try continually.  

•Fixed an issue causing NIST to timeout during bulk exclude operations.  

•Fixed issue where compound documents were identified as duplicate when a child document was duplicate.  

7.6.268

•Resolved a timeout issue that occurred when PST analysis failed and was rolled back.

•Fixed an issue that resulted in an incorrect resume offset when retrying containers processed by multiple agents.

7.4.58

•Fixed an issue where a failed Analysis attempt could cause an infinite loop.

•Fixed an issue that was causing MPP filetype processing to fail, resulting in no content being extracted.

•When inventorying many sources simultaneously, the agent that counts the source items/sizes may cause a SQL timeout.

•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.

7.3.229

•Embedded compound document files residing inside E01 and L01 forensic images are not exported.

•Explore incorrectly identifies embedded Visio diagrams as Excel files.

•Added support for the RAR5+ file type for file extraction.

•In specific scenarios, Excel worksheets embedded in PowerPoint files are not extracted.

7.2.148

•Author field is not being populated for RTF documents.

•Outlook 2013 OST mailstores embedded inside office files are not extracted.

•Embedded Visio diagrams in message file are incorrectly recognized and processed as Excel documents.

•Embedded worksheets in PowerPoint files are not being detected.

•Certain Unicode characters are displayed as ?? in extracted text.

•Resolved scenarios where forensic image (E01) formats fail to process due to Out of Memory causes.

7.1.48

•The MeetingStatus field values are cutoff when they are longer than 15 characters in length. ***Note - The default hashing algorithm that CloudNine™ Explore uses includes the MeetingStatus field. Users that have hashing algorithms that include the MeetingStatus field may experience hash changes for Lotus Notes emails.***

2.6.0.96

•EnCase image segments smaller than 25MB caused CloudNine™ Explore to load the entire image twice

2.5.0.72

•Improved handling on attachment names for multi-part mixed EML files to match standard Outlook behavior - as a result, customers should expect that hash values may change for these specific email types. Other filetypes will not be affected by this specific change.

•CloudNine™ Explore fails to extract body content for emails containing an incorrectly split two-line Subject value - this situation only occurred if the subject like was split incorrectly, e.g. the 2nd line did not begin with white space. CloudNine™ Explore will now extract the entire email and contents/attachments, but it will only extract the first line of the Subject if it is incorrectly split into 2 lines.

•Embedded nsf documents being logged as critical exceptions, despite Lotus Notes being installed on processing machine.

•CloudNine™ Explore fails to import MS Word documents containing embedded objects (created by inserting a new object package).

2.5.0.64

•Modified document import to always respect the case setting for the text size threshold in determining whether to save the text to the Case Database or to disk

•Fixed an issue where appointment start and end times were not always captured during document import.

2.4.0.22

•Added support for importing\exporting .ics files as calendar items

•Improved PPTX analysis performance.

•Improved analysis performance on sMIME file types.

2.3.0.69

Case Management

•The ShowLawPrediscoveryExport case property setting is not working properly from the Manage Exports link.

7.6.268

•Improved case database migrations to prevent scenarios where existing GUIDs could be out of sync with newly-assigned GUID values.

7.3.237

•Fixed an issue that was causing large cases to fail required post-update schema migration.  This caused certain cases to not open correctly.

•Case database schema migrations missing when opening old cases.

•Case schema migrations could silently fail in the background, causing the application to stay on "Case Migration In Progress" resulting in migration not completing.

7.3.229

•CloudNine™ Explore does not wait for Lotus Notes to complete its initialization before attempting to open a document which results in various errors.

•Confirmation dialog reveals password data when configuring LAW case list database for SQL

2.5.0.72

•Modified the "Map Sources" function to convert all paths to UNC values

2.4.0.22

Case Migration

•Issue addressed that caused a Hierarchy ID database migration failure.

•Resolved a case migration issue resulting from unexpected Hierarchy Id values.

7.4.58

Compound documents

•Microsoft Equations documents are not extracted when extracting compound documents.

2.2.2.34

Content Viewer

•Certain unicode characters are displayed as ?? in extracted text.

7.2.148

Delete

•Deleting sources/custodians does not delete their embedded container files. 

7.6.268

•Attempting to delete a source containing a MBX or DBX whose emails have been previously exported to LAW results in an exception being thrown which cancels the delete. 

7.1.48

Encryption

•Encrypted archives that failed to export from CloudNine™ Explore were receiving a null reference exception, rather than a file encryption exception.

2.5.0.64

Error

•Updated log folder and default log levels to return Fatal Errors, Errors, Warnings, and Informational notifications.

7.0.206

Exceptions

•Removed "Decrypted Files" exception category since it was misleading.  It referenced files CloudNine™ Explore detected were encrypted, but were still able to be processed.

2.6.0.96

Explore Web

•Fixed an issue preventing users from being added or removed from Explore Web Review Sets.

7.7.102

Export

•Corrected some unexpected errors in LAW Direct Export to make the process more robust.

7.8.169

•Trailing space in PST folder name causes an error during Export.  

•Running LAW Direct Export on cases containing documents/emails with large families causes an exception.  

7.6.268

•Addressed an issue causing the DupCustPaths field to contain the path of the current file instead of the dupe.

7.5.89, 7.6.279

•Resolved an issue where the export numbers created for the first generated Export were used for subsequent Exports.  

7.5.67

•Fixed an issue with exporting attachments from S/MIME encrypted messages that had been successfully imported.  

•Fixed an issue resulting in "Index out of range" errors when exporting.  This was due to a difference in processing between import and export of Mime email attachments specifically.

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.

•Resolved an issue that prevented Explore's LAW Direct Export function from exporting to any LAW case with a different name.

7.3.237

•In certain scenarios, the Export process may stall on "Populate LAW Case" status, causing Export not to complete.

7.2.148

•An exception occurs when exporting embedded compound documents residing inside E01 and L01 forensic images.

7.1.48

•"Newline" values in metadata are causing record entries in the DAT to spread across multiple lines.

2.6.0.98

•Embedded images are copied to wrong location while performing a law direct export in HTML format, preventing embedded images from showing correctly in HTML files in LAW.

•Fixed an issue where .msg files embedded in Mime emails would sometimes cause exceptions during export processing.

2.6.0.96

•CloudNine™ Explore incorrectly populates LAW's RecordType field on export.

2.5.0.72

•In rare scenarios, exporting Office XML files with hidden sheets would cause the CloudNine™ Explore-exported spreadsheet to be corrupted.

•LAW Direct Export fails when the process encounters invalid characters in folder paths.

2.5.0.64

•Previously in LAW Direct exports, CloudNine™ Explore exported all tags listed in Case Settings under Tags instead of the tags only pertaining to documents being exported.  Now, LAW Direct exports will only export tags pertaining to the records being exported.

•"Load" settings link is disabled while export is in progress to prevent corruption of data.

•Improved accuracy of fields exported to match LAW in a LAW Direct export.

•"Pending" and "Exported" counts now exclude documents that error from totals.

•Added new functionality that allows user to control the creation of .ERR placeholder files on Direct Export.

•LAW Direct Export would leave "EDFolder" value blank for email attachments.  

•LAW Direct Export was marking OCR text as Extracted Text when exported to LAW.

2.3.0.69

•In a LAW Direct export, the TextXStatus field is no longer incorrectly set to C for documents without extracted text. In CloudNine™ LAW, the TextXStatus field value should be set to N for documents without extracted text.

2.2.2.22

•MBOX content no longer triggers the "Extraction failed Reason: value was either too large or too small for an int32" error message.

•LAW Direct export now completes even if the near native viewer has not been enabled.

•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.

2.1.0.105

•Documents annotated and/or redacted in CloudNine™ Explore Web are automatically converted to TIFF images upon export to CloudNine™ Explore. When these TIFF files are exported to LAW using the direct export process, the color properties are defaulting to High color and LZW compression.

2.0.1.94

Filters

•When user enables "custodian duplicate prioritization", the corresponding "EDIT" link is not appearing next to the Duplicates filter on the Filters tab.

2.6.0.98

Full Text Searching

•Improved Stemming accuracy when searching in CloudNine™ Explore.

2.3.0.69

Global Dashboard

•Dashboard Document Timeline "Items Without Dates" was not matching the Report Document Timeline "items without dates".

2.3.0.69

Hashing

•Explore normalizes whitespace in content when generating hashes. This change may result in email hashes in cases created with Explore 7.1 to be different than prior versions.  Note: Hashing will only change for new Explore cases.

7.1.48

•Bug fixes and enhancements to email processing in both CloudNine™ Explore 1.9 and 2.0 may result in changes in email hashing behavior. After upgrading, emails processing in a previous version may not always deduplicate in the same manner

2.0.1.94

Import

•CloudNine™ Explore is now capable of handling MBOX files that include Unicode characters.  

2.1.0.105

Indexing

•Re-indexing a large case skips some indexes.

7.6.268

•Fixed an issue where, in rare scenarios, the indexing job could get queued to an infinite loop.

7.3.237

Installation

•Fixed an installation issue that resulted in Explore not processing pending work after upgrading.

7.5.56

•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:

▪Microsoft Visual C++ 2008 SP1 (x86)

▪Microsoft Visual C++ 2010 SP1 (x86)

▪Microsoft Visual C++ 2010 SP1 (x64) - on 64-bit machines only

▪Microsoft Visual C++ 2012 Update 4 (x86)

▪Microsoft Visual C++ 2012 Update 4 (x64) - on 64-bit machines only

▪Microsoft Visual C++ 2015 Update 2 (x86)

▪Microsoft 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" site, and rerun the CloudNine™ LAW installer.

6.10.201

Lotus Notes

•If you try to use CloudNine™ Explore to open an email message from a Notes Storage Facility (NSF) file when Lotus Notes is not open and running, a different email opens in Lotus Notes than the one you selected. However, after this occurs, if you try to open the email again from CloudNine™ Explore, once Lotus Notes is running, the correct email opens.

2.5.0.72

Metadata

•Unicode characters are captured correctly in the Subject field.

•Specific to Powerpoints created in Microsoft Office versions 1997-2003, when a user creates a blank Powerpoint from the desktop and does not open the Powerpoint file, Windows assigns the default value of DastLastModified to April, 7th 2003 20:47:14. Previously Explore was capturing the DateLastModified of April, 7th 2003 20:47:14 as a valid date.

•Now Explore is correctly capturing the DateLastModified of April, 7th 2003 20:47:14 as a NULL value.

7.0.206

NIST

•Changes to the NIST database settings in Explore were not being saved and retained.

7.3.229

•Custom SQL accounts cannot read the NIST database if it differs from the EDA Management database connection string.

7.2.148

•We have addressed an intermittent issue that was causing an inability to configure the NIST database so that the NIST Items Count and Family Count were correctly displayed on the Filters tab.

2.1.0.105

OCR

•If you run out of disk space during OCR, the case will throw an error and blacklist the case.

7.8.169

•OCR fails when there is a large number of containers.

•OCR fails when Explore is installed alone without LAW.  

7.6.268

•Fixed an issue resulting in an incorrect warning that ABBYY Engine is not installed.

7.5.51

•OCR processing has been modified so that "Documents to OCR" no longer included filtered documents.

7.2.148

•OCR tab will now refresh as new data is added.

2.3.0.69

•Running OCR on an NSF from multiple computers triggers OCR error: "Failed to extract embedded item for input to OCR engine".

2.2.0.20

Performance

•Several updates were made to reduce the amount of data that is read during CloudNine™ Explore startup, which results in large cases opening faster.

2.6.0.96

Processing

•Fixed an issue where suspending embedded containers for multi-agent processing would create duplicate records.  

7.7.108

•Corrected an issue where some container files were displaying the wrong document location.

•Explore now extracts 0-byte empty files from OLM files.

7.7.102

•Launching source documents for emails and attachments in NSF files caused the case to be blacklisted.

7.6.268

•Fixed an issue where some PDF files were not being decrypted even when the correct password was provided.

7.6.279

•Fixed an issue resulting in duplicate DocId values when errors occur during population.

•Fixed an issue when adding a single source file results in incorrect DupCustPath and DupParentPath values.

7.5.89, 7.6.279

•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.  

7.5.67

•Fixed an issue processing very large PST files with more than 500,000 items in the same folder.

7.5.51

PST

•Some PST files larger than 20 GB may not process as expected in CloudNine™ Explore versions 2.0.1.97 or earlier. If this happens, please contact CloudNine support.

2.1.0.105

Reporting

•The Exception Report no longer displays the following error message before generating the report:

•The exception report template needs to be modified to support the modified ExceptionType enumeration. Some exception types may not be visible in the summary section.
Error: Field 'lblDescC3R21' not found.

2.2.2.22

Search

•Include organizer/required/optional contents to the To/From/Cc fields for data added for indexing to allow the data to be searchable similar to LAW.

7.4.58

•Fixed an issue with Explore Search hit highlighting that caused incorrect words to be highlighted as hits.

7.3.229

Tagging

•Eliminated a rare scenario where creating tags in case A actually created the tags in case B instead

2.4.0.22

User Interface

•When deleting documents/sources from CloudNine™ Explore, the Dashboard data is not updated to reflect the new information, even if users switch to another tab and back again.

•When switching to a new case in the CloudNine™ Explore application, if the active tab is Exceptions then the data on that tab is not refreshed.

2.6.0.96