Outlook loses connection to exchange, pop up for credentials for specific internal users only

2 load balanced CAS/web exchange 2010.
"the connection to microsoft exchange is unavailable. outlook must be online or connected to complete this action"
No one is experiencing this externally, only internally on terminal servers.
Lync 2010 and Outlook 2010.
They get the Lync MAPI conneciton prompt.
Occasionally, after the above outlook error are prompted to enter credentials for exchange logon.
When I go to connection status during this issue, the "outlook.domain.com" URL is "established" for mail, but referral, and 2 directory statuses are "disconnected" or "connecting".
Address book service on 2 front ends are fine and started during this issue.
This is only happening for one department in our environment. Of course, they are the only department that uses Lync internally on terminal servers.
Lync config also says "EWS not deployed"
Other departments testing Lync internally so far, "EWS ok".
No other departments are having outlook issues.
Departments differ from one another by OU and GPO.
Josh

Hi,
According to your description, the issue may be related to your CAS array configuration.
Thus, let’s check if there is a DNS entry pointing to
Virtual IP Address of the CAS array and check load balancer's configuration.
http://blogs.technet.com/b/omers/archive/2010/10/11/microsoft-exchange-2010-cas-array-steps-and-recommendations.aspx
For the Lync issue, I recommend you ask for more professional help on our Lync forum:
http://social.technet.microsoft.com/Forums/lync/en-US/home?category=ocs
If you have any question, please feel free to let me know.
Thanks,
Angela
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Outlook Mac Loses Connection to Exchange Server

Hi All,
I've had this problem pretty since deployment a couple of weeks ago, so I'm hoping some one can point me in the right direction. I'm running Exchange 2013 on a Server 2012 Standard box with the DC running on a different box, every thing up to date.
Mac clients running Outlook 2011 (14.4.2).
Periodically throughout the day, Outlook loses connection to Exchange server. After several minutes, it will connect back up, and seems to operate normally. During the down time, I am able to connect to OWA, and ActiveSync seems to work as well.
If I run the Remote Connectivity Analyzer while Outlook is responding, I get no errors and the "Connectivity Test Successful" message. However, if I run it while Outlook is NOT responding, I get the following:
Exchange Web Services synchronization, notification, availability, and Automatic Replies.
Not all tests of Exchange Web Services tasks completed.
Creating a temporary folder to perform synchronization tests.
Failed to create temporary folder for performing tests.
Exception details:
Message: The request failed. The operation has timed out
Type: Microsoft.Exchange.WebServices.Data.ServiceRequestException
Stack trace:
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
at Microsoft.Exchange.Tools.ExRca.Tests.GetOrCreateSyncFolderTest.PerformTestReally()
Exception details:
Message: The operation has timed out
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
Elapsed Time: 100141 ms.
Nothing I've attempted to do so far as had any meaningful impact, and I am fairly new to Exchange.
Following the adice I've seen online so far, I've:
I've made sure the auto discover in DNS points to the Exchange server.
I've disable auto-discover on the client, manually adding accounts, tried using their FQDN, local IP, LAN IP.
I've made exceptions to the proxie on the client.
Just not sure where to look next? Appreciate any advice out there.
Thanks,
Michael

Hi,
Before we go further, I'd like to confirm if your Outlook clients can work well when your Outlook MAC clients come across the issue.
If the issue only happens on your Outlook MAC clients, we can check the IIS log and confirm if there is any error releted to EWS. And you can recreate your EWS virtual directory to have a test.
Thanks,
Angela Shi
TechNet Community Support

Lync 2013 Clients prompting repeatedly for credentials for calendar data from outlook

Our Exchange server had crashed recently (nothing major) and a reboot of the CAS server resolved the issues. However since then all our domain computers with Lync 2013 clients are prompting for credentials for calendar data from outlook. We would but in
our domain credentials but it still asks. It would sometime ask once a day or sometimes repeatedly throughout the day.
I have look on the forums and tried fixes that included: editing IIS Autodiscover and ESW to use NTLM first , rebuilt lyncs cache in app data etc and none seems to resolve the issue. Any help would be appreciated.
Note: Our Lync 2013 environment is internal only. Only users on domain computers can access the service. We do use a proxy server here for internet but I do not believe Lync is going through the proxy since its internal to our network only. This is NOT happing
to our users with the Lync 2010 client.

