Runtime Error 429 – How to Fix It?

Have you ever faced ‘Run-time error 429 – ActiveX component can’t create object’ while running any application? One of the common problems, the error occurs when one tries to run Microsoft Visual Basic application to create macros or similar objects in MS-Office applications such as Microsoft Word, Excel etc.

Why Runtime Error 429 Occurs?

• Corrupted/missing office component missing, install Microsoft Scripting Engine
• Corrupt registry entries
• Wrong system configuration
• Office application issue

How to Fix Guide:

Ensure that you have installed the latest Windows service pack.

Run registry repair tool – Download and install registry repair tool to repair the damaged registry entries. Save the tool to your desktop or preferred location and run it.

Download and install new Microsoft Windows Script – Remove the previous Microsoft Windows Script software and its registry entries.

• Open your internet browser (viz. Internet Explorer or Firefox etc.), type the link in the address bar, http://www.microsoft.com/downloads/en/details.aspx?FamilyID=47809025-d89..., this will take you to the desired page and correct the error.
• Click on the download button, wait for sometime, when the window appears, and click on ‘Save File’. Save the file to your preferred location to download the file.
• When the download is completed, double click on the file icon to launch the Microsoft installation wizard.
• Follow the instructions and finish the installation. Once completed, there will be no longer
Runtime 429 errors

If the issue still persists, check that you have installed the latest, correct version of Microsoft Windows Script. If it is not the correct version then you will have to re-register the .dll file for the software. To re-register the file, you need to go to the ‘Start’ menu, go to ‘Run’. In the ‘Run’ window, type in ‘regsvr32 c:\Windows\System32\vbscript.dll’ (as it is and without quotes) and click on ‘OK’. This will re-register the correct file and resolve the problem.

Use Troubleshoot Automation Server

Check that there are no automation server issues that occur because of the faulty/damaged application configuration or setup. How would you check if the Office application that you are trying to run is currently installed on your system or not and if you are able to run it manually? It is really simple. Check the below steps:

• Click on the ‘Start’ menu> go to ‘Run’
• When the window pops up, type in ‘Excel’ (without quotes) and click on ‘OK’. If the desired application opens up, it means the application is working fine and has no automation issues. If it does not open then the application has issues with automation.
• To overcome this issue, you need to re-register the particular application. For that, open the ‘Run’ window again, type ‘C:\Program Files\Microsoft Office\Office\Excel.exe/regserver’ (as it as and without quotes) in the box and click on ‘OK’. Here, Excel only denotes the example; you can type whatever Office application you have problem with. Kindly note that the application location may vary according to the settings you made to your computer. For example, if you saved your MS-Office suite to D:\ then in the command you will start with D:\ and the rest will remain the same.

Verify Registry Entries

• Click on the ‘Start’ menu> and go to ‘Run’
• When the window appears, type in ‘regedit’ (without quotes) and click on ‘OK’
• When the Windows Registry Editor window opens, click on the ‘+’ sign before the HKEY_CLASSES_ROOT, search through the registry for CLSID,
• Click on the +’ sign before CLSID, you will see a bunch of values, locate the ‘LocalServer32 key’
• Check the keys/values, these values are related to OLE 2.0 and ActiveX control objects, if these values are incorrect, the error 429 will occur. Note all the CLSID values or class identifiers codes. Check the list below to make the point more clear:

Program – CLSID

Word – {000209FF-0000-0000-C000-000000000046}
Access – {73A4C9C1-D68D-11D0-98BF-00A0C90DC8D9}
Excel – {00024500-0000-0000-C000-000000000046}
PowerPoint – {91493441-5A91-11CF-8700-00AA0060263B}
Outlook – {0006F03A-0000-0000-C000-000000000046}
Verify that these entries exist in the registry editor and are corrected as mentioned above. If these are not correct, for example you did not have a correct registry entry for Excel in CLSID, you will need to uninstall and reinstall the particular MS-Office application.

Additional Tidbits:

Update Office application drivers regularly. If some driver has gone faulty or damaged then remove the driver and download and install a latest, compatible driver. Always install the driver for whichever Windows version you are using.

You can also uninstall and reinstall the particular MS-Office application. Remember, when you remove the application also remove its registry entries, otherwise there will be a problem and the application won’t run.
The troubleshooting procedure may seem cumbersome to you if you are not tech-savvy person. I would advise you to consult a certified tech expert to save yourself from frustration.