Communication Channel not Processing Successfuly

Dear All,
I am using file adapter at receiver side. i have sent some records from ECC. In MY CChannel Monitoring
Message processing started
but it is not showing successfull prcossing message . i have refersh the cache and refresh the CC Monitoring also. but still it is not showing completion of message. PLZ sugeest.........
Regards'
Abhay

Hi Abahy,
Check your configuration again and see whether you have proper authorizations to the Destination Directory. Also check outbound status in SXMB_MONI for the message.
Also go through the link for File adapter troubleshooting:
[http://wiki.sdn.sap.com/wiki/display/XI/TroubleshootingtheFile+Adapter]
Regards
Rahul

Similar Messages

Error in JMS Communication Channel not raising alert

Processing Errors in JMS Communication Channel are not raising alerts.
The settings on the communication channel retires are set at 3 and 5min interval.
In RWB the JMS communication channel shows processing errors but an alert is not raised.
The alert are configured in our system and we even have a catch all alert rule with * (wildcard). Errors in PI message processing are raising alerts but errors in Comm Channel are not raising alerts.
The message in SXI_MONITOR shows as processed successfully but when we check the RWB and Comm. Channel Monitoring we see processing errors "Channel error occured; detailed error description: JMS error: Connection to the server has been terminated; Linked error: Connection reset, Error Code:null"
Are we missing any configuration? How do we get alerts/notifications if there are errors in Comm. Channel without having to login into RWB and watch it periodically?
Any help is greatly appreciated.
RM

Hi,
What is the staus of Communication channel in RWB when it fails, RED ??if yes then it should genarate alert.
create one more alert for specific to JMS interface and check it out.
Regards,
Raj

JDBC Sender channel not processing the messages

Hello,
From yesterday onwards JDBC Sender channel not processing the messages. In CC monitoring it is showing in Green Led and status is functioning. Cahnnel is polling for messages to DB server as per polling interval. But it is not processing the msg's. Under Processing detials for cluster node it is showing only "Processing Started" for each polling interval.
I have done the check in DB server by executing the query in the channel, whether there are any records are exisitng or not. There are 1000+ records.
Previously the parameter "Disconnect from DB after processing each message" was not set. I have set the parameter and activated in Productiion. Still the messages are not processing by channel
What was the problem? How to rectify with this.
Cheers
Veera

Check in the Visual Admin >Cluster> "LOCKING ADAPTER"
we get a option of Display Locks .Check for an entry with
NAME : $XIDBAD.JDBC2XI
reset the locks and restart the CC ,now it works fine.
Note 1083488 - XI FTP/JDBC sender channel stop polling indefinitely(04/04S)

Mail Sender Communication channel not polling

Dear all,
In our PI 7.1 Sever, we have observed a issue.
Sender mail communication channel status is green in RWB-->Channel monitoring but the channel does not pick up any mails form the mailbox.
After we stop and then start the channel, it is picking up the mails.
Any pointers on the root casue for this issue and any resolution steps or any SAP Notes to implement will be of great help.
Regards,
Younus

Hi,
Is it like everytime you have to restart the mail channel again and again?
Sometimes it happens, a quick restart will refresh the adapter cache and the messages are processed.
So, its not a problem.
Regards,
Sushama

Inactive Sender Communication Channel still processing Files?

We de-activated the Sender Communication Channel of an interface. However, the file adapter keeps processing?
Anybody know what is going on?
Thank-You.

Hi Tom,
1) Check out Whether you have De-activated the Right Adapter.
2) Refresh the Cache,
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
c)Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

PI sender communication channel not reading files from NFS directory

Hello,
I have a sender communication channel configured to read file from NFS directory which is on ECC server. A program in ECC generates the file and puts it on the ECC server in the output directory. PI sender communication channel is supposed to pickup this file and process it. If I give the NFS path as the source directory, I am getting error: Configured source directory '//Server/DIR/OUT' does not exist. I tried putting '
Server\DIR\OUT' too but same error. Do I have to add the NFS path of ECC into PI as logical path?
Any suggestions?
Thanks,
Sangita

