Once again the online community came through.  Thank you for all your help. I found that the INI file was indeed considerably smaller than the bak & bk2 files. Copied over the backup file and all is back working as normal.

Thanks again

Hi

We have a Mercury for Windows V4 Mail Server running at the school for teacher mail. It had been working fine up until 24 hrs ago. I noticed that it stopped downloading the outside mail. Checking with our service provider it all seemed right their end. 

I then noticed that the drive that mercury and all the files where on had only a couple of K left. So I shutdown the mercury server and deleted a series of old log files and deleted a heap of TCP?????.md files located in the c:\log directory. 

I then went to start the Mercury mail server but it does not load. I noticed that when I clicked on the Mercury Loader it tries to load displaying the image on the screen to say it is loading but never actually loads. It acually flashes the loading Mercury graphic on the screen 7 times over 30 second time period and then stops but never actually loads.

 I am bit of a newbee with mercury and I would really appreciate some help as it controls all the mail for the school.

Thanks a million

Michael

Try to narrow it down, by editing Mercury.ini and therein adding a # in front of the loaded modules - so that you get the core up - ie loading the Mercury core with alias and users. If this fails, then you should check that the path-settings within Mercury are valid.

When Mercury core loads ok, you can re-enable module by module in mercury.ini until you find the one that's preventing Mercury from starting.

The loader.log file in the mercury folder may give some clues as to why it fails to load properly.

Also, mercury will shut down immediately after starting if the mercury.ini is corrupt, maybe because of a failed write due to no disk space.

There will be a backup, mercury.bak & mercury.bk2, that you can use to rebuild it if that is the case.

You should uncheck the box for 'session logging' in the MercD module and any others that have it checked.

It is there for debugging problems, and as you have seen, eats disk space rapidly