DISPATCH PROGRAM ERROR MESSAGES FOR DOS AND OS/2

This file lists error messages for the DISPATCH program. Messages are 
listed in alphabetical order. System messages for returned mail are 
documented in the Microsoft Mail Administrator's Guide under "System Log" 
in Appendix B, "Log Files."

For information on specifying the options correctly, see the option 
descriptions in Chapter 14, "The Dispatch Mail Program" 
of the Microsoft Mail Administrator's Guide, or in Appendix B, 
"Dispatch Options" in the Microsoft Mail Multitasking MTA 
Administrator's Guide.
             --------------------------------------

A critical error has occurred on drive <drive>.
   Dispatch cannot link to the file server using the specified drive. 
   Either the server connection has failed, the wrong drive was specified, 
   the drive is full, or there is a hardware problem.

   Check to see if the drive specified is correct. If it is, check the 
   connection to the server. If the connection is working, check to see if 
   the file server is full.

Cannot connect to drive <drive letter>.
   Dispatch cannot access the MASTER.GLB file. The cause could be a file I/O 
   error or a failed connection to the file server.

   Check the connection to the server, and try again. Check to see if the 
   correct drive letter is specified. 

Could not change to path <path>.
   Dispatch could not use the path to the postoffice you specified. Make sure 
   you specified the correct path to the postoffice, and try again.

Could not find mail system data files on drive <drive>.
   Dispatch cannot find the Mail data files for the postoffice you specified.
   
   If you did not specify a drive for the home postoffice (-H or DrivesHomePO 
   option), Mail expects the data files to be on drive M. If you 
   specified a direct drive (-D or DrivesDirect option), Mail expects 
   the data files to be on the first drive in the range of drives you 
   specify.

Drive is either used or greater than LASTDRIVE.
   The drive you specified is in use, or is a drive letter greater than the 
   drive letter specified with the MS-DOS command LASTDRIVE or drive E 
   (the default).

   Check to see if you specified the correct drive letter. If the drive is in use,
   use another drive. If the drive letter is greater the one specified or 
   defaulted to by LASTDRIVE, use the LASTDRIVE command to include the 
   drive letter. 

Dynamic connections could not be established.
   Dispatch cannot create a list of dynamic postoffices to be polled.
   These are the postoffice connections you created with the Dynamic 
   Administrator program or the connections you specified in the 
   DISPATCH.INI file or on the Dispatch command line.

   To solve this problem, increase the memory available to the Dispatch 
   program.

Error writing to log file.
   Dispatch cannot update the log file. The server connection may have failed, 
   the hard disk may be full, or the user access rights may be insufficient.

   Check to see that there is still a connection to the server. If your hard 
   disk is full, remove unwanted files or install a larger hard disk. For 
   Novell networks, check that the necessary rights to access the server 
   have been assigned.

Failure while accessing the process table.
   Dispatch cannot access the PROCESS.GLB file while another postoffice is 
   using it. If the file is locked open, Dispatch will skip to the next 
   postoffice and retry this postoffice in the next cycle.
 
   Each instance of Dispatch should have a unique combination of postoffice 
   connections; do not attempt to run more than one instance that connects 
   to the same postoffice.

File server is already logged in under another ID.
   Another user with administrator rights is currently using this file server. 
   Try again later.

Invalid option specified <option>.
   You specified an option which is not valid.

   Check the option you specified on the command line or in the .INI file 
   if you are using one. For the correct syntax, see Chapter 14, 
   "The Dispatch Program."

Mapping <drive-letter> failed.  Error code is <error-code>.
   The attempt to map this drive to the postoffice failed. Check the name and 
   the syntax for the server you specified  For the correct syntax, see 
   Chapter 14, "The Dispatch Program."

No drive is available for dynamic attaching.
   The dynamic connection (-F, DrivesUNC, or DrivesNovell option) to the 
   postoffice can not be made.    

   Check that you have available disk drives, and try again. 