Hello Sangita,
Your ECC server is an external system, therefore you need to activate FTP service in that system and use the transport protocol FTP:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
You can use NFS protocol when you have a local directory in XI server.
Best Regards,
.Luis Bernal.

Communication channel not present in Communication channel monitoring

Hi All,
We have the communication channel in Integration builder and it is active state. but we are not able to see it in C.C monitoring. and we are not sure whether the channels are started.
how can we check whether the channels are started?
and why the communication channel is not visible in C.C monitoring.
It works fine in DEV and QA. but we are facing this issue in PRD

Hi Ravi,
in the cache connectivity test, all the components are in GREEN color (Enterprise Service Repository, Integration directory, Integration server - ABAP, , mapping runtime on central adapter engine, adapter engine, mapping runtime) . Only central adapter engine is in yellow color and the message says:
Apr 19, 2010 6:16:28 AM - Cache notification from Integration Directory received successfully
Attempt to fetch cache data from Integration Directory not yet started or still in process.
Restarting the server also did not work.

Communication Channel not getting any adapter

I am getting this error when i goto the ID and refresh the cache, but when i goto the SXI_CACHE it shows me the green light.
Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server>
I am not getting any adapter in Communication Channel also getting java.LangNullPointer Error.
can somebody please help me as quickly as possible.
If possible can somebody please reply me the post installation of XI with complete screen shots.
on muiqbal2008 at gmail dot com

Thanks for the information sarvesh, i won't add the email from next time.
ok i am getting these erros.
1) in ID when i am trying to refresh the Cache.
com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.sapserver, string], target element type: SAP_BusinessSystem)
     at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:488)
     at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:140)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:370)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:294)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:142)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
     at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     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:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.sapserver, string], target element type: SAP_BusinessSystem)
     at com.sap.aii.ib.server.sldquery.SLDQuery.dammiIlMioCentralAdapterFramework(SLDQuery.java:77)
     at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:202)
     at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:140)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:370)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:294)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:142)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
     at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     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:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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(SingleThd.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
2) I am getting this error when i am trying to refresh the cache
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'http://sapserver:50100/CPACache/refresh?mode=full'. L...
CPA cache refresh (mode=full) successfully executed in 2297 milliseconds.
^
Although if i check the cache via SXI_CACHE it shows me the green light.

PI 7.1 RFC Communication Channel not found

Hello,
We have recently upgraded to PI 7.1 and I am having a problem getting my RFC adapter to work. This is the error message:
Error when calling an adapter by using the communication channel CC_UDF_RFC_CALL_TO_PI_ABAP (Party: , Service: IS_D06, Object ID: 5873a160602e3be5866ab820596b752c) The channel with object ID 5873a160602e3be5866ab820596b752c could not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cache
I went to SXI_CACHE and refreshed (Delta nad Complete). I can see that the CC exists in integration builder.
How can I determine what is causing this error?
Thanks,
Matt

