You need to upgrade the daemons as well - a lot of changes to the daemon interface occured between 4.5x and 4.6x.

Always make a backup of your system setup before doing an upgrade, so you easily can downgrade if something should arise.

This night I upgraded my Mercury MTS from 4.52 to 4.62 (all running on my freshly patched Windows Server 2003).

The upgrade process went well and no errors seemed to occur, but after the upgrade my server started to respond sluggish and when sending e-mails from different local users none of the emails seemed to go through the Mercury Server.

The SMTP server received the messages as normal, but nothing happened in the Core Process windows - and nothing was sent from the SMTP Client.

I'm also using SpamHalter, Clamwall and Greywall functionallity, but have not altered anything from the 4.52 config on these products.

Today I downgraded back to the 4.52 version and everything is working fine again.

 Any suggestions to solve this and let me upgrade to 4.62 again? [:)]

/Trygve

This upgrade is usually very easy and smooth. Assuming that the program directory hasn't been moved you only need to run the installer. (If it has been copied to a new location you need to modify paths in mercury.ini.) The only thing I can think of that could cause symptoms like you describe is if some Mercury files for some reason were locked by the system or write-protected and couldn't be updated.

Try making a separate installation of Mercury 4.62 in another location on the server and test if that works normally. If it does, I would suggest that you retry the update, making sure Mercury is closed down and no files are locked.

/Rolf