Access Database is getting corrupt again and again

Anonymous

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?

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

Anonymous

2020-02-26T06:07:01+00:00

Yes I am 100% sure. Followed all the steps to many clients. The speed decrasement issue with this solution is when you are performing complex queries with dlookups as also if you are using continous forms with a few thousands of records.

Otherwise you notice just a slight speed decrease.

On the other hand, the disable leasing on server is by far faster under these db operations
Was this answer helpful?

0 comments No comments
Anonymous

2020-02-26T04:51:07+00:00

Really? A huge Performance impact! I have applied this to numerous sites with NO performance impact for the past 6-9 months with the corruption problem being fixed every time. Are you sure you are applying it correctly and that there is not some other factor that is causing the performance impact you are observing?
Was this answer helpful?

0 comments No comments
Anonymous

2020-02-25T20:41:45+00:00
What about the hack as mentioned before (and on Daniel Pineault's site) of changing the Client's File cache as below. Does anyone report an impact performance with this? This is the option I have chosen in the past 2 weeks.

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] "FileInfoCacheLifetime"=dword:00000000 "FileNotFoundCacheLifetime"=dword:00000000 "DirectoryCacheLifetime"=dword:00000000
This is the SMB registry fix that was mentioned above. It works well but with a huge performance impact
Was this answer helpful?

0 comments No comments
Anonymous

2020-02-25T08:48:46+00:00
What about the hack as mentioned before (and on Daniel Pineault's site) of changing the Client's File cache as below. Does anyone report an impact performance with this? This is the option I have chosen in the past 2 weeks.
```
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"FileInfoCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000
"DirectoryCacheLifetime"=dword:00000000
```
Was this answer helpful?

0 comments No comments
Anonymous

2020-02-25T08:27:46+00:00
I am also condirming the following:

If we are using the server disable leasing option, everything seems fixed. If this option is selected then corruption returns (but not so often) through mapped networked drive and corruption is not appearing again when using unc path for linking to the back end.

The other solution, the SMB registry fix, that is applied only on client machines, has a tremendous impact on speed, especially when using dlookups or dsums. The server disable leasing solution is also having a speed impact but is by far faster than SMB registry fix.

Tried the erd solution that mentioned here. The "turn off background refresh of group policy". So I dissabled all other solutions, made a clean restart to serveer and client machines, apllied this to server, rebooting again everything and checked. Didnt work for me
Hello Theodorus,

Many thanks for confirming your test results, particularly my suspicion that the SMB registry fix on clients can impact performance. Your experience with using the server disable leasing option with mapped drives is also invaluable. Great work.
Was this answer helpful?

0 comments No comments