You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using pyexchange 0.6(latest as of now).
I am running my python script in Linux.
I am trying to connect to Outlook Exchange Server using this module.
I am getting an error which says,
python3.5/site-packages/pyexchange-0.6-py3.5.egg/pyexchange/base/soap.py", line 42, in _parse
raise FailedExchangeException(u"Unable to parse response from Exchange - check your login information. Error: %s" % err)
pyexchange.exceptions.FailedExchangeException: Unable to parse response from Exchange - check your login information. Error: Double hyphen within comment: <!--[if lt IE 9]>
<link rel="stylesheet" href="inc, line 16, column 87 (, line 16)
Can someone please help?
Please Note:
The exact same script works fine in my windows environment without any errors.
I am using the same pyexchange and lxml modules (versions) in both the environments.
Thanks,
Phani.
The text was updated successfully, but these errors were encountered:
Hi,
I am using pyexchange 0.6(latest as of now).
I am running my python script in Linux.
I am trying to connect to Outlook Exchange Server using this module.
I am getting an error which says,
python3.5/site-packages/pyexchange-0.6-py3.5.egg/pyexchange/base/soap.py", line 42, in _parse
raise FailedExchangeException(u"Unable to parse response from Exchange - check your login information. Error: %s" % err)
pyexchange.exceptions.FailedExchangeException: Unable to parse response from Exchange - check your login information. Error: Double hyphen within comment: <!--[if lt IE 9]>
<link rel="stylesheet" href="inc, line 16, column 87 (, line 16)
Can someone please help?
Please Note:
The exact same script works fine in my windows environment without any errors.
I am using the same pyexchange and lxml modules (versions) in both the environments.
Thanks,
Phani.
The text was updated successfully, but these errors were encountered: