Fix Excel VBA ActiveX Component Cannot Create Object Error with Acrobat
Question details
The user is encountering VBA errors when attempting to automate Adobe Acrobat from Excel after upgrading to Microsoft 365.
- Product
- Microsoft Excel, Adobe Acrobat XI
- Device & OS
- Windows 10
- Scenario
- Using the CreateObject function or New keyword in an Excel VBA macro to automate PDF tasks with Acrobat.
- Observed behavior
- The macro throws Run-time error 429 ('ActiveX component cannot create object') with late binding, or a compile error ('User-defined type not defined') with early binding.
Verify that you have the full version of Adobe Acrobat (Standard or Pro) installed, as the free Adobe Acrobat Reader does not support COM/ActiveX automation via VBA.
Resolve 32-bit and 64-bit Architecture Conflicts
Microsoft 365 installs the 64-bit version by default, which cannot directly call 32-bit COM components from older software like Acrobat XI.
When you upgrade to Microsoft 365, it is highly likely that Excel runs as a 64-bit application. Because Acrobat XI is an older release, its ActiveX components may only be registered as 32-bit. A 64-bit host program cannot instantiate a 32-bit out-of-process COM object without throwing an ActiveX error.
Open Excel, go to File > Account > About Excel, and look at the top line of the dialog box to see if it specifies 32-bit or 64-bit.
If Excel is 64-bit and your Acrobat XI is 32-bit, you must either uninstall Office and reinstall the 32-bit version of Microsoft 365, or upgrade to a modern 64-bit release of Adobe Acrobat DC.
Add the Missing Acrobat Type Library Reference
If you receive a 'User-defined type not defined' compile error when using the New keyword (early binding), you must link the Acrobat library to your VBA project.
Repair the Adobe Acrobat Installation
During the Windows 10 or Microsoft 365 migration, Acrobat's COM registry keys may have become unregistered or corrupted.
Avoid Legacy VBA Compatibility Issues with WPS Office
If Microsoft 365 architecture changes are breaking your legacy Excel macros and COM add-ins, consider switching to WPS Office. It provides a highly compatible spreadsheet environment with excellent macro support and built-in PDF tools, removing the need for complex third-party automation.
- 1. Download WPS Office: Visit the official WPS website and download the free software suite.
- 2. Install and Launch: Run the setup file, then open WPS Spreadsheets.
- 3. Enable Macros: Open your existing .xlsm file and enable macros to continue working with your VBA scripts seamlessly.
Frequently Asked Questions
Why does CreateObject('AcroExch.App') return Run-time error 429?
Run-time error 429 occurs when the Windows registry cannot locate the requested COM object, or when there is an architecture mismatch (e.g., a 64-bit version of Excel trying to call a 32-bit Acrobat DLL). Ensuring both programs are either 32-bit or 64-bit usually resolves the issue.
What causes the 'User-defined type not defined' error in Excel VBA?
This compile error happens during early binding when your VBA code declares variables specific to an external application (like Acrobat), but the required Type Library reference has not been enabled in the VBA Tools > References menu.
Can I use VBA to automate the free Adobe Acrobat Reader?
No, Adobe Acrobat Reader does not expose the necessary OLE/COM interfaces (such as AcroExch) required for VBA automation. You must have a paid version (Standard or Pro) installed to use CreateObject with Acrobat.
Is Adobe Acrobat XI still supported on Windows 10?
Adobe Acrobat XI reached its end of support in October 2017. While it may still run on Windows 10, it is highly prone to registry and COM compatibility issues following modern updates like Microsoft 365. Upgrading to a newer version like Acrobat DC is recommended for reliable automation.
