New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated Appointment via EWS shows UTC instead of local TZ #398
Comments
@itbw please look into this issue |
@rajeshpatil1012 I think this is related to #357.
|
@itbw Thanks for your reply !! |
Hi @itbw i tried following code in ServiceRequestBase.java class just giving hard coded value then i got correct result // Emit the RequestServerVersion header
|
I'm currently using 2.1-snapshot but still have same bug, how to disable when message in body, i set start and end time zone but still message is UTC format
// meeting.startTimeZone = new OlsonTimeZoneDefinition(TimeZone.getTimeZone('Europe/Istanbul')) . |
I am also using 2.1-snapshot and I observed same issue in meeting invitation while creating appointment not only while updating. |
I changed exchange version to Exchange2007_SP1 and solved problem also set only startTimeZone like this. I hope this will help you.
|
@selamialtin thanks for your suggestion I am dealing with Microsoft Exchange server 2010 SP2 so I have to use ExchangeVersion.Exchange2010_SP2 to get exchange service otherwise I can not perform other operations |
Yes, we are using excahge server 2010 sp2 too, you should use the ews service as ExchangeVersion.Exchange2007_SP1 while sending appointment, no problem. |
@selamialtin thank you so much. It is working after setting ExchangeVersion.Exchange2007_SP1 while sending appointment. |
Hi All
I have researched for this issue and am unable to find a solution.
Updated Appointment via EWS shows UTC instead of local TZ in attendee's calender event notification mail
Here is what's wrong:
in when it showing time in UTC instead of local timezone ie (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi . both timing has 05:30 difference so it create confusion,Both timing should be same.
The text was updated successfully, but these errors were encountered: