Problem: A calendar event created on the device is not being
synced to Meeting Maker and the following error appears in the
NotifyLink PIM log for the user.
[Jun 29, 2009 10:55:49][0]ProcessVCalendar - start [Jun 29, 2009 10:55:49][0]Parsing Calendar Event VCard [Jun 29, 2009 10:55:49][0]ParseVEvent: Adding Start Date: 29.06.2009 22:00:00 [Jun 29, 2009 10:55:49][0]ParseVEvent: Adding End Date: 30.06.2009 22:00:00 [Jun 29, 2009 10:55:49][0]ParseVEvent: Setting Reminder 29.06.2009 21:45:00, Total Minutes 15 [Jun 29, 2009 10:55:49][0]ParseVEvent: All Day Event [Jun 29, 2009 10:55:49][0]ParseVEvent: Adding Subject: BBTest1 [Jun 29, 2009 10:55:49][0]Process Device Calendar Change - start [Jun 29, 2009 10:55:49][0]Process Device Calendar Change: Appointment not found in database by UID: BBTest1 C104513-89299002- [Jun 29, 2009 10:55:49][0]Process Device Calendar Change: Adding appointment: BBTest1 [Jun 29, 2009 10:55:49][0]Start and End Times in GMT are 29.06.2009 22:00:00; 30.06.2009 22:00:00 [Jun 29, 2009 10:55:49][0]PutEventVCard: XML: <?xml
version="1.0"
encoding="UTF-8"?><SYNCMSG><AUTHENTICATION><SESSION
sessionid="Sergio@meetingmaker:ac5a9a:1222b6b2e3b:b3ba7812"/> </AUTHENTICATION><ACTION
type="Appointments"><PUTPIMREQUEST/><RECORDS><APPOINTMENTS><APPOINTMENT
alarmFlag="Y" allDayEvent="Y" proposal="N" description="BBTest1"
location="" notes="" startDate="20090629" startTime="220000"
endDate="20090629" endTime="220000"> <ALARM alarmDate="20090629" alarmTime="214500"/> <ITEMHEADER requestedAction="NEW"/> </APPOINTMENT> </APPOINTMENTS></RECORDS></ACTION></SYNCMSG> [Jun 29, 2009 10:55:49][0]PutEventVCard: Failed PutPimRequest, HTTP status = 500 [Jun 29, 2009 10:55:49][0]Process Device Calendar Change - end
Solution: The issue is caused by a Meeting Maker multi-day or single day recurring banner (or all day event). The item will error only if the user creates the all day event on their device and uses a reminder. The "reminder" will cause the issue so simply removing the reminder will resolve this issue. This is a problem on the Meeting Maker side and they are aware of it and working on a permanent resolution.
|