We installed mercury/32 on Windows 2008 Server R2 (x64) (a domain controller), and installed the mercury32 service via instm32s.exe.
------------------------------------------------------------------------------------------------------------
Mercury/32 version: Mercury/32, v4.72, Jul 10 2009
Operating mode: Standalone
Windows version: 6.1
MERCURY.EXE directory: C:\Program Files (x86)\MERCURY
Base directory: C:\Program Files (x86)\MERCURY
New mailbox location: C:\MAIL\USERS\~N
TMP environment variable: C:\Users\ras\AppData\Local\Temp\2
TEMP environment variable: C:\Users\ras\AppData\Local\Temp\2
Licensee: {omitted for privacy}
License number: {omitted for privacy}
License level: Licensed for 1 - 15 users (currently 0 active)
------------------------------------------------------------------------------------------------------------
Before starting the service, we tested mercury/32 in foreground, testing from a Thunderbird version 2.0.0.24 (20100228) client.
Tests via POP3 incoming and SMTP sending mail were successful. mercury32 had TCP sockets listening on ports as follows:
abridged netstat -ano output:
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:70 0.0.0.0:0 LISTENING 2380
TCP 0.0.0.0:79 0.0.0.0:0 LISTENING 2380
TCP 0.0.0.0:110 0.0.0.0:0 LISTENING 2380
TCP 0.0.0.0:143 0.0.0.0:0 LISTENING 2380
TCP 0.0.0.0:2525 0.0.0.0:0 LISTENING 2380
This was as expected.
We terminated mercury/32 foreground and tested the mercury32 service, with varying degrees of failure.
We originally configured and started the service to run as Local System Account with "Allow service to interact with desktop" checked.
No GUI appeared, and (using netstat -ano) no TCP ports were listening. Naturally, our test client PC running Mozilla Thunderbird version 2.0.0.24 (20100228) got a "connection refused" when we tried to read mail via POP3.
Same result with "Allow service to interact with desktop" un-checked.
Same result using a domain account with administrative rights.
HOWEVER, using NT AUTHORITY\NetworkService a different, but still unsuccessful result. netstat -ano indicated that ports 70, 79, 110, 143, and 2525 were listening, as in the foreground case, but the Thunderbird mail client popped up "An error occurred with the POP3 mail server. Mail server {mercury server} responded:". An attempt to send mail via SMTP also failed, with the popup "An error occurred while sending mail. The mail server responded: Service not available, closing channel.. Please verify that your email address is correct in your Mail preferences and try again.".
We seemed to be getting closer, but still no cigar.
Does anybody have experience with Windows Server 2008 R2 and Mercury/32 running as a server? Any thoughts on diagnosing this further?
Rob
<p>We installed mercury/32 on Windows 2008 Server R2 (x64) (a domain controller), and installed the mercury32 service via <b>instm32s.exe</b>.</p><p>------------------------------------------------------------------------------------------------------------&nbsp;
</p><p>Mercury/32 version: Mercury/32, v4.72, Jul 10 2009
Operating mode: Standalone
Windows version: 6.1
MERCURY.EXE directory: C:\Program Files (x86)\MERCURY
Base directory: C:\Program Files (x86)\MERCURY
New mailbox location: C:\MAIL\USERS\~N
TMP environment variable: C:\Users\ras\AppData\Local\Temp\2
TEMP environment variable: C:\Users\ras\AppData\Local\Temp\2
Licensee: {omitted for privacy}
License number: {omitted for privacy}
License level: Licensed for 1 - 15 users (currently 0 active)</p><p>------------------------------------------------------------------------------------------------------------
</p><p>&nbsp;Before starting the service, we tested mercury/32 in foreground, testing from a Thunderbird version 2.0.0.24 (20100228) client.</p><p>&nbsp;Tests via POP3 incoming and SMTP sending mail were successful. mercury32 had TCP sockets listening on ports as follows:</p><p>abridged <b>netstat -ano </b>output:
</p><p>&nbsp;Proto&nbsp; Local Address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Foreign Address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; State&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PID
&nbsp; TCP&nbsp;&nbsp;&nbsp; 0.0.0.0:70&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0.0.0:0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LISTENING&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2380
&nbsp; TCP&nbsp;&nbsp;&nbsp; 0.0.0.0:79&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0.0.0:0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LISTENING&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2380
&nbsp; TCP&nbsp;&nbsp;&nbsp; 0.0.0.0:110&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0.0.0:0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LISTENING&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2380
&nbsp; TCP&nbsp;&nbsp;&nbsp; 0.0.0.0:143&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0.0.0:0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LISTENING&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2380
&nbsp; TCP&nbsp;&nbsp;&nbsp; 0.0.0.0:2525&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0.0.0:0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LISTENING&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2380
</p><p>This was as expected.
</p><p>We terminated mercury/32 foreground and tested the mercury32 service, with varying degrees of failure.
</p><p>We originally configured and started the service to run as <b>Local System Account</b> with&nbsp; "Allow service to interact with desktop" <b>checked</b>.</p><blockquote><p>No GUI appeared, and (using <b>netstat -ano</b>) no TCP ports were listening. Naturally, our test client PC running Mozilla Thunderbird version 2.0.0.24 (20100228) got a "connection refused" when we tried to read mail via POP3.</p><p>Same result with "Allow service to interact with desktop" <b>un-checked</b>.</p><p>Same result using a domain account with administrative rights.</p><p>HOWEVER, using&nbsp; <b>NT AUTHORITY\NetworkService</b> a different, but still unsuccessful result.&nbsp; <b>netstat -ano </b>indicated that ports 70, 79, 110, 143, and 2525 were listening, as in the foreground case, but the Thunderbird mail client popped up "<i>An error occurred with the POP3 mail server. Mail server {mercury server} responded:</i>".&nbsp; An attempt to send mail via SMTP also failed, with the popup "<i>An error occurred while sending mail. The mail server responded: Service not available, closing channel.. Please verify that your email address is correct in your Mail preferences and try again.</i>".</p></blockquote><p>&nbsp;We seemed to be getting closer, but still no cigar.</p><p>Does anybody have experience with Windows Server 2008 R2 and Mercury/32 running as a server?&nbsp; Any thoughts on diagnosing this further?</p><p>Rob
</p><blockquote><p>&nbsp;</p></blockquote>
