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. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2020-06-18T03:59:33+00:00

    Try it, and let us know how you fare.

    You are part of this community, and this is your way to contribute to it.

    Btw, that version is out of support: 

    https://support.microsoft.com/en-us/help/4456235/end-of-support-for-windows-server-2008-and-windows-server-2008-r2

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-05-03T21:47:40+00:00

    Well, I reverted the backend db from .mdb back to .accdb, moved my .accdb be database to another folder, then relinked the front end db to the new be's new folder location. Recompiled the fe to .accde and distributed to clients' desktops. This was after I reached out for IT Support and received no response.

    So far, the move to another be db folder trick seemed to be working again. Four days, no database corruption. I may have to fall back on the client side registry fix or disable leasing option if the database corruptions pop up again, but after a month and a half of daily db corruptions and no help from IT, It's good to find something that finally works again.

    George

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-04-28T18:40:31+00:00

    Virtual server is just another server, but they do not have all the same settings as a normal system. 

    Our company has tried the disable leasing, which caused communication problems with some of our Machining Equipment that is running XP still.

    Also, that supposed fix, disables more than what you think and can be a security issue.

    We then tried the registry fix on the client computers and the server.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

    "FileInfoCacheLifetime"=dword:00000000

    "FileNotFoundCacheLifetime"=dword:00000000

    "DirectoryCacheLifetime"=dword:00000000

    This link shows a list of parameters in the tuning servers. 

    It will give a brief explanation of what the parameters above are. 

    Edit:  add link::    https://docs.microsoft.com/en-us/windows-server/administration/performance-tuning/role/file-server/

    How it works is up to how you interpret it. I think the main thing to read is the 

    DirectoryCacheLifetime ,  notes in purple. 

    Why this worked for us we are not sure but we think it is related to server timing out a possible reconnect to the cached files or possibly one of these other theories. 

    When a access file is used, it creates a lock file.

    It is presumed the lock file gets cached as well and is not updated quick enough for the next incoming connecting to say its not locked.

    Or the lock file never gets renewed and the system doesn't update causing corruption?

    We run  ACCDE Front  and  ACCDB Back.

    Corruption was about once a week with 2010 Access.

    We upgraded to 2016 and had the issue multiple times a day until running the reg fix. 

    Knock on wood, we have not had an issue since October 2019. 

    I suggest having your IT guys look into the reg edit / fix and see what they think. Its ultimately their decision anyway.  They can get your company's current values and make another registry file, like this one to run in the event they need to revert back to the old settings.

    Not sure what else to suggest for you guys. We just know this has made the change we needed.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-04-28T12:10:19+00:00

    Hello All

    Corrupt files.

    My problems with corrupt files started after de-installing Office 2019 with only one user licence.

    I have other priorities before attending to this problem again.

    I accessed my *.accdb fils via  USB-Stick on my old windows 8 computer.

    Everything works.

    My files are not corrupt.

    The fault is my access on my Win10 computer.

    I suspect the database engine is the problem

    I hope this helps

    Bye

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-01-28T04:25:21+00:00

    Hi Tom  I am amazed you are still touting the disableleasing on the server as the solution - it has been pointed out here many times that (1) it requires administrator access to a server that in many cases is a shared resource used by numerous other departments in an organisation, and (2) it is a  "FIX" that is known to cause serious side effects for speed on some servers.  It is not a viable solution.

    So why is it still being rolled out here again. The simple Windows 10 CLIENT SIDE reg fix provided here 9 months ago works in every case and requires only local privileges on the Windows 10 Client. 

    The disableleasing on the server is not a solution and has too many caveats and side effects.

    Has anyone found this not to be the case?  Please post if you have applied the Client side fix and it has not worked.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments