Sometime around April 1, my Cisco Meraki Network Health (BETA) sensor stopped working and returns the following error:

"The sensor could not get a response from the server. 0 (). schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed). More detail may be available in the Windows System event log."

I am wondering if anyone else is seeing this. I tried generating a new API key and re-creating the sensor but the same error is produced. I am not sure if Meraki changed something and since this sensor is in BETA it is just broke for now :(

Article Comments

Hello,

Where there any changes to PRTG prior to the issue appearing?

Kind regards,
Sasa Ignjatovic, Tech Support Team


Apr, 2023 - Permalink

The Dashboard API version 1.32 was release right around when this sensor went into error (4/1/23). Release notes here: https://developer.cisco.com/meraki/whats-new/#!v1-32-0

The update looks minor but there was a change to organization-level device listing response - additional property added.

I can reach out to Meraki with a specific question if that will help?


Apr, 2023 - Permalink

Same error here, since PRTG upgrade to 23.2.83.1760 Ticket open, now waiting for solution by Paessler engineering.


Apr, 2023 - Permalink

Exact same issue here - have you had any response to your ticket? I've just upgraded to 23.2.83.1760 today, about to log a ticket also.


May, 2023 - Permalink

Cause found: PRTG is running on a Windows Server 2012 R2, wich can not handle newer TLS ciphers used by the Meraki sensor. But Server 2012 R2 is officialy still supported by Paessler PRTG. Solution: Migration to a newer Windows Server. Other Solution? Waiting for feedback from engineering.


May, 2023 - Permalink

The same issue here. have you any response ? Thanks


Jul, 2023 - Permalink

We have developed a fix for this issue, it is planned to release it in the PRTG version 23.x.86 which is scheduled for end of July. A preview of this version will be available this week, so you can update to it, if you need the fix sooner.

Kind regards,
Sasa Ignjatovic, Tech Support Team


Jul, 2023 - Permalink