XL5: "File Not Found" Error Using References Dialog Box

Last reviewed: June 3, 1997
Article ID: Q120404
The information in this article applies to:
  • Microsoft Excel for Windows, versions 5.0, 5.0c
  • Microsoft Excel for Windows NT, version 5.0

IMPORTANT: This article contains information about editing the Windows 95 registry. Before you edit the registry, you should first make a backup copy of the registry files (System.dat and User.dat). Both are hidden files in the Windows folder.

SYMPTOMS

In a Visual Basic module, if you click References on the Tools menu, you may receive the following error message:

   File Not Found

In addition, when you attempt to open a workbook that contains a module sheet, you may receive the message:

   Error 48: Error in loading DLL

CAUSE

This problem occurs when the following conditions are true:

  • You perform a workstation installation of Microsoft Excel.

    -and-

  • In a Visual Basic module, you click References on the Tools menu.

When you perform a workstation installation of Microsoft Excel 5.0, most of the program files are run from the server, including Xlen50.olb and Vbaen.olb, the Microsoft Excel and Visual Basic for Applications, object library files. By default, these files are listed in the References dialog box as available object libraries. However, when you use the References dialog box in a Visual Basic module as described in this section, and the server uses the universal naming convention (UNC), Microsoft Excel cannot locate these files.

Note that this error may also occur if Microsoft Excel cannot locate the Stdole.tlb file.

WORKAROUND

To work around this problem, copy the Xlen50.olb and Vbaen.olb files to the appropriate location on your computer. For example, copy these files to the following locations.

   File           Folder
   -----------------------------

   Xlen50.olb     Excel
   Vbaen.olb      Windows\System

After you copy the files locally, use the appropriate following procedure.

Microsoft Excel 5.0 Under Windows 3.1:

To edit the Reg.dat file to point to new locations, use the following steps:

  1. In Program Manager, click Run on the File menu.

  2. In the command line box, type "regedit /v" (without the quotation marks).

  3. On the Search menu, click Find Key. In the Find What box, type "win16" (without the quotation marks), and click Find Next.

  4. On the Search menu, click Find Next until you locate the following entry

          WIN16=\\<EXCEL>\XLEN50.OLB.
    

    where <EXCEL> is the network server directory from which you are running Microsoft Excel.

  5. Select the entry and edit the text in the Value box to reflect the new location of Xlen50.olb, for example:

          C:\Files\Xlen50.olb.
    

  6. On the File menu, click Exit. Click Yes to save the changes.

  7. Repeat steps 1-7 to move Vbaen.olb (and Stdole.tlb) and to modify the Reg.dat file to point to its new location.

  8. Restart Microsoft Windows.

Microsoft Excel 5.0 Under Windows NT 3.51:

To edit the registry to point to new locations, use the following steps:

  1. In Program Manager, click Run on the File menu.

  2. In the command line box, type "regedit /v" (without the quotation marks). Click OK.

  3. On the Search menu, click Find Key.

  4. Type the following in the Find What box

          \TypeLib\{000204F3-0000-0000-C000-000000000046}\1.0\9\Win16
    

    and then click Find Key.

  5. Modify the value of this key to use the new path of Vbaen.olb (the value box is at the top of the window below the menu bar) and press ENTER.

  6. On the Search menu, click Find Key.

  7. Type the following in the Find What box

          \TypeLib\{00020813-0000-0000-C000-000000000046}\1.0\9\Win16
    

    and click Find Key.

  8. Modify the value of this key to use the new path of Xlen50.olb (the value box is at the top of the window below the menu bar) and press ENTER.

  9. On the File menu, click Exit. Click Yes to save changes.

  10. Restart Windows.

Microsoft Excel 5.0 Under Windows 95 or Windows NT 4.0:

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows 95. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the Changing Keys And Values online Help topic in Registry Editor (Regedit.exe). Note that you should make a backup copy of the registry files (System.dat and User.dat) before you edit the registry.

To edit the registry to point to new locations, use the following steps:

  1. On the Start menu, click Run.

  2. Type "regedit" (without the quotation marks), and click OK.

  3. In the Registry window, click the plus sign (+) to the left of the following keys, in order

    HKEY_CLASSES_ROOT TypeLib {000204F3-0000-0000-C000-000000000046} 1.0 9

    to open the following registry key:

    My Computer\HKEY_CLASSES_ROOT\TypeLib\{000204F3-0000-0000-C000- 000000000046}\1.0\9

    Then, click the folder to the left of Win16. The following key appears in the status bar:

    My Computer\HKEY_CLASSES_ROOT\TypeLib\{000204F3-0000-0000-C000- 000000000046}\1.0\9\Win16

  4. Click the entry for Vbaen.olb.

  5. On the Edit menu, click Modify.

  6. Change the Value Data to the new path for Vbaen.olb and click OK.

  7. In the Registry window, click the plus sign (+) to the left of the following keys, in order

    HKEY_CLASSES_ROOT TypeLib {00020813-0000-0000-C000-000000000046} 1.0 9

    to open the following registry key:

    My Computer\HKEY_CLASSES_ROOT\TypeLib\{00020813-0000-0000-C000- 000000000046}\1.0\9

    Then, click the folder to the left of Win16. The following key appears in the status bar:

    My Computer\HKEY_CLASSES_ROOT\TypeLib\{00020813-0000-0000-C000- 000000000046}\1.0\9\Win16

  8. Click the entry for Xlen50.olb.

  9. On the Edit menu, click Modify.

  10. Change the Value Data to the new path for Xlen50.olb and click OK.

  11. Repeat steps 3–10 using the following registry keys:

    HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{000204F3-0000-0000- C000-000000000046}\1.0\9

    HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{00020813-0000-0000- C000-000000000046}\1.0\9

  12. On the Registry menu, click Exit.

  13. Restart Windows.

Microsoft Excel 5.0 for Windows NT:

Use the method that corresponds with the version of Windows that you are running and use the criteria in the following table.

   Replace This file   With This File
   ----------------------------------

   Win16               Win32
   Xlen50.olb          Xlen32.olb
   Vbaen.olb           Vbaen32.olb

If you are a network administrator, you may want to perform this workaround with a batch procedure. For more information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q129422
   TITLE     : XL5: Network Admin Method for Updating Registration Database

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

In Microsoft Excel, you can use the References dialog box to create a link to another project (for example, a workbook that contains a Visual Basic module) from the active project. When you reference another project, you can call any Sub or Function procedure within that project without opening the workbook or using the name of the module that contains the Sub or Function.

REFERENCES

For more information about a referenced projects, click the Search button in the Visual Basic Reference and type:

   referenced project


Additional query words: network lanman novell
Keywords : kberrmsg kbprg
Version : 5.0 5.0c
Platform : WINDOWS
Issue type : kbprb


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: June 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.