Traveler Client: Error (-1073741819)

I cannot sync mails from one specific user.Server is a W2003 + Domino 8.5.1

Mobile device is HTC TN II with windows mobile 6.1

I installed Traveler and configured with my accunt and everything works fine, but when reconfiguring Traveler for the final user I get following error message:

Error (-1073741819): Initial synchronization is not completed

It seems that the synchronization task begins to sync the calender items, then the mails and it is when it receives the modifications from the server that stops.

the strange thing is that I can access the traveler page, if I browse to the servlet page, after authentication I can see the following message:

Waiting for message from device the following modifications are waiting to be syncd:mail:add

How canI fix this?

Thanks in advance,

Ricard

Subject: RE: Traveler Client: Error (-1073741819)

Sounded like other users are fine - just not this user - that correct?

If so then try

tell traveler reset

If that does not help then most likely there is a document that this particular user is trying to sync that is causing problems. Unfortunately the best way to troubleshoot is to open a Problem Report with Lotus Support so log files can be reviewed.

this will turn server logging on for the user:

tell traveler log adduser finest

This will turn on packet tracing for the user:

tell traveler log syncml on

Then look at this wiki article to generate client logs:

http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Best_Practices__Submitting_a_problem_report_from_a_device.

Subject: 8.5.1.1 fix the situation

Actually I did all these suggestions but nothing changed. Finally I opened a TPR with Lotus support and they send me a new version of traveller=> 8.5.1.1.201001281427 to install on the device. This fixed the issue.Thanks for the suggestions!

Subject: Upgraded traveler to 8.5.1.1 ?

I’ve had the exact same problem for a few users on a SonyEricsson Xperia X2 (windows mobile 6.5). Which is not officially supported yet.

The problem was resolved by upgrading both the Traveler server to 8.5.1.1 and upgrading the Traveler client on the devices.

Worth a try if you havent tried that yet.