Esben,
I know you’ve seen this before, but in my case, I had a working sync
process before I upgraded to PHP5, and then following my upgrade, I get
these issues.
20/03/2006 20:49:38 [DEBUG]: Error happend: Outlook died!
20/03/2006 20:49:38 [CRITICAL!!]: A Critical error has happend, sync
aborted! Turn up log level to debug for more information.
20/03/2006 20:49:38 [CRITICAL!!]: Error returned from Outlook engine.
Code/Message: 0 - You must specify a valid time.
20/03/2006 20:49:38 [WARNING!]: Warning returned from Outlook.
Code/Message: 0 - There was a critical error in Function/Source: Submit
Item/System.Runtime.InteropServices.COMException
20/03/2006 20:49:38 [INFO]: Adding item to Outlook with ID: 916
20/03/2006 20:49:37 [DEBUG]: Assemble finished, assembled item had ID: 916
20/03/2006 20:49:37 [DEBUG]: Starting to assemble eGroupware item now.
20/03/2006 20:49:37 [DEBUG]: Success… Got item from eGroupware with ID: 916
20/03/2006 20:49:36 [DEBUG]: Getting item from eGroupware with ID: 916
I think the issue stems from the xml process sending the wrong data.
For this error, I captured the XML log…
recur_enddate
<dateTime.iso8601>1738-12-03T12:00:00</dateTime.iso8601>
It appears to occur on recurring events, though I cannot verify that
right now. This specific event is a birthday, recurring on 6th Jan, each
year. It looks to me like the transcoding from the database to XML is
wrong, though the data shows correctly in eGW.
Hi Ian,
did you set a recur-enddate and if yes what?
Did you set a start-date and if yes what?
Is the server running on windows?
Ralf
Ian J Cornish schrieb:
Esben,
I know you’ve seen this before, but in my case, I had a working sync
process before I upgraded to PHP5, and then following my upgrade, I get
these issues.
20/03/2006 20:49:38 [DEBUG]: Error happend: Outlook died!
20/03/2006 20:49:38 [CRITICAL!!]: A Critical error has happend, sync
aborted! Turn up log level to debug for more information.
20/03/2006 20:49:38 [CRITICAL!!]: Error returned from Outlook engine.
Code/Message: 0 - You must specify a valid time.
20/03/2006 20:49:38 [WARNING!]: Warning returned from Outlook.
Code/Message: 0 - There was a critical error in Function/Source: Submit
Item/System.Runtime.InteropServices.COMException
20/03/2006 20:49:38 [INFO]: Adding item to Outlook with ID: 916
20/03/2006 20:49:37 [DEBUG]: Assemble finished, assembled item had ID: 916
20/03/2006 20:49:37 [DEBUG]: Starting to assemble eGroupware item now.
20/03/2006 20:49:37 [DEBUG]: Success… Got item from eGroupware with ID: 916
20/03/2006 20:49:36 [DEBUG]: Getting item from eGroupware with ID: 916
I think the issue stems from the xml process sending the wrong data.
For this error, I captured the XML log…
recur_enddate
<dateTime.iso8601>1738-12-03T12:00:00</dateTime.iso8601>
It appears to occur on recurring events, though I cannot verify that
right now. This specific event is a birthday, recurring on 6th Jan, each
year. It looks to me like the transcoding from the database to XML is
wrong, though the data shows correctly in eGW.
–
eGroupWare Training & Support ==> http://www.egroupware-support.de
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users
Ralf,
Answers below… This was data that was already synched across from
Outlook. I had modified it to include some additional data, but then my
sync’s failed.
Let me know where in the DB I should look for the recur_enddate /
start_date fields
Ralf Becker wrote:
Hi Ian,
did you set a recur-enddate and if yes what? No
Did you set a start-date and if yes what? No
Is the server running on windows? Yes
Ralf
Ian J Cornish schrieb:
Esben,
I know you’ve seen this before, but in my case, I had a working sync
process before I upgraded to PHP5, and then following my upgrade, I get
these issues.
20/03/2006 20:49:38 [DEBUG]: Error happend: Outlook died!
20/03/2006 20:49:38 [CRITICAL!!]: A Critical error has happend, sync
aborted! Turn up log level to debug for more information.
20/03/2006 20:49:38 [CRITICAL!!]: Error returned from Outlook engine.
Code/Message: 0 - You must specify a valid time.
20/03/2006 20:49:38 [WARNING!]: Warning returned from Outlook.
Code/Message: 0 - There was a critical error in Function/Source: Submit
Item/System.Runtime.InteropServices.COMException
20/03/2006 20:49:38 [INFO]: Adding item to Outlook with ID: 916
20/03/2006 20:49:37 [DEBUG]: Assemble finished, assembled item had ID: 916
20/03/2006 20:49:37 [DEBUG]: Starting to assemble eGroupware item now.
20/03/2006 20:49:37 [DEBUG]: Success… Got item from eGroupware with ID: 916
20/03/2006 20:49:36 [DEBUG]: Getting item from eGroupware with ID: 916
I think the issue stems from the xml process sending the wrong data.
For this error, I captured the XML log…
recur_enddate
<dateTime.iso8601>1738-12-03T12:00:00</dateTime.iso8601>
It appears to occur on recurring events, though I cannot verify that
right now. This specific event is a birthday, recurring on 6th Jan, each
year. It looks to me like the transcoding from the database to XML is
wrong, though the data shows correctly in eGW.
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users