We help IT Professionals succeed at work.

Problems with email after update to Exchange 2010 SP3

dakotas94
dakotas94 asked
on
238 Views
Last Modified: 2017-11-11
I'm running an SBS2011 Server and a few months ago I updated Exchange from SP2 to SP3. Ever since the update we have had some strange issues like email disappearing from Outlook but still showing up on our phones or OWA. Having to click send/receive on Outlook sometimes to get new emails in. New emails not showing up until we close Outlook and reopen, task flags not updating until we close Outlook and reopen. This happens on different computers, different users and different versions of Outlook (2013 & 2016). Some emails will disappear from Outlook once they have been opened but still show up on our phones or OWA. I am stumped!
Comment
Watch Question

K B

Commented:
I would patch to the latest CU version of SBS and Exchange

Author

Commented:
Already updated for both
K B

Commented:
So the errors are isolated to?:

1. Outlook?
2. In the Office?
3. Outside of the Office?
4. Wireless Connections
5. Wired Connections
6. 100% Fully Patched Windows
7. 100% Fully Patched Office

I recommend you try fully wired on a workstation with a brand new Outlook profile and report back results. all 100% patched

I know its not frequent but if it never happens there that will be a good level-set
Nathan HawkinsTechnical Lead - Network Security

Commented:
This sounds like an Exchange database issue. You may need to do some database maintenance. Have you ever done any (2010 is 7ish years old...)?

This is an article with some beginning steps to execute:
https://www.linkedin.com/pulse/20140323025652-86053522-exchange-2013-maintenance-without-user-impact

Please report back after you have done all these steps.
K B

Commented:
In Exchange 2010 the CAS role rendered views for Outlook.  In 2013 that was moved to the Mailbox Role.  Nevertheless, I don't see this being a database issue when OWA works perfectly.  If the database was the issue you would see the issue in more than just Outlook.

Author

Commented:
All wired connections all in the office, we don't use Outlook over the VPN. I have gone thru and set new Outlook profiles with the same results, it even happens with Outlook that is installed on the SBS Server. All updates for all products are current.
Nathan HawkinsTechnical Lead - Network Security

Commented:
Outlook is simply a client. It is the Database and how it presents its data to Outlook that (at least to me) appears to be the issue. I didnt say this IS a database issue, but I have seen things like this before from aging databases. The fix for me was we just went to the next version of Exchange and the problem/s went away. Since that doesnt seem like that will happen, if it were me, Id spend some time on the database.
K B

Commented:
do you have autodiscover working?  Is Outlook Anywhere configured?

Perform the check below and check the Protocol column and report back what you see please

2017-05-10_2119.png
K B

Commented:
Also are you running in cached mode or online mode?

Run Outlook in Safe Mode: quit Outlook, navigate to Start > in Search field type in outlook.exe /safe (mind the space between .exe and /safe)> Enter.


How often does this happen for a single user?

Author

Commented:
Yes and Yes, protocol is RPC/TCP, connections are fine
K B

Commented:
RPC/TCP is not Outlook Anywhere so we might look at your configuration of virtual directories.
K B

Commented:
Please run this on an Exchange server from elevated EMS prompt

1.      download the script https://gallery.technet.microsoft.com/scriptcenter/Exchange-Virtual-Directory-93839d75 
2.      rename it to get-virdirinfo.ps1
3.      Create a directory c:\scripts
4.      copy the RENAMED script to c:\scripts
5.      open elevated PowerShell prompt
6.      cd c:\scripts
7.      copy and paste this into EMS PowerShell:

. .\get-virdirinfo.ps1

Get-VirDirInfo –FilePath c:\scripts

8.      send me the HTML output please or post redacted

Author

Commented:
Cached mode, and happens for all users, running in safe mode makes no difference
K B

Commented:
Its best to use screenshots to post the HTML

Author

Commented:
I just messaged you the html file
K B

Commented:
I don't see it.. I see the message but no attachment.

Author

Commented:
Sent it again
K B

Commented:
Looks fine. Internally Outlook only fails back to RPC/HTTPS if it can't connect with TCP.

make sure the firewall service enabled on the server.. then turn off the firewall in start > run > firewall.cpl

Check the event logs of client and server.
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.