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.
111: Execution Error - Encrypted/Encoded verification failed
Keywords: 111: Execution Error - Encrypted/Encoded verification failed
Question:
Hello, I have a very interesting problem. This problem only seems to happen with Windows 98 machines so I am curious if there is something different about it (versus Win95).I have a compiled winbatch that I use to control Microsoft Outlook 98. I named it OUTLOOK.EXE and renamed Microsoft's to OL98.EXE (this was the only way I could get roving clients to work for us). Everything was tested and worked fine on Windows 95. Even under NT, the winbatch works fine.
However, under Windows 98 every so often (not reproducable, and not often) the winbatch gets corrupted and throws up this error:
--------------------------------------------- 111: Execution Error Encrypted/Encoded verification failed. If you are CALL'ing a WBT from a compiled program, you must encode the WBT using the compiler's Encode option. WinBatch 32 98D WIL Version: 2.6dbr ---------------------------------------------It happens on various machines and everytime it happens, the "corrupted" winbatch is exactly the same as all the other "corrupted" ones (I did a binary compare). The "corrupted" versions also have the same file properties (except size) I compiled into the original, so I know it is the same EXE. At first I thought a virus was the problem, but that is not the case. Have you run into this problem?
PS. I use the same version of Outlook on the Win98 machines as I use on the Win95 machines.
Answer:
Does it happen before the script runs, or during execution of the script after it has managed to start?- Before the scipt runs.
If it is running off a network drive, then this error usually indicates a network card beginning to have problems.
If the problem is limited to one machine, then I would try replacing the network card in that machine.
If it happens in a small batch of machines I would try to understand the network topology between the server and the affected machines and see if they share any equipment in common. Hubs, switches, etc.
One test is to copy a BIG file to the server from an affected machine then copy it back. Then compare the original and copied files to see if there are any changes.
- If you were doing a CALL to a WBC file, make sure the WBC file was compiled with the same version of the compiler and the calling EXE.
Article ID: W12938
Filename: 111 Encrypt Encode Verification Error.txt
File Created: 1999:04:15:16:50:40
Last Updated: 1999:04:15:16:50:40