HTTP_RESP_STATUS_CODE_NOT_OK

[Former Member]

Hi All,

When I place any source file for processing, the message ends with the below error in MONI.

<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code> 
  <SAP:P1>401</SAP:P1> 
  <SAP:P2>Unauthorized</SAP:P2> 
......................................
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>

Earlier all went fine, but recently the server was down for sometime and then restarted all services. Since then this problem is occurring.

I have gone through similar kind of threads and as per the suggestion from those threads, have gone throughrestarting the J2EE server. But still have the same problem. Please anybody help me to resolve this issue.

Thank you

[Former Member]

Hi Bhanu ,

SAP J2EE Engine returns HTTP response with status code 500 when many parallel users are trying to login to one application. One or several

requests may fail with HTTP response code 500 during the load scenario. In such cases, when the error happens, the following

exception must be present in the default trace of the j2ee engine .

java.lang.NullPointerException

at

com.sap.engine.services.security.login.LoginContextFactory.initializeLog

inContextmp;#40;LoginContextFactory.java:180mp;#41;

at

com.sap.engine.services.security.login.FastLoginContext.loginmp;#40;Fast

LoginContext.java:127mp;#41;

at

com.sap.engine.services.servlets_jsp.server.runtime.context.SessionServl

etContext.doLoginmp;#40;SessionServletContext.java:619mp;#41;

at

...

If this error happens in XI load scenarios, this trace is visible in the

additional information of the failed message.

Reason and Prerequisites

Reason: The authentication stack for the corresponding application is

not initialized properly.

check SAP Note - 822211 .

there is no harm in refreshing the cache also .

Regards,

[Former Member]

Hi Bhanu,

1. This Error Code (401) is used when access to a resource is protected and the client did not provide valid authentication credentials.

Often 401 response includes information that causes the user agent to prompt the user for a username and password.

2. Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER

u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>

u2022 If the error is in Adapter Engine

u2013then have a look into SAP Note- 821026 (https://service.sap.com/sap/support/notes/821026) (SMP Login Required), Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.

u2022 May be wrong password for user XIISUSER

u2022 May be wrong password for user XIAFUSER

u2013 for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message.

Regards

Venkat Rao .G

[Former Member]

Hi,

I have tried all the ways mentioned: Role was assigned, J2EE engine restarted, Cache refreshed.

Still the issue exist.

Let me know what to do.

Deleting of cache in Adapter Engine will work?

[agasthuri_doss]

Hey,

• Did you Checked Adapter Engine Cache,

• Check the User ID used in the Sender JDBC adapter has the Authorization to read the records from Table,

Cheers

Agasthuri

[Former Member]

Hi Bhanu,

Also check in Visual Admin All Services Configuration Parameters comparing with previous values & new

values and all are running perfectly or not. And Delete the Cache at Adapter Engine Level and restart

the server once. Also verify the SAPJSF & JCo User credentials in VA before restarting the server.

Regards

Venkat Rao .G

[Former Member]

Hi,

Your user doesn't having the "SAP_XI_APPL_SERV_USER" role.

Ask your BASIS guy to add that role to your user id.

Regards

Ramesh

[Former Member]

Hi,

Username or password may be changed which is used in communication channel. (Based on that username and password we can access the R/3 System). or may be the user is locked, So check in SU01 or refresh the cache.

Regards

Vijaykumar

[agasthuri_doss]

Hey,

>recently the server was down for sometime and then restarted all services

Check whether Cache is Upto date

Cheers

Agasthuri

[Former Member]

Hey

Please check the below blog

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Thanks

Aamir

[agasthuri_doss]

Hey,

Can you check the User ID - Authorization

Cheers

Agasthuri

[Former Member]

Hi,

Can you be more clear?

Thank you.

[former_member568822]

Hi,

Its seem like a user was locked. Pls go to su01 to check and unlock it.