I have asked the onsite tech to run Test Email Autoconfiguration, and Connection Status from the right-click menu on the notification area Outlook icon, and send me the results. This may be another symptom, but we will troubleshoot this issue, and maybe that will lead us to a solution for the main problem. Second, there are no OAB files on the computer. From what I read this seems to be only a display issue, and unrelated to our problem.
#OFFICE 2016 OUTLOOK SEND UPON EXIT UPDATE#
If the folder is updating more than 4gb of mail items, the status will be incorrect, causing the update operation to This seems to be a problem only for the status update area, which shows a maximum 3.99gb left to update. We also ran the OFFCAT tool, which came up with two "critical" issues.įirst, inbox is bigger than 4gb. If you have feedback for TechNet Support, we tried renaming the send/receive settings file but that did not fix it. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If the issue would be gone, please enable Cached Exchange mode again and then recreate your OST file to see If you have feedback for TechNet Support, you using Outlook with cached Exchange mode enabled? If so, please try switching to online Exchange mode and then check if this issue continues.
Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office See:Ĭonfiguration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. If above doesn't fix the issue, please try creating a new mail profile in Control Panel and reconfigure your email account in the new profile to see the result. old, then, restart Outlook and test the issue again. To do this, exit Outlook, navigate to the following path:Ĭ:\Users\%username%\AppData\Roaming\Microsoft\Outlookįind and rename the. We can also try recreating the send/receive settings file (.srs) in case the send/receive settings file is corrupt. Are you using Outlook with cached Exchange mode enabled? If so, please try switching to online Exchange mode and then check if this issue continues.