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

This article was previously published under Q254054
This article has been archived. It is offered "as is" and will no longer be updated.
Invalid Ordinals that are contained in accessors while calling IRowsetChange::SetData on a cached rowset may cause the proxy to crash.
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.
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 theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Only pass valid accessors. Valid accessor ordinals are "0" and "1".
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.

Article ID: 254054 - Last Review: 10/20/2013 17:21:45 - Revision: 1.4

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbbug kbfix kbprogramming KB254054