9:49 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/07/12 23:14, Patrick Ohly wrote:
On Tue, 2012-07-03 at 23:04 +1200, Jane Atkinson wrote:
> On 03/07/12 22:07, Patrick Ohly wrote:
>> On Tue, 2012-07-03 at 21:47 +1200, Jane Atkinson wrote:
>>> My Nokia E63 is no longer able to sync the calendar. I'm not
>>> quite sure what caused it, but suspect something to do with
>>> attempting to set my caldav connections to SSL. I've since
>>> reverted these to plain HTTP, but the problem persists.
>>>
>>> Specifically, I keep getting
>>>
>>> error code from SyncEvolution authorization failed (remote,
>>> status 401): REPORT 'full calendar': bad HTTP status:
>>> <status 1.1, code 401, class 4, Unauthorized>
>>>
>>> Trying --sync refresh-from-local removes all the entries
>>> from the phone but will not allow anything to be written to
>>> it.
>>>
>>> Even after formatting, the problem persists.
>>>
>>> Any ideas how to fix?
>>
>> The problem is in the access to the WebDAV data. Username
>> and/or password seem to be wrong.
>>
>> Are you sure you spelled the URL in the "database" property
>> exactly as before? Looking up the "databasePassword" uses the
>> URL as key in GNOME keyring.
>>
>> I suggest that you set the "databasePassword" property again,
>> which will ensure that there is a matching entry in the GNOME
>> keyring.
>>
>
> Actually, it was a phone@webdav config that I'd just setup, and
> I'd forgotten to add the username and password to the
> appropriate config.ini file (oops). Now it's working.
The core question of course is: why wasn't it obvious from the
available output? How can that output be improved so that I don't
have to be involved in deciphering it? ;-)
"error code from SyncEvolution authorization failed" lacks some
kind of separator between "error code from SyncEvolution" and
"authorization failed".
Whether it is an error "from SyncEvolution" is open for debate: it
is encountered inside SyncEvolution but in reality comes from the
remote WebDAV server. It probably should be marked as "remote
problem".
Finally, there's no correlation with the affected source. That's
because the code doesn't know that it is running as part of a
source, something that has to be changed.
If I recall rightly, in a webdav config "remote" refers to the phone,
not the caldav server. Which is why I got fixated on the phone as
being the problem.
Something along the lines of "caldav URL / username / password
incorrect" or "Check caldav server connection / authentication
details" would have made it clear where to look.
Jane Atkinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJP8txcAAoJEERzSJEx033jbg0H/1lHzrvhpIpYYF3jkp5psoK5
u8s1Yg/rFGAjSNChQ74YKoLG4WiqiAVAorH+vgmXJxvVLI2aC4hdRY+rIVL4Vf0I
riR8nz32rNNsKOgh/opog+vgalATyPieOVfegm4ReeCs88dkiIRTIsat2/7jvPcd
WhqvP/tC3wRNhgGkq6+p665cftscLajgGy3dr7CCqFxoD0pkqrrp3QkWuKluvk1k
Qw8tC6Af94dahqYzZXngQS8Va/KoJM5jlTY41sZ0brkrtMI+dZsRmsf/SAGHqmLI
uaOLJfXfPUxiWitsu9AvvZGqDEk5Ee97GG1FR6HSaOeAqPQoWwhGdBev/op6gjg=
=eCjh
-----END PGP SIGNATURE-----