System resource exceeded: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
Line 10: | Line 10: | ||
== Observation - Timing of this becoming a problem again == | == 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 [[ | 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 == | == Solution approach: Query size limiting == |
Revision as of 16:45, 2019 September 12
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 laptop has a larger than usual number of records on it, but it is possible to send the data from Tina's laptop at HSC; although it turns out there are intermittent errors there as well.
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, seems to eliminate error for now.
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: Mirosoft 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
- sending again this morning to find out if wifi is still being turned off successfully - Wifi is still being disconnected successfully, and reconnected successfully
- 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: |