Bagikan melalui

"The server address (URL) is not valid" error when you configure Microsoft Dynamics CRM for Outlook

  • Artikel

This article provides a resolution for an error that occurs when you set up Microsoft Dynamics CRM for Outlook.

Applies to:   Microsoft Dynamics CRM, Microsoft Dynamics CRM 2015, Microsoft Dynamics CRM Online
Original KB number:   3123894, 3048775

Symptoms

When you try to set up Microsoft Dynamics CRM for Outlook, you receive the following error message:

The server address (URL) is not valid.

Cause 1: The URL isn't valid or can't access Microsoft Dynamics CRM

Resolution

To verify that the URL is valid and can successfully access Microsoft Dynamics CRM, try using the same URL to access Microsoft Dynamics CRM via your web browser. If you can't access your CRM organization via your web browser, Microsoft Dynamics CRM for Outlook can't access it either. If you try to connect to a CRM Online organization, select the CRM Online option instead of typing a URL in the Microsoft Dynamics CRM for Outlook Configuration Wizard.

Tip

If you still have an issue connecting Microsoft Dynamics CRM for Outlook to your CRM Online organization, scan Outlook by using Microsoft Support and Recovery Assistant to diagnose and fix the problem.

Cause 2: Microsoft Dynamics CRM for Outlook tries to use domain credentials to connect to Microsoft Dynamics CRM

Resolution

To authenticate as a different account, you need to clear the Connect automatically with my current credentials checkbox. If the checkbox isn't visible, select the CRM Online option again from the dropdown list or type your Microsoft Dynamics CRM Online URL. You can also copy and paste the URL from your web browser.

Tip

If you still have an issue connecting Microsoft Dynamics CRM for Outlook to your CRM Online organization, scan Outlook by using Microsoft Support and Recovery Assistant to diagnose and fix the problem.

More information

If you select Details or view the log file, you see the following error:

Client configuration failed with the exception : The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Bearer authorization_uri=https://login.windows.net/common/oauth2/authorize'.
Server stack trace:
 at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory`1 factory)
 at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
 at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
 at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
 at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
 at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
 at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
 at Microsoft.Xrm.Sdk.Discovery.IDiscoveryService.Execute(DiscoveryRequest request)
 at Microsoft.Xrm.Sdk.WebServiceClient.DiscoveryWebProxyClient.<>c__DisplayClass1.<ExecuteCore>b__0()
 at Microsoft.Xrm.Sdk.WebServiceClient.WebProxyClient`1.ExecuteAction[TResult](Func`1 action)
 at Microsoft.Xrm.Sdk.WebServiceClient.DiscoveryWebProxyClient.ExecuteCore(DiscoveryRequest request)
 at Microsoft.Xrm.Sdk.WebServiceClient.DiscoveryWebProxyClient.Execute(DiscoveryRequest request)
 at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo`1.DeploymentInfo`1.RequestOrganizationDetailsFromDiscovery(IDiscoveryService proxy, EndpointAccessType endpointAccessType)
 at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo`1.DeploymentInfo`1.LoadOrganizationsInternal(AuthUIMode uiMode, Control parentWindow)
 at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo`1.DeploymentInfo`1.LoadFederatedOrganizations(AuthUIMode uiMode, Control parentWindow)
 at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo`1.LoadFederatedOrgs(DataCollection`1 orgs)
 at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo`1.LoadOrganizations(AuthUIMode uiMode, Control parentWindow)
 at Microsoft.Crm.Application.Outlook.Config.ClientConfig.AddDeployment(DeploymentsDeployment[] deployments, AuthUIMode uiMode)
 at Microsoft.Crm.Application.Outlook.Config.ClientConfig.AddDeployment_ReducedUI()
 at Microsoft.Crm.Appli