SOAP - channel started but inactive

Hi experts..
while testing Scenario using SOAP adapter. in RWB -
> adpapter monitaring . here all the adapters in gery status , when i check in communicational chanel monitaring iam seeing error "channel started but inactive "
but i cheked all adapeters in IR ID and refreshed the cashes, and tested the proxy also evrthing is ok.
even i run the scenarion why the adpter status is not changed from yello to green?
i chek the notes 809420, 764176 but i didnt understand what is causing this issue?
note : previously all the scenarios are implemeted in SP6 , now iam working on SP16 , iam wondering in my current system all the adapters in grey color even othe scenarios excuted sucessfully also.
please suggest me ?
thanks
vasavi

Hi sheshagiri
i run the proxy iam able to see the below error in
outbound processing----
> payload after service
ADDRESSVALIDATERESPONSE>
- <RESPONSE>
- <TRANSACTIONREFERENCE>
<CUSTOMERCONTEXT>Local mode using Progistics XML Processor</CUSTOMERCONTEXT>
<XPCIVERSION>6.1.9</XPCIVERSION>
</TRANSACTIONREFERENCE>
<RESPONSESTATUSCODE>609</RESPONSESTATUSCODE>
<RESPONSESTATUSDESCRIPTION>Unable to process request</RESPONSESTATUSDESCRIPTION>
- <RESPONSEERROR>
<ERRORSEVERITY>Fatal</ERRORSEVERITY>
<ERRORCODE>2441</ERRORCODE>
<ERRORDESCRIPTION>Invalid Login ID. Verify Login ID with System Administrator. I7A9</ERRORDESCRIPTION>
<MINIMUMRETRYSECONDS>N/A</MINIMUMRETRYSECONDS>
- <ERRORLOCATION>
<ERRORLOCATIONELEMENTNAME>LOGINID/FOLDER</ERRORLOCATIONELEMENTNAME>
<ERRORLOCATIONELEMENTREFERENCE>n/a</ERRORLOCATIONELEMENTREFERENCE>
<ERRORLOCATIONATTRIBUTENAME>N/A</ERRORLOCATIONATTRIBUTENAME>
</ERRORLOCATION>
<ERRORDIGEST>N/A</ERRORDIGEST>
</RESPONSEERROR>
</RESPONSE>
</ADDRESSVALIDATERESPONSE>
please suggest me

Similar Messages

"Channel started but inactive" in RWB Monitor for SOAP sender channel

Dear XI specialists,
I have configured a communication scenario involving SOAP Adapter (sender) usage, but I'm facing the issue when testing the scenario. The problem is that none of messages are coming into the SOAP Adapter (checked via TCode SXI_MONITOR in XI) when using 3rd party SOAP-clients (XML Spy, soapUI) based on WSDL-file generated and exported from XI.
I checked the sender communication channel for SOAP Adapter - it is activated in Integration Builder's Directory. SOAP Adapter itself is also started.
I checked Runtime Workbench monitors and in the Communication Channels Monitor of the Components Monitor received the warning saying "Channel started but inactive" for my configured channel as well as for other channels working on SOAP Adapter.
Activities which were performed (in the order in which they were performed and results tested):
1. the configuration channel restart;
2. the communication channel re-activation and further re-start;
3. SOAP Adapter restart;
4. XI system's Java instance restart.
All mentioned activities didn't give any positive effect in part of this issue resolution.
On the other hand, if I use test message functionality of the Runtime Workbench (Component Monitor), then messages are seen in SXI_MONITOR and expected response messages are also returned to XI from integrated business system.
Would you please advise what can be checked else here and where the root of the problem may be detected?
All your answers and feedback will be greatly appreciated and awarded accordingly.
Many thanks in advance and my regards,
Vadim

