Outlook sync issue - working only partly

KDY · Beitrag von **KDY** » Mo 15. Aug 2011, 15:25

Hi I recently installed your SW and it looks very promising!

I connect to my Samsung Gio (S5660) running Gingerbread from my PCrunning WinXPSP3 with Outlook 2003.
Sync'ing messages, calls, contacts works fine, but calender events doesn't really fully work:
Sync from Outlook to MyPhoneExplorer on the PC works fine - everything is there. Syncing on to the phone doesn't work: Only some of the calender events gets transferred.

I have tried the 'Create sync logs' and looked in the created log-file. In the log THERE ARE confirmation for all events (nice entry starting: "Appointment created [Phone]"), but on the phone, they are not all there??? (No events after a certain date).

After browsing the Forum I have tried to 'kick' the set-up of the software on the phone, by re-selecting in 'Calenders to sync' and 'add new events to...', but as it is only some of the events, that are missing, this is probably not where the problem lies - and of course it didn't help.
Any ideas?

Beitrag von FJ » Mo 22. Aug 2011, 22:12

Which events are missing ? Is there any pattern ? Press on the second button in the toollbar of MyPhoneExplorer ("Download entire") -> are the events still all visible in MyPhoneExplorer ?

KDY · Beitrag von **KDY** » Di 23. Aug 2011, 06:58

Thanks a lot, FJ, for responding.

At first I didn't really understand your question, but after having tried, I see.

The effect of "Download all" is that the Kalender in MPE is completely emptied ?!? It only took a second or two.

No impact on the contents of the calender in the Phone itself - or on Outlook (you got me worried for a second). I then did a new Sync with Outlook, and they came back.

bjopoh · Beitrag von **bjopoh** » Mi 24. Aug 2011, 13:23

Hi, I have a similar problem, when I sync my Outlook-2003 calendar to a Sone-Ericsson Xperia Neo all events in the calendar that have recurrence, i.e. are repeated on a e.g. weekly basis will not be loaded to the phone. All other calendar events are stored in the phone calendar. Does somebody knows how to fix this?

Lucien Kolkman · Beitrag von **Lucien Kolkman** » Mi 31. Aug 2011, 14:06

Hi,
I have the same problem.
I have a Samsung GIO and my PC is running Microsoft Office 2010.
First I had the Samsung running on Frojo, and then everything worked fine, including syncing the calender!!!
But I recently upgraded my phone to Gingerbread, and now the calander sync does not work anymore.
The sync from Outlook to Myphoneexplorer on the PC works fine, but no entry in the phone is created...

Please let me know if you have any tips,
Thanks in advance,

Lucien Kolkman

Beitrag von FJ » Fr 2. Sep 2011, 21:03

@KDY:

The effect of "Download all" is that the Kalender in MPE is completely emptied ?!? It only took a second or two.

This is a hint to a problem with the client. Please post the logfile after "Download entire"

@bjopoh & Lucien: Please install the current beta of the client and report if its working; www.fjsoft.at/mpeclient.apk

bjopoh · Beitrag von **bjopoh** » Mo 5. Sep 2011, 09:59

@FJ; I installed the beta version and as far as I can tell it seems to be working now. Thank you very much for the tip and the information about the beta.

Regards Björn

Lucien Kolkman · Beitrag von **Lucien Kolkman** » Mi 7. Sep 2011, 07:37

@FJ,

I installed the new beta client.
When I try to sync I get the following error message:

'Obex Protocol could not be initialised!'
OBEX Errorcode: D0 - Internal Server Error

Thanks,

Lucien
PS: when i return to the 'market-version' the error is gone again..

Beitrag von FJ » Mi 14. Sep 2011, 22:28

Please post the logfile as soon as you got the errormessage (with installed beta)

Lucien Kolkman · Beitrag von **Lucien Kolkman** » Di 20. Sep 2011, 10:19

Hi,

