On Wed, 2009-03-04 at 00:55 +0800, [email protected] wrote: > > if it was unable to retrieve the session pointer from opaque obj_store. > > I don't think Exchange (but I may be wrong) actually returns > > MAPI_E_INVALID_PARAMETER on its own as a valid mapi_response retval for > > this call. Maybe enabling debug would show you whether the call is > > actually being packed and relay to Exchange or not. > > not knowing what debug_level means, I set it to 5. > Then I got a message "ndr_pull_error(2): Bad switch value 0" > Then I numbered all these ndr_pull_error and found that this one > came from ndr_pull_EcDoRpc_MAPI_REPL_UNION
The overall problem is very likely to come from here. Looks like libmapi has troubles with the mapi_response sent by Exchange for a particular call. To make it short: whenever ndr_pull_error is met means something is wrong with libmapi. It is possible this may be a special case we didn't yet handle in libmapi. If you could provide me more feedback on this one such as "when does it occur" etc. I may be able to trigger this bug and fix it. A wireshark capture may also be very useful here. Cheers, Julien. --- Julien Kerihuel [email protected] OpenChange Project Manager GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79 _______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
