SyncML Pro Hangs PDA

[WizRd]

Hi,

I recently purchased SyncML Pro for my Windows Mobile PDA so that I could benefit from the automatic syncing, however since ungrading to windows mobile 6.1 I am unable to use the pro version.

It never completes a successful sync, and makes the PDA so sluggish I am unable to use it.

The standard version works flawlessly with successful syncs every time.

Any help you can offer would be much appreciated.

Thanks,

Brett

[WizRd]

Is anyone else having this trouble?
Are you able to offer any suggestions or must i seek a refund?

[luz]

What parameters did you set for AutoSync?

We are not aware of general AutoSync problems with Windows Mobile 6.1, so I assume the problem must be related to something specific in your setup or networking environment.

[EPM]

we use the standard version and have intermittent problems with syncml locking the win mobile OS. its worse on 6.1 but also happens on 6.0. your not alone.

im starting my own thread with more details.

[WizRd]

It isn't only the autosync that is causing the problem, the issue occurs when I initiate a sync myself with the icon bottom left of the SyncML screen.

I have tried the new version .22 and the issue is still persistant, using SyncML pro causes the device (HTC TyTN II) to become sluggish and unresponsive, a soft reset is required to allow the device to be usable once again.

I would like to point out that the sync never completes. It is using the standard 6.1 image provided by my carrier (3 Mobile), and again I will point out that SyncML std works perfectly fine, the issue is only related to SyncML Pro.

I will post more details once I am able to access the server logs to see if anything specific is listed, however after spending $60 I do expect a product to actually work as advertised.

[luz]

I would like to point out that the sync never completes.

Never? Does this mean you have to kill the app every time or soft reset the device? Even if AutoSync is turned completely off?

It is using the standard 6.1 image provided by my carrier (3 Mobile), and again I will point out that SyncML std works perfectly fine, the issue is only related to SyncML Pro.

This is indeed really interesting. Because there is really no difference in the way a sync runs between STD and PRO versions. The only difference that I can think of which could be relevant is that the PRO version registers with WinMobile's "push router" which allows it to receive those special SMS that servers can use to start a sync (only if you allow it, of course). As this is a component of windows mobile very rarely used by third party software, it could have a bug that affects the system when used the way SyncML push requires it.

To track that down, I have created a special build of the PRO client which has the SMS related code disabled. It also is a debug version which writes logs to \temp of your device. Could you please test with this version? You can simply install it over your PRO, settings will be retained, and you can later install the regular PRO again. See your private message inbox (here in your forum account) to find the download link.

I will post more details once I am able to access the server logs to see if anything specific is listed,

BTW: what server are you using?

[WizRd]

Never? Does this mean you have to kill the app every time or soft reset the device? Even if AutoSync is turned completely off?

Even with AutoSync turned off the Sync never successfully completes. However after reverting the installation to the Std version it successfully syncs. On WM6.1 this does require the installation of the pro version to be uninstalled first.

To track that down, I have created a special build of the PRO client which has the SMS related code disabled. It also is a debug version which writes logs to \temp of your device. Could you please test with this version? You can simply install it over your PRO, settings will be retained, and you can later install the regular PRO again. See your private message inbox (here in your forum account) to find the download link.

I have downloaded the cab file and will be able to install it later today to trial the syncing and will report back with the logs hopefully in a few hours.

BTW: what server are you using?

The server I am using is actually Horde, a php based webmail application, who incidently recommend Synthesis SyncML. They use rpc.php, which if you visit http://www.horde.org/ can be retrieved from their cvs repository. I can provide Sync logs from the server side if required that may assist.

[WizRd]

I have installed this build, which was "mostly" successful. The Client was capable of syncing the Calendar items without an issue, however the contacts / tasks failed. I am yet to try syncing just the calendar to see if this resolves the issue.

Once "Receiving" is displayed for the status the application must be closed as it doesn't respond after 5 minutes. Clicking the Application Task Manager top right of the screen shows the application has been completely closed, however the device is still slugish and unresponsive, again a soft reset is required.

I have checked the temp directory of the device and have three files in there, however I'm unsure which one was created by Syncml, if you could please let me know so I can make this avaliable to you.

Thanks for your help so far!

Cheers,

Brett

[kgeorge]

I'm having a problem very similar to this. I experienced it on the windows mobile device emulator running Windows Mobile 6 Professional and on a user's Treo Pro running 6.1. This did not happen on an AT&T Treo 750 running WM6. If autosync isn't checked, everything seems to work fine. If it is, the program locks up and a soft reset is required.