Database Search
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.
Application Error with WinBatch and Wise
Keywords: Crash GPF application error exit close script exe
Question:
After installing Wise Package Studio 3.0, I am consistantly getting an application error that occurs at the end of every Winbatch compiled EXE launched. Also, if I create a .WBT file on an affected PC, the error occurs at the end of that script as well. Again, scripts seem to run flawlessly up to the exit, then display an application error. The problems seem to occur on NT 4.0 and 2000, but not on Windows 95.I have attempted to install Winbatch on a 'clean' machine. - WinBatch runs fine I then install WISE (which doesn't even prompt for a reboot) - WinBatch runs fine. I reboot the machine - WinBatch now gets the application error on exit.
I have spoken with WISE support and they seem to indicate it's not their problem, because in only seems to affect WinBatch and I should contact you.
What is your exit processing doing that might cause the problem?
Answer:
Sounds like the classic 'passing of the buck'. We are not really doing anything unusual upon exit. It sounds like from your message that WISE is installing something after the reboot that maybe causing the issue. It would be interesting to find out from them, what their install is doing at the reboot. Installing any files?User Reply
I figured it out. I built a fresh install of NT4 Sp6 and verified that WinBatch was working, then I just started the WISE install and waited for it to prompt me to install a runtime component (MSI 2.0 from Microsoft) and clicked "Cancel". This stopped the installation cold. I was running a setup discovery tool in the background to detect any changes that the install made to my PC and it only found a single registry entry and a single new dll called setuphook.dll, under c:\winnt\system32.the registry entry made was:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows[AppInit_DLLs]="setuphook.dll"I rebooted and Winbatch started to die again.
I was on the phone with WISE at the time and the guy in their prime support group had no idea what the DLL was for (even though the properties of the file referenced WISE) or why it would cause a problem, but he said there are two solutions: delete the file or blank out the data of the registry value that was modified (it's bad form to simply delete it, apparently). I tried both and both worked. He said that one of their developers noted the problem on his own PC with some other 3rd party app and deleted the DLL and all of his WISE products still work, so their happy giving me that work around for now.
To reproduce the problem on any NT4 or Win2k machine, drop the setuphook.dll in c:\winnt\system32 and update the registry with the value above and reboot. Violla, broken WinBatch! You should probably create a KB article for others who may use WISE products and unwittingly damage their system.
Article ID: W15142
File Created: 2002:09:05:13:49:58
Last Updated: 2002:09:05:13:49:58