Skip to main content

Customer is receiving below error message. If they receive this error message, they are not able to log in to FSM. If they are already logged in, they cannot navigate because this message comes up. 

    Exception in UICommunicationManager.SendMessage: An HTTP Content-Type header is required for       SOAP messaging and none was found. client.State=Opened.

Then suddenly the message goes away and they don’t have the problem for several months. This is duplicated only in PRD.

How do we narrow this error down to resolve the issue?

Hi @Whitney,

SOAP messaging would suggest this is coming from one or more of the integrations. Have the integration logs been checked for errors around the time the message occurs? 

Specifically, it seems that the system is trying to send a message but no header has been populated on the SOAP message and so it cannot send.

Kind regards,

Lee Pinchbeck

Terms & ConditionsCookie settings