Are you seeing this error only in the "Run Now" test result view mode?    This is pretty common.   If your answer is yes, try running your workflow to see if the results are what you were expecting.

Thanks

Thanks Mark.
Yes that is when I click on 'Run Now' but even if I run the workflow, I get the below error

Failed to invoke web service. Error returned from server: <soap:Fault xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>soap:Server</faultcode><faultstring>Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.

In the Soap Editor copy and paste the following, make sure to change listName to your list name where i have "Your List Name":

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m="http://schemas.microsoft.com/sharepoint/soap/">
<soap:Header>
</soap:Header>
<soap:Body>
<m:UpdateListItems>
<m:listName>Your List Name</m:listName>
<m:updates>
<Batch OnError="Continue">
<Method ID="1" Cmd="New">
<Field Name="ID">New</Field>
<Field Name="Title">Test One</Field>
</Method>
</Batch>
</m:updates>
</m:UpdateListItems>
</soap:Body>
</soap:Envelope>

Thanks again Mike

Still gives the same error. Tried both options, 'Run Now' and running the workflow.

Are you seeing any errors in the ULS logs?

Hello Shaju Samuel‌ - 

A few things to try.

Does the login that is executing the web service have access to the list that is being written to? If not, you will be able "Test the connection" just fine, but will not be able to Run Now.

Also, check the spelling on the list name, could be something as simple as a typo .

Hope this helps!

Can you take a screen shot of the action showing the Soap Editor along with the soap above?     This will  help to narrow it down a bit.

Thanks

Thanks Jan

I don't see anything specific in the ULS logs in regards to the error.

Hi Jesse

Thanks.

Yes the user have access to the list and I have made sure that the Spellings and names are all correct.

Hi Mike

The screenshot as requested. Also, I have tested the list name with and without spaces (to test)

Hmmm... That was going to be my next question if the name is accurate. We ran into an issue as a user renamed their list and we saw failures.

Have you tried any other web service calls? Do they work? What about writing to a different list?

Sometimes I've seen errors like this occur because of the URL.    It is the difference between using the "Internal" and "External" URL's specified in your URL mapping in Central Admin.    This may very well be the reason you are seeing this.    Please check your mappings and test with the URLS you see in the URL mapping.

You may also want to test with an "Https" variant, as opposed to "Http".

Hopefully this solves your issue once you locate the correct URL.

Thanks,
Mike

I think ‌ is right with the URL Mapping in Central Administration. I had the same issue at a customer and  the solution was to use the internal URL from Access Mappings in CA