If you have questions or if you want to share your opinion about Aware IM post your message on this forum
#52892 by johntalbott
Sun Jan 26, 2020 1:26 am
Is anyone familiar with this error?

There is nothing in the service documentation that references error 1010. https://positionstack.com/documentation

I get a similar popup message in the browser, but the following is from the AIM server output:
2020-01-26 00:58:12,521 ERROR RTCRM#admin -Execution Exception after starting process GetGeocodeByAddress message Service provider returned the following error: error code: 1010

I'm getting this with the following hard coded url which works fine in Postman or Chrome browser.

geocodeurl.png
geocodeurl.png (33.24 KiB) Viewed 731 times



Postman response body

Code: Select all{
    "data": [
        {
            "latitude": 38.897675,
            "longitude": -77.036547,
            "type": "address",
            "name": "1600 Pennsylvania Avenue NW",
            "number": "1600",
            "postal_code": "20500",
            "street": "Pennsylvania Avenue NW",
            "confidence": 1,
            "region": "District of Columbia",
            "region_code": "DC",
            "county": null,
            "locality": "Washington",
            "administrative_area": null,
            "neighbourhood": "White House Grounds",
            "country": "United States",
            "country_code": "USA",
            "continent": "North America",
            "label": "1600 Pennsylvania Avenue NW, Washington, DC, USA"
        },
        {
            "latitude": 38.897498,
            "longitude": -77.037538,
            "type": "address",
            "name": "1600 Pennsylvania Avenue Northwest",
            "number": "1600",
            "postal_code": "20500",
            "street": "Pennsylvania Avenue Northwest",
            "confidence": 1,
            "region": "District of Columbia",
            "region_code": "DC",
            "county": null,
            "locality": "Washington",
            "administrative_area": null,
            "neighbourhood": "White House Grounds",
            "country": "United States",
            "country_code": "USA",
            "continent": "North America",
            "label": "1600 Pennsylvania Avenue Northwest, Washington, DC, USA"
        }
    ]
}
Last edited by johntalbott on Sat Feb 01, 2020 3:44 pm, edited 1 time in total.
#52893 by himanshu
Sun Jan 26, 2020 12:38 pm
Hi John,

I also have the same issue in one implementation. I currently manage to create a plugin and complete the task to meet timelines.
I am sure this is not from the API provider, it must be something which is not posted properly from AIM. I will spend some more time to troubleshoot the issue later week and will update with my findings.

On which AIM version you did this test?
#52894 by johntalbott
Sun Jan 26, 2020 4:29 pm
Hello Himanshu. Thanks for the information.

I've tested in 8.3 and the latest build (2719) of 8.4.
#52997 by gijsvb
Fri Jan 31, 2020 6:21 pm
Same error here on a simple call to openiban service.

Error 1010 nowhere to be found in the service provider docs.
#52998 by BobK
Fri Jan 31, 2020 7:41 pm
gijsvb wrote:Same error here on a simple call to openiban service.

Error 1010 nowhere to be found in the service provider docs.


The following is my answer I added in the other thread.

@gijsvb

To get https://openiban.com/validate/NL36RABO0310308267 working within Aware:
In your BO that implements REST, add the following to the "Request HTTP Headers"

Accept */*
User-Agent Mozilla/5.0
Cache-Control no-cache
Host openiban.com
Connection keep-alive

I added all 5 and it worked, but I do not know which one actually fixed the issue.


I got these headers from looking at what headers Postman used when successfully making the REST call. I removed the Postman-Token and Accept-Encoding headers and changed the User-Agent to Mozilla/5.0.
#52999 by johntalbott
Fri Jan 31, 2020 11:38 pm
Thanks for the guidance.

I narrowed it down to the User-Agent header. It appears that hosts throwing the error must require it.

https://developer.mozilla.org/en-US/doc ... User-Agent

https://stackoverflow.com/questions/242 ... uest-valid
#53003 by gijsvb
Sat Feb 01, 2020 9:21 am
johntalbott wrote:Thanks for the guidance.

I narrowed it down to the User-Agent header. It appears that hosts throwing the error must require it.

https://developer.mozilla.org/en-US/doc ... User-Agent

https://stackoverflow.com/questions/242 ... uest-valid



Thanks, adding the HTPP request header values is the solution. Just added the 'accept', 'user-agent' and 'cache' parameters and it worked.

Thanks a lot.

Who is online

Users browsing this forum: MSN [Bot] and 24 guests