Exchange 2013 Outlook Client connectivity

I'm migrating from Exchange 2010 to Exchange 2013 and on the final stages. I pointed the external and internal DNS records to Exchange 2013. I moved one mailbox to Exchange 2013 and then tried to create a new Outlook client profile and bring the mailbox
up however the client would not connect. It stated trying to connect encrypted and unencrypted. It did not work. I checked nslookup and the IPs are all set pointing to Exchange 2013. I then checked my certificates. I have a certificate that is a wild card.
When I checked assigned services on my wild card it had IIS and SMTP assigned. Also in IIS on the default site bindings what should you use as a certificate on the two https settings? Originally they were the local generated certificate. I changed them to
the wild card no luck. Please assist.

Try running through this and see if it gives you some ideas on what is wrong:
https://testconnectivity.microsoft.com/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Similar Messages

Exchange 2013 NLB Client Connections

Hi everyone, I'm
setting up an Exchange 2013 system,
the infrastructure that will be mounted
as follows:
-> 2 Domain Controllers
-> 2 Exchange 2013 backend servers
for DAG mailbox
-> 2 Servers frontend for
client connections on Microsoft NLB.
My question is regarding the Fronted
Microsoft NLB servers, I understand that
you have to redirect all SMTP and
IMAP traffic, POP, HTTPS, AS
... to distribute all Fronted
connections to servers (NLB shared
IP to the cluster).
This is correct?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi everyone, I'm
setting up an Exchange 2013 system,
the infrastructure that will be mounted
as follows:
-> 2 Domain Controllers
-> 2 Exchange 2013 backend servers
for DAG mailbox
-> 2 Servers frontend for
client connections on Microsoft NLB.
My question is regarding the Fronted
Microsoft NLB servers, I understand that
you have to redirect all SMTP and
IMAP traffic, POP, HTTPS, AS
... to distribute all Fronted
connections to servers (NLB shared
IP to the cluster).
This is correct?
thank you very much
Microsoft Certified IT Professional Server Administrator
If you want to "Load balance" them, yes. Note that WNLB doesn't do such a great job at this and is typically not recommended as its not application aware.
Not sure what you mean by "NLB shared
IP to the cluster)" The client connections go to the CAS roles, not the DAG cluster IP
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 - outlook cannot connect server

Hi,
I have installed exchange server 2013 to testing it in my home lab. DC - domain.local and exchange - sub.domain.com. Internet connection is with dynamic IP from ISP - router (PPPoE). My ISP provide DDNS and I got sub.domain.com for dynamic
IP. Also ISP is blocking port 25. I've asked ISP to unblock port 25 and i don't know if they unblock it. For exchange server i use smart host for relay.
Problem: If i use port forwarding (25) mail flow is normal intern - extern. This was tested with OWA, but outlook cannot connect to exchange server: logging on mail server failed.
If i don't use port forwarding (25) outlook connect to exchange server, but i cannot receive email from external.
Please give me a hand on this.
Thank you.

Hi Radu,
how do you connect Outlook with Exchange? Usually you're using MAPI/RPC/HTTPS so there is no dependency with SMTP. How did you configure your Outlook? How did you configure your CAS Settings?
Please verify your CAS is configured correctly and you are using Outlook AnyWhere, see
http://technet.microsoft.com/en-us/library/hh529912(v=exchg.150).aspx
Regards,
Martin

Exchange 2013 Outlook Anywhere connection issues when using F5 VIP

Hello,
We are in the process of deploying Exchange 2013 into our Exchange 2010 Org. We are using an F5 to load balance all services. We are doing some initial testing and have not cut over autodiscover or other URLs yet to 2013. We are using host files
on the local testing machines to point the URLs to 2013. OWA, Activesync, ecp work with no issue through the F5 VIP. However, we are having issues with Outlook. If our host file entries point to a single server, Outlook functions
normally. If the host file entries point to the F5 VIP, it keeps prompting for creds and will never connect.
Just wondering if anybody has run into this or has any guidance as far as OA and F5 deployment.
Thanks

Hi,
Please check your Load Balance configuration and make sure the namespace used for Load Balance has been included in the Exchange certificate. For example: mail.domain.com and autodiscover.domain.com.
If possible, please share your load balance configuration with us for further analysis. Here are some references about the Load Balance Scenario:
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx
Regards,
Winnie Liang
TechNet Community Support

