Cannot connect to exchange server
I am trying to connect to my exchange server and I get this error when the calendar creation is final:
ERROR CODE: MODIFICATION_FAILED
<?xml version="1.0" encoding=
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Internal server error with no detail :/
Can you please:
1. add "//" in front of the "return;" statement in the "sdbg()" function in <email address hidden>
2a. go to Edit->Preferenc
2b. right click->New->Boolean "browser.
Then run thunderbird from a terminal and paste the (relevant) output.
Revision history for this message
|
#2 |
Added requested info. I created a new calendar and this was the output I got.
User:<email address hidden>
Server: https://<email address hidden>
Init
doRequest
doRequest
doRequest
doRequest
doRequest
doRequest
do init
getAccount
Sending: <?xml version="1.0" encoding=
do init done
getInterface
IID: {d974c99e-
getInterface
IID: {09b54ec1-
getInterface
IID: {bd9dc0fa-
getInterface
IID: {447fc780-
getInterface
making prompt
reply
<?xml version="1.0" encoding=
fail status: 500 <?xml version="1.0" encoding=
Sending: <?xml version="1.0" encoding=
getInterface
IID: {d974c99e-
reply
<?xml version="1.0" encoding=
fail status: 500 <?xml version="1.0" encoding=
Sending: <?xml version="1.0" encoding=
getInterface
IID: {d974c99e-
reply
<?xml version="1.0" encoding=
fail status: 500 <?xml version="1.0" encoding=
Sending: <?xml version="1.0" encoding=
getInterface
IID: {d974c99e-
reply
<?xml version="1.0" encoding=
fail status: 500 <?xml version="1.0" encoding=
Sending: <?xml version="1.0" encoding=
getInterface
IID: {d974c99e-
reply
<?xml version="1.0" encoding=
fail status: 500 <?xml version="1.0" encoding=
Sending: <?xml version="1.0" encoding=
getInterface
IID: {d974c99e-
reply
<?xml version="1.0" encoding=
fail status: 500 <?xml version="1.0" encoding=
doRequest
Sending: <?xml version="1.0" encoding=
getInterface
IID: {d974c99e-
reply
<?xml version="1.0" encoding=
fail status: 500 <?xml version="1.0" encoding=
Revision history for this message
|
#3 |
Thanks, these requests do look correct. I have no idea why exchange would report an internal server error.
Do other clients work with this server? Do you have a way to find out why the server is reporting an internal error?
Revision history for this message
|
#4 |
I am encountering the same problem with the same error message. Has the problem been fixed in the meantime?
Revision history for this message
|
#5 |
No, I don't have any idea why an internal server error would happen. Do you have a way to find out why the server is reporting an internal error?
Revision history for this message
|
#6 |
Sorry, I have no idea. I will ask our exchange admins. However, I do not believe that they have an idea how to solve this problem.
Revision history for this message
|
#7 |
Did you ever find a solution or more details about this fault?
Revision history for this message
|
#8 |
No, unfortunately not. It is still not working.
Revision history for this message
|
#9 |
Did you manage to obtain details from the exchange admins? An error log, etc? Right now I'm quite at loss as to what might be going on.
Revision history for this message
|
#10 |
Just phoned with our exchange admins. They were unable to find any information in the exchange error logs.
Revision history for this message
|
#11 |
Greetings,
I was getting similar failures as above and was coming here to add my error output to this thread until I tried something...
From the above error messages, I looked at how it was being formatted for entry into the "Location" field in the "Create New Calendar" dialog and tried doing the following that worked for me! :-)
1.) In the Location field, format the entry as follows:
https://<account name>@<Exchange server hostname>.<AD Domain Name>.<standard domain name>.com/
2.) When entering the login information for setting up the calendar, watch for the double-backslash. E.g.:
Login: <AD Domain Name>\\<account login>
Password: <password>
Hope this helps.
Revision history for this message
|
#12 |
Following up on my last post:
After looking at what I posted, I realized it still might not be clear, so I am going to clarify what I was saying above:
If your email address is <email address hidden> and your Active Directory domain is TCAD and your exchange server's FQDN name is exchserv.
a.) In the Location field, put https://<email address hidden>
b.) In the Login dialog that comes up after the "Create New Calendar" dialog, put:
Login: tcad\\jsmith
Password: <your password>
NOTE: While it seems to definitely want the double-backslash when logging in for the calendar right after the initial creation/setup of the calendar, it seems hit-or-miss if it wants double- or single-backslash when you close Thunderbird out and re-open it. I added my calendar as well as the company's "Master Calendar", and when I log into my calendar, it's happy with a single-backslash, but the Master Calendar wants single-backslash sometimes and double-backslash at others.
But, that is a different issue than this thread covers.
HTH.
Revision history for this message
|
#13 |
Hmm, this is my first try to use this addon.
The server I want to use is a exchange 2007 system. The webinterface is up an running (owa.<domain>). I can login using a browser using my <AD Username>, not using <my mail address>
In the localtion filed I put https://<my mail address>
In the login dialog I put: <AD Domain>\<my username>
==> no success.
What to I have to use in the location field ? https://<my username>
Regards
Peter
Revision history for this message
|
#14 |
can you try https://<ad domain>
Revision history for this message
|
#15 |
Had same problems like #13.
#14 solved it.
Please update section 'Usage and documentation'. It will save a lot of time in starting with your extension.
Thanx in advance
Thomas
Revision history for this message
|
#16 |
Do the steps of the updated documentation work for you?
Revision history for this message
|
#17 |
Unfortunately, it is still not working. Maybe it is because of the exchange server version. We are using exchange server 2003.
Revision history for this message
|
#18 |
Yes, Exchange 2003 does not support Exchange Web Services (EWS). You will have to upgrade to Exchange 2007 or 2010.
Revision history for this message
|
#19 |
Hello
I'm trying to use the provider with Exchange 2003 (I think, maybe it's 2007 after all:!!)
Actually, when type in in a browser, the wsdl URL does retrieve data that seems correct, but nothing appear in Lightning.
I dont know how to retrieve calendar log files on XP though. There is only one XML error in the console for the wsdl page (missing /META tag).
Thanks
Revision history for this message
|
#20 |
I don't exactly know what you mean by wdsl URL. Exchange 2003 does not support EWS, AFAIK.
You can obtain logs from the error console.
Revision history for this message
|
#21 |
Hello
I meant that URL: https:/
That URL is available on my corporate servers, and I have checked: it's actually Exchange 2007, you're perfectly right :)
Thanks
Revision history for this message
|
#22 |
... and the only errors I get when creating the calendar are those:
Erreur : balise ne correspondant pas. Attendu : </META>.
Fichier source : https:/
Ligne : 11, Colonne : 3
Code source :
</HEAD><BODY><TABLE width=500 border=0 cellspacing=
(and a green arrow pointing to /HEAD)
----------
Erreur : missing = in XML attribute
Code source :
<parent xmlns=""><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://
(and a gree arrow pointing to PUBLIC)
Thanks
Revision history for this message
|
#23 |
I don't think you can use Services.wsdl. The correct URL is /EWS/Exchange.asmx
Revision history for this message
|
#24 |
I'm so stupid, the other URL is just the web service description, right? Don't know where I took that...
And the good news is that it is working far better now, thanks :)
Revision history for this message
|
#25 |
This bug has become a support box for configuration issues. Let's use a question for this instead.
Revision history for this message
|
#26 |
Hi!
I also get the same error message "modification failed" when connecting to the exchange server. Changing the URL does not help as well.
Is there some solution out now or under construction?
Thanks a lot!
Revision history for this message
|
#27 |
Which Exchange are you connecting to? What's the URL you're using?
Revision history for this message
|
#28 |
I tried
https://<ad domain>
and all others mentioned in this discussion and on your "how-to-do".
Our Server is a Microsoft Exchange 2007 Server.
Revision history for this message
|
#29 |
could you try the latest git version and use the @auto feature?
Revision history for this message
|
#30 |
How do I get the git version on a windows platform?
Revision history for this message
|
#31 |
You can download the latest development version from <http://
Revision history for this message
|
#32 |
I did so, unfortunately same result.
Is there a way to check for me, which URLs in combination with login names and domains is working for me? The ideas in this 'answer' are a bit confusing.
does 'modification_
Revision history for this message
|
#33 |
Can you please capture the calendar logs when using the autodetect URL?
Revision history for this message
|
#35 |
I believe the problem for the missing autodetection is that the thunderbird addon manager still says that the version of lightning change provider is 0.8 ( despite following your copy instructions). I also followed the debugging instruction, but failed running thunderbird from a console. Sorry for being so stupid. What is a console and how run thunderbird there?
logging the error console is not a problem. I am using Windows Vista and Thunderbird 3.1.2. Does the whole thing work with Vista?
Thanks a lot for your help and especially for your patience with me.
Revision history for this message
|
#36 |
Can you try downloading 0.10 and see whether it still doesn't work for you?
Can you help with this problem?
Provide an answer of your own, or ask Dan Radigan for more information if necessary.