DataTables warning: table id=Logs - Invalid JSON response

Thanks for letting us know Matthew. Are you in an environment where you can capture the response that is actually coming back? Either using the browser developer tools or something like wireshark?

Unfortunately with this particular UI component, it doesn't give us too much information that assists with diagnosing issues.

Thanks.

Invalid JSON.pcapng

Perfect, thanks for supplying that:

<s:envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
    <s:body>
        <s:fault>
            <faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode>
            <faultstring xml:lang="en-AU">Collection was modified; enumeration operation may not execute.</faultstring>
            <detail>
                <exceptiondetail xmlns="http://schemas.datacontract.org/2004/07/System.ServiceModel" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
                    <helplink i:nil="true"></helplink>
                    <innerexception i:nil="true"></innerexception>
                    <message>Collection was modified; enumeration operation may not execute.</message>
                    <stacktrace>   at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
   at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
   at System.Linq.Enumerable.WhereListIterator`1.MoveNext()
   at System.Linq.Enumerable.<SkipIterator>d__30`1.MoveNext()
   at System.Linq.Enumerable.<TakeIterator>d__24`1.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Unify.Framework.Logging.LoggingEngineNotifierDecorator.<>c__DisplayClass6_0.<ReadLogSearch>b__0()
   at Unify.Framework.Notification.NotifierDecoratorBase.Notify[TResult](ITaskNotificationFactory notificationFactory, Func`1 function)
   at Unify.Framework.Logging.LoggingEngineNotifierDecorator.ReadLogSearch(DateTime date, String search, Int32 skip, Int32 take)
   at Unify.Framework.Logging.LoggingEngineAccessor.ReadLogSearch(DateTime date, String search, Int32 skip, Int32 take)
   at Unify.Product.IdentityBroker.IdentityServiceCollector.ReadLogSearchSkipTake(DateTime date, String search, Int32 skip, Int32 take)
   at SyncInvokeReadLogSearchSkipTake(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</stacktrace>
                    <type>System.InvalidOperationException</type>
                </exceptiondetail>
            </detail>
        </s:fault>
    </s:body>
</s:envelope>

A quick test suggests this may have fixed the issue. 

Oops maybe I spoke too soon. Still producing errors.

Would it be too much to ask if you could capture it again to see if the error is actually the same? I wasn't able to reproduce the same behaviour. Thanks.