Directory Synchronization Error and Status Messages
----------------------------------------------------------------
This file contains messages for the Import utility, IMPORT.EXE, 
and for the directory synchronization programs SRVMAIN.EXE, 
REQMAIN.EXE, and REBUILD.EXE. For each program, the messages are
listed in alphabetical order.

For messages that occur when you use Import to import a file of
local user information into a postoffice, see the file IMPORT.ERR,
which also contains messages for the LMEXT and NOVEXT utilities
you can use to extract user names from your network operating system.

The messages listed in this file are logged to the DIRSYNC.LOG
file in the LOG subdirectory of the postoffice. 

***All Programs***
Out of Memory
   Ensure that you are running the program on a computer with at least 640k 
   of memory.

***Reqmain, Srvmain, and Import
Directory Sync has not been enabled
   Ensure that your postoffice is a version 3.0 or later postoffice. If it is 
   not, upgrade to version 3.0 or later before continuing.

******************************* IMPORT **************************************

Address element is too long
   Check the import file for Microsoft Mail type addresses (PCM, PROFS, 
   SNADS and OV addresses) that have a network name (or gateway name), 
   postoffice name (or NodeID or DGN) or a mailbox name (or UserID or DEN) 
   that exceeds ten characters.


Alias already exists
   Check the import file for aliases following an Add (A) or a Modify (M) 
   code that already exists in one of the postoffice's address lists.  All 
   address lists except for the Global Address List must have unique 
   aliases.


Alias does not exist
   Check the import file lines containing Delete (D) or Modify (M) codes 
   for an alias that does exist.


Alphanumeric characters only allowed in mailbox name
   Only letters and numbers are allowed in mailbox names.


Alphanumeric characters only allowed in network name
   Only letters and numbers are allowed in network names.


Alphanumeric characters only allowed in postoffice name
   Only letters and numbers are allowed in postoffice names.


Can't find Dirsync Server postoffice definition
   Ensure that the directory server postoffice has been specified at the 
   directory server postoffice itself and at all requestors.
 

Duplicate alias in transaction queue
   Check the import file for duplicate aliases destined for the same 
   address list in lines containing Add (A) or Modify (M) codes.


Error accessing configuration information
   If this error occurs while running the Import utility, try the operation 
   again.  If the problem persists, the REQCONF.GLB 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 database file
   Ensure that there is still a connection to the server and try the 
   operation again.

   If the problem persists, the specified data 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 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.
   

Error autocreating postoffice: xxxxxx
   Ensure that the computer running the Import utility has at least 640K of 
   memory and that there is still a connection to the server.  One of the 
   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.

   You can also create the postoffice with the Administrator program 
   External-Admin Create command.


Error creating mailbag
   Ensure that the computer that is running Import has at least 640K of 
   memory.  One of the data files could be locked open, so try the 
   operation again.  Also check that there is still a connection to the 
   server.  If the problem persists, use the Administrator program to 
   create the user.


Error in physical address
   There is an error in at least one address in the import file following 
   an Add (A), Delete (D) or Modify (M) code.  The error is most likely in 
   an MCI or FAX address.  Both of these types of addresses have carriage 
   returns within the address while the import file format requires the 
   address to fit on one line.  The solution is to substitute different 
   characters for the carriage return.  For FAX addresses in the import 
   file, tildes (~) separate the four fields of the physical address.  The 
   Import utility replaces these with carriage returns before storing the 
   address in the postoffice data files.  For MCI addresses in the import 
   file, a space substitutes a carriage return-linefeed. The Import utility 
   inserts the required carriage return-linefeeds into the address before 
   storing it in the postoffice data files.


Error generating TID
   Check that the TID.GLB file exists.  If it cannot be found, it must have 
   been accidentally deleted and you should restore a back-up of your data 
   files. If TID.GLB exists, ensure that it is not locked open. Also ensure
   that the CONTROL.GLB file is not locked open. Refer to your network 
   operating system documentation to determine how to find and close files 
   that are locked open.

    
Error loading postoffice template
   Try the operation again.  If the problem persists, check that there is 
   still a connection to the server.  If the connection to the server is 
   still intact, run the Mail program and check an address information 
   window for a user in the specified network and postoffice.  If you 
   cannot see any template prompts and template information then either run 
   the import utility with a template file code (T) in the import file to 
   import the template file of the specified postoffice, or submit an 
   Import request to your directory server postoffice.  
   The response to your import request will include the template file.


