Skip to main content

On FSM 6.16, we are routinely running into outbound integration errors that result in the error “The underlying connection was closed: The connection was closed unexpectedly.”  The vast majority of the records are published successfully without issue, but a handful receive this error daily.  These errors occur on multiple outbound integrations from FSM. 

They occur daily and always around the same time just after business hours.  However, almost every single time, the data is actually received at the target system but since the error gets thrown, FSM will send the same data again, sometimes duplicating the data in our ERP.  

Any suggestions on what to look for either within FSM or the infrastructure would be appreciated.  

 

Hi @TNCBSNYDER ,

Were the integrations involved with code level customization? Just need to make sure that this error is coming from the baseline.


Hi Brian,

did you check the Server Log for more details on the Error? If there is not more than that you may want to set the Server Log Levels for Exception higher. Eventually your transaction is running into a timeout?

Best regards
Roman


Reply