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-04-16T07:00:38+00:00

    I agree it should be fixed by Microsoft. But in the interest of giving you and your clients some relief, I would urge you to try the client side registry change that has been suggested. It seems that is working for my clients without any downside so far. Also does not require a server change. Disable leasing on the server does work, so I suggest both to my clients, but the Windows 10 PC changes to the registry below seem to do the trick. 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

    I have a client with a small environment where the Access Files are stored on a Synology hosted SMB share. We are only seeing this issue created by 2 of the 5 Windows 10 Clients which are on build 1809. Can I expect this workaround to help even though only applied to those 2 client machines or do I have to modify parameters on the Synology too? I am Thankful for any advice.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-04-15T19:27:44+00:00

    For those following this issue, Microsoft updated their website regarding it as indicated below:

    Important: April 4 update: We have been able to gather additional data about the causes of this issue, which are due to usage patterns in the Access Database Engine with networked files that did not cause issues with previous versions of Windows, but no longer work properly.  We are testing a fix for this problem now, and will give further updates when we can confirm that this resolves the issue.

    The link is listed:

    https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state--7ec975da-f7a9-4414-a306-d3a7c422dc1d

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2019-03-28T19:15:14+00:00

    I agree it should be fixed by Microsoft. But in the interest of giving you and your clients some relief, I would urge you to try the client side registry change that has been suggested. It seems that is working for my clients without any downside so far. Also does not require a server change. Disable leasing on the server does work, so I suggest both to my clients, but the Windows 10 PC changes to the registry below seem to do the trick. 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

    Thank you Mark.  I will add this to the documentation that I've been distributing to my users.

    Was this answer helpful?

    0 comments