PI internal error : HTTP connection to ABAP Runtime failed

Hi Experts,
From last 3 days,I am geting a SAP PI internal error(PFA for the detail).for that error,previous sucessful scenario also not working.The error I am getting in the 'TEST CONFIGURATION' of the ID:(sometimes i am getting this error in ' Receiver Determination' and sometimes in 'interface determination & mapping')
[ Receiver Determination
<Not found>
Internal Error
HTTP connection to ABAP Runtime failed. Error: Unexpected end of file from server URL: http://deveppi103:8002/sap/xi/simulation?sap-client=117 User: PIDIRUSER ]
Please,suggest.
Regards,
Raj Tripathy

Hi Raj,
We had faced this issue a few days back and there was an entry missing in the table.
This issue has been discussed on this forum multiple times:
Prefix number: entry missing for system TST client
workflow- Prefix number: entry missing for system xxx Client xxx
Regards,
Sanjeev.

Similar Messages

Error : HTTP Connection to ABAP Runtime failed

Hi,
i am working on xml to flatfile interface.when i am trying to test the scenario from ID - > Tools -> Test configuration option i am getting below error.
Receiver Determination <Not found>
Internal Error Http connection to ABAP runtime failed.
Error : 403 for bidden.
I have checked in Receiver determination its been configured properly.
Is it any basis settings problem ?
Thnx,
Siva.

Hi Siva,
Check this links
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Regards
Ramesh

HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL

HI experts,
I am tsting Test configuration in ID in Quality environment. I am getting below error for all interfaces.
but same interfaces are working fine in Develoment environment.
Internal Error
HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://abcdxi06.abcdk.abcpower.com.sg:8000/sap/xi/simulation?sap-client=300 User: PIDIRUSER.
thanks
Srinivas

Similar problem discussed here:
HTTP connection to ABAP Runtime failed : 403 : forbidden
Error testing configuration: "HTTP connection failed"
Check if the port is defined, as suggested in second link.
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 1, 2009 1:27 PM

HTTP connection to ABAP Runtime failed. Error: 403 Forbidden

Hi ALL
We where testing our scenario using the Test Configuration in Integration Engine.
We have come across the following error in the second step of Determining the receiver.Here is the error message we received...
HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: _http://SAPXDV01.sap.client1.local:8000/sap/xi/simulation?sap-client=150 User: PIDIRUSER
Please, do let us know ... if you have received similar error & what solution can be applied...
Your help is greatly appreciated!
Thank you,
Patrick

Hi,
Go through this thread...
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0f00c890-0201-0010-beb2-c96050edc426
JCO_COMMUNICATION_FAILURE
Error in XI server: JCO_COMMUNICATION_FAILURE in Message Mapping
This might help you..
Regards,
Divya

HTTP connection to ABAP runtime failed

I am building a scenario where XI picks up a file from a directory and pushes an IDoc to ECC. I have configured the interface with the Design tool, and I believe my setup in the Configuration tool are correct too, however I am encountering an error when testing the scenario by means of --
Tools --> Test Configuration.
The testing tool is giving me the following error upon processing the reciever determination:
HTTP connection to ABAP Runtime failed.
Error: 403 Forbidden
URL: http://serveraddress:port/sap/xi/simulation?sap-client=100
User: PIDIRUSER
First of all, I am not sure who the PIDIRUSER is, I assume it's a system user? Second, given that this error is a HTTP connection error, I am lead to believe that the issue lies somewhere in the RFC connection from XI -> ECC. I am not sure why exactly it's attempting to connect via HTTP as my communication channel is using the IDoc adapter with an RFC destination to connect to ECC. Possibly I have configured this incorrectly. I have read about having to configure a RFC adapter when posting messages from R/3 to XI, does the same apply when posting an IDoc from XI to ECC? Does anyone have any other thoughts as to why this error may be occuring? Thanks in advance for your time and help.

This might help you
http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
Regards
Agasthuri Doss

HTTP connection to ABAP Runtime failed : 403 : forbidden

Hi all,
I have configured a normal file to file scenario and when i test it in the TEST CONFIGURATION tool in intergration directory, am getting the error.
HTTP connection to ABAP Runtime failed
403: forbidden
user: PIDIRUSER
Sugessions plzzz
Regards
Arun
Message was edited by:
Arunkumar sukumar

Hi
Try this
note 517484
1) Activated all services
2) In Integration builder, receiver communication channel make sure you have entered proper
host service number
path = /sap/xi/enigne?type = receiver.
3)Go to SU01 > type PIISUSER and reset the user's pw
Check out this might be helpful
http://help.sap.com/saphelp_nw04/helpdata/en/89/05793c05f0807be10000000a11405a/content.htm
1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.
2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear.
3.to send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.
4.
- Activated all services on the r3 system.
- Create HTTP connection to XI from r3
sm59-> http connetons to r3
- let us say you have created a HTTP connection in the integrationserver_XI, make sure in its settings the prefix path is set to /sap/xi/engine?type=entry. Also check its log on credentials, you can use xiappluser.
- IN Integration builder, receiver communication channel make sure you have entered proper
host service number
path = /sap/xi/enigne?type = receiver.
5. can you also try the following;
Visual Admin -> start the service,
"com.sap.aii.af.ms.app".
I don't know this Forum no fhats why i copied.
Thanks

