Outlook Exchange Directory Connection - Slow Response

Hi All
We are in process of migrating from Exchange 2007 to 2013. Clients are Outlook 2013.
Users who are migrated to 2013 are experiencing outlook timeouts regularly throughout day (we do not run in cache mode).
I am noticing that Outlook Connection is reporting slow response times for Exchange Directory connection (screen shot shown below) i.e. 1000ms or above. All other connections are fine.
When outlook times out - I notice that connection to Exchange Directory is the one that times out also.
I suspect a GC / DC issue - perhaps Exchange is querying GCs outside of site? and that's causing timeout? WAN connections between sites are slow (1.5Mb or below).
But my AD team tells me there is nothing wrong with infrastructure. :-)
Could someone assist me in identifying the cause?
Thanks in advance
Anthony

Hi Anthony,
Please use OWA to check whether the migration completed successfully.
I noticed that you are not under the Exchange Cached mode, please try to turn it to Exchange Cached mode to have a test.
Please try to run Outlook under safe mode to avoid some AVs and add-ins.
I also found an related blog, collect some information for your reference:
These default Keep-Alive intervals are NOTs home networking devices and/or aggressive network devices on the Internet. Some of those devices are dropping TCP connections after as little as 5 minutes (300 seconds)
of inactivity. When one or both of the two default connections are dropped, the connection to the Exchange server is essentially broken and not useable.
To address this issue, we are recommending setting a registry key on the Exchange CAS to change the default Keep-Alive from 15 minutes (900 seconds) to 2 minutes (120 seconds):HKLM\Software\Policies\Microsoft\Windows
NT\RPC
More details in the following link:
Outlook Anywhere Network Timeout Issue
http://blogs.technet.com/b/messaging_with_communications/archive/2012/06/06/outlook-anywhere-timeout-issue-and-recommendation.aspx
Please correct me if there is any misunderstanding.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Thanks
Mavis Huang
TechNet Community Support

Similar Messages

Outlook 2013 connection status 'Exchange Directory' disconnected randomly for random users (Exchange 2013)

We have been encountering an issue where upon random Outlook 2013 users are unable to open the address book, or add a room to a meeting (using 'Add Rooms...' button), and an error message is displayed that the server is unavailable. Mail flow and
everything else functions normally.
If I look at the Outlook connection status of an affected user, I will see that all connections are established except for the 'Exchange Directory' connections which show disconnected. If I click the 'Reconnect' button the Exchange Directory connections
are re-established, and the user can now access the address book/meeting rooms as normal.
Are there any ideas what I would check, logs I could look at, events or anything I can check on the server side that might lead me to an answer what could cause this?

Outlook 2013 gets that data from Exchange 2013 by connecting to Exchange Web Services. That's where you should look.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site

Hi all,
I could really do with your help!
We have 3 physical sites, A, B & C, with sites A & B having a really fast low latency links between them, so from an AD point of view they are 1 site. Site C has links to both sites A & B, but the link is a lot slower.
We have an exchange design with 3 servers (one located at each physical site) that will form a DAG spread over the 3 physical sites. Ideally we will separate the CAS and mailbox server roles out and have them controlled by a hardware load balancer,
however we can have both roles on the same server if required.
What we want, is to prevent is a situation where an outlook client in site C connects to a CAS server in site A/B with the mail being hosted on a mailbox server in site C therefore traversing the network twice to get its mail.
From doing the Microsoft training course, my understanding is that in Exchange 2013, the CAS server only proxy's the request on to the mailbox server and does not redirect the request to the CAS server in the site where the mailbox server resides.
I have seen information online stating that a single namespace is the way to go as long as your site links/network bandwidth is good, but nothing to help with our scenario.
Has anyone else come across this situation and how did you get round it?
Thanks in advance :)

Hi Johnson,
Based on my knowledge, Outlook Client will connect to the CAS server which in local first.
Please check whether the CAS server that in site C is healthy.
If the CAS server in site C is healthy, please disable the CAS Load Balance for testing.
Also found a useful blog for your reference:
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2011 not connecting to exchange server

