none
OWA serialization Error after ex2016->2019 migration RRS feed

  • Question

  • Hi,

    last week I've installed a new Win/Exch 2019 server. After moving any user/system Mailbox to the new Exchange and adjusted the DNS entries, the following error occurs serval times a day. OWA and any other exchange services seems to running fine...

    Does anyone know this problem?

    Alex

    Log: Application
    Type: Error
    Source: System.Runtime.Serialization
    EventID: 65535
    MESSAGE    <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/de-DE/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>/LM/W3SVC/2/ROOT/owa-2-132115438191466061</AppDomain><Exception><ExceptionType>System.Runtime.Serialization.SerializationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>DateTime values that are greater than DateTime.MaxValue or smaller than DateTime.MinValue when converted to UTC cannot be serialized to JSON.</Message><StackTrace> at System.Runtime.Serialization.Json.JsonWriterDelegator.WriteDateTimeInDefaultFormat(DateTime value)
    at System.Runtime.Serialization.Json.JsonWriterDelegator.WriteDateTime(DateTime value)
    at WriteOwaLightningStateToJson(XmlWriterDelegator , Object , XmlObjectSerializerWriteContextComplexJson , ClassDataContract , XmlDictionaryString[] )
    at System.Runtime.Serialization.Json.JsonClassDataContract.WriteJsonValueCore(XmlWriterDelegator jsonWriter, Object obj, XmlObjectSerializerWriteContextComplexJson context, RuntimeTypeHandle declaredTypeHandle)
    at System.Runtime.Serialization.Json.XmlObjectSerializerWriteContextComplexJson.WriteDataContractValue(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
    at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithoutXsiType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle declaredTypeHandle)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph)
    at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.WriteObject(XmlDictionaryWriter writer, Object graph)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.WriteObject(Stream stream, Object graph)
    at Microsoft.Exchange.Data.Storage.LightningConfigurationHelper.SaveConfiguration[T](Stream stream, IUserConfiguration lightningConfiguration, DataContractJsonSerializer jsonSerializer, T state)
    at Microsoft.Exchange.Data.Storage.LightningConfigurationHelper.&lt;GetUnseenLightningItems&gt;d__0`2.MoveNext()
    at System.Linq.Enumerable.&lt;CastIterator&gt;d__97`1.MoveNext()
    at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
    at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
    at Microsoft.Exchange.Clients.Owa2.Server.Core.ServiceCommands.GetUnseenLightningIds.InternalExecute()
    at Microsoft.Exchange.Services.Wcf.ServiceCommand`1.DetectDuplicatedCallOrExecute()
    at Microsoft.Exchange.Services.Wcf.ServiceCommand`1.Execute()
    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
    at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
    at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaServiceMethodDispatcher.InvokeMethod(HttpRequest request, MethodInfo methodInfo, Object obj, Object[] parameters)
    at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaServiceMethodDispatcher.&lt;&gt;c__DisplayClass22_0.&lt;InternalInvokeMethod&gt;b__0()
    at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func`2 filterDelegate, Action`1 catchDelegate)
    at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaServiceMethodDispatcher.InternalInvokeMethod(ServiceMethodInfo methodInfo, Object service, HttpRequest httpRequest, HttpResponse httpResponse, Object[] arguments)
    at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaServiceMethodDispatcher.InvokeMethodWithPostDataInHeader(ServiceMethodInfo methodInfo, Object service, HttpRequest httpRequest, HttpResponse httpResponse)
    at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaServiceHttpHandler.InternalProcessRequest(HttpContext httpContext)
    at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaServiceHttpHandler.ProcessRequest(HttpContext httpContext)
    at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)
    at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
    at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
    at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
    at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&amp; notificationStatus)
    at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&amp; notificationStatus)
    at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    </StackTrace><ExceptionString>System.Runtime.Serialization.SerializationException: DateTime values that are greater than DateTime.MaxValue or smaller than DateTime.MinValue when converted to UTC cannot be serialized to JSON. ---&gt; System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
    Parameter name: value

    Monday, September 2, 2019 8:49 AM

All replies

  • Hi,

    Based on my searching, there doesn't exist a detailed introduce about "EventID: 65535". It is hardly to find root cause only from this event id.

    Does there exist any detail issue in your lab, such as cannot login OWA. If there doesn't exist issue on your Exchange, I think you can safely ignore this event.

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, September 3, 2019 2:46 AM
    Moderator
  • Does there exist any detail issue in your lab, such as cannot login OWA.

    Hi Kyle.

    everything seems fine. I like to keep my server logs clean... so hopefully one of the following tasks solve this issue:

    * simple server reboot :)

    * currently the old Exchange 2016 is still running for undo reasons. Maybe the event will be gone after downgrading the server

    I keep you informed...

    Alex

    Tuesday, September 3, 2019 11:31 AM
  • Hi Alex,

    Thank for your sharing, please be free to mark it as an answer which could be useful to other users narrow down similar problem.

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 6, 2019 9:12 AM
    Moderator
  • Hi Kyle,

    I've downgraded our Exchange 2016 system. So our environment now running on Exchange 2019 only.

    The error still occur :(

    After further research: the error will logged every time, after a user logged on in OWA.

    On a clean isolated Server 2019/ Exchange 2019 test environment, the same error will be thrown after logon in owa...

    On both environments the time zone is set to UTC+1 (Berlin). So it seems, there are a bug related to this time zone?!

    Regards,

    Alex

    Monday, September 16, 2019 9:49 AM
  • Hi Alex,

    Do you try to change time zone to other location? Does this event disappeared after the changing of time zone?

    If this event disappeared, could you tell use the CU of Exchange 2019 do you used, I will confirm it in my lab.

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 18, 2019 6:35 AM
    Moderator
  • Do you try to change time zone to other location? Does this event disappeared after the changing of time zone?

    Yes for sure. I've tried many different location and time zone settings in my test environment without affect.

    Exchange Version 15.2 (Build 397.3)


    Wednesday, September 18, 2019 8:03 AM