SM59 - HTTP Connection to ABAP System fails

I am building an http conn from XI to ECC6 for ABAP proxy
On Connection Test, I get the error - ICM_HTTP_CONNECTION_FAILED
On running the trace in SMICM, I get the following:
[Thr 5] *** ERROR => Connection request from (-1/65535/0) to host: srpidev.srhouse.com, service: 8000 failed (NIEHOST_UNKNOWN)
[Thr 5] *** ERROR => IcmJ2EEScheduleFunc: Connection to srpidev.srhouse.com:8000 failed - please check host configuration (-8)
I get the foll on running the report: SPROX_CHECK_HTTP_COMMUNICATION
HTTP communication contains errors (see long text for diagnosis)
Message no. SPRX086
Diagnosis
The HTTP communication of this application server is not functioning correctly.
When calling the method
IF_HTTP_CLIENT=>RECEIVE
the exception
HTTP_COMMUNICATION_FAILURE
was triggered.
The short text for this exception reads as follows:
Communication Error
Procedure
Contact your system administrator
Can someone please help?
Thanks in advance.
Regards,
Prasad

Hello Michal,
Thanks for your response.
Part of this problem has been solved right now...the http port on the R/3 server is 8002 and not 8000!!
Changing the port solved my problem from XI to R/3.
But the R/3 to XI error persists with the same behaviour. I have checked with BASIS, no firewall exists in between.
I have used the ip add while creating the http conn....do I have to change this elsewhere?
[Thr 6] Wed Jul 23 15:33:25 2008
[Thr 6] *** ERROR => Connection request from (-1/65535/0) to host: <hostname masked>, service: 8002 failed (NIEHOST_UNKNOWN) {
[Thr 6] *** ERROR => IcmJ2EEScheduleFunc: Connection to <hostname masked>:8002 failed - please check host configuration (-8) [
[Thr 13] Wed Jul 23 15:34:13 2008
[Thr 13] *** ERROR => PlugInHandleNetData: client: premature EOS - header not complete in response [http_plg_mt. 2627]

HTTP connection ABAP runtime failed- 404 Error

Hi,
We have just installed a new PI 7.0 system. When we do the cache connectivity test we get the following error:
"HTTP connection to ABAP runtime failed:
Error: 404 Not Found
URL: http://PID:50000/sap/xi/simulation?sap-client=020
User: PIDIRUSER
The port should have be 8000, but it is picking 50000. Can someone tell us where to fix this issue? Your help will be greatly appreciated.
Thanks,
Karma

Hi,
I know you got to set the correct URL and port ,I am not sure but I think URL in SLD and port for IS.
and URL supposed to be something like this http://<host>:<port>/sap/xi/engine?type=entry
please see last two replies in this thread,
Re: unable to get file into output folder
and this might also help you
Error 404 in SXI_Cache ?
regards,
Babu

HTTP connection to ABAP Error

What is this error"HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://dst01pi:8001/sap/xi/simulation?sap-client=100 User: PIDIRUSER" ?

Make sure user PIDIRUSER has role SAP_XI_ID_SERV_USER.
U may try changing your service user password using SAP Note 721548.
Regards,
Prateek

SM59 Error in HTTP connections to ABAP Sytems

Hi All,
My scenario is to connect to XI systems... I need to create a RFC destination (HTTP connections to ABAP Systems) in SM 59 with below details.....
Target host: xyz.abc.com
Service No. : 0000
Prefix path : /sap/xi/engine?type=entry
But SAP GUI is not accepting the character "?" ...
Can any one tell what can be done to avoid this error?

Hi,
it's only a warning -> just press 'Enter' key.
Regards
Patrick

Error: java.sql.SQLException: Internal Error Invalid Connect String

hi,
facing errror while deploying the process
A problem occured while connecting to server "sfhyd1.softforce.com" using port "8888": bpel_getCustomerAccounts_1.0.jar failed to deploy. Exception message is: java.sql.SQLException: Internal Error:Invalid Connect String
at com.collaxa.cube.engine.util.DBUtils.checkIfFatalConnectionError(DBUtils.java:920)
at com.collaxa.cube.ejb.impl.BaseCubeSessionBean.checkIfFatalConnectionError(BaseCubeSessionBean.java:153)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:462)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase(Unknown Source)
at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:319)
at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:341)
at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:376)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.sql.SQLException: Internal Error:Invalid Connect String
at oracle.lite.poljdbc.POLJDBCErrMsg.throwSQLException(Unknown Source)
at oracle.lite.poljdbc.LiteThinJDBCConnection.<init>(Unknown Source)
at oracle.lite.poljdbc.LiteThinJDBCFactory.createConnection(Unknown Source)
at oracle.lite.poljdbc.POLJDBCConnection.<init>(Unknown Source)
at oracle.lite.poljdbc.OracleConnection.<init>(Unknown Source)
at oracle.lite.poljdbc.POLJDBCDriver.connect(Unknown Source)
at oracle.oc4j.sql.DriverDataSource.getConnection(DriverDataSource.java:116)
at oracle.oc4j.sql.DriverDataSource.getConnection(DriverDataSource.java:75)
at oracle.oc4j.sql.DataSourceConnectionPoolDataSource.getPooledConnection(DataSourceConnectionPoolDataSource.java:57)
at oracle.oc4j.sql.xa.EmulatedXADataSource.getXAConnection(EmulatedXADataSource.java:92)
at oracle.oc4j.sql.spi.ManagedConnectionFactoryImpl.createXAConnection(ManagedConnectionFactoryImpl.java:211)
at oracle.oc4j.sql.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:170)
at com.evermind.server.connector.ApplicationConnectionManager.createManagedConnection(ApplicationConnectionManager.java:1398)
at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnectionFromFactory(ConnectionPoolImpl.java:327)
at oracle.j2ee.connector.ConnectionPoolImpl.access$800(ConnectionPoolImpl.java:98)
at oracle.j2ee.connector.ConnectionPoolImpl$FixedWaitPoolingScheme.getManagedConnection(ConnectionPoolImpl.java:1455)
at oracle.j2ee.connector.ConnectionPoolImpl.getManagedConnection(ConnectionPoolImpl.java:785)
at oracle.oc4j.sql.ConnectionPoolImpl.getManagedConnection(ConnectionPoolImpl.java:45)
at com.evermind.server.connector.ApplicationConnectionManager.getConnectionFromPool(ApplicationConnectionManager.java:1596)
at com.evermind.server.connector.ApplicationConnectionManager.acquireConnectionContext(ApplicationConnectionManager.java:1541)
at com.evermind.server.connector.ApplicationConnectionManager.allocateConnection(ApplicationConnectionManager.java:1486)
at oracle.j2ee.connector.OracleConnectionManager.unprivileged_allocateConnection(OracleConnectionManager.java:238)
at oracle.j2ee.connector.OracleConnectionManager.allocateConnection(OracleConnectionManager.java:192)
at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:272)
at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:200)
at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:142)
at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:127)
at com.collaxa.cube.engine.data.ConnectionFactory$ConnectionFactoryImpl.getConnection(ConnectionFactory.java:336)
at com.collaxa.cube.engine.data.ConnectionFactory.getConnection(ConnectionFactory.java:140)
at com.collaxa.cube.engine.adaptors.common.BaseProcessPersistenceAdaptor.storeProcess(BaseProcessPersistenceAdaptor.java:361)
at com.collaxa.cube.engine.adaptors.olite.ProcessPersistenceAdaptor.storeProcess(ProcessPersistenceAdaptor.java:52)
at com.collaxa.cube.engine.data.ProcessPersistenceMgr.storeProcess(ProcessPersistenceMgr.java:76)
at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:937)
at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:792)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:455)
... 45 more