I tried to first use the original client. Than it seems that the changes are recognized, and there are also changes made in the pc-software (and it looks also in the phone) but there are no new entries...
I also looked a bit into it, and I saw that also my other Phone, a Nokia E5 shows up here and there. But before going to Gingerbread everything worked...
Here is the last part of the log-file.
I don't like to add the first part of the log-file here, because it's possible to decode and read it. (Of course I'm willing to pm the whole file to you)
Thanks in advance,
Lucien

10:27:53.88 Device Tracker Message: 0016S5660969d2fce offline

10:27:53.98 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:27:54.98 Device Tracker Message: 0016S5660969d2fce offline

10:27:59.25 DBT_DEVICEREMOVECOMPLETE: COM12
10:28:03.40 DBT_DEVICEREMOVECOMPLETE: COM11
10:29:41.87 DBT_DEVICEARRIVAL: COM11
10:29:41.98 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:29:42.98 Device Tracker Message: 002bS5660969d2fce offline
S5660969d2fce device

10:29:45.70 DBT_DEVICEARRIVAL: COM12
10:29:45.87 Refresh ComDescriptions...
10:29:45.95 PORT: COM12 Enumerator=USB Displayed=SAMSUNG Android USB Diagnostic Serial Port (WDM) InstanceID=USB\VID_04E8&PID_689E&MI_02\S5660969D2FCE_02
10:29:45.95 PORT: COM6 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000000
10:29:45.95 PORT: COM8 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000001
10:29:46.00 MODEM: COM8 Enumerator=ROOT Displayed=Nokia E5-00 Bluetooth Modem FriendlyName=Nokia E5-00 Bluetooth Modem InstanceID=ROOT\MODEM\0000
10:29:46.00 MODEM: COM11 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_689E&MI_00\S5660969D2FCE_00
10:29:46.00 MODEM: COM7 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-modem FriendlyName=Bluetooth-modem InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\WCBTMODEM0\1&30EE4AD&0&1000000040001
10:30:00.48 Try connecting to 192.168.178.44 (fixed IP)...
10:30:01.59 Broadcaster started
10:30:01.59 Sending broadcast
10:30:02.09 Sending broadcast
10:30:02.59 Sending broadcast
10:30:03.59 Try connecting to 192.168.178.44 (cached WifiIP)...
10:30:04.70 Closing Broadcaster
10:30:04.70 RunADBCommand: start-server
10:30:04.92 ADB CommandResponse:
10:30:04.92 RunADBCommand: devices
10:30:05.13 ADB CommandResponse: List of devices attached
S5660969d2fce offline
S5660969d2fce device
10:30:05.13 RunADBCommand: forward tcp:5210 tcp:5210
10:30:05.34 ADB CommandResponse:
10:30:05.34 Try connecting to 127.0.0.1...
10:30:05.95 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
10:30:06.15 ADB CommandResponse:
10:30:06.15 Try connecting to 127.0.0.1...
10:30:08.15 Avaiable Ports: COM6=\Device\BtPort0; COM7=\Device\BtModem0; COM8=\Device\BtPort1; COM11=\Device\ssadmdm0; COM11=\Device\ssadmdm1; COM12=\Device\ssadserd0; COM12=\Device\ssadserd1;
10:30:08.15 Neue COM-Bibliothek wird verwendet
10:30:08.17 SPort Properties set, opening COM11
10:30:08.17 After OpenPort
10:30:08.18 Kan niet worden geopend COM11!! (Toegang verboden)
10:30:08.18 Connect to Android failed!
10:30:08.18 bOpened=False
10:30:08.18 Kan niet worden geopend COM11!! (Toegang verboden)
10:30:08.18 Refresh ComDescriptions...
10:30:08.29 PORT: COM12 Enumerator=USB Displayed=SAMSUNG Android USB Diagnostic Serial Port (WDM) InstanceID=USB\VID_04E8&PID_689E&MI_02\S5660969D2FCE_02
10:30:08.29 PORT: COM6 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000000
10:30:08.29 PORT: COM8 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000001
10:30:08.40 MODEM: COM8 Enumerator=ROOT Displayed=Nokia E5-00 Bluetooth Modem FriendlyName=Nokia E5-00 Bluetooth Modem InstanceID=ROOT\MODEM\0000
10:30:08.40 MODEM: COM11 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_689E&MI_00\S5660969D2FCE_00
10:30:08.40 MODEM: COM7 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-modem FriendlyName=Bluetooth-modem InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\WCBTMODEM0\1&30EE4AD&0&1000000040001
10:30:08.40 ErrMsg: Connection to phone could not be established:
Kan niet worden geopend COM11!! (Toegang verboden)
10:30:08.65 SocketError: 10061 - Connection is forcefully rejected
10:30:17.82 Device Tracker Message: 0016S5660969d2fce offline

10:30:18.00 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:19.00 Device Tracker Message: 0016S5660969d2fce offline

10:30:19.00 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:20.00 Device Tracker Message: 0016S5660969d2fce offline

10:30:20.00 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:21.00 Device Tracker Message: 0016S5660969d2fce offline

10:30:21.00 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:22.00 Device Tracker Message: 0042S5660969d2fce offline
S5660969d2fce offline
S5660969d2fce offline

10:30:23.00 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline
0016S5660969d2fce offline

10:30:23.00 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:24.00 Device Tracker Message: 0016S5660969d2fce offline

10:30:24.00 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:25.00 Device Tracker Message: 0016S5660969d2fce offline

10:30:25.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:26.00 Device Tracker Message: 0016S5660969d2fce offline

10:30:27.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:27.06 DBT_DEVICEREMOVECOMPLETE: COM12
10:30:28.01 Device Tracker Message: 002bS5660969d2fce offline
S5660969d2fce device

10:30:31.06 DBT_DEVICEREMOVECOMPLETE: COM11
10:30:36.38 Device Tracker Message: 0016S5660969d2fce offline

10:30:37.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:37.12 DBT_DEVICEARRIVAL: COM11
10:30:38.01 Device Tracker Message: 0016S5660969d2fce offline

10:30:38.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:39.01 Device Tracker Message: 0016S5660969d2fce offline

10:30:39.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:40.01 Device Tracker Message: 0016S5660969d2fce offline

10:30:40.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:41.01 Device Tracker Message: 0016S5660969d2fce offline

10:30:41.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:41.12 Refresh ComDescriptions...
10:30:41.21 PORT: COM12 Enumerator=USB Displayed=SAMSUNG Android USB Diagnostic Serial Port (WDM) InstanceID=USB\VID_04E8&PID_689E&MI_02\S5660969D2FCE_02
10:30:41.21 PORT: COM6 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000000
10:30:41.21 PORT: COM8 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000001
10:30:41.26 MODEM: COM8 Enumerator=ROOT Displayed=Nokia E5-00 Bluetooth Modem FriendlyName=Nokia E5-00 Bluetooth Modem InstanceID=ROOT\MODEM\0000
10:30:41.26 MODEM: COM11 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_689E&MI_00\S5660969D2FCE_00
10:30:41.26 MODEM: COM7 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-modem FriendlyName=Bluetooth-modem InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\WCBTMODEM0\1&30EE4AD&0&1000000040001
10:30:41.92 DBT_DEVICEARRIVAL: COM12
10:30:42.01 Device Tracker Message: 0016S5660969d2fce offline

10:30:42.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:43.01 Device Tracker Message: 0016S5660969d2fce offline

10:30:43.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:44.01 Device Tracker Message: 0016S5660969d2fce offline

10:30:44.01 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:45.01 Device Tracker Message: 0016S5660969d2fce offline

10:30:45.03 Device Tracker Message: 002cS5660969d2fce offline
S5660969d2fce offline

10:30:45.92 Refresh ComDescriptions...
10:30:46.00 PORT: COM6 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000000
10:30:46.00 PORT: COM8 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000001
10:30:46.10 MODEM: COM8 Enumerator=ROOT Displayed=Nokia E5-00 Bluetooth Modem FriendlyName=Nokia E5-00 Bluetooth Modem InstanceID=ROOT\MODEM\0000
10:30:46.10 MODEM: COM7 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-modem FriendlyName=Bluetooth-modem InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\WCBTMODEM0\1&30EE4AD&0&1000000040001
10:30:46.10 Device Tracker Message: 0016S5660969d2fce offline

10:30:46.96 DBT_DEVICEREMOVECOMPLETE: COM12
10:30:51.01 DBT_DEVICEREMOVECOMPLETE: COM11
10:30:59.88 Try connecting to 192.168.178.44 (fixed IP)...
10:31:00.21 Connect to Android OK
10:31:00.21 Settimeout: RT=2000 WT=500
10:31:00.21 bOpened=True
10:31:00.21 [TX]: AT+CGSN
10:31:00.38 [RX]: AT+CGSN
10:31:00.38 [RX]: 357331041581487
10:31:00.38 [RX]: OK
10:31:00.38 Settimeout: RT=15000 WT=1000
10:31:00.38 [TX]: AT*PIN?
10:31:00.40 [RX]: AT*PIN?
10:31:00.40 [RX]: *PIN: ACCESS OK,10
10:31:00.40 [RX]: OK
10:31:00.40 [TX]: ATI
10:31:00.42 [RX]: ATI
10:31:00.42 [RX]: samsung GT-S5660
10:31:00.42 [RX]: OK
10:31:00.42 [TX]: AT*APPVERSION=1.8.1
10:31:00.43 [RX]: AT*APPVERSION=1.8.1
10:31:00.43 [RX]: 10,1.0.11 beta12
10:31:00.43 [RX]: OK
10:31:00.43 [TX]: AT+CSCS="UTF-8"
10:31:00.43 [RX]: AT+CSCS="UTF-8"
10:31:00.43 [RX]: OK
10:31:00.45 [TX]: AT+CNMI=2,1,0,1
10:31:00.45 [RX]: AT+CNMI=2,1,0,1
10:31:00.45 [RX]: ERROR
10:31:00.45 [TX]: AT*ECAM=1
10:31:00.46 [RX]: AT*ECAM=1
10:31:00.46 [RX]: OK
10:31:00.46 [TX]: AT+CIND=?
10:31:00.48 [RX]: AT+CIND=?
10:31:00.48 [RX]: ERROR
10:31:00.48 [TX]: AT+CBC
10:31:00.50 [RX]: AT+CBC
10:31:00.50 [RX]: +CBC: 0,29
10:31:00.50 [RX]: OK
10:31:00.50 [TX]: AT+CSQ
10:31:00.50 [RX]: AT+CSQ
10:31:00.50 [RX]: +CSQ: 3,99
10:31:00.51 [RX]: OK
10:31:00.51 Alle Verbindungsaktionen beendet
10:31:00.56 Form_Activate fSync Operation=7
10:31:00.57 [TX]: AT+CPROT=0
10:31:00.59 [RX]: AT+CPROT=0
10:31:00.59 [RX]: CONNECT
10:31:00.59 OBEX Connect: 16384 Bytes Paketgröße, Target: IRMC-SYNC
10:31:00.59 [TX]: 80 00 13 10 00 40 00 46 00 0C 49 52 4D 43 2D 53 59 4E 43
10:31:01.95 [RX]: D0 03 3C 4C 03 39 61 6E 64 72 6F 69 64 2E 64 61 74 61 62 61 73 65 2E 73 71 6C 69 74 65 2E 53 51 4C 69 74 65 45 78 63 65 70 74 69 6F 6E 3A 20 6E 6F 20 73 75 63 68 20 63 6F 6C 75 6D 6E 3A 20 61 76 61 69 6C 61 62 69 6C 69 74 79 53 74 61 74 75 73 3A 20 2C 20 77 68 69 6C 65 20 63 6F 6D 70 69 6C 69 6E 67 3A 20 53 45 4C 45 43 54 20 6F 72 69 67 69 6E 61 6C 45 76 65 6E 74 2C 20 61 76 61 69 6C 61 62 69 6C 69 74 79 53 74 61 74 75 73 2C 20 6F 77 6E 65 72 41 63 63 6F 75 6E 74 2C 20 5F 73 79 6E 63 5F 61 63 63 6F 75 6E 74 5F 74 79 70 65 2C 20 76 69 73 69 62 69 6C 69 74 79 2C 20 72 72 75 6C 65 2C 20 6C 61 73 74 44 61 74 65 2C 20 68 61 73 41 6C 61 72 6D 2C 20 67 75 65 73 74 73 43 61 6E 4D 6F 64 69 66 79 2C 20 67 75 65 73 74 73 43 61 6E 53 65 65 47 75 65 73 74 73 2C 20 65 78 72 75 6C 65 2C 20 72 64 61 74 65 2C 20 74 72 61 6E 73 70 61 72 65 6E 63 79 2C 20 74 69 6D 65 7A 6F 6E 65 2C 20 73 65 6C 65 63 74 65 64 2C 20 64 74 73 74 61 72 74 2C 20 74 69 74 6C 65 2C 20 5F 73 79 6E 63 5F 74 69 6D 65 2C 20 5F 69 64 2C 20 68 61 73 41 74 74 65 6E 64 65 65 44 61 74 61 2C 20 5F 73 79 6E 63 5F 69 64 2C 20 63 6F 6D 6D 65 6E 74 73 55 72 69 2C 20 64 65 73 63 72 69 70 74 69 6F 6E 2C 20 68 74 6D 6C 55 72 69 2C 20 5F 73 79 6E 63 5F 61 63 63 6F 75 6E 74 2C 20 5F 73 79 6E 63 5F 76 65 72 73 69 6F 6E 2C 20 68 61 73 45 78 74 65 6E 64 65 64 50 72 6F 70 65 72 74 69 65 73 2C 20 63 61 6C 65 6E 64 61 72 5F 69 64 2C 20 65 76 65 6E 74 4C 6F 63 61 74 69 6F 6E 2C 20 64 74 65 6E 64 2C 20 61 63 63 65 73 73 5F 6C 65 76 65 6C 2C 20 61 6C 6C 44 61 79 2C 20 5F 73 79 6E 63 5F 6C 6F 63 61 6C 5F 69 64 2C 20 6F 72 67 61 6E 69 7A 65 72 2C 20 6F 72 69 67 69 6E 61 6C 41 6C 6C 44 61 79 2C 20 64 65 6C 65 74 65 64 2C 20 75 72 6C 2C 20 6F 72 69 67 69 6E 61 6C 49 6E 73 74 61 6E 63 65 54 69 6D 65 2C 20 5F 73 79 6E 63 5F 64 69 72 74 79 2C 20 64 75 72 61 74 69 6F 6E 2C 20 63 6F 6C 6F 72 2C 20 67 75 65 73 74 73 43 61 6E 49 6E 76 69 74 65 4F 74 68 65 72 73 2C 20 73 65 6C 66 41 74 74 65 6E 64 65 65 53 74 61 74 75 73 2C 20 65 78 64 61 74 65 2C 20 65 76 65 6E 74 53 74 61 74 75 73 2C 20 65 76 65 6E 74 54 69 6D 65 7A 6F 6E 65 20 46 52 4F 4D 20 76 69 65 77 5F 65 76 65 6E 74 73 20 57 48 45 52 45 20 28 31 29 20 4F 52 44 45 52 20 42 59 20 5F 69 64 20 41 53 43 20 4C 49 4D 49 54 20 31 0D 0A 61 6E 64 72 6F 69 64 2E 64 61 74 61 62 61 73 65 2E 44 61 74 61 62 61 73 65 55 74 69 6C 73 2E 72 65 61 64 45 78 63 65 70 74 69 6F 6E 46 72 6F 6D 50 61 72 63 65 6C 28 44 61 74 61 62 61 73 65 55 74 69 6C 73 2E 6A 61 76 61 3A 31 35 38 29 0D 0A
10:31:01.95 OBEX Disconnect
10:31:01.95 Settimeout: RT=10000 WT=10000
10:31:01.95 [TX]: 81 00 03
10:31:02.07 [RX]: A0 00 03
10:31:02.07 Disconnect answered...
10:31:02.07 Disconnect hat funktioniert
10:31:02.07 ErrMsg: Obex Protocol kon niet worden geïnitialiseerd!!
OBEX Errorcode: D0 - Internal Server Error
10:31:04.35 DoItemUpdate
10:31:04.38 DoItemUpdate fertig
10:31:09.21 Refresh ComDescriptions...
10:31:09.26 PORT: COM6 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000000
10:31:09.26 PORT: COM8 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-communicatiepoort InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000001
10:31:09.31 MODEM: COM8 Enumerator=ROOT Displayed=Nokia E5-00 Bluetooth Modem FriendlyName=Nokia E5-00 Bluetooth Modem InstanceID=ROOT\MODEM\0000
10:31:09.31 MODEM: COM7 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth-modem FriendlyName=Bluetooth-modem InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\WCBTMODEM0\1&30EE4AD&0&1000000040001
10:31:09.93 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False
10:31:10.57 Settimeout: RT=3500 WT=800
10:31:10.57 [TX]: AT+CBC

owenWatson · Beitrag von **owenWatson** » Mi 21. Sep 2011, 02:55

I've installed 1.8.1, and it syncs texts but not Outlook 2007 appointments (which is really what I'm after): I get a "can't comminicate with Outlook" message. What do I do next?

