455
Views
1
Comments
An exception occurred in the client script. Error: this[0] is undefined
Question
Hi,

After upgrading to the latest release (9.1.0.10), I began to see this error on the client. Anybody have an idea what this is?

TypeError: this[0] is undefined
Stack trace:
outsystems.internal.ProbeInit.prototype.bindToEvents/</<@https://dev.revued.com.au/PerformanceProbe/performanceprobe.js?9_1_0_10:164:228
@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:65:6578
@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25 line 18 > eval:2:1
window.outsystems.internal.jQueryFactory/</<.globalEval/<@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:18:13993
window.outsystems.internal.jQueryFactory/</<.globalEval@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:18:13967
OsEvaluateUserJavaScript@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:5:11838
OsExecuteJSONUpdate@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:5:13625
OsExecuteNextJSONUpdate@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:5:17593
OsExecuteJSONUpdate@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:5:14255
OsJSONUpdate@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:5:10663
@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25 line 65 > eval:2:1
OsAjaxBackendXHR/XHRState/this.ProcessNextScriptBlock@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:65:15950
OsAjaxBackendXHR/XHRState/this.ProcessPartialResponse@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:65:15276
OsAjaxBackendXHR/XHRState/this.ProcessFinalResponse@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:65:16010
OsAjaxBackendXHR/this.SubmitForm/e@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:65:13992
window.outsystems.internal.jQueryFactory/</$.Callbacks/l@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:18:16833
window.outsystems.internal.jQueryFactory/</$.Callbacks/m.fireWith@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:18:17618
d@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:26:3442
window.outsystems.internal.jQueryFactory/</</<.send/d@https://dev.revued.com.au/ERP_acc/_osjs.js?9_0_1_25:26:9007

Regards,
JC
2024-06-12 10-07-10
Daniel Martins

Hi JC Elorde,


We had similar issues with Performance Probe after platform upgrade.

Make sure that:

- IIS reset is performed on all front ends.

- Client browser cache is cleared.


In my case, the issues with Performance Probe were related with cache.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.