Cannot Map Drive to Server Error: "8901 or 0057"

(Last modified: 13Jul2004)

This document (10067152) is provided subject to the disclaimer at the end of this document.


Novell Operating Systems

Novell Clients

Novell eDirectory

Novell Directory Services


Cannot Map Drive to Server Error: "8901 or 0057"

licenses have expired as of 23:59 12/31/01

login-4.21 15-430 the following drive root s:=.server_volume.servers.a.b.c.:\public   Error code 8901

MAP.EXE reports error 0057 trying to map a drive



8901 error indicates that there is insufficient space on the volume.

Users are not getting drive mapping when logging in

Error 8901 is reported on client when mapping drives

Page not found errors when attempting to authenticate to Remote Manager (Portal.nlm)

Authenticated connections exist (or are created) to server(s) but drives can not be mapped

Packet trace shows Request Denied - No Disk Space on Change Connection State request(s)

No errors are displayed on the server(s) console


Evaluation licenses have previously been installed and have not been formally removed.

Client License Connections has exceeded allowed licenses or License Certificate has expired.
The 8901 error is reporting a lack of Disk Space when there is lots of free space on the server's volumes. An authenticated connection to eDirectory indicates that  Directory Services is not the problem. The packet trace report of Request Denied due to lack of Disk space on the Change Connection State is a symptom of Licensing Services not providing a licensed connection to a server. In this case the 8901 error is misleading.


If there have been evaluation versions of any licenses installed into the tree, they need to be totally removed. Remove all licenses if there are any questions and then install the full real versions once the tree has been cleaned.

You need to clearly identify the reason for the license connection refusal. It could be due to exceeding allowed license connections, the License Certificate has expired or something is not working correctly with Licensing Services.

Possible Fixes:
1. Increase Licenses for user connections by adding additional licenses
2. Delete the expired License and install a valid license
3. Identify problem with licensing services and correct problem

1.  Workstation has a * next to the connection indicating it is a non-licensed connection.
2.  If you delete the license container and SN: objects and try to reinstall them through NWCONFIG you are told that the licenses have expired as of 23:59 12/31/01.
3.  Viewing the license object under the license container (SN:xxx...) displays they have expired.

In one situation after completing the above steps, Grace Logins were still occurring. It was identified that the old license was still being used by the server.

DSBRowse, ConsoleOne or iMonitor can be used to check the NLS:Licenses Used attribute for license numbers currently in use by the NCP server object. If any of these entries are the old licenses, the problem(s) will persist. Restarting the server should clear these invalid values and resolve the problem. 

An alternative to restarting the server is to delete the invalid License value on the NLS:Licenses Used attribute of the NCP server object. This can be done by:
1. Navigating to the NCP Server object in ConsoleOne
2. Selecting properties of the NCP Server object
3. Selecting the Other tab
4. Select and edit the NLS:Licenses Used attribute to delete the invalid License values

Once the incorrect License values were deleted, the server correctly found and started to use the new license resolving this problem.


Document Title: Cannot Map Drive to Server Error: "8901 or 0057"
Document ID: 10067152
Solution ID: NOVL67494
Creation Date: 01Jan2002
Modified Date: 13Jul2004
Novell Product Class:Management Products


The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.