Dear all,
Thank you for your input! Unfortunately, the problem still exists after testings and checkings which you suggested.
TO Seshagiri:
I checked message monitor and found only several messages for the required sender/receiver services pair in the used namespace - all of them were successfully processed (these are messages which I sent by means of RWB Component Monitor's test message functionality).
TO Sarvesh:
Yes, sender agreement is configured properly. I configured it when configuring communication scenario in the Configuration Wizard and then manually re-checked its definition. Moreover, when performing Test Configuration in ID, I received positive results.
TO Nallam Guna:
I cleared Data Cache in Integration Builder, but this didn't help.
TO Gujjeti:
I'm on SAP NetWeaver 2004s PI 7.0. Service Pack level for PI is 13.
TO Durga:
Thank you for provided links! I have already had a look at them - but proposed solutions doesn't seem to be working in my situation.
Thank you all once again for your prompt answers! I really appreciate your attempts in helping me!
I would appreciate if you could share any further ideas on this issue.
My best regards,
Vadim

SOAP Adapter: Channel started but inactive

Our system is XI 3.0 running on Solaris 10 zoning and Oracle 9i. All on Support Package 17.
When consulting the status of the adapter in the RWB environment we are receiving the message above "Channel started but inactive".
How can We solve this problem?

hi,
SOAP adater will be green when you process the first message via this adapter
Regards,
michal

SOAP adapter - Channel started but inactive (case inside)

Good day everyone!
I have integration scenario IDOC->XI->SOAP. I did all setting and created SOAP adapter with 2 parametrs: "Target URL" and "SOAP Action".
But when I look at Channel Monitoring I see my SOAP-channel with status "Channel started but inactive" ??
What could it be?
Thanks in advance!

hi,
this issue is too common. i face it i some of my channels. there no error.
test your scenario. im sure it will work but the adapter still has been in yellow at least it fails and turn red.
I have some CC in red status and working fine. later few minutes it turn green.
don worry about it. if you leave it working it will turn green later. if u restart the java stack you can solve it but i dont recommend it because this error could appear in other adaprter too.
commonly it appear when you start and stop the channel from RWB.
Hope Helps
thanks
Rodrigo.

SOAP Adapter status stay "Channel started but inactive"

Hi, Folks:
We have a couple of SOAP adapters that I have not used for a while, so I put them in inactive status.
Now we need to switch SOAP Scenario, I activate them, however, in Communication Monitoring Page, The status is Yellow Triangle: "Channel started but inactive"
I have tried to inactivate and reactivate them for a couple of times, it does not help.
Any ideas are welcomed !
Liang

Hi Guys
As suggested by you guys, after I sent first message, all the SOAP adapter get active now. I believe I fogort how I setup it up initially. That is the value stay with your guy
Thanks everyone !
Liang
Edited by: Liang Ji on Feb 29, 2008 8:48 PM

Yellow LED: Channel started but inactive from CC monitoring

Hi
We are trying SOAP to SOAP scenario, we done with all IR and ID part deployment and Activated the all the Objects ,
But still In CC monitoring both channels showing Yellow LED: Channel started but inactive
In omponent Monitoring Adapter Engine also showing Yellow LED
We tried with SXI_CACHE and CAP cache refresh also...
Help me out to solving this issue..
Thanks
Vadde

Hi Vishwanadh,
We have faced the same issue for the past two days and the sam has got resolved automatically while testing the scenario. So please go ahead with your testing, the channel will then be activated automatically.
Before that clear the CPAcache with the user PIISUSER (make sure that the user is having access to SAP_XI_Administrator_J2EE and SAP_XI_Configuratoe_J2EE
Regards,
Varadhu

"Channel started but Inactive" - Issue with JDBC channels

Hi all,
I have 5 channels configured with Oracle which were functioning till yesterday night properly. All of a sudden 3 out of them have decided not to co-operate and they show a status in RWB as "Channel started but Inactive".
The rest two are functioning correctly which is more weird.
I did the following:
1. Complete cache refresh.
2. Delta cache refresh
3. channel was copied with a new name and used and it works but this doesnt make any sense.There has to be a proper way to deal with this situation.
4. All channels are activated in ID.
Has anybody faced similar issues with JDBC or any other type channels?
Regards,
Amol Joshi

Hi Amol,
Usually the channel information is available in the monitor after the service and the channel are activated successfully.
However, in the case of the SOAP adapter, the
adapter status is not available until the first request is sent to the adapter.
For JDBC Adapter try to:
1. Re-configure JDBC parameters, it might happened that it is not able to establish a database connection.
Just re-enter and activate the same.
2.goto to the IR adn ID and run the cache ,you will get the cache objects list in red color check the error details there, make sure the AE cache is up and running fine.
goto to the RWB>cache monitoring or status->check the cache status of the AE and IS, it should be green in color,
run the CPA cache from the URL with the PIDIRUSER ...then again run the cache from IR and ID and check.
Also check :
1.if you have right permission to write the data to the table
2. Check whether that table takes NULL values, if so check what data is being supplied by XI to the receiver end.
*Pls: Reward points if helpful*
Regards,
Jyoti

RWB issue Channel started but inactive

Hi,
In RWB the SOAP adapter is showing status message as"Channel started but inactive" but all the SOAP adapters are active in Directory.
This is happening only in new environment Pre-Production.
Valueable inputs will be appreciated.
Thanks
Santosh

Hi Santosh,
SOAP adapter shows "Channel started but inactive" message when there are no messages processed till now(after activating any changes to comm channel or server is restarted). Once a message is triggered in SOAP adapter, this will go away. Try to trigger a message and see.
Regards,
Sreenivas

What happens if Channel started but inactive?

Hi.
While monitoring the training server, i found there are 100 channels with yellow color status "Channel started but inactive".
All these channels are not SOAP or MAIL channels. Most are FILE, JDBC, JMS channels.
I know that we can stop the channels in RWB but what happens if these channels are kept with that yellow status? If i stop these channels will it improve the performance??
Kindly let me know how it will effect the performance.
Thanks... !
Warm regards,
Praveen.

Hi,
While monitoring the training server, i found there are 100 channels with yellow color status "Channel started but inactive". - It means there was no msg for these channels so they are inactive......when there will be msgs for these channels, then those msgs will be processed by these channels and its status will change to running........
I know that we can stop the channels in RWB but what happens if these channels are kept with that yellow status? - No performance impact because of this inactive channels :).............
If i stop these channels will it improve the performance?? - Do not stop these channels but keep them started..........
Regards,
Rajeev Gupta

Channel Started but inactive

hi all -
i have 2 scenarios - idoc to file which works fine without any problem
in the other scenario - file to file i get this message in the communication channel monitoring for the file sender which says "Channel started but inactive".
I checked the integration directory and made sure that its activ and the change list is activated.
I also checked the sxi_cache and the contents are upto date.
any ideas how to resolve this issue?
Thanks,
Tirumal

Hi,
Try to do the CPACache Refresh.
Also adapter metadata Refresh ( Integration Builder->Admin->Cache Overview)
Also restarting Adapter engine may also help here.
This SAP Note - 764176 (SLD inconsistence )
Regards,
Moorthy

SOAP Sender - RWB "Channel started but inactive"

I have a sender soap channel configured. In Integration Directory the Adapter Status is active. However when I go to Runtime Workbench and view the channel it says the "Channel is started but inactive". Can someone explain to me why it is not active in Runtime Workbench?
Also, SOAP messages sent to this channel are failing obviously because the channel is inactive. How can I make this channel active so that XI can receive SOAP requests.

hi rodel,
You have to process one message at least to make SOAP adapter Active
refer this discussion
how can i enable SOAP Adapter?
regards
Ramesh P

ON RWB - CC Monitoring - SOAP Channel. status says "inactive or unregister

Hi,
I am working on SOAP Webservices.
My Scenario is working fine ... But Some How on RWB - CC Monitoring - SOAP Channel. status says "inactive or unregistered".
On the otherside , my SOAP Scenario is working fine...
But why for that status " "inactive or unregistered"." , I dont Know?
Please Suggest, How to Deal with this ........?
I executed transaction code " se38 - > SRT_ADMIN_CHECK report "
It states me almost every thing unregistered/ inactive/ not configured except ICM Services ..
are these services shoud active and registered for SOAP Scenario?
how to activate them .............????????
That CC status " "inactive or unregistered" has anything to do with this SRT_ADMIN_CHECK report????
Regards
Prabhat Sharma.

Hi
This is the problem which i recently faced and solved.
Cause: Saop related J2EE application are stoped or not set to default start as initial state.This is also a reason
             for 503 service unavailable error while soap posting.
Solution : start the J2EE app , com.sap.aii.adapter.soap.app & com.sap.aii.adapter.soap.lib set them as defualt started
               as initial state.
Where : If you are in PI 7.1 , http:<host>:<port>/nwa->Operations Management -> Systems -> Start & Stop -> Java EE
               Applications.
                Refer http://wiki.sdn.sap.com/wiki/display/XI/start_stop_applications for more help.
               Also in Start button , there will be a dropdown where you can set the default initial state as started.Simply starting may
               cause similar problem ( not registered ????????) again ,so better to set initial as started state.
Regards,
$rinivas

SOAP Sender Adapter remains inactive

I have a Service BS_IMIWH_DEV and an interface DeliveryReceipt_OB, and it is running on our fatfreddy system; the J2EE engine port is 50000.
I have used the Web Service wizard to generate a WSDL file. I used the following target url:
http://fatfreddy:50000/XISOAPAdapter/MessageServlet?channel=:BS_IMIWH_DEV:SOAP_Out_IMIWH_DELIVERY_RECEIPT_I98
When I paste this address into the web browser, it asks for user id and password (I use PIAPPLUSER which seems to work), then I get the following message:
Message Servlet is in Status OK
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#10 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0
ModuleProcessorRemote not instantiated
Not knowing that much, I assume this is an OK response.
I use Stylus Studio to try to post a web service call using the WSDL I created. When I submit it, and look at the communication channel monitoring for this channel, it sits there with a yellow triangle in the status, and 'Channel started but Inactive' in the short log column. So to me it looks like the SOAP adapter never received the call.
I checked in Stylus Studio to provide the PIAPPLUSER user ID and password to call the web service, but nothing seems to be happening.
Can anybody suggest what to try now?
Kind Regards,
Tony.

I switched from Stylus Studio to XMLSpy and tried to create a Web Service Client call again. This time the channel processed the message but ended up in error:
Attribute Value
Engine Integration Engine
Status Canceled with Errors
Repeatable No
Cancelable No
Start 15.01.2008 19:14:54
End 15.01.2008 19:14:54
Sender Party
Sender Service ED1CLNT110
Sender Interface urn:sap-com:document:sap:idoc:messages
WMMBXY.WMMBID02
Receiver Party
Receiver Service BS_IMIWH_DEV
Receiver Interface urn:acando:imiwh:deliveryreceipt:i98
DeliveryReceipt_OB
Quality of Service Best Effort
Error Category IDOC_ADAPTER
Error Code ATTRIBUTE_BE_NOT_SUPP
Message DCC38D62C70912F1B1FE00199908972A
Reference 635397A0C38D11DCA943001999089729
So I suspect my first problem was my inability to configure Stylus Studio correctly; my second is that there is now something wrong in the conversion of the Web Service call to an IDoc, which is a different problem.
BR,
Tony.

One of the sender SOAP channel is inactive by itself in the CC monitoring

HI All
sender soap channel is showing inactive in the RWB. But when i check the status in Integration directory it is active. It got inactive by itself . can anybody help me how i can activate it.
regards
sandep

Hi Sandeep,
There are two ways to Active or Incative communication channel,
1)Select communication channel in Componnet monitoring and start the communication channel,it will actuvate.if you want inactive stop it.
or
2)Iin Integration Directory select mode as Active it will start.
sometimes it behaves like that...
REgards,
Raj

