Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Error Codes
- !! 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.
DrWatson Error WBDDB32I!WinEnumXXXIcon
Keywords: Crash Dr Watson DrWatson Error GPF WBDDB32I!WinEnumXXXIcon
Question:
Hi - I have an issue with a winbatch script our company has been using for a few years. The file is a compiled exe script. The script is accessed by about 100 users and only recently it has started to crash on about 5 users or so."xxx.exe has encountered a problem and needs to close. We are sorry for the inconvenience" the application is crashing with wbddb34i.dll.This is the DRWatson Report:
The application (xxx.exe) generated an application error. The error occurred (date/time). The exception generated was c00000005 at address 1c041f43 (WBDDB32I!WinEnumXXXIcon)The script itself is extremely simple - It reads a text file, gets the computer name and launches the webbrowser. And once again, this has worked without error for many years.
Answer:
Your Dr. Watson dump shows enough detail to conclude that WinBatch is failing in one of the internal functions called by the implementation of the WinBatch 'Wallpaper' function. If your script is not actually calling the 'Wallpaper' function then the CPU's program counter is being corrupted by a problem someplace else in WinBatch process memory. Often but not always, the cause of program counter corruption is stack corruption. Program counter corruption caused by stack corrupt can sometime appear random and be difficult to track to the root cause even with the aid of debugging tools and a memory dump. This means that the problem can be very hard to diagnose from long distance.The Dr. Watson information you posted also indicates that your script was compiled with a version of WinBatch that is at least 10 years old. We don't have the same kind debugging information for older version that we now have for newer version of WinBatch executable images. This further reduces the chances of discovering the root cause of your problem.
Your best hope is to attempt to eliminate the problem at the script level with the newest version of the WinBatch+Compiler, assuming you have access to the original uncompiled script. You can renew your software here: http://renewal.winbatch.com.
IMPORTANT: If you still have a problem with your script using the latest version of the software we can help you address the problem immediately.
Article ID: W17866
Filename: DrWatson Error WBDDB32I!WinEnumXXXIcon.txt
File Created: 2011:04:15:14:15:32
Last Updated: 2011:04:15:14:15:32