App-V CRM 2013 Outlook Client and Office 2013 Click to Run

Hi,
I'm trying to get going with enbing the CRM 2013 for Outlook client with the VL version of Office Pro Plus 2013. I have successfully published and use Office App-V package in a test environment. App-V version 5.0 SP2 is installed on the client
PC (Windows 7 64bit). SCCM 2012 R2 is used to publish APP-V applications to user groups.
I have sequenced the CRM 2013 Outlook client (offline mode disabled) with UR2 and published it using SCCM as a "Add-on or Plug-in. I've also created a connection group so that the App-V version of Office 2013 is able to connect to the sequenced
CRM client. The client installs successfully, but the CRM tab doesn't appear in the Outlook Ribbon, and the Configuration Wizard crashes each time it is launched. The App-V event log is blank (which I'm taking to be a good sign). All CRM
client prerequisites have been preinstalled on the target PC.
I'm thinking that the CRM client can't see the Outlook application and therefore crashes and doesn't integrate with the Outlook application. Problem Signature 09 (from the crash explanation) states "System.NullReference Exception".
I can't seem to find much out there for sequencing the 2013 version of the client. Has any else managed this yet or have any ideas where I'm going wrong?
Thanks,
Tim

Hello,
I would use Process Monitor to understand what happens and to see why Outlook isn't seeing the plugin, and why the wizard is crashing
Nicke Källén | The Knack| Twitter:
@Znackattack

Exchange 2013 CAS server connection to Exchange 2010 Mailbox server

Hi Guys,
I have a quick question i am planning to upgrade my infra from Exchange 2010 to Exchange 2013 and i have come across a small question, my infra looks likes below
3 Exchange server (CAS+ HT + MBX roles) Exchange 2010
1 Exchange server MBX role For journlaing Exchange 2010
1 CAS for internet owa access Exchange 2010
Now i will be installing exchange 2013 CAS on 2 box and MBX on 3 box
will decomm the 3 exchange box which has (CAS+ HT + MBX roles) and 1 CAS which we use for owa access.
will keep the Journaling server as it is will not be decomming it as of now.
My question is is will i be able to connect to the journaling mailbox's which are hosted on exchange 2010 journaling server without actually having any 2010 cas server, will exchange 2013 cas directly help me to connect to the journal mailbox or would i need
to add CAS role on Exchange 2010 journaling server and enable outlook anywhere configure the directories with the url's to make it working.
Please suggest on the same.
BR/Deepak

Hi TheLearner,
Thank you for your question.
Exchange 2013 didn’t connect to the journal mailbox directly when we access it by outlook/OWA. The journal mailbox will connect the former Exchange 2010 CAS. Or we could migrate Journaling mailbox to Exchange 2013. Because Exchange 2010 could communicate
with Exchange 2010 by RPC, but Exchange 2013 could communicate with Exchange 2013 by HTTPS.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2013 - Outlook 2010 - 550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address

Hello,
I have issue when sending email to some addresses. Server respond with:
Remote Server returned '550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address (IMCEAINVALID-)'
My enviroment: Exchange 2013, Outlook 2010 - no cached mode. Issue happend with two email addresses but not always.
Any suggestion, how to resolve issue?
Thx.

Hi Tomas,
Does this issue occur in OWA? How is the impact, only one user or all users?
Please try to run Outlook under safe mode to avoid add-ins and AVs.
If there is any 3rd party add-ins, please try to disable them for testing.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2013, Outlook 2007 clients Problems with Outlook Anywhere connection

Hi everyone,
I have a mail system Exchange 2013 SP1, on Windows Server 2012 R2.
I have only one mail server with the Client Access and Mailbox roles Server.
I have a Wildcard certificate type *. Mydomain.com.
All connections to the Outlook Anywhere Outlook 2010, Outook 2013 work correctly.
The ActiveSync connections are working properly, too.
But Outlook 2007 clients connecting with Outlook Anywhere asking for credentials continuously fail continuously.
How can I solve this?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
Based on my experience, we need to set Outlook provider with the domain name if it's wildcard certificate:
Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com
http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx
Thus, I recommend you try the above configuration and test the Outlook connection again.
Thanks,
Angela Shi
TechNet Community Support

How to disable Exchange 2013 Outlook Anywhere for internal Outlook client

