Hi,
We have a message appearing very often :
[0A70:000B-0F50] 03/12/2015 11:45:12 Traveler: SEVERE xxxxx XXXX Event from device does not have TimeZone, use prefTZ:sun.util.calendar.ZoneInfo[id=“Europe/Paris”,offset=3600000,dstSavings=3600000,useDaylight=true,transitions=184,lastRule=java.util.d=Europe/Paris,offset=3600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=1,startTime=3600000,startTimeMode=2,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=3600000,endTimeMode=2]] Exce
[0A70:000B-0F50] 03/12/2015 11:45:12 Traveler: SEVERE xxxxx XXXX Exception Thrown: java.lang.NullPointerException
where xxxxx XXXX is user first and lastname.
Many users are concerned and we also have some anomalies in synchronizing calendars.
I didn’t find any post with the same message.
Somebody else with this problem ?
Cordialement,
Luc
Subject: RE
Hi Luc,
The issue that you are experiencing seems to be a known problem with iOS -
http://www-01.ibm.com/support/docview.wss?uid=swg21966731 http://www-01.ibm.com/support/docview.wss?uid=swg21966731
To fix this issue, we recommend upgrading your server to Traveler 9.0.1.8 which is the latest version.
The APAR fixes for this issue are as follows:
LO86580: IOS 9 NATIVE CALENDAR UPDATE FROM DEVICE MAY CAUSE EVENT TO BE FILTERED FROM DEVICE(S). -
http://www-01.ibm.com/support/docview.wss?uid=swg1LO86580 http://www-01.ibm.com/support/docview.wss?uid=swg1LO86580
LO86164: CALENDAR EVENT MAY DISSAPEAR FROM IOS 9 DEVICE. -
http://www-01.ibm.com/support/docview.wss?uid=swg1LO86164 http://www-01.ibm.com/support/docview.wss?uid=swg1LO86164
For information on upgrading to Traveler 9.0.1.8 kindly review the release documentation -
http://www-01.ibm.com/support/docview.wss?uid=swg21967070 http://www-01.ibm.com/support/docview.wss?uid=swg21967070
Kindly take note that sometimes calendar events affected by the issue might not be fixed by just merely upgrading to 9.0.1.8. Users might to resync to the device either by reconfiguring the profile or by turning off calendary sync, power-cycling the device, and then turnin on calendary sync again from the device.