How to Fix Runtime Error 429
Run time errors occur frequently on Microsoft Windows, and one of the most common is runtime error 429. Many of these errors occur when attempting to automate the tasks in Microsoft Office applications. The primary cause of runtime error 429 is the use of the CreateObject function or the New operator in VB (Visual Basic) to create an Office application instance. When this error occurs, you typically get an error messages that reads: “Active X component can’t create object.”
Troubleshooting Runtime 429
Runtime error 429 is usually related to automation server issues that occur due to application bugs and misconfigurations. To troubleshoot this problem, it is important to first make sure the application in question is installed on your local hard drive and can be run manually.
For example, if the application is Excel, open the “Start” menu, hit “Run,” type “Excel” into the command field and click “OK.” If Excel doesn’t open, that means the application will not work through automation.
In order to resolve this issue, you need to re-register the application. Let’s use Excel for example. To re-register this application, type “C:\Program Files\Microsoft Office\Office\Excel.exe /regserver” into the command field, and press “OK.” Keep in mind that the actual path all depends on your Windows operating system, as well as the version of Microsoft Office you are using.
Verify Entries in the Registry
A runtime error 429 could also occur when values in the Windows registry are missing or corrupt. To launch the registry editor, type “Regedit” in the command field and click “OK.” Next, find the “HKEY_CLASSES_ROOT\CLSID” registry key. From here, you want to verify that the “LocalServer32″ key is using the path name “DOS 8.3″ to point to Excel’s location. To determine the right path, copy the LocalServer32 key’s value, paste it into the “Run” command field, and click “OK.” You will know the application is registered if it runs automatically. If it doesn’t, you may need to change the application path to fix your run time errors.
Address Corrupt Files
Corrupted Excel.xlb and Normal.dot templates have also been known to fail automation processes and generate runtime error 429. To find out if there are problems with these files, run a search for all Excel.xlb and Normal.dot files on your system and rename them. You can then rerun the automation process to see if it works. If it does, the files will be recreated to their respective applications. If automation fails, assign the files with their original names as they are probably not the source of the problem.
Overcoming Runtime Error 429
Automated tasks in Microsoft Office applications are the biggest cause of run time errors. The best way to manually solve runtime error 429 is to re-register the application giving you the error, or verify and fix it through the Windows registry. Since Excel.xlb and Normal.dot files can also be the source of the problem, they should be checked for signs of corruption as well. You can help prevent such issues by installing a reliable registry cleaner on your computer. This type of program will protect registry keys and keep your system performing at an optimal level.