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
    2018-07-02T19:39:37+00:00

    I'm glad you got on top of it in your situation but reinstalling Windows on many workstations and then disabling Windows updates isn't my idea of a fix in my situation. 

    I'm not holding my breath but MS should be all over this and be producing a proper fix ASAP.

    I'll know within a few hours if disabling leasing has worked and will report back here.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-07-02T16:04:23+00:00

    No doubt it's a windows 10 problem. We upgraded 12 workstations to the 1803 release and immediately had problems with our server side, linked database being corrupted, I would compact & repair but with a few hours the file was corrupt again.

    It took me a month to figure it out. I reinstalled windows on 6 workstations, did not install the new 1803

    release. We are running 1709. Since then we've no problems what so ever! I also disabled the Windows Update service.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-07-02T10:47:43+00:00

    It's just a registry key, try it, if you experience any issue simply switch it back.

    From what I've seen in this thread and others, the DisableLeasing hack fixed the issue.  In one case, one person started that although this worked, their databases were much slower.  No one else, that I've seen, reported any other issues.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-07-02T09:16:19+00:00

    We too are experiencing these issues, which have just reoccurred this morning whilst using build 1806 10228.20080.

    tbh I'm not surprised that this didn't fix the problem.... whilst there are 3 separate (June 2018) Insider Releases containing 'Access - Various performance and stability fixes' (https://support.office.com/en-us/article/insider-release-notes-for-office-2016-for-windows-desktop-523b3d33-8f46-4c79-b427-fdcf40c0b433 these seem to have been stripped form the latest 1806 release (https://docs.microsoft.com/en-gb/officeupdates/monthly-channel-2018#version-1806-june-25)

    We are hesitant to DisableLeasing - for fear of other repercussions. Do you have any indications of what they may be, if any?

    Thanks

    PAul

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-07-02T00:55:47+00:00

    No, not really.

    They're was a Windows update this week and people were asked to report back if that happened to resolve the issue, but nothing definitive.

    To my knowledge, the only true solution still remains the DisableLeading registry hack/fix.

    Was this answer helpful?

    0 comments