You may possibly modified the oc4j-ra.xml file in the stand-alone directory instead of the file under the OC4J_BPEL directory in midtier.
Currently, we are seeing some issues with the sample in midtier. So you may like to wait for the GA release [ mid May] for trying out this sample.
Otherwise please send a mail to [email protected], you need any early drop of this sample.
HTH.
Thanks,
Rakesh

Load balance for HTTP Connection to ABAP System (Type H) RFC connection

Experts,
For proxy we are using HTTP Connection to ABAP System (Connection type H) RFC connection in PI to get connected to ECC. I only see the option to use Target host in the Target system settings than Load balance option. In general ABAP Connection (Connection type 3) has Load balancing status option in Target system settings.
My requirement is I should use a logon group with the message server when PI connects to ECC. How can we achieve this? At the moment I can only use the Central Instance or any dialog server (App server) in RFC but not a logon group.
Thanks in advance.
Mahesh

Hi Naga
Could you check the link below?
http://help.sap.com/saphelp_nwmobile71/helpdata/en/47/c5935087b62d66e10000000a42189c/content.htm
https://service.sap.com/sap/support/notes/1040325

HTTP Connection to ABAP System - Query String Not Allowed message

Hi All,
We are trying to create HTTP Connection to ABAP System on a SAP ECC system.
Following entries are added
1 Connection Type: H
2 Target Host: Host name
3 Service Number: HTTP Port name
4 Path Prefix: /sap/XI/engine/?type=entry
It is not allowing me to enter Path prefix as "/sap/XI/engine/?type=entry". It is throwing a warning message as "Query String Not Allowed message".
As per the documentation it is mentioned that -<b> If the system displays the Query String Not Allowed message, you can ignore it.</b>
It is not allowing me to save the entries succesfully . I need to remove the path refix entry then only i am able to save other wise it is not allowing me to proceed at all.
Please let me know what entry i can put for the same or let me know how can i ignore and proceed by saving the path prefix as "/sap/XI/engine/?type=entry".
Please provide your valuable help on this.
Regards,
Nanda

