Jump to content

Barrett Gardner

Cloud Solutions Architect
  • Posts

    53
  • Joined

  • Days Won

    1

Everything posted by Barrett Gardner

  1. Hello Milind, eCapture uses Leadtools as its OCR engine.
  2. Excellent, I'm glad Tanner was able to answer your questions. Please let us know if you need anything else.
  3. Hi, The error 'Cannot insert duplicate key in object 'dbo.DataExtractMetadataExtended' is not a normal or common status during OCR. Can you please include the full stack trace error logged by the worker in an email to support@iprotech.com so we can review the issue further? Thank you.
  4. Jeff I can submit this to eCapture Product Management for you as a feature request in a future release.
  5. Hi Stephen, I tested and confirmed that this functionality is not currently supported in eCapture upon export. I can only get this to work when importing and exporting both as single pages, however the document boundaries are lost during this process and will require a similar manual editing process post-export. I can submit this to eCapture Product Management for further review to be addressed in a future release. If you can provide your email address to me I can forward you the request information. Thanks.
  6. Hi Gayle, I have submit this request to Eclipse SE Product Management for further review. Let us know if you have any additional questions regarding this request. Thanks!
  7. It appears that not all documents in your loadfile have a NATIVE file path for import. We would recommend first importing the .DAT file without mapping the native file. Once this import is completed, make a copy of the .DAT file and delete all of the rows for the documents in the beginning of the file that do not have a NATIVE file path populated until you hit a document that does. Be sure to maintain the column headers. Then save this modified .DAT file and perform an overlay of just the NATIVE file path. Using this new loadfile will allow the application to see a record that contains the NATIVE file path immediately without having to search or hunt down another sample record within the loadfile that has this path to map.
  8. Starting in 2018.5, Eclipse user and group permissions have migrated to ADD Web. When new users are created in Eclipse Web Administration with 'User must change password on next login' option enabled, the user will encounter an error in red text upon changing their password: "An unhandled exception occurred on the ADD server" The following stack trace will be logged to the Enterprise.ErrorLogEntry in the ADDconfig database: "Nucleus.Domain.ErrorHandling.UnauthorizedException: You do not currently have permission to edit this User." We recommend creating the new users in ADD Web under System > Users to avoid this issue moving forward.
  9. The following error may be thrown by eCapture Worker servers configured with Office 2016, resulting in unsuccessful task completion in any job: System.Exception: System.InvalidCastException: Unable to cast COM object of type 'Microsoft.Office.Interop.Excel.ApplicationClass' to interface type 'Microsoft.Office.Interop.Excel._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{000208D5-0000-0000-C000-000000000046}' failed due to the following error: Interface not registered (Exception from HRESULT: 0x80040155). at System.StubHelpers.StubHelpers.GetCOMIPFromRCW(Object objSrc, IntPtr pCPCMD, IntPtr& ppTarget, Boolean& pfNeedsRelease) at Microsoft.Office.Interop.Excel.ApplicationClass.set_DisplayAlerts(Boolean RHS) at Ipro.eCapture.ecProcess.Service.ObjectManager.get_ExcelApplication() at Ipro.eCapture.ecProcess.Service.PageCounter.ExcelGetPageCount(String fileName) at Ipro.eCapture.ecProcess.Service.PageCounter.DiscGetPageCount(String targetFileName, Int32 stellentID) at Ipro.eCapture.ecProcess.Service.PageCounter.GetPageCount(String targetFile, Int32 stellentID, Int32 timeoutSeconds) at Ipro.eCapture.ecProcess.Service.WorkDispatcher.GetPageCount(String targetFile, Int32 stellentID, Int32 timeoutSeconds) at Ipro.eCapture.ecProcess.Service.ecProcessService.GetPageCount(GetPageCountArgs args) at Ipro.eCapture.Processing.ecProcessWrapper.GetPageCount(String targetFile, Int64 stellentID, Int32 timeoutLimit) at Ipro.eCapture.Discovery.DiscoverDocument.CalculatePageCount(DiscoverDocumentStatus& DocStatus, ecProcessWrapper& processor, Int32 TaskTimeout) at Ipro.eCapture.Discovery.DiscoverDocument.DiscoverDocument(DiscoverDocumentStatus& DocStatus, ResourcesProxy& Resources, ecProcessWrapper ecProcessor, Int32 indexesPerJob, List`1& indexTargetKeysToAdd, Boolean& lotusInitialized, Boolean lotusDXLMethod, Boolean extractAttachmentAndEmbedded) at Ipro.eCapture.Discovery.Discovery.DiscoverDocumentGroup() at Ipro.eCapture.Discovery.Discovery.Discover(Task& t) A repair on the Office installation followed by server reboot resolved this error.
  10. Starting with the 2018.5 release, All Eclipse permissions and permissions templates will be migrated to ADD Web. Upon upgrade, existing permissions templates CANNOT BE MODIFIED and new permissions templates CANNOT BE CREATED. If there are any permissions templates you wish to either create or modify in your current Eclipse environment, we strongly recommend to perform these updates/modifications PRIOR TO upgrading to the 2018.5 version. Thanks.
  11. Extract email metadata from emails converted to PDF (33940) - Standalone emails which have been converted to PDF prior to ingestion into eCapture will be hashed using configured 'Custom Email Hash' settings when any of the following fields are identified in the file (MailFrom, MailTo, MailCC, MailDate, or MailSubject). Associated email metadata fields (MailFrom, MailTo, MailCC, MailDate, MailSubject, MailFolder, and MailTransportHeader) are also extracted and are available upon export. Streaming Discovery – Disable all file extraction (38728) - The checkbox 'Enable file extraction' is now present within 'Discovery Options' which allows all extraction to be disabled. This option is set to enabled by default and the existing 'Extract email inline images' and 'Extract embedded files' boxes are now sub-options that can be selected independently when 'Enable file extraction' is set. When unchecked no files will be extracted from the ingested source data resulting in a 1:1 ratio of files after Streaming Discovery has completed. Perform Overlay against entire Streaming Export Series (57529) - The option 'Create Series Overlay' exists when right clicking on an Export Series in the eCapture Controller. Once selected the user is presented with a list of jobs available within the series to include in the Overlay followed by the fields and associated mapping for the end review database. The field '[bEGDOC]' is a required field within field list as it is used to associate the updated values. Overlay jobs are identified within an export series by the prefix '(Overlay)' in the job name. Windows 10 / Server 2016 OS Certification (62213) - eCapture and its associated modules (Controller, Queue Manager, Worker, and QC) can now be installed on machines using Microsoft Windows 10 / Server 2016 Operating Systems. Allow resizing of ‘Field Name’ column when selecting fields in a QC session (67559) - When modifying the Selected Fields within a QC session, the 'Field Name' column can be resized. This facilitates viewing of content in the 'Type' field to more quickly and easily distinguish System/Metadata field types.
  12. As you may have read in the 2017.4 release notes documentation, eCapture error logs have now been centralized to the following location: C:\ProgramData\IPRO Tech\logs The log4net configuration files used to enable DEBUG logging for all the various eCapture modules and services have also moved to a similar centralized location as nlog files: C:\ProgramData\IPRO Tech\configuration When working with the nlog files, this is the line you can change 'INFO' to 'DEBUG' to allow for expanded activity logging for the specified module/service: <logger name="*" minlevel="Info" writeTo="production-size-restricted" />
  13. Excellent question Vaibhav. With the industry standard for deduplication being set at the family level, our recommendation would be to include standalone documents that are found to be duplicated as attachments in separate document families. The reasoning behind this recommendation is mainly contextual. For instance let's say a responsive document was attached in an email sent from Custodian A to Custodian B. A copy of the same document is also found loose on the desktop of Custodian C. From a lawyer's prospective they may certainly have interest in knowing that other copies of this document exist amongst Custodians outside of A and B as well as why Custodian C also has a copy of this document. So if this standalone document is not included in the review, even though it is clearly a duplicate of a separate email attachment we could still run the risk of not identifying the fact that it exists elsewhere amongst your dataset and with different custodians.
  14. Excellent question Vaibhav. With the industry standard for deduplication being set at the family level, our recommendation would be to include standalone documents that are found to be duplicated as attachments in separate document families. The reasoning behind this recommendation is mainly contextual. For instance let's say a responsive document was attached in an email sent from Custodian A to Custodian B. A copy of the same document is also found loose on the desktop of Custodian C. From a lawyer's prospective they may certainly have interest in knowing that other copies of this document exist amongst Custodians outside of A and B as well as why Custodian C also has a copy of this document. So if this standalone document is not included in the review, even though it is clearly a duplicate of a separate email attachment we could still run the risk of not identifying the fact that it exists elsewhere amongst your dataset and with different custodians.
  15. Excellent question Vaibhav. With the industry standard for deduplication being set at the family level, our recommendation would be to include standalone documents that are found to be duplicated as attachments in separate document families. The reasoning behind this recommendation is mainly contextual. For instance let's say a responsive document was attached in an email sent from Custodian A to Custodian B. A copy of the same document is also found loose on the desktop of Custodian C. From a lawyer's prospective they may certainly have interest in knowing that other copies of this document exist amongst Custodians outside of A and B as well as why Custodian C also has a copy of this document. So if this standalone document is not included in the review, even though it is clearly a duplicate of a separate email attachment we could still run the risk of not identifying the fact that it exists elsewhere amongst your dataset and with different custodians.
  16. According to the developer's release notes, language ranking was first implemented in eCapture version 2015.2.
  17. According to the developer's release notes, language ranking was first implemented in eCapture version 2015.2.
  18. According to the developer's release notes, language ranking was first implemented in eCapture version 2015.2.
  19. Hi Luke, We don't have a "Top 5 SQL tips" for running eCapture/Eclipse per se, however we provide a SQL best practices document available for download on myipro.iprotech.com. This is listed under Resources > ADD Workflow > Best Practice & Implementation documents. This lists our recommendations for install, configuration, data/log file management, maintenance, backup/restore and alerts monitoring.
  20. Hi Luke, We don't have a "Top 5 SQL tips" for running eCapture/Eclipse per se, however we provide a SQL best practices document available for download on myipro.iprotech.com. This is listed under Resources > ADD Workflow > Best Practice & Implementation documents. This lists our recommendations for install, configuration, data/log file management, maintenance, backup/restore and alerts monitoring.
  21. Hi Luke, We don't have a "Top 5 SQL tips" for running eCapture/Eclipse per se, however we provide a SQL best practices document available for download on myipro.iprotech.com. This is listed under Resources > ADD Workflow > Best Practice & Implementation documents. This lists our recommendations for install, configuration, data/log file management, maintenance, backup/restore and alerts monitoring.
  22. When processing word documents with revisions/comments you may encounter the following error from the Worker: "Error occurred on processing the word document: System.Runtime.InteropServices.COMException (0x800A1018): Bad parameter" This can be resolved by updating the user name and initials to a non-blank value in your Microsoft Word installation under File > Options > General.
  23. When processing word documents with revisions/comments you may encounter the following error from the Worker: "Error occurred on processing the word document: System.Runtime.InteropServices.COMException (0x800A1018): Bad parameter" This can be resolved by updating the user name and initials to a non-blank value in your Microsoft Word installation under File > Options > General.
  24. If you need to populate ENDDOC for your documents that have images, you can identify and create an overlay file using SQL that will list the last suffixed imagekey for the documents in question. You can use this script: Select D.DocumentKey AS BEGDOC, MAX (ImageKey) AS ENDDOC from Documents D join Documentpages P on D.DocID = P.DocID group by P.DocID, D.DocumentKey ORDER BY D.DocumentKey ASC
  25. If you need to populate ENDDOC for your documents that have images, you can identify and create an overlay file using SQL that will list the last suffixed imagekey for the documents in question. You can use this script: Select D.DocumentKey AS BEGDOC, MAX (ImageKey) AS ENDDOC from Documents D join Documentpages P on D.DocID = P.DocID group by P.DocID, D.DocumentKey ORDER BY D.DocumentKey ASC
×
×
  • Create New...