Outlook 2016 & Hosted Exch. Outlook only updates after closing and re-opening.

thecomputerguy

Well-Known Member
Reaction score
1,407
I have a client who has Outlook 2016 and Hosted Rackspace Exchange. He has his email account on multiple computers and phones etc. This particular computer will only update when Outlook is closed and re-opened. Once re-opened it will update new mail then stop updating altogether until Outlook is again closed and re-opened. Folders stop updating too. His other computer with this email account runs Outlook 2010 (No issue with this one).

I've tried:

Reboots
Manual Send/Receive
Re-create profile and Dump OST's
Speedtest (350mbps down/50 mpbs up)
Reinstalled Outlook 2016

Computer is on a wireless connection and hard-wiring it is impossible. Wireless connection seems solid as speedtest/ping checks out OK and while remoted in the connection is very good with little to no lag/delay.

His OST is HUGE at about 35GB but it will basically update to 2GB or 4GB or 5GB or eventually 10GB then eventually 14GB then just stop. No other device has this issue. If I close and re-open Outlook I assume I would be able to eventually get the full 35GB downloaded but something is clearly wrong.

Ideas?
 
By chance is the internet connection behind an ISP gateway that has IPv6 enabled?

Wireless with a large OST like that shouldn't be an issue, my wifes OST is around that size, and zero problems with both her Win10 rigs with Outlook 2016 (or 13 before that).
 
By chance is the internet connection behind an ISP gateway that has IPv6 enabled?

Wireless with a large OST like that shouldn't be an issue, my wifes OST is around that size, and zero problems with both her Win10 rigs with Outlook 2016 (or 13 before that).

Not sure about the answer to that ...

Trying a downgrade to Outlook 2013
 
try a downgrade for sure,

Is the downgrade link always in the "Additional Options" page of the My Account section now? I just did one like this, but I remember the last time I had to do this a couple of months ago, there was no option other than phoning MS support and getting a 2013 key & link.
 
Jesus... another client today same issue ... what the hell did they do to 2016 .. so many random problems...
 
yeah, I wonder that too. I know for MSP guys this is not usually billable so I feel for you, but for break/fix it's somewhat profitable. I just am sick of it and explaining to clients.
 
Back
Top