alexander · Beitrag von **alexander** » Sa 24. Sep 2011, 15:42

I have similar problem with syncing calender. Sync Contact is OK. Sync Log indicated it has created events in my Motorola DEFY but I cannot find them on teh phone calender nor in the MPE calender on PC.

Any solution please ?

Gast · Beitrag von **Gast** » Mo 26. Sep 2011, 02:05

Attached the phone, and noticed the "what do you want to do with this device" dialog for the first time. Clicked on Sync, and MyPhoneExplorer came up, and synced events. Great!

Beitrag von FJ » Di 27. Sep 2011, 22:27

@Lucien: Your problem was caused throught the Android-Update to 2.3.3 - it has nothing to do with the versions of MyPhoneExplorer Client, your calendar-database is a littlebit damaged. I found already a workaround for this issue, please test the current beta and report the result: http://www.fjsoft.at/mpeclient.apk

@owenWatson: Ensre that Outlook was launched with the same access as MyPhoneExplorer. If you started Outlook as Admin then you have to run myPhoneExplorer also as Admin

@alexander: Is your problem still active ?

MarkAtHome · Beitrag von **MarkAtHome** » Di 11. Okt 2011, 01:27

FJ hat geschrieben:@Lucien: Your problem was caused throught the Android-Update to 2.3.3 - it has nothing to do with the versions of MyPhoneExplorer Client, your calendar-database is a littlebit damaged.