Hi Aamir ,
Thanks for the response.
Tried both but still same issue .
Any more inputs .
Cheers,
Nanda

Http connection to ABAP problem

Hey Gurus,
I have a problem with the configuration of a http connection to an ABAP system (type H ). Due to the PI Development Book I shall set up a connection called "XI_Integrationserver".
The target host is: saptest8 , port 50000.
The path prefix is: /sap/xi/engine/?type=entry
client
user: PIAPPLUSER
When I test the connection I get an 404 (Not found) error. But it should be an 500 (internal server error). In transaction SICF the engine is started. I don't know how to solve this problem. Please help me!
I'm using PI 7.01!!!
Thanks for any reply.

Hi,
the name does not matter, but "XI_Integrationserver" is missleading because the target is an application system, better would be "INTEGR_ENG_SAPTEST8"
Assumedly the port is wrong. Did you put the port of the ABAP WAS? Transaction SMICM / GoTo / Services
Regards,
Udo

E recruitment Internal error( Rabax_state) in webdynpro abap services

Hi all,
We are facing an error as shown below in our webdynpro services for E recruitment release 604 level 0006 and Ecc 6.0 , all customizations has been done , trex already installed and running properly but many of services throwing this error as below . I have searched extensively on sdn but not found the solution , tried debugg dump in st22, pls guide me , i am stuck up in between due to this error.
Error when processing your request
What has happened?
The URL http://kbldev.kbl.co.in:8000/sap/bc/webdynpro/sap/hrrcf_a_candidate_profile_int was not called due to an error.
Note
The following error text was processed in the system DEV : Internal Error
The error occurred on the application server kbldev_DEV_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: REPORT_MESSAGE of program CL_WDR_MESSAGE_MANAGER========CP
Method: IF_WD_MESSAGE_MANAGER~REPORT_T100_MESSAGE of program CL_WDR_MESSAGE_MANAGER========CP
Method: INITIALIZE of program /1BCWDY/6N9NUEU3ADS9XG9U4DTI==CP
Method: WDDOINIT of program /1BCWDY/6N9NUEU3ADS9XG9U4DTI==CP
Method: IF_WDR_COMPONENT_DELEGATE~WD_DO_INIT of program /1BCWDY/6N9NUEU3ADS9XG9U4DTI==CP
Method: DO_INIT of program CL_WDR_DELEGATING_COMPONENT===CP
Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP
Method: INIT_CONTROLLER of program CL_WDR_COMPONENT==============CP
Method: INIT of program CL_WDR_CONTROLLER=============CP
Method: INIT of program CL_WDR_CLIENT_COMPONENT=======CP
Regards,
Shwetang

Hi,
such errors can have quite a number of reasons. As a first step I'd head for the sap-load-generator (T-Code SGEN) and run it over the complete system and after it over all web dynpro applications. When everything is finished invalidated the http server caches e.g. by usung T-Code smicm.
If this is not successful please give us a nother post.
Kind regards
Roman

PI internal error : HTTP connection to ABAP Runtime failed

Similar Messages

Maybe you are looking for