Bad Request Using Active Sync Protocol

Question

Hi All,
I am facing a Bad Request error while sending the FolderSync Command to exchange server using Netbook. I checked headers and url everything is proper, the same request works well in another device. Please let me know if anything i should take care.

Thanks in advance

Answer 1

Hi Sirishak:
Thank you for your inquiry.

A member of Protocol Documentation Team will be in touch soon.

---

Regards, Obaid Farooqi

Answer 2

Hi Sirishak,

I am the engineer who has taken ownership of your inquiry.

Could you please e-mail me the packet trace for this to dochelp [at] winse.microsoft.com ?
I need to see the full request and responses.

Dominic Michael Salemno
Senior Support Escalation Engineer
US-CSS DSC Protocols Team

Answer 3

Sirishak,

I still have not received your network trace at the previously provided e-mail address.

Would you still like me to investigate this issue?

Dominic Michael Salemno
Senior Support Escalation Engineer
US-CSS DSC Protocols Team

Answer 4

Sorry for late reply. Yeah i wanted to investigate on this issue. Here is the attached file for packet trace. Also i have sent the same packet trace to  dochelp [at] winse.microsoft.com 
 
Please let me know if anything else is required to investigate this issue.
 
Thanks,
Sirisha

Answer 5

Is any progress has been made on this issue after sending the packet trace?


Thanks,
Sirisha

Answer 6

Sirishak,

I am still investigating this issue.

Dominic Michael Salemno
Senior Support Escalation Engineer
US-CSS DSC Protocols Team

Answer 7

Any luck on this issue. I am waiting for solution.

Thanks,
Sirisha

Answer 8

Sirisha,

I am still investigating this issue. I am still analyzing your trace.

Dominic Michael Salemno
Senior Support Escalation Engineer
US-CSS DSC Protocols Team

Answer 9

Sirisha,

 

After analyzing the trace in question, I have found two extra bytes at the end of the commands that have resulted in a 400 Bad Request. The extra bytes in question are “0d 0a” and correlate to a CRLF. Perhaps you have inadvertently inserted those bytes by using a function/method that appends these particular bytes to the stream in question? For example, if you are using WriteLine() as opposed to Write() will cause such behavior to occur.

 

Removing these two extra bytes should correct the problem.

 

Have I answered your question?

 

Dominic Michael Salemno

Senior Support Escalation Engineer

US-CSS DSC Protocols Team