You might encounter the following errors while connecting to the Exchange portal:
The driver shuts down with the following error message.
There was no endpoint listening that could accept the message.
This issue is observed when the Exchange portal is down.
Workaround: Start the driver when the Exchange portal is functional.
In iManager, when you modify any driver parameter and try to restart the driver, the driver shuts down with the following error message:
IOException: graph.windows.net: Name or service not known
Workaround: Start the driver when the Exchange portal is functional.
This issue is randomly observed.
If you restart the driver, the driver displays the following error, when the Office 365 Exchange Online parameter is set to No and Publisher channel is disabled.
java.net.UnknownHostException: login.windows.net
This error is reported from Azure AD. As there is no functionality loss, start the driver after few minutes.
When you run the driver with Exchange Online enabled, error messages are reported in the Exchange trace. For example:
publish: Operation Failed: Starting a command on the remote server failed with the following error message. The I/O operation has been aborted because of either a thread exit or an application request
Ignore the error message as it does not cause any functionality loss.