The 24x7 service on one of my systems is constantly returning the message Low of memory! Free system rousources below 20%. The system is currently running at .4% total memory usage and 5% processor usage. Why are we getting this error? Performance monitor shows no high memory usage for the last 72 hours on that machine, even though we've been getting messages about it.

Check you have free space left on the drive holding the Windows swap file.

Also you said that you get multiple "low memeory" messages. This indicates that you have memory utilization spikes. May be some jobs take a lot of memory then quickly release it.

: The 24x7 service on one of my systems is constantly returning the message Low
: of memory! Free system rousources below 20%. The system is currently
: running at .4% total memory usage and 5% processor usage. Why are we
: getting this error? Performance monitor shows no high memory usage for the
: last 72 hours on that machine, even though we've been getting messages
: about it.

There are no 24x7 jobs running on that system at this time. Also, there are 26gb of free space ont he drive with the swap file, so I doubt that is the problem.

: Check you have free space left on the drive holding the Windows swap file.

: Also you said that you get multiple "low memeory" messages. This
: indicates that you have memory utilization spikes. May be some jobs take a
: lot of memory then quickly release it.

Something is still going on. To monitor and log memory utilization you can create an "instant on" job like the following

Dim Bytes, number
Dim MBytes, number
Dim FileNo

// loop forever
LoopWhile TRUE, END_LOOP

MemoryGetFree Bytes
// convert to Mbytes
Divide Bytes, 1048576, MBytes

// open log file
FileOpen( "c:\\memory.log", "LineMode", "Write", True, FileNo )
// write to file
FileWrite FileNo, MBytes
// close file
FileClose(FileNo)

// wait 3 seconds
Wait 3

END_LOOP:

: There are no 24x7 jobs running on that system at this time. Also, there are
: 26gb of free space ont he drive with the swap file, so I doubt that is the
: problem.