One of the HTTP\S scouts in Scoutbees is failing with an error related to SSL/TLS alerts. The Application Events section shows that the organization is currently inactive and suggests a possible error with cipher suite hardening. However, the monitor server can access the site fine through Edge and other internal HTTP\S scouts are working properly. No further information could be found in the Windows System event log.
Read the entire ‘Troubleshooting Scoutbees Issues with SSL/TLS Alerts’ thread below:
More Scoutbees issues. 1 of many HTTP\S scouts failing:
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.
Nothing in system events
Found this in Application Events:
Organization is not active (no broker heart beats for a while)
Process ID: 3056
Correlation ID: ce6d7999-624d-4eb3-ac92-86f052926770
Client computer name: 1001-######.local
Error Description:
- Error type – c5c6f82e1d76bf3f59e3068bc0dd22dda : Exception of type ‘A.c5c6f82e1d76bf3f59e3068bc0dd22dda’ was thrown.
Cipher suite hardening?
Not sure. I can get to the site fine in Edge from teh monitor server and all other internal http\s scouts to internal sites work.
Continue reading and comment on the thread ‘Troubleshooting Scoutbees Issues with SSL/TLS Alerts’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers, ControlUp Synthetic Monitoring