Sorry not to be able to be more accurate in the bug description but the problem is not trivial.

It occurs (not every time) just after a call on a method like DeleteItem($deleteItem) on a NTLMSoapClient_Exchange instance.

This call is the last I can trace. Just after the process has jumped on an inpredictable line of the code previously loaded by the php interpreter. And there is absolutely no relation beetween the DeleteItem and the next line of code executed. Of course, the program can't run much further because the contexte is not the good one.

Normaly, if no bug occurs, just after a call to DeleteItem, the next line of code I can trace is in the __construct method of the NTLMSoapClient instance. The SOAP enveloppe has been created and the program is almost ready to call the server.

I suppose the bug occurs while creating the SOAP request, but I can't trace it. I already tried to activate exceptions and trace this way: $EWSClientOptions = array ( 'user' => EWS_CLIENT_USER, // for curl 'password' => EWS_CLIENT_PASSWORD, 'trace' => true, // options the should be used by soapclient http://www.php.net/manual/fr/soapclient.soapclient.php 'exceptions ' => true ); $this->EWSclient = new NTLMSoapClient_Exchange(EWS_CLIENT_WSDL, $EWSClientOptions);

but it doesn't launch any exceptions and I see no traces.

If only it could launch an exception ... !

Running on - Windows Server 2008 R2 Enterprise. - PHP Version 5.2.14 - Zend Server - Curl info: libcurl/7.20.0 OpenSSL/0.9.8o zlib/1.2.3 - Exchange 2010 (but it has not yet been called when to problem occurs)

but I also had the problem on PHP5.3 and a simple (wamp) apache server.

I hope we can solve this problem.

Thanks,

Alain

This issue has been moved to GitHub https://github.com/jamesiarmes/php-ews/issues/9