Hi,
I am trying to use outlook 2011 with my Mac to connect to my Company server Exchange with no success
while I can do it fine with the Mac native aplication "Mail".
Here after the Exchange Server Connectivity Test (in italian) which has been passed:
Altri dettagli Impostazioni account del servizio di individuazione automatica Risposta XML: <?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User> <DisplayName>GGGGG GIAMBERTO</DisplayName> <LegacyDN>/o=Messaging/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=U333</LegacyDN> <DeploymentId>4e25f968-2a52-4b3e-a495-85893d549218</DeploymentId>
</User> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>EXCH</Type> <Server>outlook-to.sede.corp.NN.com</Server> <ServerDN>/o=Messaging/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=outlook-to.sede.corp.NN.com</ServerDN> <ServerVersion>7383807B</ServerVersion> <MdbDN>/o=Messaging/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=outlook-to.sede.corp.NN.com/cn=Microsoft
Private MDB</MdbDN> <ASUrl>https://webmail-01.XX.com/ews/exchange.asmx</ASUrl> <OOFUrl>https://webmail-01.XX.com/ews/exchange.asmx</OOFUrl> <OABUrl>https://webmail-01.XX.com/OAB/8b29a335-91f9-459d-8226-af3af35a0f11/</OABUrl>
<UMUrl>https://webmail-01.XX.com/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <PublicFolderServer>EXC10TSPPF00.sede.corp.NN.com</PublicFolderServer>
<AD>RSDCFTS008.filiali.corp.NN.com</AD> <EwsUrl>https://webmail-01.XX.com/ews/exchange.asmx</EwsUrl> <EcpUrl>https://webmail-01.XX.com/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
</Protocol> <Protocol> <Type>EXPR</Type> <Server>webmail.XX.com</Server> <ASUrl>https://webmail-01.XX.com/ews/exchange.asmx</ASUrl> <OOFUrl>https://webmail-01.XX.com/ews/exchange.asmx</OOFUrl> <OABUrl>https://webmail-01.XX.com/OAB/8b29a335-91f9-459d-8226-af3af35a0f11/</OABUrl>
<UMUrl>https://webmail-01.XX.com/ews/UM2007Legacy.asmx</UMUrl> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <SSL>On</SSL> <AuthPackage>Ntlm</AuthPackage>
<CertPrincipalName>msstd:webmail.XX.com</CertPrincipalName> <EwsUrl>https://webmail-01.XX.com/ews/exchange.asmx</EwsUrl> <EcpUrl>https://webmail-01.XX.com/ecp/</EcpUrl> <EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr> <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt> <EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
</Protocol> <Protocol> <Type>WEB</Type> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <Internal> <OWAUrl AuthenticationMethod="Basic, Ntlm, Fba, WindowsIntegrated">https://webmail-01.XX.com/owa/</OWAUrl>
<OWAUrl AuthenticationMethod="Ntlm, WindowsIntegrated">https://webmailint-01.XX.com/owa/</OWAUrl> <OWAUrl AuthenticationMethod="Basic, Ntlm, WindowsIntegrated">https://webmailint-01.XX.com/owa/</OWAUrl> <Protocol>
<Type>EXCH</Type> <ASUrl>https://webmail-01.XX.com/ews/exchange.asmx</ASUrl> </Protocol> </Internal> <External> <OWAUrl AuthenticationMethod="Fba">https://webmail-01.XX.com/owa/</OWAUrl> <Protocol>
<Type>EXPR</Type> <ASUrl>https://webmail-01.XX.com/ews/exchange.asmx</ASUrl> </Protocol> </External> </Protocol> </Account> </Response> </Autodiscover> Intestazioni risposte HTTP: Connection: Keep-Alive
Transfer-Encoding: chunked Persistent-Auth: true Cache-Control: private Content-Type: text/xml; charset=utf-8 Date: Wed, 11 Feb 2015 05:31:48 GMT Server: Microsoft-IIS/7.5 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Tempo trascorso: 1894 ms.
And hereafter the Trouble shooting log of Outlook 2011:
Outlook Exchange Auto Configure,Verbose,=== Performing autodiscover for [email protected]
Outlook Exchange Auto Configure,Verbose,--- HTTPS endpoints
Outlook Exchange Auto Configure,Verbose,Querying https://xx.com/autodiscover/autodiscover.xml
Outlook Exchange Web Services,Verbose,"EWS: Request data on thread=0x7a2bf264, XML data=
<?xml version=""1.0"" encoding=""UTF-8""?><soap:Envelope xmlns:soap=""http://schemas.xmlsoap.org/soap/envelope/"" xmlns:t=""http://schemas.microsoft.com/exchange/services/2006/types""
xmlns:m=""http://schemas.microsoft.com/exchange/services/2006/messages""><soap:Header><t:RequestServerVersion Version=""Exchange2007_SP1"" /><t:MailboxCulture>it-IT</t:MailboxCulture><t:TimeZoneContext><t:TimeZoneDefinition
Id=""XXX Standard Time""/></t:TimeZoneContext></soap:Header><soap:Body><GetFolder xmlns=""http://schemas.microsoft.com/exchange/services/2006/messages""><FolderShape><t:BaseShape>IdOnly</t:BaseShape></FolderShape><FolderIds><t:DistinguishedFolderId
Id=""inbox""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""outbox""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""contacts""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""calendar""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""notes""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""tasks""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""journal""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""sentitems""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""deleteditems""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""drafts""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId
Id=""junkemail""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId><t:DistinguishedFolderId Id=""root""><t:Mailbox><t:EmailAddress>[email protected]</t:EmailAddress></t:Mailbox></t:DistinguishedFolderId></FolderIds></GetFolder>"
2015-02-28 11:44:10.075,0xFFFFFFFF,Outlook Exchange Web Services,Info,"EWS: Sending request on connection=0x7a399eb8, URL=/ews/Exchange.asmx, SoapAction=""http://schemas.microsoft.com/exchange/services/2006/messages/GetFolder"""
Outlook Exchange Auto Configure,Error, Error code: -3259
Outlook Exchange Auto Configure,Verbose,Querying https://autodiscover.xx.com/autodiscover/autodiscover.xml
Outlook Exchange Auto Configure,Error, Error code: -39
Outlook Exchange Auto Configure,Verbose,--- HTTP redirect endpoint
Outlook Exchange Auto Configure,Info, Error code: -3259
Outlook Exchange Auto Configure,Verbose,--- DNS SRV method
Outlook Exchange Auto Configure,Error, Error code: -3176
Outlook Exchange Auto Configure,Verbose,No _autodiscover._tcp.xx.com service found
Outlook Exchange Auto Configure,Verbose,--- HTTPS endpoints
Outlook Exchange Auto Configure,Verbose,Querying https://webmail.xx.com/autodiscover/autodiscover.xml
Outlook Exchange Auto Configure,Error, Error code: -39
Outlook Exchange Auto Configure,Verbose,Querying https://autodiscover.webmail.xx.com/autodiscover/autodiscover.xml
Outlook Exchange Auto Configure,Error, Error code: -3259
Outlook Exchange Auto Configure,Verbose,=== Failed to retrieve autodiscover settings for [email protected]
Outlook Exchange Web Services,Verbose,"EWS: Request data on thread=0x7c20cee4, XML data=
Can somebody help?
Thank you in advance

