Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Error: The underlying connection was closed: The server committed a protocol violation

Error: The underlying connection was closed: The server committed a protocol violation

Created by Tiarnan Stacke, last modified by Shane Horgan on Sep 26, 2016

Views: 2,252 Votes: 0 Revisions: 5

Overview

This article describes the issue when the FTP User Experience Monitor Produces the following error:

 The underlying connection was closed: The server committed a protocol violation.

Environment

All Versions of SAM

 

Cause 

One cause of this error occurs when trying to use the FTP User Experience Monitor to check SFTP or FTPS.

Resolution

SAM currently doesn't support SFTP or FTPS with the FTP User Experience Monitor.

To get this functionality we recommend looking into custom scripts to achieve this.

 

If you are using the FTP User Experience Monitor for FTP only and still receiving the above Error.

Please edit the Application Monitor and change the FTP monitor to Passive Mode as this has resolved some "False protocol Errors" in recent cases.  

 

Active mode - Client open one channel to server and then server opens data chanell back from server to client.
Passive mode - Both channels are opened from client side

 

 

Please note that Solarwinds Technical Support cannot assist with the customization of scripts. For assistance in this regard we recommend asking in the Thwack Script Lab forum.

 

 

 

Last modified

Tags

Classifications

Public