Error processing resync.glb
   The Import utility is temporarily unable to generate RESYNC.GLB. Run the 
   Import utility again with the -S option to clear the problem.
 

Expecting '/' in template information line
   The import file requires a forward slash (/) to separate a template 
   prompt from template information.  The format of the line is: - 
   prompt/information.  Check the import file for at least one missing 
   prompt/information forward slash separator.


Expecting physical address
   Check the import file for lines that are missing an address.


Expecting tab or space
   Check the import file for invalid characters where there should be a tab 
   or a space.  For example, when specifying to add (A), delete (D) or 
   Modify (M) an address, there must either be spaces in columns 2 and 33, 
   or the alias must be separated from the address code (A, D or M) and the 
   address type by tabs.


FAX recipient address field too long
   Check the import file for fax addresses that are too long.  The maximum 
   length of the recipient field in a fax address is 30 characters. The 
   four fax address fields must be in the following order: recipient, 
   location, company, and phone number.  The fields are separated by tildes 
   (~).


FAX location address field too long
   Check the import file for fax addresses that are too long. The maximum 
   length of the location field in a fax address is 30 characters. The four 
   fax address fields must be in the following order: recipient, location, 
   company, and phone number.  The fields are separated by tildes (~).
     

FAX company address field too long
   Check the import file for fax addresses that are too long. The maximum 
   length of the company field in a fax address is 30 characters. The four 
   fax address fields must be in the following order: recipient, location, 
   company, and phone number.  The fields are separated by tildes (~).


FAX phone number address field too long
   Check the import file for fax addresses that are too long.  The maximum 
   length of the phone number field in a fax address is 22 characters. The 
   four fax address fields must be in the following order: recipient, 
   location, company, and phone number.  The fields are separated by tildes 
   (~).


File error sorting queue
   Try the operation again.  If the problem persists, check that there is 
   still a connection to the server.


Fullname is too long
   Check the import file for at least one alias (fullname) that exceeds 30 
   characters.


Gateway alias has no physical address
   There is no address specified for this gateway alias.  Run the 
   Administrator program and try to delete the alias.  If this is not 
   possible, either run Import as a stand-alone utility with the Replace 
   (R) code to replace the entire list for this gateway, or submit an 
   Import request to your directory server postoffice.  The response to 
   your import request will include the list for this gateway. 


Gateway not installed
   There is a directory synchronization transaction for an address type 
   that is not recognized at the postoffice.  Install the Gateway Access 
   component for this address type before trying to process this type of 
   transaction.


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


Internal sort error
   This is an internal error.  Please notify Product Support Services.

   Transactions will be processed correctly except if you are updating the 
   Postoffice Address List with the -R command line option, which requires 
   correct sorting in order to avoid missing aliases.


Invalid character in column 1
   The import file has an invalid character in column 1.

   Check the file for an invalid code in column 1.  The valid codes are A 
   (Add), D (Delete), M (Modify), R (Replace) and T (Template file).

   Also check the file for an invalid character in column 1 following the 
   line that contains the code.  Lines that follows Add, Delete or Modify 
   codes and contains specific user template information should have a dash 
   in column 1.  Lines that follow a T code and are part of a template file 
   should have a space in column 1.


Invalid character in phone number
   Check the import file for an invalid character in at least one of the 
   FAX phone number fields. Valid phone number characters are digits, the 
   space, the comma (,) and the dash (-).


Invalid transaction command
   Check the import file for an invalid code in column 1.   The valid codes 
   are A (Add), D (Delete), M (Modify), R (Replace) and T (Template file).
 

Network name already in use
   The network name of the postoffice you tried to create with the -C 
   autocreate option already exists.  Select another network name.


Network not found
   Check the import file for a network name that is not defined at this 
   postoffice. 


No fullname
   Check the import file for lines that are missing an alias (fullname).


No Server name has been set
   The requestor administrator must specify the directory server postoffice 
   before continuing.


No template defined for postoffice
   You are trying to import users with template information to a postoffice 
   that has no template defined.


No template information defined for postoffice
   The postoffice for which you are extracting addresses does not have any 
   template information.  To get the template information, run the 
   Administrator program, set Config Dir-Sync Requestor Options Templates 
   Receive to Yes and then submit an Import request to the directory server 
   postoffice by selecting Config Dir-Sync Requestor Import.

   Or, you can get the template information from the administrator of the 
   external postoffice, manually insert it into the import file and then 
   run Import to insert the information into your postoffice's data files.


Out of disk 
   There is not enough disk space to run the program.  Increase the 
   available disk space before continuing.