Hi,
The connection in Outlook 2011 for Mac is difference from the Exchange connection in Outlook for Windows. The Outlook for Mac is using EWS for Exchange connection.
According to your original posting, there seems to be some issue with your autodiscover service. And some Exchange services (such as OAB, OOF, OWA etc.) are using webmail-01.xx.com namespace in the URL. Please double confirm the configuration in your Exchange
server.
Additionally, please check the autodiscover service on Outlook for Windows machine. If all configurations in server side are correct but the issue persists, I suggest we can ask a question in Outlook 2011 for Mac forum for more help:
http://answers.microsoft.com/en-us/mac/forum/macoutlook?tab=Threads
Regards,
Winnie Liang
TechNet Community Support

After lion 10.7.3 update messed my mac had to restore from time machine now Outlook won't connect with microsoft exchange, any idea?

after lion 10.7.3 update messed my mac had to restore from time machine now Outlook won't connect with microsoft exchange, any idea?

I've had a similar problem. On my first boot up after installing 10.7.4, Firefox would not open. Crashed every time. Safari was not affected. I have no idea if it was related to the flash plugin, but I did install a the latest version of that a couple of weeks ago.
Here's what fixed it: a second boot up.

Slow response when using Xcelsius web service connection witn input values

We've been very successful in using the Xcelsius Web Service Connection. We've recently moved forward toward using input values when calling a web service and having issues with response time. Without input values, it takes 3 - 6 seconds to retrieve and display the results in Xcelsius, but, when using the input values to the web service, it takes about 27 seconds for Xcelsius to retrieve and display the results. Does anyone have experience with fixing slow response associated with using input values for a web service connection?

Hi Sharone,
What's the version of your Xcelsius and BOBJ server?
I'm asking because using the last version of BOBJ server (BOXI 3.1 SP 3) you have new services on CMC just to help Xcelsius to work better with WebServices.
Regards,
Rodrigo.

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Connecting to Outlook Exchange Server

I cannot connect to my Outlook exchange server on my iMac, although there was no problem with my iPad. Can you help me?

