Exchange connector Autodisover not set but SCSM try always use it

Question

Dears,

 

   when I try to set Exchange connector 4.1 in SCSM2019, with correct tenant and client, an error message appear: Exchange Connector: Unable to validate credentials, please refer to the event logs for more information (Error Type=AggregateException, Message=One or more errors occurred.) Additional Details: System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'autodiscover.domain' at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar) --- End of inner exception stack trace ---

 

I didn´t checked autodiscover option so why this issue appear? For security reasons I changed domain name so the issue is not there.

Answer 1

Hi,

It sounds like you’re encountering a common issue with the Exchange Connector in SCSM2019. The error message you’re seeing, particularly the part about the remote name not being resolved, suggests that the connector is trying to reach the autodiscover service but is unable to do so.

Here are a few steps you can take to troubleshoot and resolve this issue:

Check DNS Configuration: Ensure that the DNS settings are correctly configured and that the autodiscover service can be resolved. You can use tools like nslookup to verify this.

1. Update Exchange Web Services (EWS) URL: Make sure that the EWS URL is correctly specified. Sometimes, manually setting the EWS URL can help bypass autodiscover issues. The URL typically looks like https://outlook.office365.com/EWS/Exchange.asmx.

Firewall and Network Settings: Verify that there are no firewall rules or network settings blocking the connection to the autodiscover service or the EWS URL.

Service Account Permissions: Ensure that the service account used by the Exchange Connector has the necessary permissions to access the Exchange server.

Event Logs: Check the event logs for more detailed error messages that might give additional clues about what is going wrong.