Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/104658

From BetaArchive Wiki

UNC Names in Icon Properties May Cause File Not Found Errors

Q104658



The information in this article applies to:


  • Microsoft Windows NT Server version 3.1
  • Microsoft Windows NT Workstation version 3.1
  • Microsoft Windows NT Advanced Server, version 3.1





SYMPTOMS

If you create an icon which uses a Universal Naming Convention (UNC) path name for a program in combination with a data file, error messages indicating the data file could not be found may appear when you choose it.

Steps to Reproduce Problem

  1. On computer 1, use Write to save a file called TEST.WRI. Place this file in a shared directory, such as \TEST. Also copy WRITE.EXE into the TEST directory.
  2. On computer 2, create an icon with the following Properties:

    Description: Test
    Command Line: \\MACHINE1\TEST\WRITE.EXE TEST.WRI

When you try to use this icon to open Write and the TEST.WRI file, you will receive a "File not found" error message even though the file is in the TEST directory.

This error message does not occur if a standard network redirection (created with File Manager) is used, such as X:\WRITE.EXE TEST.WRI.



CAUSE

Once the network connection is made with the UNC name and the application is loaded, the network connection is broken. Because the network connection no longer exists, the data file cannot be found. This behavior is by design.



RESOLUTION

To prevent error messages using UNC names in icons, also specify a UNC name for the location of the data file to be loaded, such as:

Command Line: \\MACHINE1\TEST\WRITE.EXE \\MACHINE1\TEST\TEST.WRI

Additional query words: prodnt

Keywords : kbnetwork
Issue type :
Technology : kbWinNTsearch kbWinNTWsearch kbWinNTW310 kbWinNTSsearch kbWinNTS310 kbWinNTAdvSerSearch kbWinNTAdvServ310 kbWinNTS310xsearch kbWinNT310xSearch kbWinNTW310Search


Last Reviewed: October 27, 2000
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.