DOCUMENT:Q183354 04-MAR-2002 [exchange] TITLE :XCLN: Unable to Attach Files with Long File Names PRODUCT :Microsoft Exchange PROD/VER::5.0 OPER/SYS: KEYWORDS:kbusage ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Exchange Windows NT client, version 5.0 ------------------------------------------------------------------------------- SYMPTOMS ======== When you try to attach a file with a long file name, the following error message appears: The file could not be opened. This message appears when you try to attach files with file names of 12 or more characters and the file does not reside on the local computer. Most often, the symptom occurs when the file is on a UNIX or Novell server. CAUSE ===== Win32 API suggests that a truncated short file name appear in a separate field when a long file name is being accessed from a server. The field for the truncated short file name was empty in this case; therefore, the returned file name was used as a short file name. This resulted in an inability to open the file, because the name was actually a long file name. WORKAROUND ========== To work around this problem, do one of the following: - Copy the file to your local hard disk, and then attach it to the message. - Use an 8.3 file name on the server. - Use the Exchange 4.0 client. - Use the Outlook client. STATUS ====== Microsoft has confirmed this to be a problem in Microsoft Exchange Windows NT client version 5.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. Additional query words: OS2 namespace 3.12 4.11 netware capone attachments findfirstfile ====================================================================== Keywords : kbusage Technology : kbExchangeSearch kbExchangeClientSearch kbZNotKeyword2 kbZNotKeyword3 kbExchange500NT Version : :5.0 Issue type : kbbug Solution Type : kbfix ============================================================================= 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. Copyright Microsoft Corporation 2002.