XCLN: Free/Busy Connector Errors 1027 and 1029

Last reviewed: January 23, 1998
Article ID: Q167648

The information in this article applies to:
  • Microsoft Exchange Server versions 4.0 and 5.0

SYMPTOMS

The Microsoft Schedule+ Free/Busy Connector logs the following events:

   Event ID: 1029
   Source: MSExchangeFb
   Type: Error
   Category: None

   Unable to find the MS Mail user MS:NETWORK/PONAME/USERNAME the
   Microsoft Exchange Address Book.

   This address is not defined in the Recipients container.
   Synchronize your MS Mail Postoffice addresses or create a custom
   recipient entry for this address.


   Event ID: 1027
   Source: MSExchangeFb
   Type: Error
   Category: None

   Unable to import the Microsoft Schedule+ data for MS:NETWORK/PONAME/
   USERNAME.

   Ensure that this recipient is defined in the Address Book.

CAUSE

The Admin.prf file on the Microsoft Mail postoffice contains an invalid network or postoffice name.

RESOLUTION

To correct this problem, reset the Admin.prf file on the user’s postoffice. For details on how to reset the Admin.prf file and the associated POF files, see step 11 in the Microsoft Knowledge Base article, Q141755, “How to Setup Schedule Distribution.”

Keywords          : XCLN
Version           : WINDOWS:4.0,5.0
Platform          : WINDOWS
Issue type        : kbprb
Solution Type     : kbworkaround


================================================================================


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