Jump to content

ifinch001

Members
  • Posts

    14
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

535 profile views

ifinch001's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. I have a client that wants me to stamp all documents with a long, 3-line stamp. When I attempt to apply the stamp during export, it extends off of the page and appears to ignore carriage returns from the 3 lines. I would assume this to be due to a margin limitation for stamps. At present, my only solution I have found is to export the tiff from Intella, then re-process the tiff in another tool to add the custom stamp. Is there any way that I can manually either increase the margin that the stamp can use or decrease the font/size of the stamp? Is there a configuration file for that?
  2. There are 2 machines that have the exact same setup and both exhibit the same behavior. Strangely enough, the second machine will export significantly more items (around 100k) before the destination disconnects. As for a stress test, I did go down this road and everything I throw at these SSDs turns up normal. Thanks, both of these are good ideas and I will try them out this week.
  3. In the event that someone has encountered this when transitioning from HDD drives to SSDs for Intella purposes. Last week, I switched out 2 HDDs for SSDs, making the current workstation setup 1x PCIe NVMe C:\, 2x Crucial SSDs for cases and exports, and 1x WD HDD for large, long-term storage. I am finding that when I index on or export to one of these new SSDs, the destination SSD disconnects (e.g. the SDD that contains the index or the SSD that is being exported to). This happens on multiple machines and multiple different Intella cases (using 2.4.2 and 2.5). Event logs show an event 129 in the System log "Reset to device, \Device\RaidPort0, was issued." At the end of the day, this is the result of the drive disconnecting while data is being written to it. All other drives remain connected to the workstation without issue. Index/export work as expected when using the NVMe or the HDD. Both SSDs (and even a separate machine with the exact same setup, so 4 total SSDs) are experiencing the same issue. I have run the gambit of troubleshooting for the last week from a general driver/firmware/software/SSD perspective and no improvement. The reason I am posting here is because this seems to happen exclusively when using Intella. As a test, I exported out a data set that causes the issue to the NVMe drive (which worked perfectly fine, but not a long-term solution), then copied the exported data to both SSDs and the disconnect did not occur. And after using the workstation for other purposes, Intella appears to be the only trigger. I should also note that some indexes work perfectly fine. It seems if indexes or exports are in the ballpark of 40K items, the disconnect occurs. So, I am inclined to believe that indexing or exporting from Intella is stressing the SSDs for some reason. Anyone else experience this issue? Or is there some setting I need to change or Intella version I should try?
  4. Recently, I have been having issues with export sets disappearing from Intella 2.4.2 without manually removing them. Is there a location in the case folder where the export sets are stored (similar to export templates) so they can potentially be manually recreated? Most recently, I exported data and generated a data set (approx. 300,000 files, if that matters), attempted to export additional data and generated a new export set but Intella crashed, then the first export set was no longer listed. The first export completed without an issue. Tried closing Intella and rebooting the workstation the index was open on to no success.
  5. I have been attempting to re-export a data set - around 250 documents - using the Load File format and into a single-page tif image output. The first export went as expected and the 250 items were assigned bates numbers, each page exported to a file, and then saved to an export set "Export Set A." When I adjust the tifs that were previously exported, mainly change what metadata is displayed in the exported tif of the item, and go to export them again, I run into my issue. When exporting out the single-page tifs using the Export Set A naming scheme in Advanced File Naming section, it appears as though the pages are exporting from Intella, but each page of a document is being assigned the same name and overwriting the previous page. For example, "DOC00001.doc" has 10 pages and was originally exported to 10 files, DOC00001.tif through DOC000010.tif, as expected. However, when I go to re-export using the created export set as the naming scheme, I end up with only 1 file, DOC00001.tif, but the tif is actually of the final page of the document. It looks like the first page was overwritten by the second, then the third, etc., because all 10 pages appear to be exported as "DOC00001.tif." I can provide more information if necessary. I have confirmed that I have the single page tif option selected (I used the same export template for both exports, so the exact same export settings were used). Any insight into how I can use an export set to re-export to single page tif would be much appreciated.
  6. Are there any plans to incorporate RSMF as an export format for Relativity load file exports? We have seen an increase in requests for this format.
  7. I had a question regarding embedded images on emails and if someone has a workaround, it would be appreciated. Test Environment: Intella 2.2.1 and a single email with 0 attachments, but multiple embedded images. Specifically, the embedded images are signature block pictures, a image that was copy-pasted to the email, and another of unknown origin. My goal is to be able to index that email and get a result saying that there is only a single item in the index. More specifically, I want to PREVENT Intella from peeling out the images found in an email unless they are explicitly attached to the message. If an image was a traditional attachment to the email, of course I would want that separated into its own item. Here are my tests. First, using default settings, the index resulted in 5 family items - not what I need. Second, unchecking the option in the "Add New Source" prompt under "Items" for "Index images embedded in emails and documents," the index resulted in 5 family items - again, not what I need. Based on the "?" explanation on the same page for the indexing embedded images option, I would expect this to solve my problem, but it does not. Based on what I am seeing in the metadata from the indexed email, it appears that Intella is interpreting the embedded images as attachments, which I would consider to be fundamentally incorrect. As for my question, is there any way for me as a user to manipulate the Intella indexing process in a way that prevents the split of embedded images (sig blocks are generally the biggest issue) as separate items in the index? In other words, is there something I can do in the above test that results in only a single email in the index as opposed to an email and 4 embedded images? I will say that an E-Discovery tool that we use for specific situations classifies all 4 embedded images as such and has a toggle to prevent the images from being separated as individual files from the parent email. Please let me know if this needs further clarification.
  8. Attempted to use ScanPST.exe and no luck, still hanging on the PST for multiple hours after crawling appears to end.
  9. Hello, I currently have an OST that is processing in 2.0.1 and seems to have stalled out. It spent about 2 hours actively processing about 550,000 items as I would expect, but since then, it has elapsed 16 hours with no additional items processed. Has this been encountered before and is it a known issue? Is it a bad/corrupt OST? Or am I just being impatient and there really isn't an issue? For an environment baseline, my machine has 32GBs RAM, 8 core CPU, 4 active crawlers, 2 GB memory per crawler (set in the ini file to fix a previous issue), and I have indexed PSTs/OSTs larger than this 31GB one perfectly fine. Any thoughts or suggestions appreciated. Thanks
  10. My company currently has 3 licenses of Intella and this problem persists with any computer that runs 1.9.1 and we try to export a large number of emails to a pst. This has worked perfectly fine in the past, so i don't know if 1.9.1 was the issue or if 2.0 fixed it. Regardless, I have tried different versions of Outlook (2007, 2010, and 2013), thinking that may be the issue, but it doesn't seem to matter. Here's an example situation. I have 3 internal drives, one where the case lives, one for the source evidence, and one for the export data. I have an index where I am trying to export out 50,000 items to a PST file. When the exporter gets to around 20,000 items (sometimes more, sometimes less. It is inconsistent), the exporter starts spitting errors for every item. When I open up the report file that was exported with the files, it simply says "Server response timed out" under the error column, and "skipped" under the skipped column. From some looking I've done, I can confirm that the drives aren't disconnecting. Unless Intella is the only tool that disconnects them temporarily, I use these drives on a daily basis and have no other issue. Has anyone else encountered this issue? And if so, how can I fix this? I can supply more info if need be. Thanks
  11. Thank you for the answer on this. However, I have a follow-up. Occasionally, in the FROM field, it shows just the name and email address for some messages and NOT the name and company, but for others it shows the name and company but NOT the name and email address. The behavior appears to be inconsistent. We are seeing some that show the name and email address in the FROM field for messages sent to people outside of the organization, as well as name and email address in the FROM field for messages sent to people inside of the organization. For instance, we have some messages where the FROM is "Miller, Jane <Jmiller@company.com>" ONLY and in the TO field we have "Bob Smith <BSmith@company.com>, Bob Smith </O=Company...>." No one is CCd on them. Based on the explanation provided, it would be expected to see Last Name, First Name </O=Company> in the FROM field. Those emails were exchanged within the organization only. However, we also have some messages with "Miller, Jane </O=Company...>" (so, no email address is shown) in the FROM field, followed by a TO field of "Smith, Bob </O=Company...>" (and again, no email). Those emails were exchanged within the organization only. What is the cause for the inconsistency, so that we may understand why we are seeing this behavior and be able to explain that to our clients? Is this just because one or the other field is unavailable on that particular message? Again, I can attempt to explain better if need be. Thanks
  12. Just a quick question. When I review an original email in an OST in Outlook, it has only a single name in a given field, e.g. "Bob Smith <BSmith@company.com>." However, when I process the OST in Intella (1.8.4, 1.9.1, 2.0.0 all appear to do this), there is an additional form of the name in the Preview and Contents tabs, e.g. "Bob Smith </O=Copmany...>" (See example below). In the client's eyes, it appears that the email had the individual in the TO field twice, sparking a question as to why. What original in Outlook and Intella Header tab displays: To: Bob Smith <BSmith@company.com> What Intella Contents/Preview tab and exported message in a PST displays: To: Bob Smith <BSmith@company.com>, Bob Smith </O=Company/OU=EXCHANGE ADMINISTRATIVE GROUP (*alpha-numeric characters*)/CN=RECIPIENTS/CN=BOB SMITH00A> I understand that this may be an Outlook thing and I understand that the "Bob Smith </O=..." is from a metadata field inside the message, but I am mostly curious as to why this additional address entry is appended to an exported email when the original does not have it (at least not in that field)? Is it pulling that metadata and then appending it to the TO field? If so, why is it doing this? Is there a need to do so when the original message does not have this format? It's not a huge issue, I would just like to be able to explain to clients the reason why there appears to be 2 of the same name in the address fields. If more clarification is needed, I can attempt to do so. Much thanks
  13. Any updates as to whether or not this will be in future versions? Or is it still a "maybe" type of feature?
  14. Coming back to this topic a year and some change later, has anything been added (or plan to be added) similar to what is mentioned here? Or any changes to deduplication in general between the 1.8 versions and 1.9 versions (particularly 1.9.2 and/or 1.9.3)? A configurable hashing formula to fit specific needs for deduplication would be phenomenal on many fronts, allowing the user to fine-tune how deduping is performed. I apologize for bringing an old topic back to life, but this problem apparently still persists for my company (same as OP).
×
×
  • Create New...