Runtime errors are computer errors that commonly plague the Windows operating system and various Microsoft applications. They are typically the result of unforeseen problems in applications installed on a computer. For the most part, these errors occur due to conditions that were not addressed during the development of a particular application. To give you a better understanding of runtime errors, let us review common Microsoft errors that often occur on Windows and XP computers.

Microsoft Runtime Error 429

When encountering runtime error 429, you will be presented with a message that reads: “Active X component can’t create object.” This error is usually generated when you try to automate tasks within a Microsoft Office application, a problem that is common in Windows XP.

Runtime error 429 often occurs if the task you are trying to automate requires the use of the CreateObject or VB (Visual Basic) New operator function to create an Office instance. This Microsoft error might occur because one of the following situations:

• The application in question is not installed properly or contains corrupt files.

• Essential values in the registry are missing or corrupt.

• Template objects such as Excel.xlb and Normal.dot are corrupt.

To fix runtime error 429, you can try re-registering the application that is presenting the problems. For example, if Microsoft Word is the culprit, open the file prompt, navigate to the folder that contains the Word.exe file, run the word.exe\regserver command, and then click “OK.” If the template files are causing the issue, deleting those files and recreating them should solve the problem. Once you restart the application, the files will be recreated and the program should work fine.

Microsoft Runtime Error 339

Runtime error 339 typically occurs when the MCI32.OCX (or any of the related .OCX file)file or one of its dependent components is not properly registered. This type of error will give you a message that reads: “a file is missing or invalid.” By default, Vista is only shipped with the VB 6.0. files required to make it compatible with earlier versions of Windows and Office applications. For this reason, users who upgrade from XP to Vista may get runtime errors when trying to run applications that use MCI32.OCX files for the simple fact that they are not included on the Vista operating system.

The best way to fix runtime error 339 is to uninstall and reinstall the application that is prompting the MCI32.OCX errors. A registry cleaner may be required to make sure that no entries are left in the registry as a result of the un-installation. You may need to shutdown your OS and reboot too.

If the error still occurs, you can download the latest version of the MCI32.OCX file online, copy it to the system folder and run the “regsvr32.exe C:\windows\system32\MCI32.OCX” command to register it.

The Bottom Line on Microsoft Errors

Most runtime errors are the result of programming flaws that can’t be prevented on your part. On a good note, you can reduce their occurrence by keeping your operating system and applications fresh with the latest updates and patches available to address any errors that might be discovered.

For some of the most known runtime errors, Microsoft offers solutions directly on their website to solve the issue. Not only do these fixes help eliminate Windows errors, but they also improve the performance and security of your computer.

If you enjoyed this post, make sure you subscribe to my RSS feed!