Out of file handles
   Ensure that the CONFIG.SYS file has FILES=20 (minimum).  If the error 
   persists, increase this number.


Possible database corruption detected
   In most cases, the problem in the data files is not serious enough to 
   prevent successful processing of transactions.  If this causes a fatal 
   error, restore a backup of your data files.


Postoffice not found
   Check the import file for a postoffice name that is not defined at this 
   postoffice. 


Prompt not found in template
   Check the import file for lines containing template information that do 
   not have a matching prompt in the template file. 


Physical address is too long
   Check the import file for an address following an Add (A), Delete (D) or 
   Modify (M) code that exceeds the size limit.  

   If this problem occurs while running the Dispatch program, try the 
   operation again.  If the problem persists, check that the MASTER.GLB 
   file is in the GLB directory.  If it is not there, it may have been 
   accidentally deleted and you should restore a backup of your data files.  
   If it is there, it may be locked open. For instructions about unlocking the 
   file, see Appendix G, "Troubleshooting" and refer to your network operating
   system documentation.


Replace option failed
   Try the operation again.  Then check that there is still a connection to 
   the server and ensure that there is enough disk space to perform the 
   operation.  If the problem persists, one of the data files may be locked 
   open.  Refer to your network operating system documentation to 
   determine how to find and close locked files.


Reserved network name
   The network name of the postoffice you tried to create with Import's -C 
   autocreate option or with the Administrator program requestor Create-PO 
   option is a reserved name.  Select another network name.
 

Resync extract can be performed only at a Directory Synchronization Server
   You can run the Import utility with the -s and -st options at the 
   directory server postoffice only.


Resync extract failed
   Try the operation again.  Then check that there is still a connection to 
   the server.  If the problem persists, one of the data files may be 
   locked open.  Refer to your network operating system documentation to
   determine how to find and close locked files.


Template file not found
   If you are running Import as a stand-alone utility, use the template 
   file (T) code in the import file to import a new template file for the 
   requestor. Otherwise, submit an Import request to the directory server 
   postoffice with the Administrator program. The response to your import 
   request will include the template file.


Template info not allowed for this address type
   Check the import file for template information specified for an address 
   that does not support templates.  The types of addresses that do not 
   support templates are: MCI, X400, SMTP, MHS, MSMAIL, and FAX.  Remove 
   any template information that appears with addresses of these types.


Template information not accessible
   Try the operation again.  If the problem persists, check that there is 
   still a connection to the server.  If the connection to the server is 
   still intact, check that the specified filename exists and is not locked 
   open, preventing Import from accessing it.  Refer to your network 
   operating system documentation to determine how to find and close files 
   that are locked open.

   If the specified filename is ADMIN.INF, copy backups of ADMIN.INF and 
   ADMIN.TPL to your data files.  If the specified filename is for an 
   external postoffice, submit an Import request to your directory server 
   postoffice.  The response to your import request will include the 
   template information.


Template memory allocation error in file
   Ensure that you are running Import on a computer with at least 640k of 
   memory.


Template mismatch error in file
   The template information in the .INF file does not match the template 
   prompts in the .TPL file.  If changes are made in one file, they must be 
   reflected in the other file.  Change the files so that they match.
 

Template option not set, template information will be ignored
   The Import utility cannot import template information.  Ensure that the 
   Dir-Sync Requestor Options Templates Receive command in the 
   Administrator program is set to Yes, or if you use Import as a stand-
   alone utility, run the utility with the -T command line option.


Unable to read network and postoffice definitions
   Ensure that the computer you are running Import on has at least 640K of 
   memory.  Try the operation again.  If the problem persists, MASTER.GLB 
   or an .XTN file may be locked open.  Refer to your network operating
   system documentation to determine how to find and close files that 
   are locked open.


Unexpected end of line in fullname
   Check the import file for a missing address and possibly a missing 
   portion of the fullname (the alias) following an Add (A), Delete (D) or 
   Modify (M) code.


Unexpected end of line in node address
   Microsoft Mail type addresses (PCM, PROFS, SNADS and OV) require a 
   network (or gateway name) and a postoffice (or a node or DGN) separated 
   by a forward slash.  Check the import file for at least one Microsoft 
   Mail type address that is not correctly specified. 


