PDA

View Full Version : WM6 and ActiveSync scheduling


embryjim
12th December 2007, 05:31 PM
Has anyone experienced weird ActiveSync behavior since upgrading? I sync with my work's exchange server and in WM5 I had no problems setting up a schedule and the Treo would stick to it, never trying to sync at other times. Now, even though I set it to sync at 30 minute intervals, it syncs on its own at random times (it tried about 50 times yesterday). It seems to totally ignore the settings within the phone. This is killing my battery time, I used to get about 3 days in WM5, but now only get about a day. I've tried resetting (hard and soft) a dozen times, setting it to manually sync, looked at the task manager and disabled repllog.exe, but it keeps syncing at will. I've noticed in the logs, on a scheduled sync it will say "type=scheduled", but all the other times it says "type=interactive". I never looked at the logs in WM5 because it worked like I told it to. Any suggestions, registry hacks to make it sync only on my schedule? Thanks in advance. BTW, I did scour the web for answers before posting, maybe I missed something.

embryjim
12th December 2007, 10:33 PM
OK, more info. I have gotten it to sync on schedule twice. If I fire up a task manager and look at the repllog.exe instances, on a good sync I will have 4 intances (three with AppRunAfter arguments which I understand are normal) and one with a /sched /remote /h argument which has the correct scheduled time to sync. On those occassions when it syncs at will, the task manager will show as many as 7 repllog.exe instances, with those above the normal 4 showing /remote /h /all arguments with various times before the next scheduled sync. Confusing? YES...Any takers?

embryjim
12th December 2007, 11:59 PM
Last post. It seems to be working now, I did have HandySwitcher running and set to close ActiveSync on disconnect. I turned that off and it has synced successfully for six 30 minute intervals. Thanks to all who may have been trying to troubleshoot. Still not convinced HandySwithcer was the culprit...but...