Hi FJ -- I am running Android 2.3.7 and do not see a problem. Should I be seeing one? :wink:

FrankV · Beitrag von **FrankV** » Mi 12. Okt 2011, 22:31

Hi,
the app looks good and connections are made well with mij phone (YTC Desire Z).
But the sync with outlook and MPE is not good.
Tasks are not shown on the phone, recurring task are "accidently" marked as completed, in MPE only 8 tasks are shown where I still have almost 90 items active!
It also asks almost every sync what to do with the same task, (write to phone) but somehow it doesnt.
Calender is messed up, specially recurring events (like birthdays etc) ore even items marked as "private" are suddenly not private anymore....
Contacts in MPE are still seperated, but after sync with outlook there is no mark whatsover that an adress is from facebook, linked in or others, so contacts are a mess within outlook....
I have this issues on my WXP/office pc (outlook xp), at home (XP/OL 2003) and at home w W764/OL2003).

I suppose I'n not the only one - how are these problems solved?

esteban · Beitrag von **esteban** » Do 13. Okt 2011, 08:07

Hi there I have been following up the links and I have the following problem now:

Nexus S Updated to Android 2.3.6, updated both Client and MPE SW (1.8.2)

Phone directory updates Smoother than Never and that is great! Thumbs up!

Outlook Calender does not synchronize a single entry get the OBX Error OO Phone Didn't answer Message

