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.
Latest posts by Shishir Chandrawat (see all)
- Exchange 2010 Std: Mailbox server has reached the maximum database limit of 5 Error RcrExceedDbLimitException - December 12, 2016
- Exchange 2010: Unable to add Mailbox Database copies on DAG member servers, Error: An error occurred while processing a request on server - December 12, 2016
- Unable to Mount Microsoft Exchange DAG Database, Error: Failed to determine the mount status of the active database copy - December 12, 2016
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?
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
Thank you. It solved my problem too.
Thanks Wilson, An affirmation from the viewer’s always boost our confidence.
Thanks, also did solve my problem 🙂
Thanks for the update, it always helps us to know that our solutions helped someone. 🙂
I’ve seen the same issue with POP3 http://blog.jasonsherry.net/2014/08/19/exchange-2013-pop3-service-drops-connections-fix/
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.
Happy to know that it worked for you. Feel free to reach us for your Microsoft Server Issues and Projects.
Thank you so much, this post solved my problem! 🙂
Glad it worked for you, thanks for letting us know 🙂