System resource exceeded: Difference between revisions

TOstryzniuk (talk | contribs)
mNo edit summary
TOstryzniuk (talk | contribs)
Sending Process - CHANGES - for those staff that are getting the system resource ERRORs
Line 1: Line 1:
{{Bug}}
{{Bug}}


The STB_MedB laptop gets the following error message when sending:  
The following error message is display when sending: :: '''Microsoft 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]].


:: '''Microsoft Access - System resource exceeded'''
== Interim work-around: Pagasa will send for a collector who gets this error ==
*Nov 28.19- '''Sending only allowed between:  1430 to 1530 daily'''. 
*'''NO SENDING or ADDING NEW DATA to your CCMDB records after 1530 daily''' ---until further notice.--[[User:TOstryzniuk|Trish Ostryzniuk]] 11:43, 2019 November 28 (CST)
**'''Collector''':  must finish going through all data entry for that day that would benefit from Patient Copier since you will need to delete records as part of this
**'''Collector''' must run [[Pre-send Checker]] and correct all error ID'd before running [[News and backup]] '''each day'''.
*Try sending.
*If get this error message, stop trying to send
*'''Collector''' must coordinate with '''[[p:Pagasa Torres | Pagasa]]''' so that Pagasa can send your completed files. You must work very closely together on this so that no records are lost.
**'''Pagasa and Collector''': establish a phone call or email between the two of you
**'''Collector''': close out of Access and leave Access closed.
**'''Pagasa''':  download the newest backup file.
**'''Pagasa''' will email the '''Data Collector''' to open their CCMDB and delete all the COMPLETED profiles.
**'''Collector''' '''must check email''' for notification from '''Pagasa''' that they can proceed in the follow order to:
***(a) delete COMPLETED files
***(b) do New and Backup and
***(b) now be able to add any new data to their CCMDB 
*'''Collector''': you must delete the completed files because otherwise it will be impossible otherwise to distinguish between the completes that Pagasa sent, and the completes she has not yet sent.
*'''Collector''': after you delete the completed files Pagasa sent, you must do one more News and Backup.  This will help reduce the number of records being kept on laptop that no longer need to be there.


Internally this is also noted in the dbengine object as error number 3035.
== Date issue started with each laptop ==
 
The error occurs specifically when the send program runs [[Query send check centralized is owner]].
 
{{Discuss|
*main office needs documentation here in order to get better idea which laptop, how often and perhaps this would help us ID a pattern.[[User:TOstryzniuk|Trish Ostryzniuk]] 16:48, 2019 October 1 (CDT)}}
== Interim work-around to have Pagasa send for a collector who gets this error ==
*STB CICU - started Nov 27, 2019
*STB CICU - started Nov 27, 2019
*GRA ICU - started Nov 27, 2019
*GRA ICU - started Nov 27, 2019
Line 24: Line 37:
*STB_MEDB - B5_IMCU - started Nov 5.19  
*STB_MEDB - B5_IMCU - started Nov 5.19  
**Pam Able to send without error November 26, 2019 for this one day only.  Go figure.
**Pam Able to send without error November 26, 2019 for this one day only.  Go figure.
*STB_MedD - E5 - started Sept 2019
*STB_MedD - E5 - started Sept 2019  
 
 
**Pagasa and I had a look at STB_MEDD (Debbie’s) data, and it seems to be a matter of there really being too many records. MS Access is reaching its limit. For testing I tried to send with the first half of your patients and with the second half, and each works. Of course that is not a solution, but it confirms that the volume is the issue. In the long term we need to find an alternative to MS access, and to bring down the backlog, but that won’t be quick.
 
In the meantime, the following will have to be our '''work around''':
*If you have this error, stop trying to send, this error will keep coming up.
*Once a week, Data Collector must coordinate with [[p:Pagasa Torres | Pagasa]] for her to send your completed files. You will need to work very closely together on this so we don’t lose records. Here is how it will work:
**Data Collector:  must finish going through all data entry for that day that would benefit from Patient Copier since you will need to delete records as part of this
**Collector must run [[Pre-send Checker]] and correct all error ID'd before running [[News and backup]] each day.
**Pagasa and Data Collector: establish a phone call between the two of you
**Data Collector: close out of Access and do a news and backup and leave Access closed
**Pagasa:  download the newest backup file, delete the incompletes, and send the completes (3-5min)
**If all goes well, Pagasa will tell Data Collector to open Access and delete the completes
**Data Collector: you would need to delete the completes because otherwise it will be impossible otherwise to distinguish between the completes that Pagasa sent, and the completes she has not yet sent
**Data Collector: do one more News and Backup to move that to the newest status
This should allow files to keep being offloaded from Debbie’s laptop slowly, but it causes extra work for Debbie and Pagasa, so this is not a long term solution. We will need to discuss a longer term solution when Trish and Julie are back.


== Observation - A new build of Windows10 was deployed at around the same time this became more common again ==
== Observation - A new build of Windows10 was deployed at around the same time this became more common again ==
Line 52: Line 49:


== 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 [[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)
*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)
***Pagasa and Tina had a look at STB_MEDD (Debbie’s) data, and it possibly seems to be a matter of there really being too many records. MS Access is reaching its limit. For testing I tried to send with the first half of your patients and with the second half, and each works. Of course that is not a solution, but it confirms that the volume is the issue. In the long term we need to find an alternative to MS access, and to bring down the backlog, but that won’t be quick.


== Solution approach: Purging some old data from centralized ==
== Solution approach: Purging some old data from centralized ==