Q146398: XCLN: PAB with .MMF Extension Is Not Recognized
Article: Q146398
Product(s): Microsoft Exchange
Version(s): WINDOWS:4.0,5.0
Operating System(s):
Keyword(s): kbusage
Last Modified: 18-MAR-1999
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Exchange Windows 95/98 client, versions 4.0, 5.0
- Microsoft Exchange Windows 3.x client, versions 4.0, 5.0
- Microsoft Exchange Windows NT client, versions 4.0, 5.0
-------------------------------------------------------------------------------
SYMPTOMS
========
When you try to import a Personal Address Book (PAB) into the exchange client,
if the PAB has an extension that is .MMF instead of .PAB you will receive the
following error:
File "FILENAME.MMF" is not a recognized MMF File.
If the Personal Address Book file has any entry other than MMF, the file will
import correctly. On the other hand, if you have a actual MMF file that has the
extension of .PAB, it will also import correctly.
RESOLUTION
==========
Rename the Personal Address Book extension to anything other than .MMF and the
import will work correctly.
STATUS
======
Microsoft has confirmed this to be a problem in Microsoft Exchange version 4.0
Windows, Windows NT, and Windows 95 clients. We are researching this problem and
will post new information here in the Microsoft Knowledge Base as it becomes
available.
Additional query words: pab address
======================================================================
Keywords : kbusage
Technology : kbExchangeSearch kbExchange500 kbExchange400 kbExchangeClientSearch kbZNotKeyword kbZNotKeyword2 kbZNotKeyword3 kbExchange400NT kbExchange500NT kbExchange400Win95 kbExchange500Win95
Version : WINDOWS:4.0,5.0
=============================================================================
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.
Copyright Microsoft Corporation 1986-2002.