Slow Access via LAN and windows 10

I think that the problem is when 2 users with Win 10 are working in the same time in the same form
 
After reviewing the entire thread, I see there is a significant question that was never asked. I'm not ashamed to ask questions for clarification.

What are the distribution characteristics of this database? I saw mention of a front end and that implies a back end. But does every user have a private copy of the front end?
 
After reviewing the entire thread, I see there is a significant question that was never asked. I'm not ashamed to ask questions for clarification.

What are the distribution characteristics of this database? I saw mention of a front end and that implies a back end. But does every user have a private copy of the front end?
Sorry for late reply and Happy new year !

Yes every user have a private copy of the front end

All problems solved now
On server I put new ssd disk and windows 7 pro
Users have win10

If users updated win10 we have crash on openning forms of Access 2000
The solution was to add the (Access 2000) msaccess.exe as an exception in the Data Execution Prevention (DEP).

Also I used the following for no hangs up :
Set these registry keys on the server: (Please look them up and check before putting these in place, don't blindly trust people who tell you to edit your registry! Including me!)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"EnableOplocks"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters]
"Oplocksdisabled"=dword:00000001

And this key on the client:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters]
"Oplocksdisabled"=dword:00000001
 
Update info:
All pc's except one working fast
Only one has problem
I thought it was a network cabling issue and I installed a new cable directly from the switch, but access it's slow again sometimes especially the first time you open a form. The second time is faster.
I don't know if it is a network card problem or windows problem or something else with this pc
 
try physically swapping with a ‘good’ computer, if the problem persists it implies a computer problem, if it doesn’t, a network problem

Also compare memory usage- perhaps the problem computer has a lot more apps open
 
OpLocks (see post 64) relates to SMB protocol's "Opportunistic Locks" feature, introduced during an upgrade to SMB v2, having to do with an attempted buffer optimization used for deferred updating of remote file contents open over a long period of time. SMB v1 couldn't do that, and this feature was introduced sometime around the advent of Office 2007. (SMB v2 came out in 2006).

"Deferred updating" is also known as "file write-behind" meaning that you update the particular disk buffer for a file and go on about your merry way immediately while the O/S does the actual write-back of the buffer contents based on linearizing the queue of pending disk operations... as opposed to always writing back contents immediately after an update, blocking the execution until the disk write is complete. What was happening with SMB v2 with Opportunistic Locks was that the file was staying open longer and running into file update collisions.

To learn more about this feature, Google: Why does Opportunistic File Locking not work in SMBv2?

(You will see a reference to, and explanation of, the registry hack from post #64.)
 
OpLocks (see post 64) relates to SMB protocol's "Opportunistic Locks" feature, introduced during an upgrade to SMB v2, having to do with an attempted buffer optimization used for deferred updating of remote file contents open over a long period of time. SMB v1 couldn't do that, and this feature was introduced sometime around the advent of Office 2007. (SMB v2 came out in 2006).

"Deferred updating" is also known as "file write-behind" meaning that you update the particular disk buffer for a file and go on about your merry way immediately while the O/S does the actual write-back of the buffer contents based on linearizing the queue of pending disk operations... as opposed to always writing back contents immediately after an update, blocking the execution until the disk write is complete. What was happening with SMB v2 with Opportunistic Locks was that the file was staying open longer and running into file update collisions.

To learn more about this feature, Google: Why does Opportunistic File Locking not work in SMBv2?

(You will see a reference to, and explanation of, the registry hack from post #64.)
Thank you.
Do you suggest to do this ?
 

Attachments

Yes. It is a known workaround for the SMB v2 bug. To be technically fair, it is actually a bug in Access because it didn't catch up to SMB v2 right away. I did a further search and up to Ac2021 (the version I personally run), that bug is still there. I also found notes suggesting that creation of a PDF can run afoul of the OpLocks bug. The only solution I've seen so far relates to disabling OpLock usage.
 
Yes. It is a known workaround for the SMB v2 bug. To be technically fair, it is actually a bug in Access because it didn't catch up to SMB v2 right away. I did a further search and up to Ac2021 (the version I personally run), that bug is still there. I also found notes suggesting that creation of a PDF can run afoul of the OpLocks bug. The only solution I've seen so far relates to disabling OpLock usage.

The base of the problem is windows 10 11?
This databese with Access 2000 worked from 1995 without problems at all with 10-15 users running windows 95-98-2000-xp win7
 
I've only just noticed this thread. Apologies if the following has already been mentioned.

Access 2000 is not officially supported in either Windows 10 or 11. It is functional but performance may never be optimal
The earliest supported version for Win 10 is A2007. For Win 11, A2010 is the oldest version officially supported.

In fact, A2000 hasn't been officially supported since Windows XP
For more info, scroll to the bottom of the page of this article:

 

Users who are viewing this thread

Back
Top Bottom