2025 Feb 04 1:43 PM
It is something very simple but it is not working for me
I am calling the SAP business one web service to log in
here you can see that it works from postman
but when I make the call from sap build it gives me an error
Any comments, I feel a little frustrated because I haven't been able to move forward and I know it's something stupid that I'm missing
Please your help
2025 Feb 04 3:12 PM
Good morning, excuse my boldness,
I saw that you have great experience with web services
Maybe you can help me, I would really appreciate it.
2025 Feb 04 4:01 PM
Hello,
It seems to me that you cannot reach the server. It is the same machine that you run your test using postman?
Best regards
2025 Feb 04 4:19 PM - edited 2025 Feb 04 4:21 PM
Yes, it is the same machine, my browser is Google Chorme
2025 Feb 05 6:15 AM
2025 Feb 05 12:46 PM
Yes, here it is in the project I only have three activities
Custom Script
custom code
Call Web Service
Log Message
The error is
Error Detail 1: "Login job started before irpa_core.request.call activity ended. Missing await ?"
Error Detail 2: "queryA ENOTFOUND 45.163.29.123",
2025 Feb 05 6:06 PM
I don't that much about the Call Web Service activity, just what I know from using it with DMS. But the way it is documented the JavaScript is slightly different.
2025 Feb 10 1:12 PM - edited 2025 Feb 10 1:13 PM
Hello Freyagiran,
Thank you for reaching out to us. After reviewing both of your web service calls, I couldn’t find any issues with the configuration or custom code.
The error ENOTFOUND 45.163.29.123 typically indicates that the hostname or IP address in the URL is not reachable or cannot be resolved. Since you are directly using the IP address 45.163.29.123, it seems the application is unable to connect to the specified IP or port.
Incorrect or Unreachable IP Address
Port Accessibility
Connectivity Issues
If everything checks out, you can use the following payload as an example:
let input = {
"CompanyDB": "URGO_TEST",
"Password": "xxxxxxxxx.",
"UserName": "layer"
};
return {
method: 'POST',
url: "https://45.163.29.123:50000/b1s/v1/Login",
responseType: 'json',
resolveBodyOnly: true,
json: input,
headers: {
'Accept': 'application/json',
'Content-Type': 'application/json'
},
https: { rejectUnauthorized: false }
};
2025 Feb 10 3:20 PM
Thanks for your help!!!
I honestly don't know what I did to make it work.
Change the agent version, and also the SDK. I´m currently using agent version 3.24.54, SDK 1.27.60 and it works
I try it with the new versions and it doesn't work
2025 Feb 11 1:12 PM
Hello All,
I am also getting the same issue while making an API call to the S4HANA on-premise system. Basically, my I the automation is trying the generate the CSRF token but it fails with the same issue - queryA ENOTFOUND.
API endpoint - https://sdcnl1dtm002.openstack.eu-nl-1.cloud.sap:44301/sap/opu/odata/sap/API_PURCHASEREQ_PROCESS_SRV
In Postman, it works perfectly fine with the HEAD call and the corresponding csrf token is returned in the response headers. When I implement the same in SBPA with Ajax call (mentioned below), the issue appears:
Please find below the API call defination:
3 weeks ago
Hello All,
Same issue here. Desktop agent 3.32.58. This issue only shows up in Design Mode