cancel
Showing results for 
Search instead for 
Did you mean: 

USER_CONTEXT_ERROR

former_member204873
Contributor
0 Kudos
1,258

hi All,

I have async scenario(file to ABAP). In CALL ADAPTER pipeline step of sxmb_moni, i am getting below error:

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">USER_CONTEXT_ERROR</SAP:Code>

<SAP:P1>Error when accessing the secure storage (-> evaluate trace)</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>create_user_context</SAP:AdditionalText>

<SAP:Stack>An Error Has Occurred in User Context Error when accessing the secure storage (-> evaluate trace)</SAP:Stack>

I tested sync scenario and it is working correctly.

What can be the cause of this error?

Thanks,

Mayank

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member654879
Discoverer
0 Kudos

HI,mayank.gupta5.

Did you get any solution to your issue?

I get the same issue now and want to get the solution,Can you tell me your solution,

Thanks!!!

Former Member
0 Kudos

Hi Mayank.

Did you get any solution to your issue?

Warm Regards,

Anshul

former_member200962
Active Contributor
0 Kudos
I tested sync scenario and it is working correctly.

Did you create an Async Proxy for the File to Proxy Async flow?

former_member204873
Contributor
0 Kudos

Actually i am trying to get acknowledgement from client proxy. Scenario is proxy -> file -> proxy(Acknowledgement). I am following this link: http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/frameset.htm .

Acknowledgement status as visible in sxmb_moni of PI is "No errors in Acknowledgement". It is giving this error while sending acknowledgement to proxy (ECC system).

former_member204873
Contributor
0 Kudos

hi all,

Any solution for the error i am getting.

Thanks,

Mayank

former_member187339
Active Contributor
0 Kudos

Hi Mayank,

>>I have async scenario(file to ABAP). In CALL ADAPTER pipeline step of sxmb_moni, i am getting below error:

In your question you are mentioning the scenario as file to proxy

>>Actually i am trying to get acknowledgement from client proxy. Scenario is proxy -> file -> proxy(Acknowledgement).

And in one of the replies you have mentioned it as proxy to file!!!

So which is your scenario..

Regards

Suraj

former_member204873
Contributor
0 Kudos

scenario is proxy -> file -> proxy(Acknowledgement).

since it is failing file - Proxy(Acknowledgement) ,, hence i mentioned it as file to proxy.

Oher than this i had created another scenario http - proxy and getting the USER_CONTEXT_ERROR error .

former_member187339
Active Contributor
0 Kudos

Hi Mayank,

Have you used the same code as mentioned in help.sap in the client proxy? Can you paste here the code snippet?

Also make sure that you are asking only for Transport acknowledgment in the Proxy code (since the file adapter can provide only Transport acknowledgment)

Regards

Suraj

former_member204873
Contributor
0 Kudos

hi suraj,

Let me clarify my scenario.

Please help me in identifying the below mentioned scenario:

Scenario is File to Abap proxy (Async). Now, i am getting the above mentioned error in Moni in the Call Adapter pipeline step of PI.

This error is coming for all async scenarios where i am trying to connect to an ABAP proxy on the ECC. Its not an issue with the user credentials as i have tested the same channel for an ABAP proxy sync scenario and it is working as expected.

Please let me know if you need any more info on the same.

Thanks!!!

lnirmala
Participant
0 Kudos

Hi Mayank,

Are you using BPM in your scenario?

Please check the SAP Note Number: 1248707 BPE-RUN: Error USER_CONTEXT_ERROR when sending

Rgds,

Lekshmi.

Former Member
0 Kudos

What you are sending to ABAP system? Is it IDoc or RFC?

former_member204873
Contributor
0 Kudos

Scenario is file to ABAP Proxy.

In trace it is coming as:

<Trace level="3" type="T">HTTP-client: closing...</Trace>

</Trace>

<Trace level="3" type="System_Error">External error header received</Trace>

</Trace>

</Trace>

<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="3" type="T">Persisting message Status = 014</Trace>

<Trace level="3" type="T">Message version 003</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>