X400: Err Msg: Error 12 (Restarting MTA): execv...

 Last reviewed: October 20, 1997
Article ID: Q132529
3.00 MS-DOS kbinterop kberrmsg kbbug3.00

The information in this article applies to:

  • Microsoft Mail Gateway to X.400, version 3.0

SYMPTOMS

Version 3.x of Microsoft Mail Gateway to X.400 may not be able to successfully restart the gateway when you use a Restart Interval greater than zero. The Restart Interval, as documented on page 89 of the Microsoft Mail Gateway to X.400 "Administrator's Guide," determines how frequently the X400GATE program automatically stops and restarts. The following error is displayed when the gateway attempts to restart and fails: 

   ERROR 12 (restarting MTA): execv (N:\mailexe\x400gate.exe, argv) failed
The gateway may also produce an error: 

   ENOMEM (not enough memory)

CAUSE

Running out of memory will cause the heap to be sufficiently fragmented that the call to execv() to restart the gateway will fail.

RESOLUTION

This issue has been resolved in version 3.2.016 were a _heapmin() call was added to compact the heap before calling execv() to restart the gateway.

STATUS

Microsoft has confirmed this to be a problem in version 3.x of Microsoft Mail Gateway to X.400. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: 3.00
KBCategory: kbinterop kberrmsg kbbug3.00
KBSubcategory: MailGWX400
Keywords : MailGWX400 kbbug3.00 kberrmsg kbinterop
Version : 3.00
Platform : MS-DOS

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.

Last reviewed: October 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.