Communication error at synchronous interfaces.

Hello experts.
I have some synchronous interfaces and the scenario bellow can occur:
When a Source system start a process, and the target(ECC) system execute the process whit sucess, but at the moment that they try to delivery the answer have a problem(connection problem for example). My question is, have some way to guarantee that the message will be delivered, even whether the problem be a infrastructure problem?
Thanks

>My question is, have some way to guarantee that the message will be delivered, even whether the problem be a infrastructure problem?
Depends on the context and where the connectivity fails. If the synch message already reached target system and say your proxy is processing it and during that time ECC does not respond then it is a failure. User would get only system error mesg as response.  But ofcourse you can pretty much find the problem using log where it failed. Whereas if your scenario is not best effort then PI can retry the same mesg few times default. Hope that helps.  So mesg will not be delivered if there is a infrastructure problem for synchronous mostly.

Similar Messages

  • Idoc Processing Error - Communication error calling XI interface

    Hi All, We in the middle of our upgrade from IS-PS-CA 472 to ECC6 and are facing issues processing old Idoc's with status 64 via BD87 the error message says that "Communication error calling XI interface". We have not implemented XI at this point in time.
    Can anyone please advice why this is happen is this something to do the SAP version.
    Please help.
    Rgds
    Saj

    Can you provide the message number.
    Reddy

  • CANNOT_READ_PALOAD error with SOAP to PROXY Synchronous interface

    Hi,
       Problem with SOAP to PROXY Synchronous interface.
    In Production client, some times we are getting the below shown error in SXMB_MONI. There is no Inbound payload also.
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Please suggest me to resolve this.
    Thanks in advance,
    Hari.

    Hi Hari,
    In your case, check SAP Notes: 1082111 and  1060723.
    Regards,
    P.Rajesh

  • Increase in wait time of synchronous interface

    I am working on HTTP to proxy synchronous interface on PI 7.3
    PI uses communication channel with SOAP receiver adapter over XI protocol
    Now I am facing below error in the interface while testing after 3minutes-
          com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message (INBOUND)expired
    Can anyone please tell me how can I increase wait time in the channel.
    I have tried adding the parameter name 'XMBWS.Timeout' and parameter value '30000' to increase wait time to 5minutes. But it didnot work.

    Shwetha,
    Set property of Service "XPI Adapter:
    XI" within SAP NetWeaver Administrator -->xiadapter.inbound.timeout.default ---180000ms--(3 min)
    Executing the below mentioned steps
    1.(PI 7.3)
    Goto NWA(PI 7.3)-->configuration-->Infrastructure-->Java System Properties-->goto Services tab-->find xiadapter--> u can increase value inbound.timeout.default
    see the below screenshot :
    2.
    PI 7.0 & 7.1x
    Please check point no 2.2.7 of the below doc:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?QuickLink=index&overridelayout=true&44478681512917
    Mutti

  • Communication Error with HP 8600 Fax

    I have a LENOVO_PN_90BG0003US running Windows 8.1 with a 64-bit operating system.  I have installed an HP Officejet Pro 8600 Plus All-In-One Scanner/Printer/Fax.  I am able to print and scan, but cannot setup the digital fax.  I get a communication errors that states "There is a problem communicating with the printer".  I have troubleshooted through HP without any luck.  The printer is online and I have no issues printing or scanning.  I am able to digitally fax from two other systems that are also running Windows 8.1.  I have also disabled the anti-virus and firewall, and this did not help.  Any assistance would be greatly appreciated.
    Thank you,
    Bob

    And on HP Photosmart C7280 All-In-One.
    I've got mine connected to the network on Ethernet - figured that would be less problematic than wifi - and my MacPro can see everything about the printer, just not print to it. This includes the C7280's built-in webserver which - like alot of SOHO routers - gives you a web-based interface to the printer's configuration and status. Everything on that page looks right-on, but no printing.
    The printer's copy and fax functions work, and I can even scan images and save them across the network onto my machine, so the printer is already interoperating with the network to a high degree, just not printing.
    Like alot of people, I bypassed the HP driver CD and downloaded a fresh software package yesterday from HP's site (200MB+, ***?), which is what I used to configure my system. As far as I could tell, there appear to be no firmware updates available for this printer. MacOS "Software Update" doesn't offer any printer driver updates - I'll try the posted link to Apple's site next.

  • Sender JDBC Adapter and Synchronous Interfaces

    Hello
    I have a Oracle/JDBC -> XI -> ECC/RFC scenario. The communication mode is Synchronous.
    In the Oracle database I have a table with a "STATUS" field.  When JDBC Adapter Sends the rows from this table to the Integration Engine, it updates the "STATUS" from "G" (GENERATED) to "R" (READ).
    The response from the RFC contains for each row sent to RFC a "STATUS_from_RFC" field, that I would like to use to update Oracle STATUS field to "S" (SUCCESS) or "E" (ERROR).
    Can the Sender JDBC Adapter use the response from the Synchronous RFC to update Oracle "STATUS" field itself ?
    Or do I need a Receiver JDBC Adapter? In this case, I have to use asynchronous communication and BPM, ok ?
    thanks
    Julio

    Bhavesh,
    <i>>>>But, the online help states it supports QOS of BE and so it does support Synchronous Processing.</i>
    Even File adapter has QOS of BE
    To my understanding response back is possible only if it is PUSH + Sync
    Adapters PUSH + Sync
    HTTP
    SOAP
    RFC
    XI
    etc...
    For the above response is possible
    Adapter PULL + Sync
    File
    JDBC
    etc..
    In general there can be a response if there is a request. In the case of File and JDBC there is no request message coming to the adapter, its the adapter which is actually requesting.
    This is just an idea and my understanding.. might not be true If possible do try it and let everyone know I will also give it a try when time permits
    Thanks,
    Prakash

  • BPE_adapter The process does not support the given synchronous interface

    We are using PI 7.0 Sp 14 .
    Old dev box needed to be upgrade with 64 bit hardware. We did a fresh installation and done all the technical configuraiton. Imported SLD , IR,ID , Runtime value mapping . All scenario working fine after migration except one particular scenari which involves SOAP Web service .
    Our scenario is Extern system send SOAP call to PI  - BPM_SYNC_ASYnc_process --> BPM Proxy_send 
    this BPM proxy_send   to ECC R/eceiver at R/3
    We are getting the following error after migraiton. Please help
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Call Adapter
    -->
    Error! Hyperlink reference not valid. <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="BPE_ADAPTER">SYNCHONOUS_MESSAGE</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>The process does not support the given synchronous interface or does not support synchronous messages</SAP:Stack>
    <SAP:Retry>N</SAP:Retry>
    </SAP:Error>

    Is there any other Configuration to be done at the Abap side part from BPE_XI_customising (Automatic customising) done as part of the post installation steps .
    Wondering any other configuration needs to be done at the ABAP side (as BPE is running on the ABAp stack) to resolve this.
    Thanks

  • How to exclude synchronous interfaces from component based message alerting

    Hi Pi experts,
    We are configuiring Alerts in PI 7.3 single stack.If we have 'n'number of interfaces, and if we configured general alerts for all.How to exclude synchronous interfaces in that.Alerting is for asynchronous interfaces only.How to do that.
    Please advice on this.
    Regards
    Suneel

    Hello,
    >>What are your approaches regarding this requirement in the context of java-only?
    I would suggest you to schedule jobs like this:
    Customize Alerts Using Job in PI 7.31/PO
    >> alerts are consumed according to the given interval and not in "real time" when error occurs, today solution using BADI is "real time" - if possible I would prefer "real time" solution
    Check this:
    Michal's PI tips: How to trigger an alert for Component Based Message Alerts (CBMA) via "API" ?
    >>an separate service determine the actual alert count would be helpful to provide the correct value for maxAlerts, this have to be called beforehand
    I haven't tried it but i think u can do that, since these consumers are nothing but JMS queues only so i think there will be a method to read number of alert counts.
    >>In history I saw emails generated by the standard alert consumer which only contain details for the first alert, in my case I need details especially the message id for all errorneous messages
    If ur max alert parameter is greater than 1 then u should see multiple alert text  (along with message id and other details) in ur email message.
    Thanks
    Amit Srivastava

  • AS2: Synchronous MDN request but no synchronous interface possible?

    Hello,
    in our AS2 scenario with the Seeburger Adapter we request the MDN synchronously and we also would like to use a synchronous interface for this.
    But obvisouly this is not possible as you have to create a separate sender communication channel for reports and a sender agreement (where I have to use an outbound or abs interface).
    Is there really no way to use a synchronous interface for that scenario as we need to get the response back synchronously for handling in integration server.
    Thank you for your advice!

    So basically my idea was to use a synchronous send step in the integration process and then call a proxy when we have received the MDN.
    Even when you use sync MDN with report protocol, you can send message to Integration Engine and process further. You should be able to use this message in BPM also and then it could be sent to receiver proxy.
    the SAP sender wants to be notified in case there was a transmission problem and this can only be handled automatically with a synchronous interface.
    If you are already using BPM in your scenario, then use of sync scenario is no longer a limitation. You can try correlating the MDN with the AS2 request message.
    Regards,
    Prateek

  • Communication error with the LOCAL_EXEC Function BAPI_PTMGREXTATTABS_CHECK

    Hello,
    We use timesheet (CATS) in a separate SAP system from the SAP system in which HR resides.
    I found out how the loosely coupled scenario with CATS works with a SAP HR system. We transfer the workschedule and absence data with report RPTIMEOVERVIEW_REPLICATE to the SAP system in which CATS is used. This data is then available in the PTIMEOV1 table to perform time checks in CATS. The distribution model for ALE takes care of the fact that the data is posted into table PTIMEOV1. With BD97 I set up that the BAPI: PTMGREXTATTABS.CHECK has RFCdestination for synchronous calls  = LOCAL_EXEC.
    When I want to record on an attendance code without clock times then the above works fine. The SAP system in which CATS resides looks into table PTIMEOV1. So far so good.
    However, when I want to record hours WITH clock times then I cannot save the data. The error message HRTIM00CATS667 shows up:
    "Communication error with the LOCAL_EXEC Function BAPI_PTMGREXTATTABS_CHECK is no t available  system"
    Diagnosis
    An error has occured during communication with the HR System. The HR data in the time sheet cannot be validated.
    From the error message description it seems that it wants to check the SAP HR system instead of looking for the check in the SAP system in which CATS resides.....
    When I change the value from LOCAL_EXEC to the system in which HR resides then the error disappears, but then it really checks into the SAP HR system (synchronous check with that SAP HR system) and that is not what the customer wants. The check should be local on the PTIMEOV1 table (in case the SAP HR system is down).
    I did not find any OSS notes on the topic....or other info on SDN.
    Can anyone help me out concerning this starnge error message, at least for me?
    Thanks very much in advance,
    Kind regards,
    Mirko

    "A point to add"
    I just noticed that following message is being continously receiving in the database alert_log:
    Sat Oct 9 16:04:52 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:05:32 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:06:30 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:07:10 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:09:35 2010
    Incremental checkpoint up to RBA [0x1d.1f9928.0], current log tail at RBA [0x1d.1f9a79.0]
    Sat Oct 9 16:11:52 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:29:40 2010
    Incremental checkpoint up to RBA [0x1d.1f9b87.0], current log tail at RBA [0x1d.1f9bf4.0]
    ~
    Please help.

  • Dynamic receiver determination for synchron interface

    Hello everybody,
    I want to use dynamic receiver determination for a synchron scenario.
    The problem is, that the interface 'ReceiverDetermination' (http://sap.com/xi/XI/System SAP BASIS 7.00) is a asynchron interface.
    This leads to an error when activating the Interface-Mapping (synch source Interface -> asynch destination Interface ReceiverDetermination)
    Is there a way to use the dynamic receiver determination for synchron interface?
    Thanks a lot,
    Thomas

    Hi Thomas,
    I guess your scenario is not possible ASIS, since XI doesn't support 1:n for sync interfaces (and even if your mapping condition reduces it to 1:1, actually it is still 1:n, since your receiver list is unbounded).
    Theoretically, you could make it work with BPM, though.
    But I've never worked with a Receiver Determination Step reading from an enhanced receiver determination in ID (though there should be no problems).
    Use sync async bridge, then use receiver determination step to obtain the receiver from an enhanced Receiver Determination. Pay attention that this enhanced receiver determination is a dummy one, using a mapping from your async abstract interface to the ReceiverDetermination interface. Once your mapping has determined the receiver, the enhanced receiver determination will return that receiver to the Receiver Determination step in the BPM. Then use this receiver in the sync send step (in mode receiver from receiver list, not from context).
    The receiver determination of the actual sync send step may be a standard one, with the several receivers there (even if there are several there, at the moment of the sending, only one will be used).
    Maybe it will work, maybe not.
    Just try it.
    Regards,
    Henrique.

  • RFC Communication - error CPIC return code 020, SAP return code 665

    Hello,
    I have created RFC destination for connecting SCM system from Solution Manager. Both the systems are Unicode.
    I am getting the following error --
    ERROR                service '?' unknown
    LOCATION             SAP-Gateway on host gva4103 / sapgw00
    COMPONENT            NI (network interface)
    COUNTER              4028
    MODULE
    LINE
    RETURN CODE          -3
    SUBRC                    0
    RELEASE              640
    TIME                 Mon Apr 24 11:28:21 2006
    VERSION              37
    And in SM21, I am getting following description
    Communication error, CPIC return code 020, SAP return code 665
    Following are the things I have checked..
    1. RFC destination user checked, password reset in SM59 and in the target system
    2. checked entries in /etc/services - Entry sapgw03 is present.
    Please let me know what all things I need to check.
    Thanks and Regards,
    Vaibhav

    I solved the problem by myself.
    The problem was with the entry in services file only.
    I was checking the file on Target system, which had the entry. There was no entry in Host system services file. After modifying the file, the connection now works fine.
    Thus for RFC connection, entry of the target system gateway MUST be there in /etc/service of Host system.
    Regards,
    Vaibhav

  • Archiving of Soap header part for a synchronous interfaces

    We have a requirement where we have to retain the soap header details for a longer period for tracking purpose. So is there any option of archiving only soap header part from the message for a synchronous interface.
    More Information about the requirement:
    1. We will be passing some parameters to the XI Soap header.
    2. In the WSDL we will add the header fields, so that the end system can populate them.This is done for tracking and searching the message, end to end.
    3.  Another thing to note, is that, for synchronous messages the payload will not be available (without enabling logging), Can we search the messages using the values in the header?
    4. The above process is done, keeping in mind that when the messages are archived, the XI soap header will be the only thing that will be archived and not the whole payload, and the messages that are archived can be searched or retrieved based on the values in the XI Soap header.
    Regards
    Nitya

    Hi,
    Glad to hear that you solve this issue, thanks for your sharing.
    Thanks,
    Linda Li
    Linda Li
    TechNet Community Support

  • Multiple Printer Communication Errors after July Mavericks Upgrade

    Running multiple machines and printers, including:
    - iMac 2014; MacBook Pro 2013; iMac 2011; Tower 2010 / Mavericks
    - HP 8500 / USB and AirPrint / "Communication Error while Scanning"
    - Dymo Twin Turbo / USB / "Printer is Offline"
    - HP 400, HP 2430, Epson 3800 / LAN / No communication errors
    Since latest upgrade, my machines have stopped communicating with these printers. Those machines running Mountain Lion (two older Towers and MacMini) an still print and scan. I have dumped and re-installed all drivers. Have powered-down, disconnected, and reconnected all printers multiple times.
    Can scan to HP using web interface. Dymo is dead in water with anything running Mavericks. Because both the trouble printers are connected USB, I'm thinking that is the smoking gun. Anyone else in the same boat?
    Hoping a patch is in the work. Thanks.

    Haven't heard of that before.
    Before anything else - Apple has changed their print driver paradigm. Manufacturers give current drivers to Apple who have it on their server for automatic download/install when you add the printer in Print & Scan prefs. Since 10.8, you don't normally install drivers (Dymo is probably an exception). HP even includes instructions for this on their web site.
    You need to try some generic maintenance first.
    Reset the Printing System:
    OS X Mavericks: Reset the printing system
    Restart from the Recovery partition (or some other bootable drive), and repair the normal boot drive using Disk Utility:
    (read the 1st paragraph about how to start in Recovery)
    OS X: About OS X Recovery

  • TCS communication error

    Hi gurus,
    i am getting the below error when ever i save in the runtime in CMS
    tail -f defaultTrace.18.trc
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Error connecting to TCS
    DeployServlet: Connection returned with 302
            at com.sap.cms.tcs.client.TCSServletCommunicator.<init>(TCSServletCommunicator.java:66)
            at com.sap.cms.pcs.conf.communicator.TCSConfCommunicator.tcsServletConfiguration(TCSConfCommunicator.java:54)
            ... 42 more
    #1.#00306EF3AC8A00BD000003FF000003FD00043D8811901B6A#1193554526345#com.sap.cms.ui.landconf.LandConfController#sap.com/tc
    wddispwda#com.sap.cms.ui.landconf.LandConfController#NWDI_CMSADM#9457##juepdd_EPD_4284050#NWDI_CMSADM#a5f11f11852111dc
    8bb700306ef3ac8a#SAPEngine_Application_Thread[impl:3]_136##0#0#Error#1#/Applications/CMS#Plain###CMSConfigurationExcepti
    on communication error: Error connecting to TCSDeployServlet: Connection returned with 302#
    #1.#00306EF3AC8A00BD000005F0000003FD00043D8823A48622#1193554829673#com.sap.cms.tcs.client.TCSServletCommunicator#sap.com
    /tcSLCMS~PCS#com.sap.cms.tcs.client.TCSServletCommunicator#NWDI_CMSADM#9457#SAP J2EE Engine JTA Transaction : [0415eff
    ffff920058ffffffc7]#juepdd_EPD_4284050#NWDI_CMSADM#a5f11f11852111dc8bb700306ef3ac8a#SAPEngine_Application_Thread[impl:3]
    _136##0#0#Error#1#/Applications/TCSDeployer#Plain###Error connecting to TCSDeployServlet: Connection returned with 302#
    #1.#00306EF3AC8A00BD000005F3000003FD00043D8824D8C018#1193554849872#com.sap.cms.tcs.client.TCSServletCommunicator#sap.com
    /tcSLCMS~PCS#com.sap.cms.tcs.client.TCSServletCommunicator#NWDI_CMSADM#9457#SAP J2EE Engine JTA Transaction : [0415eff
    ffff920058ffffffc7]#juepdd_EPD_4284050#NWDI_CMSADM#a5f11f11852111dc8bb700306ef3ac8a#SAPEngine_Application_Thread[impl:3]
    _136##0#0#Error#1#/Applications/TCSDeployer#Plain###Error connecting to TCSDeployServlet: Connection returned with 302#
    #1.#00306EF3AC8A00BD000005F5000003FD00043D8824D8F46E#1193554849886#com.sap.cms.pcs.conf.manager.CmsConfManager#sap.com/t
    cSLCMS~PCS#com.sap.cms.pcs.conf.manager.CmsConfManager#NWDI_CMSADM#9457#SAP J2EE Engine JTA Transaction : [0415effffff
    920058ffffffc7]#juepdd_EPD_4284050#NWDI_CMSADM#a5f11f11852111dc8bb700306ef3ac8a#SAPEngine_Application_Thread[impl:3]_136
    ##0#0#Error#1#/Applications/CMS/PCS#Plain###Edit track (EPD/XSSTRKID) configuration failed#
    #1.#00306EF3AC8A00BD000005F6000003FD00043D8824D967BE#1193554849908#com.sap.engine.services.ejb#sap.com/tcwddispwda#com
    .sap.engine.services.ejb#NWDI_CMSADM#9457##juepdd_EPD_4284050#NWDI_CMSADM#a5f11f11852111dc8bb700306ef3ac8a#SAPEngine_App
    lication_Thread[impl:3]_136##0#0#Error##Java###
    [EXCEPTION]
    #1#com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method editTrackConfiguration.
            at com.sap.cms.pcs.conf.manager.proxy.LocalCmsConfProxyLocalObjectImpl0_0.editTrackConfiguration(LocalCmsConfPro
    xyLocalObjectImpl0_0.java:2143)
            at com.sap.cms.ui.landconf.LandConfController.editTrack(LandConfController.java:2937)
            at com.sap.cms.ui.landconf.wdp.InternalLandConfController.editTrack(InternalLandConfController.java:1310)
            at com.sap.cms.ui.landconf.LandConfController.decideSaveOrEdit(LandConfController.java:5186)
            at com.sap.cms.ui.landconf.wdp.InternalLandConfController.decideSaveOrEdit(InternalLandConfController.java:1378)
            at com.sap.cms.ui.landconf.SingleTrack.saveWithoutRestore(SingleTrack.java:2240)
            at com.sap.cms.ui.landconf.wdp.InternalSingleTrack.wdInvokeEventHandler(InternalSingleTrack.java:1996)
            at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
            at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
            at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
            at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
            at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
            at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
            at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:
    759)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
            at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
            at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
            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:387)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
            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(ApplicationS
    essionMessageListener.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)
    Caused by: com.sap.cms.util.exception.conf.CMSCTCSCommunicationException: communication error: Error connecting to TCSDe
    ployServlet: Connection returned with 302
            at com.sap.cms.pcs.conf.communicator.TCSConfCommunicator.tcsServletConfiguration(TCSConfCommunicator.java:58)
            at com.sap.cms.pcs.conf.core.services.SystemManagerObject.saveSystem(SystemManagerObject.java:281)
            at com.sap.cms.pcs.conf.core.plugin.DefaultTrack.newTrack(DefaultTrack.java:177)
            at com.sap.cms.pcs.conf.core.TrackManager.editTrack(TrackManager.java:139)
            at com.sap.cms.pcs.conf.manager.CmsConfManager.editTrackConfiguration(CmsConfManager.java:792)
            at com.sap.cms.pcs.conf.manager.proxy.CmsConfProxyBean.editTrackConfiguration(CmsConfProxyBean.java:289)
            at com.sap.cms.pcs.conf.manager.proxy.LocalCmsConfProxyLocalObjectImpl0_0.editTrackConfiguration(LocalCmsConfPro
    xyLocalObjectImpl0_0.java:2092)
            ... 36 more
    Caused by: com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Error connecting to TCS
    DeployServlet: Connection returned with 302
            at com.sap.cms.tcs.client.TCSServletCommunicator.<init>(TCSServletCommunicator.java:66)
            at com.sap.cms.pcs.conf.communicator.TCSConfCommunicator.tcsServletConfiguration(TCSConfCommunicator.java:54)
            ... 42 more
    com.sap.cms.util.exception.conf.CMSCTCSCommunicationException: communication error: Error connecting to TCSDeployServlet
    : Connection returned with 302
            at com.sap.cms.pcs.conf.communicator.TCSConfCommunicator.tcsServletConfiguration(TCSConfCommunicator.java:58)
            at com.sap.cms.pcs.conf.core.services.SystemManagerObject.saveSystem(SystemManagerObject.java:281)
            at com.sap.cms.pcs.conf.core.plugin.DefaultTrack.newTrack(DefaultTrack.java:177)
            at com.sap.cms.pcs.conf.core.TrackManager.editTrack(TrackManager.java:139)
            at com.sap.cms.pcs.conf.manager.CmsConfManager.editTrackConfiguration(CmsConfManager.java:792)
            at com.sap.cms.pcs.conf.manager.proxy.CmsConfProxyBean.editTrackConfiguration(CmsConfProxyBean.java:289)
            at com.sap.cms.pcs.conf.manager.proxy.LocalCmsConfProxyLocalObjectImpl0_0.editTrackConfiguration(LocalCmsConfPro
    xyLocalObjectImpl0_0.java:2092)
            at com.sap.cms.ui.landconf.LandConfController.editTrack(LandConfController.java:2937)
            at com.sap.cms.ui.landconf.wdp.InternalLandConfController.editTrack(InternalLandConfController.java:1310)
            at com.sap.cms.ui.landconf.LandConfController.decideSaveOrEdit(LandConfController.java:5186)
            at com.sap.cms.ui.landconf.wdp.InternalLandConfController.decideSaveOrEdit(InternalLandConfController.java:1378)
            at com.sap.cms.ui.landconf.SingleTrack.saveWithoutRestore(SingleTrack.java:2240)
            at com.sap.cms.ui.landconf.wdp.InternalSingleTrack.wdInvokeEventHandler(InternalSingleTrack.java:1996)
            at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
            at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
            at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
            at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
            at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
            at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
            at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:
    759)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
            at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
            at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
            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:387)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
            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(ApplicationS
    essionMessageListener.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)
    Caused by: com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Error connecting to TCS
    DeployServlet: Connection returned with 302
            at com.sap.cms.tcs.client.TCSServletCommunicator.<init>(TCSServletCommunicator.java:66)
            at com.sap.cms.pcs.conf.communicator.TCSConfCommunicator.tcsServletConfiguration(TCSConfCommunicator.java:54)
            ... 42 more
    #1.#00306EF3AC8A00BD000005F8000003FD00043D8824D96D51#1193554849917#com.sap.cms.ui.landconf.LandConfController#sap.com/tc
    wddispwda#com.sap.cms.ui.landconf.LandConfController#NWDI_CMSADM#9457##juepdd_EPD_4284050#NWDI_CMSADM#a5f11f11852111dc
    8bb700306ef3ac8a#SAPEngine_Application_Thread[impl:3]_136##0#0#Error#1#/Applications/CMS#Plain###CMSConfigurationExcepti
    on communication error: Error connecting to TCSDeployServlet: Connection returned with 302#
    please help me on this issue
    thanks
    Kishore

    Hi Shikhil,
    i restarted the NWDI still the same error
    thanks and regards,
    Kishore

Maybe you are looking for

  • Async RFC to file -data not passsed to PI

    Hi all, Im facing a peculiar problem in Async RFC to File scenario. I have done all the required configurations for it. Referred the following blogs : /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous /people/michal.kraw

  • Pricing Procedure for Nepal with Excise in it for Export Orders

    Dear Team, I have an export Order For nepal with Pricing procedure (let us say X for all other countries other than India and there is no excise in it) but if i bill a Nepal customer i'm Liable to pay excise as it is applicable for Nepal only . How c

  • Problem moving CS5 to new computer

    I am trying to move my CS5 to my new laptop. The original media was on discs, and the new computer does not have a disc drive. I downloaded the direct download from the Adobe site, but it does not accept the original serial number. Does this have any

  • Installing Photoshop CS1 on Vista, cant even read disk

    I just got a Vista machine and have installed all my CS3 stuff, MS Office, and other various things with no problems. When I got to Photoshop CS1, It doesnt even autostart. When I click on the drive, it says to insert a CD and ejects the tray. Is thi

  • Changing a standard SAP transaction - FB03

    Hi, I am calling the standard transaction FB03 in my program. In this program, after a document's details are displayed, when I click on the line items details, the line items are shown in changeable mode. The change-display button is also there. I w