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 No comments

604 answers

Sort by: Newest
  1. Anonymous
    2018-06-14T15:57:47+00:00

    Hi Gina,

    There will be a June update for Windows that we think will resolve the issue, but in the meantime, have you tried one of the suggested workarounds?

    Shane

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-06-14T15:41:41+00:00

    Ping Shane Groff,

    Can't roll back because it has been to long.  Is there any progress on getting this resolved!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-06-12T18:04:23+00:00

    There are two potential workarounds:

    1. Set the DisableLeasing registry value to 1
    2. Ensure that either the SMBv2 or SMBv3 protocol are enabled

    In either case, this should be done on BOTH client and server machines.

    Let me know which of those you try, and the results.

    Thanks!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-06-12T15:26:41+00:00

    Dear Shane,

    one of our customers is experiencing the exact same issue as described by some users here:

    • error on MS access database (back end) stored on a network share : ERROR 3343

    server = Windows Server 2012 R2 std

    • Microsoft Access has detected that this database is in an inconsistent state
    • only fixable by compacting the database
    • user has updated recently to Windows 10 1803

    we now have applied the workaround on our fileserver where the database is stored. We will see tomorrow how this performs.

    However, I'm not sure if this also has to be applied on the client pc's (Windows 1803) or only on the back end server?

    with kind regards,

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-06-12T07:00:50+00:00

    Hi Shane and Daniel,

    I have asked my clients to try this. We have VB6 frontend application which is installed on workstations and it connects to the database(MS access) which on server(Win 7).  5 workstations are of different window version (Win7 and windows 10). This setup was working fine since last 10 years. Suddenly after update its causing issue.

    Thanks,

    Amit Borse

    Was this answer helpful?

    0 comments No comments