Otherwise, for Outlook 2007 and 2003 you may try the repair steps in Microsoft's support knowledge base article#813602 (see the related article "Repair Microsoft Office Outlook 2003 or 2007 Mapi") reprinted below:

In Windows\System\32 {or Windows\System}, rename the Mapi32.dll file (for example to mapi32.old), and then start the Fixmapi.exe program as follows:

  1. Close all programs.
  2. Click Start, and then click Search.
  3. Click All files and folders.
  4. In the All or part of the file name box, type mapi32.dll, and then click Search.
  5. When the search process is complete, right-click the Mapi32.dll file in Windows\System\32 {or Windows\System}, and then click Rename. (Note: If mapi is in memory, you will not be able to rename it.  Click Ctrl-Alt-Delete and End Task on mapisp32. Verify it's not running before trying to rename it.)
  6. Type Mapi32.old, and then press ENTER.
  7. Click Start a new search, and then click All files and folders.
  8. In the All or part of the file name box, type fixmapi.exe, and then click Search.
  9. When the search process is complete, double-click Fixmapi.exe (or right-click and "Run as Administrator" in Vista/7) to start the repair process.
  10. Follow the on-screen instructions to complete the MAPI repair process.

Outlook 2000 typically (but not always) stores a copy of the correct version of mapi32.dll for Windows XP in Program Files\Common Files\System\Mapi\1033\NT; or for Windows Vista and 7 in Program Files\Common Files\System\MSMAPI\1033\. In these older versions of Outlook, the most common reason Outlook fails is because another application (such as Netscape or Corel) has replaced the Mapi32.dll file in the Windows System folder with a customized version of the same name.  The customized version in Windows\System will be larger in size than the version in Program Files\Common Files\System\Mapi {or MSMAPI}\1033\.

The easiest way to correct this non-standard mapi32.dll  problem in older Outlooks is do a search in Start > Find > Files or Folders for Mapi32.*. to find all the mapi files. You may see the original file renamed to either Mapi32x.dll or Mapi32bak.dll. You can try restoring the original mapi file by renaming the existing mapi32.dll to mapi32.old and rename either Mapi32x.dll or Mapi32bak.dll (whichever is smaller) back to mapi.32.dll.  

Also you can try renaming the current mapi32.dll to mapi32.old and restore the original off the Microsoft Office CD. Run a search on the cd and copy it to the same Windows System file where you found mapi32.dll.

If none of these steps resolve the problem in Office Outlook but you still want to use Outlook (rather than another e-mail program), un-install and re-install Outlook from the Microsoft Office installation CD. (Be sure any anti-virus programs are disabled when installing any program such as Office Outlook.) If you do re-install Outlook, be sure to also re-install its CDO feature (since CDO is not included in the default installation setup). To fix Active X or Unspecified errors using Office Outlook, follow the instructions in the related article "Office Outlook Collaborative Data Object (CDO), Active X or Unspecified Email error."

▲ Back to the top of this page

Outlook Express

If you are using Outlook Express instead of Microsoft Office Outlook, it is best to run the latest version of both Outlook Express (version 6.0) and of Internet Explorer (version 8 in Windows XP). Check the version under Help > About Microsoft Outlook Express (and Help > About Internet Explorer).

If Outlook Express does not function correctly, ensure that it is properly configured (see the related article, "Configure Security in Outlook Express...") and that no other program (such as AntiVirus, AntiSpam, Privacy, or Internet security) is interfering with ("filtering") outgoing email. If configuring security does not fix an email problem, it is possible that some files used by Outlook Express are corrupted or damaged. To repair damaged files, follow the instructions in the related article, "Repair Outlook Express".

Some older computers running older versions of Windows cannot support the latest version of Outlook Express and Internet Explorer. To fix Mapi import errors in these older versions of Outlook Express (4.0 to 5.5) in Windows 95 or 98, or for Outlook Express 6 in Windows XP which also has Office Outlook installed, follow Microsoft's instructions in the related article "Repair Mapi Import or Export errors in Outlook Express" (reprinted below):

Configure Outlook Express to not be the default Simple MAPI client before you import the mail items. To do so, follow these steps:

  1. Restart your computer, and then start Outlook Express.
  2. On the Tools menu, click Options.
  3. On the General tab, click to clear (un-check) the Make Outlook Express my default Simple MAPI client check box, and then click Apply.
  4. Click OK when you receive the prompt to restart your computer.
  5. Click OK, quit Outlook Express, and then restart your computer.

Note 1: After you complete the import or export process, you can reconfigure older versions of Outlook Express to be the default MAPI client (which is the normal default setting unless you are using Office Outlook as your default MAPI client in Windows). For additional information from Microsoft about how to configure Outlook Express to be the default MAPI client, select "Set Outlook Express as Your Default Simple MAPI Client" in the Related Articles and Internet Links at the end of this web page.

▲ Back to the top of this page

Windows 7 or Vista Privilege Settings

If CTI Navigator was installed before April 19, 2012, it must have "Administrative Privilege" in Windows 7 and Windows Vista to be able to deliver email code to your email program. (Otherwise email may be diverted to the  Windows "Virtual Store".) To set older installations of CTI Navigator to always "run as an administrator" in Windows 7 or Vista, close CTI Navigator then: 

  1. Open Windows Explorer [right-click on Start and select Explore or "Open Windows Explorer"] 
  2. In Windows Explorer, browse to C:\Program Files\CTI Navigator\CTI Navigator.exe
       [in a 64-bit version of Windows, browse to C:\Program Files (x86)\CTI Navigator\CTI Navigator.exe
  3. Right-click on the CTI Navigator.exe file > select Properties > click the Compatibility tab > under Privilege Level, check "Run this program as an Administrator" > click Apply > click "Show/Change Settings for All Users" button (if this button is displayed) and also under Privilege Level, check "Run this program as an Administrator" > click OK. 
  4. Close Windows Explorer
  5. Close your email program before you open CTI Navigator.   

Close Email Processes: In Windows 7/Vista, you may need to always close your email program before you try to send email reports out of CTI Navigator. To verify that all email processes are closed: right-click on the Windows task bar (at the bottom of the screen) > select Task Manager or "Start Task Manager" > select the Processes tab > highlight Outlook.exe or WLMail.exe if listed in the "Image Name" column > click the "End Process" button > then click X to close the Task Manager.

For more details on special issues with Windows 7 and Vista, see "Use Windows Vista and Windows 7" in the Related Articles and Internet Links at the end of this web page.

Windows Mail in Windows Vista

Outlook Express was revised and named "Windows Mail" in Windows Vista. Apparently due to the User Account Control restrictions in Vista, Windows Mail must be closed before MLS reports can be transferred from CTI Navigator into Windows Mail. Otherwise, Vista treats the file transfer as a separate user login attempt into Windows Mail and blocks it. 

If you get a "Login Failed...clsSendMail_Send" error message using Windows Mail as your default mail program in Windows Vista, either:

  1. Re-start Vista to close Windows Mail processes and clear the failed transfer login; or 
  2. Close the error message > close Windows Mail > right-click on the Windows task bar and select Windows Task Manager > Select the Processes tab > right-click on WinMail.exe> select "End Process".

To resolve other problems in Windows Mail, see the related article entitled "Troubleshoot Problems in Windows Mail" at the end of this web page.

▲ Back to the top of this page

Windows 10, 8, and 8.1

Microsoft's Mail app included in Windows 10, 8 and 8.1,  does not support mail code to send messages created by apps such as CTI Navigator Desktop running in the Windows Desktop mode. Trying to send email from a desktop app through the Windows Mail app can lead to Mapi or clsSend errors.  

To email from a desktop app (such as CTI Navigator Desktop) in Windows 10, 8, or 8.1, first install and configure a desktop email app such as Windows Live Mail, Office Outlook, or Mozilla Thunderbird. (For information on Windows email programs, see "Setup and Use Email Service to Send MLS Reports..." in the related articles at the end of this web page.) It is not necessary to install a desktop email app in Windows 10, 8, or 8.1 if you use CTI Navigator Web (or CTI Navigator Mobile) instead of CTI Navigator Desktop to email MLS information  

If your Windows desktop email app (such as Windows Live Mail or Mozilla Thunderbird) was communicating properly with desktop CTI Navigator, but starts producing MAPI or clsSend errors, re-set the default Email Handler and default Email Program Access in the Windows Control Panel (as described in "Multiple Email Programs" above).

Windows RT Mail

Windows RT currently does not allow desktop email apps to be installed, and does not allow plug-ins (such as Silverlight) to be installed in its Internet browser. Consequently, only CTI Navigator Mobile can be used in Windows RT. Any web enabled device (including Windows RT, Apple iOS, or Android) can send email from CTI Navigator Mobile because Navigator Mobile uses CTI's Internet server to send email. 

Mozilla Thunderbird

Thunderbird may be able to send and receive email messages directly, even though a MAPI or other error may occur when another program (such as CTI Navigator) attempts to transfer a message internally to it through Windows. 

The most common causes of a MAPI type error with Thunderbird are that Thunderbird is not set as the default e-mail program in Windows, or your personal account is not set as the default account in Thunderbird, or some other email program in Windows is interfering with MAPI connections to Thunderbird. 

A "no valid ID ..." type error usually indicates that your personal account is not set as the default ID in Thunderbird. To set your personal account as the default in Thunderbird, open Thunderbird > select Tools > Account Settings > select Your Account (in the left pane) > click on Account Actions (at the bottom of the left pane) > click "Set as Default" (which will then gray out) > click OK. 

To set Thunderbird as the default Windows program for e-mail, open Thunderbird > select Tools > Options > "Use Thunderbird as the default mail application." You also can set Thunderbird as the default e-mail program in Windows Control panel (see "set Default Email Handler" instructions under Multiple Email Programs above).

To stop another email program from interfering with Thunderbird, follow the instructions to configure Windows' Program Access in the Multiple Email Programs above. 

Novell GroupWise 

GroupWise from Novell is a messaging and collaboration platform that competes with Microsoft Exchange Server. The email component of GroupWise sets itself as the default email client. To be able to use a different default email client with a server running GroupWise, install the GroupWise MAPI32.DLL stub to the GroupWise folder rather than to the Windows System folder.

To restore the normal MAPI32.DLL in Windows System32 if it has been overwritten or corrupted, rename the Mapi32.dll in System32 and run Fixmapi.exe as described above under Office Outlook

▲ Back to the top of this page

Related articles and Internet links:

▲ Back to the top of this page


To return to CTI's menu of Instructions to Fix Errors, click here or use the back arrow at the top of your Internet browser.



rev. 12.11.2017