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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-03-25T01:23:19+00:00

    So what is it now? 10 or 12 months since Microsoft created this problem? Is the current state of the issue still that there has been no official fix from Microsoft?

    Yep, you pretty much summed it all up.

    Update 2019-03-25

    I was informed (by the moderators of this forum) that the above was not helpful, so let me be more explicit in my answer: "basically, absolutely nothing has changed and the only option remains implementing the DisableLeasing registry hack workaround."

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-03-25T00:57:56+00:00

    So what is it now? 10 or 12 months since Microsoft created this problem? Is the current state of the issue still that there has been no official fix from Microsoft?

    Shane Groff, can you please give us an update?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-03-12T14:10:37+00:00

    Do you know if you need to restart the PC or workstation service after making the registry change? Or does it take effect immediately without restarting anything?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-03-08T22:22:12+00:00

    I made the registry changes today on the user's PC since she is out of the office. So we'll see next week if it helps things.

    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