Any hints to overcome this?

Thx

Esteban

Nexus S is not a Smartphone is a Dumb Phone...

esteban · Beitrag von **esteban** » Do 13. Okt 2011, 08:49

Yup

I decided to go for all tests, files, messages, phone calls and Phone Entries... all works perfectly really really smooth
much smoother and faster than ever before - Great! :mrgreen:

but the calendar gives me OBEX talk and cannot overcome it for even a single entry...

I downloaded the mpeclient.apk and still only the calendar is not speaking with the phone... if we get this going we make the nobel prize of aplication development I recon..

Beitrag von FJ » Di 18. Okt 2011, 22:34

@FrankV: Which version of MyPhoneExplorer you are using ?
@esteban: Please post the logfile after the errormessage appeared

esteban · Beitrag von **esteban** » Mi 19. Okt 2011, 12:03

Here the Logfile

let me know if I need to do anything else to support you to support us...

Bests

Esteban

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.2
Datum: 2011-10-19

18:50:14.71 Setting Port: 999
18:50:14.71 Setting Baud: 115200
18:50:14.72 Avaiable Ports: COM1=\Device\Serial0;
18:50:14.72 Main Load frmSplash
18:50:14.74 Load frmSplash...
18:50:14.74 Show splash...
18:50:14.77 frmSplash geladen
18:50:15.38 Hauptfenster wird geladen
18:50:15.50 Sidebar fertig geladen
18:50:15.54 UC SMS wird geladen
18:50:15.57 UC Phonebook wird geladen
18:50:15.58 UC Phonebook fertig geladen
18:50:15.58 UC Calls wird geladen
18:50:15.60 UC Organizer wird geladen
18:50:15.65 Organizer initiated
18:50:15.68 Startpage=1
18:50:15.69 UC Filebrowser wird geladen
18:50:15.72 UC Filebrowser fertig geladen
18:50:15.72 UC AppBrowser wird geladen
18:50:15.74 UC Notes wird geladen
18:50:15.74 UC Calls wird geladen
18:50:15.75 Setting Lastuser: samsung Nexus S [357194040870297]
18:50:15.77 Lade Userdatenbank: samsung Nexus S [357194040870297]
18:50:15.82 LoadDatafile: Phonebook.dat(613268 Bytes)
18:50:16.65 Kontakte geladen
18:50:16.69 LoadDatafile: Calls.dat(10343 Bytes)
18:50:16.83 Anrufe geladen
18:50:16.85 LoadDatafile: Organizer.dat(45 Bytes)
18:50:16.85 Organizer geladen
18:50:16.85 Notizen geladen
18:50:16.85 Load SMS Data...
18:50:16.90 LoadDatafile: SMS.dat(218478 Bytes)
18:50:16.90 SMS - Datenbank wird geladen...
18:50:17.10 SMS Laden - Readfile: 47 Split: 0 Parse: 203 HandleMultiSMS: 0 Nachrichten: 1046
18:50:17.35 RefreshList (Archive): Addrows=0 Sort=0 MenuUpdate=0 Redraw=0
18:50:17.57 SMS Data Loaded...
18:50:17.57 SMS geladen
18:50:17.97 Hauptfenster fertig geladen
18:50:18.07 Init Android Connection for future connect via USB
18:50:18.07 RunADBCommand: start-server
18:50:19.24 Downloader: RC=6 BytesMax=5 URL=http://www.fjsoft.at/myphoneexplorer/version.txt
18:50:23.49 Refresh ComDescriptions...
18:50:23.51 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\0
18:50:23.85 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False
18:50:59.67 DoAdbCommand failed: ExecCmd: Timeout!
18:50:59.67 Run DeviceTracker
18:50:59.70 Init Tracker
18:50:59.72 Device Tracker Message: OKAY00183833589BB1C000EC device

