XCLN: No E-Form when Sent from a Public Folder

Last reviewed: October 29, 1997
Article ID: Q147540

The information in this article applies to:
  • Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0
  • Microsoft Exchange Windows NT client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0

SYMPTOM

When you read an electronic form that has been created using the Microsoft Exchange, version 4.0, Electronic Forms Designer, the following message can appear in the message body that appears as a standard mail message in the recipients Inbox:

   Correctly displaying this item requires a custom form that is either
   not available or not correctly installed. Please see your network
   manager for more information.

CAUSE

One possible reason for the inability of the Microsoft Exchange client to launch the send form is due to the send form being installed only in a public folder. The Microsoft Exchange client will search only the default send form locations (Inbox and Enterprise forms registry).

However, the Microsoft Exchange client will search all available public folders for post forms.

WORKAROUND

To allow the form to be launched, drag or copy the message to the public folder where the form is installed, or install the form in the Organization Forms or local folder (mailbox or .PST).


Additional query words:
Keywords : XCLN kbusage
Version : 4.0
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: October 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.