Jump to content

Michael Avakian

S.W.A.T. Engineer
  • Posts

    119
  • Joined

  • Days Won

    2

Michael Avakian last won the day on February 13 2017

Michael Avakian had the most liked content!

About Michael Avakian

Recent Profile Visitors

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

Michael Avakian's Achievements

Enthusiast

Enthusiast (6/14)

20

Reputation

  1. Steve, There is an updated version that includes information about adding permissions. Below is a link to the updated version 2018.5.1. It is also available with the ADD Web documentation that comes with the ADD installation files. Ipro ADD 2018.5.1 Custom Report Creation.pdf
  2. When launching the eCapture controller today I was faced with a dialog that was requesting my eCapture environment name, integration directory, and my ADD url. When I clicked save I was faced with a new error in the controller log: No MediaTypeFormatter is available to read an object of type 'ErrorInfo' from content with media type 'text/html'. ---> System.Net.Http.UnsupportedMediaTypeException: No MediaTypeFormatter is available to read an object of type 'ErrorInfo' from content with media type 'text/html'. I will paste the full stack trace below. The error was caused by the IP address of my authorization service machine changing. ADD Service was unable to connect to the authorization service and thus the error was thrown when I tried to launch the controller. The Resolution: In my environment, the solution was to update the IP address of the authorization service in the ADD database. Enterprise.ConfigurationSetting table. For other environments it may be as simple as making sure the authorization service is running and is hosting a valid authorization. Full error stack trace: 2017-09-18 10:25:18,737 [1] WARN Ipro.eCapture.Api.Configuration - In VerifyNucleusConnectivity. Exception Detail: Nucleus.Domain.ErrorHandling.NucleusException: No MediaTypeFormatter is available to read an object of type 'ErrorInfo' from content with media type 'text/html'. ---> System.Net.Http.UnsupportedMediaTypeException: No MediaTypeFormatter is available to read an object of type 'ErrorInfo' from content with media type 'text/html'. at System.Net.Http.HttpContentExtensions.ReadAsAsync[T](HttpContent content, Type type, IEnumerable`1 formatters, IFormatterLogger formatterLogger, CancellationToken cancellationToken) at Nucleus.Gateway.Infrastructure.ErrorHandling.HttpMessageErrorHandler.<ThrowFailureException>d__a.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Nucleus.Gateway.Infrastructure.ErrorHandling.HttpMessageErrorHandler.<SendAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Nucleus.Gateway.ApplicationEnvironmentGateway.<GetApplicationEnvironmentById>d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Ipro.eCapture.Gateways.Gateways.ApplicationEnvironmentGateway.<GetNucleusApplicationEnvironmentById>d__9.MoveNext()
  3. When launching the eCapture controller today I was faced with a dialog that was requesting my eCapture environment name, integration directory, and my ADD url. When I clicked save I was faced with a new error in the controller log: No MediaTypeFormatter is available to read an object of type 'ErrorInfo' from content with media type 'text/html'. ---> System.Net.Http.UnsupportedMediaTypeException: No MediaTypeFormatter is available to read an object of type 'ErrorInfo' from content with media type 'text/html'. I will paste the full stack trace below. The error was caused by the IP address of my authorization service machine changing. ADD Service was unable to connect to the authorization service and thus the error was thrown when I tried to launch the controller. The Resolution: In my environment, the solution was to update the IP address of the authorization service in the ADD database. Enterprise.ConfigurationSetting table. For other environments it may be as simple as making sure the authorization service is running and is hosting a valid authorization. Full error stack trace: 2017-09-18 10:25:18,737 [1] WARN Ipro.eCapture.Api.Configuration - In VerifyNucleusConnectivity. Exception Detail: Nucleus.Domain.ErrorHandling.NucleusException: No MediaTypeFormatter is available to read an object of type 'ErrorInfo' from content with media type 'text/html'. ---> System.Net.Http.UnsupportedMediaTypeException: No MediaTypeFormatter is available to read an object of type 'ErrorInfo' from content with media type 'text/html'. at System.Net.Http.HttpContentExtensions.ReadAsAsync[T](HttpContent content, Type type, IEnumerable`1 formatters, IFormatterLogger formatterLogger, CancellationToken cancellationToken) at Nucleus.Gateway.Infrastructure.ErrorHandling.HttpMessageErrorHandler.<ThrowFailureException>d__a.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Nucleus.Gateway.Infrastructure.ErrorHandling.HttpMessageErrorHandler.<SendAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Nucleus.Gateway.ApplicationEnvironmentGateway.<GetApplicationEnvironmentById>d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Ipro.eCapture.Gateways.Gateways.ApplicationEnvironmentGateway.<GetNucleusApplicationEnvironmentById>d__9.MoveNext()
  4. Avi, Thank you for the details. The values available to calculate the hash are the same between the two job types for emails, however, the algorithm used between the two is slightly different due to a technology difference. For emails, you can see the fields used in the discovery options. For loose files or non email type files, the entire file is hashed. Because of this difference, streaming jobs and standard jobs cannot deduplicate against each other.
  5. Avi, Thank you for the details. The values available to calculate the hash are the same between the two job types for emails, however, the algorithm used between the two is slightly different due to a technology difference. For emails, you can see the fields used in the discovery options. For loose files or non email type files, the entire file is hashed. Because of this difference, streaming jobs and standard jobs cannot deduplicate against each other.
  6. mewing, Does the issue sound similar to the issue at the end of this other community post? https://community.iprotech.com/forum/eclipse-se/eclipse-se-aa/1834-ingested-documents-don-t-stay-in-produced-order The documents may need to be zero padded to sort properly or a sort field added for sorting purposes.
  7. mewing, Does the issue sound similar to the issue at the end of this other community post? https://community.iprotech.com/forum/eclipse-se/eclipse-se-aa/1834-ingested-documents-don-t-stay-in-produced-order The documents may need to be zero padded to sort properly or a sort field added for sorting purposes.
  8. When installing the IPRO File Mounting Service Host, a Mount Image PRO license key is needed to activate the product. eCapture ships with both OSF mount and Mount Image Pro for forensic file mounting. A mount image pro license key can be provided by IPRO sales team at a nominal charge. During the installation of eCapture, if the machine is not internet enabled, MIP will not be able to activate itself and will cause the file mount service to not start. Internet access will be required in order to activate mount image pro. Once MIP is activated using the instructions in the eCapture installation guide, the file mount service will start.
  9. When installing the IPRO File Mounting Service Host, a Mount Image PRO license key is needed to activate the product. eCapture ships with both OSF mount and Mount Image Pro for forensic file mounting. A mount image pro license key can be provided by IPRO sales team at a nominal charge. During the installation of eCapture, if the machine is not internet enabled, MIP will not be able to activate itself and will cause the file mount service to not start. Internet access will be required in order to activate mount image pro. Once MIP is activated using the instructions in the eCapture installation guide, the file mount service will start.
  10. If the Begdoc value is structured to display a letter as the last digit, the gap report is unable to determine if a gap exists between the letters and numbers and returns an error. A feature request has been submitted to account for alphanumeric suffixes that may exist in some data sets. The current work around is to eliminate the letters at the end of the Begdoc by deleting the records and re-importing them without the letters at the end of the Begdoc value. The error displayed is: Encountered error creating Gap Report from selected fields. Version: Eclipse 2017.3.3
  11. If the Begdoc value is structured to display a letter as the last digit, the gap report is unable to determine if a gap exists between the letters and numbers and returns an error. A feature request has been submitted to account for alphanumeric suffixes that may exist in some data sets. The current work around is to eliminate the letters at the end of the Begdoc by deleting the records and re-importing them without the letters at the end of the Begdoc value. The error displayed is: Encountered error creating Gap Report from selected fields. Version: Eclipse 2017.3.3
  12. While submitting this defect for Eclpise SE version 2017.3.4, I did find another reported issue in Eclipse 2015.1.1 where using sticky rotate would rotate all documents in the case. If this is the behavior you are experiencing, then upgrading may help resolve this behavior. The defect I have submitted for version 2017.3.4 can be tracked using ticket number 65868. Please feel free to contact us if you have any questions or comments.
  13. While submitting this defect for Eclpise SE version 2017.3.4, I did find another reported issue in Eclipse 2015.1.1 where using sticky rotate would rotate all documents in the case. If this is the behavior you are experiencing, then upgrading may help resolve this behavior. The defect I have submitted for version 2017.3.4 can be tracked using ticket number 65868. Please feel free to contact us if you have any questions or comments.
×
×
  • Create New...