Causes of Runtime Error 429
Runtime error 429 can be found when you attempt to automate office applications. An example would be is when you generate a script to export information from an Access database and put that information into an Excel sheet, and then create a chart based on that data which you got from Access. To automate an office application, you may use the automation server carried on from the Windows COM architecture. What the automation server does is allow Office applications to open internal functions as COM or executable objects and automate tasks that are usually done using menus. The usual system error message that you will receive goes like this:
Run-time error ‘429’: ActiveX component can’t create object
An error 429 usually occurs because you are either using the Create Object function or the New operator used in Microsoft Visual Basic (VB) in order to create a Microsoft Office Application occurrence. Below are the steps to fix Runtime Error 429.
Automation Server Troubleshooting to Fix Error 429
In order to avoid server problems, make sure that you don’t have any faulty application setups or configurations. Troubleshoot the error by first, making sure that the Office application that you are using is installed on the local drive and also check if you are able to run the program manually by hitting Start>Run, type the application e.g. Excel, and press OK. If the program will not open through that, then chances are it will not run through automation.
Re-Registering the Application
In order to run the applicatoin, you must first re-register it. You will need to re-register the Office application in the Run dialog box. Type C:\Program Files\Microsoft Office\Office\Excel.exe/regserver then press OK.
Remember: The path depends and may change according to your operating system and Office version.
Verifying Registry Entries
If you find out that there are missing registry values causing the error, follow these steps to repair Error 429.
- On the Run dialog box, type the Regedit command to open the Registry Editor window.
- Find your way to the registry key HKEY_CLASSES_ROOT\CLSID.
- Make sure that the LocalServer32 key is using the correct short path name which is DOS 8.3, to point to the location of the application.
- Take note that CLSID are class identifiers which are associated with ActiveX or OLE 2.0 objects, created by a certain component or server. All CLSID related to automation servers are found under the HKEY_CLASSES_ROOT\CLSID key. CLSID which are associated with Office applications are as follows:
Program CLSID
Word {000209FF-0000-0000-C000-000000000046}
Excel {00024500-0000-0000-C000-000000000046}
PowerPoint {91493441-5A91-11CF-8700-00AA0060263B}
Outlook {0006F03A-0000-0000-C000-000000000046}
Access {73A4C9C1-D68D-11D0-98BF-00A0C90DC8D9}
- To know which the correct path is, copy the value in between the LocalServer 32 key, paste it in the Run dialog box, delete or automate, and then click OK. If the application runs, then it means that you have registered it properly. If it doesn’t, then change the path for the application in the LocalServer32 key using the short path name in order to fix it.
Normal.dot or Excel.xlb Corruption
You may also encounter Error 429 when automation has failed because of the corruption of the Normal.dot template or Excel.xlb resource file. In order to check if errors are generated due to problems with these files, search for all Normal.dot and Excel.xlb files on your system and rename all of them. Afterwards, rerun your automation test and see if it runs. If the automation pushes through then the deleted files will be recreated along with their respective application. However, if it does not work, you can rename the files back to their original names in order to continue using them.
Note: The two files which you renamed will be recreated using Microsoft Word and Microsoft Excel, if found missing.
Indeed, the most common reasons which cause Runtime Error 429 are problems with the automation server of Office applications. As a summary, you may either re-register the application causing the error or verify and fix the problem in the LocalServer32 under the CLSID key in the system registry. Another way is to check and repair corrupted Normal.dot and Excel.xlb files by renaming them and allowing the applications to recreate these files. The best way however to prevent registry-related problems such as Runtime Error 429 is to acquire a registry cleaner which is reliable to help you prevent your system registry files from being corrupted and ensure that your computer is working at its utmost best.
You can scan your PC Free below.
Mail this post
|
Run a Free PC Scan NowSelect Your Operating System: |
