Jump to content

Roman Johnson

Escalation Engineer
  • Posts

    25
  • Joined

  • Days Won

    1

Roman Johnson last won the day on October 21 2016

Roman Johnson had the most liked content!

About Roman Johnson

  • Birthday 11/03/1984

Roman Johnson's Achievements

Enthusiast

Enthusiast (6/14)

20

Reputation

  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.
×
×
  • Create New...