Exchange 2013: Unable to Connect to Imap services “Your Server unexpectedly terminated the connection”

by | Nov 25, 2014 | Exchange, Exchange 2013 | 11 comments

Exchange 2013: Unable to Connect to Imap services “Your Server unexpectedly terminated the connection”

We had fresh install of Exchange 2013 CU3 and found that the clients weren’t able to connect to exchange server over IMAP protocol. Telnet to the name and Ip of Exchange server on port TCP 143 (IMAP Port) was also failing.

Imap profile on outlook client was failing with following error

Log onto incoming mail server (IMAP): Your Server unexpectedly terminated the connection. Possible causes include server problems, network problems, or a long period of inactivity.

Strangely if we telnet localhost (127.0.0.1) on port TCP 143, than we do get the IMAP Banner. Though  if we telnet locally on Exchange server to FQDN or IP address of Exchange Server; the connection fails.

Checked Application logs and found the following events

Event  ID 1011:
      Log Name:      Application

Source:        MSExchangeIMAP4
 Event ID:      1011

Level:         Information
User:          N/A

Computer:      SERVERNAME

Description:
The IMAP4 server’s Online status has changed to False

Checked the servercomponenthealthstatus and found it was offline:
RunspaceId                 : 
PSShowComputerName         : False
SerializationData          : }
ServerFqdn                 : SERVERNAME
Component                  : ImapProxy
State                      : Inactive
ServerWideOfflineIsOffline : False
RemoteStates               : {}
LocalStates                : {Microsoft.Exchange.Data.Directory.Management.ServerComponentStatePresentationObject+RequesterDetails}
Identity                   : SERVERNAME
IsValid                    : True
ObjectState                : New

Solution

Further investigation revealed Server Component “IMAPProxy” was in Inactive state.

Executed the following command to fix the issue

Set-ServerComponentState -Identity SERVERNAME -State Active -Requester HealthAPI -Component ImapProxy

Restarted the IMAP services

This resolved the issue for us and hopefully for you too.  Feel free to start a new thread in our forum if you need further assistance.

The following two tabs change content below.
My Google+ profileMy LinkedIn profile

Shishir Chandrawat

An automobile enthusiast at heart and computer geek by profession, started my Career with MS in 2005.Left Jobs and started Pledge Technologies (the parent company to Grishbi) back in 2009.We have been providing IT consulting to various Small and Medium businesses across US and UK since then.Our company specialises in Microsoft Server technologies like AD, Exchange, the rest and with numerous Office 365 migrations under our belt, we quite an expert with that too. Whatever we learn in our day to day life, we share it back on Grishbi as a Thank for all the love and support our customers have given us.
468

11 Comments

  1. Lucas
    Lucas on December 14, 2015 at 11:16 am

    Shishir,

    The imapProxy component is getting inactive every 2/3 days. No log at evenviewer can help, the register is:

    Process MSExchangeHMWorker.exe (ExHMWorker). ServerComponentState for Component ‘ImapProxy’ set by Requester ‘HealthApi’ to ‘Inactive’.

    Can you help me?

    Reply
    • Shishir Chandrawat
      Shishir Chandrawat on December 16, 2015 at 8:29 am

      HI Lucas

      Sorry for delayed response, All information we provide on the site is our experiences and we are very happy if it helps any one. But if that doesnt resolve the issue, We can definitely provide you personal paid support, Please drop us an email at support@pledgetechnologies.com with issue details and contact details.

      thanks
      shishir

      Reply
  2. Wilson
    Wilson on November 11, 2015 at 9:16 am

    Thank you. It solved my problem too.

    Reply
    • Rishi Chaudhary
      Rishi Chaudhary on November 13, 2015 at 6:09 am

      Thanks Wilson, An affirmation from the viewer’s always boost our confidence.

      Reply
  3. HUBH
    HUBH on September 22, 2015 at 1:13 am

    Thanks, also did solve my problem 🙂

    Reply
    • Shishir Chandrawat
      Shishir Chandrawat on September 22, 2015 at 6:21 am

      Thanks for the update, it always helps us to know that our solutions helped someone. 🙂

      Reply
  5. nnatic
    nnatic on March 27, 2015 at 11:10 am

    Man, I have been trying to find out what is wrong with one of my server’s IMAP connection for two days. I FINALLY stumbled upon this post. Thank you so much for this. I never would have figured this out.

    Reply
    • Shishir Chandrawat
      Shishir Chandrawat on March 27, 2015 at 11:17 am

      Happy to know that it worked for you. Feel free to reach us for your Microsoft Server Issues and Projects.

      Reply
  6. rsantus0
    rsantus0 on February 26, 2015 at 10:29 am

    Thank you so much, this post solved my problem! 🙂

    Reply

Leave a Reply

%d bloggers like this: