Page 1 of 1

HTTP Error: Internal error in server

Posted: Mon Sep 27, 2010 2:38 am
by victorgt
Dear All,
I got this message error from XMLSpy when i send request to server.
HTTP error : internal error in server.
Thanks.


<?xml version="1.0"?>
<!-- see the documentation -->
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/NW701_03_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#1 $)
at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
]]></text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Re: HTTP Error: Internal error in server

Posted: Mon Sep 27, 2010 7:33 am
by Baz
what happens when you test in the Integration Directory using the test tool?

or can you test from Web Services Navigator.

Re: HTTP Error: Internal error in server

Posted: Mon Sep 27, 2010 8:48 pm
by victorgt
When i use test configuration in integration directory, the result like this:

Sender Agreement
<Not found>
 <Trace level="1" type="B">SENDER AGREEMENT SIMULATION</Trace>... (5 lines)

Receiver Determination
<Not found>
 Internal Error
HTTP connection to ABAP Runtime failed. Error: Connection refused: connect


And result from wsnavigator is like this :
Cannot download WSDL from http://XXXXXX:50000/XISOAPAdapter/Messa ... nder_Equip: Given http://XXXXXX:50000/XISOAPAdapter/Messa ... nder_Equip is not WSDL definitions file !

Re: HTTP Error: Internal error in server

Posted: Tue Sep 28, 2010 1:31 am
by Baz
and i guess when you look at your proxy connection in RWB it does now work either!

you need to fix your connections between ECC and PI.

run SLDCHECK too. see if that works!

Re: HTTP Error: Internal error in server

Posted: Tue Sep 28, 2010 3:42 am
by victorgt
i have run SLDCHECK in PI
the result is Summary: Connection to SLD works correctly

i run SLDCHECK in ECC

RFC destination SAPSLDAPI does not exist
=> Create the RFC destination by using transaction SM59!

Summary: Connection to SLD does not work
=> Check SLD function and configurations

Now checking access to the XI Profile

RFC destination LCRSAPRFC does not exist
=> Create the RFC destination by using transaction SM59!

Re: HTTP Error: Internal error in server

Posted: Tue Sep 28, 2010 5:49 am
by Baz
to fix that, follow this: https://cw.sdn.sap.com/cw/docs/DOC-29740


p.s. this is linked to your other error! i said check the SM59 connections.....