on 04-10-2015 12:50 AM
Hi Experts,
I have implemented Service gateway and test it through REST Client and all tests are pass.
I've tried to connect to that service through an Android App using "HttpURLConnection" using that code:
public static String serviceURL = "http://xxxxxxxxxxxxxxxx/sap/opu/odata/sap/Z_GWDEMO_FM_SRV/";
URL obj = new URL(serviceURL):
con.setRequestMethod("GET");
int responseCode = con.getResponseCode();
Exception was thrown at mentioned point point. Here I've tried to test the service again through REST Client the following response is generated:
<error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
RFC Error: Password logon no longer possible - too many failed attempts
</message>
<errordetails/>
</innererror>
</error>
When tried with other services, the same XML response is generated.
Note: I could not use GWPA now as SSL connection is not enabled to my server.
My questions:
It seems that the RFC is locked. How to unlock it?
What is the best way to connect to Gateway service by URL + Headers + operations through Android app?
Regards,
Mohamed.
Hi Experts,
Finally after long search and trials cooperating with my colleagues, I found the problem solution.
The services were for some reason locked by system. We've reset logon Data by entering to the service screen using T.Code: SICF and search for our service name as follow:
Execute your search, the service tree will be displayed as follow:
Double click on the service at the end of the tree then go to "logon Data" tab screen to reset the logon data as follow:
After reset the logon data service will be available again as normal.
Regards,
Mohamed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is not the RFC which is locked. It is the user which is locked.
- SAP Basis/Security person should be able to help you to unlock the user. (Tcode SU01).
Also check if a user is hardcoded in the RFC destination. In that case, that user need to be unlocked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elmarakby,
Use Authorization Basic Header in the service and check whether it will Resolve.
Regards
Gaurav Ahluwalia
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.