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-08-14T02:56:23+00:00

    I didn't realise that applying the fix on individual PCs could be problematic. Has anyone else who has employed the fix on client PCs had similar issues?

    Also, what has been people's experience with employing the fix on the server? I had the IT guy for a company that I've supplied a database to employ the server fix many months ago. It fixed the corruption problem and there were no problems with slow access times. Is there some other variable in the mix that can cause slow access times when the server fix is implemented? I've read that this can occur and I'm wondering why I haven't seen it in this case.

    I will shortly be installing a similar database for another client and I'm tossing up whether to ask their IT people to employ the server fix or to try the client PC fix.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-14T04:53:54+00:00

    I applied the fix on both server and workstations (DisableLeasing fix). Even computers that didn't have the fix had issues connecting to the server. It was messy.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-08-14T07:33:43+00:00

    My understanding is the DisableLeasing "FIX" causes more problems than it fixes and in many cases cannot be applied on big sites where servers are shared across many departments. The best fix is applying the simple registry change below to ALL the Windows 10 clients accessing the data - no need to apply to Win7 machines or to the Server. From experience this works and has been reported here numerous times to work. I am not sure why the Disable Leasing fix to the server is still being mentioned as a possible solution.

    Here is the registry change to apply to ALL windows10 "Clients"

    Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]"FileInfoCacheLifetime"=dword:00000000"FileNotFoundCacheLifetime"=dword:00000000"DirectoryCacheLifetime"=dword:00000000

    If anyone has applied this and still gets problems they should report it back to this list.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-08-14T08:36:30+00:00

    Hi

    I have applied the Server Fix to all my clients’ servers and my own. This fixed the Access corruption issue and there have been no problems with performance or connection. All good for over a year (touch wood). I have a mixture of 2008, 2012 & 2016 servers in the mix. 

    Hope this experience helps. 

    Graeme

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-08-14T08:48:33+00:00

    Is the server fix just a reg file that can be run on the server, similar to the client fix? If so, can you please post it? I didn't have any hands-on involvement in applying it on my client's server where it was applied by their IT people.

    Was this answer helpful?

    0 comments