sow56091
asked on
The following drive mapping operation could not be completed.
Hi experts,
Without any (known) changes having occured at the server, at least 1 employee is unable to map to any drives, whereas yesterday he could. What is error code 8901? I read posts here on experts exchange talking about migrating from netware 5.5 to 6, but this is a 6.5 SP5 machine and it was working fine until today.
I have created new users but they all have the same error messages while trying to map drives. The supervisor account has no problems and it appears to be a security problem because this user cannot access the SYS drive when trying the \\server\share notation.
What is this problem and Is there a way to fix it without rebooting?
Sean
====================
Your current context is CONTEXT1
User: USER1 Context: CONTEXT1
Your current tree is: MYTREE
You are attached to server COMP3.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[INS S1:=COMP1\SYS:\LOGIN\NAV]
The error code was 8901.
LOGIN-LGNWNT32.DLL-740: This utility could not execute external program OSVER.
LOGIN-LGNWNT32.DLL-740: This utility could not execute external program \\COMP1\SYS\LOGIN\NAV\OSVE
LOGIN-LGNWNT32.DLL-740: This utility could not execute external program VP_Log32.
LOGIN-LGNWNT32.DLL-470: The specified drive mapping is an invalid path:
(DEL S1:)
Login script begin
Hello USER1
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[F:=\\COMP1\SYS]
The error code was 8804.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[G:=\\COMP1\USER\]
The error code was 8804.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[H:=\\COMP1\SHARE\]
The error code was 8804.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[I:=\\COMP3\SHARE2\]
The error code was 8804.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[J:=\\COMP1\APPS\]
The error code was 8804.
End login Script
Without any (known) changes having occured at the server, at least 1 employee is unable to map to any drives, whereas yesterday he could. What is error code 8901? I read posts here on experts exchange talking about migrating from netware 5.5 to 6, but this is a 6.5 SP5 machine and it was working fine until today.
I have created new users but they all have the same error messages while trying to map drives. The supervisor account has no problems and it appears to be a security problem because this user cannot access the SYS drive when trying the \\server\share notation.
What is this problem and Is there a way to fix it without rebooting?
Sean
====================
Your current context is CONTEXT1
User: USER1 Context: CONTEXT1
Your current tree is: MYTREE
You are attached to server COMP3.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[INS S1:=COMP1\SYS:\LOGIN\NAV]
The error code was 8901.
LOGIN-LGNWNT32.DLL-740: This utility could not execute external program OSVER.
LOGIN-LGNWNT32.DLL-740: This utility could not execute external program \\COMP1\SYS\LOGIN\NAV\OSVE
LOGIN-LGNWNT32.DLL-740: This utility could not execute external program VP_Log32.
LOGIN-LGNWNT32.DLL-470: The specified drive mapping is an invalid path:
(DEL S1:)
Login script begin
Hello USER1
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[F:=\\COMP1\SYS]
The error code was 8804.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[G:=\\COMP1\USER\]
The error code was 8804.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[H:=\\COMP1\SHARE\]
The error code was 8804.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[I:=\\COMP3\SHARE2\]
The error code was 8804.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[J:=\\COMP1\APPS\]
The error code was 8804.
End login Script
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It certainly does sound like a security issue. Try going into nwadmin and check each of the user's effective rights to the folder in question (alternately, you can use windows explorer and check it through the properties for each folder on a computer with a recent version of nwclient installed). If the user does not have effective rights for whatever reason (and this is entirely possible for a new account seeking access to parts of the system volume) you will have to assign the appropriate rights for the drive mapping to work.
Luckily, assigning rights does not require that the user reboot his/her computer - the rights are made available immediately. If you really don't want to reboot, you could map the drive manually at the workstation without restarting.
Luckily, assigning rights does not require that the user reboot his/her computer - the rights are made available immediately. If you really don't want to reboot, you could map the drive manually at the workstation without restarting.
ASKER
Thanks ShineOn,
In fact, it was a space issue on the server after all. Thanks for the info!
Sean
In fact, it was a space issue on the server after all. Thanks for the info!
Sean
Glad to help, Sean. Come back any time you have a question...
Beachdude67, just a "point of order" so to say - this Asker has NW6x, not NW4x. The suggestion should've at least been "Try going into C1 and check ..." and not "... nwadmin ..." ;)
Beachdude67, just a "point of order" so to say - this Asker has NW6x, not NW4x. The suggestion should've at least been "Try going into C1 and check ..." and not "... nwadmin ..." ;)
One more thing, Sean - if it was a space issue on the server, are we talking about running SYS: vol out of space? If so, that should get your highest-priority attention. SYS: must NEVER be run out of space, and if any user or queue or NDPS files are on SYS:, plan to move them to a separate volume ASAP. Also, make sure the SYS: NSS pool is NOT being shared with any other volumes - SYS: should have its own, separate NSS pool.
I had a similar error message wih error code 886f.
Found the computer name was the same as the server name.
Changed the computer name to fix the problem.
Found the computer name was the same as the server name.
Changed the computer name to fix the problem.
8804 means that the object or folder is not there, or the user does not have rights to the folder.
yes, 8804 does mean that, but the first error usually is the causative error.
If you can't access the login directory because of space problems on SYS, or licensing issues, or whatever else causes 8901, you're going to get 8804's on all the rest of the mappings.
Now, if the user had authenticated to a different server in their tree, they'd only have had problems on the COMP1 server.
If you can't access the login directory because of space problems on SYS, or licensing issues, or whatever else causes 8901, you're going to get 8804's on all the rest of the mappings.
Now, if the user had authenticated to a different server in their tree, they'd only have had problems on the COMP1 server.
Check the memberships or inherent rights, if the supervisor account is able to access, make sure the inherent rights were assigned correctly to the login directory and all the new users have at least one of the memberships necessary to be allowed to the login directory.
MAP M: = .<volume_object>.<context>
where <volume_object> is the name of your volume object and <context> is the context of the volume object. So, using one of your mappings for an example:
MAP H: = .COMP1_SHARE.CONTEXT1:\