BUG: OpenFile() Fails When UNC Name Longer Than 11 Characters

Last reviewed: July 23, 1997
Article ID: Q101414
3.10 3.11 WINDOWS kbprg kbbuglist

The information in this article applies to:

  • Microsoft Windows Software Development Kit (SDK) for Windows versions 3.1 and 3.11

SYMPTOMS

OpenFile() successfully opens files with universal naming convention (UNC) names when the server portion of the name is 11 characters or shorter, but fails to open files when the server name is longer than 11 characters. Error code number 2, "File not found," is placed in the nErrCode member of the OFSTRUCT structure passed to OpenFile.

CAUSE

OpenFile() validates filenames before opening them, and in the case of UNC names, allows server names that are 11 characters or shorter only. No attempt is made to open a file with a UNC name longer than 11 characters.

RESOLUTION

To open files with UNC names when the server name is longer than 11 characters, use _lopen().

STATUS

Microsoft has confirmed this to be a bug in the Windows SDK versions 3.1 and 3.11. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

This is not a problem under Windows NT WOW or under Windows 95.

MORE INFORMATION

This problem also affects the File Open common dialog box, because GetOpenFileName() calls OpenFile().


Additional reference words: 3.10
KBCategory: kbprg kbbuglist
KBSubcategory: KrFileIO
Keywords : kb16bitonly KrFileIO kbbuglist kbprg
Version : 3.10 3.11
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: July 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.