DOCUMENT:Q125918 29-JAN-1999 [pcmail] TITLE :PC DirSync: SRVMAIN.EXE Causes Trap 000D Error PRODUCT :Microsoft Mail For PC Networks PROD/VER:WINDOWS:3.2a OPER/SYS: KEYWORDS:kberrmsg kbinterop ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Mail for PC Networks, version 3.2a ------------------------------------------------------------------------------- SYMPTOMS ======== During the T2 phase of directory synchronization (Dir-Sync), when SRVMAIN -r runs on OS/2 or in the OS/2 subsystem on Microsoft Windows NT, a Trap 000D error may occur. CAUSE ===== SRVMAIN.EXE produces a Trap 000D error when it tries to process a corrupt attachment sent with the status message from a requestor. The DSSERVER.LOG on the requestor is the file that gets sent as an attachment to the Dir-Sync server, and this file contains corruption. STATUS ====== Microsoft has confirmed this to be a problem in SRVMAIN.EXE version 3.2a of Microsoft Mail for PC Networks. This problem was corrected in SRVMAIN version 3.2.12. Additional query words: 3.20 kbbug3.20a kbfix3.20.13 ====================================================================== Keywords : kberrmsg kbinterop Technology : kbMailSearch kbZNotKeyword3 kbMailPCN320a Version : WINDOWS:3.2a 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. Copyright Microsoft Corporation 1999.