Hello;
By default, Exchange 2013's Outlook Anywhere is enable for all user mailbox, if I disable the Outlook Anywhere per user mailbox, the user will not able to connect his Outlook client to Exchange 2013. What is the best method to disable the Outlook anywhere
on mailbox but let the Outlook 2013 still able access to Exchg server.
The initial idea is to prevent user from access to company Exchange server from ANYWHERE, we just want to open the Outlook Anywhere for the authorized user only. Looks like Microsoft did not think about the security.
thanks!

Hello;
By default, Exchange 2013's Outlook Anywhere is enable for all user mailbox, if I disable the Outlook Anywhere per user mailbox, the user will not able to connect his Outlook client to Exchange 2013. What is the best method to disable the Outlook anywhere
on mailbox but let the Outlook 2013 still able access to Exchg server.
The initial idea is to prevent user from access to company Exchange server from ANYWHERE, we just want to open the Outlook Anywhere for the authorized user only. Looks like Microsoft did not think about the security.
thanks!
I don't understand your request. If you disabled Outlook Anywhere, Outlook will only be able to connect via IMAP or POP3.
If you want to disable this ability and allow some then perhaps use cas-mailbox to disable in bulk and then enable only those allowed:
http://technet.microsoft.com/en-us/library/bb125264(v=exchg.150).aspx
The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox by using Outlook Anywhere (RPC over HTTP) in Microsoft Outlook.
Valid values for this parameter are:
$true Only Outlook clients that aren't configured to use Outlook Anywhere (RPC over HTTP) are allowed to access the mailbox. By default, Outlook 2013 is configured to use Outlook Anywhere.
$false Outlook clients that are configured to use Outlook Anywhere (RPC over HTTP) are allowed to access the mailbox.
The default value is $false.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 - Outlook 2007 - Server name GUID

Hi Guys.
I am hoping someone can shine some light on something for me.
Right now I have the following with roles.
1 x Exchange 2010 - MBX & CAS
1x Exchange 2013 - MBX
1 x Exchange 2013 - CAS
Mix of Outlook 2007 & 2010
I migrated a user from Exchange 2010 over to Exchange 2013 and the process went fine. Email flow is working, OWA and Active Sync again working ok.
However when we opened Outlook 2007 it displayed a message to say an Administrator had made changes and we needed to restart Outlook. No issues there.
Outlook connected up fine and everything works. However when you look in the mail profile for the Exchange server name i see something like
[email protected]
Also Outlook Anywhere is ticked and when you untick it from the client and then open it again it comes back.
Are the above items of migration?

Hi,
RPC is no longer a supported direct access protocol. This means that all Outlook connectivity must take place using RPC over HTTP (also known as Outlook Anywhere).
Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP
address.
To expand on this a little bit, I worked an issue with a new Exchange 2013 environment for 3 days before figuring out that you do NOT specify a server name where it asks for it in Outlook, you use the format mentioned above.
For reference, I received a very particular error from testconnectivity.microsoft.com that made no sense until I discovered the server name format. If a test fails with a 404 HTTP Not Found error and an X-CasErrorCode of MailboxGuidWithDomainNotFound,
this is most likely your problem. Its very frustrating that Microsoft does not have it documented anywhere exactly what this error means, would have saved me a lot of time and energy.

Exchange 2013 outlook server name is my owa URL not hash

i was migrating from exchange 2003 to 2010 to 2013.
after the migration and i install the exchange 2013 with exchange 2010 and configured it. the outlook not working with users that migrated to exchange 2013, and working well with the users already existing on exchange 2010.
when i try to fix this issue i set my outlook provider using this commend Set-OutlookProvider EXPR -CertPrincipalName
"msstd:mail.mydomain.com"
but unfortunately it's impacted the server name in client outlook.
then i removed the outlook provider and create it again. but with no change. then i uninstall the CAS server and install it again but with now change too.
now the outlook server name is my URL "mail.mydomain.com" and i need to recover it to be hash like "[email protected]"
the outlook client version outlook 2010 sp2 & and outlook 2013

