Read time 5 minutes

Summary: Outlook Express users encounter various errors during email communication, stemming from data file corruption or account configuration issues. This article highlights common errors and provides solutions. It covers issues such as invalid page faults, disk space errors, crashes, and failure to start. The article guides users through troubleshooting steps and email recovery from damaged DBX files, emphasizing the use of Kernel for Outlook Express as a result-oriented tool for recovery.

Outlook Express users frequently encounter a variety of errors throughout their email communication. These errors can arise from issues such as data file corruption and poorly configured account settings. Below, we’ve compiled a list of common errors to help you address these issues.

‘MSIMN caused an invalid page fault’

MSIMN has caused the error at the Msoe.dll is the address.

‘Outlook Express: Could not send the message. Disk area is insufficient.’

The message clearly shows that the disk area is insufficient to send the message.

‘MSIMN invalid page fault. Module: unknown
MSIMN invalid page fault. Module: DIRECTDB.DLL
MSIMN invalid page fault. Module: WAB32.dll
MSIMN C0000006h. Module: Directdb.dll’

These error messages are typically a result of various issues within the sender and recipient’s email addresses or systems.

Outlook Express frequently crashes or fails to launch due to damage in *.dbx files. Additionally, if these files are set as “Read-only,” they won’t open. To troubleshoot this issue, ensure none of the files are marked as “Read-only.”

  1. Close Outlook Express, go to Windows Explorer and open store folder
  2. Select all files and right click on any selected file. Click on Properties and clear the Read-only checkbox.

If Outlook Express starts in this situation, attempt to compact all your folders, as this process often helps users repair minor damage.

  1. Click File and Work Offline so that no new messages are received
  2. In the Folder list, click on Outlook Express in order to make sure that no folder or newsgroup is open
  3. Click File > Folder > Compact All Folders. Don’t perform any further functions until the compacting process is complete as it might take several minutes. In between if any error occurs, close OE, reopen it and start the process again. In case the same error occurs again, restart your computer again by logging off and logging on again and initiate with the entire process again.

If Outlook Express does not start, initiate moving the *.dbx files from your store folder into any other empty folder by following the procedure mentioned below:

  1. Download this small script that opens the store folder of the currently logged-on Identity. Otherwise, you can find the script by searching in Windows Explorer for files named *.dbx. Make sure you include the hidden files in your search, as OE user files are by default marked as hidden. In order to view the hidden files, perform the following steps:

    Click Tools in Windows Explorer > Folder Options > View
    Enable the check-box for showing hidden files and folders

  2. Right-click on the Desktop and Open New Folders
  3. In store folder window, click Edit > Select All or press Ctrl + A
  4. Copy the selected files and drop them into the New Folder on your desktop

Attempt to start Outlook Express, and if it launches without displaying any errors, proceed to import your mail folders:

  1. Click File > Import > Messages > Microsoft Outlook Express
  2. Select Import from store folder and click on Browse button
  3. Search for the New Folder on the Desktop

If Outlook Express cannot import your email folders, it likely indicates that the file Folders.dbx is damaged. In this scenario, close Outlook Express and relocate the other *.dbx files back to the store folders. After restarting OE, it will automatically reconstruct a new index for all the *.dbx files it can read, generating a new set of Folders.dbx. Keep in mind that your mail tree structure will be lost, and you’ll need to edit all lists of newsgroups, synchronization options, and message rules.

If you still can’t start Outlook Express, it’s likely that your Identity in the registry has been damaged.

  1. Download Force Identity Logon script
  2. Run the script to get to Identities Manager
  3. Create a new Identity and switch to it when prompted
  4. If you already have exported your accounts settings to Internet Account files (*.iaf) then cancel the Add Account wizard to start automatically. Click Tools > Accounts and Import button to import each and every single *.iaf file.
  5. In case you have not exported your account settings, follow the wizard to set up your basic email account.

There are instances when the Identities Manager won’t run, and OE refuses to start. In such severe cases, the situation demands drastic measures.

Open Regedit and export the entire HKCU/Identities key, then delete it. Double-click the saved *.reg files you exported and attempt to open Outlook Express. If it still doesn’t open, export the subkey HKCU\Identities\{GUID} to its own *.reg file, and then try opening Outlook Express again. The New Account Wizard will initiate; cancel it, as you should bypass the default Identity. (Please make sure to back up your registry before proceeding with these steps.)

Click File > Identities > Manage Identities and try switching to your old Identity; if this is successful, you can delete the new empty Identity from the manage identities dialogue. If this fails and OE does not responds, you would have to delete the HKCU\Identities key again, open OR, set up new Identity and import all of your email folders from the previous Identity.

Invalid Message Rules errors mentioned below are often encountered:

Invalid Message Rules errors (older versions of OE5)
MSIMN caused an Invalid Page Fault in module unknown
MSIMN caused an invalid page fault in module MSOE.DLL at memory address
MSIMN caused an Invalid Page Fault in module kernel32.dll

These errors occur when a message rule employs invalid logic. If the rule’s criteria specify a condition determined after the message body is downloaded, but the rule’s action is set to “Do not download” or “delete from the server,” this creates a logical contradiction that causes Outlook Express to crash.

Following are the conditions that require the message body to be downloaded:

  • Where the message body contains specific words
  • Where the message is secure
  • Where the message has an attachment

If these conditions are included in the rule, you must not select either do not download or delete from server.

If you find yourself in a disastrous situation where your DBX files are corrupt, inaccessible, and in need of repair, it’s essential to fix your Outlook Express DBX files to recover your emails and other mailbox items. Kernel for Outlook Express is a reliable Outlook Express recovery tool designed to recover emails and other items from .DBX files effectively.

Kernel for Outlook Express Recovery