Cannot Open or Compose Message in Windows Messaging

This article was previously published under Q137245
This article has been archived. It is offered "as is" and will no longer be updated.


IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore itif a problem occurs. For information about how to do this, view the"Restoring the Registry" Help topic in Regedit.exe or the "Restoring aRegistry Key" Help topic in Regedt32.exe.

NOTE: In this article, the term "Windows Messaging" refers to bothMicrosoft Exchange and Windows Messaging.
Symptoms
When you attempt to start Windows Messaging or Microsoft Outlook 97, orcompose or open a message in Windows Messaging or Outlook 97, you mayreceive one of the following error messages:
  • EXCHNG32 caused an exception 05h in WMSFR32.DLL
  • EXCHNG32 caused an invalid page fault in module WMSFR32.DLL
  • EXCHNG32 caused an invalid page fault in module WMSUI32.DLL
  • Some information could not be read. Microsoft Exchange Client - 9992 - [81002708]
  • The item could not be displayed. The object could not be found. Microsoft Windows Messaging System Forms Registry - 13085 - [8004010F]
  • The item could not be displayed [80004005]
  • The item could not be displayed [81003355]
  • The command you specified could not be carried out. The object could not be found. Microsoft Windows Messaging System Forms Registry - 13085 - [8004010F]
  • The command you specified could not be carried out. The form cache file <frmcache> is not valid. Contact your administrator. Error code 0x81003364. Microsoft Windows Messaging System Forms Registry - 13156 - [80040119]
  • The Mapi spooler has shut down unexpectedly.
In addition, you may find that the long folder name associated with theProgram Files\Microsoft Exchange folder is damaged or that the ProgramFiles folder has been renamed to $!$!$!$!.$!$.
Cause
This behavior can occur if any of the following conditions exists:
  • The Wmsfr32.dll, Wmsui32.dll, or Frmcache.dat file is missing or damaged.
  • The long folder name associated with the Program Files\Microsoft Exchange folder is damaged or the Program Files folder has been renamed to $!$!$!$!.$!$.
  • The Exchange or MlSet values under the Hkey_Local_Machine\Software\ Microsoft registry key are missing or damaged.
Resolution
WARNING: Using Registry Editor incorrectly can cause serious problems thatmay require you to reinstall your operating system. Microsoft cannotguarantee that problems resulting from the incorrect use of RegistryEditor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing KeysAnd Values" Help topic in Registry Editor (Regedit.exe) or the "Add andDelete Information in the Registry" and "Edit Registry Data" Help topicsin Regedt32.exe. Note that you should back up the registry before you editit. If you are running Windows NT, you should also update your EmergencyRepair Disk (ERD).

