This article was previously published under Q185126
This article has been archived. It is offered "as is" and will no longer be updated.
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:
Run-time error '429': ActiveX component can't create object Run-time error '53': File not found
Microsoft Visual C++:
0x80070003: The system cannot find the path specified.
Microsoft Visual FoxPro:
DCOM error: %1 is not a valid Windows NT application
Microsoft Office (OLE):
Failed to create object. [Office App Name] can't start the application required to open this object.
This problem only occurs on computers that are running Microsoft Windows NT 4.0.
This problem can occur if the ActiveX server is installed to a long folderpath that may conflict with a similar path on the computer. Usually, theproblem occurs when the path of the ActiveX server contains spaces andanother 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 Officeapplication. If you installed Microsoft Office to the default path:
C:\Program Files\Microsoft Office
and you also have a folder named C:\Program or C:\Program Files\Microsoft,you might experience this problem. A conflicting folder can also appear ona different drive.
Here are three resolutions:
Reinstall the ActiveX server to a short folder path. For example, you can reinstall Microsoft Office to C:\Office97. To reinstall to a differentpath, you should first uninstall the application before reinstalling.
Uninstall any applications that are installed in the conflicting folder (for example, C:\Program), and then delete or rename this folder so that it no longer conflicts. After you rename or delete this folder, you might need to re-register or reinstall your ActiveX server application to ensure it is properly registered.
Edit the LocalServer32 key in the Registry for the ActiveX serverapplication. The LocalServer32 key specifies the path to the ActiveXserver. Change the path from a long path name to a short path name.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To edit the registry, run the RegEdit.exe utility. The LocalServer32 keyfor your ActiveX server are located in the HKEY_CLASSES_ROOT\CLSIDsection of the registry.
To locate the LocalServer32 key for your ActiveX server, choose Find fromthe Edit menu and specify the file name of your ActiveX server (or searchon the ProgID). For example, to find the LocalServer32 key for MicrosoftExcel, search for "Excel.exe." You might need to press the F3 key to Find Nextuntil you see the LocalServer32 key. For the case of Microsoft Excel, theLocalServer32 value might be:
Assuming that the short path is C:\Progra~1\Micros~1\Office, you can changethe LocalServer32 value to:
You should only have to change one LocalServer32 key for your ActiveXserver. To determine exactly what to specify for the short path, check theproperties of the ActiveX server file in the Windows Explorer. See the MS-DOS name setting in the Properties window. Also check the properties of thefolder in which the ActiveX server resides so that you can determine thecomplete short path of your ActiveX server.
Another way to determine the short path is to use the GetShortPathName APIfunction. For additional information about using the GetShortPathName APIfunction, click the article number below to view the article in the Microsoft Knowledge Base:
175512 HOWTO: Get a Short Filename from a Long Filename
Microsoft has confirmed this to be a bug in the Microsoft productslisted at the beginning of this article.
Steps to Reproduce Behavior
Install Microsoft Office 97 to C:\Program Files\Microsoft Office.
In Visual Basic, start a new project.
Add the following code to the Form_Click event of Form1:
Dim x as Object Set x = CreateObject("Excel.Application") Msgbox x.Name
Press the F5 key to run the project and click the Form. Result: MsgBox displays "Microsoft Excel."
Stop the project.
Create a new folder named C:\Program.
Press the F5 key to run the project again, and click the Form.
Result: The CreateObject function fails with the following error: