I've just installed Mercury v4.72, and when it is running, it runs great. (I'll explain that caveaut below.) My real question however is about the "QUEUE" directory. I understand this is where messages go to be processed by the "core" server. I am running a pretty busy mail server, and this directory is slowly filling up with .QIF, .QCF, .QDF files. Often they are of a few hours, or even days old, and about a third of them of are 0 bytes in size.
This is running on a Windows Server 2003 box. I've dskchk'ed it, it has plenty of RAM and free hard drive space, and is effectively not running much of anything else other than this Merucry server.
Is this normal? Should this directory really be filling up without bound? Is this a problem of things not being able to keep up?
Any information would be greatly appreciated.
Thanks,
C.J.
P.S. - What I alluded to in my first sentence is that I've attempted a few times to run this on a Windows Server 2008, 64-bit, box that I have, and that has failed misserably. No matter what I do, including a clean, fresh installation of everything from the OS on up, Mercury runs for a few minutes and then crashes pretty badly. Sometimes with a message that says, "Semaphore error creating handle lock", but most of the time just crashing with the generic Windows message, "Mercury/32 Core Processing Module v4.72 has stopped working". I'm hoping this has to do with trying to run this on a 64-bit version of Windows 2008 (which I know really shouldn't be an issue), thus my attempt on a totally different machine running a native 32-bit Windows operating system. We'll see! But as you can see from above, I think even this install has issues. Argh! I'm really trying to get this to work. Thanks again.
<P>I've just installed Mercury v4.72, and when it is running, it runs great.&nbsp; (I'll explain that caveaut below.)&nbsp; My real question however is about the "QUEUE" directory.&nbsp; I understand this is where messages go to be processed by the "core" server.&nbsp; I am running a pretty busy mail server, and this directory is slowly filling up with .QIF, .QCF, .QDF files.&nbsp; Often they are of a few hours, or even days old, and about a third&nbsp;of them of are 0 bytes in size.</P>
<P>This is running on a Windows Server 2003 box.&nbsp; I've dskchk'ed it, it has plenty of RAM and free hard drive space, and is effectively not running much of anything else other than this Merucry server.</P>
<P>Is this normal?&nbsp; Should this directory really be filling up without bound?&nbsp; Is this a problem of things not being able to keep up?</P>
<P>Any information would be greatly appreciated.</P>
<P>Thanks,</P>
<P>C.J.</P>
<P>P.S. - What I alluded to in my first sentence is that I've attempted a few times to run this on a Windows Server 2008, 64-bit, box that I have, and that has failed misserably.&nbsp; No matter what I do, including a clean, fresh installation of everything from the OS on up, Mercury runs for a few minutes and then crashes pretty badly.&nbsp; Sometimes with a message that says, "Semaphore error creating handle lock", but most of the time just crashing with the generic Windows message, "Mercury/32 Core Processing Module v4.72 has stopped working".&nbsp; I'm hoping this has to do with trying to run this on a 64-bit version of Windows 2008 (which I know really shouldn't be an issue), thus my attempt on a totally different machine running a native 32-bit Windows operating system.&nbsp; We'll see!&nbsp; But as you can see from above, I think even this install has issues.&nbsp; Argh!&nbsp; I'm really trying to get this to work.&nbsp; Thanks again.</P>
