Re: [SyncEvolution] SoupTransport Failure: http://../syncevolution via libsoup: D-Bus server done

I've started getting an error message I don't understand when trying to sync between two peers: jwd@maple ~ $ syncevolution --sync refresh-from-server redwood-server todo [INFO] pat: inactive [INFO] personal-projects: inactive [INFO] work-calendar: inactive [INFO] personal-blocked: inactive [INFO] events: inactive [INFO] memo: inactive [INFO] work-blocked: inactive [INFO] addressbook: inactive [INFO] commute: inactive [INFO] calendar: inactive [INFO] work: inactive [INFO] SoupTransport Failure: http://redwood:9000/syncevolution via libsoup: D-Bus server done ^X[INFO] SyncContext: resend previous request #1 [INFO] SoupTransport Failure: http://redwood:9000/syncevolution via libsoup: D-Bus server done ^[[1;5D^[[1;5D[INFO] SyncContext: resend previous request #1 [INFO] SoupTransport Failure: http://redwood:9000/syncevolution via libsoup: D-Bus server done The SoupTransport error messages repeat until SE gives up. The same thing happens no matter which source (or all) I try to sync. The same thing also occurs if I try a --sync refresh-from-server. This is an SE 1.1 client talking to an SE 1.1 server, which is using the Evolution backends. The log on the server side shows _two_ _successful_ sessions for each "SoupTransport Failure" message on the client side. These two peers were syncing with each other yesterday. The change I mad this morning was to add a source to the configuration on both sides. However, that source is not involved in the above attempt. Can anyone suggest where to look to troubleshoot this problem?