Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

• !! Complete List Of WIL Errors !!
• !!Windows System Errors!!
• 1003 FileMove failed
• 1009 FileCopy FROM File Open Failed
• 1015 FileRename Failed
• 1016 FileDelete File Not Found
• 1022 waituntil passed time not in proper format
• 1028 Log Disk DirRemove Error
• 1029 DirMake Dir not created
• 1034 Clipboard Owned by Another Application
• 1036 Clipboard error
• 1077 File Open Failed
• 111 Encrypt Encode Verification Error
• 1129 OLE Initiate Failed Error
• 1207 snapshot out of memory
• 1300 DLL file not loadable
• 1330 When Compiling
• 1395 AddExtender Not a valid Extender
• 1422 DirAttrSet Directory not Found or Access Denied
• 145 Map Attempted - Cannot access net resource
• 1470 DiskInfo Function Failed
• 1478 BinaryHash BinarySort
• 1526 RegLoad-UnloadHive Access Denied
• 1588 Unable to Allocate or Lock Memory
• 1590 FileDelete Failed
• 1900 error level list
• 1905 winexec 5 Attempt to Dynlink to a Task
• 1915 winexec 15 error
• 1932 WinExec Errors
• 2001G Could not locate
• 3052 Unitialized Variable or Undefined Function
• 3067 Error when Installing
• 3074 Expression continues past expected end
• 3088 FileRead Error - Attempt to Read Past EOF
• 3096 Out of memory for strings
• 3101 Substituted Line Too Long (greater than 256 chars)
• 3132 OLE Error
• 3338 FP Math Illegal Floating Point Numbers
• 3357 Endif Match Not Found
• 3397 List Itemization - Could not allocate global buffer
• 3437 Extender Load Failed. Make sure 16 32 bit matches
• 499 Unrecognized Network Error
• 9000 Level Errors
• Application Error with WinBatch and Wise
• Batch DLL Initialization Error
• Call Error when Launching WB from another App
• Cannot Access File Error
• Cannot locate entrypoint SetHandleContext in kernel32
• Could not Allocate (or lock) Work Buffer
• DLL Initialization Err - INETMIB1 DLL
• DrWatson Error WBDDB32I!WinEnumXXXIcon
• Error 1004 FileMove FROM file open failed
• Error 1299 DLL Dll file not found
• Error 3353 Structure Too Complex Recursive UDF
• Error 3353 Structure Too Complex
• Error 998 on Banyan Vines Network Drive
• Errors 9012 and 9015
• Execution Error 111 Line too Long - Greater than 256 Char
• FileDelete and Access Denied
• FileRead Error 1591
• FileRename 1025 Error
• General Protection and Invalid Page Fault Errors
• How do I trap errors
• How to Check Exit Status Code of Program
• How to Suppress Error Displays
• How to trap error 3033 GoTo label not found
• Ignore Error and Return From Called Script
• IntControl 73 Not Capturing Error
• Internal Dynalloc Tag Overwrite Error
• Percent Sign in Comment
• RunWait Failing Segment Load Failure
• RunWithLogon 1932 All Pipe Instances are Busy
• SNMPAPI Dll Problems
• Trapping Win32 Network Extender Errors
• User Defined WB Error
• WBERRORHANDLEROFFSET
• Win95 Error upon Exit from Logon Script
• Windows 98 Error Codes
• Write Variable Table To File Upon Error

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

3397: List Itemization: Could not allocate global buffer

Keywords: 	 3397: List Itemization: Could not allocate global buffer

---

Question:

I wrote a program which keeps on running and writes some information to a log file. Searching the right log file, I use the function FileItemize.

However sometimes (not everytime the function is executed) the program terminates with the error: 3397: List Itemization: Could not allocate global buffer

This error seems strange to me because it only happens a few times a day. I thought about some memory problem, so I dropped the variable containing the results of the FileItemize function. However the error still exists.

Is there anyone who can tell me what is going on and what is meant by the "global buffer"?

More Info: I use the FileItemize function to see all the logfiles in a directory. The size of each log file is limited to 10MB, the number of logfiles in the directory is growing each time. However at this moment, 10-20 files are located in the directory.

If the Winbatch program is restarted, the FileItemize function does not give an error anymore. Only after a few hours of running the "Could not allocate global buffer" error occurs. The Winbatch program should be running in loop for ever. Might this be a problem?

Answer:

This tends to indicate that WinBatch cannot grab any memory for working with. This can be caused by a memory leak in either Winbatch itself or in your script.

Currently I suspect your script? How big is it? Does it allocate any Binary Buffers or arrays?

The general technique here is:

1. Find a script that will crash eventually.
2. Comment out some code that seems irrelevent to the crash. Test again.
3. If it still crashes, comment out more code. If it did not crash put the code back in and comment out different code.
4. Try to boil the problem down to a minimal test case that illustrates the problem with only a few lines of code.

Question (cont'd):

My script is about 640 lines and uses 3 arrays. However because the script is running in a loop the function, allocating the arrays, is called different times.

Variables declared in a function, will they be de-alocated automatically by Winbatch or should I do an manual drop? Should I try dropping the variable arrays?

For now I will use your workaround, exiting the script on an error. The script is restarted automatically, using the winNT schedule service.

Answer:

It *should be* automatic.

Drops should not be required.

---

Article ID:   W14845

File Created: 2001:11:08:12:40:20

Last Updated: 2001:11:08:12:40:20