<> LISTQ.EXE ========= The Listq utility (LISTQ.EXE) shows the three Dir-Sync queue files (SRVTRANS.GLB, REQTRANS.GLB, and MSTTRANS.GLB). Examine these files to see the effects of adding users, to monitor the inclusion of names, and to pinpoint problems with the queue files. Syntax ------ listq -d -v [-q] Where: -d Is the postoffice drive. -v Indicates verbose mode. -q Is only needed when viewing the MSTTRANS.GLB file. file Is either REQTRANS.GLB, SRVTRANS.GLB, or MSTTRANS.GLB. Example ------- All of the files have similar formats. They show the last sync number sent followed by either transactions or a status report. The following is a typical MSTTRANS.GLB file display showing how template information is used by Dir-Sync. Microsoft (R) Transaction File List Utility. V3.0.4000 Copyright 1991-1992 Microsoft Corporation. All rights reserved. m:glb\MSTTRANS.glb Item Sync No. Transaction ------ ---------- ----------------------------------------------- 1 0000000011 R PCM:NET3/PO5 2 0000000012 T PCM:NET3/PO5 Field_1:~0~20~A~~ Field_2:~0~20~A~~ 3 0000000013 A RalphPCM:NET3/PO5/Ralph - Field_1:/Dogfood - Field_2:/Chow 4 0000000014 A RogerPCM:NET3/PO5/Roger - Field_1:/Woof - Field_2:/BowWow 5 0000000015 A X1PCM:NET3/PO5/X1 - Field_1:/X1 - Field_2:/X1 6 0000000016 R PCM:NET2/PO3 7 0000000017 T PCM:NET2/PO3 Field_1:~0~20~A~~ Field_2:~0~20~A~~ 8 0000000018 A User 1PCM:NET2/PO3/User1 - Field_1:/Mar - Field_2:/Dee't End of Queue The various fields in the MSTTRANS.GLB, REQTRANS.GLB, and SRVTRANS.GLB files are: Field Description ------------------------------------------------------------------ Item Is an internal counter for the number of records in the MSTTRANS.GLB file. Sync No. Is the record number Dir-Sync uses to determine which updates are required by each requestor. All records in the MSTTRANS.GLB file that have sync numbers greater than the sync number recorded in the SRVCONF.GLB file are sent back to the requestor. The SRVCONF.GLB file is updated to reflect the new requestor sync number. In this way, only updates are sent, keeping the total volume of Dir-Sync messages to a minimum. Transaction Is the type of modification for the address. This is in standard input file format, as described in the "The Import Utility" section of the "Microsoft Mail Administrator's Guide," version 3.0. TROUBLESHOOTING DIR-SYNC ======================== Problem 1: The GAL on a Postoffice Does Not Have All Other Postoffice Address Lists ------------------------------------------- When updates are not being added to the GAL, the network administrator must troubleshoot the Dir-Sync process to determine where the problem lies. Follow the troubleshooting guidelines below to quickly isolate the problem. 1. Verify no problems exist with the general Dir-Sync process Open the Administrator accounts on the server postoffice and the requestor postoffices to see if any error messages have been sent to the administrator. If an error message stating "requestor not registered" is present, verify that the server is registered with the requestor and vice versa. Other error messages may indicate a temporary condition that will be corrected by continuing with these troubleshooting steps. Enable logging of Dir-Sync if this is not done already. Examine CENTRAL.LOG and DIRSYNC.LOG for the status of Dir-Sync on all the requestor postoffices. Verify that each postoffice is participating in Dir-Sync, that updates are being sent and received, and that the GAL is being rebuilt. If these steps are not occurring on a postoffice, verify that Dispatch can reach postoffice and that the External Mail program or MTA can deliver mail to it from the server postoffice. Examine the DISPATCH.LOG file to verify that NSDA -RT and NSDA -RR complete successfully on the requestors and that NSDA -S completes successfully on the server. Verify that the time for the requestor's NSDA -RT is before the server's NSDA -S, and that the requestor's NSDA -RR is after the server's NSDA -S. Be sure to allow time for the External Mail program or MTA to transfer the Dir- Sync messages between the requestors and the server. Determine which postoffices do not have the full GAL: a. If a single requestor postoffice does not have all other postoffice address lists, run the Administrator program on that postoffice and select Config, Dir-Sync, Requestor, Import to get the server to send down the complete list of addresses. b. If the server does not have the complete address list, determine which requestor postoffice is not in the server's list. From the Administrator program on that requestor postoffice, select Config, Dir-Sync, Requestor, Export to send the address list to the server. c. If all other postoffices don't have a single postoffice's address list, run the Administrator program on the missing postoffice and select Config, Dir-Sync, Requestor, Export to send the address list to the Dir-Sync server. Wait for Dispatch to execute the Dir-Sync cycle. If this does not clear the problem, the sync numbers may be invalid. 2. Reset the requestor sync numbers To reset the sync numbers on the requestor postoffices, generate the RESYNC.GLB file. On the server postoffice, run: import admin -p -s -d This will create a file in the server postoffice's GLB directory called RESYNC.GLB. Copy this file to the postoffices that do not have the full GAL, and delete them from the server postoffice. On the requestor postoffices that have the RESYNC.GLB file, run: import admin -p -q -y -d rebuild -f -d Import looks for the RESYNC.GLB file and processes it before any other Dir-Sync mail. The RESYNC.GLB file contains new sync numbers for the requestor that reflect what the server has recorded in SRVCONF.GLB. This will clear any sync number conflicts. Wait for the Dispatch program to execute the Dir-Sync cycle. In extreme cases, the server's SRVCONF.GLB file or the requestor's REQTRANS.GLB file may be corrupt, so generating a resync file will not correct the problem. For this case it is necessary to reset the Dir-Sync files. 3. Reset the Dir-Sync Files For a single requestor postoffice without a complete GAL, perform a local reset. On the server: a. Delete the requestor record. From the Administrator program select Config, Dir-Sync, Server, Requestors, Delete, and select the requestor postoffice. b. Re-create the same requestor postoffice. This will reset that postoffice's record in the SRVCONF.GLB file. On the requestor: c. Reset the REQCONF.GLB file by running the following command: listds -dm -r -z net po [] d. Verify that the REQCONF.GLB file is reset by running the following command: listds -dm -r The Dir-Sync server entry will be blank if the REQCONF.GLB file is correctly reset. If not, repeat this step. This step is not necessary if you use a dummy REQCONF.GLB file. e. Set the REQTRANS.GLB file to zero bytes. For example, assuming the requestor postoffice is on drive N, run the following command: type aaa > n:\glb\reqtrans.glb This command will return the error "File not found - AAA." This error message is expected; the REQTRANS.GLB file will be zeroed (set to zero bytes). f. From the Administrator program, select Config, Dir-Sync, Requestor, Registration. Enter the network and postoffice name for the Dir-Sync server. If the server name is already listed, the REQCONF.GLB file was not reset correctly. Repeat steps c and continue with step f. g. Reset the types of names propagated by Dir-Sync by selecting Config, Dir-Sync, Requestor, Types. This is only necessary if gateways are installed and gateway names are included in Dir- Sync. h. Select Config, Dir-Sync, Requestor, Export to re-export the address list. i. Wait for the Dispatch program to carry out the Dir-Sync cycle. If the server postoffice must be reset, or if Dir-Sync is not working for all postoffices involved, a global reset may be needed. This should only be done after the previous troubleshooting steps have been performed. On the server postoffice: a. Reset the REQCONF.GLB file by running the following command: listds -dm -r -z net po b. Verify that the REQCONF.GLB file is reset properly by running the following command: listds -dm -r The Dir-Sync server entry will be blank if the REQCONF.GLB file is properly reset. If not, repeat step a. c. Set the REQTRANS.GLB file to zero bytes. For this example, assuming that the postoffice is on drive M, run the following command: type aaa > m:\glb\reqtrans.glb This command will return the error "File not found - AAA." This error message is expected; the REQTRANS.GLB file will be zeroed. d. From the Administrator program, select Config, Dir-Sync, Options, No, and reply Yes to the warning. This step deletes the SRVCONF.GLB file and the MSTTRANS.GLB file from the server. e. Select Yes from the same menu to re-create the SRVCONF.GLB and MSTTRANS.GLB files. f. Select Config, Dir-Sync, Requestor, Registration to verify that the server is registered. If the entries for Network and Postoffice are blank, the SRVCONF.GLB file was not created correctly. Repeat steps d and e, exit the Administrator program to write the SRVCONF.GLB file correctly, restart the Administrator program, repeat step f, and continue. g. Select Config, Dir-Sync, Server, Requestors, Create to redefine all the requestors. h. Select Config, Dir-Sync, Requestor, Types to reset the types of names propagated by Dir-Sync. This step is only necessary if gateways are installed and gateway names are included in Dir- Sync. i. Select Config, Dir-Sync, Requestor, Export to send the list to the other postoffices. On each requestor postoffice: j. Reset the REQCONF.GLB file by running the following command: listds -dm -r -z net po [] k. Verify that the REQCONF.GLB file is reset properly by running the following command: listds -dm -r The Dir-Sync server entry will be blank if the REQCONF.GLB file is reset. If not, repeat this step. l. Set the REQTRANS.GLB file to zero bytes. For example, assuming the requestor postoffice is on drive N, run the following command: type aaa > n:\glb\reqtrans.glb This command will return the error "File not found - AAA." This is expected; the REQTRANS.GLB file will be zeroed. m. From the Administrator program, select Config, Dir-Sync, Requestor, Registration. Enter the network and postoffice name for the Dir-Sync server. If the server name is already listed, the REQCONF.GLB file was not reset. Repeat steps l and m, and continue with step n. n. Select Config, Dir-Sync, Requestor, Types to reset the types of names propagated by Dir-Sync. This is only necessary if gateways are installed and gateway names are included in Dir-Sync. o. Select Config, Dir-Sync, Requestor, Export, to send the list out to the other postoffices. Now all the Dir-Sync files will be reset. Wait for Dispatch to complete the Dir-Sync cycle. Problem 2: Names in GAL When Administrator Has Specified Not to Include Them ------------------------------------------ The most common cause of this problem is when External-Admin, Export is selected from the Administrator program. This command places a complete address list, regardless of any Dir-Sync settings, into the other postoffice's .USR file for that postoffice. Dir-Sync reads this file as part of the T3 step and the names will be in the GAL. To restore the GAL, run Administrator and select Config, Dir-Sync, Requestor, Import. After the next Dir-Sync cycle, the GAL will have the correct names in it. Problem 3: Fatal Error 161 Server Configuration Busy on a Requestor Postoffice --------------------------------------------- This error occurs when a server postoffice was turned into a requestor while Dir-Sync mail was still waiting to be processed, or when a requestor sends Dir-Sync updates to another requestor. Although the message states this is a fatal error, the Dir-Sync process is fine. To clear the error from the requestor postoffice: 1. Set the SYSTEM.MBG file to zero bytes by running the following command: type aaa > m:\glb\system.mbg 2. Clear the SYSTEM.KEY file by running the DEBUG utility: debug m:\key\system.key At the dash (-) prompt, type the following and press ENTER at the end of each line: -f, 100, 200, 0 -w -q This may not be sufficient to clear the problem if the requestor was once a server. The PROCESS.GLB file may contain a deferred server process time. Check the DIRSYNC.LOG file on the requestor postoffice for an error of "NSDA -S missed its run window." If this occurs, reset the PROCESS.GLB file by running the DEBUG utility: debug m:\glb\process.glb At the dash (-) prompt, type the following and press ENTER: -rcx At the colon (:) prompt, type the following and press ENTER at the end of each line: : 0200 -w -q From the Administrator program, select Config, Dir-Sync, Requestor, Schedule to reset all the T1 and T3 times for the requestor. Problem 4: Error 203 GAL Rebuild Problem Accessing Files -------------------------------------------------------- This error occurs when the GAL.NME or GALINDEX.NME file is locked open and the REBUILD utility attempts to replace them with the updated GAL. Unlock these files and run the REBUILD utility to restore the GAL. This must be done as soon as the error occurs; otherwise, it is possible that one of the files will be replaced but not the other, which will lead to misdirected mail. GLOSSARY ======== Directory The automatic process of transferring address Synchronization lists from one postoffice to another (Dir-Sync) postoffice. Dispatch The program that controls the Dir-Sync process. External The program that delivers mail between postoffices. GAL See Global Address List. GAL.NME The actual file for the GAL. This file is in the NME subdirectory of the Mail database. GALINDEX.GLB The index to the GAL. This file is meant to decrease the time the GAL is searched for a name. It is located in the GLB directory of the Mail database. GALNETPO.GLB The list of all external user addresses added in the Dir-Sync process. Global Address List The single address list containing all (GAL) addresses participating in Dir-Sync. Import A utility that allows for batch processing of user and gateway names. It is used to incorporate gateway names into the Dir-Sync cycle. Message Transfer The External Mail program or a gateway that Agent (MTA) delivers mail from one postoffice to another. MSTTRANS.GLB The master list of all addresses that are participating in Dir-Sync. It is maintained by the Dir-Sync server postoffice. MTA See Message Transfer Agent. Nsda Name Service Directory agent. It is spawned by the Dispatch program to run the appropriate step of the Dir-Sync cycle. PROCESS.GLB The storage file for the times defined in the Administrator program for Dir-Sync to send, process, and receive updates to the GAL. Rebuild The utility that re-creates the GAL from the local postoffice list, external postoffice lists, and gateway name files. REQCONF.GLB The requestor configuration record file. Reqmain The primary requestor process. It creates and receives mail messages that contain the updates to the GAL. REQTRANS.GLB The requestor transaction file. It contains a record of the current updates that need to be sent to the Dir-Sync server for incorporation into the MSTTRANS.GLB file and the external postoffice GALs. Requestor A postoffice that sends and receives Dir-Sync requests but does not maintain the master Dir- Sync files. Server A postoffice that sends, receives, and maintains the database of address lists. SRVCONF.GLB The server configuration record file. Srvmain The server process. It accepts the updates from the requestors, maintains the MSTTRANS.GLB, and creates mail messages containing updates to the requestors' GALs. SRVTRANS.GLB The server transaction file. It is a temporary storage place on all requestors and is used in the processing of updates from the Dir-Sync server. SYSTEM.MBG The mailbag that receives the Dir-Sync mail messages. <>