Menu
▾
▴
opensync-users
|
From: Soeren S. <ope...@nn...> - 2008-05-02 07:02:44
|
Dear all, I successfully managed to use libsyncml from current svn to do receive the contacts via $ syncml-obex-client -b 00:11:22:33:44:55 10 --slow-sync text/x-vcard contacts --wbxml --identifier "PC Suite" However trying to receive the calendar entries always results in Forbidden (0x43) and the phone saying 'system error': $ syncml-obex-client -b 00:11:22:33:44:55 10 --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" connection with device succeeded Received an Alert for the DS Server at Calendar: Type: 201, Last , Next 20080502T053518Z Slowsyncing Just received a new session with ID 1 Received the DevInf Session 1 reported final. flushing Received an transport error: Forbidden (0x43) SYNCML_LOG/SYNCML_TRACE's are here: http://nn7.de/debugging/syncml/sent-0.xml http://nn7.de/debugging/syncml/received-0.xml http://nn7.de/debugging/syncml/sent-1.xml http://nn7.de/debugging/syncml/Thread3079489312-30333.log http://nn7.de/debugging/syncml/Thread3079486352-30333.log Ideas welcome, Soeren |
|
From: Christian H. <Chr...@co...> - 2008-05-02 08:55:33
|
Soeren Sonnenburg schrieb: > $ syncml-obex-client -b 00:11:22:33:44:55 10 --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" > connection with device succeeded > Received an Alert for the DS Server at Calendar: Type: 201, Last , Next 20080502T053518Z > Slowsyncing <--- (*) > Just received a new session with ID 1 > Received the DevInf > Session 1 reported final. flushing > Received an transport error: Forbidden (0x43) ... > Ideas welcome, http://libsyncml.opensync.org/ticket/143 Rootcause seems to be a slow sync requested (*) from the mobile and the libsycml sends improper answers. That cause the forbidden from the phone. Michael Bell knows the root cause. Christian -- Christian Hilgers |ConSol* Tel. +49.2102.994-423 |Consulting&Solutions Software GmbH Fax +49.2102.994-411 |Berliner Str. 101, 40880 Ratingen email: Chr...@co... |WWW: http://www.consol.de |
|
From: Soeren S. <ope...@nn...> - 2008-05-02 10:27:33
|
On Fri, 2008-05-02 at 10:55 +0200, Christian Hilgers wrote: > Soeren Sonnenburg schrieb: > > > $ syncml-obex-client -b 00:11:22:33:44:55 10 --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" > > connection with device succeeded > > Received an Alert for the DS Server at Calendar: Type: 201, Last , Next 20080502T053518Z > > > Slowsyncing <--- (*) > > > Just received a new session with ID 1 > > Received the DevInf > > Session 1 reported final. flushing > > Received an transport error: Forbidden (0x43) > ... > > > Ideas welcome, > > http://libsyncml.opensync.org/ticket/143 Actually in this ticket there is a text/x-vcard request which seems to work fine here (why?). But not the text/x-vcalendar variant... > Rootcause seems to be a slow sync requested (*) from the > mobile and the libsycml sends improper answers. > That cause the forbidden from the phone. > > Michael Bell knows the root cause. That name rings a bell, cc'ing him :-) Would be interested in knowing what the root cause is and what part needs fixing. Soeren. |
|
From: xyon <xy...@in...> - 2008-05-02 12:50:56
|
> Actually in this ticket there is a text/x-vcard request which seems to > work fine here (why?). But not the text/x-vcalendar variant... I seem to be having a similar problem with the n95. > That name rings a bell, cc'ing him :-) Would be interested in knowing > what the root cause is and what part needs fixing. Could you please post your findings to the list? |
|
From: Christian H. <Chr...@Co...> - 2008-05-29 13:46:08
|
dpreiss wrote: > I'm having this problem since i updated my n95 from 12.0.001 to 14.0.00. > Before it worked with opensync 0.32 (the debian packet). > After the update i tried opensync 0.22, 0.32 and 0.36 all with the same > result: Syncing just contacts works, syncing calendar (solo or with > contacts) does not. Could you sync once using the vendor software and test afterwards again using opensync. I expect the error is gone then. If yes, see my comment in http://libsyncml.opensync.org/ticket/143 If not, you found another bug. Christian -- Christian Hilgers |ConSol* Tel. +49.2102.994-423 |Consulting&Solutions Software GmbH Fax +49.2102.994-411 |Berliner Str. 101, 40880 Ratingen email: Chr...@co... |WWW: http://www.consol.de |
|
From: dpreiss <dp...@wi...> - 2008-05-29 19:57:22
|
Christian, Christian Hilgers-2 wrote: > > Could you sync once using the vendor software and test afterwards > again using opensync. > do you mean using Nokia PC Suite under Windows ? Best reagrds, Dieter -- View this message in context: http://www.nabble.com/Nokia-E90%3A-syncml-obex-client---slow-sync-text-x-vcalendar%09Calendar-transport-error%3A-Forbidden-%280x43%29-tp17014811p17544506.html Sent from the Opensync - User mailing list archive at Nabble.com. |
|
From: xyon <xy...@in...> - 2008-05-29 21:08:58
|
> do you mean using Nokia PC Suite under Windows ? Yes, I believe that's what he means. Did you know they have version 20.x firmware out for n95? I have not tried anything higher than 12.0.013 yet, but am anxious to hear how people like 20.x. I would recommend starting fresh with everything (clear out n95 from all calendar, task, contact entries; then mv ~/.opensync to ~/.opensync-backup and recreate the sync group; then do a fresh sync). opensync+n95 has always worked well when starting clean for me. -- xyon |
|
From: dpreiss <dp...@wi...> - 2008-05-30 06:54:22
|
Hello xyon, xyon wrote: > > Did you know they have version 20.x firmware out for n95? I have not tried > anything higher than 12.0.013 yet, but am anxious to hear how people like > 20.x. > I 've seen taht already. I think threr are different version number for free and branded and maybe international versions versions. Mine is a t-mobile version. 14.0.001 is the only version offered by Nonkia's updater. I would like to debrand the phone if i can be sure not to burn it. xyon wrote: > > I would recommend starting fresh with everything (clear out n95 from all > calendar, task, contact entries; then mv ~/.opensync to ~/.opensync-backup > and recreate the sync group; then do a fresh sync). opensync+n95 has > always > worked well when starting clean for me. > This is what i did when my opensync 0.32 failed. I first removed that version and installed an "offical stable" 0.22 and started fron scratch. Then i removed 0.22 completely and complied 0.36, where the syncml plugin did not compile, probably due to a script problem. So i took svn, but copied the src-dir from 0.36 to remain consistent. I also started without an existing .opensync dir. This version also shows the same problem with n95. Another interesting Detail (all nokia 14.0.001): Using 0.22 or 0.32, the phone displays a "Serverfehler" (Server fault) message. Using 0.36, the msynctool log still says Forbidden (0x43), but the phone now displays a different message: "Sychronisationsserver-Fehler" (sync server fault). Before n95 update it worked quite well with 0.32. So now i'll try Christian's suggestion and post the results later. I also found a crash (segfault) in the http-Server of 0.36 if the server path name the phone requests is not found and a hanging process if path is ok. But i did not check it against the bug list so it needs some more investigation if this is a new issue. Best regards, Dieter -- View this message in context: http://www.nabble.com/Nokia-E90%3A-syncml-obex-client---slow-sync-text-x-vcalendar%09Calendar-transport-error%3A-Forbidden-%280x43%29-tp17014811p17552769.html Sent from the Opensync - User mailing list archive at Nabble.com. |
|
From: Christian H. <Chr...@co...> - 2008-05-30 12:13:50
|
xyon schrieb: > I would recommend starting fresh with everything (clear out n95 from all > calendar, task, contact entries; then mv ~/.opensync to ~/.opensync-backup > and recreate the sync group; then do a fresh sync). opensync+n95 has always > worked well when starting clean for me. If the problem is the one I assume this will not work, as the mobile asks for a slow-sync and opensync/libsyncml reacts wrong then. Christian -- Christian Hilgers |ConSol* Tel. +49.2102.994-423 |Consulting&Solutions Software GmbH Fax +49.2102.994-411 |Berliner Str. 101, 40880 Ratingen email: Chr...@co... |WWW: http://www.consol.de |
|
From: xyon <xy...@in...> - 2008-05-30 12:08:44
|
> I 've seen taht already. I think threr are different version number for > free and branded and maybe international versions versions. Mine is a > t-mobile version. 14.0.001 is the only version offered by Nonkia's updater. > I would like to debrand the phone if i can be sure not to burn it. My n95 is "unlocked" (from Buy.com, n95-1) and works fine, perhaps you can look at ways of unlocking yours, but am not sure if this is the root of your issue. > Before n95 update it worked quite well with 0.32. From my direct experience, using anything other than 0.32 compounds sync issues significantly (including introducing that forbidden (0x43) error). I personally would suggest sticking to opensync 0.32 and libsyncml 0.4.5. > So now i'll try Christian's suggestion and post the results later. Best of luck, hope it works out for you. -- xyon |
|
From: dpreiss <dp...@wi...> - 2008-05-30 13:24:06
|
xyon wrote: > > Best of luck, hope it works out for you. > Indeed, it did! I had to sync both kontacts and calendar with the supplier tool, then the n95 stopped to give "Forbidden" to opensync. Using 0.36, the sync procedure hung at its end. Reverting back to 0.32+, everything suceeded. Thanks, Christian, this was a hot hint! -- dieter xyon ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Opensync-users mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/opensync-users -- View this message in context: http://www.nabble.com/Nokia-E90%3A-syncml-obex-client---slow-sync-text-x-vcalendar%09Calendar-transport-error%3A-Forbidden-%280x43%29-tp17014811p17558797.html Sent from the Opensync - User mailing list archive at Nabble.com. |
|
From: Soeren S. <ope...@nn...> - 2008-06-09 16:43:24
|
On Fri, 2008-05-30 at 06:24 -0700, dpreiss wrote: > > > xyon wrote: > > > > Best of luck, hope it works out for you. > > > > Indeed, it did! I had to sync both kontacts and calendar with the supplier > tool, then the n95 stopped to give "Forbidden" to opensync. Using 0.36, the > sync procedure hung at its end. Reverting back to 0.32+, everything > suceeded. > Thanks, Christian, this was a hot hint! indeed that also makes it work for me, except that opensync 0.22 fails sending more than 293 calendar entries. Opensync 0.36 also fails here (crashes with a double free). As I would like this phone to reliably work at some point, which versions should I try, the upcomming 0.40 branch? Soeren |
|
From: dpreiss <dp...@wi...> - 2008-05-29 13:25:49
|
Deare Soeren, xyon wrote: > > > Could you please post your findings to the list? > > I'm having this problem since i updated my n95 from 12.0.001 to 14.0.00. Before it worked with opensync 0.32 (the debian packet). After the update i tried opensync 0.22, 0.32 and 0.36 all with the same result: Syncing just contacts works, syncing calendar (solo or with contacts) does not. Best regards, Dieter -- View this message in context: http://www.nabble.com/Nokia-E90%3A-syncml-obex-client---slow-sync-text-x-vcalendar%09Calendar-transport-error%3A-Forbidden-%280x43%29-tp17014811p17535817.html Sent from the Opensync - User mailing list archive at Nabble.com. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X