Inconsistent syncObjectEvents behaviorþ

  • Thread starter Thread starter Exchnerd
  • Start date Start date
E

Exchnerd

Hi all,

I have a callback for SyncObjectEvents in my outlook plugin. MSDN and
blogs say that one cannot register for the callbacks when Outlook
syncs or does a Send/Receive but can only when one is started
programmatically. However, I've had a few observations and appreciate
your comments on it -

I disable my n/w connectivity to generate an onError callback during a
sync. This works fine. But when I enable the n/w and initiate a sync
or send/receive, outlook still invokes the onError handler but this
time with no value in the Description parameter. I am unable to
distinguish because the description parameter sometimes has a text
during a real error condition and it sometimes does not. (I was trying
to concur that it is connected if the description param is NULL but
has a valid error code)

Is this a known issue? Any clues please??

I am trying to be notified when Outlooks looses connectivity and then
again when it gains.
 
Hi all,

I have a callback for SyncObjectEvents in my outlook plugin. MSDN and
blogs say that one cannot register for the callbacks when Outlook
syncs or does a Send/Receive but can only when one is started
programmatically. However, I've had a few observations and appreciate
your comments on it -

I disable my n/w connectivity to generate an onError callback during a
sync. This works fine. But when I enable the n/w and initiate a sync
or send/receive, outlook still invokes the onError handler but this
time with no value in the Description parameter. I am unable to
distinguish because the description parameter sometimes has a text
during a real error condition and it sometimes does not. (I was trying
to concur that it is connected if the description param is NULL but
has a valid error code)

Is this a known issue? Any clues please??

I am trying to be notified when Outlooks looses connectivity and then
again when it gains.
Click to expand...

Now, checking the OlExchangeConnectionMode to get the exact status :-)
 
Back
Top