Password or network name is invalid.
  The password or network name you specified is incorrect. Correct 
  any errors and try again.

<program> missed its run window.
   Dispatch was unable to run this program according to the schedule. 
   It will be run in its next scheduled window.

<program> terminated abnormally with exit code <exit-code>.
   Dispatch failed because this program failed with this exit code. 
   For common exit codes, see Chapter 14, "The Dispatch Program."

READY process <program> missed its run window.
   This process could not be run in its scheduled window. It has been 
   rescheduled to run in its next run window. Revise your schedule by 
   increasing the interval between scheduled directory synchronization 
   events to avoid scheduling conflicts.

Server is either busy or cannot be found.
   Either the server you specified is in use by another program, or you 
   specified its name incorrectly.

The -D option was used incorrectly.
   Check this option you specified on the command line. For the correct 
   syntax, see Chapter 14, "The Dispatch Program."

The connection ID table is full.
   You have exceeded the maximum of connections allowed from a workstation 
   to a server (the maximum is 8 connections to the same server). 
   Solve this problem by releasing one or more connections.

The file server table is full.
   The maximum number of connections for the file server has been reached. 
   Release one or more connections, or wait and try again later.

The -H option was used incorrectly.
   Check this option you specified on the command line. For the correct 
   syntax, see Chapter 14, "The Dispatch Program."

The -I option was used incorrectly.
   Check this option you specified on the command line. For the correct 
   syntax, see Chapter 14, "The Dispatch Program."

The -N option was used incorrectly.
   Check this option you specified on the command line. For the correct 
   syntax, see Chapter 14, "The Dispatch Program."

The share name given for a dynamic connection was invalid.
   Check share name you specified for the file server when using the 
   DrivesUNC or DrivesNovell options. For the correct syntax, see Chapter 14, 
   "The Dispatch Program."

The -T option was used incorrectly.
   Check this option you specified on the command line. For the correct 
   syntax, see Chapter 14, "The Dispatch Program."

Unable to allocate system resources for Dispatch.
   In OS/2, the keyboard thread cannot be started. If this occurs, 
   increase the value of the THREADS= statement in your 
   CONFIG.SYS file. 

Unable to find specified .INI instance; using shared instance.
   Dispatch cannot find the instance you specified with the InstanceName 
   option. Check the name you assigned the instance; for example 
   [Dispatch-Modem]. The name you specified with InstanceName must match 
   exactly with how it is specified in the INI file.
   
   Note: Dispatch continues processing using only the shared .INI 
   file entries.

Unable to free <drive-letter>, error code is <error-code>.
   The drive indicated by <drive letter> cannot be disconnected.
   To solve this problem you must manually release the drive.
   For further information about releasing drives, see your
   network documentation.

Unable to log to <filename>.
   Check the filename in the file share path. It is either incorrect or 
   could not be found. Correct the problem and try again.

Unable to map server <server-name>.
   Check the server name in the file share path. It is either incorrect 
   or could not be found. Correct the problem and try again.

Unable to open INI file for Dispatch.
   Dispatch cannot read the INI file. The server connection may have failed, 
   the file may not be located in the path expected or specified, or the user 
   access rights may be insufficient.
   
   Check to see that there is still a connection to the server. Unless you 
   specified another filename with /IniFileName=, DISPATCH expects the 
   DISPATCH.INI file to be in the INI directory of the home postoffice. 
   Check that you specified the path correctly. For a Novell network, 
   check that the necessary rights to access the server have been assigned.

Unable to open or create log file.
   Dispatch cannot update or create the log file. The server connection may 
   have failed, the path and filename may be specified incorrectly, or the 
   user access rights may be insufficient.
   
   Check to see that there is still a connection to the server. If the path 
   or filename is wrong, correct it and try again. For Novell networks, check 
   that the necessary rights to access the server have been assigned.




