Article ID: 185126 - View products that this article applies to.
This article was previously published under Q185126
When you try to start a (COM) Automation server or embed an OLE object, you may receive one of the following error messages:
Microsoft Visual Basic:
Microsoft Visual C++:
Run-time error '429': ActiveX component can't create object
Run-time error '53': File not found
Microsoft Visual FoxPro:
0x80070003: The system cannot find the path specified.
Microsoft Office (OLE):
DCOM error: %1 is not a valid Windows NT application
This problem only occurs on computers that are running Microsoft Windows NT 4.0.
Failed to create object.
[Office App Name] can't start the application required to open this object.
This problem can occur if the ActiveX server is installed to a long folder path that may conflict with a similar path on the computer. Usually, the problem occurs when the path of the ActiveX server contains spaces and another path on the computer is the same, up to a space. For example, suppose you have this problem when you try to automate a Microsoft Office application. If you installed Microsoft Office to the default path:
C:\Program Files\Microsoft Officeand you also have a folder named C:\Program or C:\Program Files\Microsoft, you might experience this problem. A conflicting folder can also appear on a different drive.
Here are three resolutions:
322756To edit the registry, run the RegEdit.exe utility. The LocalServer32 key for your ActiveX server are located in the HKEY_CLASSES_ROOT\CLSID section of the registry.
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To locate the LocalServer32 key for your ActiveX server, choose Find from the Edit menu and specify the file name of your ActiveX server (or search on the ProgID). For example, to find the LocalServer32 key for Microsoft Excel, search for "Excel.exe." You might need to press the F3 key to Find Next until you see the LocalServer32 key. For the case of Microsoft Excel, the LocalServer32 value might be:
C:\Program Files\Microsoft Office\Office\excel.exe /automationAssuming that the short path is C:\Progra~1\Micros~1\Office, you can change the LocalServer32 value to:
C:\Progra~1\Micros~1\Office\excel.exe /automationYou should only have to change one LocalServer32 key for your ActiveX server. To determine exactly what to specify for the short path, check the properties of the ActiveX server file in the Windows Explorer. See the MS- DOS name setting in the Properties window. Also check the properties of the folder in which the ActiveX server resides so that you can determine the complete short path of your ActiveX server.
Another way to determine the short path is to use the GetShortPathName API function. For additional information about using the GetShortPathName APIfunction, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/175512/EN-US/ )HOWTO: Get a Short Filename from a Long Filename
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.
Steps to Reproduce Behavior
For additional information, please click the article numbers below to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/173430/EN-US/ )Off97: Error Inserting an Office Object Under Windows NT 4.0
(http://support.microsoft.com/kb/244264/EN-US/ )INFO: Error 429 When Automating Office Applications
(http://support.microsoft.com/kb/167591/EN-US/ )ACC97: "Microsoft Access Can't Find the Wizard" Error Message
(http://support.microsoft.com/kb/189366/EN-US/ )ACC97: Run-Time Error 429 Message Using Run-Time Application
Article ID: 185126 - Last Review: February 12, 2007 - Revision: 4.3