[AccessD] Speed Issues on network just with Access App

[John Bodin]

Well after several weeks, still having speed issues.  Jim, on your comment about maxing out MaxBuffers, does the max # of 65535 trigger some different behavior than setting it to a very large, but not max, 50000?  Just curious as I've mostly seen 50000 as the suggested number.

To date, I have made three changes on the machines:

MaxBuffers = 50000
GPEdit Turn Off Multicast Name Resolution = Enabled
Turn of Autotuning - Netsh Interface TCP Set Global Autotuninglevel=disabled 

Some days, everyone is good.  Other days, one or more stations are bad for 1/2 stretches or longer.  

Any other ideas besides embarking on a re-write to SQLServer?  Appreciate it.

John

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Tuesday, October 18, 2016 11:09 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Speed Issues on network just with Access App

John,

<<Any other ideas? >>

 A few.

1. Anti-virus - I would assume it's the same for all, but try turning it off.
2. NIC drivers - make sure their up to date.
3. Make sure there is no diagnostic protocol loaded for the NIC.  If so, remove it.
4. Make sure the NIC is not set to go to sleep (low power mode) 5. Are you using mapped drives or UNC?  If mapped, default settings in Win 7 disconnect a mapped drive after 10 minutes of inactivity.  You can disable this.
6. You should disable ipv6 if your not using it.

That's it for the moment off the top of my head.

 Oh and the MaxBuffers, set it to the max of 65535.   There was a bug in
some versions of Access when running on a 64 bit multi-core processor.   JET
has three background threads by default, one of which was for cache cleanup.
If the threads ended up on different processors, they can block one another.
Setting MaxBuffers to the max alters the cache cleanup process to work around that.

Jim.
 

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bodin
Sent: Monday, October 17, 2016 09:40 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Speed Issues on network just with Access App

Not sure if any of you have had the below issues before, but I haven't in the dozens of years of using access.  Driving me nuts, along with the customer.  Hope someone can help.  Sorry for long post but wanted to share details.

About 15 users w/Access 2000 running a front end access program Backend lives on a server in a shared folder (both FE/BE are MDB's) Gigabit Ethernet Switch Workstations are (were) XP Pro SP3, Win7Pro SP1 64Bit XP machines are Dell Optiplex 360's and 380's Win7Pro machines are Dell Optiplex 3020 Small Form Factor and Micro, and one Opti 7010

Above combo has been running fine since pretty much before dinosaurs became extinct.  Besides Access, some users have Quickbooks, and everyone has some flavor of Office H&B (2007, 2010, 2013, 2016).  None of the H&B come with Access, so only one version of Access on the PC.

In attempt to get remaining users off XP, I bought more Dell's, but they were the Optiplex 3040 Micros, Win7Pro 64Bit.  Not too long after putting these on the network, some, but not all, of the 3040 users experienced slowdowns where a screen that would normally take 2 seconds to open up, now taking 10, 15 sometimes up to 2 minutes.  Not consistent, user might work fine for a while and then bang, slow to a crawl, pretty much unusable.
Other 3040 users may or may not have same problem, but then some of the 3020 micro users experienced the same problem where they never did before, but not nearly as many times as the 3040 users.  Very strangely, the XP users never experience any of this nor the 7010 w/Win7Pro 64Bit, even when the other users are.  They just move along.  So to with the Opti 7010, no issue.
And all machines are running fine with all other apps - QB, Word, Outlook, PDF's, Internet, etc. - Just Access Issue.

Saw various articles describing same problem, even with a standalone workstation running both FE and BE with Windows 7 64Bit.  I haven't seen the issue if there is only one user in the system (common on a Saturday).
However, I've seen this issue with just 2 people in.

Although I can't tell if every machine needs the below or just ones with issues, I have tried the following based on many posts that I have read:

PC Specific:
Group Policy Change to Turn Off Multicast Name Resolution=Enabled Registry MaxBufferSize=50,000 Turn Autotuning Off (NetSh Interface TCP Set Global Autotuning=Disabled)

Non-PC Specific
I replaced the network switch with an older gigabit model but again, I do not think is it.
Replaced wiring at some workstations
Made sure the Lock file was deleted in the shared folder when all users out so it would get created fresh Access 2k SP1 or SP3 was installed on workstations Checked Tools/References to make sure none were missing on the workstation VBE6.DLL was dated 3/17/2015 on the Win7 Machines Bought a used Opti 7010 with same specs (because only other 7010 has never had an issue to date), set it up and put it on the network.  Issue right away with only one other person on the network Probably a few other things I forgot to mention, I've lost track

Customer has brought back some old XP machines because of issue and they are working just fine.

I have a 32bit Win7Pro machine that I am almost done reformatting and will put on the network to see if that does anything.

Any other ideas?  I don't think the number of users is the issue.  I have a
2002 Insurance app with 65 people in it from three locations all day long and no speed issues.

Thanks for taking the time.

John





---

John Bodin
sBOR Office Systems
jbodin at sbor.com<mailto:jbodin at sbor.com>


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com