Since recently upgrading to Web Access 10.4.2.214 in our live production environment, we have lost the ability to preview Microsoft Office documents without opening the electronic file. In the web client, all we get is an error in the middle of the preview pane that states "One or more errors occurred."
I've tried uninstalling and reinstalling with no change.
When I switch the diagnostics logging level to debug, I do get some relevant entries in the Event Log:
One or more errors occurred.
Operation: /laserfiche/DocumentService.ashx/GetMetisToken
Message: Exception encountered, stack trace:
WebAccessServices.HttpHandlers.DocumentService.GetMetisToken
System.RuntimeMethodHandle.InvokeMethod
System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal
System.Delegate.DynamicInvokeImpl
WebAccessServices.HttpHandlers.BaseWAIHttpHandler.InvokeFunction
WebAccessServices.HttpHandlers.BaseWAIHttpHandler.ProcessRequestInternal
Exception details:
Message: One or more errors occurred.
Stack trace: at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at WebAccessServices.HttpHandlers.DocumentService.GetMetisToken(String repoName, Int32 documentId, String version)
Message: Could not load file or assembly 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Stack trace: at System.Net.Http.Formatting.BaseJsonMediaTypeFormatter..ctor()
at System.Net.Http.Formatting.JsonMediaTypeFormatter..ctor()
at WebAccessServices.HttpHandlers.DocumentService.<SendToMetis>d__93.MoveNext()
Message: Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Any idea what might be the problem here? I've checked file versions on the Newtonsoft.Json.dll assemblies and they all appear to be correct. We have a Development and UAT environment running the same versions of everything and we're not having this problem on those servers. I've even compared everything I can think of between the separate environments and everything appears to be the same.