Please update your Lync client with the latest version.
You can check the following KB:
http://support.microsoft.com/kb/2825630/en-us
November 7, 2013 update for Lync 2013 fix the issue Proxy authentication dialog box appears when you sign in to Lync 2013.
Lisa Zheng
TechNet Community Support

Outlook 2013 randomly loses connection to Exchange 2007 server

Hello everyone,
I have received complaints from some of our users over the past couple of months about them not receiving mails or about sending mails which do not get delivered. A little bit of investigation into the matter showed me that Outlook 2013 had lost its connection
to the Exchange server. (Which is Exchange 2007 SP3 running on Windows Server 2008 / SBS2008, in case it matters.)
Which is bad enough in itself - none of our users running Outlook 2007 and 2010 had that problem - but it also does so in a rather inconspicuous manner, so the users did not notice. Closing and restarting Outlook helped every single time, but the users did
not notice when this happened, and telling them to just restart Outlook every hour or so does not seem like an overloy practical idea.
All of the clients encountering the problem are running Outlook 2013 on Windows 8/8.1 Pro. We do not have any clients running older versions of Outlook on Windows 8, so I cannot tell for sure if this problem originates in the OS or if it is an Outlook problem.
The first couple of times I encountered the problem, it was on laptops, so I suspected some power management issue initially. I made sure Outlook connected to the server via HTTPS, which it already did. Then I did not hear of the problem for about two months,
but recently, two of our users have run into the problem again, and while these were still Windows 8.1 machines, running, of course, Outlook 2013, they are plain desktop computers, not laptops, and I already toned down their power management settings, so I
do not think that it has to do with the problem.
Has anybody encountered a similar problem or even - more importantly - a solution? This problem is really frustrating, because our users are very sensitive to problems with their email, and the fact that this problem only occurs randomly and - all in all
- rather rarely, makes it very hard to track down.
Thank you all very, very much for any insights you might be able to share with me!

Hi,
Please ensure that Outlook 2013 clients retain their connection with the Exchange server using HTTP:
Have the Outlook 2013 user check the settings under FILE -> Account Settings -> Account Settings -> E-mail tab -> Select the account and click Change -> More Settings -> Connection tab -> Exchange Proxy Settings -> Make sure both
"On fast networks, connect using HTTP first, then connect using TCP/IP" and "On slow networks, connect using HTTP first, then connect using TCP/IP" are selected -> OK.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

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."

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

Need help with Outlook 2013 connecting to Exchange server(2010)

Hi
I need help with Outlook 2013 and with my exchange server(2010) email account
After setting up account initially emails come in and than after an hour or two stop. My OWA is working fine with no issues. I have even created a forward rule in OWA to my GMAIL account whch works fine
However Outlook 2013 is not syncing messages, have difficulty in sending emails sometimes as it takes too long. In fact the connection also is intermittent. Even if the task bar shows connected to exchange, it seems that is not the case since new emails
and any emails I compose dont work. I have trouble shot the issue with my ISP and email service provide, but they havent resolved the issue I have also done a TraceRoute and that shows no drops or problems to he exchange server.
Can someone please help me resolve this matter so I can continue to use Outlook 2013( running Windows 8.1) in both my computers which have the identical problem
Look forward to a solution soon
Thanks

Hi Angela
Thanks for your message
To answer your questions, please note the following
a) My account is set up in Cache Mode( not online mode)
b) I am the only other user on the account
c) When the connection to the exchange server is broken, I see upon clicking connection tab that there is no information in the box, and when I press reconnect it starts showing "connecting"
d) When the connection to the server is there, it shows connection as "established"
e) Sorry I dont understand th meaning of CAS array in your environment? Can you pls explain
Since yday I have been using Outlook 2010 on desktop and Outlook 2013 on my laptop using Exchange 2013 account. So far all emails are syncing, and I can send emails from both computers. However, I am concerned that the connection can break-off anytime,
as it has done that in the past on both outlook versions. The max time it has worked without any problem is 48 hrs and than after that the same issue of not connection, not syncing and unable to send emails happens
My ISP has checked and there is no network connectivity issues. My email service provider has trouble shot the issue many times, but to no positive results. I have also changed the profile a few times, but the intermittent connectivity problem hasn't
been resolved.
Can you identify the possible causes and more importantly a working permanent solution please
Thanks
Mahesh

