DOCUMENT:Q170577 07-NOV-1999 [pcmail] TITLE :MDG: Private Folders in MMF named Orphan Folder #n PRODUCT :Microsoft Mail For PC Networks PROD/VER:WINDOWS:3.5 OPER/SYS: KEYWORDS: ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Mail for Windows, version 3.5 ------------------------------------------------------------------------------- SYMPTOMS ======== After using the chkmmf (SHIFT+ENTER) or moveuser utilities, a user's mmf file contains private folders named "orphan folder #n" where n is a number. CAUSE ===== The MMF file is already corrupted prior to running the chkmmf or moveuser utilities. The Orphan folder symptom indicates that the portion of the MMF file that was corrupted was the index. WORKAROUND ========== To work around this problem, perform one of the following: - Use the Windows Mail client to export the MMF file before using the moveuser or chkmmf utilities. - Instead of using chkmmf, rename the existing MMF file and import the old MMF file into a newly created mail message file. If a backup copy of the MMF is not available, there is no recovery from this corruption. Additional query words: ====================================================================== Keywords : Technology : kbMailSearch kbZNotKeyword3 kbMail350 Version : WINDOWS:3.5 Issue type : kbprb ============================================================================= 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 1999.