XGEN: CDO's GetNext with Custom Property Fails at 17th Time

Last reviewed: March 6, 1998
Article ID: Q182084
The information in this article applies to:

- Microsoft Exchange Server, version 5.5

SYMPTOMS

When you search a custom property of a message on Messages Collection Object in Collaboration Data Objects (CDO) version 1.2, calling the GetNext method more than 16 times results in the following error message. The error message dialog box appears, and the CDO program is terminated, if there is no error trap.

    Run Time error -2147467259(80004005)
    [Collaboration Data Objects [E_Fail (80004005)]]

STATUS

Microsoft has confirmed this to be a problem in Exchange Server version 5.5. 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.

MORE INFORMATION

This problem only occurs when you access a custom property of a Field(s) object. When you use the MAPI property tag instead of the name of the custom MAPI property, you can call GetNext more than 16 times successfully. This problem also applies to the GetPrevious method.


Additional query words: 17 Active Messaging OLE Visual Basic
Keywords : XADM XGen kbbug5.50 kbusage
Version : 5.5
Platform : winnt
Issue type : kbbug
Solution Type : kbpending


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