"Out of Memory" Errors in AGRIS (Basic 7 or 2147024882 Errors)

These errors generally refer to the operating system not having enough available memory to process requests. Below are a few ideas to keep in mind when troubleshooting these kinds of errors.

How much RAM is installed on the database server? Please refer to the AGRIS System Requirements document that is appropriate for your current installation of AGRIS to ensure that enough memory is available for the operating system and the Pervasive database engines.
Ensure that the /3GB switch in the boot.ini file is not present. Pervasive generally recommends not using this switch as it may adversely impact performance by decreasing the amount of RAM available for the operating system. On the other hand, the /PAE switch can normally be used without negatively impacting performance.
Is a page file available for the operating system in the event that physical memory is becomes scarce? It is highly recommended to use a page file for systems that do not have enough physical RAM to satisfy all of the memory-related requests that the system is expected to perform.

Below are examples of these kinds of errors:

    BASIC #-2147024882 (AeUI:clsForm:InitializeForm)
    Out of memory
    SysSupport:bSysMenu:Main, SysDsMgr:clsDatasetMgr:SelectDataset, AeUI:clsAeUI:AeSaveScreenAeUI:clsFrmMgr:CreateForm, AeUI:clsForm:InitializeForm

    BASIC #7 (SysSupport:bSysMenu:LoadToolBar)
    Out of memory
    SysSupport:bSysMenu:Main, SysSupport:bSysMenu:MenuSetup, SysSupport:bSysMenu:LoadToolBar

Comments

'Out of memory' errors are most typically due to COM+ attempting to use more than 2GB of virtual memory regardless of how much RAM/page file size is available on the server. Be sure that Pervasive PSQL is 10.31 or 11.20 or higher and a version that we support. Also, if using COM-intensive processes such as iView or AgLogic CFT, then please contact TAC to see if script files may reduce or eliminate 'out of memory' errors.
"Basic 2147024882: Exception of type 'System.OutOfMemoryException' was thrown." Had this issue recently on a single client machine when invoicing or reprinting. All other client machines were fine. We had to repair the install of AGRIS on that machine to get around it.
This is an error observed recently when AGRIS_ABS was known to be in an out of memory state: ERROR Occurred In AeData BASIC #91 (AeData:clsAeData:AeGetDBName) Object variable or With block variable not set AGRIS_ABS attempting to exceed a virtual size greater than 2GB is the cause of many out of memory situations in AGRIS, especially when the server is returning the error, but had a large amount of physical memory still available.