Results 1 to 4 of 4
  1.    #1  
    Since I've upgraded to 1.4 (doctored) my EAS isn't working like it should, a lot of calendar items are missing on the pre (but some do show). Adding new items on the Pre works and are visible in Evolution and works the other way around as well.

    The server is running Exchange 2003 on a SBS 2003 server.

    Log from the Pre when pressing "Sync Now" in the calendar app:
    Code:
    # tail -f /var/log/messages -n0 | grep com.palm.mail
    2010-02-28T13:47:26.903717Z [1972] lex-pre user.info powerd: {powerd}: POWERD-ACTIVITY: PowerdActivityStart: (com.palm.mail.transports.eas.EasTransportThread-EAS_Sync_Active-52776558133266) for 900000ms => true
    2010-02-28T13:47:26.938720Z [1972] lex-pre user.warning java: {com.palm.mail}: Syncing EAS account: 52776558133266, reason: EasTransport.syncAccount()
    2010-02-28T13:47:27.022857Z [1972] lex-pre user.info powerd: {powerd}: POWERD-ACTIVITY: PowerdActivityStart: (com.palm.mail.transports.eas.EasTransportThread-EAS_Sync_Active-52776558133266) for 900000ms => true
    2010-02-28T13:47:31.119812Z [1976] lex-pre user.warning java: {com.palm.mail}: EAS failed to find initial sync in response for Tasks: {Status=5}
    2010-02-28T13:47:31.120361Z [1976] lex-pre user.warning java: {com.palm.mail}: EAS failed to get initial sync key for Tasks (82463372083330), http response: 200
    2010-02-28T13:47:31.120605Z [1976] lex-pre user.warning java: {com.palm.mail}: Sync key null for EAS collection Tasks, skipping sync.
    2010-02-28T13:47:31.465728Z [1977] lex-pre user.info powerd: {powerd}: POWERD-TIMEOUT: _power_timeout_set (,com.palm.mail.eas.read.timeout.282640776367,wakeup) at 02/28/2010 14:17:32
    2010-02-28T13:47:31.514038Z [1977] lex-pre user.info powerd: {powerd}: POWERD-ACTIVITY: PowerdActivityStop: (com.palm.mail.transports.eas.EasTransportThread-EAS_Sync_Active-52776558133266)
    2010-02-28T13:47:31.535278Z [1977] lex-pre user.info powerd: {powerd}: POWERD-ACTIVITY: PowerdActivityStart: (com.palm.mail.transports.eas.EasTransportThread-EAS_Sync_Active-52776558133266) for 900000ms => true
    2010-02-28T13:47:31.560363Z [1977] lex-pre user.warning java: {com.palm.mail}: EAS failed to send command Ping: 52776558133266: response code 400
    2010-02-28T13:47:31.564514Z [1977] lex-pre user.info powerd: {powerd}: POWERD-TIMEOUT: _power_timeout_clear (,com.palm.mail.eas.read.timeout.282640776367,private)
    2010-02-28T13:47:31.714508Z [1977] lex-pre user.info powerd: {powerd}: POWERD-ACTIVITY: PowerdActivityStop: (com.palm.mail.transports.eas.EasTransportThread-EAS_Sync_Active-52776558133266)
    I think this is the culprit:
    Code:
    EAS failed to send command Ping: 52776558133266: response code 400
    Log on the server:
    Code:
    10.0.0.200 - - [28/Feb/2010:14:54:16 +0100] "OPTIONS /Microsoft-Server-ActiveSync HTTP/1.1" 200 - "-" "Palm/1.0.1"
    10.0.0.200 - - [28/Feb/2010:14:54:16 +0100] "POST /Microsoft-Server-ActiveSync?Cmd=FolderSync&User=lex&DeviceId=PALM073f015a80eb8c02df5fa8fe46d9&DeviceType=Palm HTTP/1.1" 200 63 "-" "Palm/1.0.1"
    10.0.0.200 - - [28/Feb/2010:14:54:19 +0100] "POST /Microsoft-Server-ActiveSync?Cmd=Sync&User=lex&DeviceId=PALM073f015a80eb8c02df5fa8fe46d9&DeviceType=Palm HTTP/1.1" 200 109 "-" "Palm/1.0.1"
    10.0.0.200 - - [28/Feb/2010:14:54:19 +0100] "POST /Microsoft-Server-ActiveSync?Cmd=Sync&User=lex&DeviceId=PALM073f015a80eb8c02df5fa8fe46d9&DeviceType=Palm HTTP/1.1" 200 112 "-" "Palm/1.0.1"
    10.0.0.200 - - [28/Feb/2010:14:54:20 +0100] "POST /Microsoft-Server-ActiveSync?Cmd=Sync&User=lex&DeviceId=PALM073f015a80eb8c02df5fa8fe46d9&DeviceType=Palm HTTP/1.1" 200 112 "-" "Palm/1.0.1"
    10.0.0.200 - - [28/Feb/2010:14:54:20 +0100] "POST /Microsoft-Server-ActiveSync?Cmd=Sync&User=lex&DeviceId=PALM073f015a80eb8c02df5fa8fe46d9&DeviceType=Palm HTTP/1.1" 200 11 "-" "Palm/1.0.1"
    10.0.0.200 - - [28/Feb/2010:14:54:21 +0100] "POST /Microsoft-Server-ActiveSync?Cmd=Ping&User=lex&DeviceId=PALM073f015a80eb8c02df5fa8fe46d9&DeviceType=Palm HTTP/1.1" 400 46 "-" "Palm/1.0.1"
    Anyone else seeing this problem or knows how to fix it?
  2.    #2  
    Solved by installing Service Pack 2 for Exchange 2003 .
  3. #3  
    i love my EAS :-)
  4. #4  
    Quote Originally Posted by lexb View Post
    Solved by installing Service Pack 2 for Exchange 2003 .
    Thanks for reporting back with the resolution. I wonder how many folks have issues, solve them, and just leave the issue hanging out there.
    Treo 600 > Treo 650 > HTC Mogul (*****!) > HTC Touch Pro (***** squared!) > PRE! > Epic

Posting Permissions