Also check the cache notification after activating the Comm channel in ID whether cache is properly updating for the changes in the comm channel.
Menu--> Environment --> Cache Notification
If cache notification is proper thentry to refresh CPA cache using following URL and execute ur scenario.
[http://<host>:<port>/CPACache/refresh?mode=full]
Edited by: Samiullah Qureshi on May 14, 2009 8:36 AM

Error in communication channel " not initialized"

Hi All,
I'm working in FIle to mail scenario. In this scenario whenever i upload a text file to the R/3 application server. that file should be sent (as a attachment with a mail) to any email id. I did all the required configuration in IR. but i'm verymuch confused in ID configuration. I have created both sender and receiver communication channel in the same business system which refers a sender (R/3) System.sender communication channel is working fine. but when i activate the receiver communication channel it shows an error "not initialized".
So kindly let me know,
1. Should i use business system for my receiver end?,If so how do i create it?
2. is receiver agreement, receiver determination, interface mapping necessary? If so, how do i configure it? because i'm not using any recever service since i'm sending mail to my mail box.
note:
It would be very helpful if u refer any link to find out the recever determination and interface determination configuration for this type of scenario.
Thanks & Regards,
hari.

Provide us the XML formed after mapping.
make sure that the msg type name is Mail and the name space name is http://sap.com/xi/XI/Mail/30.
regards
krishna

Sync/Async - JMS receiver comm. channel not processing

I have a Sync/Async scenario (without bpm) in PI 7.11:
RFC -> PI -> JMS
whereby the JMS receiver comm. channel does not fully process the message.
More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
- Message processing started
The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
- Message processing started
(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
14.02.2011 12:50:19 Information Transform: transforming the payload ...
14.02.2011 12:50:19 Information Transform: successfully transformed
14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
14.02.2011 12:50:19 Information ROB: forwarding the request message
14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
wheras the non-success msg shows only:
14.02.2011 12:55:30 Information Transform: transforming the payload ...
14.02.2011 12:55:30 Information Transform: successfully transformed
14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
14.02.2011 12:55:30 Information ROB: forwarding the request message
14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
And also the sxi_monitor shows these messages with a status of "Log version".
Keith

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

Communication channel not listed in RWB

Hi,
I'm facing a strange problem.
Working on File to IDOC scenario. Suddenly my communication channel has stoppped listing in RWB.
It say 0 channel found. Initially it was not so and I was able to monitor my channel.
Any help on this ?
Vikas

Hi Vikas,
-->In the ID deactivate your File sender communication channel and activate it.
-->also refresh the cache.
Thanks

Communication channel not selectable in monitoring

Dear experts,
From SAP 4.6c, I want to send data to XI via RFC adapter. I did the following:
- create an RFC on sap 4.6 with no coding, only parameters;
- import the RFC in the integration repository;
- did the message- and interfacemapping to my outputstructure there;
- configured everything in the integration directory, so comm.channel, send/receiv determination etc.
- on the SAP system, created an abap that fills the parameters for the RFC and calls RFC with destination = XI system.
I created a Sender Comm.channel (from SAP to XI) with adaptertype RFC and set it to Active.
Now, when I look in the Communication Channel Monitoring in the Runtime Workbench, I can not select the CC. I'just does not appear when I press "input help" button. I must e forgetting something but I have no idea what...
Can anybody please help?
Thanks in advance
William

Hi JWD,
Check in your change list whether it is activated or not. If activated you should be able to see.
Regards,
---Satish

Communication channel not visible in RWB

Hello everyone,
I am not able to view the communication channel in RWB. This is a HTTP sender . i have imported it but still it is not visible in RWB. what could be the reason ?
Regards,
Ravi

Hi Ravi,
In PI there are basically two types of adapter, adapter engine based and Integration engine based. Integration engine based adapters are HTTP, XI and IDOC. These adapters can be monitored from ABAP stack means from SXI_MONITOR and adapter engine based can be monitored from RWB. Due to this differentiation you HTTP adatper is not visitble in RWB. But you can monitor it from ABAP stack.
Edited by: Rajhans Abhay on Jan 18, 2012 6:06 AM

Sender JMS Synchronous communication channel not picking up files from JMS

Hello,
One of our Sender JMS synchronous communication channel (used Sync/Async bridge in the module section to make it Synchronous) is not picking up files from JMS system though the channel looks to be active (greeen).
When I am trying to stop the channel, it is giving error as "1 of 1 administered and selected channels have not been stopped", and after this when I start the cannel again it shows green but not picking up any files.
if anyone is haivng any solution for this, please reply back.
Thanks in advance.

Messages available in JMS system? please check queue's if message were there and it is not picking up then some thing wrong with cc.
simple solution create new communication channel with same details and try to use the same.

Communication Channel not Processing Successfuly

Similar Messages

Maybe you are looking for