Release Automation KB: "SOAP Request New" Action Fails with Error Code 500

Document created by JamesPanetti Employee on Sep 12, 2014Last modified by JamesPanetti Employee on Oct 16, 2014
Version 2Show Document
  • View in full screen mode

Problem

 

Applies to all supported versions.

 

When performing a test run in Automation Studio for the action "SOAP Request New", the following error occurs:

 

Could not access endpoint

http://<ip address>/.../<service name>.asmx?wsdl, HTTP

error code 500

 

Cause

 

Whereas some web services only mandate use of a SOAP header, other types of web services require the SOAPAction when all of the service's actions are part of a single web service.  In the latter case, failing to add the action will cause the above error. Note that by default, SOAP UI attaches the SOAPAction based upon the WSDL.

 

Resolution

 

(1) Compare the XML within SOAP UI to to action in RA to see what is missing.

(2) If there is a SOAPAction foundin SOAP UI that is missing from the RA action, add it to the action.

Attachments

    Outcomes