Error: Various when Outlook cannot be started by NEO
Applies to All NEO products
Problem NEO uses an invisible copy of Outlook to perform operations such as opening, forwarding and replying to messages, and to run Outlook menu commands such as initiating send/receive. This copy of Outlook is started using Outlook’s automation interface.
If NEO cannot start Outlook using its automation interface, one of the following errors may be reported:
Error 80004002-01 communicating with Outlook. The interface to Outlook did not start.
Error 80004005-01 communicating with Outlook. Unspecified error.
Error 80040102 No support.
Error 80040111-01 class factory cannot supply requested class.
Error 80040111-E02 communicating with Outlook. MAPILogon failed.
Error 8004011C-E02 communicating with Outlook. MAPILogon failed. (Not configured.)
Error 80040401-E02 communicating with Outlook. MAPILogon failed. (Timeout.)
Error 80040605-E02 communicating with Outlook. Not Initialized
Error 8007007E-01 communicating with Outlook. The specified module could not be found.
Error 8007045A-01 communicating with Outlook. A dynamic link library (DLL) initialization routine failed.
Error 800703E6-01 communicating with Outlook. Invalid access to memory location.
Error 800706BE-02 communicating with Outlook. The remote procedure call failed.
Error 80080005-01 communicating with Outlook. Server execution failed.
These problems are typically caused by a damaged Outlook installation, but may also be caused by:
Some incidental problem during startup of the machine causing Outlook to not load properly.
Outlook add-ins that do not behave correctly when an invisible copy of Outlook is started via automation.
Errors within the current Outlook session that prevent creation of an invisible copy of Outlook.
Before trying the below check whether a reboot resolves the issue: switch off the machine, wait for 20 seconds then restart your system for a fresh reboot. If the problem is not resolved, continue with the below.
See if the work around below solves the problem. It may be easier to adopt the work around than to repair the Outlook environment.
Disable all other Outlook add-ins: Outlook Tools menu | Options | Other tab | Advanced Options | COM Add-Ins | uncheck the items. If this solves the problem, then re-enable one add-in at a time until the problem reappears. Note that Microsoft Backup for PSTs can cause these problems. You may want to consider disabling it first.
Repair/reinstall Outlook. See Outlook Help menu | Detect and Repair, or see your Outlook documentation.
Uninstall then reinstall Outlook fully as a last resort (note do not simply reinstall - you must uninstall Outlook first then reinstall it). Do not uninstall the Office package as a whole, just select Outlook to uninstall. This has a high success rate, particularly with 8007007E-01 and 8007045A-01. Your message stores (psts) and account data will not be lost when you uninstall. On reinstall you will be able to open both Outlook and NEO. The one drawback is that if you have applied patches to your Outlook since the initial install, they will need to be reapplied when Outlook is reinstalled. You can do this by going to Outlook/Help/Check for Updates.
Work Around Some users have found that manually starting Outlook before NEO solves the problem.
Open the NEO Options dialog. On the General tab, make sure that “Start NEO when Outlook starts” is unchecked.
Close all visible copies of Outlook and all Outlook message windows.
Check in the Processes tab of Task Manager whether the process OUTLOOK.EXE is running. If it is running, wait 10 seconds and then end the process.
After Outlook has started, start NEO.
If this solves the problem, in the future just remember to start Outlook before NEO. Make sure that “Fast synchronize on startup” is checked in the General tab of the NEO Options dialog, to make sure that NEO shows messages received by Outlook before NEO starts.