Hi,
Is there any error when you connect your Exchange 2013 mailbox in Outlook? Also confirm if the problematic users can access Exchange 2013 mailbox from OWA.
Generally, Outlook uses Autodiscover service to auto setup Exchange account in Outlook. We can check the Autodiscover service in Exchange 2013 (mail.mydomain.com is pointed to Exchange 2013):
Get-ClientAccessServer | FL Identity,fqdn,*autodiscover*
Set-OutlookAnywhere -Identity "Exch13\Rpc (Default Web Site)" -InternalHostname mail.mydomain.com -ExternalHostname mail.mydomain.com -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl
$True -InternalClientsRequireSsl $true
Also make sure the name which is used in the AutoDiscoverServiceInternalUri has been included in your Exchange certificate with
IIS service. We can restart IIS service by running IISReset /noforce from a Command Prompt window.
Regards,
Winnie Liang
TechNet Community Support

Exhcange 2010 to 2013 Outlook client still looking at the old CAS

Hello,
Exchange 2010 SP3 and Exchange 2013 Version 15.0 (Build 913.22) Living in Co-Existence mode.
When I move a test mail box from 2010 to 2013 the outlook client continues to look for the old CAS server. IT appear recycling Exchange Application pools and/or a forced AD replication solves the issue. repadmin /syncall. I would like to have this resolved.
I have thousands of mailboxes and recycling or replicating after each mailbox is moved is not acceptable. I see multiple posts on these forums that talk about the issue but none with a solid solution. Can any one point me in the right direction?

If I move a mailbox and delete the old outlook profile and recreate it, yes it will connect with the 2013 CAS server 9 out of 10 times. But randomly the outlook client when closed and restarted will try connecting back to the 2010 CAS server, when this happens
the users gets prompted for their credentials. I have had a ticket open with Microsoft for 4 days now. Spent about 6 hours on remote sessions. I have performed dozens of exchange migrations, 2003-2007-2007-2010, this is my first 2010-2013, I have no way
to explain this behavior.
Recreating profiles is not a legitimate fix, I have thousands of mailboxes, it just isn't feasible. Any help or guidance would be greatly appreciated. Thank you for the reply DareDevil57!
All of my DNS/SRV/autodiscover records public and private point to the new 2013 CAS server.
All remote connectivity test are green.
https://testconnectivity.microsoft.com/
This article describes my scenario exactly however no real solution is offered. Only manual fixes. Give the size of this environment it will not work.
http://www.jaapwesselius.com/2011/06/27/outlook-profile-not-updated-after-move-mailbox/

Exchange 2013 / Outlook 2007

Hi,
Just finish to configure Exchange 2013 CU3; I have no problem with OWA. But trying to connect to outlook 2007 SP3 (PC is joined to local domain: mysociety.lan) i'm facing with this error: "The connection to Microsoft Exchange is unavailable. Outlook
must be online or connected to complete this action". When i try to continue it gives to me : [email protected]; when i replace it to:[email protected] it connect; but restarting the computer give me the same error.
Please Help

Hi,
In addition, please use the ExRCA to test Outlook Anywhere connectivity and see if there is any error. For your convenience:
https://www.testexchangeconnectivity.com
Regards,
Rebecca Tu
TechNet Community Support

CRM 2013 Outlook client error

Hi
We have a test install of CRM 2013 which is working correctly on the server. Logon via the web is ok.
A user was setup to access through the outlook client in office13 running on a win7 platform which also worked correctly. The same user also has secondary access through the outlook client in office 13 running on a win8.1 platform. This never worked correctly
and would show credential errors.
Recently the win7 platform has also disconnected and shows connection errors.
I have tried the following on the win 7 platform:
1. Uninstall the client and reinstall from scratch - unsuccessful
2. Run through the steps in the built in trouble shooter - unsuccessful
Logon using the same creds via the web on the same machine is ok!
What are the next steps to rectify this problem?
Thanks in advance!

