10 machines in a Peer-to-Peer Network with a mixture of W10 and W7 OS's, Office Pro 2003, 2016, 2019 all running 2 application MDB files (with split BE MDB data files) All but one machine can run both of these applications over the local network ... this one machine running Office Pro 2016 (32bit) has recently begun failing to load and run either of these MDB files or their data BE files
So far:
- attempted to load these files using the SHIFT key load option (so the apps don't start running) with the plan to do a compact/repair
- did a full Office Pro Repair on this machine (nothing reported)
- sfc /scannow (no issues found)
- virus scans using MS Security Essentials as well as Malwarebytes (nothing found)
- this Machine can ping the Peer Server
- the Peer Server can ping this Machine
- this Machine can run ACCDB apps located on the Peer Server
- did a forced compact/repair on both apps and their back end data files from the Peer Server ... attempts to do this from the machine having issues failed
basically any time these MDB files are opened on this Machine, ACCESS goes into a NOT RESPONDING mode.
Although these 10+ year-old apps have had recent minor cosmetic changes, because the other WX 2016 and WX 2019 machines don't have any issue running these apps, from my perspective, this suggests something external to these apps is causing this issue on this machine. Just haven't determined what and run out things to try
The event viewer states there are application errors relating to Access but not sure if these errors are related to the issue or my having taken down these programs with brute force by KILLING them from the Task Manager.
Machines
1 - WX 2016
2 - W7 2003 Peer Server
3 - WX 2016
4 - WX 2016 having issues unable to run these apps
5 - WX 2016
6 - WX 201
7 - WX 2016
8 - WX 2019
9 - WX 2019
10 - W7 2003 Stand-in Front Counter Machine
11 - W7 2003 Offsite Managerial Machine
Machines 1,3,4,5,6, and 7 were purchased at the same time so they all are running exactly the same HW and SW ... all have the same updates ... machines 8 and 9 were added over the last 2 years ... machine 10 was resurrected in the last year as a stand-in Front Counter machine ... the Peer Server is running an ADMIN MDB process written in Access 2003 which monitors an external ODBC SQL DB for crucial updates to these 2 apps ... an additional offsite Machine (W7 2003) can also reach in via VPN to access these apps ... The three W7 Machines with OFP 2003 licenses dictate the reason these apps are still in MDB format
If this were a PEER machine count overload, my experience is that PEER machines would randomly have issues (it has been well over a decade that I bumped the Buffering on the PEER Server to allow for more PEER machine connections not sure where my notes are on that registry change) ... being this issue is with the SAME machine and only this machine just doesn't flow with the early PEER issues we had many years back.
The MDB Apps are MATURE they have been working for over 10 years and even with some recent cosmetic changes still work on every machine BUT this one. If it isn't clear from my rambling, these APPS did and have worked on this machine.
Any thoughts on what else I can try?
Perhaps do a dump reload of all the app objects into a fresh MDB file?
Appears Access knows it has had issues with these files on this machine, not sure where that history is being stored, in some internal/local log OR if this is information is stored in the mdb files. Is there any way to forcibly reset this History?