Runtime Error 429 is a problem that is reported to occur on many Windows systems recently, and it usually indicates there is an issue somewhere in the automation in your Microsoft Office applications. The error typically shows up when you try to automate Office application files using Visual Basic macros. The error is caused by the Windows Component Object Model (COM) being unable to create the requested automation object. You need to resolve the issues surrounding COM to be able to automate Microsoft applications successfully. This tutorial will help you resolve runtime error 429 easily.
What Causes Runtime Error 429?
Runtime error code 429 is most often caused by one of the following issues:
- There is a mistake in the application.
- There is a mistake in the system configuration.
- A component is missing.
- A component is damaged.
Alternatively, the error can also be caused by problems inside the Windows registry. You need to identify exactly what the source of the problem is, and then fix it efficiently – which can be done by performing the steps described below:
How To Fix Runtime Error 429
Step1 – Make Sure That Macros Can Be Used In The Program
To resolve the error, the first thing you need to do is ensure that your application is able to work with automation. Sometimes you will find that Microsoft Office doesn’t have Macros enabled. If this is the case, then this is the likely reason you are seeing error. To verify if your application is compatible with automation, simply follow these simple steps:
- Click Start > Run.
- Type the name of the application. For example, type “Word” to troubleshoot Microsoft Word.
- Press OK.
Step 2 – Register The Application Again
You also need to make sure the application is properly registered. Re-registering the application will enable the automation server to process the application correctly. If it is not registered with the automation server, the error will occur. You re-register the application by following these steps:
- Click Start > Run.
- Type “C:\Program Files\Microsoft Office\Office\Word.exe/regserver” and press Enter.
- If MS Word is located in a different path, type the correct path with Word.exe/regserver at the end, and press Enter.
Step 3 – Rename Vital Word Files (Normal.dot World.xml)
This step is essential as there are times when Runtime Error 429 can occur due to the failing of automation, which is down to the Normal.dot template or the Word.xml file becoming damaged. You need to rename vital Word files to resolve this issue, which you can do by following these simple steps:
- Locate all Normal.dot and Word.xml files on your system by using the search function.
- Rename each file included in the search results.
- Run your automation test again to see if it runs. If the issue has been resolved, it means the deleted files will be recreated along with their application.
- However, if this is not the case, then rename the files back to their original names to re-use them.
Step 4 – Clean The Registry
The registry of Windows can often cause serious errors to show up on your PC, including the runtime error 429. The registry is a large central database that is used to store file settings. It is an important module for your Windows system, as it uses these settings to remember the configuration of all your files and programs. However, it is prone to errors, either corrupted settings or missing settings.
When this happens, errors show up. To fix runtime error 429, you need to clean the registry using a registry cleaner to effectively detect and repair broken registry keys. We highly recommend this tool that has been consistent in fixing 99% of system errors allowing you to use your PC without errors.