KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q244702: XFOR: Exchange Server 5.5 Post-SP3 Migration Fixes Available

Article: Q244702
Product(s): Microsoft Exchange
Version(s): 5.5
Operating System(s): 
Keyword(s): exc55kbfixlist
Last Modified: 23-OCT-2000

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Exchange Server, version 5.5 
-------------------------------------------------------------------------------

SUMMARY
=======

This article lists the article numbers for Exchange Server 5.5 migration bugs
that have been fixed since Exchange Server 5.5 Service Pack 3 was released. For
information about how to obtain the fixes listed in this article, click the
article number next to the title of the article about that issue to view the
article in the Microsoft Knowledge Base.

NOTE: Exchange Server fixes for a particular component are cumulative and contain
all previous fixes for that component. Fixes with a particular version number
contain all fixes with an earlier version number.

MORE INFORMATION
================

Migration fixes include the following files:

+--------------------------------+
| File name    | Current version | 
+--------------------------------+
| Lsntshc.dll  | 5.5.2652.13     | 
+--------------------------------+
| Mlmig32.dll  | 5.5.2652.39     | 
+--------------------------------+
| Mlmignts.dll | 5.5.2652.13     | 
+--------------------------------+

Fixes Released on July 7, 2000
------------------------------

The following files are modified:

- Lsntshc.dll added and incremented to version 5.5.2652.13
- Mlmig32.dll incremented to version 5.5.2652.39
- Mlmignts.dll incremented to version 5.5.2652.13

The following fixes are included:

  Q247291 XFOR: Migration Is Slow to Enumerate Names from a Large Notes Address
  Book

  Q247622 XFOR: Migrating from Lotus Stops the Wizard with a Dr. Watson Event

  Q249883 XFOR: Migration Wizard Reports Error Message 12024 When Migrating from
  Notes

  Q251018 XFOR: Configure Migration Wizard with Lotus cc:Mail 8.5 32-bit
  Executables

  Q254788 XFOR: Schedule+ 7.5 Users Are Always Prompted for a Password After
  Migration from MS Mail

  Q257698 XFOR: Migration Wizard Stops Responding While Migrating Calendar Data
  from Lotus Notes

  Q262989 XFOR: Lotus cc:Mail Migration Event 1030 Error Message Caused By
  Return Receipt

Fixes Released on September 15, 1999
------------------------------------

NOTE: The Lsntshc.dll file is not included with these fixes. This file is added
later. The following files are modified:

- All files incremented to version 5.5.2651.29

The following fixes are included:

  Q237886 XFOR: Message Attachment Name Incorrectly Changed in Migration from
  cc:Mail DB6 Post Office

  Q237993 XFOR: Users Cannot Reply to SMTP Messages in a PST After Migration

  Q238756 XFOR: Migration Fails to Migrate Messages from a GroupWise 5.x PO with
  Forwarded Appointments

  Q238784 XFOR: Not All Messages Are Migrated from a Lotus cc:Mail DB8 Post
  Office and 1032 Events Are Produced

  Q238850 XFOR: Migration Fails with Error Message and Event 6003

  Q240873 XFOR: Notes Migration Source Extractor Fails To Migrate Mail

  Q241292 XADM: Collabra Migration Objects - File Attachments Not Visible

  Q241553 XFOR: Migrated Message Returned as Not Deliverable for Migrated Lotus
  cc: Mail User

Additional query words:

======================================================================
Keywords          : exc55 kbfixlist
Technology        : kbExchangeSearch kbExchange550 kbZNotKeyword2
Version           : :5.5
Issue type        : kbinfo

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

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.