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.
RunWithLogon 1932 All Pipe Instances are Busy
Question:
OK, I know this is obvious, but I'll ask anyway.I am "occassionally" getting the following error during a script that runs at user's login script each time they login.
"1932:All Pipe Instances are Busy"
I know this is a Windows API call, and probably means the network traffice is heavy, OR, the specified USER ID is in use. But I was hoping for a clerification on this, if you have one.
(not sure if we have another process running at the same time with RunWithLogon .. possibility - would that cause problems?)
Answer:
Yes, you can only have one client at a time accessing the RunAs service. That would include RunWithLogon, as well as any other processes you had that were performing a similar RunAs operation.Article ID: W16441
File Created: 2005:02:18:12:20:36
Last Updated: 2005:02:18:12:20:36