getting error through testing from services registry

[Former Member]

Dear All,

I have done development of soap--to--proxy scenario and moved it to production.When i tried to test the wsdl after published into services registry am getting an error...i couldn't find what the exact prob..

Web service returned error. Fault Code:
"(http://schemas.xmlsoap.org/soap/envelope/)Server" Fault String: "Server
Error"

Error Log

<?xml version="1.0" encoding="utf-8"?>

<!-- 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.adapter.soap.web.SOAPHandlerException ["adapter inactive"]

at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:533)

at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470)

Any one can you please provide u r valuable inputs on this.....????

thanks in advance

Thanks

Kumar

[Former Member · Accepted solution]

Hi all,

thanks to all who replied to solve this...

thanks to Glowacki,Baskar,Sukarna,Raja

server restart solved the issue

thanks to all....

[rajasekhar_reddy14]

I strongly beleive that your request test data was wrong..

[Former Member]

Hi everyone,

thanks for all u r inputs....

As you told i checked and couldnt find anything,I have attached screenshot please correct me if am wrong.To test from xmlspy and soapui client network not allowed.proxya authentication error.i cannot test it.

@Chirumamilla Sukarna

Please see the attached screenshots

@Raja sekhar

i tried all inputs empty and correct format.my correct request is

*0016111300 000000000020101202281307231308210000300 1 000008650002623 0000000000000000000000800L#

still the same error.

Thanks

Kumar

[Former Member]

[rajasekhar_reddy14]

Hi Kumar,

I dont see any error in SOAP adapter and your request data.

The problem is your receiver system not sending response, did you found any entry in MONI..?/ can you please copy paste here.

Regards,

Raj

[Former Member]

Hi Kumar,

can you post the rest of the message, I am working with WS recently and the message that I see here is same for all the adapter errors, in my case we faced issues with the XML Validation (like wrong data type sent or length issues) and we got errors with details below like this.

Thanks...

Karna...

[baskar_gopalakrishnan2]

There are two places you can set the adapter inactive. One in the integration builder where we create communication channel. Other place is go RWB, look for component monitoring and check your communication channel sender adapter. See whether someone set inactive over there. If so enable it.

[former_member184681]

Hi,

As far as I remember, when the channel is stopped in Communication Channel Monitoring, the error that PI raises says something like "channel stopped". This error suggest something more like Inactive setting in Integration Directory.

Regards,

Greg

[Former Member]

Hi thanks for the quick replys....

@Grzegorz ,Baskar

In integration directory it's in active and in RWB also active.channel running.when i send req from WS Navigator channel status changing from green to red.

SOAP: channel setup successfully

request received for a channel

the above two messages only i can see in the comm channel monitoring.

Thanks

kumar

[baskar_gopalakrishnan2]

Can you check in adapter engine and tell what  do you see the error?  Also you see request received for a channel as message, I want to see whether any problem in the processing steps. If possible, test with external tool like soapui or xmlspy and see what do you see inside pi.

[former_member184681]

Hi Kumar,

Most probably your sender SOAP Communication channel is set as Inactive (in the Advanced tab page). Change the setting to Active, save and activate to get the scenario working fine.

Regards,

Greg