English
Chinese (Simplified)
French
German
Italian
Japanese
Russian
Spanish
Vietnamese
MDaemon 25.0.2 Crashes
-
Hello.
After update MDaemon to 25.0.3 version, service crashes, we've seen no relevant entries in internal MDaemon logs, but in App evt there's that:
Faulting application name: MDAEMON.EXE, version: 25.0.3.2, time stamp: 0x685083f7
Faulting module name: MDASMgmt.dll, version: 25.0.3.1, time stamp: 0x685082b8
Exception code: 0xc0000005
Fault offset: 0x00000000000a913c
Faulting process id: 0x1c08
Faulting application start time: 0x01dc2de99a245230
Faulting application path: C:\MDaemon\APP\MDAEMON.EXE
Faulting module path: C:\MDaemon\App\MDASMgmt.dll
Report Id: 1867ad5d-d162-452f-a69c-bf21366f0c2e
Faulting package full name:
Faulting package-relative application ID:And in System evt:
The MDaemon service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
I've seen nothing in 25.5.0 RN that can make me think that version solves the issue, so, while that is solved, a downgrade has been made.
Can you help us?
-
I've wrote in subject 25.0.2, but is 25.0.3, my fault.
-
Please check the MDaemon\Dumps folder for .dmp files with a modified date around the time the crash occurred. If there are dmp files, please zip them and upload them to us https://mdaemon.sharefile.com/r-rc3922c1eed334d4dbf5e34f0bd04ccd6.
If there are no .dmp files, please upgrade to 25.0.3, install debug diag and collect dump files the next time the crash occurs using the procedures in this article, https://knowledge.mdaemon.com/how-to-collect-crash-dumps.
Once debug diag has created dump files, zip them and upload them to us using the URL above.
Once the upload is complete, please let us know the name of the file you uploaded.
-
Hello
I've put the file Dumps25.0.3.zip there.
I have to tell you, that it seems the issue is solved, it was that the MDaemon was on a virtual harware 13 (Compatible with vmWare 6.5), and updating it to v.19 (7.2 vmWare compatible) made it works.
I've updated the files, as will allow you to investigate the issue, if needed.
-
I've submitted the dump file to the development team for review. It may still be possible for the crash to occur. I'll let you know as soon as I have more information.
-
The crash occurred because ActiveSync was doing a lookup for an account that exists and it failed. The lookup was not expected to fail, so processing continued and ultimately caused a crash. We'll look into fixing it for a future version.
-
Hello.
The custom reports is happening again, and it's not reliable to stop Activesync, as there are some accounts, should they uncheck any option to avoid the process? Most of users use WorldClient, and it's so annoying to start https session so commonly.
-
Is MDaemon configured to use an ODBC backend? Are there any errors being logged in MDaemon's system log, MDaemon's Airsync Log, MDaemon's AirSync-Mgmt log, or the windows event log about issues with the database?
-
Hello.
Yes, the MDaemon user database is stored on a database, and MDaemon access with OBDC, in the link you put on a former post, I've updated the logs from a day the MDaemon had the issue, with the name System_AS.zip. They have went back to the former version, so right now, they don't have active that 25.0.2, the y can't afford have the server starting continuously, but they recover the logs file from a backup in a time where the server was suffering the issue.
In the app and sys logs, the only thing that appear is
App evt
Faulting application name: MDAEMON.EXE, version: 25.0.3.2, time stamp: 0x685083f7
Faulting module name: MDASMgmt.dll, version: 25.0.3.1, time stamp: 0x685082b8
Exception code: 0xc0000005
Fault offset: 0x00000000000a913c
Faulting process id: 0x1c08
Faulting application start time: 0x01dc2de99a245230
Faulting application path: C:\MDaemon\APP\MDAEMON.EXE
Faulting module path: C:\MDaemon\App\MDASMgmt.dll
Report Id: 1867ad5d-d162-452f-a69c-bf21366f0c2e
Faulting package full name:
Faulting package-relative application ID:and in sys evt
The MDaemon service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Thanks.
-
We believe this only affects customers using an ODBC backend. To avoid the crash you can change to using the userlist.dat file for the account database or we have an updated dll you can try. If you'd like to try the updated dll, please make sure you are running MD 25.0.3, and then make a backup of the MDaemon\app\mdasmgmt.dll and replace it with the one found here, https://mdaemon.sharefile.com/public/share/web-s7c347a5413fc42909cc336eaec02f82e.
This file has had a limited amount of testing. Please proceed with caution.
Let us know if you have any issues.
