It is a secret token that exchanges between the clients and the server for services OWA,ECP and other exchange web services.
It creates 4 attributes while schema preparation or it may be even just one attriubute
Stack trace: at .Canary15.Init(Byte userContextIdBinary, Byte timeStampBinary, String logonUniqueKey, Byte hashBinary, String logData)īy looking into the event viewer we can see this is related to Active Directory Cache error related with CAS server for a value called Canary Dataīasically Canary Data is an attribute that is created during the first exchange 2013 schema preparation. Request URL: Request path: /owa/logoff.owa While looking into the event logs you can find the below log with the descriptionĮvent message: An unhandled exception has occurred.Įvent ID: f959d55d927a45f8b3b69051bbd62038Īpplication domain: /LM/W3SVC/2/ROOT/owa-1-130223042171473642Īpplication Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\Įxception message: Object reference not set to an instance of an object.Īt .Canary15.Init(Byte userContextIdBinary, Byte timeStampBinary, String logonUniqueKey, Byte hashBinary, String logData)Īt .Canary15.ctor(String logonUniqueKey)Īt .Canary15Cookie.Tr圜reateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile)Īt .Canary15Cookie.Tr圜reateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile)Īt 2.(Object sender)Īt 2.(Object sender, EventArgs e)Īt .Execute()Īt (IExecutionStep step, Boolean& completedSynchronously) X-OWA-Error: System.NullReferenceExceptionġ) Rebuilding OWA/ECP virtual directories will not helpĢ) Playing with owa authentication settings will not helpģ) Re-installing exchange server also will not help at times User can use outlook to send/receive emails normally, but when the user try to login OWA, a “something went wrong” screen with the following information appears:Īn unexpected error occurred and your request couldn’t be handled. After applying updates on Exchange 2013 environment we might come across the below symptom from end users while accessing OWA
0 kommentar(er)
