Err Msg: Cannot Find File or One of its Components

Last reviewed: April 4, 1997
Article ID: Q166389
The information in this article applies to:
  • Microsoft Windows 95
  • Microsoft Windows 95 OEM Service Release version 2
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0

SYMPTOMS

When you double-click a file that is associated with a program, the program may start but you may receive the following error message

   Cannot find file <file path> (or one of its components).
   Check to ensure the path and filename are correct and that
   all required libraries are available.

where <file path> is the path to the file being loaded. When you click OK, the file is loaded correctly.

CAUSE

The Use DDE setting is enabled, or the information in that section is incorrect.

RESOLUTION

To resolve this issue, follow these steps:

  1. Double-click My Computer.

  2. On the View menu, click Options.

  3. Click the File Types tab. To modify an association, click the file type in the Registered File Types box, and then click Edit.

    To determine which file type is causing the problem, use the right mouse button to click a file of the appropriate type in Windows Explorer, and then click Properties. The line titled Type lists the entry in the Registered File Types box that needs modification.

  4. Click the Use DDE check box to clear it.


Additional query words: 4.00
Keywords : kberrmsg kbui NTSrvWkst osr2 win95 winshell
Version : 4.0 95
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.