System resource exceeded - Revision history

Ttenbergen at 23:39, 5 May 2020

2020-05-05T23:39:28Z

← Older revision		Revision as of 18:39, 5 May 2020
Line 1:		Line 1:
	{{Fixed ~~Bug~~}}		{{Fixed bug\|}}

	This problem was fixed with [[CCMDB.accdb_Change_Log_2019#2019-12-07]].		This problem was fixed with [[CCMDB.accdb_Change_Log_2019#2019-12-07]].

	See page history for details, deleting from here so they don't pollute the searches.		See page history for details, deleting from here so they don't pollute the searches.

Ttenbergen: cleaning up info since this is fixed; if anyone still gets this error let Tina know

2020-05-05T23:39:12Z

cleaning up info since this is fixed; if anyone still gets this error let Tina know

Show changes

Ttenbergen: /* Status */

2020-05-05T23:28:02Z

Status

← Older revision		Revision as of 18:28, 5 May 2020
Line 116:		Line 116:
	* https://stackoverflow.com/questions/34184018/does-upgrading-to-64-bit-access-fix-system-resource-exceeded-error		* https://stackoverflow.com/questions/34184018/does-upgrading-to-64-bit-access-fix-system-resource-exceeded-error
	** Using MS Office 64 bit?		** Using MS Office 64 bit?
	~~{{Discuss \|~~emailed Brandon to see if this might be possible to test~~. }}~~		*** emailed Brandon to see if this might be possible to test
			**** as of 2020-05 eHealth seems to paln to move to Office 360, so this may well be moot; also, the problem was resolved by differently so not pursuing this further for now Ttenbergen 18:28, 2020 May 5 (CDT)

	== Related articles ==		== Related articles ==

Ttenbergen: /* Steps Sending Locally */

2019-12-09T17:15:45Z

Steps Sending Locally

← Older revision		Revision as of 12:15, 9 December 2019
Line 140:		Line 140:
	** Windows 10?		** Windows 10?
	== Steps Sending Locally ==		== Steps Sending Locally ==
	** Open ccmdb.data.mdb		* Open ccmdb.data.mdb
	** Go do Database Tools		* Go do Database Tools
	** Visual basic		* Visual basic
	** Click Global -You will see txt message		* Click Global -You will see txt message
	*** ‘ Public Const Centralized_data_accdb = Outpath & "Centralized_data.accdb" –become green once you add apostrophe (')		** ' Public Const Centralized_data_accdb = Outpath & "Centralized_data.accdb" –become green once you add apostrophe (')
	*** Public Const Centralized_data_accdb = "C:\Centralized_CCMDB\" & "Centralized_data.accdb"		** Public Const Centralized_data_accdb = "C:\Centralized_CCMDB\" & "Centralized_data.accdb"
	** Then save		* Then save

	== Sending ==		== Sending ==

Ttenbergen at 17:14, 9 December 2019

2019-12-09T17:14:35Z

← Older revision		Revision as of 12:14, 9 December 2019
Line 56:		Line 56:
	*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.		***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: copy those parts centralized to local ==
			2019-12-09: Copy those parts of of CFE L_Log that are needed by [[Query send_check_centralized_is_owner]] to local, do comparison, then delete them. This way the query doesn't need to run across the network.

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

Ttenbergen: /* Observation - A new build of Windows10 was deployed at around the same time this became more common again */

2019-12-09T17:10:59Z

Observation - A new build of Windows10 was deployed at around the same time this became more common again

← Older revision		Revision as of 12:10, 9 December 2019
Line 52:		Line 52:
	** The result will be the About Windows window with information on the current running build. e.g: Version 1809 (OS Build 17763.720)		** 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/		** Source: https://www.ilicomm.com/how-to-find-out-which-build-and-version-of-windows-10-you-have/
	~~{{Discuss \| Herman, do we have an idea which versions would be the "working" vs "broken" ones? }}~~

	== Observation - Timing of this becoming a problem again ==		== Observation - Timing of this becoming a problem again ==

TOstryzniuk: /* Date issue started with each laptop */

2019-12-04T22:59:56Z

Date issue started with each laptop

← Older revision		Revision as of 17:59, 4 December 2019
Line 43:		Line 43:
	*STB_MedD - E5 - started Sept 2019		*STB_MedD - E5 - started Sept 2019
	**will try having Debbie send Dec 3.19 in AM to see if it works.		**will try having Debbie send Dec 3.19 in AM to see if it works.
			***Did not work.

	== 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 ==

Malcudia: /* Date issue started with each laptop */

2019-12-04T20:46:39Z

Date issue started with each laptop

← Older revision		Revision as of 15:46, 4 December 2019
Line 40:		Line 40:
	**Alana able to send Monday Dec 2.19 in AM and also at 1439 on same day. Go figure....		**Alana able to send Monday Dec 2.19 in AM and also at 1439 on same day. Go figure....
	**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.
			**Allyson worked Dec 4, got error message.
	*STB_MedD - E5 - started Sept 2019		*STB_MedD - E5 - started Sept 2019
	**will try having Debbie send Dec 3.19 in AM to see if it works.		**will try having Debbie send Dec 3.19 in AM to see if it works.

Vpenner at 20:50, 3 December 2019

2019-12-03T20:50:10Z

← Older revision		Revision as of 15:50, 3 December 2019
Line 34:		Line 34:
	*GRA_N5/S3, HSC_B3/D5, HSC_D4 - Nov 25.19		*GRA_N5/S3, HSC_B3/D5, HSC_D4 - Nov 25.19
	*GRA_N3 - started Nov 21, 2019		*GRA_N3 - started Nov 21, 2019
	*HSC_H4_h - started Nov 12.19		*HSC_H4_h - started Nov 12.19 - able to send Dec 2nd & 3rd.
	*HSC_D4 - started Nov ? not sure what date.		*HSC_D4 - started Nov ? not sure what date.
	*HSC_A4-started Nov 7.19		*HSC_A4-started Nov 7.19

TOstryzniuk: /* Date issue started with each laptop */

2019-12-03T20:37:33Z

Date issue started with each laptop

← Older revision		Revision as of 15:37, 3 December 2019
Line 26:		Line 26:

	== Date issue started with each laptop ==		== Date issue started with each laptop ==
			*STB_MICU-Dec 3, 2019 - first incident
	*STB E6 - Dec 2, 2019 - first incident		*STB E6 - Dec 2, 2019 - first incident
	*STB CICU - started Nov 27, 2019, also on and off can send or not.		*STB CICU - started Nov 27, 2019, also on and off can send or not.