cancel
Showing results for 
Search instead for 
Did you mean: 

AE error in RWB

former_member192375
Participant
0 Kudos

Hi,

SAP PI 7.10 SP7.

Since we have applied SP7 we have the following error on the Central Adapter Engine in the RWB.

"HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://host Name:port/AdapterFramework/rtc]" "

However when I go into the channels into the channels for this AE then the status of the channels is fine.

In all the Exchange Profile, NWA and ABAP configuration parameters I have been using fully Qualifier Domain names. However when this error is displayed the "Host Name" s not fully qualified. I just have a feeling that this has something to do with it, but not sure where to rectify it.

Please can someone assist in this matter?

Regards

Willie Hugo

Accepted Solutions (0)

Answers (6)

Answers (6)

former_member192375
Participant
0 Kudos

PLease see above.

former_member192375
Participant
0 Kudos

Problem solved apply SP7 PL 10 for Messaging in JAVA, as recommended by SAP support.

JoelTrinidade
Active Contributor
0 Kudos

Hi Hugo,

please go to the exchange profile and try checking

com.sap.aii.connect.integrationserver.name

com.sap.aii.connect.integrationserver.httpport

central adapter framework details are taken from there

also check these:

com.sap.aii.adapterframework.serviceuser.language

com.sap.aii.adapterframework.serviceuser.name

com.sap.aii.adapterframework.serviceuser.pwd

name = XIAFUSER

and the correct pwd

Regards

joel

Also dont forget to do a cache refresh.

sugata_bagchi2
Active Contributor
0 Kudos

Hi,

Your Web server encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.

This is a 'catch-all' error generated by your Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong.

500 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).

Open an IP socket connection to that IP address.

Write an HTTP data stream through that socket.

Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '500'.

Here you should chek the parameters -- ICM or host_name_full and also check in C:\WINDOWS\system32\drivers\etc the host file that caontains the proper information.

Thanks

Sugata B

former_member184619
Active Contributor
0 Kudos

Hi,

Check this blog... it might be helpful...

PI7.1 Issue (Fully Qualified Domain Names)

/people/rohit.mehta3/blog/2008/05/13/pi71-issue

Or Just cross check with this OSS note

XI readiness check u2013 sap note 817920 (SMP login required)

https://websmp209.sap-ag.de/~sapidb/012003146900000492702008E/ReadinessCheckFor71.pdf

and maintainf the FQDN host name in HOST file.

Sachin

Edited by: Sachin Dhingra on Mar 27, 2009 2:24 PM

Shabarish_Nair
Active Contributor
0 Kudos