Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[raldo]

Syncing my WM6 device over active sync doesn't seem to work in 497, 512, 515.

I believe syncing used to work on 494.

When I sync the device, and then do a recheck sync (with the same playlists), all files have status "in queue". The files that were synced (I checked that you can play the files on the handheld) now have status "delete on sync".

The same symptoms persist even if I disconnect, reboot, etc.

[JimH]

If you mean MC's sync (and not ActiveSync's), then I think that's what it would look like just before hitting the Transfer button in the Action Window in MC.

[raldo]

I mean MC's sync.

When  I did "Recheck sync" previously, all files that had been synced showed "On Device" (or something like that).

Where can i download 494? I have tried finding it on your pages.

I'd like to see if windows update is the sinner...

[raldo]

So... I cannot get a a hold of 494 (in which sync works). I'd rather not roll back my operating system (for obvious reasons).

What to do now?

Does anyone else have problems with syncing via MS Active Sync?

[SwellGuy]

We have found a problem the caching system. So if your files are getting converted during the sync process this could be effecting you. We will get this fixed immediately.

Is conversion involved with your sync?

[raldo]

There is no conversion involved.

Here's an observation:

I delete all the music files on the handheld, do a sync, and then I immediately do a recheck sync.

The situation in the sync window (Righthand, lower part of the mc main window) is as described above.

Then all files with status "on device" seem to have no tags except from the name tag. The name tag now contains the filename (ending with .mp3). I.e. all tags are different.

[raldo]

I deleted the WM6 handhelds (storage card and "onboard flash") and then did a redetect.

I have now set up MC to sync with the original playlists, and

      --- sync now seems to be working as expected.

I think one of the upgrades may have caused this problem.

[SwellGuy]

That great news - thanks for reporting it.