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-02-16T23:53:10+00:00

    Great post Mark!

    Fully agree on the credibility remark.  As if IT departments needed another excuse to not want to support Access in industry and then this!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-02-18T16:10:02+00:00

    We have a in house Point of Sale Access FE - BE application and have had many of the same issues as everyone else here. Our problem has not been nearly as severe as many others have been.

    We only seem to have an issue first thing in the morning after doing a maintenance compact and repair, on either Fridays or the end of the month. I will open the BE DB and re-compact and then all seems fine for another week. I have tried several of the easier fixes to no avail. 4 weeks ago, I came across a link by WayneAprato on page 12 of this thread "https://github.com/MicrosoftDocs/windows-itpro-docs/issues/934" and decided it couldn't do any harm and tried it.

    I have not had any lockups or slowdowns since applying the fix on the Win10 workstations.

     Here is the fix in the included thread.

    Copy and save the following text to notepad and save it as "SMBCacheFix.reg" (with quotes)

    Windows Registry Editor Version 5.00

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

    "FileInfoCacheLifetime"=dword:00000000

    "FileNotFoundCacheLifetime"=dword:00000000

    "DirectoryCacheLifetime"=dword:00000000

    I hope this will help others.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-02-19T15:15:25+00:00

    Bravo, Mark!  You have fully articulated the impact this is having.  I wonder if Microsoft realizes the sophistication of the applications that are developed under Access and how critical these applications are to government, business and data analysis.  It's not all Northwind.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-03-03T19:43:01+00:00

    Please review https://github.com/MicrosoftDocs/windows-itpro-docs/issues/934 and apply registry settings to Windows 10 computers.  This has resolved all problems with MSAccess back-end database issues.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-03-06T23:34:20+00:00

    I do not understand how you are able to disable leasing mode in SMB. LeasingMode is not a parameter for the set-smbshare command. Here's what I get when I try to run it:

    PS C:> set-smbshare Database-No-Lease$ -LeasingMode None

    Set-SmbShare : A parameter cannot be found that matches parameter name 'LeasingMode'.

    At line:1 char:33

    • set-smbshare Database-No-Lease$ -LeasingMode None

    +                                 ~~~~~~~~~~~~

        + CategoryInfo          : InvalidArgument: (:) [Set-SmbShare], ParameterBindingException

        + FullyQualifiedErrorId : NamedParameterNotFound,Set-SmbShare

    And when I run the get-smbshare command you describe, leasingmode is not a property that is listed.

    I've been Googling this trying to puzzle it out but finding nothing useful. I am running this on a 2012R2 server. It has SMB v1, 2 and 3 running on it. Does this require Server 2016 to run your command?

    -Margaret

    Was this answer helpful?

    0 comments