Hi, I’m getting an error when using EWSClient trying to access Exchange on WebCentral. Error 440 Login Timeout.
I’ve been able to connect to all others hosts, just not WebCentral. Any ideas?
Hi Paul,
Thank you for contacting Aspose support team.
As you have mentioned that you are able to connect to all other hosts except WebCentral, so it requires little analysis. You may please generate log of exchange client by using feature mentioned here. Once the log is generated, please send it to us for analysis.
You are also requested to arrange a test account on the said exchange for our testing. It will help us to re-produce the scenario here and provide assistance accordingly.
Thank you. I only have the clients credentials so setting up a test account is not possible at this stage.
The results of the logging:
— Aspose.Email EWS Client diagnostic log —
— Started: 1/01/2016 9:48:31 AM —
1/01/2016 9:48:35 AM <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap=“http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=“http://www.w3.org/2001/XMLSchema”>soap:Header
1/01/2016 9:48:35 AM </soap:Header>
1/01/2016 9:48:35 AM soap:BodyIdOnly
1/01/2016 9:48:35 AM </soap:Body></soap:Envelope>
Hi Paul,
As mentioned earlier, we are not able to reproduce this issue at our end with Exchange Server 2010 and Office365 account. We shall be in need of some account that we can use to test this issue at our end for assisting you further. If possible, please share the client’s account credentials so that we can run our tests and assist you further.
Hi, unfortunately I cannot supply the clients credentials. I have requested WebCentral create a test account and provide other information, I will update this ticket as soon as that is ready.
Thanks
Paul.
Hi,
Thank you for your understanding. Once a test account is available, please feel free to share these with us for our further investigation. We’ll look into these for assisting you further.