Please let us know if a daily maintenance restart does not reset that counter.

Edit:  I withdraw this clarification inquiry because a during a reread of Rolf's post it became apparent he is talking about an OS restart and not a Mercury restart.

We are running mercury 4.80 on a Windows 2012 server.  In the last few days it seems to have become impossible for users to log in to the server.  I have made no changes to their accounts or passwords.  It is possible that a batch of Updates to Windows server 2012 mayhave caused the problem.  Has anyone else noticed this.   Those users still on Pegasus are unaffected but I can no longer log in from my phone and a few users on Outlook are getting log in error messages at regular intervals.

Om my Android phone the message I am getting is authentication failed and the outlook users are getting similar prompts. 

Hi Chris,

do the Pegasus users access their mailbox via IMAP or directly via fileaccess? That may be the difference.

Checked your firewall on the server and the ports Mercury may use.

Do Outlook and android use the same ports?

Regards

   Olaf

We actually discovered a possible issue with IMAP access just 2 days ago, affecting servers that aren't restarted very often. When Windows has been running for 49.7 days the internal tick counter will be reset (due to an integer capacity limitation), which will cause MercuryI to be inaccessible for the amount of time set as timeout in MercuryI configuration (usually 30 minutes). A fix is being tested right now and will be available in the next release.

If you saw problems shortly after a Windows restart or if problems persisted longer than the timeout period it's not due to this though (in that case most likely a networking or firewall issue).