PC DirSync: Err Msg: Error [ 81] No Mailbox Name Net/PO/

Last reviewed: August 7, 1995
Article ID: Q128872
The information in this article applies to:
  • Microsoft Mail for PC Networks, versions 3.2

SYMPTOMS

With version 3.2 of Microsoft Mail for PC Networks, persistent errors during Directory Synchronization (Dir-Sync) may be recorded in the DIRSYNC.LOG file during the SRVMAIN -T (T2) process:

   Error [ 81] No mailbox NAME NET/PO/

CAUSE

This error indicates that the transaction is missing the group address. This happens when the GROUP.GLB file is corrupt or has been reset to 4 bytes without deleting groups using ADMIN.EXE. The next time an administrator updates the group, a transaction is put in the REQTRANS.GLB without the group name, even if the group is excluded from Dir-Sync.

NOTE: This error should disappear in Keep Updates time.

RESOLUTION

  1. Print out the members of groups from ADMIN.EXE by selecting Local-Admin, Group, Print, and choose either Printer or File.

    NOTE: Use this file to recreate the groups after deleting them.

  2. Select Local-Admin, Group, Delete.

  3. Delete all the groups.

Deleting the groups through ADMIN.EXE will remove the entries in ADMIN.NME, and resolve the error.

STATUS

Microsoft has confirmed this to be a problem in ADMIN.EXE version 3.2.12, included with Microsoft Mail for PC Networks. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional reference words: 3.20
KBCategory: kbother kberrmsg kbbug3.20
KBSubcategory: MailPCAdm


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: August 7, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.