XCLN: 16-Bit Exchange Client Memory Issue

Last reviewed: February 3, 1998
Article ID: Q162670

The information in this article applies to:
  • Microsoft Exchange Windows 3.x client, version 4.0

SUMMARY

The error message:

   The MAPI spooler could not be started. Close and restart all mail-
   enabled applications. MAPI 1.0[000004c7]

appears when you start a 16-bit Exchange Client. In most cases, this is a conventional memory issue.

WORKAROUND

To work around this problem:

  1. Optimize conventional memory as much as possible (for example by means of MEMMAKER from MS-DOS 6.0/6.2).

  2. Disable all real mode device drivers and TSR programs you do not need.

  3. Disable automatically started applications by WIN.INI via RUN=, LOAD=).

  4. Use Program Manager (PROGMAN.EXE) as your shell.

  5. Change the order in which your programs or drivers load in order to minimize memory fragmentation.

  6. Remove as many 3rd-party Windows drivers or virtual device drivers (VxDs) as possible.

  7. Using Windows for Workgroups uncheck the option "Use Network DDE" in control panel app network.

  8. Configure the computer using NetBEUI or TCP/IP if possible.

  9. Test a Win16 computer by means of the Memvalet utility (this forces DLLs to load into upper memory). The utility is unsupported and should only be used after the normal troubleshooting steps have failed. (ftp://ftp.microsoft.com/bussys/exchange/exchange-unsup-ed/Memval.zip)

For more information about Win16 memory issues, please see the following articles in the Microsoft Knowledge Base:

   ARTICLE ID: Q124421
   TITLE     : WG1137: Memory Valet Utility to Correct "Out of Memory"

   ARTICLE ID: Q151359
   TITLE     : XCLN: Out of Memory Errors Starting Schedule+ After Exchange

   ARTICLE ID: Q150156
   TITLE     : XCLN: Cannot Send from Word When Exchange Client Not Running

   ARTICLE ID: Q112676
   TITLE     : Troubleshooting Insufficient Memory Errors

   ARTICLE ID: Q124421
   TITLE     : WG1137: Memory Valet Utility to Correct "Out of Memory"

MORE INFORMATION

You might also get this error when trying to access Windows Messaging email in MSN 2.0. If so, try emptying your Temp directory, Temporary Internet Files directory, and History folders in your Windows directory and then rebooting the computer.


Additional query words: kbfaq
Keywords : XCLN
Version : 4.00
Platform : WINDOWS


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: February 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.