System resource exceeded
The STB_MedB laptop gets the following error when sending:
- Mirosoft Access - System resource exceeded
Internally this is also noted in the dbengine object as error number 3035.
The error occurs specifically when the send program runs Query send check centralized is owner.
Current status of this problem
Please state if your laptop currently has this problem e.g.
- HSC_A1 - has system resource problem Ttenbergen 11:00, 2019 September 19 (CDT)
- HSC_B2 - doesn't have system resource problem Ttenbergen 11:00, 2019 September 19 (CDT)
List of locations:
- GRA_ICU - not yet reported
- GRA_N3 - not yet reported
- GRA_N5 - not yet reported
- HSC_A4 - not yet reported
- HSC_B3 - not yet reported
- HSC_D4 - It worked!
- HSC_H4 - Sent with no problems
- HSC_ICUa - not yet reported
- HSC_ICUb - not yet reported
- HSC_ICUd - it worked. Sending was fine.
- OAK_MICU - Sent with no problems
- STB_CCU - not yet reported
- STB_CICU - not yet reported
- STB_MedA - doesn't have system resource problem Pamela Piche 12:06, 2019 September 19 (CDT)
- STB_MedB - not yet reported
- STB_MedD - no system resource exceeded window, sending complete seemed a little slow, but o/w seems o.k. DPageNewton 11:43, 2019 September 19 (CDT)
- STB_MISI - not yet reported
Observation - A new build of Windows10 was deployed at around the same time this became more common again
|
Will need to find out more details from Herman. |
- In order to find out the running Windows 10 version do this:
- Press the Windows key + R
- Type winver
- Press Enter
- The result will be the About Windows window with information on the current running build. e.g: Version 1809 (OS Build 17763.720)
- Source: https://www.ilicomm.com/how-to-find-out-which-build-and-version-of-windows-10-you-have/
Observation - Timing of this becoming a problem again
Pagasa observed that this became a problem again around the same time we changed the schedule of PHI Loader.accdb. We discussed possible connections but could not think of anything causal. Just putting this down here in case someone else can think of the connection. Ttenbergen 15:34, 2019 September 12 (CDT)
Solution approach: Query size limiting
The error happens when trying to run Query send check centralized is owner. That query actually ties into the Centralized data.mdb's L_Log. This makes for a very large record set, and have a max size of 1GB rather than the general Access limit of 2GB.
- 13:29, 2019 September 4 (CDT) - optimized the query further, seemed to eliminate error for now, but error has recurred since
Solution approach: disconnecting wifi
Darryl from STB desktop had suggested that turning off wifi might fix this problem. Since they don't actually have wifi in their area this is easy to try. This worked during his tests, but they have had additional problems sending after that.
During additional tests at HSC Tina found out that sending is faster with wifi disabled, so she added some lines to the sending code that disconnect wifi at the start of sending.
Solution approach: Maxlock setting
- https://access-programmers.co.uk/forums/showthread.php?t=285553 sugggests to apply the following
- DBEngine.Idle dbRefreshCache
- DbEngine.SetOption dbMaxLocksPerFile, 1000000
Tried, doesn't solve the problem
MaxBuffer
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 2.x Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 3.x Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Jet\4.0\Engines\Jet 4.0
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\14.0\Access Connectivity Engine\Engines\ACE Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\14.0\Access Connectivity Engine\Engines\Jet 3.x
MaxLocksPerFile
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\14.0\Access Connectivity Engine\Engines\ACE - conf 1000000 Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\14.0\Access Connectivity Engine\Engines\Jet 3.x
Solution approach: Microsoft Hotfixes
- https://support.microsoft.com/en-us/help/2760394/description-of-the-access-2010-hotfix-package-ace-x-none-msp-october-3
- Hotfix is no longer available, suggests we use newer software.
- confirmed this is not installed
Noticed that we may not be getting Office updates installed (newest not present)
Status
As of 09:48, 2019 September 4 (CDT) this is still a problem, and recently more of a problem.
Next things I will try:
- try to send from local to local - the query works fine when I run it while connected to a local version of CFE
- updating ccmdb.mdb to .accdb; if that is the solution we will also need to update many scripts and VBS/VBA programs.
Related articles
| Related articles: |
Considerations
- https://stackoverflow.com/questions/34184018/does-upgrading-to-64-bit-access-fix-system-resource-exceeded-error
- Is it possible to update to 2010 64bit before going accdb?
- https://stackoverflow.com/questions/19550367/access-2010-system-resource-exceeded
- 32/64 Bit issue?
- Forms too big?
- Other programs using lots of memory?
- Windows 10 over Windows 7?
- Run Access in Windows 7/XP compatibility mode?
- https://stackoverflow.com/questions/34184018/does-upgrading-to-64-bit-access-fix-system-resource-exceeded-error
- Using MS Office 64 bit?