Arunhclite Super Contributor.
Super Contributor.
3248 views

Server did not recognize the value of HTTP Header SOAPAction

Jump to solution

Hi All,

I have been creating Vugen script for a SOAP request. The request works fine in SOAP UI tool.

But the same request fails in Vugen tool with the below error

<soap:Fault><faultcode>soap:Client</faultcode><fault
Action.c(14): string>System.Web.Services.Protocols.SoapException: Server did not recognize the value of
Action.c(14): HTTP Header SOAPAction: .\r\n

In the request we have authorization header as below.

<tns:AuthenticationHeader xmlns:tns=\"http://ws.synectics-solutions.com/webservices/DataServices/v2/ServicesAccess\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">"
                    "<tns:Username>xxxxxxxx</tns:Username>"
                    "<tns:Password>xxxxxxxxxxxxxxxxxxxxxxxxx</tns:Password>"
                    "<tns:ClientName>xxx</tns:ClientName>"
                "</tns:AuthenticationHeader>"

 

Is there any Header syntax need to be added in script?

Kindly update on this.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Arunhclite Super Contributor.
Super Contributor.

Re: Server did not recognize the value of HTTP Header SOAPAction

Jump to solution

Hi ,

 

Thanks much, this issue has been resolved.

 

The problem is SOAPAction name is not taken automatically, so we have added it manually and it worked.

0 Likes
2 Replies
Jgor2810 Respected Contributor.
Respected Contributor.

Re: Server did not recognize the value of HTTP Header SOAPAction

Jump to solution

Hello,

 

Greetings,

 

I´ll like to review this but first could you share the following

* Script folder.

*Raw data from the web services.

HTTP Request and HTTP Response log from SOAP UI .

 

With this I will be able to review this and share proper steps to you to correct this

0 Likes
Highlighted
Arunhclite Super Contributor.
Super Contributor.

Re: Server did not recognize the value of HTTP Header SOAPAction

Jump to solution

Hi ,

 

Thanks much, this issue has been resolved.

 

The problem is SOAPAction name is not taken automatically, so we have added it manually and it worked.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.