Hi Melon,
here is the full error message and a copy of the log file is given below.
17:50:49|   Info| === Microsoft Dynamics CRM for Outlook Configuration Wizard logging started: 24/03/2014 5:50:48 PM ===
17:50:49|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ClientConfig.Initialize
17:50:49|   Info| Client Configuration Wizard Version      : 6.0.0001.0061
17:50:49|   Info| Client Configuration Wizard LanguageID   : 1033
17:50:49|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.Validator.IsOutlookInitialized
17:50:49|   Info| Query all rows in profile table
17:50:49|   Info| Outlook is initialized
17:50:49|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.Validator.IsOutlookInitialized
17:50:49|   Info| Client Configuration Wizard Running Mode : Normal
17:50:52|   Info| Configuration file Type : OnPremise.
17:50:52|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ConfigInfo.ConfigInfo
17:50:52|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.OutlookCRMDatastoreInstaller.GetAllCRMOrgsInOutlookProfile
17:50:52|   Info| Logon mapi store
17:50:52|   Info| Logon admin service
17:50:52|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.OutlookCRMDatastoreInstaller.GetServiceIds
17:50:52|   Info| Query all rows in msg service table
17:50:52|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.OutlookCRMDatastoreInstaller.GetServiceIds
17:50:52|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ConfigInfo.CleanUpDatastoreIfNeeded
17:50:52|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ConfigInfo.CleanUpDatastoreIfNeeded
17:50:52|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ConfigInfo.ConfigInfo
17:50:52|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ServerForm.ServerForm
17:50:54|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm.ServerForm
17:50:54|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ServerForm.SetUIData
17:50:54|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm.LoadAvailableUrls
17:50:55|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm.LoadAvailableUrls
17:50:55|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm.SetUIData
17:51:03|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ServerForm._testConnectionButton_Click
17:51:03|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ServerForm.TestConnection
17:51:03|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm.TestConnection
17:51:03|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm._testConnectionButton_Click
17:51:30|   Info| Fill organization comboBox with server information.
17:51:35|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ServerForm._testConnectionButton_Click
17:51:35|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ServerForm.TestConnection
17:51:35|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm.TestConnection
17:51:35|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm._testConnectionButton_Click
17:51:36|   Info| Fill organization comboBox with server information.
17:51:37|Verbose| Method entry: Microsoft.Crm.Application.Outlook.Config.ServerForm._okButton_Click
17:51:37|Verbose| Method exit: Microsoft.Crm.Application.Outlook.Config.ServerForm._okButton_Click
17:51:40| Error| Exception : Metadata contains a reference that cannot be resolved: 'https://ldp-crm-01:80/LDP/XRMServices/2011/Organization.svc?wsdl'.    at System.ServiceModel.Description.MetadataExchangeClient.MetadataRetriever.Retrieve(TimeoutHelper
timeoutHelper)
   at System.ServiceModel.Description.MetadataExchangeClient.ResolveNext(ResolveCallState resolveCallState)
   at System.ServiceModel.Description.MetadataExchangeClient.GetMetadata(MetadataRetriever retriever)
   at System.ServiceModel.Description.MetadataExchangeClient.GetMetadata(Uri address, MetadataExchangeClientMode mode)
   at Microsoft.Xrm.Sdk.Client.ServiceMetadataUtility.RetrieveServiceEndpointMetadata(Type contractType, Uri serviceUri, Boolean checkForSecondary)
   at Microsoft.Xrm.Sdk.Client.ServiceConfiguration`1..ctor(Uri serviceUri, Boolean checkForSecondary)
   at Microsoft.Xrm.Sdk.Client.OrganizationServiceConfiguration..ctor(Uri serviceUri)
   at Microsoft.Xrm.Sdk.Client.ServiceConfigurationFactory.CreateConfiguration[TService](Uri serviceUri)
   at Microsoft.Crm.Outlook.ClientAuth.ClientAuthProvidersFactory`1.GetAuthProvider(Uri endPoint, Credential credentials, AuthUIMode uiMode, Uri webEndPoint, IClientOrganizationContext context, Form parentWindow)
   at Microsoft.Crm.Application.Outlook.Config.ServerInfo.LoadUserId()
   at Microsoft.Crm.Application.Outlook.Config.ServerInfo.Initialize(Uri discoveryUri, OrganizationDetail selectedOrg, String displayName, Boolean isPrimary)
   at Microsoft.Crm.Application.Outlook.Config.ServerForm.LoadDataToServerInfo()
   at Microsoft.Crm.Application.Outlook.Config.ServerForm.<InitializeBackgroundWorkers>b__2(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
17:51:40| Error| Exception : The underlying connection was closed: An unexpected error occurred on a send.    at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Description.MetadataExchangeClient.MetadataLocationRetriever.DownloadMetadata(TimeoutHelper timeoutHelper)
   at System.ServiceModel.Description.MetadataExchangeClient.MetadataRetriever.Retrieve(TimeoutHelper timeoutHelper)
Look forward to hearing from you,
Thanks

Exchange 2013 Outlook Client connectivity

Similar Messages

Maybe you are looking for