Closed vepishkin closed 1 month ago
It’s an internal Exchange error message with no additional information on why the duration is invalid. I would suggest either:
I'll close the issue until we have some indication that we can help users with a better error message, or detect this situation up-front in exchangelib. As it stands, I don't think we can do any better than display the error message from the server.
@ecederstrand Sorry for a long answer, i was away. The MS website indicates in the example a format like this:
<Duration>
<StartTime>2005-10-05T00:00:00</StartTime>
<EndTime>2005-10-25T00:00:00</EndTime>
</Duration>
YYYY-MM-DD HH:MM:SS (time zone is not transmitted)
but the script sends it in a different format, maybe that's the problem?
<t:Duration>
<t:StartTime>2025-07-22T01:00:00+03:00</t:StartTime>
<t:EndTime>2025-08-05T23:59:00+03:00</t:EndTime>
</t:Duration>
YYYY-MM-DD HH:MM:SS+UTC
Setting the duration works and is part of the test suite, so it's not a general problem with the datetime format.
Hello!
Had the same problem. Discussions in this thread didn't help. I would be grateful if someone could help with the problem.
My env: Exchange 2019 Version 15.2 (Build 1258.12) exchangelib/5.4.2 python-requests/2.32.3
py code:
DEBUG LOG: