Skip to main content
Question

FSM TO PSO Integration issue

  • August 6, 2023
  • 2 replies
  • 106 views
D
Sidekick (Partner)
Forum|alt.badge.img+7

Hi All,

 

I am getting below error while initializing data from FSM to PSO. Could please help me to fix the issue.

Configured  all parameters  in FSM  which are required to load data from FSM to PSO.

 

An error occurred while making the HTTP request to https://XXXXXXXX:8744/IFS/Scheduling/Gateway/Service/Session. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server

Thanks,

Durga

2 replies

P
Do Gooder (Employee)
Forum|alt.badge.img+1
  • Prabu
  • Do Gooder (Employee)
  • August 7, 2023

Hi Durga,

Can you please post this issue in below team channel, someone in this group will assist you.

 

https://teams.microsoft.com/l/channel/19%3af42772013625402bad3cbb8377add9c7%40thread.skype/FNDSCH?groupId=11318fb3-0582-4b08-aee1-adf3d3ad933e&tenantId=afadec18-0533-4cba-8578-5316252ff93f

L
Do Gooder (Customer)
Forum|alt.badge.img+4
  • LeeT
  • Do Gooder (Customer)
  • February 3, 2026

​@Prabu I don’t have access to this microsoft account. I also would like to know the solution as we converted our pre-prd environment in the Spring from http to https, then more recently had a new cert applied to the PSO server. 

We are getting the same error on the Service Manager screen in FSM:

An error occurred while making the HTTP request to https://<server_name>.<environment.<domain>.com:8744/IFS/Scheduling/Gateway/Service/Session. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server.

Prior to the error above we were seeing:

There was no endpoint listening at https://<server_name>.<environment.<domain>.com:8744/IFS/Scheduling/Gateway/Service/Session that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Terms & ConditionsCookie settingsAccessibility statement