subject: How to Fix Runtime Error 429 [print this page] How to Fix Runtime Error 429 How to Fix Runtime Error 429
Unexpected problems with computer applications often lead to runtime errors. Each error has been numbered to provide an indication as to the cause of the problem.
What is Runtime Error 429?
Runtime error 429 typically arrives with the message "Object creation failed" or a similarly worded message such as "ActiveX component can't create object." Most commonly, this error occurs because the program that the user is trying to access has been corrupted. Since the program cannot complete its action and create the requested object, runtime error 429 is generated.
In particular, this error often occurs when activating Microsoft Visual Basic in connection with the Microsoft Office application. The user attempts to use the automated feature by accessing the CreateObject function or the new operator in Microsoft Visual Basic feature.
How to Fix Runtime Error 429: Troubleshooting and Checking Automation Server
If the application set up or configuration is at fault, you can easily check this by looking to see that the application has been installed on the operating system that you are using as well as checking to see that you can run the application manually. If the application does not run using the following directions, then it will not work when you are trying to use the automation feature either.
Navigate to Start.
Select Run.
Type the name of the application that you are checking.
Select ok.
How to Fix Runtime Error 429: Re-register the Application
Navigate to Start.
Select Run.
Type the path for the server adding /regserver at the end into the empty box that appears. For example, if you are trying to access Excel, you might type "C:Program FilesMicrosoft OfficeOfficeExcel.exe/regserver."
Select ok.
How to Fix Runtime Error 429: Run a Registry Cleaner
Download a registry cleaner.
Install the registry cleaner.
Run the registry cleaner to fix broken or missing files.
How to Fix Runtime Error 429: Verify the Registry Entries
Incorrect registry errors will also generate runtime error 429, therefore, you need to use the following set of directions to check whether the entries are accurate.
Navigate to Start.
Select Run.
In the open box, type "regedit" to open the Registry Editor window.
Select ok.
Navigate to HKEY_CLASSES_ROOT/CLSID. This is the registry key that you need to look at.
Now, you need to check that the LocalServer32 key is using the correct short path name to indicate the location of the application that is generating the runtime error. Use the following list to verify that the key is accurate: Access: {73A4C9C1-D68D-11D0-98BF-00A0C90DC8D9}
Now you need to check that the path is entered correctly by completing this set of directions:
Navigate to Start.
Select Run.
Copy the value that is listed in the registry and enter it into the opened dialog box. Remove the /automation.
Select ok and verify that the application runs. If it does so, it is entered correctly. If it does not, then you need to replace the value of the LocalServer32 key with the correct one.
