Monitoring Error - TypeError: e is not iterable

dcota

Hi all,

We had a server throw a monitoring error early this morning and it continues to show red and is not monitoring, although the server is up and running and I can't find any issues with it. Does anyone have any insight into what might be happening here?

The error in SQL Monitor I'm seeing is below.

Thanks in advance for any assistance!

This most likely indicates a bug in SQL Monitor.

TypeError: e is not iterable

TypeError: e is not iterable
    at D (http://fa-sqldbb:8080/Scripts/ManageMonitoredEntities.js?v=12.0.16.22039:87:59025)
    at D.next (<anonymous>)
    at Function.from (<anonymous>)
    at http://fa-sqldbb:8080/Scripts/ManageMonitoredEntities.js?v=12.0.16.22039:87:59933
    at Object.Mi [as useMemo] (http://fa-sqldbb:8080/Scripts/ManageMonitoredEntities.js?v=12.0.16.22039:59:63746)
    at t.useMemo (http://fa-sqldbb:8080/Scripts/ManageMonitoredEntities.js?v=12.0.16.22039:79:5745)
    at P (http://fa-sqldbb:8080/Scripts/ManageMonitoredEntities.js?v=12.0.16.22039:87:59921)
    at li (http://fa-sqldbb:8080/Scripts/ManageMonitoredEntities.js?v=12.0.16.22039:59:59042)
    at Vi (http://fa-sqldbb:8080/Scripts/ManageMonitoredEntities.js?v=12.0.16.22039:59:68560)
    at Ql (http://fa-sqldbb:8080/Scripts/ManageMonitoredEntities.js?v=12.0.16.22039:59:112097)

Kurt_M

Hi @dcota,

From the error, I can see you're running on 12.0.16. Would it be possible for you to upgrade to the latest to confirm if this fixes it?

I haven't seen this particular error myself, but I have been able to find references to the TypeError message in other customers support tickets. But, none of them reference the same error as what you've reported. Those customers appeared to have an issue with their browser and with JavaScript. As it could be related, may I ask what browser you're running SQL Monitor in?

dcota

I am accessing SQL Monitor via Chrome. We can look at updating Redgate to the latest version today to see if that fixes the issue.

We did find the "culprit" though...I think. Apparently the latest Windows Update is what causes the issue, at least for us. Uninstalling the below Update brought SQL Monitor back into a monitoring state for this server.

2022-06 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5014702)

Kurt_M

Hi @dcota,

Thanks for advising about the windows update. Let me know if the error returns after you update SQL Monitor.