PC DirSync: Err Msg: Fatal [161] Server Configuration Busy

 Last reviewed: February 4, 1998
Article ID: Q136487

The information in this article applies to:
  • Microsoft Mail for PC Networks, versions 3.0, 3.0a, 3.2, and 3.5

SYMPTOMS

The following error may be recorded in the DIRSYNC.LOG on a requestor postoffice: 

   Fatal 161 Server configuration busy

CAUSE

The above error indicates that the postoffice was once designated a server; however, it was later changed to a requestor. When this occurs, the SRVCONF.GLB and MSTTRANS.GLB files are removed, but the T2 processes that were scheduled still remain in the PROCESS.GLB. When Dispatch runs, it finds the NSDA -s process scheduled and tries to launch it. However, because this is a requestor, the postoffice records an error.

RESOLUTION

Reset the PROCESS.GLB file using DEBUG: 

   debug process.glb <ENTER>
   -rcx <ENTER>
   xxxx
   :200 <ENTER>
   -w <ENTER>
   -q <ENTER>
Then schedule the T1 and T3 processes on this postoffice using the Administrator's program (ADMIN.EXE) or the DSSCHED.EXE program included with Application Note WA0725 "Directory Synchronization (Dir-Sync)".

MORE INFORMATION

If this error appears on the Dir-Sync server postoffice, make sure that SRVCONF.GLB is not locked open or missing.

Additional query words:
Keywords : MailPCDirSync kbfaq
Version : 3.00 3.00a 3.20 3.50
Platform : MS-DOS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 4, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.