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:
Get-HealthReport <exchange-servername> | where { $_.state -eq “Offline”}
Set-ServerComponentState -Identity <exchange-servername> -Component IMAPProxy -State Active -Requester HealthAPI
Get-HealthReport <exchange-servername> | where { $_.HealthSet -eq “IMAP.Proxy”}
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 😉
Related Posts
Reported Zero-day Vulnerabilities in Microsoft Exchange Server 2013, 2016, and 2019
How to hide all users in a particular OU in the Global Address List- Exchange: An error occurred while using SSL configuration for endpoint 0.0.0.0:444
- Exchange: Replacing certificate for Microsoft 365 hybrid connector’s
- PATCH NOW: April 2021 Exchange Server Security Updates
- Exchange Online: Native external sender callouts on email in Outlook
Champion, I don’t do enough Exchange to know these commands out of my head, easy fix – exactly what I needed. I think DCs were been rebooted, so you hit the nail on the head there.
Glad to hear! – thanks for your comment, appreciate it 🙂
best regards
Martin