• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 109
  • Last Modified:

Exchange 2013 Disappearing Reappearing messages

I've just finished migrating my Exchange 2010 server to Exchange 2013.  Everything went smoothly, even the UM stuff transferred pretty nicely.  After having the Ex2010 server powered off for a week I turned it on today and uninstalled EX2010.  That went smoothly after I moved my public folder replicas (we don't use public folders, but they were used once upon a time).  However, now that the EX2010 software is removed from the server, and the server powered down I'm having an issue with some of my users with outlook clients.

Once the user opens Outlook (2013), the status bar says, "Updating this folder.   Connected to: Microsoft Exchange".  After a few seconds it says, "This folder is up to date."  The user then sees all of their messages.  A few seconds later, the status bar will read "This folder was last updated at: HH:MM", and shortly thereafter will switch to "Updating this folder" and the latest dozen or so messages will disappear.  After a few seconds it'll say "this folder was updated at: HH:MM" except the time will be a half hour ago.  A couple more seconds later, the messages will re-appear in the inbox list and the status bar will say "this folder is up to date."

The messages don't seem to go anywhere.  If you've got one selected, it's visible in the reading pane the entire time the disappearing-reappearing act is going on.  I checked the email account settings and the server name is <uid>.domain.com  rather than <servername>.domain.com which strikes me as odd, but it does work and we're not using http (local network clients appear to be the only ones affected).  I've checked mobile devices and OWA and neither seems to exhibit this behavior.  So I'm suspicious of the servername.  I went into control panel and checked the mail settings there and ran a repair and that didn't change anything (the server name or the behavior).

I'm stumped, but it doesn't appear to be destructive, just a now-you-see-it, now-you-don't that becomes really annoying when you're trying to click on an email (because they all move up/down).
0
MihiNomenEst
Asked:
MihiNomenEst
  • 3
1 Solution
 
FOXActive Directory/Exchange EngineerCommented:
Try running the Exchange Remote connectivity Analyzer on the client in question to see if it throws any errors.  Use the exchange tab and select outlook connectivity

ref link:  https://testconnectivity.microsoft.com/
0
 
MihiNomenEstAuthor Commented:
I ran the outlook connectivity test on both a local client and on a remote client.  The only warning I get is:

The address book Bind operation returned ecNotSupported. This typically indicates that your server requires encryption. The Microsoft Connectivity Analyzer will attempt the Address Book test again with encryption.

The analyzer then runs the test again and succeeds.


I removed the exchange account from my own workstation then re-added; this time I didn't enable cached mode.  This seems to stop the behavior, but I'm not sure it's a practical solution for my road warriors with laptops.
0
 
MihiNomenEstAuthor Commented:
After watching Outlook's connection monitor, I noticed a connection popping up but never establishing to a guid.domain.com that looked familiar.  The other three connections would establish, then drop which explains the now-you-see-it, now-you-don't behavior.  A couple of googles later:

https://social.technet.microsoft.com/Forums/en-US/fda6f2b4-9eb9-46cb-ad7e-6e343e83d12a/error-microsoft-exchange-sending-reported-error-0x80040115?forum=exchangesvrclients

https://blogs.technet.microsoft.com/exchange/2013/01/14/managing-oab-in-exchange-server-2013/

http://msexchangeguru.com/2014/11/07/exchange-2013-public-folders/


The guid that wasn't connecting was to a public folder mailbox I had created with -holdformigration but never migrated to because we stopped using public folders years ago.  Deleting the folder caused a newly configured client to display, "Updating folder 55.4mb (3 min)" then, it actually updated.  OL connection monitor showed three solid, established connections.  OL's status bar would still show "This folder has not been updated" so I created a new public folder mailbox which didn't help, but then I created a public folder and now everything appears to be completely normal.
0
 
MihiNomenEstAuthor Commented:
Unfortunately, I figured this out on my own before anyone else could respond.  rather than delete the question, I'm accepting my own solution in case someone has a similar problem.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now