Hi NotSoKlear:
Please be kind enough to advise the folllowing:
1) Are you on a Mac ?
2) Is it Hosted Exchange such as CloudWire
3) Try unchecking the SSL through your email client settings and try again.
Let me know if that works.

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService

All the Exchange 2013 Prerequisites appeared to install correctly. The installation of Exchange 2013 on Windows Server 2012 hangs at Initializing Setup. Then I find event 4027, source MSExchange ADAccess in the application event log. The
same thing happens if I try to prepare the Active Directory from the command prompt. The old Exchange 2007 server and Active Directory Server are on the same network and all firewalls are off. The entire content of the event is below. Any ideas
appreciated.
Log Name: Application
Source: MSExchange ADAccess
Date: 1/30/2014 12:47:01 PM
Event ID: 4027
Task Category: (1)
Level: Error
Keywords: Classic
User: N/A
Computer: MAILSRV2.sescolighting.com
Description:
The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ExSetupUI.exe
3868
Get Servers for sescolighting.com
TopologyClientTcpEndpoint (localhost)
3
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0038715. TCP error code 10061: No connection could be made because
the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
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 System.ServiceModel.ICommunicationObject.Open()
at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient()
at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange ADAccess" />
<EventID Qualifiers="49156">4027</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-01-30T17:47:01.000000000Z" />
<EventRecordID>821</EventRecordID>
<Channel>Application</Channel>
<Computer>MAILSRV2.sescolighting.com</Computer>
<Security />
</System>
<EventData>
<Data>ExSetupUI.exe</Data>
<Data>3868</Data>
<Data>Get Servers for sescolighting.com</Data>
<Data>TopologyClientTcpEndpoint (localhost)</Data>
<Data>3</Data>
<Data>System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0038715. TCP error code 10061: No connection
could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
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 System.ServiceModel.ICommunicationObject.Open()
at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient()
at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)</Data>
</EventData>
</Event>
Tina M. White Boundless Data

Hello,
Please make sure whether you install exchange 2013 on a DC server. If so, we don't recommend you install Exchange 2013 server and DC server on a server.
Please use ping to check if the server you will install exchange 2013 server on can communicate with DC server.
Please use telnet to check if 890 port is opened on your firewall.
Besides, please refer to the following article to check if you have installed required components again.
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
Cara Chen
TechNet Community Support

Outlook Can't connect to Exchange Server

Dear All;
I install the exchange server 2013 in our Environment with basic configurations, it was work correctly in out look and OWA.
In this period I install outlook Clint and connect to exchange correctly , Then I log in to Exchange Administrations Center , then make some changes , after that i can't connect outlook Clint to exchange server while I
can connect to OWA but with error message related to Certificate.(Kindly check the screen shoot of error )
Kindly help me to solve this issue I beginner with Exchange.

Here are the default permissions for the Exchange virtual directories:
http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
I found that the print in the screenshots was not clear - maybe it's me or my browser.
What names do you have on the certificate?
exchange.abc.local
Is that it?
Is this a self-signed certificate? Or did you get it from Digicert, VeriSign, GoDaddy or some other 3rd party authority?
Regardless, the URLs for the virtual directories, OWA in particular, have to match what is on the cert.
So OWA might be:
https://mail.exchange.abc.local/owa
Other possibility:
https://webmail.exchange.abc.local/owa
Since exchange.abc.local is what you have on the cert, the URL has to configured as shown above. You can use "mail", "webmail" or whatever just before (once again, as shown above) but you have to make sure that is what the users enter
when they attempt to access email.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Outlook clients cannot connect Exchange 2013 cutover from 2010

Hello,
My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server.
We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
the external URLs are $null
Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
and 2013 CAS servers.
I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
It was only the Outlook 2010 and 2013 clients that could not connect.
We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
but the settings seem correct unless I'm missing something. Any help is appreciated.
Thanks!

Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

OUTLOOK FOR MAC CONNECTING TO EXCHANGE

I just purchased Office for Mac and Outlook won't connect to our exchange server.

Version number of your Exchange Server please

ISA 2006 slow response, connections timeout, maximum limit reached?

