http 500 error with http sender adapter

[krishg]

Our partner has been sending us messages successfully until suddenly they started getting http 500 error (

Error message: Connect failed: connect: Connection refused; Connection refused)

I have looked at smicm and nwa logs.. what could be the possible reasons for this error message? and where can i find the logs on PI?

[Former Member · Accepted solution]

Along the same lines as Nabendu, are you able to verify / test your HTTP Sender interfaces independently? What is the result if you run your own interface test procedure internally and externally (to firewall). What about with / without HTTPS?

I wonder if something happened with character set or encoding which confuses the server. It is strange that you see no trace of the errors in SXMB_MONI or ICM. If the trace is turned on you should see the whole HTTP conversation in the ICM log (e.g. HTTP/1.1 200 OK and then the content type/ headers their program is sending)

Is it only this one partner who has issues over similar interfaces in your PI environment?

[krishg · Accepted solution]

Thank you to everyone for their suggestions.

Aaron, We did not turn on the trace on SMICM. I just looked at trace logs (i was expecting http errors to show up in smicm logs )...Is that a wrong assumption.

Suddenly, Our partner was finally able to start sending some messages to PI server.  The first time message was sent, it failed with 500 error and a re-try after 5 minutes was successful. This kept happening for almost two hours (and suddenly all the messages in the queue got processed with in 2-3 minutes) . We are perplexed as to why messages were consistently failing the first time and got processed second time (and then suddenly everything got processed).

We thought it could be due to Router/network issue (on one of the two servers)..When we tried to hit the url from outside our firewall, we were able to access without any issues. We are going to monitor to see if this error happens again. If anyone else has encountered this issue, please do let us know.

We use web dispatchers and the message is sent via https.

[krishg · Accepted solution]

We resolved the issue.. Our partner did not add all our IP address to their firewall :-(...

[Former Member · Accepted solution]

Krish,

The same firewall issue I suggested you in my third point but not sure why it took so long to sort out the issue.

Anyways good to see it worked.

Regards,

Ashish

[Former Member]

Hi Krish,

Http 500 error is temporarry error, can you please check the below points ....It may help you.

Internal Server Errors are not often caused by caching issues but I have, on occasion, seen the error go away after clearing the cache. It's such an easy and harmless thing to try so don't skip it.

Delete your broser's cookies.Some 500 Internal Server Error issues can be corrected by deleting the cookies associated with the site you're getting the error on.

Even if the http 500 Error is a problem on the web server, the issue may only be temporary. Trying the page again will often be successful.

Regards,

Ramana

[smavachee]

Can you check Note # 1522630. It may help you.

Regards,

Sunil

[Former Member]

Krish,

Please check if the user id being used by your sender application is locked? That you can check in SU01.

If so then get it unlocked & get your password reset & share the same with the sender application.

If the user id is not locked then check with your basis team to find whether the sender application is able to login to the PI server. This can be done by tcode STAD with the input as user id (used by sender application).

If there is no login attempt by the sender application on the PI server then you need to involve network team to trace out if there could be possibility of firewall issue which is not allowing the sender application to send requrest to your PI server. If so then ask network team  to add the IP address of the sender application to your firewalll to allow request to reach at Pi server.

Hope this will help to sort out the issue.

Regards,

Ashish

[nabendu_sen]

Hi Krish,

Go to SXMB_MONI of ABAP Stack and open Trace of this message. You should find detail of this error. Revert back with the error details.

[krishg]

Hi Nabendu

Unfortunately I am not seeing my partner's msg in sxmb_moni. I have looked at smicm to see if there are any logs and i dont' see anything there as well.

[nabendu_sen]

Hi Krish,

Can you check whether the URL they are using to send data to PI are correct or not? It should have the below format.

http://<host>:8000/sap/xi/adapter_plain?namespace=<namespace>&interface=<interface>&service=<sender_service>&party=&agency=&scheme=&QOS=EO&sap-client=001&sap-language=EN

You can also try by entering this URL in any Internet Browser.

[nabendu_sen]

Hi Krish,

This should not be a problem with User Access / Lock, otherwise 401 Unauthorized would come. It is coming because Sender 3rd Party is not able to reach SAP PI. As you said, it happened suddenly may be the URL at sender to call PI has changed or connectivity / Firewall configuration changed. Checked properly. As I said, check in Internet Browser to check whether you can reach PI server or not.