Exchange 2013/2016 Server Component State Inactive (IMAP)

Suddenly IMAP can stop working on your server. As you look through your setup, you will find, that it’s still configured correctly, and the service is running! – So what could be wrong?

Exchange have since version 2013, used Server Component States to granular control over the state of the components that make up an Exchange Server .

When theese are not working as supposed (Read=inactive/offline!), the service that lays behind, stops working, even though you find it “Running” in Services manager.

Here we will troubleshoot the IMAP service, which has an underlaying IMAP.Proxy, so let’s head to Exchange management Shell:

Here we find, that the service is OFFLINE!
Get-HealthReport <exchange-servername>  | where { $_.state -eq “Offline”}
Let’s try to get it reactivated, with this.
Set-ServerComponentState -Identity <exchange-servername> -Component IMAPProxy -State Active -Requester HealthAPI
Let’s see if it worked? – it did!
Get-HealthReport <exchange-servername> | where { $_.HealthSet -eq “IMAP.Proxy”}
Event log shows this (You have the time of error from the “LastTransitionTime” above: 07-01-2019 02:45:20

So why this happens, can be difficult to know, as theese are ADAccess related, it could be that one or more DC’s are offline or have been rebooted, network problems or other issues. But here is how to fix it 😉

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close