linus-it 0 Posted June 22, 2023 Share Posted June 22, 2023 Hello, I am facing an annoying problem with ESET Mail Security for Exchange Server. Due to several reasons I've setup my whole Exchange Server from scratch. Everything is working just fine except the integration of ESMX, which I've now reinstalled several times but which didn't fix my (new) problem. My Exchange Server is standalone and hosting the Mailbox Role. Servers involved: Windows Server 2019 (Domain Controller), Windows 2022 (Exchange Server 2019 CU13 SU1 + ESET ESMX). All servers are patched with latest available updates. My problem: ESET TransportAgents (normally two) are missing and not installed ESET Event Logs tells me every 30 minutes that "An error has occurred while updating transport agent status 3221226505" ESET Shell Status tells me everything is Enabled and fine. This is a big lie. Well... I was able to manually install ONE of the ESET Transport Agents (described in another thread somewhere here in the forum). This makes the filtering of Spam and Virus Mails work again but it doesn't make the Event Log Errors go away neither does it fix other issues like ESET Advanced Setup not Showing my Transport Agents (Agent Priority Setup). I saw an entry inside the Event Log just after installing ESMX but it's (weird enough) now gone. It was like "Faile to load server module" which would indicate that ESMX has problems using the powershell snapin for Exchange. The Exchange Powershell Module is definitely present and can be used! emsx_logs.zip Link to comment Share on other sites More sharing options...
Administrators Marcos 5,406 Posted June 22, 2023 Administrators Share Posted June 22, 2023 Ex64.exe is crashing. Please create a dump by running the following command (procdump must be downloaded and saved to the disk first) and supply the generated dump: procdump -ma -w -e ex64.exe Link to comment Share on other sites More sharing options...
linus-it 0 Posted June 22, 2023 Author Share Posted June 22, 2023 (edited) Glad you've found something. I am not able to create a dump... Image with output is attached. The process has state 'Suspended'. Details from PS Cmtlet Get-Process is attached as txt. Edit: I've found that somit device drivers are not yet installed - my bad. Will retry when all devices got correct drivers installed. ex64.exe.txt Edited June 22, 2023 by linus-it Link to comment Share on other sites More sharing options...
linus-it 0 Posted June 22, 2023 Author Share Posted June 22, 2023 So... What I did now: Install remaining device drivers Uninstall ESMX 10 Reboot OS Install ESMX 10 Try to perform ProcDump for ex64.exe ex64.exe process is now gone, not present anymore. Problem is still there. New esmx zip attached. emsx_logs.zip Link to comment Share on other sites More sharing options...
Administrators Marcos 5,406 Posted June 22, 2023 Administrators Share Posted June 22, 2023 Please rename ex64.exe back, renaming it might make the situation ever worse. Did it start you upgraded Exchange when the issue started? The first record of the crash is from 2023-06-20T12:41:49. Do you use a non-standard path to the Exchange db? Please raise a support ticket with ESET DE so that the issue is properly tracked. Link to comment Share on other sites More sharing options...
linus-it 0 Posted June 22, 2023 Author Share Posted June 22, 2023 (edited) Ticket is already opened, ticket id: #00548711 I didn't rename the ex64.exe - nothing changed on that. Exchange Server and Database Paths are default: C:\Program Files\Microsoft\Exchange Server\V15 C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 0564416363\Mailbox Database 0564416363.edb I did a complete fresh reinstallation of the Exchange Server (from scratch, which includes removing everything exchange related from Active Directory with ADSIedit before I started. I even removed the Exchange Server Computer Object from AD as well as DNS entries). The only remaining from the original installation are recovered mailboxes. The reason why I did a new installation was that I had real big issues on the Exchange side after performing an Exchange Recovery Installation on new Hardware. Exchange is now running like charm again. The issue must lie somewhere inside ESMX. I disabled IPv6 to see if that changes something. Things then become really strange: Multiple Errors in ESMX Event Log about Active Directory not being reached. Turing IPv6 back on and these Error are gone. Edited June 22, 2023 by linus-it Link to comment Share on other sites More sharing options...
linus-it 0 Posted June 22, 2023 Author Share Posted June 22, 2023 (edited) Update: ex64.exe is back in the Task Manager Process List. I am still not able to generate a dump with procmon64 because the process still remains in state "suspended". Edited June 22, 2023 by linus-it Link to comment Share on other sites More sharing options...
Administrators Marcos 5,406 Posted June 23, 2023 Administrators Share Posted June 23, 2023 ESET DE will follow up based on the current development of investigation. Currently we probably won't need any further dumps since we have already got some and those are being looked into. Link to comment Share on other sites More sharing options...
PBA72 0 Posted July 17, 2023 Share Posted July 17, 2023 Hi it seems that CU13 is not supported yet System requirements | ESET Mail Security | ESET Online Help i have the same trouble, after install ESET mail security product the transport agents from ESET are not installed. Pavel Link to comment Share on other sites More sharing options...
PBA72 0 Posted July 17, 2023 Share Posted July 17, 2023 and to support when will be the CU13 supported ? Pavel Link to comment Share on other sites More sharing options...
linus-it 0 Posted July 17, 2023 Author Share Posted July 17, 2023 (edited) Glad to hear that I am not the only one here. Already doubt CU13 and therefore installed CU13-SU1 (Download Security Update For Exchange Server 2019 CU13 SU1 (KB5026261) from Official Microsoft Download Center) Nothing changed. Agents still missing. I am already thining about to pro-actively warn my employer (BWI GmbH) - which switched to ESMX for new Anti Virus Mail Gateway Solution about a year ago - not to install CU13. Edited July 17, 2023 by linus-it Link to comment Share on other sites More sharing options...
linus-it 0 Posted July 17, 2023 Author Share Posted July 17, 2023 (edited) ESET - this is really NOT cool! CU13 was released in May 2023 ! Edited July 17, 2023 by linus-it Link to comment Share on other sites More sharing options...
PBA72 0 Posted July 31, 2023 Share Posted July 31, 2023 Hi everyone CU13 supported 🙂 System requirements | ESET Mail Security | ESET Online Help Link to comment Share on other sites More sharing options...
Recommended Posts