What is "runtime error 429”?
Runtime error 429 is generated when an automation sequence fails to operate the way it is scripted. The runtime error 429 occurs in all the Office modules when there is a glitch in the automated sequence script.
Microsoft Visual basic (VB) is the program that runs these automation sequences, so a combination of Visual Basic plus all the Office modules is responsible for generating this error.
Applications affected with runtime error 429 are:
- All Modules of Microsoft Office like Word, Excel etc
- Microsoft Visual Basic Version 5,6,7
Error appearing on the screen
“Run-time error '429': ActiveX component can't create object”
What are the main causes of runtime error 429?
Automation sequence is used in the Windows environment to get a series of jobs done automatically. Downloading a table from an online database and then placing the table on Excel and then generating a bar chart next to it. This is an example of a sequence and VB generates this automatic sequence by creating a script and if there is a glitch in any of these sequences, runtime error 429 is generated.
The main reasons behind this error are:
- Problem with the automation server
- Problem with the Office Application
- Missing or Damaged Office Component
What should I do to fix the runtime error 429?
You may perform the following steps to resolve the issue.
Step 1 – Resolve Problems with the Automation Server
Inspect the code and the objects involved in the automated sequence and then check the automation Server. Most of the time the error occurs in the CreateObject or the New option in the server application. You can try to re-register the Office application by performing the following steps to resolve the issue:
- Click Start and select Run .
- Type the path of the server with /RegServer in the end and click OK .
For example, if you are using Excel, Type C:\Program Files\Microsoft Office\Office\Excel.exe /RegServer and press OK . Remember RegServer is not case sensitive, and the path depends on the location where Office software is installed on the system.
When you perform this step, the application is re-registered on the system. If this doesn’t solve the issue try the next step.
Step 2 – Verify the Registry Entries for Office Applications
You can run the Registry Editor tool to check for the Office application entries. To do so follow these steps:
- Click Start and then Run.
- Type Regedit and press Enter.
- Navigate to HKEY_CLASSES_ROOT\CLSID key in the Registry Editor window that is displayed.
- Ensure that LocalServer32 key uses the correct path and it matches to the location of the file.
The common Office CLSID keys are:
To find the correct path names, type each of the paths in the Run dialog box with ‘/ automate’ in the end and if the application runs fine, then it is installed properly. If the application does not run, then you will need to change the path in the LocalsServer32 key. If this doesn’t solve the problem, try the next step.
Step 3 – Resolve Problem s with Office Applications
This is when you are calling on one of the office applications and the module doesn’t start when the automation sequence is run. Let us look at an example of Excel, to check if excel is working fine.
- Click Start.
- Select Run.
- Type Excel and click OK.
If Excel launched and runs fine, you will not face any issues. Otherwise, you can delete the templates of Excel and Word to solve the problem. Every time you start Excel or Word or any of the Office applications, these templates are loaded and if they are corrupt, the application will fail to start. You can Search and delete the Normal.dot and Excel.xlb files from the system. These two templates are recreated once the application is started and this will solve the problem.
If the above steps do not solve the problem, you can run the repair feature of Office with the help of its installation CD. You can either repair or reinstall a fresh copy. This will take care of all the problems with runtime error 429.