on 07-13-2009 3:10 PM
Hi All,
I'm on PI 7.1 and performing an RFC Lookup graphically. When I test it, i'm getting the error *com.sap.aii.utilxi.hmi.api.HmiMethodFault: Technical error when calling an adapter remotely. The HMI method with the ID process was called with an incorrect session status. The system accessor object is missing*. I cheked the mapping with the trace level DEBUG and found that the exception is occuring when the sytem is trying to close the accessor.
I checked the SDN and found few threads which talk about the same error but none of them had provided the solution.
Can anyone please help me out in this regard.
Any help would be highly appreciated.
Regards
Anil Veepuri
Hi, I have exactly the same problem. There is exception on test but no problem on runtime. How can you resolve it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jayasima,
I have already looked through both of those postings and sadly they don't help:
-> Checked authorisation and this is ok. I even tried with my own userid and the comm channel monitor shows with 'green' status showing all is fine
-> I tried the INTEGRATION_DIRECTORY_HMI with path /dir/hmi_cache_refresh_service/ext via IE url and this shows everything working fine.
We get the error when trying to call the RFC comm channel, so it seems that the UDF is unable to trigger this. Thus, the problem seems to lie between the UDF and the comm channel. The error shown is:
1) when triggering the RFC:
Technical error when calling an adapter remotely. The HMI method with the ID process was called with an incorrect session status. The system accessor object is missing
2) when trying to close the accessor:
Technical error when calling an adapter remotely. The HMI method with the ID close was called with an incorrect session status. The system accessor object is missing
To me it seems that it may be an issue with the com.sap.aii.mapping.lookup but I've been assured that the version will be the same in Dev & QA. So the following code seems ok:
accessor = LookupService.getRfcAccessor(channel);
InputStream inputStream =new ByteArrayInputStream(rfcxml.getBytes());
XmlPayload payload = LookupService.getXmlPayload(inputStream);
but the actual call:
rfcOutPayload = accessor.call(payload);
seems to fail, and then the following 'close' also fails:
accessor.close();
I see that there are other postings where a solution has been found - but no explanation provided. e.g., and
Thanks,
Sukhy
Hi,
Feedback from OSS was that the user for the RFC connection we had did not have all the necessary authorisations.
Trace showed following:
>RfcGetException rc (7) message: User XIUSER_RFC has no RFC authorization for function group SALERT_CREATE.
<RfcGetException
Recommendation:
Please add the correct authorization, the role SAP_XI_APPL_SERV_USER is not sufficient. Specifically you need:
Implementation of the authorization object S_RFC:
- ACTVT: 16
- RFC_NAME: SALERT_CREATE
- RFC_TYPE: FUGR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
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.