Unexpected end of line in physical address
   Microsoft Mail type addresses (PCM, PROFS, SNADS and OV) require a 
   network name (or gateway name), a postoffice name (or a NodeID or DGN), 
   and a mailbox name (or UserID or DEN) separated by forward slashes.  The 
   address is preceded by an address type and a colon (:).  Here is an 
   example of a PROFS address: PROFS:VMGATE/NODE1/USER1.  Check the import 
   file in lines containing Add (A), Delete (D) and Modify (M) codes for at 
   least one Microsoft Mail type address that is not correctly specified.


Unknown address type
   Check the import file for an invalid address. See the Server version 
   Administrator's Guide for the format of Microsoft Mail addresses and the 
   specific gateway manual for the format of foreign addresses.  


Using direct routing for autocreated postoffice
   This is an information message.  Since the Import utility is running 
   from the directory server postoffice, the new postoffice's routing will 
   be direct via an MS-DOS drive.  On any other postoffice, the autocreate 
   feature creates a new postoffice that has the same routing that the 
   current postoffice uses to reach the directory server postoffice.

****************************** SRVMAIN / REQMAIN ****************************************

Attachment is missing or is empty
   Check that the foreign requestor did not forget to send an attachment 
   with the system message.  If the requestor did send the attachment, wait 
   at least one synchronization cycle as the problem will most likely clear 
   up on its own.


Could not append transactions to the updates file
   Ensure that:
   *    There is sufficient disk space to perform the operation
   *    The computer running the Dispatch program has 640K of memory and that 
	FILES=20 (minimum) in the CONFIG.SYS file. 

   If the mail is from a foreign requestor, check that the foreign 
   requestor did not forget to send an attachment with the system message.

   If the problem persists, wait at least one synchronization cycle as the 
   problem will most likely clear up on its own.


Could not compress file
   The directory server could not backup the master update file MSTTRANS.GLB 
   or the server configuration file.  Ensure that there is still a connection 
   to the server and try the operation again.  Also check that there is 
   sufficient disk space to perform the compression.


Could not find specified sync number
   Wait at least one synchronization cycle and the problem should clear on 
   its own.   If the problem persists, copy a backup of the MSTTRANS.GLB 
   file.  Then ask all requestors to export their address lists.


Could not process requestor status report
   Ensure that there is still a connection to the server.  Also ensure that 
   there is sufficient disk space to receive the report.  Wait at least one 
   directory synchronization cycle and try the operation again.  If the 
   problem persists, contact Product Support Services.


DirSync software version out of sync
   Ensure that the directory server and all requestors have upgraded to 
   version 3.0 or later.


Failed to read the last transaction
   Wait at least one synchronization cycle and try the operation again.  If 
   the problem persists, copy a backup of the MSTTRANS.GLB file.  Then ask 
   all requestors to export their address lists.


Failure to copy attachment file
   Ensure that there is sufficient disk space at the directory server 
   postoffice to perform the operation.

   If the attachment is from a foreign requestor, check that the foreign 
   requestor did not forget to send an attachment with the system message.

   Wait at least one synchronization cycle as the problem will most likely 
   clear up on its own.


Failure to copy server updates
   Ensure that:
   *    There is still a connection to the server
   *    There is sufficient disk space to copy the updates
   *    The computer running the Dispatch program has 640K of memory and that 
	FILES=20 (minimum) in the CONFIG.SYS file

   If the problem persists, wait at least one directory synchronization 
   cycle and as the problem should clear on its own.


Failure to delete a message
   Ensure that there is still a connection to the server and try the 
   operation again.  If the problem persists, contact Product Support 
   Services.


Failure to read mail from
   Ensure that the computer running the Dispatch program has 640K of memory 
   and that FILES=20 (minimum) in the CONFIG.SYS file.  If the problem 
   persists, contact Product Support Services.


Failure to send mail to
   Ensure that there is still a connection to the server.  Also ensure that 
   there is sufficient disk space to receive the mail.  Wait at least one 
   directory synchronization cycle and try the operation again.  If the 
   problem persists, contact Product Support Services.


Failure to send update mail to requestor
   Ensure that:
   *    There is still a connection to the server
   *    That there is sufficient disk space to receive the mail
   *    The computer running the Dispatch program has 640K of memory and that 
	FILES=20 (minimum) in the CONFIG.SYS file

   If the problem persists, wait at least one directory synchronization 
   cycle and as the problem should clear on its own.


Failure to transmit server updates
   Ensure that:
   *    There is still a connection to the server
   *    There is sufficient disk space to receive the updates
   *    The computer running the Dispatch program has 640K of memory and that 
	FILES=20 (minimum) in the CONFIG.SYS file

   If the problem persists, wait at least one directory synchronization 
   cycle and as the problem should clear on its own.


