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
{{ message }}
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.
This request is preceded by the following log entries (line numbers might be different):
1st-setup:2017-8-3 22:22:15.772:[Team] getOnlyFreeBusyInformation: aRangeStart:1970/01/01 00:00:00 UTC isDate=0 nativeTime=0, aRangeEnd:2017/09/21 00:00:00 Europe/Berlin isDate=1 nativeTime=1505944800000000 (_getOnlyFreeBusyInformation in mivExchangeCalendar.js:8558)
1st-setup:2017-8-3 22:22:15.773:[Team] getOnlyFreeBusyInformation: aRangeStart is 1970. To big a range. Setting startrange to 40 days before endrange. (_getOnlyFreeBusyInformation in mivExchangeCalendar.js:8566)
The server response is as follows:
<?xml version="1.0" encoding="utf-8"?>
<s:Envelopexmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<s:Fault>
<faultcodexmlns:a="http://schemas.microsoft.com/exchange/services/2006/types">a:ErrorInvalidMergedFreeBusyInterval</faultcode>
<faultstringxml:lang="en-US">The specified merged free/busy interval is not valid. Specify an interval that is less than the free/busy time window and between 5 and 1440 minutes.</faultstring>
<detail>
<m:ErrorCodexmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages">5004</m:ErrorCode>
</detail>
</s:Fault>
</s:Body>
</s:Envelope>
Expected behavior:
Valid range is sent to server and calendar entries are shown.
The text was updated successfully, but these errors were encountered:
Update: I investigated a bit more and it appears that this is problem is not necessarily causing the calendar to not show any information. Nevertheless, this server response should never be triggered by a bad request.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Actual:
ec-4.0
branch.Expected behavior:
The text was updated successfully, but these errors were encountered: