XADM: Cannot Edit the PAB Migration Message in Exchange 5.0

 Last reviewed: February 12, 1998
Article ID: Q175967
The information in this article applies to:
  • Microsoft Exchange Server, version 5.0

SYMPTOMS

When you migrate users from SFS or cc:Mail to Microsoft Exchange Server, you cannot edit the PAB migration message that is paced in the migrated user's Inbox. This functionality existed in Microsoft Exchange Sever, version 4.0.

CAUSE

This change was implemented to simplify codepage issues resulting from editing the default PAB message.

WORKAROUND

To workaround this problem, follow these steps:

  1. Create a text file called Pabmsg.txt and place it in the \Exchsrvr\bin directory.

  2. Run all migrations that will generate the PAB migration message (SFS, CCMail).

When you no longer want this functionality, simply remove the Pabmsg.txt file.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server, version 5.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. 

Keywords          : kbbug5.00 kbfix5.00.sp2 XADM
Version           : WinNT:5.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix

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

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