Troubleshooting the Nodinite Web Service Monitoring Agent

Quickly resolve issues and get expert answers for your Nodinite Web Service Monitoring Agent. This troubleshooting guide helps you identify, diagnose, and fix common problems with web service monitoring, configuration, and response handling.

✅ Diagnose and resolve web service response issues fast
✅ Get step-by-step solutions for configuration and protocol errors
✅ Access direct support and community resources

If you encounter issues you cannot solve, contact our Support or email support@nodinite.com for expert assistance.

Cannot get a response from the Web Service

You may experience this issue if the web service returns a malformed response, such as an incorrect handling of CRLF (Carriage Return + Line Feed) characters.

Example of a bad CRLF combination in a web service response.

Error: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF”.

• Verify the logic and ensure the Web Service returns the correct data.
• Test with the following accept header:

Accept: text/html, application/xhtml+xml, */*

• If the issue persists, update the Nodinite.MonitoringAgent.WebServicesHost.exe.config file as follows:

<system.net>
    <settings>
        <httpWebRequest useUnsafeHeaderParsing="true" />
    </settings>
</system.net>

Restart the Nodinite Web Service Monitoring Agent service to apply the changes.