18:51:03.14 DoItemUpdate
18:51:03.22 DoItemUpdate fertig
18:51:05.13 RunADBCommand: start-server
18:51:05.19 ADB CommandResponse:
18:51:05.19 RunADBCommand: devices
18:51:05.28 ADB CommandResponse: List of devices attached
3833589BB1C000EC device
18:51:05.28 RunADBCommand: -s 3833589BB1C000EC forward tcp:5210 tcp:5210
18:51:05.35 ADB CommandResponse:
18:51:05.35 Try connecting to 127.0.0.1...
18:51:05.36 Socket closed
18:51:05.36 RunADBCommand: -s 3833589BB1C000EC shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
18:51:06.33 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }
18:51:06.49 Try launch USB connection
18:51:06.50 Socket closed
18:51:06.80 Try launch USB connection
18:51:06.92 Connect to Android OK
18:51:06.92 Settimeout: RT=2000 WT=500
18:51:06.92 bOpened=True
18:51:06.92 [TX]: AT+CGSN
18:51:06.97 [RX]: AT+CGSN
18:51:06.97 [RX]: 357194040870297
18:51:06.97 [RX]: OK
18:51:06.97 Settimeout: RT=15000 WT=1000
18:51:06.97 [TX]: AT*PIN?
18:51:07.00 [RX]: AT*PIN?
18:51:07.00 [RX]: *PIN: ACCESS OK,10
18:51:07.00 [RX]: OK
18:51:07.00 [TX]: ATI
18:51:07.03 [RX]: ATI
18:51:07.03 [RX]: samsung Nexus S
18:51:07.03 [RX]: OK
18:51:07.03 [TX]: AT*APPVERSION=1.8.2
18:51:07.06 [RX]: AT*APPVERSION=1.8.2
18:51:07.06 [RX]: 10,1.0.12
18:51:07.06 [RX]: OK
18:51:07.11 [TX]: AT+CSCS="UTF-8"
18:51:07.14 [RX]: AT+CSCS="UTF-8"
18:51:07.14 [RX]: OK
18:51:07.14 [TX]: AT+CNMI=2,1,0,1
18:51:07.20 [RX]: AT+CNMI=2,1,0,1
18:51:07.20 [RX]: ERROR
18:51:07.20 [TX]: AT*ECAM=1
18:51:07.24 [RX]: AT*ECAM=1
18:51:07.24 [RX]: OK
18:51:07.24 [TX]: AT+CIND=?
18:51:07.27 [RX]: AT+CIND=?
18:51:07.27 [RX]: ERROR
18:51:07.27 [TX]: AT+CBC
18:51:07.33 [RX]: AT+CBC
18:51:07.33 [RX]: +CBC: 1,79
18:51:07.36 [RX]: OK
18:51:07.36 [TX]: AT+CSQ
18:51:07.39 [RX]: AT+CSQ
18:51:07.39 [RX]: +CSQ: 21,99
18:51:07.39 [RX]: OK
18:51:07.39 Alle Verbindungsaktionen beendet
18:51:07.39 [TX]: AT*SOPS
18:51:07.42 [RX]: AT*SOPS
18:51:07.42 [RX]: *SOPS: CMCC,46002,cn
18:51:07.42 [RX]: OK
18:51:07.50 Form_Activate fSync Operation=7
18:51:07.52 [TX]: AT+CPROT=0
18:51:07.55 [RX]: AT+CPROT=0
18:51:07.55 [RX]: CONNECT
18:51:07.55 OBEX Connect: 16384 Bytes Paketgröße, Target: IRMC-SYNC
18:51:07.55 [TX]: 80 00 13 10 00 40 00 46 00 0C 49 52 4D 43 2D 53 59 4E 43
18:51:07.99 [RX]: A0 00 18 10 00 FF FF CB 00 00 00 01 4A 00 0C 49 52 4D 43 2D 53 59 4E 43
18:51:07.99 Connection ID:1
18:51:07.99 Paketgröße: 16384, maximal möglich:65535
18:51:07.99 Ermittle und verarbeite info.log
18:51:07.99 Settimeout: RT=20000 WT=10000
18:51:07.99 OBEX Get: telecom/cal/info.log
18:51:07.99 [TX]: 83 00 35 CB 00 00 00 01 01 00 2D 00 74 00 65 00 6C 00 65 00 63 00 6F 00 6D 00 2F 00 63 00 61 00 6C 00 2F 00 69 00 6E 00 66 00 6F 00 2E 00 6C 00 6F 00 67 00 00
18:51:12.85 [RX]: D0 02 B2 4C 02 AF 61 6E 64 72 6F 69 64 2E 64 61 74 61 62 61 73 65 2E 73 71 6C 69 74 65 2E 53 51 4C 69 74 65 45 78 63 65 70 74 69 6F 6E 3A 20 43 61 6E 27 74 20 75 70 67 72 61 64 65 20 72 65 61 64 2D 6F 6E 6C 79 20 64 61 74 61 62 61 73 65 20 66 72 6F 6D 20 76 65 72 73 69 6F 6E 20 35 20 74 6F 20 34 3A 20 2F 64 61 74 61 2F 64 61 74 61 2F 63 6F 6D 2E 66 6A 73 6F 66 74 2E 6D 79 70 68 6F 6E 65 65 78 70 6C 6F 72 65 72 2E 63 6C 69 65 6E 74 2F 64 61 74 61 62 61 73 65 73 2F 74 61 73 6B 73 2E 64 62 0D 0A 61 6E 64 72 6F 69 64 2E 64 61 74 61 62 61 73 65 2E 73 71 6C 69 74 65 2E 53 51 4C 69 74 65 4F 70 65 6E 48 65 6C 70 65 72 2E 67 65 74 52 65 61 64 61 62 6C 65 44 61 74 61 62 61 73 65 28 53 51 4C 69 74 65 4F 70 65 6E 48 65 6C 70 65 72 2E 6A 61 76 61 3A 31 39 39 29 0D 0A 63 6F 6D 2E 66 6A 73 6F 66 74 2E 6D 79 70 68 6F 6E 65 65 78 70 6C 6F 72 65 72 2E 74 61 73 6B 73 2E 54 61 73 6B 73 53 74 6F 72 65 2E 71 75 65 72 79 28 54 61 73 6B 73 53 74 6F 72 65 2E 6A 61 76 61 3A 31 32 36 29 0D 0A 63 6F 6D 2E 66 6A 73 6F 66 74 2E 6D 79 70 68 6F 6E 65 65 78 70 6C 6F 72 65 72 2E 63 6C 69 65 6E 74 2E 43 61 6C 65 6E 64 61 72 57 6F 72 6B 65 72 2E 67 65 74 45 76 65 6E 74 73 43 6F 75 6E 74 28 43 61 6C 65 6E 64 61 72 57 6F 72 6B 65 72 2E 6A 61 76 61 3A 36 31 36 29 0D 0A 63 6F 6D 2E 66 6A 73 6F 66 74 2E 6D 79 70 68 6F 6E 65 65 78 70 6C 6F 72 65 72 2E 63 6C 69 65 6E 74 2E 43 61 6C 65 6E 64 61 72 57 6F 72 6B 65 72 2E 67 65 74 44 61 74 61 28 43 61 6C 65 6E 64 61 72 57 6F 72 6B 65 72 2E 6A 61 76 61 3A 34 30 34 29 0D 0A 63 6F 6D 2E 66 6A 73 6F 66 74 2E 6D 79 70 68 6F 6E 65 65 78 70 6C 6F 72 65 72 2E 63 6C 69 65 6E 74 2E 4F 42 45 58 57 6F 72 6B 65 72 2E 68 61 6E 64 6C 65 4D 65 73 73 61 67 65 28 4F 42 45 58 57 6F 72 6B 65 72 2E 6A 61 76 61 3A 32 35 35 29 0D 0A 63 6F 6D 2E 66 6A 73 6F 66 74 2E 6D 79 70 68 6F 6E 65 65 78 70 6C 6F 72 65 72 2E 63 6C 69 65 6E 74 2E 54 43 50 53 65 72 76 65 72 2E 72 75 6E 28 54 43 50 53 65 72 76 65 72 2E 6A 61 76 61 3A 31 31 35 29 0D 0A 6A 61 76 61 2E 6C 61 6E 67 2E 54 68 72 65 61 64 2E 72 75 6E 28 54 68 72 65 61 64 2E 6A 61 76 61 3A 31 30 31 39 29 0D 0A
18:51:12.85 ObexGet Fertig, Returncode=D0
18:51:12.85 OBEX Errorcode: D0 - Internal Server Error
18:51:12.85 Info.log:

