Jump to content

Roman Johnson

Escalation Engineer
  • Posts

    25
  • Joined

  • Days Won

    1

Everything posted by Roman Johnson

  1. Good idea. If the repair/rebuild doesn't resolve the issue, please provide the actual error in this thread. Thank you.
  2. During a Native Ingestion, you might come across an error when mapping database fields. That error would say "Error in before-edit: An item with the same key has already been added." If you ever see this error, go into Case Management > Database Fields. Sort the fields by the field name and delete any duplicate field entries. Once this is done, you can run the native ingestion like normal.
  3. This is great info! Thank you very much for posting this. I'm sure a lot of our clients will find this valuable.
  4. Give this a try, Dave: 1. Delete the exported clip 2. Reboot the machine 3. Re-run the export
  5. Different cases will act differently in Publish, depending on the case size, number of fields included, the amount of text for the documents, the number of pages for each document, etc.
  6. Different cases will act differently in Publish, depending on the case size, number of fields included, the amount of text for the documents, the number of pages for each document, etc.
  7. If you receive this error when trying to ingest natives, it is a permissions issue. If you open the ingestion log, you'll see "64 bit streaming object terminated with an exit code of: -999" What you can do to resolve this is run the Admin module as administrator via right-click > Run as administrator. This will elevate the permissions necessary to run the ingestion.
  8. If you receive this error when trying to ingest natives, it is a permissions issue. If you open the ingestion log, you'll see "64 bit streaming object terminated with an exit code of: -999" What you can do to resolve this is run the Admin module as administrator via right-click > Run as administrator. This will elevate the permissions necessary to run the ingestion.
  9. So you're running Eclipse SE Admin as an administrator, and you go to ingest natives, but you only see your C:\ drive; none of your other mapped drives are showing up. This is due to the default admin account on that machine not having those drives mapped. In order to fix this so that the drives will show up during an ingestion, you'll need to modify the registry. 1. Click your Start menu and type in regedit 2. Once you're in the registry, navigate to this location: HKEY_LOCAL_MACHINE > Software > Microsoft > Windows > CurrentVersion > Policies > System 3. Now, left-click on that System folder and select NEW > DWORD 4. Name it EnableLinkedConnections and hit Enter 5. Double-click that new registry key and set the value to 1, and click OK 6. Close the registry 7. Reboot the machine 8. Run SE Admin as an administrator and go to Ingest Natives 9. Voila! Your mapped drives will now show up
  10. So you're running Eclipse SE Admin as an administrator, and you go to ingest natives, but you only see your C:\ drive; none of your other mapped drives are showing up. This is due to the default admin account on that machine not having those drives mapped. In order to fix this so that the drives will show up during an ingestion, you'll need to modify the registry. 1. Click your Start menu and type in regedit 2. Once you're in the registry, navigate to this location: HKEY_LOCAL_MACHINE > Software > Microsoft > Windows > CurrentVersion > Policies > System 3. Now, left-click on that System folder and select NEW > DWORD 4. Name it EnableLinkedConnections and hit Enter 5. Double-click that new registry key and set the value to 1, and click OK 6. Close the registry 7. Reboot the machine 8. Run SE Admin as an administrator and go to Ingest Natives 9. Voila! Your mapped drives will now show up
  11. Did you select the 'keep families together when sorting' option? How was this data loaded? Were they all in PDF form? If so, then your BEGATT field won't be populated, causing family relationships to not exist.
  12. Did you select the 'keep families together when sorting' option? How was this data loaded? Were they all in PDF form? If so, then your BEGATT field won't be populated, causing family relationships to not exist.
  13. Did you select the 'keep families together when sorting' option? How was this data loaded? Were they all in PDF form? If so, then your BEGATT field won't be populated, causing family relationships to not exist.
  14. If you have a VM and Roaming Profiles setup, the first time you go to access the Eclipse site, everything will work great. Any subsequent launches into that VM will cause the Eclipse site to throw "An error occurred in the application you were using." On the end user's machine, the Eclipse site is a ClickOnce application. Microsoft ClickOnce deployment is not supported with Roaming Profiles. To resolve this issue, you'll either have to turn off Roaming Profiles, or, you can clear the app cache upon logging into that machine (BEFORE you launch Internet Explorer). The app cache can be cleared two different ways: 1. Navigate to %localappdata%\Apps\2.0 > Delete everything in the 2.0 folder 2. Create a batch file with this command: rundll32 %windir%\system32\dfshim.dll CleanOnlineAppCache Once the user has cleared the app cache, launch IE and browse to the Eclipse site If you choose to use the option to just clear the app cache, then keep in mind that it will need to be done every single time a user launches that VM and logs into Windows.
  15. If you have a VM and Roaming Profiles setup, the first time you go to access the Eclipse site, everything will work great. Any subsequent launches into that VM will cause the Eclipse site to throw "An error occurred in the application you were using." On the end user's machine, the Eclipse site is a ClickOnce application. Microsoft ClickOnce deployment is not supported with Roaming Profiles. To resolve this issue, you'll either have to turn off Roaming Profiles, or, you can clear the app cache upon logging into that machine (BEFORE you launch Internet Explorer). The app cache can be cleared two different ways: 1. Navigate to %localappdata%\Apps\2.0 > Delete everything in the 2.0 folder 2. Create a batch file with this command: rundll32 %windir%\system32\dfshim.dll CleanOnlineAppCache Once the user has cleared the app cache, launch IE and browse to the Eclipse site If you choose to use the option to just clear the app cache, then keep in mind that it will need to be done every single time a user launches that VM and logs into Windows.
  16. If you have a VM and Roaming Profiles setup, the first time you go to access the Eclipse site, everything will work great. Any subsequent launches into that VM will cause the Eclipse site to throw "An error occurred in the application you were using." On the end user's machine, the Eclipse site is a ClickOnce application. Microsoft ClickOnce deployment is not supported with Roaming Profiles. To resolve this issue, you'll either have to turn off Roaming Profiles, or, you can clear the app cache upon logging into that machine (BEFORE you launch Internet Explorer). The app cache can be cleared two different ways: 1. Navigate to %localappdata%\Apps\2.0 > Delete everything in the 2.0 folder 2. Create a batch file with this command: rundll32 %windir%\system32\dfshim.dll CleanOnlineAppCache Once the user has cleared the app cache, launch IE and browse to the Eclipse site If you choose to use the option to just clear the app cache, then keep in mind that it will need to be done every single time a user launches that VM and logs into Windows.
  17. If you're coding in the grid view, you can hit Ctrl+Down Arrow to go down to the next document (within the same column).
  18. If you're coding in the grid view, you can hit Ctrl+Down Arrow to go down to the next document (within the same column).
  19. If you're coding in the grid view, you can hit Ctrl+Down Arrow to go down to the next document (within the same column).
  20. Alternatively, there is a report in the Admin module that can do this as well. Go to Reports > Case Data Summary, and select your case. Select the option for 'Image File Size.' Set the radio button to Advanced Search, click the build search button, and run your search for that subset of documents. Once you've done all of this, click the Start button on the bottom right corner. This will show you your total pages, and the image size as well.
  21. Alternatively, there is a report in the Admin module that can do this as well. Go to Reports > Case Data Summary, and select your case. Select the option for 'Image File Size.' Set the radio button to Advanced Search, click the build search button, and run your search for that subset of documents. Once you've done all of this, click the Start button on the bottom right corner. This will show you your total pages, and the image size as well.
  22. Alternatively, there is a report in the Admin module that can do this as well. Go to Reports > Case Data Summary, and select your case. Select the option for 'Image File Size.' Set the radio button to Advanced Search, click the build search button, and run your search for that subset of documents. Once you've done all of this, click the Start button on the bottom right corner. This will show you your total pages, and the image size as well.
  23. Although eScan-IT doesn't offer the functionality to directly placeholder Excel files, you can "trick" it into doing so by following these steps. Please note that you must have Microsoft Office 2010 or newer, otherwise this will not work. 1. Launch Excel 2. Click on File, or the Home menu, in the top left corner 3. Click on Options 4. Go to the Trust Center section 5. Click the Trust Center Settings button 6. Go to the File Block Settings section 7. You'll see three different columns here: File Type, Open, and Save. Put a checkmark in every single box in the Open column 8. On the bottom, there are 3 radio buttons. Set the button to the middle one, which says "Open selected file types in Protected View" 9. Click OK 10. Click OK again 11. Close out of Excel 12. Launch eScan-IT and begin your EDD batch. Now, whenever eScan-IT tries to process an Excel file, it won't be able to open it, causing it to force an Exception placeholder to be given Now, if you'd like to reprocess these in QC to get accurate images, you'll need to undo what you just did in Excel. To do this, just go back into the File Block Settings section in the Trust Center, and hit that button that says Restore Default. Once you've restored those default settings, close out of Excel, go into QC in eScan-IT and reprocess those files as you see fit.
  24. The easiest fix for a blank native path is to click the button that says "Edit Native File Path." By clicking this button, it will scroll through each record in the DAT file until it comes across the first path in that field.
  25. When ingesting a Unicode PST into Eclipse SE, you can potentially get errors stating that it's "Unable to extract file from attachment #:". You'll then see a filename with special characters that shouldn't be there. This is due to the fact that there are Unicode characters in the subject line of the email. The 32-bit version of Stellent doesn't support those characters in the filename/subject line. When you see this error, it also means that you're case will be missing those parent items. There are two ways to fix this: Option 1: Purchase the Streaming Ingestion license for the 2016.3.2 version of Eclipse SE, and ingest the PST that way Option 2: Convert the Unicode PST to ANSI 1. Launch Microsoft Outlook 2. On the Home screen, click on New Items > More Items > Outlook Data File 3. Provide the new ANSI PST with a name, then click the drop-down menu for 'Save as type' and set this to Outlook 97-2002 Data File. Click OK. You have now created an ANSI PST file 4. Now, you need to load the Unicode PST into Outlook. Click on File > Open > Open Outlook Data File 5. Point to the Unicode PST and click Open 6. On the far left panel of Outlook, you will now see at least two different PSTs. One for your ANSI PST, and the other for the Unicode PST that you just opened 7. Go to File > Open > Import 8. Set the action to Export to a File, and click Next 9. You want to set this file type to Outlook Data File, and click Next 10. You are now presented with another window that says "Select the folder to export from:". You will be selecting either the entire Unicode PST, OR you will be selecting individual folders from that Unicode PST. **Please note that Microsoft has a limit on the maximum file size for ANSI PSTs. This limit is set to 1.93 GB. If your Unicode PST is larger than that, then you'll need to create ANSI PSTs for each root folder within the PST, and convert the folders accordingly from the Unicode to the ANSI PST** 11. On this next screen, you'll be browsing to the ANSI PST that you created, and also set the radio button to Allow Duplicate Items to be Created. Click Finish. 12. You'll then be presented with a warning message that basically says you are exporting data to a file that doesn't support Unicode. Just click OK 13. Once the export completes, navigate to the directory that you saved/created your ANSI PST in. This PST can now be ingested into Eclipse SE, under the Ingest Natives screen, without getting those errors
×
×
  • Create New...