I would clear the queue and scratch directories and upgrade to the current release of Mercury/32. It might be a good idea to run Chkdsk on the disk in question and restart Windows as well.
/Rolf
Mercury claims to be running but after Server 2003 update on Friday 26th Feb no emails are being delivered by Pegasus and Mercury reports Error - user not known for all emails sent to addresses on school networl. We are using version 4 mercury (Not 4.72 but I do not know exactly which one!) It would seem that Mercury cannot see the users in the PMAIL folder - permissions/security issue???
Make sure that the mercury.ini file isn't damaged somehow, and then verify that the user running Mercury.exe has full access to all Mercury directories.
/Rolf
I don't know about Server 2003 but in XP you can see the version of Mercury by right click on mercury.exe and view Properties.
Similarly you can see which account Mercury is running under using Task Manager, and you can see the permissions on a folder using right click, Properties > Security tab.
I have a similar issue.
Win 2003 Sever, Mercury won't start !! It try's and then shut's down straight away :(
Help.. any ideas ??
I have a similar issue.
Win 2003 Sever, Mercury won't start !! It try's and then shut's down straight away :(
Help.. any ideas ??
Nothing but the common one of using one of the backup mercury.ini files and try again.
Hmm. not sure what is going on.
Rebooted the server, tried again, start / stop, start / stop.
Then start and OK !! Just got this from the server:
The Mercury/32 Loader Subsystem has attempted to recover from a sequence of
abnormal program terminations by quarantining the contents of the Mercury
mail processing queue.
2 queue-related files have been moved to the following directory:
C:\MERCURY\QUEUE\BAD-10-03-07.1532
Note that some or all of these queue files may be valid and unrelated to
the problem causing the abnormal terminations. You should consider moving
each queue file pair (two files with the same name, one with the extension
'.QCF', the other with the extension '.QDF') back into the queue one pair
at a time, restarting Mercury after each pair has been copied.
I'll see how it goes on !
Thanks for the advice :)
If you have a drive mapped for Mercury to use is it still mapped on your server 2003 system? Failing to remake your mail share and map will cause exactly the symptoms you describe but of course the drive and data are all still there just not aliased to where Mercury expects them to be.
This morning i experienced the same issue: a total of 3575 msg to admin like this:
"The Mercury/32 Loader Subsystem has attempted to recover from a sequence of
abnormal program terminations by quarantining the contents of the Mercury
mail processing queue.
57 queue-related files have been moved to the following directory:
C:\MERCURY\QUEUE\BAD-10-03-31.1302
Note that some or all of these queue files may be valid and unrelated to
the problem causing the abnormal terminations. You should consider moving
each queue file pair (two files with the same name, one with the extension
'.QCF', the other with the extension '.QDF') back into the queue one pair
at a time, restarting Mercury after each pair has been copied."
Mercury/32 V.4.5 & Popfile on XP SP3 [:(]
Alex_
