our Exchange server resides in a central location, out of our control.
Hi there,
If you have ruled out local connectivity issues and this is effecting multiple users then the problem will more than likely exist on the exchange server. You won't be able to fix the issue if you cannot see or work on the exchange server.
From another source with the same issue - upon advice from MS:
- Restart the Microsoft Exchange Server Information Store service
- Run eseutil /d to perform an offline defrag of the database
- Run isinteg
Initially the restart of the Information Store service seemed to resolve the
issue immediately. The other two items were more to make sure no other issues
were going to make the problem return.