Import Program Messages -- Local User Import Only.
LAN Manager and Novell Extract Utility Messages
----------------------------------------------------

This file lists messages that occur when you use the Microsoft Mail Import
utility, IMPORT.EXE, to import a file of local user information into a 
postoffice. For messages that occur when you use Import to import external
postoffice and foreign addresses, and during directory synchronization,
see the file DIRSYNC.ERR.

This file also lists messages for the LAN Manager and Novell Extract utilities,
LMEXT.EXE and NOVEXT.EXE. 


Local User Import Messages
--------------------------
                          
Access tokens ignored for admin user:
   You do not need to specify access privileges for administrators with the 
   &access= user profile component; an administrator is automatically 
   assigned all privileges.


Cannot modify local user to external:
   You cannot import a local user into another postoffice or gateway by 
   modifying the mailbox, network, or postoffice name of a local user.


Error accessing input file
   Try the operation again.  If the problem persists, check that there is 
   still a connection to the server.

   Check for someone editing the Import utility input file (specified with 
   -F command line option).  If the problem persists, the file may be 
   locked open. Refer to your network operating system documentation to 
   determine how to find and close files that are locked open.


Error accessing output file
   Try the operation again.  If the problem persists, check that there is 
   still a connection to the server.

   If the problem persists, the Import utility output file (specified with 
   the -F or -X command line option) may be locked open.  
   Refer to your network operating system documentation to determine how to 
   find and close files that are locked open.
   

Input file is corrupt or has incorrect format.
   Check the import file for any lines that are not in the correct format.


Invalid local user token:
   An incorrect entry exists in the import file for one of the local user 
   profile components. The following are allowed: 
   &password=
   &usertype=
   &access=
   &folders=
   &dirync=


Invalid local user token value:
   The value for the &usertype= user profile component must be either ADMIN 
   or USER. 


Invalid token assignment:
   User profile information must be preceded by an & and followed by an
   = sign. For example: &usertype=admin.
   You cannot enter: &usertype


No mailbox name.
   The Import program requires an administrator mailbox name.


Local user information not allowed for this address type.
   You can only import Microsoft Mail users with the address type PCM when 
   you include local user profile information after the `&' in column 1.


Maximum number of local users has been reached.
   The number of users at the postoffice exceeds the 500-user limit.


Reserved network name.
   The network name that has been entered is a name that is reserved for a 
   Microsoft Mail gateway or add-on module: MCI, X400, EASYLINK, GTE, DISOSS,
   ENVOY, COMPUSERVE, SOURCE, ATTMAIL, SMTP, MHS, FAX. Enter another network 
   name.


The database is locked by another process.
   Data files that Import needs to write to in the data files directory are 
   locked open. Ensure that there is still a connection to the server and try 
   the operation again.

   If the problem persists, data files may be locked open. Refer to your 
   network operating system documentation to determine how to find and 
   close files that are locked open.


Truncating password to 8 characters.
   You cannot enter a local user password longer than eight characters.


Unable to create local user.
   The Import program cannot access one of the files it needs to create the 
   user or has insufficient memory to process the file of user information. 


Unable to delete local user.
   The Import program cannot access one of the files it needs to delete the 
   user or has insufficient memory to process the file of user information. 



Extract Utility Messages
------------------------

This section lists messages for LMEXT.EXE first, followed by messages for
NOVEXT.EXE.


LAN Manager Extract Utility Messages
------------------------------------

Additional data is available but could not be retrieved.
   Not enough memory was available to retrive all the names that the UAS 
   could supply. 


The network path was not found.
   The LMEXT.EXE program could not find or could not access the named server.  
   Check that this is a valid server that you can access by using the LAN 
   Manager NET VIEW command.


The network request is not supported.
   The named server does not support the requested UAS service. Ensure that
   the server is using user level security and that the UAS service is 
   started.


The workstation service is not started.
   You tried to run LMEXT.EXE on a machine at which the LAN Manager 
   Workstation service has not been started. Start the workstation service 
   first.

  
The process was unable to complete.
   Ensure that there is a connection to the server and that the command line 
   parameters are entered correctly and retry the operation.


Novell Extract Utility Messages
-------------------------------

Failed to access output file.
   The program could not access the specified output file. Check that the 
   filename is a valid MS-DOS filename, and that there is sufficient disk 
   space available (about 1K ought to be enough). Also make sure the 
   specified file is not read-only.


The process was unable to access the Netware server.
   This error occurs if you run the program when you are not attached
   to a NetWare server.


The process encountered an error while accessing the Netware Bindery
   This error occurs if the process was unable to extract the user names from 
   the Bindery. Ensure that you are attached to the NetWare server and that
   you are logged in as Supervisor. 


The workstation is not attached to the Netware server.
   Use the ATTACH command to attach the workstation to a Netware server, 
   then start the utility again.


The workstation must be logged on to the Netware server.
   Log on to the Netware server, then start the utility again.
