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
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Also, just to note, it's not recommended to use UNC paths for drive mappings in login scripts. The recommended drive mapping notation is:
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:\
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.
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.
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.
Business Accounts
Answer for Membership
by: ShineOnPosted on 2005-11-03 at 12:16:22ID: 15220009
8901 is kind of a generic error that is technically reporting lack of sufficient disk space. That's not literally true in most cases, and often means you have a licensing issue.
I see you have at least 3 servers (COMP1, COMP2 and COMP3) and the user is loggin in to COMP3 and then getting failures mapping.
What I have found to be the case in the past is:
1) The Admin made the mistake of associating user licenses with specific servers, and the user couldn't obtain a license
or
2) there's a problem with SLP configuration and the user is logging into a non-DA server and so not getting at the appropriate services to log in properly
8804 errors also tend to be indicative of the same things, even though technically they are reporting a problem with volume objects. I would recommend not redoing your volume objects until you've eliminated the two things I mentioned.