Users lose connection to Exchange.

Hi
I have a Exchange 2007 on Windows 2003 environment with about 9,000 users.
Lately I have been struggling with an issue and I need some help.
Some users lose their connectivity of Outlook to Exchange (outlook appears Offline), even though they have Network connection and normally to solve this, I disconnect the network cable and reconnect it. I just want to clarify if this is a network or Exchange
issue and also, how could I solve this.
Thanks.

1) If unplugging the network cable to the user's computer and plugging it back in again fixes the issue, it is probably not a, server issue.
2) However, to test, can the user access OWA while their Outlook is unable to connect? If so, their mailbox is fine.
3) How are you configuring Outlook to connect - RPC/TCP or RPC/HTTP (OutlookAnywhere)? RPC/TCP will connect directly to the Mailbox server with Exchange 2007 and OutlookAnywhere will connect to the CAS server, so it is important to distinguish which
connection you are troubleshooting.
4) What is common about the group of users who lose connectivity? Same switch? Same Database? Connecting to same CAS (if OutlookAnywhere)?
5) Do some basic network connectivity tests (ping, tracert, nslookup, etc) on the PC when in repro
6) Collect and analyze a netmon capture during the issue.
EDIT:
Also, from a client perspective - take a look at event logs. Also, is AV installed and does the issue occur if you uninstall or disable it temporarily?

Outlook 2010 connected to Exchange 2013 prior to coexistence

I installed Exchange 2013 into the environment (Exchange 2010 SP3) and left it at that (ie no additional config). I noticed Outlook 2010 client connected to Exchange 2013 somehow (it got a cert warning). Why would Outlook connect to the new
Exchange 2013 server like that? Although I enabled Outlook Anywhere, it is not trying RPC/HTTP first, but rather RPC/TCP.

Hi,
By design, if the user mailbox located in Exchange 2010 server, the Outlook client will connect to Exchange 2010 server automatically.
According to your description, I found that we have nothing additional configuration on Exchange 2013. So, only server name and internal services' URLs are configured automatically during the Exchange 2013 server installation.
If it has no mailbox located in Exchange 2013, it is odd that Outlook client connect Exchange 2013 first.
I suggest running "Test E-mail AutoConfiguration" in Outlook to verify which Exchange server the Outlook connected.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Lync 2010 & 2013 Co-existence, After Moving fileshare clients are prompting for Credentials for RGS

Hello,
I am in middle of migration from lync 2010 to 2013. At the moment both enviroments are in Co-existense state, Got pools on both enviroments, however all users are moved to 2013 pool already. Also edge has been migrated already to 2013, and it seems to work
fine (except mobility).
Last Friday I decided to move the lyncshare from old server to new one (both servers were using same lyncshare on old server). I was using this guide: http://technet.microsoft.com/en-us/library/gg195742%28v=ocs.14%29.aspx and all were working pretty fine.
When about hour was passed after last steps, problems started to occur. All clients are asking for credentials to RGS, nowhere else. Entering credentials won't help, prompt appears again. If i cancel the prompt, lync works, but shows error in lower right corner:
Cannot synchronize addressbook (or something similar). Checking connection configuration from client shows that EWS is not deployed, which has been deployed.
I have also checked twice that the permissions are right on lyncshare.
Where should i start to look a solution for the problem ? Seems bit odd that moving a share kinda breaks whole system.

Hello,
Apparently the problem this time is not the Lync, but Exchange. As we are having Exchange migration on the same domain at the same time, I were troubleshooting the problem more, and found out that Lync Client is configured to use EWS Internal & External
url in "https://server005.domain.local/ews/exchange.asmx" , but when opening the url i receive the followin page:
and syntax is: svcutil.exe "https://server014.domain.local:444/EWS/Services.wsdl" , so If i understood right, the problem is in exchange, not in Lync at the moment.
About errors in FE Event Viewer, There is one error repeating often, have not found a solution yet.
Best Regards
Jaakko

SQLServer Reporting Services 2005 Prompts for Credentials for a trusted domain user