Hey guys,
I've been having an issue with a client's ISA Server for the past couple of weeks and haven't been able to understand why this is happening.
They have a couple of ISA Servers Enterprise Edition in an array. This ISA Servers give Internet access to the entire company. They have significant amount of traffic through a Cisco Iron Port that all the users proxy settings are configured to this device
and the Iron Port forwards the requests to the ISA Servers.
This implementation have been working fine for months, until a few weeks back that started to have slow response problems from the ISA Servers. Analyzing the reports from the ISA Servers, I've noticed an increased amount of traffic a few times this
has happened and mostly from the Iron Port. The Cisco people says this increase amount is due to the fact that the ISA Server stops responding and new requests are made at the moment from the device. We have configured the Iron port IP in the exceptions of
the Flood Mitigation Settings of the ISA Server, and configure it to take more than 20,000 connections.
Still after this configuration, the same problem raised a couple of days back. The ISA Servers stops responding and they need to be forced shut down and restarted to get them back to work.
There are also some errors from some other internal IPs that it reaches maximum connection limits, but these are about 10 errors like this only. I was thinking maybe there are some infected computers or something but they said that they scanned the ones
that show the errors and nothing is detected.
From the ISA reports of the time of the incident, I saw that it reached more than 15,000 concurrent connections. More than double of what it usually handles throughout the day.
I don't know if there is like a connection limit that the ISA can handle before it hangs of something?
Is there any ideas on what can be happening with this?
Thanks for any replies!
Eduardo Rojas

Hi,
Have you check the Event logs on the ISA Server? Any error?
You could use ISABPA to do some basic troubleshootings.
http://www.microsoft.com/en-hk/download/details.aspx?id=811
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

How to find out what server the outlook client is connected to/change it automatically

Hi,
I am performing a server migration from Exchange 2010 to Exchange 2010 (the previous installation was installed by an outsourced provider and is rubbish so I'm configuring it properly). On the of things the existing server lacks is a CAS array configured,
so I have built the new Exchange 2010 server, configured a new DB and CASArray. I have created a brand new mailbox for a new user and the user's outlook shows it is connected to casarray.domain.local, I have migrated my own mailbox but internally my outlook
shows it is connected to oldserver.domain.local (under the account settings when you go to change the settings for the account), this is on a domain joined internal desktop. But at home on my personal laptop non-domain joined, it has appeared to reflect the
new casarray.domain.local. The outlook client is 2007 in both situations.
When I run the following command, it shows my mailbox is indeed connected to the new exchange server, but this is not true in outlook
Get-LogonStatistics -Server "new-exch2010" | where {$_.clientname -eq "new-exch2010"}| ft username,servername,clientname
If I run the above command against the old server my name shows on that list as well. When I look at the connection status of my outlook it shows that it is connected to casarray for directory, but the old server for mail.
A couple of other things:
Mailflow is now going to the new exchange server from the gateway over port 25, the autodiscover record in the internal DNS is now also pointing to the new exchange server, outlook clients and users computers have been completely restarted but still don’t
seem to pick up the new settings, both the old server and new server functions as a multi-role exchange having the Hub, CAS and MBX roles.
Now that you have all that background info my question is two parts:
What is the correct powershell command I can run on the exchange server to ensure that all my outlook clients are connected to the new exchange server for all connection types (or identify those which are connected against the old server)?
How do I get the outlook clients to automatically pick up the casarray servername once their mailboxes have been migrated?
I am considering removing the CAS from the old server which may force outlook to find it’s new server but am unsure whether this will work or not, and I think I should migrate all the mailboxes into the new DB before I do this.
Other than that, I am out of ideas.
Appreciate, any help. Thanks
Steve

I had already run the command Get-MailboxDatabase | FL Identity,RpcClientAccessServer
and it only identified the old database as being tied to the server name, the new database has the correct casarray and all mailboxes are in this new database. should I also set the old database to point to my casarray as the second command indicates? can't
do any harm right?
also, I have outlook 2007 and 2013 at home and both of them had automatically reconfigured
themselves to point to casarray, my problem is with the internal clients.
today I have also noticed in DNS there is a Zone which points to autodiscover.domain.co.uk
and in there it points to my old server.
a few things to note about the above:
1. the zone is pointing to the .co.uk domain not the .local - is this correct?
2. should that zone even be in our internal DNS, i hadn't noticed on previous implementation
of Exchange I have done
3. if i change the record within that zone to point to my new server, will this likely show
up the popup message shown in this link http://www.rackspace.com/apps/support/portal/1218 I havent yet got a certificate for the new exchange server (few more days) and i dont want users seeing any kind of untrusted unsecure connection box or it
will only lead to panic and flooding the helpdesk
many thanks
Steve

Outlook Exchange Directory Connection - Slow Response

Similar Messages

Maybe you are looking for