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.
Error 145: Map Attempted. No Network Resource.
Keywords: error 145 cannot access net resource
Question:
I'm using the function n3MapDir, and am getting the error 145, cannot access net resource error message.My syntax is:
n3MapDir("\\OPERATION_2\SYS\APPS\PROFILE\","J:\")
Further investigation has revealed that if I run the script from the "network" copy of
Windows I get the error of "136: Invalid driver number" or "145: Cannot map to the resource".
Originally I was on my "C:" drive copy of Windows and things were working just fine. It was after rebooting and logging in to the network that I began having these troubles. I have again tested by going back to my C: drive copy of Windows 3.11 and the script works like a charm.
So what would let the script work if Windows is on C: vs Windows on F:? I will now investigate SYSTEM.INI and WIN.INI settings but do you know of anything such as DLLs and such that could affect this?
Resolution:
Usually I get an error from Netware when the driver loads (when using NETX and trying to load the Netware driver for VLM). This time I didn't.After comparing two SYSTEM.INI files, (one that worked and one that didn't) and switching out different things, I found that although I was using VLMs, the NETWARE.DRV from Windows was in use when using IPX/NETX.
Error 145 with Compiled EXE and Not WBT:
- When you get the error: "145: Map Attempted. Cannot access net resource,"
and the script works fine as WBT, but not as compiled EXE:
Check the Netware extender DLL .EXT (or .DAT in older versions) file in the \WINBATCH\SYSTEM\ directory and make sure that:
- There's only one Netware DLL listed, and that
- Both the compiler and the WinBatch script are looking at this same DLL.
- There's only one Netware DLL listed, and that
- If you're getting this error on both the Compiled and Uncompiled WinBatch script,
the problem might be that the net resource access rights are not set with permissions
that allow you to map to that area.
For example, in the following code:
n3map("\\SERVER\VOLUME\DIRPATH", "K:")you could get this error if the DIRPATH share rights were not set to let your users map to that area.Make sure you can map to that area manually (outside of WinBatch) and see if you're also having problems. If so, the problem is with your Novell access rights permissions on that resource.
Article ID: W12944
Filename: 145 Map Attempted - Cannot access net resource.txt
File Created: 2001:03:01:11:40:46
Last Updated: 2001:03:01:11:40:46