I would also recommend to update to v4.80

In past wee also experienced occasional Mercury crashes from time to time, often in connection with the establishment of SSL connection to our ISP. Sometimes once a week, sometimes only once per month or more rare. But since we have updated to v4.80 at the beginning of this year, no further crashes. We are happy.

We are running v4.72 on a virtualized Windows 2008R2 64bit server. It runs fine as a service except on rare occasions during high SMTP throughput, when it dies unexpectedly.

 The Mercury logs show no errors; neither do the Windows event logs. There is always an abandoned partial message in the SCRATCH  folder with a matching time-stamp..

This might happen once every 3-6 months. Not a huge deal but we used to run on Windows 2008 32 bit non-virtualized and it never died that I can recall over a 4 year stretch.

Has anyone else seen this? Any suggestions on how to  debug?

Thanks

Peter

No idea if this is what you are seeing, but I recall that there were some rare issues involving temporary work files that were fixed during testing of v4.80. There were other fixes as well, so upgrading is probably a good advice. Other than that it's as always best to make sure that there is no real-time antivirus program or similar running that might block access to files in any directory that Mercury is using.