-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The request failed schema validation #1310
Comments
I believe this was fixed in exchangelib 5.4.0. See #1301 Try upgrading and report back your findings here. |
Thanks @ecederstrand.
|
That's just your server resetting the connection. Exchange servers will do that once in a while. If you want exchangelib to handle that gracefully, then add a retry policy: https://ecederstrand.github.io/exchangelib/#fault-tolerance |
ok I see, but why it would reset the connection with version 5.4.0 but when I change it back to using the previous version this error doesn't raise? Is that ok? |
Connection errors come and go. It's not necessarily correlated with you installing different versions of exchangelib. Unless this is a persistent error and you cannot get any data at all from the server using 5.4.0 then I don't think there's anything to worry about. |
ok thanks, I'll keep monitoring for the night and let you know. |
Hey @ecederstrand, |
How does the error manifest? Did you add a retry policy? Do you have a stack trace? And does the stack trace happen before the retry policy is set to time out? The best way to find out what a working and a non-working version of exchangelib do differently is to enable debug logging and comparing the XML requests and responses leading up to the exception. |
we looked into this doesnt seem related to the library code |
Describe the bug
I'm currently trying to locate an email with the MessageID (NTLM, version: 2013). Interestingly, when I utilized exchangelib 5.0.3, I encountered no errors and received the intended message. However, upon upgrading to exchangelib version 5.3.0, I encountered an error when attempting to retrieve emails with version 2013 (although it worked fine with 2013 SP1).
I saw that a fix was out in v1.1.1 according to #320, but I'm not sure how and if it is related since this fixed was merged in v1.1.1.
Expected behavior
getting the message with 2013 server version.
Additional context
python 3.10
The text was updated successfully, but these errors were encountered: