Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You receive run-time error 429 when you automate Office applications
Article ID: 828550 - View products that this article applies to.
If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business
|Office Server||CLSID key|
To determine whether the path is correct, follow these steps:
- Click Start, and then click Run.
- Copy the value from the registry, and then paste the
value in the Run dialog box.
Note Remove the /automation switch before you run the application.
- Click OK.
- Verify that the application runs correctly.
If the application runs after you click OK, the server is registered correctly. If the application does not run after you click OK, replace the value of the LocalServer32 key with the correct path. Use a short path name if you can.
Note For systems that run Microsoft Windows 2000 or for systems that run Microsoft Windows XP, you may find multiple copies of these files. There is one copy of each of these files for each user profile that is installed on the system.
Temporarily rename the Normal.dot files or the Excel.xlb files, and then rerun your automation test. Word and Excel both create these files if they cannot find them. Verify that the code works. If the code works when a new Normal.dot file is created, delete the files that you renamed. These files are corrupted. If the code does not work, you must rename these files back to their original file names to save any custom settings that are saved in these files.
Examine the systemSystem configuration may also cause problems with the out-of-process COM servers creation. To troubleshoot, use the following procedures on the system where the error occurs:
- Determine whether the problem occurs with any out-of-process server. If you have an application that uses a particular COM server (such as Word), test a different out-of-process server to make sure that the problem is not with the COM layer itself. If you cannot create an out-of-process COM server on the computer, reinstall the OLE system files as described in the "Reinstalling Microsoft Office" section of this article or reinstall the operating system to resolve the problem.
- Examine the version numbers for the OLE system files that
manage automation. These files are typically installed as a set. These files
must match build numbers. An improperly configured setup utility can mistakenly
install the files separately. This causes the files to be mismatched. To avoid
problems with automation, examine the files to make sure that the files builds
The automation files are located in the Windows\System32 directory or in the Winnt\System32 directory. Examine the following files.To examine the file version, right-click the file in Windows Explorer, and then click Properties. Notice the last four digits of the file version (the build number) and the date that the file was last modified. Make sure that these values are the same for all the automation files.Collapse this tableExpand this table
File name Version Date modified Asycfilt.dll 3.50.5014 September 04, 2002 Oleaut32.dll 3.50.5016 September 04, 2002 Olepro32.dll 5.0.5014 September 04, 2002 Stdole2.tlb 3.0.5014 September 04, 2002
Note The earlier version numbers and the earlier dates are retrieved from a computer that uses a Windows Server 2003 computer with Office 2003 installed. These numbers and dates are just used as examples. Your values may be different.
If the files do not match the build numbers or the modified dates, download a self-extracting utility that updates your automation files.
For more information about how to access the run-time files, click the following article number to view the article in the Microsoft Knowledge Base:235420(http://support.microsoft.com/kb/235420/ )Vbrun60sp4.exe installs Visual Basic 6.0 SP4 run-time files
- Use the System Configuration utility (Msconfig.exe) to examine the services and system startup for third-party applications that might restrict running code in the Office application.
For more information about Msconfig.exe, click the following article number to view the article in the Microsoft Knowledge Base:
310560For example, Outlook Automation applications may fail because you are running an antivirus program that has "script blocker" features.(http://support.microsoft.com/kb/310560/ )How to troubleshoot configuration errors by using the System Configuration utility in Windows XP
Note Only disable the antivirus program temporarily on a test system that is not connected to the network.
Alternatively, follow these steps in Outlook to disable third-party add-ins:
- On the Tools menu, click Options.
- On the Other tab, click Advanced Options.
- In the Advanced Options dialog box, click Add-In Manager.
- Click to clear the check box for any third-party add-in.
- Restart Outlook.
Reinstall OfficeIf none of the previous procedures resolve the problem, remove Office and then reinstall Office. Microsoft recommends that you remove the existing version first, and then reinstall Office by using the original installation disks.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/219423/ )How to remove the Office 2000 CD1
(http://support.microsoft.com/kb/158658/ )How to completely remove Microsoft Office 97
For more information about troubleshooting the '429' error message, click the following article number to view the article in the Microsoft Knowledge Base:
240377For more information about Office automation and code samples, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/240377/ )How to ensure Jet 3.5 is installed correctly (part I)
Article ID: 828550 - Last Review: April 15, 2013 - Revision: 5.5
- Microsoft Office Excel 2007
- Microsoft Office SharePoint Designer 2007
- Microsoft Office Outlook 2007
- Microsoft Office Outlook 2003
- Microsoft Office PowerPoint 2007
- Microsoft Office PowerPoint 2003
- Microsoft Office Word 2007
- Microsoft Office Access 2007
- Microsoft Office Access 2003
- Microsoft Visual Basic 5.0 Enterprise Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 5.0 Professional Edition
|kbexpertisebeginner kbtshoot kbprogramming kberrmsg kbautomation kbinfo KB828550|
- Brasil (Português)
- Česká republika (Čeština)
- Deutschland (Deutsch)
- España, Latinoamérica (Español)
- France (Français)
- Italia (Italiano)
- Magyarország (Magyar)
- Nederland (Nederlands)
- Polska (Polski)
- Portugal (Português)
- Türkiye (Türkçe)
- Việt Nam (Tiếng Việt)
- Ελλάδα (Ελληνικά)
- Россия (Русский)
- ไทย (ไทย)
- 대한민국 (한국어)
- 中国 (简体中文)
- 台灣 (繁體中文)
- 日本 (日本語)