PerformanceProbe - The operation was canceled

After our recent upgrade to Version 11, we are getting the following REST error from the Performance Probe, any assistance of suggestion will be appreciate to resolve this issue:

eSpaceVer: 0 (Id=2906, PubId=0, CompiledWith=11.0.212.3)
RequestUrl: https://xxx.xxx.xxx.xxx/PerformanceProbe/rest/BeaconInternal/WebScreenClientExecutedEvent (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/PerformanceProbe-73-131995433540583602
FilePath: C:\...\PS\running\PerformanceProbe.01429902314\
ClientIp: xxx.xxx.xxx.xxx
Locale: en-US
DateFormat: yyyy-MM-dd
PID: 3712 ('w3wp', Started='2019/04/11 08:52:03 PM', Priv=2243Mb, Virt=16396Mb)
TID: 100
Thread Name: 
.NET: 4.0.30319.42000

The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Net.Http.HttpContentExtensions.<ReadAsAsyncCore>d__0`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.ModelBinding.FormatterParameterBinding.<ExecuteBindingAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Controllers.HttpActionBinding.<ExecuteBindingAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()

Hi, 

What application this module is part of? 

You upgrade from version 10 to 11 or from 11.minor version to a 11. Newer version? 

Cheers 

We upgrade from 10 to 11. From what I figured out the Performance Probe sends information to Lifetime for Analytics. Attached is a screenshot of the error log.

Hello, 

I don't have experience with this error, but being an upgrade error on what seems to be a native feature of the application, I recommend you to open a support ticket, as this shouldn't be happening. 

I'll try to see if someone else has encountered this problem before. 

Cheers

@admin fastnet:  Did you open a ticket?  I'm having the same issue in 11, and Lifetime Analytics doesn't show any data for us.

Tony Abedini wrote:

Hi Tony,

We're experiencing the same issue. Have you found a solution yet?

Bump,

We're experiencing this too.

We are experiencing the same issue.

Has anyone found out why this is happening?

Sæunn Sif Heiðarsdóttir wrote:

Nothing that resolved the issue, Logged a ticket and the only explanation they found was the page timed out before a response could be send.