On the Gateway Webpage the Status/System/Gateway Scripts Status page is not loading. After clicking to view the page, the Tab Bar will flash on screen for a split second and then the screen will be blank. There is a similar item number that was solved a while ago and might be good reference [BUG-12800].
Browser: Google Chrome
Ignition Version Number: 8.0.2- b20190516
OS: Windows 10 Pro and Windows Server 2016 Datacenter
OS of Gateway Location: Windows Server 2016 Datacenter
Can you check the browser console and gateway logs to see if any errors are thrown when the page fails to load?
I can’t reproduce out of a development environment.
Okay, that should be enough for us to track it down. Thanks for the report.
Awesome! Thanks
I’m having the same issue on two separate gateways with version 8.0.1.
Is there any workaround to view these pages some other way?
I’m getting the same issue on my gateway script status page running version 8.0.5 and the browser is Chrome.
Is this a known issue? Is there a fix?
Same issue, several browsers (chrome, edge on different computers), several different versions of Ignition 8 (8.06 still has the problem)
We have this problem too,and have for a long time - all browsers (ie, edge, chrome) has it and it has persisted since at least 8.01 through 8.06
Here’s a dump from chrome - I do not know if it is useful
sys.gateway-scripts?4:1 [DOM] Found 2 elements with non-unique id #timer-panel_pagination_page_input: (More info: https://goo.gl/9p2vKq) <input type=​"text" pattern=​"[1-9]​[0-9]​*" id=​"timer-panel_pagination_page_input" value=​"1">​ <input type=​"text" pattern=​"[1-9]​[0-9]​*" id=​"timer-panel_pagination_page_input" value=​"1">​
DevTools failed to parse SourceMap: http://i8server:8088/web/status/twotiermenu.js.map
DevTools failed to parse SourceMap: http://i8server:8088/web/status/gateway_scripts.js.map
DevTools failed to parse SourceMap: http://i8server:8088/web/status/GatewayBreadcrumb.js.map
DevTools failed to parse SourceMap: http://i8server:8088/web/status/trialbar.js.map
react-dom.js:117 Invariant Violation: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at pb (http://i8server:8088/res/sys/js/react-dom.js:12:454)
at n (http://i8server:8088/res/sys/js/react-dom.js:13:221)
at wc (http://i8server:8088/res/sys/js/react-dom.js:61:140)
at http://i8server:8088/res/sys/js/react-dom.js:79:83
at N (http://i8server:8088/res/sys/js/react-dom.js:90:3)
at hi (http://i8server:8088/res/sys/js/react-dom.js:105:408)
at Qg (http://i8server:8088/res/sys/js/react-dom.js:144:217)
at Rg (http://i8server:8088/res/sys/js/react-dom.js:145:76)
at Sc (http://i8server:8088/res/sys/js/react-dom.js:158:109)
at Z (http://i8server:8088/res/sys/js/react-dom.js:156:492)
Bg @ react-dom.js:117
c.callback @ react-dom.js:126
Ag @ react-dom.js:116
zg @ react-dom.js:116
qi @ react-dom.js:131
ui @ react-dom.js:133
(anonymous) @ react-dom.js:158
unstable_runWithPriority @ react.js:27
Vc @ react-dom.js:158
Sc @ react-dom.js:158
Z @ react-dom.js:156
Kc @ react-dom.js:155
ya @ react-dom.js:153
enqueueSetState @ react-dom.js:202
t.setState @ react.js:20
u.onStateChange @ VM2549:14
m @ VM2549:14
eval @ VM2549:1
dispatch @ VM2549:14
eval @ VM2549:14
Promise.then (async)
eval @ VM2549:14
eval @ VM2549:1
value @ IgnitionLib-ver-529E74C3F1794104A22D05E8BE29EF08.js:1
setTimeout (async)
value @ IgnitionLib-ver-529E74C3F1794104A22D05E8BE29EF08.js:1
eval @ VM2549:14
Promise.then (async)
eval @ VM2549:14
eval @ VM2549:1
value @ IgnitionLib-ver-529E74C3F1794104A22D05E8BE29EF08.js:1
(anonymous) @ IgnitionLib-ver-529E74C3F1794104A22D05E8BE29EF08.js:1
F @ IgnitionLib-ver-529E74C3F1794104A22D05E8BE29EF08.js:1
value @ VM2549:14
value @ VM2549:14
Pd @ react-dom.js:69
qg @ react-dom.js:92
hi @ react-dom.js:104
Qg @ react-dom.js:144
Rg @ react-dom.js:145
Sc @ react-dom.js:158
Z @ react-dom.js:156
Kc @ react-dom.js:155
ya @ react-dom.js:153
bh @ react-dom.js:160
xe @ react-dom.js:160
nb.render @ react-dom.js:215
(anonymous) @ react-dom.js:164
$g @ react-dom.js:159
Wc @ react-dom.js:164
render @ react-dom.js:217
cb @ sys.gateway-scripts?4:76
(anonymous) @ IgnitionLib-ver-529E74C3F1794104A22D05E8BE29EF08.js:1
fire @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:2538
fireWith @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:2649
done @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:7038
(anonymous) @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:7327
load (async)
send @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:7344
ajax @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:6957
jQuery.<computed> @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:7077
getScript @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:7065
value @ IgnitionLib-ver-529E74C3F1794104A22D05E8BE29EF08.js:1
(anonymous) @ sys.gateway-scripts?4:76
dispatch @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:3782
elemData.handle @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:3632
load (async)
add @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:3671
(anonymous) @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:3598
each @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:269
each @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:90
on @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:3597
on @ jquery-ver-C2E3D53624F901F3F15AE4D03B098EEF.js:4064
(anonymous) @ foundation.min.js:1
(anonymous) @ foundation.min.js:1
VM2549:14 Error fetching script diagnostics: Invariant Violation: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Hey @PGriffith
This is still a problem in version 8.0.12 (b2020042115)
Is there any fix for this planned?
Thanks.
Same error:
We were never able to reproduce internally, but I believe some changes were made to how these pages load React components for 8.0.14/8.0.15. I’ll re-open the internal ticket, but it may end up being resolved by those other changes.
I’ve personally noticed this has been much better since about 8.0.10, for me at least. Not sure if it has to do with a script I’ve changed, or if it was gateway updates.
I noticed it seemed to be happening for me when I was running long scripts in a shared thread.
That would make sense. I have a few of them!
Noticed that happening since 8.0.10. Did not look for it before.
So Gateway Scripts->Timer Script with Fixed Rate and Dedicated Thread
If the script did not finish in desired Delay Gateway Scripts Status Page not loading, disappearing.
In 7.9 If the script did not finish there is an exclamation mark with Slow
In order to make Gateway Scripts Status Page be visible again Delay value must be bigger than script duration.
also seeing this on EDGE 8.0.15,
disabling this script allows the page to load:
I also see a similar (if not same) issue on 8.1.1
Confirmed that increasing the delay appears to be the temporary solution.
Found a thread that looks like it may have a resolution for the issue, but haven't seen any feedback on whether this is fixed in 8.1.2 or not.
Seeing the same error here. Mine is on fixed delay but tried it at 10K and 20K ms and still had same issue. Weird thing tho, when I changed it to 20K ms and saved it the page was able to load and showing it never run. But once it did run the page started showing the error again…
I am seeing this issue as well, did anyone ever find a solution for this?
This should be fixed as part of 8.1.3 and was here in the change logs.