Invalid DirSync password from
   The specified password in the directory synchronization system message 
   does not match the password in that is registered with the directory 
   server postoffice.  The directory server administrator and the requestor 
   administrator should determine which is the correct password.


Invalid DirSync profile from
   The directory server received a directory synchronization message with 
   unknown TASK= values.  The mail likely has a TASK= value that is not
   supported by the server.  See [133].  This message is redirected to 
   the directory server administrator who should notify the foreign 
   requestor administrator of the problem.


Invalid Server Request
   Ensure that the directory server's requestor schedule does not have any 
   errors.  Check the requestor schedule.  Ensure that there is enough
   time for the server mail to reach the requestor post office.


Invalid transaction format
   Ensure that there is sufficient disk space to perform the operation. 

   If the requestor is a foreign requestor, ensure that:
   *    The system message is in the correct format and starts with [dirsync]
   *    The foreign requestor did not forget to include an attachment file if 
	one was specified
   *    If there is an attachment file, it is in the correct format and 
	starts with [dirsync-transactions]

   Wait at least one synchronization cycle and the problem should clear 
   itself up.


Manual import required for
   The size of the message generated to send the directory synchronization 
   updates to the specified requestor exceeds the limit set by the 
   requestor.  A manual import procedure as described in The 
   Administrator's Guide is required.


Non-delivery report from
   This is an information message.  The requestor received a directory 
   synchronization message that is not addressed to it and is not from a 
   $SYSTEM (directory synchronization) mailbox. This message is put in the 
   DIRSYNC.LOG file.

   The directory server may receive a directory synchronization message 
   that is not addressed to a $SYSTEM mailbox. This message is redirected 
   to the administrator.

   If the requestor is a foreign requestor, ensure that the directory 
   synchronization message is addressed to $SYSTEM.


Number of missing transactions=nnn (aaa -> bbb)
   This message appears with message #138 ("Server sync does not exist). 
   This indicates the number and the range of transactions that are missing
   in the master update file.


Requestor configuration busy
   Try the operation again.  If the problem persists, the REQCONF.GLB may 
   be locked open. Refer to your network operating system documentation 
   to determine how to find and close files that are locked open.


Requestor not registered
   The specified requestor is not registered with the directory server 
   postoffice.  Instruct the requestor administrator to register with the 
   Administrator program Config Dir-Sync Requestor Registration command.  
   The directory server administrator should also create the requestor with 
   the Administrator program Config Dir-Sync Requestors Create command.


Server configuration busy
   Try the operation again.  If the problem persists, the SRVCONF.GLB may 
   be locked open. Refer to your network operating system documentation
   to determine how to find and close files that are locked open.


Server sync does not exist anymore (nnnn)
   The indicated transaction number could not be found in the master update 
   file MSTTRANS.GLB.  


The local requestor is not registered
   Ensure that this postoffice is registered as the directory server with 
   the Administrator program Config Dir-Sync Options command.

   *If this is a warning message then some update transactions
   will be missing.  This Requestor should submit an Import request.

   *If this is a fatal message then the Server PO has been restored.
   All Requestor must Export their addresses to the Server.


Transaction limit reached
   The size of the message generated to send the directory synchronization 
   updates to the specified requestor exceeds the limit set by the 
   requestor.  A manual import procedure as described in The 
   Administrator's Guide is required.
 

****************************** REBUILD *****************************************

Gal Rebuild out of disk space
   The Rebuild utility needs extra temporary disk space during sort and 
   merge operations.  Ensure that there is sufficient disk space to perform 
   the operation.


GAL Rebuild problem accessing files
   Ensure that:
   *     There is sufficient disk space to perform the operation
   *     The computer running the Rebuild utility has 640K of memory and that 
	 FILES=20 (minimum) in the CONFIG.SYS file
   *     Novell users have sufficient access rights


No Valid Postoffice found.
   Try the operation again.  If the problem persists, check for that the 
   MASTER.GLB file is in the GLB directory.  If it is not there, it may 
   have been accidentally deleted and you should restore a backup of your 
   data files.  If it is there, it may be locked open. Refer to your network 
   operating system documentation to determine how to find and close files 
   that are locked open.


Not enough free file handles.
   Ensure that the computer running the Rebuild utility has 640K of memory 
   and that FILES=20 (minimum) in the CONFIG.SYS file.


Warning .USR file missing.
   This is an information message.  There is a postoffice without a list of 
   users.


