Access Database is getting corrupt again and again

Thanks Jon. I have to see if IT has any VM's available or are willing to buy some for us. However, given their lack of response in the past, I am not holding out a lot of hope for this option, as good as it may be.

George

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.

Hi Daniel,

Well, Option 1 isn't feasible since Windows 10 is at the point of no return here.

Option 2 is a possibility but I am concerned about the slow performance and the possible removal of mapped drives.

Option 3 I have to review again. Any downside here ?

Is the client side registry fix still a good solution or no ? I still have to research what this registry fix is accomplishing & how it addresses the db corruption issues.

Yeah, Option 4. That isn't an easy one, especially with lack of IT Support.

So bottom line, how would you rank these above solutions ? Another option is going back to the moved backend db folder solution, once we get back to work and get back on LAN. But who knows when that will be ?

George

Hi Ron,

Could you post your link again ? I didn't see it in your prior post.

Thanks,

George

The performance and mapped drive issue doesn't impact everyone equally.  So you may be one of the lucky ones where everything runs smoothly.  You won't know until you try.

I haven't heard of any issues regarding the file changing workaround.