Currently the report is running in the domain AAA. Users in the domain AAA are using the report.
Another new domain BBB and an user XXX is now created and BBB\XXX has been given Browser access. Domain AAA and BBB are trusted domains.
After this when the user BBB\XXX logs in and access the report, before loading the report, credentials dialog is prompted, once credentials of BBB\XXX is entered, the report is loaded.
Why the report prompts for this additional credential dialog for the trusted domain user?

Hello,
Did you have get two textboxes in the report parameter panel (in the left side of the "View Report" button)? The issue is occurred when the credential of the datasource is configured with “Prompt for credentials”. Please check if you configured the credential
with "Stored Credential" of the datasource.
Please refer to the following thread to configure the credential.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/1564cd7a-6b7a-40f1-9f98-5c766ebfc63e/datasource-userid-and-password-being-asked-eachtime-when-report-is-generated?forum=sqlreportingservices
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

First timeout, push retry and then succesfull connect?! Starting Outlook 2010 connect to Exchange 2013

Hi!
Some info:
2x AD/DC Windows 2003 Native.
Previous Exchange 2003 installed, but now cleanly as it gets uninstalled.
Exchange 2013CU2v2 Aka Version 15.0 (Build 712.24)
Office 2010 with Outlook 2010 (Latest SP, and WU)
Outlook-prf configured for Outlook Anywhere. (i've also tried to configure manually, no difference)
Exchange: SAN Cert. GUI requested from ECP. This one covers all possible host names the server can use. autodiscover, owa, mail, "netbios"-name. Self issued from the internal CA. CA distributed to clients with GPO. I get NO certificate warnings
surfing to OWA, ECP.
Exchange: ECP/Server/Outlook Anywhere; Auth set to NTLM (not Negotiate)
Ping inside host names resolves to the Exchange server.
Starting Outlook.exe with /rpcdiag show two connections for a while. One of the type catalog and one of the type redirect.
Problem:
When starting Outlook you see "Loading profile" for about 30-40 seconds. /rpcdiag show two connections CID "9","11"; SERVERNAME "---","[GUID]@thedomain", AUTH and ENCRYPT is empty.
The the a dialog comes up that says that the server isn't available?!
Clicking "Retry" makes Outlook connect as it should. Everything from there works like a charm! /rpcdiag windows show that it has connection as it should.
Tried to click "Reconnect" in /rpcdiag. It also takes about 30 sec before it regains the conneciton. The part hanging there is the Type: Redirect.
So, does anyone have a clue for why it doesn't work and then does?
Can it be something wrong with the autodiscover?

Hello,
Do you mean the issue occurs when you select manually configure outlook exchange account or automatically configure outlook exchange account? If so, please make sure whether all users have the issue.
I recommend you check if there exists redirection on your rpc virtual directory.
I recommend you use "test e-mail autoconfiguration" tool to check if your autodiscover is correct.
Besides, I recommend you to enable global and advanced logging for outlook to check RPC trace events.
How to enable global and advanced logging for Outlook 2010 and Outlook 2013
http://support.microsoft.com/kb/2260527
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

Hello,
we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
using Outlook Anywhere.
The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content## from the external provider's servers.
When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
We have no problems using the company's Exchange 2013 servers.
Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
Thank you
Sascha

Hi,
The problem should be related to the External Exchange 2007.
Please refer to this kb below:
http://support.microsoft.com/kb/2203381/en-us
This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body. If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
To resolve this problem, you should let the External Provider install the following update rollup:
2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
Hope this helps.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Outlook problems connecting to Exchange server

I am using client version 5.0, PIX 506e and Microsoft IAS to vpn into a corporate network. Once connected some users have problems with their Outlook unable to connect to the Exchange server. Trying to figure out if I need to make a configuration change, or if a Microsoft issue. Thanks.

The problem could be because of MTU sizing. Reduce the MTU sizing of the tunnel on both ends till the end users do not face any such connectivity problems. Packet reassembly and fragementation are some of the main causes for connectivity loss.

Iphone 5 loses connectivity to exchange server

I know this is pretty common with Exchange servers...any news/updates? I have heard it is impossible to drop back to a previous version of IOS...like 6.1...too bad!

Thanks James, however I have tried that numerous times. Even tried to restore the phone to factory settings however I am getting an error that prevents the restore. I'm starting to believe there is something wrong with the phone.

Outlook loses connection to exchange, pop up for credentials for specific internal users only

Similar Messages

Maybe you are looking for