Cannot connect to Novell Data Synchronizer
Hi,
We installed Novell Groupwise here at the company and are using Novell Mobility Data Synchronizer to sync mail and calendar items to phones and tablets. That is using the Exchange protocol, so I reckoned I could also use your data provider for thunderbird (I don't like Evolution that much ...)
However, when following your instructions, I always get the following error: MODIFICATION_
Can you help me setting it up, or figuring out what could cause the problem?
TIA
Bart Friederichs
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#2 |
How should I run Thunderbird to do that?
Revision history for this message
|
#3 |
See the wiki for instructions.
Revision history for this message
|
#4 |
Following the result of the debug log.
From what I understand, the server gives a HTTP500, internal server error. Note though, that with all other exchange connectors (N900 phone, iPad, Android), I only provide the server name and a username and password. No domain, no "/EWS/Exchange.
Regards
Bart
unknown [object Object]: User:<DOMAIN>
unknown [object Object]: Server: https://<DOMAIN>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
[calTimezoneSer
[calTimezoneSer
dcf9b717-
[calAlarmService] starting...
dcf9b717-
dcf9b717-
dcf9b717-
*** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable).
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
unknown [object Object]: User:
unknown [object Object]: Server: https://<FQDN>/
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
dcf9b717-
dcf9b717-
dcf9b717-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
a91f05a5-
a91f05a5-
a91f05a5-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
dcf9b717-
dcf9b717-
dcf9b717-
dcf9b717-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
dcf9b717-
dcf9b717-
dcf9b717-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
<soap:Envelope xmlns:soap="http://
<soap:Header>
<t:
</soap:Header>
<soap:Body>
<m:FindItem Traversal=
<m:ItemShape>
<
<
<
<
<
</m:FindItem>
</soap:Body>
</soap:Envelope>
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
a91f05a5-
Revision history for this message
|
#5 |
Can you make sure that this is an Exchange 2007 or 2010 server and that EWS is enabled? It looks like a server configuration issue.
Revision history for this message
|
#6 |
As I said, this is a Novell Groupwise Server.
What exactly is EWS?
It seems to be enabled, because when I browse to the URL https://<server>
Revision history for this message
|
#7 |
EWS is Exchange Web Services. I don't know if Novell supports that.
Revision history for this message
|
#8 |
From the Novell website:
In general, the Mobility Connector works with devices that:
* Support connecting to MS Exchange 2003 SP2 or later
I guess it uses the old protocol.
Revision history for this message
|
#9 |
From another part of the novell site:
What version of ActiveSync do you use?
ActiveSync Protocol ver 2.5
My whole idea of connecting to this mobility server using the exchange protocol was flawed.
Revision history for this message
|
#10 |
The provider does not use mobily or activesync, but EWA.
Can you help with this problem?
Provide an answer of your own, or ask Bart for more information if necessary.