Jump to content

Peter Randziak

ESET Moderators
  • Posts

    3,516
  • Joined

  • Last visited

  • Days Won

    207

Posts posted by Peter Randziak

  1. 17 hours ago, RClegg said:

    I think I figured it out; we are running "PROTECT", while you specified that this is for "Endpoint Security" and "Endpoint Antivirus". Is the Outlook Plugin the same for all three? What are the plans for deploying this to the PROTECT family?

    The new Outlook plugin is present in both ESET Endpoint Security i.e. EES and ESET Endpoint Antivirus i.e. EEA.

    The Endpoints 9.1 with the new Outlook plugin will be released later as standard products.

    Peter

     

  2. Hello @eclipse79,

    as the issue probably won't be easy to reproduce, I would recommend to enable the logging before the attempt for sure. So if you succeed (I hope you will 😉 ), we will have the logs for the dev team to check it.

    On 3/21/2022 at 8:15 PM, Peter Randziak said:

    if any issues will arise, we will need the user to enable diagnostic logging of this component whenever needed (see screen below), run Outlook (or other email client), wait for the issue to demonstrate, quit Outlook and disable diagnostic logging to avoid extensive log-recording for a longer time. The resulting log will be stored under C:\ProgramData\ESET\ESET Security\Diagnostics\MailPlugins.etlLogging.png

    Peter

  3. The error "RUN_LOOP_ERROR RUN_LOOP_TIMEOUT " is known and should be fixed in the 1.9 release.

     

    On 4/18/2022 at 5:39 PM, j-gray said:

    Error: License check failed.

    When it comes to this error, it should be fixed in next hot fix release. (P_EEI-11289)

    As you can see in the logs, the events are being sent successfully to EI server despite the error...

     

     

    I apologize for the apologize for the inconvenience caused by those issues.

    Peter

  4. Hello @j-gray

    when it comes co macs, as of now the licensing is not yet implemented for the EI connector, that is the reason for the "PERSEUS_UNKNOWN (5000)" log entries. It is not in v.6, but the license is required for v.7.

    The logs show, that the events are being collected, send to server and it accepts it.

     

    The error "RUN_LOOP_ERROR RUN_LOOP_TIMEOUT " is known and should be fixed in the 1.9 release.

    Peter on behalf of the local EI guru 😉 

  5. Hello @Alexander Szewczyk,

    are you able to reproduce the issue on demand i.e. does it happen after you remove them and start the Outlook again? 

    If yes, can you please:

    1. Delete the additional Junk email folders (to make the issue easier to spot)
    2. Quit Outlook
    3. Enable diagnostic logging for Email client protection as shown on the screenshot and confirm
    4. Logging.png.718f054bfc7d8829d28731069052
    5. run Outlook and wait for the issue to demonstrate
    6. quit Outlook
    7. disable diagnostic logging to avoid extensive log-recording for a longer time.
    8. The resulting log will be stored under C:\ProgramData\ESET\ESET Security\Diagnostics\MailPlugins.etl
    9. Provide me with the log generated and info from which shared mailboxes the issue occurred to check it with our dev team.

    Thank you, Peter

×
×
  • Create New...