*Bulletin ID* A2E_168
*Last Review* 05/17/2018
*Revision* 1.0
*Previous IDs* None
*Obsoletes* None

ERROR: Console Load Error and/or Run-time error ‘429’: ActiveX component can’t create object

Add2Exchange Enterprise Console does not open:

Summary

This error can be caused by several things, however, if your installation was working fine, and you did a MS update and the Add2Exchange Console doesn't open, see the Known Issue section below.

RESOLVED - upgrade to the latest edition using normal procedures.  Make sure you have valid software maintenance to get the upgrade free.

Background History of the issue
July 2018 Security and Quality Rollup  .NET’s nuts report – from here

"The .NET patches released on Patch Tuesday were bad. They were so bad that Microsoft itself has disavowed any knowledge of their actions. On July 20 — 10 days late and $10 short — ‘Softie Rich Lander posted on the official .NET blog:

The July 2018 Security and Quality Rollup updates for .NET Framework was released earlier this month. We have received multiple customer reports of applications that fail to start or don’t run correctly after installing the July 2018 update… We have stopped distributing the .NET Framework July 2018 updates on Windows Update and are actively working on fixing and re-shipping this month’s updates. If you installed the July 2018 update and have not yet seen any negative behavior, we recommend that you leave your systems as-is but closely monitor them and ensure that you apply upcoming .NET Framework updates.

Since that time, we’ve seen some fancy footwork to stop the disease from spreading. It now appears as if the patches are either not available or, if available through Windows Update, aren’t checked for automatic installation. The official apology hasn’t been updated with any word of a fix."

https://www.ghacks.net/2018/07/10/microsoft-windows-security-updates-july-2018-release-overview/
https://www.askwoody.com/2018/the-july-net-patches-are-even-worse-than-you-think/

KB4338815 and KB4054566 are target issues
 

Other Historical Causes for this kind of issue

(Prior to 6/1/2018 and for other types of installations)
There are other (less common) reasons why this error can be received.   On older versions of Exchange and using CDO on the machine, this error can also be gotten when opening the Add2Exchange Console for the first during the installation process. The user receives a “Run-time error ‘429’” error dialog and the Console does not open. CDO is not available on this server or has not been installed yet. Consult the appropriate section of the installation manual and below for your exact Exchange platform fix.

Note:  This error is not directly related to a sync stopping issue, but only to opening up the Console.  TIP: If Add2Exchange is stopping, and you have Outlook installed, most probably you are logging out as the service account,  so don’t.  Keep the service account logged in and lock the machine with that user on and you should be fine.  If rebooting though, have to log in and stop and start the Service and then lock as that user.


Symptom

While opening the Add2Exchange Console, it fails and in Add2Exchange Event log  the user receives a “Run-time error ‘429’: ActiveX component can’t create object” error dialog - either after a MS update or when opening the Add2Exchange Console for the first time during the installation process.
OR
In the Add2Exchange Event log you get a message such as:
Console Load Error: -2147024894 Automation error. The system cannot find the file specified.  At Line 2010 or (some other number for different versions)

Description

Update: 7/30/18   Known Issue
Microsoft issued a bad .net patch which caused issues everywhere.  See the Immediate Fix below.

OR a less likely solution is in Exchange 2000-2010 usage, Add2Exchange could be installed on a VM, standalone or the Exchange server which already has Collaboration Data Objects, installed as part of Exchange 2003, separately for Exchange 2007 and 2010. On these types of install, either the CDO component was never installed or has become unregistered.  if you are installing Add2Exchange on a server other than the Exchange server, this component is missing or unregistered from the server on which Add2Exchange is installed. This is the error you receive when Add2Exchange attempts to use the missing component.

If you are running Exchange 2013, 2016 or Office 365, you will be using Outlook for the Mail profile, and CDO is not installed. A recent update 6/28/18 created an issue which should be resolved shortly.  See the Immediate Fix below.. 

Resolution

Update: 7/30/18  This is an Immediate Fix.  Make sure you have valid Software Assurance to get the update for free.

Stop the Add2Exchange Service.
Uninstall Add2Exchange Enterprise and Recovery and Migration if installed
Download and install latest from Downloads. Download the "Update" if Console has ever opened or "Full" version if it has not.

Uninstall the older version, (again, make sure you have valid Software Assurance and can receive the upgrade free) 
Install the newer versions
Open the Add2Exchange Console.  It should open. 
If it does not open, see the scripts below.

If the Add2Exchage Console still Fails to open: open a ticket online
 If this doesn't work for you, please Open a Ticket for DidItBetter Support 

Exchange 2013 - 2016 and Office 365


Add2Exchange - Error opening Console using Outlook on the machine instead of CDO

 

Currently, with the "no Console access" should still sync fine, but no Console access. 
See Immediate Fix above.

 

Exchange 2003

If you are installing on the Exchange server, you already have the CDO component installed and it simply needs to be registered with Windows. If you are installing on a server other than the Exchange server, you need to install the Exchange System Management tools. See the appropriate following section.

If replication is being done on the Exchange Server – Register CDO

1. If installed on the Exchange Server.  In Explorer, find the location of your Exchange install. Typically this will under be \Program Files\Exchsrvr on your C: drive or whichever drive you typically install programs.
2. Verify that the file cdo.dll exists in the “bin” subdirectory of your Exchange install.
3. From the Start menu, select Run… and run cmd.exe.
4. Run the following command. The use of quotes is important and edit for your specific location:

regsvr32 "C:\Program Files\Exchsrvr\bin\cdo.dll"

If installed on a separate Synchronization Server –
Make sure UAC is off in the registry and reboot if it is, and then unregister and reregister CDO.dll usually installed to C:\Program Files (x86)\Mapi\

Exchange 2007 - 2010

Install the Exchange 2007 MAPI/CDO subsystem from the extracted Add2Exchange Setup files located in
\a2e-enterprise.xx.x.xxxx.xxxx\Preinstaller\ExchangeMapiCdo.MSI.

Make sure UAC is off in the registry and reboot prior.
Uninstall Collaboration Data Objects and reboot, and then reinstall from the directory above. 

Disabling UAC

  • Open regedit
  • Go to Start, Run
  • At the common prompt type regedit and press enter to open the Registry Editor
  • Drill down to the System folder found under
  • When you click on the System folder, on the right hand side you will see a key for EnableLUA
  • Double click to open the Edit DWORD Value window. Under Value data: change from 1 to 0
  • Click OK
  • Close regedit and reboot if it has been changed

 

Applies To

  • Add2Exchange Enterprise
    Recovery and Migration Manager

Keywords: CDO

Live Help for Exchange Sync