Microsoft: IExchangeExportChanges is broken

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Cain Random - 05 Nov 2003 18:31 GMT

Dear Someone At Microsoft, Please God Anyone at Microsoft:

The IExchangeExportChanges interface is broken as of OL2003. It'll work
fine for IExchangeImportContentChanges-derived objects, but it fails on the
Synchronize call with an E_FAILED HRESULT for
IExchangeImportHierarchyChanges-derived objects. This interface is critical
for the interoperation of our product with Exchange Server.

Please advise. Thank you.

Cain T. S. Random
Software Developer
Telescan, LC

Reply to this Message

Anton Lauridsen - 05 Nov 2003 23:03 GMT

I have found that you get different results depending on using cached mode
or not.

/anton

> Dear Someone At Microsoft, Please God Anyone at Microsoft:
>
[quoted text clipped - 9 lines]
> Software Developer
> Telescan, LC

Reply to this Message

Cain Random - 06 Nov 2003 01:17 GMT

In cached mode, IExchangeExportChanges will not work at all because the
datastore is PST (I think). In any case, we verified that cached mode is
not being used. When it is, neither the hierarchy nor the contents
importers will work, and the OpenProperty call fails to return either
object. When cached mode is off, then only the hierarchy importer will
fail, and it will fail in the subsequent Synchronize call.

Thanks, though, Anton.

> I have found that you get different results depending on using cached mode
> or not.
[quoted text clipped - 15 lines]
> > Software Developer
> > Telescan, LC

Reply to this Message