Calendar is no longer accessible SM17/100 Build 6928 (Permission Error and Array Dimensions Exceeded error)
Problem reported by Ionel Aurelian Rau - January 3 at 6:11 AM
Resolved
Hello!

Starting today (apparently), users can no longer access the Calendar section of the WebMail. When trying to do so, these 2 errors appear one after the other (after a long loading period):
And then:

The browser console logs this information:
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
angular-v-100.0.6928.30712.8d6668c62e2f700.js:114 [Violation] 'load' handler took 197ms
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [14:59:27 GMT+0200 (Eastern European Standard Time)] SignalR: Invoking mailhub.Ping
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [14:59:27 GMT+0200 (Eastern European Standard Time)] SignalR: Invoked mailhub.Ping
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:00:02 GMT+0200 (Eastern European Standard Time)] SignalR: Invoking mailhub.Ping
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:00:02 GMT+0200 (Eastern European Standard Time)] SignalR: Invoked mailhub.Ping
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:00:15 GMT+0200 (Eastern European Standard Time)] SignalR: Triggering client hub event 'mailModified' on hub 'MailHub'.
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:00:15 GMT+0200 (Eastern European Standard Time)] SignalR: Triggering client hub event 'mailRemoved' on hub 'MailHub'.
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:00:18 GMT+0200 (Eastern European Standard Time)] SignalR: Triggering client hub event 'mailboxSizeUpdate' on hub 'MailHub'.
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:00:18 GMT+0200 (Eastern European Standard Time)] SignalR: Triggering client hub event 'mailAdded' on hub 'MailHub'.
site-v-100.0.6928.30712.8d6668c62e2f700.js:100 Got mailAdded event
site-v-100.0.6928.30712.8d6668c62e2f700.js:100 (2) [{…}, {…}]
angular-v-100.0.6928.30712.8d6668c62e2f700.js:115 POST https://mail.redacted.com/api/v1/folders/folder 400 (Bad Request)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:115
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
e @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:54
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
setTimeout (async)
h.defer @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
$evalAsync @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:140
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
then @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:145
c @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:105
n @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
n.(anonymous function) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:111
resyncFolderUnreadCount @ site-v-100.0.6928.30712.8d6668c62e2f700.js:87
g @ site-v-100.0.6928.30712.8d6668c62e2f700.js:87
h @ site-v-100.0.6928.30712.8d6668c62e2f700.js:5
$broadcast @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:159
n.mailAdded @ site-v-100.0.6928.30712.8d6668c62e2f700.js:100
(anonymous) @ VM7578:25
f.(anonymous function).(anonymous function) @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248
dispatch @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
q.handle @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
trigger @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:4
triggerHandler @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:4
(anonymous) @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248
(anonymous) @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248
dispatch @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
q.handle @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
trigger @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:4
triggerHandler @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:4
triggerReceived @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248
(anonymous) @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248
each @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:2
processMessages @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248
e.socket.e.socket.onmessage @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248
angular-v-100.0.6928.30712.8d6668c62e2f700.js:115 GET https://mail.redacted.com/api/v1/calendars/events/iarau/f0983f72ec9f48dca3bdefe2418f87f4?endDate=2019-02-04T12:57:07.119Z&startDate=2018-12-04T12:57:07.119Z 400 (Bad Request)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:115
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:170
e @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:54
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
setTimeout (async)
h.defer @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
f @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:170
(anonymous) @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:12
dispatch @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
q.handle @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:00:37 GMT+0200 (Eastern European Standard Time)] SignalR: Invoking mailhub.Ping
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:00:37 GMT+0200 (Eastern European Standard Time)] SignalR: Invoked mailhub.Ping
angular-v-100.0.6928.30712.8d6668c62e2f700.js:115 GET https://mail.redacted.com/api/v1/calendars/events/iarau/d6a08e0c690941d08a144acb53900049?endDate=2019-02-03T12:57:07.119Z&startDate=2018-12-04T12:57:07.119Z 400 (Bad Request)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:115
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:170
e @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:54
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
setTimeout (async)
h.defer @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
f @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:170
(anonymous) @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:12
dispatch @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
q.handle @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:01:12 GMT+0200 (Eastern European Standard Time)] SignalR: Invoking mailhub.Ping
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:01:12 GMT+0200 (Eastern European Standard Time)] SignalR: Invoked mailhub.Ping
angular-v-100.0.6928.30712.8d6668c62e2f700.js:115 GET https://mail.redacted.com/api/v1/calendars/rooms/3eba306a415743f7a5300491debc3860?endDate=2019-02-07T12:57:07.119Z&startDate=2018-12-04T12:57:07.119Z 400 (Bad Request)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:115
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:170
e @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:54
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
setTimeout (async)
h.defer @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
f @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:170
(anonymous) @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:12
dispatch @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
q.handle @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
angular-v-100.0.6928.30712.8d6668c62e2f700.js:130 Possibly unhandled rejection: {"data":{"message":"Array dimensions exceeded supported range."},"status":400,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","params":{"startDate":"2018-12-04T12:57:07.119Z","endDate":"2019-02-07T12:57:07.119Z"},"url":"/api/v1/calendars/rooms/3eba306a415743f7a5300491debc3860","headers":{"Accept":"application/json, text/plain, */*","Authorization":"Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJuYW1laWQiOiJpYXJhdUBxdWFudGljbGFiLmNvbSIsIm5hbWUiOiJJb25lbCBBdXJlbGlhbiBSYXUiLCJ1c2VybmFtZSI6ImlhcmF1IiwiYWRtaW4iOiJGYWxzZSIsInJvb3RlbWFpbCI6ImlhcmF1QHF1YW50aWNsYWIuY29tIiwicm9sZSI6WyJEb21haW5BZG1pbiIsInVzZXIiXSwiSW1wZXJzb25hdGluZyI6IkZhbHNlIiwiaXNzIjoic21hcnRlcm1haWwiLCJhdWQiOiIqIiwiZXhwIjoxNTQ2NTIxMjQyLCJuYmYiOjE1NDY1MjAzNDJ9.PZTSm0ew7_-ijKxLgK14R0gsfl4CYPI6Kpfcw6V6Hi6mUEdUAFPmu6MFoN5c_jQmGK7U-VKwN5nYG8_S-Yu7TDFSXCDep2oEtPPgR15MK23_GJmziU6b9_TH3Ky7OVjhRcXUly3XNptMwUPBLYtsgDQwNAXmc9MqOC85PZloE2y3Rjzhlb6bW2YYnWFWVV75Rr6wuziF6fUE1Jy5M-PGDWjemW2n1p9zZnKq2AtJMdqzogEuNiuckBUjTOfQDgJDXfEOXcnLXemgR0TXCscVGwq26Y5VljV7D7A6U3XMwiGN7HwScc-kdiNA1qwdd-AI-VMkksFRHRgBnGEhAKJIcQ"}},"statusText":"Bad Request","xhrStatus":"complete"}
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:130
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:101
g @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
k @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:108
s @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:113
w.onload @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
load (async)
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:114
B @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:110
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:107
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:142
$digest @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:153
$apply @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:157
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:170
e @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:54
(anonymous) @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
setTimeout (async)
h.defer @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:56
f @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:170
(anonymous) @ vendor-v-100.0.6928.30712.8d6668c62e2f700.js:12
dispatch @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
q.handle @ angular-v-100.0.6928.30712.8d6668c62e2f700.js:3
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:01:47 GMT+0200 (Eastern European Standard Time)] SignalR: Invoking mailhub.Ping
vendor-v-100.0.6928.30712.8d6668c62e2f700.js:19248 [15:01:47 GMT+0200 (Eastern European Standard Time)] SignalR: Invoked mailhub.Ping

Any known calendar issues in the current build? Is there anything we can do to get back the calendar function of WebMail?

6 Replies

Reply to Thread
0
Robert Emmett Replied
Employee Post
Ionel, is this happening to all users?  Or only a few?  Is the calendar to which they are connecting a shared calendar or their personal calendar?
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Ionel Aurelian Rau Replied
I`ll open a ticket as suggested to the high RAM usage issue. Note that I also opened this issue: https://portal.smartertools.com/community/a91510/syncing-outlook-2016-2019-office365-via-eas-no-longer-working-some-users-with-sync.aspx

As far as I know, after updating from v16 to v17 build 6922, everything went well and the calendar interface was accessible. However, we had some shared resources (2 calendars and 3 conference rooms) and all of these were disconnected from each account`s mailboxes. We instructed users that need them to reconnect them and at least a whole department did that and used the shared calendars and booked the rooms up until sometime last week (since few people worked during the holidays, I`m not sure how many actually used the calendar in WebMail last week or the week before).
What I know for sure is that most users that needed the calendars already had them re-attached and none of them can open the Calendar interface in WebMail. However, there was one employee today that called and asked me how to reattach the conference rooms as she did not do that last year and I walked her through it on the phone, so I guess she was able to access the Calendar. In the end she reported that she could not create the calendar event as the interface would load forever.
0
Ionel Aurelian Rau Replied
We are still investigating the issue with SM support, but it appears that one of our shared resources was at fault for the Calendar section not being accessible. We had several conference rooms and shared calendars from SM 16 or even 15 (I think at least one of the conference room was created in SM 15) which were mapped to many of our users. Apparently calendar still worked fine in the initial build of SM 17 we originally updated to, but then after a subsequent update, the calendar section would choke on one of these shared resources.

We removed all of the permissions from these resources which detached them from all users - after that, RAM usage dropped to more normal levels and even Outlook started syncing again via EAS. We created other shared resources to replace the old ones and so far there were no issues with the new ones.. but time will tell.

For users that previously had the bad shared resources attached, while now the Calendar section loads and can be used, we still get the 2 Permission Error and Array Dimensions Exceeded red notifications when browsing through this section, so this still needs to be looked into.
0
Ionel Aurelian Rau Replied
We`re now on the latest public release (Build 6948) and the same behavior occurs with Shared Resources. Without these, everything works just fine.
0
echoDreamz Replied
Ditto here, latest 6948 and still have clients reporting shared folder issues. New ones seem to be OK, but existing shares are broken.

Christopher

0
Ionel Aurelian Rau Replied
Marked As Resolution
Hi all,

In the end it turns out that we had a shared calendar insider our calendar file which had a custom category that duplicated over and over again so that the file reached a size of ~ 800MB. If we removed all shared resources from all users, calendars would work, but with low performance and high system resource usage. But if we mapped any shared calendars, whether the problematic one, or even new ones, then RAM and CPU usage would shoot up to impossible levels (e.g. over 60GB of RAM used when we would normally see 6GB used).

Also, after we mapped any shared resources, Outlook would stop syncing mail via EAS for the users that did so.

Now the calendar file has been fixed and we are on the latest build - resource usage is back to normal levels and user experience is great. 

So this issue appears to be fixed, at least after almost a day where users were again able to use shared resources.

Reply to Thread