Menu

#82 The specified time zone isn't valid

closed
nobody
None
5
2011-06-21
2010-11-08
Anonymous
No

I have a setup here at work. It is a development environment so I could see if I could get davmail working with exchange 2010 and thunderbird in both windows and linux. The issue I am having is with the caldav stuff. Specifically the free/busy schedule. When I try to create an event and invite attendees, I create the event, pick a time, invite attendees and everybody has an avaliability of "no information". I have double checked that public folders are enabled and the free busy schedule is in the public folders on the exchange server so I am not sure why they are not showing up... but I think it is related to the "The specified time zone isn't valid" error message I get. I have exchange running on windows server 2008 and thunderbird running in XP (have not tested linux yet) and DavMail running on the XP machine. Versions of software:
thunderbird 3.1.6
lightning 1.0b2
DavMail 3.8.6-1530
The error comes up when I go to look at the invited attendees for a calendar event or when I am inviting attendees.
The exact error that is coming up is:
Date: Mon Nov 08 14:22:07 CST 2010 (1289247727532)
Thread: CaldavConnection-4347
Message #: 45964
Level: DEBUG
NDC:
Category: davmail.caldav.CaldavConnection
Message: > The specified time zone isn't valid.
request: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages"><soap:Header><t:RequestServerVersion Version="Exchange2010"/></soap:Header><soap:Body><m:GetUserAvailabilityRequest><t:TimeZone><t:Bias>0</t:Bias><t:StandardTime><t:Bias>0</t:Bias><t:Time>00:00:00</t:Time><t:DayOrder>1</t:DayOrder><t:Month>1</t:Month><t:DayOfWeek>Sunday</t:DayOfWeek></t:StandardTime><t:DaylightTime><t:Bias>0</t:Bias><t:Time>00:00:00</t:Time><t:DayOrder>1</t:DayOrder><t:Month>1</t:Month><t:DayOfWeek>Sunday</t:DayOfWeek></t:DaylightTime></t:TimeZone><m:MailboxDataArray><t:MailboxData><t:Email><t:Address>grant@corp.vecimadev.com</t:Address></t:Email><t:AttendeeType>Required</t:AttendeeType></t:MailboxData></m:MailboxDataArray><t:FreeBusyViewOptions><t:TimeWindow><t:StartTime>2010-11-08T06:00:00Z</t:StartTime><t:EndTime>2010-11-24T06:00:00Z</t:EndTime></t:TimeWindow><t:MergedFreeBusyIntervalInMinutes>15</t:MergedFreeBusyIntervalInMinutes><t:RequestedView>MergedOnly</t:RequestedView></t:FreeBusyViewOptions></m:GetUserAvailabilityRequest></soap:Body></soap:Envelope>
Location: davmail.caldav.CaldavConnection.sendHttpResponse(CaldavConnection.java:1178)
Thrown:

If need be, I can provide the full log, but I believe the problem resides in the above information. The error pops up every time I click on "invite attendees". My timezone on lightning is set to America/Regina, in XP it is set to GMT -6:00 Saskatchewan, and on the 2008 server it is set to UTC -6:00 Saskatchewan. Both of these machines have the correct time, and I do not have issues with creating the event, just the free/busy schedule does not get updated.

Any thoughts? or did I post this in the wrong section?

Discussion

  • Anonymous

    Anonymous - 2010-11-08

    Better error information:
    Date: Mon Nov 08 15:19:39 CST 2010 (1289251179548)
    Thread: CaldavConnection-4429
    Message #: 26700
    Level: ERROR
    NDC:
    Category: davmail
    Message: The specified time zone isn't valid.
    request: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages"><soap:Header><t:RequestServerVersion Version="Exchange2010"/></soap:Header><soap:Body><m:GetUserAvailabilityRequest><t:TimeZone><t:Bias>0</t:Bias><t:StandardTime><t:Bias>0</t:Bias><t:Time>00:00:00</t:Time><t:DayOrder>1</t:DayOrder><t:Month>1</t:Month><t:DayOfWeek>Sunday</t:DayOfWeek></t:StandardTime><t:DaylightTime><t:Bias>0</t:Bias><t:Time>00:00:00</t:Time><t:DayOrder>1</t:DayOrder><t:Month>1</t:Month><t:DayOfWeek>Sunday</t:DayOfWeek></t:DaylightTime></t:TimeZone><m:MailboxDataArray><t:MailboxData><t:Email><t:Address>grant@corp.vecimadev.com</t:Address></t:Email><t:AttendeeType>Required</t:AttendeeType></t:MailboxData></m:MailboxDataArray><t:FreeBusyViewOptions><t:TimeWindow><t:StartTime>2010-11-08T06:00:00Z</t:StartTime><t:EndTime>2010-11-24T06:00:00Z</t:EndTime></t:TimeWindow><t:MergedFreeBusyIntervalInMinutes>15</t:MergedFreeBusyIntervalInMinutes><t:RequestedView>MergedOnly</t:RequestedView></t:FreeBusyViewOptions></m:GetUserAvailabilityRequest></soap:Body></soap:Envelope>
    Location: davmail.ui.tray.DavGatewayTray.displayMessage(DavGatewayTray.java:113)
    Thrown:
    davmail.exchange.ews.EWSException: The specified time zone isn't valid.
    request: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages"><soap:Header><t:RequestServerVersion Version="Exchange2010"/></soap:Header><soap:Body><m:GetUserAvailabilityRequest><t:TimeZone><t:Bias>0</t:Bias><t:StandardTime><t:Bias>0</t:Bias><t:Time>00:00:00</t:Time><t:DayOrder>1</t:DayOrder><t:Month>1</t:Month><t:DayOfWeek>Sunday</t:DayOfWeek></t:StandardTime><t:DaylightTime><t:Bias>0</t:Bias><t:Time>00:00:00</t:Time><t:DayOrder>1</t:DayOrder><t:Month>1</t:Month><t:DayOfWeek>Sunday</t:DayOfWeek></t:DaylightTime></t:TimeZone><m:MailboxDataArray><t:MailboxData><t:Email><t:Address>grant@corp.vecimadev.com</t:Address></t:Email><t:AttendeeType>Required</t:AttendeeType></t:MailboxData></m:MailboxDataArray><t:FreeBusyViewOptions><t:TimeWindow><t:StartTime>2010-11-08T06:00:00Z</t:StartTime><t:EndTime>2010-11-24T06:00:00Z</t:EndTime></t:TimeWindow><t:MergedFreeBusyIntervalInMinutes>15</t:MergedFreeBusyIntervalInMinutes><t:RequestedView>MergedOnly</t:RequestedView></t:FreeBusyViewOptions></m:GetUserAvailabilityRequest></soap:Body></soap:Envelope>
    at davmail.exchange.ews.EWSMethod.checkSuccess(EWSMethod.java:621)
    at davmail.exchange.ews.EwsExchangeSession.executeMethod(EwsExchangeSession.java:1647)
    at davmail.exchange.ews.EwsExchangeSession.getFreeBusyData(EwsExchangeSession.java:1464)
    at davmail.exchange.ExchangeSession.getFreebusy(ExchangeSession.java:3014)
    at davmail.caldav.CaldavConnection.sendFreeBusy(CaldavConnection.java:996)
    at davmail.caldav.CaldavConnection.handleFolder(CaldavConnection.java:246)
    at davmail.caldav.CaldavConnection.handleRequest(CaldavConnection.java:202)
    at davmail.caldav.CaldavConnection.run(CaldavConnection.java:151)

     

    Last edit: Anonymous 2013-11-21
  • Mickael Guessant

    Looks like Exchange 2010 does not like Exchange 2007 GMT timezone definition, need to investigate this.

     
  • Anonymous

    Anonymous - 2010-11-09

    Not sure if this is a related issue/bug or not, but when I try to make a full day event, an error gets thrown too:
    Date: Tue Nov 09 13:37:04 CST 2010 (1289331424665)
    Thread: CaldavConnection-1089
    Message #: 2
    Level: ERROR
    NDC:
    Category: davmail
    Message: Invalid date: 20101119
    Location: davmail.ui.tray.DavGatewayTray.displayMessage(DavGatewayTray.java:113)
    Thrown:
    davmail.exception.DavMailException: Invalid date: 20101119
    at davmail.exchange.ews.EwsExchangeSession.convertCalendarDateToExchange(EwsExchangeSession.java:1780)
    at davmail.exchange.ews.EwsExchangeSession$Event.createOrUpdate(EwsExchangeSession.java:1180)
    at davmail.exchange.ews.EwsExchangeSession.internalCreateOrUpdateEvent(EwsExchangeSession.java:1453)
    at davmail.exchange.ExchangeSession.createOrUpdateItem(ExchangeSession.java:2598)
    at davmail.caldav.CaldavConnection.handleFolder(CaldavConnection.java:262)
    at davmail.caldav.CaldavConnection.handleRequest(CaldavConnection.java:202)
    at davmail.caldav.CaldavConnection.run(CaldavConnection.java:151)

    I am not sure if it is related, but it looks related to me.

     
  • Anonymous

    Anonymous - 2010-11-25

    Good news and bad news:
    First the good news - I figured out the "invalid date" issue. Had to modify EwsExchangeSession.java line 1778 and 1780 to be this:
    1778: SimpleDateFormat dateParser = new SimpleDateFormat("yyyyMMdd", Locale.ENGLISH);
    1780: SimpleDateFormat dateFormatter = new SimpleDateFormat("yyyy-MM-dd", Locale.ENGLISH);

    This probably breaks compatibility with exchange 2003 or server 2003, but I do not have an environment with that running to test it.
    Good news part 2: I think I found the issue with the timezone by preforming the above steps. In EwsExchangeSession.java, after making the above mentioned change, I am now getting a null pointer exception when it tries to read the timezone information from the server. Specifically at line 1190.
    1190: updates.add(Field.createFieldUpdate("starttimezone", vCalendar.getVTimezone().getPropertyValue("TZID")));
    from doing a quick check (not much verification or anything, just quick looking), I think that the vCalendar.getVTimezone().getPropertyValue("TZID") is the part that is failing, but I have yet to figure out why that is returning null... or if that is what is returning null... going to do more testing, but thought I would post my results so far.

     
  • Anonymous

    Anonymous - 2010-11-30

    so, playing more with the code, changing lines 1778 and 1780 create other issues. So, as a better fix, I added these lines UNDER those ones (ie at line 1782):
    if (vcalendarDateValue.length() == 8) {
    vcalendarDateValue=vcalendarDateValue + "T000000";
    }
    This fixed all of the errors coming from here and made full day event s a little happier, but still getting the invalid timezone issue. Will continue playing with timezone crap as this may be a lightning related bug not a davmail bug.

     
  • Mickael Guessant

    Did you try with latest svn revision ?

    I recently fixed a timezone retrieval issue, this may help.

    Anyway, I would need a sample log file to investigate and fix date conversion.

     
  • Anonymous

    Anonymous - 2010-11-30

    just updated to davmail 3.8.7 and still having the same issue. No longer need to change lines 1778/1780, but still having the invalid timezone issue.

     
  • Mickael Guessant

    Invalid date or invalid timezone ?

     
  • Anonymous

    Anonymous - 2010-12-01

    the invalid date issue seems to be resolved with the latest version of davmail, but the invalid timezone issue still persists.

     
  • Anonymous

    Anonymous - 2010-12-01

    well, instead of saying "invalid time zone" now, it says "ErrorInvalidPropertySet". I have narrowed it down to being the timezone though because if I remove the timezone section from the EWSExchangeSession.java file (comment out lines1188 to 1194), then it creates the event... just at the wrong time (full day events start at 6 PM the day prior to the event and end at 6PM on the day of the event).

     
  • Mickael Guessant

    Almost there, need to find which property is missing...

     
  • Anonymous

    Anonymous - 2010-12-01

    If I comment out lines 1188 to 1194, this removes the "StartTimeZone" (when using exchange 2010), but no other fields. Then the create calendar event succeeds, but makes the event for the wrong time/date (due to me not being in GMT/UTC). So I think it has something to do with the ID field (which I am unable to find a valid value for).

     
  • Anonymous

    Anonymous - 2010-12-29

    Due to complications and limitations set on our development network, I am unable to test installing service pack 1. So I guess I will either need to test it on the live environment (which should cause no issues as it doesn't modify exchange server nor does it require me to modify the exchange server), or wait until a time when we can update our development network... or poke through the code and tinker with requests and such to see what I can figure out...

     
  • Mickael Guessant

    Ok, please let me know

     
  • Mickael Guessant

    • status: open --> pending
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending --> closed
     
  • Mickael Guessant

    • status: closed --> open
     
  • Mickael Guessant

    Fixed in subversion

     
  • Mickael Guessant

    Please try again with 3.9.2

     
  • Mickael Guessant

    • status: open --> pending
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB