Jump to content

Andrew Coody

IPRO Employee
  • Posts

    60
  • Joined

  • Days Won

    1

Andrew Coody last won the day on April 17 2018

Andrew Coody had the most liked content!

About Andrew Coody

Andrew Coody's Achievements

Enthusiast

Enthusiast (6/14)

12

Reputation

  1. ISSUE: On a periodic basis, you may find that when you try to open a case that the splash screen for Eclipse SE hangs on "Loading Grid...". This can happen on just one SE user account or for many, and also be isolated to just one machine or several. It's profile- and machine-dependent, so the fix outlined below will need to be performed on each affected machine. CULPRIT: Here are a couple most-common culprits. They can individually or collectively be the culprit, and this can occur at random unfortunately. • Grid size is set to 5,000 or 10,000. • 'Wrap text in grid' is enabled. RESOLUTION: 1) Close Eclipse SE Admin and Desktop 2) Open Windows Explorer and in the address bar type %localappdata% 3) Find and open Ipro_Tech,_LLC. Delete all folders that start with EclipseDesktop.exe_Url_... 4) Go back a folder and navigate to IProEclipse. Delete the UserSettings folder. 5) Launch Eclipse SE Admin and find the case with the smallest possible document count under case management and take note of it. 6) Launch Eclipse SE Desktop and open that small case. 7) Once the case loads, change the following settings (you can adjust them back later*): • Change the grid size to 50. • Turn off 'Wrap text in grid' option. Because there is no checkbox for this option, you'll only know if it's enabled if the physical record lines are larger in size than each other and text from various fields is wrapped to the next line. Here's a before and after example: If wrapping is on, right-click and click 'Wrap text in grid'. 8) After these options have been corrected, go to open case and try your original case that would not load. It should load fine now. *We don't recommend reverting any of settings back as the issue may recur, but if it's absolutely necessary, adjust any of these settings as you need to.
  2. ISSUE: Do you receive the following error when trying to submit an Enterprise Image (EI) job in Eclipse? Error adding documents: System.Exception: Exception of type 'System.Exception' was thrown. [submit] CAUSE: The machine you're trying to run the EI job from is out of sync with the IIS machine. FIX: You'll need to run the following script in the Windows Command line on the machine you're running the EI job from. It's also recommended to run it on all machines in your environment because if one machine is out-of-sync, others might be as well. net time \\IIS_Server /set /y replace the word "IIS_Server" with the actual hostname (computer name) of your IIS machine.* * If your company happens to use a NTP (Network Time Protocol) server that your IIS and/or DC (Domain Controller) machines point to to get their time, please substitute the IIS_Server for the NTP_Server
  3. @Hui Jiang Nothing shows up in your last post. I recommend you call in to Support at 877-324-4776 at your earliest convenience so we can work with you on the phone and possibly a remote session to assist with this issue.
  4. @Hui Jiang Thank you for your inquiry. I do apologize, but the screenshot you tried to attach to the post did not work. It created a looooong list of garbled/hashed text instead (see example below). Can you please retry attaching it to this post, or email it in to support@iprotech.com?
  5. [uSER=1265]jmiddleton101[/uSER] You are correct, though, that this will be a temporary fix. I can only recommend that you disable Windows updates on Windows 10 machines for now until the network version's patch is available (no ETR to my knowledge at the time of this post). I do apologize for the inconvenience experienced. Please let us know if you have any further questions or issues.
  6. [uSER=1272]bcelio[/uSER] I have checked the license count for your company and confirmed you have 50 eCapture worker licenses, 60 imaging worker licenses, 30 regular ocr licenses, and 30 multi-lingual ocr worker licenses. There are more licenses on your account, but these seemed to be the only one's relevant to your question/issue. My colleague [uSER=918]William Cherry[/uSER] already highlighted a couple possible reasons why eCapture may not utilize all licenses, but I'd like to add one more reason. Sometimes it's as simple as the type of job being ran / task type eCapture is performing that limits the workers used. You can identify this if you go to the 'Queue Status Information' tab in the eCapture Controller when a job is running, and you'll see the task types with three designations beside them. Each designation has a value assigned to it: Unrestricted (tasks of this type may be performed by any worker at any time) Restricted (one task of this type at a time per worker) Exclusive (only one of that type per Discovery Job, usually indexing) This information is available in the 2018.5.1 eCapture user guide on pages 79-80. I hope this information helps!
  7. [uSER=541]jpena@wtk[/uSER] I have previewed the release notes for the latest eCapture version coming out. There are a lot of enhancements and fixes to the application as a whole, and some specific to Office Excel-related documents, but nothing as far as the user interface for modifying Excel files before TIFFing. I do apologize for the inconvenience. I'll look into any feature requests/bug fixes that might exist for this and hopefully they'll get this into a future release.
  8. [uSER=541]jpena@wtk[/uSER] Thank you for the inquiry. At the time of this post, there is no newer version of Eclipse SE available besides 2017.4.1, which is the version I made my reply and screenshots with. I do know that there are some newer version of our enterprise products coming out very soon, so I will make a note to check the release notes when they are available and will reply back if any updates in this area have been made.
  9. Have you tried to run EDD in eScan-IT and noticed that the following error appears and then eScan-IT crashes? ERROR: eScan-IT has stopped working a problem caused the program to stop working correctly. please close the program If you go to Event Viewer > Application right after closing out of the program, you'll notice that an 'Error' level event will have occured something to the effect of the below: Faulting application name: eScanIT.exe, version: 17.0.3.4, time stamp: 0x591e2482 Faulting module name: MSVBVM60.DLL, version: 6.0.98.15, time stamp: 0x49b01fc3 Exception code: 0xc0000005 Fault offset: 0x000def8a Faulting process id: 0x2de0 Faulting application start time: 0x01d3e7d6954566a7 Faulting application path: C:\Program Files (x86)\IPRO Tech\eScan-IT\eScanIT.exe Faulting module path: C:\WINDOWS\SYSTEM32\MSVBVM60.DLL Report Id: 70a1a090-1559-4796-9308-2831b3d94499 Faulting package full name: Faulting package-relative application ID: WHO/WHAT: iAPrintManager by nQueue Billback LLC (a cost recovery and document scanning and routing technology company) WHY: Since this program is basically a print management application, eScan-IT cannot be managed by any external print management applications The iAPrintManager application is basically interjecting over the eScan-IT EDD process in the background causing it to crash when trying to launch the EDD part of the program. RESOLVE: uninstall iAPrintManager
  10. Have you ever loaded up a job in QC and wanted to Auto-QC it only to find out that the option is grayed out (figure 1)? figure 1 →→→↑ The answer lies with what type of job you performed post-Discovery. Was it a Processing job or a Data Extract (DE) job? If it is the latter then that is the reason. Why? Because DE jobs do not have images whereas Processing jobs do. The Auto-QC utility is built around the premise that the reviewer would spot-check the images as QC automatically QCs the record(s), but with a Data Extract job lacking images, the Auto-QC utility would not compliment that same workflow.
  11. Odds are, you may have thought this very question yourself, or some variation of it. Figure 1 shows a sample of what Eclipse SE's system authorization menu looks like if you are using remote auth or do not yet have the program authorized yet. Figure1 When you use the remote authorization method (which we highly recommend), Eclipse SE hands-over to Ipro Authorization Manager the ability to address all authorization-related functionality. As a result, the serial number, client ID, and "modules" boxes will be empty.
  12. @ascott Below the screenshot/figure in my last post I mentioned a workaround which is similar to your method, but you don't need to use Excel, as far as I'm aware. Instead of choosing to export as a CSV, simply choose a DAT file on the mass actions export screen. All of the built-in system fields are pre-determined by the Developers as to what they should be, and unfortunately we have no control over changing them since they are non-editable fields. Here's my thought as to the likely idea why the Developers have this as a long text field type: CASE A may have a shorter relative path like \\this\is\my\really\really\short\diverged\file\path, but CASE B could have a relative path that is something in the likeness of \\this\is\my\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\long ("short")\diverged\file\path. The point here is that this field can literally be relative in terms of how long the diverged path is -- one case might be shorter or longer than another case, so there's no way to guarantee it. I will gladly put in a feature request to make this an optionally editable field -- optionally in the perspective that there would need to be some measure, determined by average length of all documents maybe, of the field and at some cut-off it would auto-lock into a LongText field type vs an editable FixedLengthText field. Let me know!
  13. @ascott Below the screenshot/figure in my last post I mentioned a workaround which is similar to your method, but you don't need to use Excel, as far as I'm aware. Instead of choosing to export as a CSV, simply choose a DAT file on the mass actions export screen. All of the built-in system fields are pre-determined by the Developers as to what they should be, and unfortunately we have no control over changing them since they are non-editable fields. Here's my thought as to the likely idea why the Developers have this as a long text field type: CASE A may have a shorter relative path like \\this\is\my\really\really\short\diverged\file\path, but CASE B could have a relative path that is something in the likeness of \\this\is\my\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\long ("short")\diverged\file\path. The point here is that this field can literally be relative in terms of how long the diverged path is -- one case might be shorter or longer than another case, so there's no way to guarantee it. I will gladly put in a feature request to make this an optionally editable field -- optionally in the perspective that there would need to be some measure, determined by average length of all documents maybe, of the field and at some cut-off it would auto-lock into a LongText field type vs an editable FixedLengthText field. Let me know!
  14. @ascott Below the screenshot/figure in my last post I mentioned a workaround which is similar to your method, but you don't need to use Excel, as far as I'm aware. Instead of choosing to export as a CSV, simply choose a DAT file on the mass actions export screen. All of the built-in system fields are pre-determined by the Developers as to what they should be, and unfortunately we have no control over changing them since they are non-editable fields. Here's my thought as to the likely idea why the Developers have this as a long text field type: CASE A may have a shorter relative path like \\this\is\my\really\really\short\diverged\file\path, but CASE B could have a relative path that is something in the likeness of \\this\is\my\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\really\long ("short")\diverged\file\path. The point here is that this field can literally be relative in terms of how long the diverged path is -- one case might be shorter or longer than another case, so there's no way to guarantee it. I will gladly put in a feature request to make this an optionally editable field -- optionally in the perspective that there would need to be some measure, determined by average length of all documents maybe, of the field and at some cut-off it would auto-lock into a LongText field type vs an editable FixedLengthText field. Let me know!
  15. @ascott I did a bit of brushing-up reading of the Smart Folder section in the Eclipse Admin user guide and found a very useful graph that I think will help out. The key takeaway is that there are only certain allowed built-in system fields you can use, along with any custom fields created that have a field type of FixedLengthText and not something like LongText or DateTime. (See Figure 1). figure 1 (click for larger view) [ATTACH=CONFIG]n2724[/ATTACH] As a result, I did some testing and created a TEST field with a field type of LongText in my sandbox case. I tried to create a smart folder based on it and verified it did not show up. I deleted the field and created a TEST2 field as a FixedLengthText and it did show up in the smart folder list. The problem is you have a field that cannot be used - File Path Relative - because it is long text. So, the only viable workaround I could come up with was to create a new field called "File Path Relative 2" as a FixedLengthText, export BEGDOC and the current "File Path Relative" field to a DAT file directly from the grid in Eclipse web, and then import overlay back into the case (begdoc on begdoc and FilePathRelative on FilePathRelative2). This essentially makes a copy of the database field that you can then overlay the same data in that field into it, and then perform the smart folder build. I hope this information helps. Please let me know if you have any further questions or issues with this.
×
×
  • Create New...