XCLN: Attempting to Open Public Folder Might Return Error

Last reviewed: April 15, 1997
Article ID: Q157017
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

When you use the Microsoft Exchange client to open a Public Folder (PF) that has a special custom view that categorizes the folder content, the open attempt might return the following:

   Error: Unable to display folder

CAUSE

When a categorized view is added to a PF, the required columns are added to the folder table in the Microsoft Exchange Information Store (IS) to support this view. When we re-use this folder table, we assumed that all the columns needed are already present in the IS. However, if this same folder table is used but the sort criteria is different, the QueryRows call will not check to make sure the columns needed for the new sort criteria are present. It only checks that the columns needed for the categorization are present. So when QueryRows tries to create an index to the sorting columns, the IS database (JET) returns a JET_errColumnNotFound (this is translated as MAPI_E_CALL_FAILED).

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K


Additional query words: Outlook
Keywords : kbbug4.00 kbfix4.00.sp3 kbusage XCLN
Version : 4.0
Platform : WINDOWS
Issue type : kberrmsg


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