ActivX component can't create object

Run-time error 429 means the COM/ActiveX component that the Visual Basic code is trying to create cannot be instantiated.

Typical causes and fixes from the provided material:

1. Class not registered

• The class for the object is missing or incorrectly registered in the system registry, or points to a file that cannot be found.
• Start the application that owns the object; if that does not repair the registration, rerun the application’s setup/installation so it correctly registers its COM classes.

2. Required DLL missing or damaged

• A dynamic-link library that the object depends on is missing or corrupted.
• Ensure all required DLLs for the component are present; if necessary, rerun the setup for that component so its supporting DLLs are reinstalled.

3. Licensed Automation object cannot verify license

• The object is present but is a licensed Automation object and cannot find its license key (for example, a registry entry or a .lic file).
• Make sure the object is properly installed via its setup program or a type/object library so the correct license key is registered.

4. Incorrect use of GetObject

• GetObject cannot be used to obtain a reference to a class created with Visual Basic.
• Use CreateObject or the New operator instead when instantiating a VB-created class.

5. Access explicitly denied or object locked

• The code may be trying to access a data object that is currently locked.
• Retry accessing the object at another time when it is not locked.

6. Automating Office and error 429

• When automating Office via New or CreateObject, error 429 indicates COM could not create the requested Office Automation object.
• Common root causes are mistakes in the application code, system configuration issues, or missing/damaged Office components. Isolate whether the problem occurs only on specific client machines and repair or reinstall Office on those clients if necessary.

If the error occurs when trying to attach to an already running Office application using GetObject or GetActiveObject, the Office instance may not yet be registered in the Running Object Table (ROT). In that case, switch focus away from the Office application (or wait until it loses focus) before calling GetObject/GetActiveObject, or prefer CreateObject/CoCreateInstance to start a new instance.

If the error appears when placing an ActiveX control on a form at design time, the registry information for that control is missing or corrupted; reinstall that ActiveX control or contact its vendor.

References:

• ActiveX component can't create object or return reference to this object (Error 429)
• You receive run-time error 429 when you automate Office applications
• GetObject or GetActiveObject cannot find a running Office application
• Cannot create ActiveX Component
• Component could not successfully create requested object
• A compatible ActiveX component must be a Visual Basic executable or a DLL