UPDATE: This issue has since been resolved.
We got a ticket today about a user getting a critical error when trying to enter Office 365 Exchange. I recall a similar issue happening to me a week prior, so I took a look. Sure enough, when entering exchange, I get this error:
Here is the full report:
Client Information
——————
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36
CPU Class: undefined
Platform: Win32
System Language: undefined
User Language: en-US
CookieEnabled: true
—————–
Exception Details
—————–
Date: Thu Feb 08 2018 09:31:21 GMT-0700 (Mountain Standard Time)
Message: Script error.
Url:
Line: 0
Call Stack
———-
Error
at Function.ErrorHandling.$Ee (https://r1.res.office365.com/ecp/15.20.464.16/scripts/common.js:1:189941)
at ErrorHandling.showUnhandledException (https://r1.res.office365.com/ecp/15.20.464.16/scripts/common.js:1:189026)
Dump Event
———-
isTrusted = true
message = Script error.
filename =
lineno = 0
colno = 0
error = null
NONE = 0
CAPTURING_PHASE = 1
AT_TARGET = 2
BUBBLING_PHASE = 3
type = error
target = [object Window]
currentTarget = [object Window]
eventPhase = 2
bubbles = false
cancelable = true
defaultPrevented = false
composed = false
timeStamp = 7115.5000000144355
srcElement = [object Window]
returnValue = true
cancelBubble = false
path = [object Window]
composedPath = function composedPath() { [native code] }
stopPropagation = function stopPropagation() { [native code] }
stopImmediatePropagation = function stopImmediatePropagation() { [native code] }
preventDefault = function preventDefault() { [native code] }
initEvent = function initEvent() { [native code] }
Detailed Call Stack
———–
This error message occurs across two of three admin accounts on three computers. Oddly, the third account does not suffer this error. It also occurs across at least three browsers – Edge, Internet Explorer 11, and Chrome (Ver 64, both normal and incognito).
As of now, I know of no fix, and several cursory google searches where fruitless. This only started to occur within the past month (as I go into exchange on a monthly basis) and sadly there are no recent posts anywhere about this. If anyone has a clue on how to fix this, or if we simply have to wait until Microsoft does something on their end, let me know. Otherwise we just have to deal with this very minor nuisance.