Hi Denise, 

On the runtime, in order to throw this error the free memory has to be less than 0. It means that we tried to get the (max memory - the used memory) and we couldn't get that value, maybe the resources of adonix.exe or the machine were so burdened we could not get trustworthy results. This is probably not likely.

Or, when trying to allocate new memory the amount of free memory is less than the difference being requested (free < diff = true in your case according to your log).

As Regard Hulsbos - XKZero says, this can happen when we have an abnormally large object to allocate larger buffers for. The runtime will attempt to allocate new buffers (in groups) until the requested value is met or we reach a point of failure, which could mean we've reached the threshold in maxmem, or the system is literally out of resources. 

ARCHIVE.adx is part of the supervisor layer and gets baked in when web services are used. Right around the line 61 as seen in your log, of course it depends on the version of the supervisor layer you have, but on my line 61 there is a declaration of a Blbfile. So, again, I like Regard Hulsbos - XKZero's point for your situation. 

Let us know. 

Hi Denise, 

On the runtime, in order to throw this error the free memory has to be less than 0. It means that we tried to get the (max memory - the used memory) and we couldn't get that value, maybe the resources of adonix.exe or the machine were so burdened we could not get trustworthy results. This is probably not likely.

Or, when trying to allocate new memory the amount of free memory is less than the difference being requested (free < diff = true in your case according to your log).

As Regard Hulsbos - XKZero says, this can happen when we have an abnormally large object to allocate larger buffers for. The runtime will attempt to allocate new buffers (in groups) until the requested value is met or we reach a point of failure, which could mean we've reached the threshold in maxmem, or the system is literally out of resources. 

ARCHIVE.adx is part of the supervisor layer and gets baked in when web services are used. Right around the line 61 as seen in your log, of course it depends on the version of the supervisor layer you have, but on my line 61 there is a declaration of a Blbfile. So, again, I like Regard Hulsbos - XKZero's point for your situation. 

Let us know. 

Hi Bob, we bumped up the maxmem, and the issue has been resolved.  Thank you!