none
Constant .ost Error RRS feed

  • Question

  • We are experiencing an issue in a non persistent XenApp environment with Outlook 2016 using O365 FSlogix containers. The employees keep getting the error message "Outlook is using an old copy of your Outlook data file (.ost). Exit Outlook delete the file, and restart Outlook..." This is happening to 10-15 employees per day. The vhdx files are stored on a DFS share, on a server 2012 file server.
    • Edited by yycctx Tuesday, January 14, 2020 4:41 PM
    Tuesday, January 7, 2020 9:30 PM

All replies

  • We had the same until we upped the connection retries.
    Thursday, January 9, 2020 10:18 AM
  • Thank you very much for the information.  Are you able to elaborate on the Settings you configured and the values used?
    Thursday, January 9, 2020 6:41 PM
  • Same issue, curious about the fix as well.
    Friday, January 10, 2020 12:40 PM
  • Connection retries for what? FSLogix ODFC? DFS? SMB on the server? SAN? I'm assuming FSLogix, and if so, what did you set it to, and which one did you modify? 

    Thank you!

    Tuesday, January 14, 2020 1:11 PM
  • Here are some of the changes we made to reduce the error messages:

    Logoff idle and disconnected sessions after three hours.

    Changed the DFS referral settings.  One of the two servers is set to "First among all targets", the second is set to "Last among all targets"

    FSLogix GPO, enabled the following:

    Locked VHD retry count (24)

    Locked VHD retry interval (5)

    Volume re-attach retry count (120)

    Volume re-attach retry interval (5)

    Slow application on Citrix / RDS – TSFairShare
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TSFairShare\Disk (0)
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TSFairShare\NetFS (0)
    • Proposed as answer by Tim Riegler Tuesday, January 14, 2020 4:43 PM
    Tuesday, January 14, 2020 4:31 PM
  • In addition, confirmed that the recommendations from this article were implemented.

    https://docs.microsoft.com/en-us/archive/blogs/samdrey/outlook-20102013206-general-recommendations-to-avoid-latencies-crashes-or-general-bad-user-experience


    Tuesday, January 14, 2020 4:39 PM
  • Thank you! We'll investigate. Not using DFS to host our FSLogix data, so we'll look into the other settings. The TS Fair Share is disabled via GPO on all of our XA VMs.
    Tuesday, January 14, 2020 4:43 PM
  • We had the same until we upped the connection retries.

    Still occurs, but not as much as before...

    We'll look in to the other recommendations. 

    Wednesday, January 15, 2020 8:39 AM
  • For us, the original error has decreased dramatically in terms of frequency.  We are now facing another infrequent error "The file C:\Users\username\AppData\Local\Microsoft\Outlook\username@domain.com.ost cannot be opened".  

    Friday, January 17, 2020 9:27 PM
  • Are u using differencing disks (RW) for the profiles that are having OST issues?

    Stephen

    Tuesday, January 21, 2020 10:36 PM
  • I'm using RW for ODFC and having the same issue for a few users.  Re-creating the ost "solved" it for all but one.  I've used process explorer to see if anything else might be using the ost to no avail.  

    I've also seen this happen when logging off/on and the initial session doesn't fully log off.

    Thursday, January 23, 2020 3:04 PM
  • we were told by FSLogix support that RWs with Outlook cache mode is not supported. Corrupted OST files are going to happen under that scenario. You would need to use Online mode if you need to support concurrent user logins.

    hope that helps.

    https://stealthpuppy.com/fslogix-containers-capacity/

    "Office 365 Container also supports concurrent access and sessions; however, once Outlook cached-mode is enabled, merging a read-write copy back into the primary container is not supported. You must then configure concurrent access per-session containers, where a container is created for each session."


    Stephen



    • Edited by slammers25 Monday, January 27, 2020 10:45 PM
    Monday, January 27, 2020 10:40 PM