Access Database is getting corrupt again and again

Anonymous
2018-06-01T17:47:41+00:00

We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted.  We ran compact and repair. But it still getting corrupted again and again.  This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.

Is there anything i have check in new windows update or any other step to prevent database corruption?

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

604 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-05-13T22:20:45+00:00

    The only other thing I can suggest is the client side registry change mentioned numerous times in this problem. I have incorporate this into my application setup and it seems to be working. This can be done on each Windows 10 PC and then would not require the server change to disable leasing. Restart the PC after making the change and do it on every Windows 10 PC that uses the database. The only downside is that it only takes one Windows 10 PC without these changes to corrupt the database again. 

    Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]"FileInfoCacheLifetime"=dword:00000000"FileNotFoundCacheLifetime"=dword:00000000"DirectoryCacheLifetime"=dword:00000000

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-03-07T12:51:18+00:00

    I have found that running this Registry edit on the client and the server has solved my corrupt database issues.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

    "FileInfoCacheLifetime"=dword:00000000

    "DirectoryCacheLifetime"=dword:00000000

    "FileNotFoundCacheLifetime"=dword:00000000

    Steve

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-06-14T16:44:07+00:00

    Shane,

    Had their IT department try to roll back the one machine and it's no longer showing.  After an hour on the phone with them they still can't roll it back.  The refuse to even think about the DisableLeasing claiming it will cause more problems.  (I even pointed them to your post above!)  Those are the only two work arounds I could find.

    Fortunately, a local Client and only one machine has the problem so I am going in there tomorrow to the person can use my laptop.  (They are only there half a day.)  But I will have to keep doing this until there is a fix.  (I am fortunate that it is only one Client and one machine!)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-06-12T18:04:23+00:00

    There are two potential workarounds:

    1. Set the DisableLeasing registry value to 1
    2. Ensure that either the SMBv2 or SMBv3 protocol are enabled

    In either case, this should be done on BOTH client and server machines.

    Let me know which of those you try, and the results.

    Thanks!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2018-06-11T05:08:43+00:00

    OK i will try this and update you. But does this workaround works for windows 10 and windows 7?  We have variety of client base who are having this issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments