• Access (office 365) backend in an inconsistent state issue

    Home » Forums » AskWoody support » Productivity software by function » MS Access and database help » Access (office 365) backend in an inconsistent state issue


    We have been running our DB backend on a NAS box for several years with very little issue but have been fall foul of the “inconsistent state” bug  as documented here. As I am running on a NAS and not a server I can’t implement the workaround that it gives.

    There is the option of setting up SQL Server in a container on the QNAP NAS that we are using. Would this be a better way of running our backend? Is it worth looking into?

    Viewing 2 reply threads
    • #2428841

      On a QNAP box you should create a specific share for the DB and disable “Lock File (Oplocks)” under advanced settings.
      Only do this for the database file. All other file shares should be standard.

      Note: not tested, make regular backups of the database.

      Opportunistic lock (Oplocks) is a Windows file locking mechanism that facilitates caching and access control to improve performance. This feature is enabled by default and should only be disabled in networks where multiple users simultaneously access the same files

      cheers, Paul

    • #2429262

      Thanks Paul,

      I have set up a new folder as per instructions. Time will tell if it is a help.

      • #2504067

        I faced sam problem after update on  QTS 5.

        Is this disabling OpLocks help in zour case?

        Thank you.

    • #2504347

      We have not had a response from the OP so we don’t know if it worked for them.
      The only way to tell if it will fix your issue is to try it.

      cheers, Paul

    Viewing 2 reply threads
    Reply To: Access (office 365) backend in an inconsistent state issue

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: