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: Oldest
Most helpful Newest Oldest
  1. 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
  2. Anonymous
    2019-03-07T18:16:26+00:00

    I didn't want to run that on the server as it's our file server for the entire organization. I didn't want to change those settings for everything. That's why I liked Mark's answer about the Leasing Mode and wish that worked.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-03-07T22:38:51+00:00

    Margaret,

    I ran the registry edit on the workstations only and it solved my issue (past 6 weeks) without any slowdowns.

    Has this fix not worked for anyone?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-03-07T22:56:08+00:00

    I haven't done that yet. My plan is to do that as soon as the user lets me on her PC and I'm hoping that will be sufficient to fix it without doing anything to the server.

    Thanks,

    Margaret

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-03-08T21:52:11+00:00

    Margaret,

    I am not an expert in Powershell. I don't think you need Server 2016. Perhaps it is the version of Powershell you are using. If you try these command under Windows 10 you will see they work. I may also try the other approach suggested to change the Windows 10 clients using the file:

    Windows Registry Editor Version 5.00

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

    "FileInfoCacheLifetime"=dword:00000000

    "DirectoryCacheLifetime"=dword:00000000

    "FileNotFoundCacheLifetime"=dword:00000000

    This approach is more easily implemented in my setup program if it works and does not require server changes. I would be curious to see how either approach works out for you.

    Mark

    Was this answer helpful?

    0 comments