Jump to content

ESET Mail Security 6.5.10059.1, W2008 R2 SP1 64bit, Exchange 2010, Undocumented Serious Error 0x1106


Recommended Posts

Posted

Hello,

since last week, we cant update our Mail Security anymore. It always show the error: "Undocumented Serious Error 0x1106".
When we enable the diagnostic log, then there are enrties about compile errors during the update.

W2008 R2 SP1 64bit
Exchange 2010
ESET Mail Security 6.5.10059.1

We tried these steps here:
https://support.eset.com/en/undocumented-serious-error-in-eset-windows-home-products

But it doesn't help.

Maybe someone have an idea or similar issues in the past with a soluton for us?

Thank you.

 

  • Administrators
Posted

Are you getting the error when attempting to update? Do you update directly from ESET's servers, via an http proxy or from a mirror? Please upgrade to the latest version of ESET Mail Security for MS Exchange v7.1 and see if the issue persists.

Posted

As far as i can see, 6.5 have still Limited Support, right? So update packages from your servers should be compatible?
https://support.eset.com/en/is-my-eset-product-supported-eset-end-of-life-policy-business-products#emsx

We dont use a HTTP-Proxy and the Update Server is set to automatic. I'll try to reboot the server today, hope this helps.

  • Administrators
Posted

I'd recommend upgrading to EMSX v7.1 since it would:
- add an option to capture network communication during update
- add Ransomware Shield (improves protection)
- add support for Deep Behavioral Inspection (improves protection)
- add support for streamed updates (improves protection and detection of malware in scanned mails)
- add support for Advanced Machine Learning (improves protection and detection of malware in scanned mails)
- add support for ESET Dynamic Threat Defense which you might want to use in the future to analyze email attachments in ESET's cloud on the fly
- add new options related to mail scanning, fix issues present in EMSX v6.

For now enable advanced engine update in the advanced setup -> tools -> diagnostics and run update. Next disable advanced logging and collect logs with ESET Log Collector. When done, upload the generated archive here. It would be also useful if you could provide a Wireshark pcap log with the network communication generated during the update.

Posted

@Marcos Server restart fixed this issue. Pretty strange. Maybe this can be added to the KB537. Anyway, thank you :)

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...