18:51:12.85 Settimeout: RT=90000 WT=10000
18:51:12.85 OBEX Get: telecom/cal/initsync
18:51:12.85 [TX]: 83 00 35 CB 00 00 00 01 01 00 2D 00 74 00 65 00 6C 00 65 00 63 00 6F 00 6D 00 2F 00 63 00 61 00 6C 00 2F 00 69 00 6E 00 69 00 74 00 73 00 79 00 6E 00 63 00 00
18:52:35.58 WM_POWERBROADCAST 10
18:52:42.87 [RX]: 00
18:52:42.87 Lesevorgang fehlerhaft! - Systemerror: 0 [The operation completed successfully.]
18:52:42.87 ObexGet Fertig, Returncode=0
18:52:42.87 OBEX Errorcode: 00 - Phone didn't answer, Timeout
18:52:42.87 ErrMsg: OBEX Errorcode: 00 - Phone didn't answer, Timeout
18:53:13.81 OBEX Disconnect
18:53:13.81 Settimeout: RT=10000 WT=10000
18:53:13.81 [TX]: 81 00 08 CB 00 00 00 01
18:53:23.81 [RX]: 00
18:53:23.81 Lesevorgang fehlerhaft! - Systemerror: 0 [The operation completed successfully.]
18:53:23.81 Disconnect answered...
18:53:23.81 DoItemUpdate
18:53:23.83 DoItemUpdate fertig
18:53:27.46 Settimeout: RT=3500 WT=800
18:53:27.46 [TX]: AT+CBC
18:53:30.96 Androidsocket wird geschlossen 7
18:53:30.96 Port wurde geschlossen
19:00:45.45 Refresh ComDescriptions...
19:00:45.48 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\0
19:00:45.79 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False

FJ Software