To resolve this issue, perform the following steps. After performing eachstep, check to see if the problem has been resolved.
  1. Verify that the Frmcache.dat file is not missing or damaged. To do so, perform the following steps. Before performing each step, rename the Frmcache.dat file in the Windows\Forms folder, if it exists. After performing each step, check to see if the problem has been resolved.

    1. Double-click the Mlset32.exe file in the Program Files\Microsoft Exchange folder.
    2. Copy the Frmcache.bak file in the Windows\Forms folder to Frmcache.dat.
    3. Obtain a copy of the Frmcache.dat file from a computer on which Windows Messaging is functioning properly and then copy the file to the Windows\Forms folder on your computer.
  2. Verify that the Program Files\Microsoft Exchange folder exists. To do so, attempt to locate the folder using Windows Explorer. If the folder name that appears in Windows Explorer is Program Files\Micros~1 or Progra~1\Microsoft Exchange, or if the Program Files folder has been renamed to $!$!$!$!.$!$, please see the following article in the Microsoft Knowledge Base:
    143395 Microsoft Exchange Folder Truncated to "Micros~1"
  3. Rename all copies of the Wmsfr32.dll and Wmsui32.dll files on your hard disk, and then extract new copies of the Wmsfr32.dll and Wmsui32.dll files from your original Windows 95 disks or CD-ROM to the Windows\ System folder. The Wmsfr32.dll and Wmsui32.dll files are located in the Win95_06.cab cabinet file on the Windows 95 CD-ROM or the Win95_07.cab cabinet file on disk 7 of your original Windows 95 disks.

    For information about using the Extract tool, type "extract" (without quotation marks) at a command prompt, or see the following article in the Microsoft Knowledge Base:
    129605 How to Extract Original Compressed Windows Files
    NOTE: If you have installed the Microsoft Exchange Update for Windows 95, you should not extract new copies of the Wmsfr32.dll and Wmsui32.dll files from your original Windows 95 disks or CD-ROM. After you rename all copies of the files on your hard disk, you should reinstall the Microsoft Exchange Update from the online source from which you originally installed it.
  4. Verify that the Exchange and MlSet values under the following registry key are not missing or damaged:
    Hkey_Local_Machine\Software\Microsoft
    The Exchange value should have the following value:
    C:\Progra~1\Micros~1\exchng32.exe
    The MlSet value should have the following value:
    C:\Progra~1\Micros~1\mlset32.exe
    If either of these values is missing or incorrect, create or modify the value manually.
  5. Remove and reinstall Microsoft Exchange. To do so, follow these steps:

    1. In Control Panel, double-click Add/Remove Programs.
    2. Click the Windows Setup tab and then click the Microsoft Exchange check box to clear it. If you are prompted to remove Microsoft Fax also, do so.
    3. Click OK.
    4. After Microsoft Exchange is removed, remove all files in the Windows\Forms folder and then restart Windows 95.
    5. In Control Panel, double-click Add/Remove Programs.
    6. Click the Windows Setup tab and then click the Microsoft Exchange check box to select it. If you also removed Microsoft Fax, click that check box to select it also.
    7. Click OK.

Microsoft Windows NT Server 4.0, Terminal Server Edition, version 4.0

To resolve this problem with Terminal Server, copy the Frmcache.dat filefrom the %SystemRoot%\Forms folder to the %SystemRoot%\Profiles\ %username%\Windows\Forms folder.
More information
The Frmcache.dat file is created during the initial configuration ofWindows Messaging, either by the Microsoft Exchange Setup Wizard or laterwhen you add the first service. The Frmcache.dat file contains standardforms and other information that Windows Messaging uses to perform taskssuch as displaying and sending messages. If the information associatedwith a particular task is missing or damaged, you receive an error messagewhen you attempt to perform that task. If all other information in thefile is not damaged, Windows Messaging appears to function properly whenperforming all other tasks.

The size of a valid Frmcache.dat file is usually 16K or larger. Manyprograms add information to the Frmcache.dat file when they are installed,causing the file to increase in size. The Frmcache.bak file is createdwhen the Frmcache.dat file is first created and is typically not modifiedwhen a program adds information to Frmcache.dat file. Therefore, if youreplace the Frmcache.dat file with the Frmcache.bak file, any informationadded to the Frmcache.dat file is lost. This information must be replacedmanually by reinstalling the program that originally added it.

The following situations can cause the Frmcache.dat file to become damaged:
  • You backed up and restored the files on your computer, but long file names were not recognized correctly. After the files were restored, the path for the Program Files\Microsoft Exchange folder did not match the associated registry entries.
  • Your computer contains a preinstalled copy of Windows 95. When an image of Windows 95 is placed on a hard disk, Windows Messaging may appear to be installed correctly, but the Frmcache.dat file may not have been created correctly.
The Microsoft Exchange Configuration Wizard (Mlset32.exe) is run for thefirst time when Windows Messaging is first installed. It can be used as atroubleshooting tool after Windows Messaging has been installed, but it isnot always successful in rebuilding the Frmcache.dat file.
corrupt form msn msnetwork
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Properties

Article ID: 137245 - Last Review: 10/24/2013 07:40:00 - Revision: 2.0

Microsoft Windows 95, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Enterprise Edition

  • kbnosurvey kbarchive kberrmsg KB137245
Feedback