DOCUMENT:Q87388 31-OCT-1999 [pcmail] TITLE :PC DB: How to Tell If a CONTROL.GLB File Is Corrupted PRODUCT :Microsoft Mail For PC Networks PROD/VER:WINDOWS:2.1e,3.0,3.2 OPER/SYS: KEYWORDS: ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Mail for PC Networks, versions 2.1e, 3.0, 3.2 ------------------------------------------------------------------------------- SUMMARY ======= The following are some tests to determine whether a CONTROL.GLB file is corrupt: 1. The file size must be 8 bytes in length. 2. The contents of the nmailbag and nletter fields do not look abnormally large. This is not necessarily a corruption that will cause the mail system not to work; instead, it is an indication that there was some file corruption in the database and that there may be future problems. MORE INFORMATION ================ Offset Size Name Description ---------------------------------------------------------------------- 0 4 long nmailbag For generating user or gateway associated filenames 4 4 long nletter For generating mail, attachment and P1 filenames Additional query words: 2.10e 3.00 3.20 ====================================================================== Keywords : Technology : kbMailSearch kbZNotKeyword3 kbMailPCN320 kbMailPCN300 kbMailPCN210e Version : WINDOWS:2.1e,3.0,3.2 ============================================================================= 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.