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
    2018-06-27T17:53:19+00:00

    We haven't been able to confirm that the Windows issue is the root cause of the issues with Access databases, but it may be, so,

    1. If you haven't tried any other workaround, please let us know if installing the latest Windows update improves the behavior,
    2. If you have tried a workaround, and installed the Windows update, let us know if removing the workaround causes the problem to reoccur.

    Thanks,

    Shane

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-06-27T11:11:05+00:00

    I wouldn't assume anything at this point.

    All I can affirm is that the Access Dev Team has not updated their own workaround page related to this issue to include any mention of the above mentioned update.  So from my perspective, nothing has changed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-06-27T09:45:13+00:00

    Hey guys,

    I notice there is a new windows update available since yesterday - June 26, 2018—KB4284848 (OS Build 17134.137)

    https://support.microsoft.com/en-us/help/4284848

    in the fix notes we see the follow fix:

    • Addresses an issue where some users may receive an error when accessing files or running programs from a shared folder using the SMBv1 protocol. The error is "An invalid argument was supplied".

    can we assume this fix is related to this issue? I will check if we can apply this asap to our workstations, revert the regkey fix and evaluate

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-06-26T20:39:10+00:00

    Thanks Dan

    I don't think they want to be bothered trying it. I could not wait. We have been struggling for three weeks. I waited two days for them then

    decided to downgrade to 1703. I had to be sure the windows update was the issue & not the new server or access code. 

    It's been fine for two days now.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-06-26T17:50:07+00:00

    Did you try the suggested fix "Disable Leasing Registry Fix"?

    Did your IT company even try it?

    Was this answer helpful?

    0 comments