Invalid Ordinals Contained in Accessors Used in RowsetChange::SetData May Cause Proxy to Crash

Article translations Article translations
Article ID: 254054 - View products that this article applies to.
This article was previously published under Q254054
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

Invalid Ordinals that are contained in accessors while calling IRowsetChange::SetData on a cached rowset may cause the proxy to crash.

CAUSE

Accessor validation only occurs on the original accessor that is created by EXOLEDB. Accessors that are created by the user to work on cached rowsets are not validated.

If an invalid accessor is supplied, the proxy will crash.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

WORKAROUND

Only pass valid accessors. Valid accessor ordinals are "0" and "1".

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server . This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1. The problem is related to a bug in MDAC 2.5, which is corrected in MDAC 2.6.

Properties

Article ID: 254054 - Last Review: October 20, 2013 - Revision: 1.4
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbprogramming KB254054

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com