Hi @Steve 3248,

Please confirm the below mentioned things to give better feedback on this.

• Is the SOAP request HTTP or HTTPS?
• Is the authentication simple or parametric?

Also, please share the configuration you have done in Command.

Hi @Padmakumar,

1. This is an HTTPS request
2. The Authentication is parametric. 

This request does not have any mandatory parameters to be passed. And even if I’m passing the arguments below, I still keep getting the same error 

Appreciate your support!

Stevin

Hi @Steve 3248 ,

Are you passing any JSON data directly to this as input?

If so, please try passing it using a variable and add the variable in the body parameter.

You can also check if authentication is required when accessing the URI without AA and try saving the SOAP data to wsdl and import it.

I’m not passing any arguments. Making a SOAP request using only the URI. Even then it shows the same error.

When opening in the browser, it doesn’t require any authentication. 

When I pass the URI, I use ‘https’ but in the error message, it shows only http. Does this ring any bells for you?

Stevin

Hi @Steve 3248

To be sure that no issues are there can you save the soap data as wsdl file and then import it...After that you can include variable to it accordingly

and you can check the bot log here

C:\ProgramData\AutomationAnywhere\BotRunner\Logs

Cheers

I am not sure. It could be because of any rule which will be available for that page to always redirect as HTTP.

For more details on working with SOAP Web Service, please refer here.

Dear @Steve 3248,

It sounds like the issue may be related to the way that Automation Anywhere is handling the URI for the SOAP request. It is possible that the bot is trying to access the URI using the wrong protocol (HTTP instead of HTTPS), which could be causing the authentication error.

One thing you could try is specifying the full URL for the SOAP request, including the protocol (e.g., https://example.com/soap). This may help the bot to correctly identify the correct protocol to use when accessing the URI.

You could also try adding a "Wait" action before the SOAP request to give the server time to respond. This may help to resolve any issues related to timing or connectivity.

If these suggestions don't help, it may be helpful to check the log files to see if there are any error messages that can help identify the cause of the issue. You can find the log files by going to the "Logs" tab in Automation Anywhere and selecting the appropriate bot from the list.

Regards,

Dear Zaibi,

I was passing the https:// in the URI. For the logs, this is what I’m getting in the CR too - 

Not sure if the wait action would help since this error is in the SOAP action itself.

Stevin

Dear @Steve 3248,

If you have checked the URI and the connection and the issue persists, it may be helpful to check the log files for more information about the cause of the error. You can find the log files by going to the "Logs" tab in Automation Anywhere 360 and selecting the appropriate bot from the list.

Regards,

Hi guys, any update about this issue? I am working with WSDL service , in SOAP works fine but not in AA. I get next error message : Incorrect SSL certificate provided for SOAP request for URI. Check if the file/certificate path or password provided is valid.

@hperezmu 1535

Hi, this was resolved. In my case, the issue was in the SOAP service definition itself. On opening the SOAP URL in a web browser, we found that even though the URL was https, the definition was still pointing to http links which was causing the error.

Hope this helps

Regards

Stevin

Thanks friend meaning that the problem was in the service no in Automation Anywhere really?

Hello,

Any updates about this issue? I am also facing similar issue. The Service call is working fine in Dev but throwing an error - “Could not parse the WSDL URL for Soap request.

Thank you