Jump to content

Josiah

IPRO Employee
  • Posts

    43
  • Joined

  • Days Won

    2

Josiah last won the day on April 3 2018

Josiah had the most liked content!

About Josiah

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Josiah's Achievements

Enthusiast

Enthusiast (6/14)

20

Reputation

  1. Hello Bcelio, Unfortunately, there isn't a way through Ipro software to force a worker to auto-startup. However, you can use the windows startup feature to add the worker's EXE to the startup list. 1) To open the “Startup� folder the easy way, just hit Windows+R to open the “Run� box, type “shell:startup,� and then press Enter. 2) Open another file explorer window and navigate to the following directory ""C:\Program Files (x86)\Ipro Tech\eCapture\Worker" Right click on the Worker.exe and select create shortcut. Then copy the shortcut 3) In the Startup folder paste the worker shortcut. The next time you restart the worker machine and login as that user, it will auto-start the worker.
  2. Hello Matthew, Unfortunately that would be the only way to get a range of begdocs. I have submitted a feature request to allow users to select the Operator "Between" The Feature request ID is TS-4908. Let me know if you need anything else!
  3. Hey Jeff! This feature is slated to be released in not the next release, but the release following it. At this time they haven't given a timeline as to when it will be released. Once I hear something, I will be sure to let you know Mac
  4. When you published the case, did you ensure that the folder structure that was created remained intact? If you are unsure, I would recommend either scheduling a time for one of our support representatives to take a look, or give us a call at (877) 324-4776 or (602) 324-4780 -Mac
  5. Hello, There is currently not a way to do that so I have added this as a feature request. Thank you for your suggestion!
  6. Josiah

    Non-Discovery Docs

    Hello Lyndsay! To add case Documents you need to log into Eclipse SE Desktop. Once logged in click "Client/Case Management" > "Case Management" > Select the case you are wanting to add Case documents to Once you've selected the case. You will see a grid display in the middle, select the tab you want (i.e Case Documents") Then on the right click the sun Icon. Select the file(s) you want to add then click "Open" Let me know if you have any questions Josiah
  7. Josiah

    Custom Logo

    Also, it should be noted that you will need to recycle the Eclipse Site after updating the logo.
  8. Hey FreshLikeSushi, At this time, all redactions are still a manual process. I like the idea though, so I sent up a feature request to our development team to see if this is something the can implement in a future release!
  9. Thanks for this Michael, Question for you on this. What would normally cause this value to be incorrect? I'm assuming it gets inserted when the ADD is installed, or upgraded, but what would cause it to become incorrect?
  10. Thanks for this Michael, Question for you on this. What would normally cause this value to be incorrect? I'm assuming it gets inserted when the ADD is installed, or upgraded, but what would cause it to become incorrect?
  11. When looking at native documents in the Document viewer, you may come across a document that instead of showing the native, shows the following: http://i.imgur.com/li8X2Cp.png This can be fixed if you have access to SQL and following the steps below: 1) Locate Eclipse Config Database (Usually title Eclipse_Config, EclipseConfig, etc) 2) run the following query to see what the current size is set to: USE [insert Eclipse Config DB name here] SELECT * FROM ReviewAdmin.SystemSettings Under 'NativeViewerFileSizeLimitMB' you will see what the current limit is set to in MB Now you get to determine the size limit that you would want. I generally wouldn't do more than 100MB as too large will cause more latency on the system, and anything too large can still be viewed in the native application if needed. 3) here's the query to update the limit: USE [insert Eclipse Config DB name here] UPDATE ReviewAdmin.SystemSettings SET SettingValue = --Put size limit, this size is in MB WHERE SettingKey = 'NativeViewerFileSizeLimitMB' Now you should be able to click on that document and view it within the native viewer.
  12. Came across this and wanted to share it as the Errors are confusing. I got this when running Email Threading. I know my case has extracted text and that Content Analytics is running (Checked the Service, and that Java was running and using Memory in Task Manager) In Eclipse Admin you will see the following: 8/22/2017 10:38:38: E-mail thread processing started Log file: C:\Users\testing-jdudley\AppData\Roaming\Eclipse\Eclipse Admin\jmdIpro_EmailThreading.log 8/22/2017 10:38:38: Number of documents to process: 100 8/22/2017 10:38:38: Clearing EmailThreadingProcessed flag for doc ids 8/22/2017 10:38:38: Staging area id: Eclipse_Email_jmdIpro 8/22/2017 10:38:50: Stage 1 - adding documents 8/22/2017 10:38:50: adding 100 documents to the staging area 8/22/2017 10:39:34: Stage 2 - processing 8/22/2017 10:39:46: Stage 3 - retrieving results 8/22/2017 10:39:49: An exception occurred in the background worker thread for email threading: One or more errors occurred. 8/22/2017 10:39:49: 100 documents processed. 8/22/2017 10:39:49: Processing complete However, nothing is put into the case in Eclipse. Checking CAAT Errors in "C:\CAAT\logs" returned the following: 2017-08-22 10:38:49,897 <<Eclipse_Email_jmdIpro>> WARN ProxyFactory <init>: Method [{0}] is synthetic and is being intercepted by {1}. This could indicate a bug. The method may be intercepted twice, or may not be intercepted at all. But no actual Error. Checking Admin Log in "C:\ProgramData\IPRO Tech\Eclipse\Admin" returned the following: 2017-08-22 10:39:49.0411 [5] ERROR Eclipse.Admin.PresentationLayer.HomeTab.ucContentAnalystEmailThreading - One or more errors occurred.* at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Eclipse.Admin.PresentationLayer.HomeTab.ucContentAnalystEmailThreading.GetBatchSize() at Eclipse.Admin.PresentationLayer.HomeTab.ucContentAnalystEmailThreading.EmailThreadProcess_RetrieveResultsToTransferImportFile(IEnumerable`1 ca_fields, List`1 eclipse_fields, String contentAnalystServer, String transferImportFilePath) at Eclipse.Admin.PresentationLayer.HomeTab.ucContentAnalystEmailThreading.backgroundWorker1_DoWork(Object sender, DoWorkEventArgs e) If you are getting the above error, you will want to check your Eclipse Endpoints for that Admin machine. There are three files that need to be checked: "C:\Program Files\Ipro Tech\Eclipse\Admin\Eclipse Admin.exe.config" "C:\Program Files\Ipro Tech\Eclipse\Admin\EclipseOcrImaging\EclipseOcrImaging.exe.config" "C:\Program Files\Ipro Tech\Eclipse\Admin\File Identification\EclipseFileIdentification.exe.config" For my issue, I notice that my Eclipse Endpoint was set to http://machinename:443/ However, my client wasn't using an SSL for Eclipse and should have been http://machinename:80/ You can locate the correct setting by looking at the site bindings for the Eclipse Site on the IIS machine, or if you have an Admin machine that is able to perform analytics, I would copy their config files into the admin machines that is having issues with Analytics. Once you modified the Config files, close and re-open Admin. A valid Threading should look like the following: 8/22/2017 11:03:35: E-mail thread processing started Log file: C:\Users\testing-jdudley\AppData\Roaming\Eclipse\Eclipse Admin\jmdIpro_EmailThreading.log 8/22/2017 11:03:37: Number of documents to process: 100 8/22/2017 11:03:37: Clearing EmailThreadingProcessed flag for doc ids 8/22/2017 11:03:37: Staging area id: Eclipse_Email_jmdIpro 8/22/2017 11:03:37: Stage 1 - adding documents 8/22/2017 11:03:37: (re)adding 100 documents to the staging area 8/22/2017 11:03:57: Stage 2 - processing 8/22/2017 11:04:08: Stage 3 - retrieving results 8/22/2017 11:04:17: Stage 4 - Enqueue import job to move data to Eclipse tables 8/22/2017 11:04:18: Import File: \\testing.local\dfs\SupportTestRacks\TST-SUPTRK078\Eclipse\jmdIpro\jmdIpro\Transfer\CAEmailTreading-20170822-1104080379\_TRANSFER.DLF 8/22/2017 11:04:18: Error Load Files will write to: \\testing.local\dfs\SupportTestRacks\TST-SUPTRK078\Eclipse\jmdIpro\jmdIpro\Transfer\CAEmailTreading-20170822-1104080379 8/22/2017 11:04:18: Step: Initializing Status: In Queue 8/22/2017 11:04:24: Step: Initializing Status: In Progress 8/22/2017 11:04:24: Step: Staging Status: In Progress 8/22/2017 11:04:26: Step: Integrating Status: In Progress 8/22/2017 11:04:31: Step: Building Smart Folders Status: In Progress 8/22/2017 11:04:32: Step: Updating Case Properties Status: In Progress 8/22/2017 11:04:33: Import completed, updating processed flags 8/22/2017 11:04:33: 100 documents processed. 8/22/2017 11:04:33: Processing complete
  13. Came across this and wanted to share it as the Errors are confusing. I got this when running Email Threading. I know my case has extracted text and that Content Analytics is running (Checked the Service, and that Java was running and using Memory in Task Manager) In Eclipse Admin you will see the following: 8/22/2017 10:38:38: E-mail thread processing started Log file: C:\Users\testing-jdudley\AppData\Roaming\Eclipse\Eclipse Admin\jmdIpro_EmailThreading.log 8/22/2017 10:38:38: Number of documents to process: 100 8/22/2017 10:38:38: Clearing EmailThreadingProcessed flag for doc ids 8/22/2017 10:38:38: Staging area id: Eclipse_Email_jmdIpro 8/22/2017 10:38:50: Stage 1 - adding documents 8/22/2017 10:38:50: adding 100 documents to the staging area 8/22/2017 10:39:34: Stage 2 - processing 8/22/2017 10:39:46: Stage 3 - retrieving results 8/22/2017 10:39:49: An exception occurred in the background worker thread for email threading: One or more errors occurred. 8/22/2017 10:39:49: 100 documents processed. 8/22/2017 10:39:49: Processing complete However, nothing is put into the case in Eclipse. Checking CAAT Errors in "C:\CAAT\logs" returned the following: 2017-08-22 10:38:49,897 <<Eclipse_Email_jmdIpro>> WARN ProxyFactory <init>: Method [{0}] is synthetic and is being intercepted by {1}. This could indicate a bug. The method may be intercepted twice, or may not be intercepted at all. But no actual Error. Checking Admin Log in "C:\ProgramData\IPRO Tech\Eclipse\Admin" returned the following: 2017-08-22 10:39:49.0411 [5] ERROR Eclipse.Admin.PresentationLayer.HomeTab.ucContentAnalystEmailThreading - One or more errors occurred.* at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at Eclipse.Admin.PresentationLayer.HomeTab.ucContentAnalystEmailThreading.GetBatchSize() at Eclipse.Admin.PresentationLayer.HomeTab.ucContentAnalystEmailThreading.EmailThreadProcess_RetrieveResultsToTransferImportFile(IEnumerable`1 ca_fields, List`1 eclipse_fields, String contentAnalystServer, String transferImportFilePath) at Eclipse.Admin.PresentationLayer.HomeTab.ucContentAnalystEmailThreading.backgroundWorker1_DoWork(Object sender, DoWorkEventArgs e) If you are getting the above error, you will want to check your Eclipse Endpoints for that Admin machine. There are three files that need to be checked: "C:\Program Files\Ipro Tech\Eclipse\Admin\Eclipse Admin.exe.config" "C:\Program Files\Ipro Tech\Eclipse\Admin\EclipseOcrImaging\EclipseOcrImaging.exe.config" "C:\Program Files\Ipro Tech\Eclipse\Admin\File Identification\EclipseFileIdentification.exe.config" For my issue, I notice that my Eclipse Endpoint was set to http://machinename:443/ However, my client wasn't using an SSL for Eclipse and should have been http://machinename:80/ You can locate the correct setting by looking at the site bindings for the Eclipse Site on the IIS machine, or if you have an Admin machine that is able to perform analytics, I would copy their config files into the admin machines that is having issues with Analytics. Once you modified the Config files, close and re-open Admin. A valid Threading should look like the following: 8/22/2017 11:03:35: E-mail thread processing started Log file: C:\Users\testing-jdudley\AppData\Roaming\Eclipse\Eclipse Admin\jmdIpro_EmailThreading.log 8/22/2017 11:03:37: Number of documents to process: 100 8/22/2017 11:03:37: Clearing EmailThreadingProcessed flag for doc ids 8/22/2017 11:03:37: Staging area id: Eclipse_Email_jmdIpro 8/22/2017 11:03:37: Stage 1 - adding documents 8/22/2017 11:03:37: (re)adding 100 documents to the staging area 8/22/2017 11:03:57: Stage 2 - processing 8/22/2017 11:04:08: Stage 3 - retrieving results 8/22/2017 11:04:17: Stage 4 - Enqueue import job to move data to Eclipse tables 8/22/2017 11:04:18: Import File: \\testing.local\dfs\SupportTestRacks\TST-SUPTRK078\Eclipse\jmdIpro\jmdIpro\Transfer\CAEmailTreading-20170822-1104080379\_TRANSFER.DLF 8/22/2017 11:04:18: Error Load Files will write to: \\testing.local\dfs\SupportTestRacks\TST-SUPTRK078\Eclipse\jmdIpro\jmdIpro\Transfer\CAEmailTreading-20170822-1104080379 8/22/2017 11:04:18: Step: Initializing Status: In Queue 8/22/2017 11:04:24: Step: Initializing Status: In Progress 8/22/2017 11:04:24: Step: Staging Status: In Progress 8/22/2017 11:04:26: Step: Integrating Status: In Progress 8/22/2017 11:04:31: Step: Building Smart Folders Status: In Progress 8/22/2017 11:04:32: Step: Updating Case Properties Status: In Progress 8/22/2017 11:04:33: Import completed, updating processed flags 8/22/2017 11:04:33: 100 documents processed. 8/22/2017 11:04:33: Processing complete
  14. I have come across this a few times when a client is attempting to do an overlay on existing documents. As you can see in the example image, I am doing an overlay, which you would expect the DocKeys to be the same. However, the true error is that the Load file for the BegDoc (ImageKey) doesn't match the exact Case that the existing BegDoc has. As you can see the overlayed begdoc is in all lowercase, but the original is in all Upper case. An easy fix is to open the load file in Notepad++ and do a find and replace and adjust the begdoc to match what is in the case database.
  15. I have come across this a few times when a client is attempting to do an overlay on existing documents. As you can see in the example image, I am doing an overlay, which you would expect the DocKeys to be the same. However, the true error is that the Load file for the BegDoc (ImageKey) doesn't match the exact Case that the existing BegDoc has. As you can see the overlayed begdoc is in all lowercase, but the original is in all Upper case. An easy fix is to open the load file in Notepad++ and do a find and replace and adjust the begdoc to match what is in the case database.
×
×
  • Create New...