SOAP Receiver Channel 2 nodes inactive in Production system

Hi All,
We are facing an issue with the SOAP receiver channels in production system. There are 4 nodes which can be seen in the communication channel monitoring and out of which 2 have the status as inactive and the short log says "inactive or never used".
But the same nodes are active on the sender SOAP channel and all other channels.We have also checked the Status of the SOAP service that is also set to active.
Now when the server (App server5 in our case) is switched off, which has the 2 active nodes, the messages are not processed since the nodes on the other server are inactive.
Request you to please help us out in finding out why the nodes are in inactive status only for SOAP receiver channels. Do we need to change any settings at the adapter engine level.
Thank you.
Regards,
Sarvesh Desai
Edited by: Sarvesh Nispat Desai on Aug 25, 2010 5:25 PM

There is an error in reporting the status of SOAP channels. This error has already been fixed by SAP and is available as a fix in higher releases (PI 7.10 and above, latest SPs) .
The status "inactive or never used" is shown in channel monitoring at the following two times:
1. After creating a new SOAP channel (sender/receiver) till this channel processes any new message.
2. After the PI system is restarted, all the SOAP channels show this status, though they are ready to handle any incoming/outgoing messages. The channels continue to display this status till they process any new message.
In both these situations, the SOAP Channel can handle/process messages successfully. So, kindly ignore this channel status ("inactive or never used") reporting error in channel monitoring. This will not at all hamper the normal functioning of the SOAP channels.
Hope this answers your query.

SOAP - channel started but inactive

Similar Messages

Maybe you are looking for