Web Services Issues

[TomProclaim]

Good Morning,

I'm having issues when trying to connect to a web service. When I try to test it within a linked action it throws an error message saying 'Failure in initializing Port (11754)'.

I've attached an image too.

IMG3.jpg (23.38 KiB) Viewed 13905 times

Any ideas?

[revellbikes]

Does it work outside of Proclaim using SoapUI or another similar application?

[TomProclaim]

Hi,

Yeah works absolutely fine in SoapUI.

As soon as it goes into Proclaim it falls over..shock!!

[revellbikes]

OK well that's a start at least!

I know for security reasons you can't divulge server names etc, but what is it exactly it can't find - WSDL, Certificate etc...?

Also have you made a copy of the WSDL file in the _docs folder for the case type you've set it up in? For some reason Proclaim doesn't like retrieving WSDL information from the outside world.

[TomProclaim]

Yeah agreed!

I'm not sure to be honest. It loads the WSDL file fine in Web Services Admin and I fill in the fields/XML I'm sending over however as soon as I click to call it via a linked action it throws that message.

I've just moved the WSDL file to inside the case type folder in the _docs but still the same message. :/

[revellbikes]

Without divulging server names etc, can you give any more detail on the 'thing' it can't find on the above error?

[TomProclaim]

Hi Revellbikes,

There are two services in the WSDL. One called BasicHTTPBinding_ISmartPropertyHubServices and one called BasicHTTPBinding_ISmartPropertyHubServices1. They look identical in what they contain however I think BasicHTTPBinding_ISmartPropertyHubServices1 which is the one Proclaim is complaining about has something to do with HTTP. When I test it in SoapUI I get the following back:

IMG1.PNG (8.16 KiB) Viewed 13874 times

Any help, greatly appreciated!

[TomProclaim]

Just to add to this I've tested it on the live web service which only contains the one service and it does exactly the same.

[steve]

Hi ,
it looks like it is trying to redirect you from the open http endpoint to the SSL (https) connection at the same address. Is your webservice endpoint http:// and not https:// ?
If possible can you point all references to https:// endpoint (including in WSDL if necessary), install the necessary certificates on your client machine and retest?

[TomProclaim]

Hi Steve,

Thanks for the reply.

I've made sure all of the necessary certificates are installed.

I've also just updated the WSDL file to https and put the same in the endpoint and it's still showing the same error message.

IMG1.jpg (39.26 KiB) Viewed 13866 times

I am stumped!