Error in XI server: JCO_COMMUNICATION_FAILURE in Message Mapping

Hi all,
I am unable to execute even a simple scenario on my server.
The status of the message in moni is random. I get either "Scheduled for outbound processing" in,or the following error(in Request Message Mapping):
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
  <SAP:P1>Error opening an RFC connection.</SAP:P1>
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error opening an RFC connection.</SAP:Stack>
  <SAP:Retry>A</SAP:Retry>
  </SAP:Error>
I tried deleting the queueus in smq1 and smq2.It did not solve the problem.The test connection for INTEGRATION_DIRECTORY_HMI in sm59 is also working properly. But I don't see any entries for t-RFCs in sm58.
Can anyone tell me what could be the problem?
Regards,
Puloma Chaudhuri.

Hi Puloma,
1. go to TCODE: SWEL and check if you have any errors over there
2. go to TCODE: SWF_XI_CUSTOMIZING
- maintaint runtime environment
- configure RFC destination
and check if the password for user WF-BATCH is correct
Regards,
michal

Similar Messages

  • Strange Errors from Import Server on Schema-based maps for repeating nodes

    I have already posted one thread about this, but perhaps some more in-depth information is required:
    We have uploaded our schema into the console, and have mapped the following multi-node file to it:
    CUSTOMER <repeating node>
      MDM_CUST (new Customer number returned)
      CUSTOMER(mapped back from XI for RECORD MATCHING)
      CREATE_DATE (text field)
      CONTACT<repeating node>
        CONTACT_NO (RECORD MATCHING : NON-QUALIFIER)
        CONTACT_SAP_NO (QUALIFIER)
         [NOTE: There are other qualifers for CONTACT, but only this one
    qualifier is being returned and is the only field that would and should be updated.
    The other fields should be left alone. However, it appears to overwrite EVERYthing
    with NULL other than these two fields. The CONTACT_NO is the sole qualifer on
    the table. It is a calculated field that equals the Auto-ID that is also produced on
    the table - but obviously not mapped.]
      PARTNER<repeating node>
        CUSTOMER_NO (RECORD MATCHING : NON-QUALIFER)
        PARTNER_FUNC (NON-QUALIFIER - Code given to lookup from PARTNER_FUNCTION table which has Code and Desc)
        PARTNER_NO     (NON-QUALIFIER)
        DEFAULT_PARTNER_FLAG (QUALIFIER)
    <CLOSE CUSTOMER NODE>
    In the Customer main table, all records are matched on CUSTOMER. The CONTACT_NO non-qualifer is matched to the CONTACT qualified lookup table directly since it is the only available non-qualifier. For the PARTNER table, the three qualifiers are mapped and then a compound field is created to map to the PARTNER table entry.
    We have the Configurations set at:
    Default Multi-Valued Update: Replace
    Default Qualified Update: Replace
    Default Matching Qualifiers: None
    Our record matching is: Create / Update(ALL MAPPED FIELDS) / Update(ALL MAPPED FIELDS)
    When the map is reused, the repeating nodes are all recognized, be it one node or many. However, when the map is reused, it does not automatically map the values for many of the Partner fields (nor the compound field) though the fields are correctly mapped.
    Also, when we attempt to use Import Server to automate the mapping, we use the mdis.ini set to
    Automap Unmapped Value=True
    Unmapped Value Handling=Add
    Always Use Unmapped Value Handling=False
    We get a very strange error saying that :
    [code]Encountered a pre-SP4 map. The map needs to be upgraded to SP4.
    Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map.[code]
    Could it be that our MDM 5.5 SP4 is not compatible with schemas generated with XI v.7 SP9?
    All of our MDM is 5.5 SP4. It makes no sense that we would get THIS kind of error. Also, I am questioning our combination of these and other configurations since it doesn't always seem to do what it should

    Hi Donald,
    this sounds good so far. Just a short hint: you've set "Default Qualified Update: Replace". This explains why Import server "appears to overwrite EVERYthing
    with NULL other than these two fields.". The reason is the replace. A replace means that the old values are completely deleted and only the new incoming ones are stored. I'd suggest to use any of the Update possibilities.
    Note: the definitions you set in in the record matching step are mainly for the new records in the main table! Records in qualified look ups are handled differently! If you open your map in Import Manager, switch to tab "Map Fields/Values". Select a field that is your non qualifier. Right-Click on it and choose "Set qualified update" from the context menu. Now you can define which qualifiers can be used for the qualified look up matching. And you can define as well what should happen with new and/or existing records.
    Regarding the value mapping: do you use keymapping? Or do you use simple values only? Do you save the map everytime you add a new value mapping?
    Regarding the issue "Encountered a pre-SP4 map. The map needs to be upgraded to SP4. Solution: Please, Launch the Import Manager GUI using the same source file and simply save the map". This sounds very likely like a bug in MDIS and should be reported to SAP!
    Hope that helps
    Michael

  • Message Mapping error:  RuntimeException in Message-Mapping transformation

    Hi,
    Being new to XI, I am struglling to sort out a basic mapping error. Appreciate if you could help out.
    Its an File->XI->R/3 scenario.
    My FCC successfully reads the File and creates an XML. However this XML is not transferred to the target XML structure which is exactly same except the root element name is different at top.
    I tried various forum tips but I still am getting the error.
    ( When I Test the Message mapping in test mode..it seems fine, however if I copy the XML from SXMB_MONI, it then throws the above error)
    I looked at the MM in text mode: below is the extract
    /ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER=
    /ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/SOURCE=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/SOURCE=
    /ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/DESTINATION=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/DESTINATION=
    /ns0:MT_REQUEST_TO_SAP/REQUEST_DETAILS/MSG_HEADER/MESSAGE_ID=/ns0:MT_REQUEST/REQUEST_DETAILS/MSG_HEADER/MESSAGE_ID=
    As seen the name space in both starts with nS0 and end of each line has '=' sign. Is that ok.
    I have run out of options and dont know , whats the problem. Please help.
    The target and Source XML structures are exactly same as shown below
    MT_REQUEST                                 MT_REQUEST_TO_SAP
       |__MSG_HEADER                            |__MSG_HEADER  
         |__SOURCE                                |__SOURCE
         |__DESTINATION                           |__DESTINATION
         |__MESSAGE_ID                            |__MESSAGE_ID
    And the SXMB_MONI Trace shows the following error
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation:
    Cannot produce target element /ns0:MT_REQUEST_TO_SAP.
    Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at ..
    Thanks
    Shirin
    Edited by: Shirin K on May 29, 2008 10:29 AM

    Hi Prakasu,
    As structure are exactly same, I have done 1:1 mapping. So all the fields in target structure are mapped, so no field has beeen left.
    In this structure, I do not have any 1:n relation. So 1:1 mapping should be fine.
    Apart from this could teher be any other reason.
    Regards
    Rajiv

  • CHECK_EXCEPTION in message mapping ??

    Hi XI friends..
    i am getting error like this ..while activating message mapping..
    <b>nternal error while checking object Message Mapping MM_MES_WorkOrderCompletion_To_BAPI</b>
    details...log..
    <i>#6 17:37:30 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
    Thrown:
    MESSAGE ID: com.sap.aii.ib.server.oa.rb_all.CHECK_EXCEPTION
    com.sap.aii.ib.core.clmgmt.ChangeListMgmtException: Internal error while checking object Message Mapping MM_MES_WorkOrderCompletion_To_BAPI | http://aaaa.com/xi/SAP_ERP/PPE/ERP_MES (AL_PPE_ERP_MES , 1.0 of aaaa); see details
         at com.sap.aii.ib.core.clmgmt.ChangeListMgmtException.createFromException(ChangeListMgmtException.java:35)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:227)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
         at com.sap.aii.ib.sbeans.clmgmt.ChangeListMgmtBean.submitChangeList(ChangeListMgmtBean.java:92)
         at com.sap.aii.ib.sbeans.clmgmt.ChangeListMgmtRemoteObjectImpl10.submitChangeList(ChangeListMgmtRemoteObjectImpl10.java:435)
         at com.sap.aii.ib.sbeans.clmgmt.ChangeListMgmtRemoteObjectImpl10p4_Skel.dispatch(ChangeListMgmtRemoteObjectImpl10p4_Skel.java:343)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java)
         at java.security.AccessController.doPrivileged1(Native Method)
         at java.security.AccessController.doPrivileged(AccessController.java)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java)
    </i>
    please guide me..
    regards
    ram

    Hi friends..
    i am getting error like this when i am trying to do static test...
    <b>There is not enough space in the file system.</b>
    details...log..
    <i>#23 19:33:37 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
    Thrown:
    MESSAGE ID: com.sap.aii.ib.server.cmpl.CompilerException
    com.sap.aii.ib.core.mapping.exec.ExecuteException: There is not enough space in the file system.
         at com.sap.aii.ib.server.mapping.exec.ServiceUtil.compileSourceCode(ServiceUtil.java:207)
         at com.sap.aii.ib.server.mapping.exec.ServiceUtil.compile(ServiceUtil.java:156)
         at com.sap.aii.ibrep.
    </i>
    plz..guide me..
    ram

  • Insufficient authorization to display object Message Mapping

    Hi there
    Every now and then when I try and open a message mapping object I get this error: Insufficient authorization to display object Message Mapping. I then restart my Integration Builder then it works again.
    Any Idea how I would fix this?
    Thanks,
    Jan

    hi,
    apart from what was said you can try changing
    com.sap.aii.ib.util.server.auth.activation
    parameter in exchangeprofile to false
    if you don't use any data-dependent authorizations
    then you should never see this error
    maybe this will help
    but remember that if you want to use data-dependent authorizations
    in the future you need to put it back to true again
    Regards,
    Michal Krawczyk

  • Problem with message mapping ...

    Hello,
    I have problem with message mapping. I implemented SOAP-to-RFC scenario. The source message is of type http://sntcz.cz/xmlns/holidays:MT_Holiday, the target message of type urn:sap-com:document:sap:rfc:functions:Z_GET_SUPERIOR. But some error is still generated in Request Message Mapping step:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_GET_SUPERIOR/USR. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at .....
    This is XSD definition of source message:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sntcz.cz/xmlns/holidays" targetNamespace="http://sntcz.cz/xmlns/holidays">
    <xsd:element name="MT_Holiday" type="DT_Holiday" />
    <xsd:complexType name="DT_Holiday">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    030495e1742f11dd963600301875333b
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="SinceDay" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fba049b067aa11dd8be6eee20abb2a3f
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="SinceMounth" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fba293a067aa11dda311eee20abb2a3f
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="SinceYear" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fba293a167aa11dd9b4eeee20abb2a3f
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="UntilDay" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fba293a267aa11ddc352eee20abb2a3f
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="UntilMounth" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fba293a367aa11ddc33aeee20abb2a3f
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="UntilYear" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fba293a467aa11dda8cfeee20abb2a3f
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="UserId" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    fba293a567aa11dd9698eee20abb2a3f
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    This is XSD definition of target message:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions">
    <xsd:element name="Z_GET_SUPERIOR">
    <xsd:complexType>
    <xsd:all>
    <xsd:element name="USR" type="xsd:string" minOccurs="0" />
    </xsd:all>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    It's strange that if I use Message Mapping Test it works fine. But in pipeline not.
    Do you have any idea where could be the problem?
    Thank you in advance!
    Best regard,
    Zbynek

    Hi,
    To know the correct error Take the Inbound Payload from MONI and Test it in Mapping Test TAB. then u will come to know the exact error.
    Procedure to take the Payload
    goto MONI-Double click on MessageInbound Message ( CENTRAL ) --Payloads ---Double click on MainDocument ( application/xml ) -Just Right Click on the second window-View Source
    then now Copy this and paste it in Mapping Test and Execute.
    REgards
    Seshagiri

  • BaseRuntime Exception during Message Mapping

    Hi I am performing the scenario File --> XI --> File
    I want to do the File content Conversion (FCC) only at the Receiver side.
    My source file(Message Type) is XML which looks like as below:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT1_FCC xmlns:ns0="http://accenture.com/xi/F2F">
    - <Name_>
    - <Name>
      <FName>abc</FName>
      <MName>bcd</MName>
      <LName>cde</LName>
      </Name>
      </Name_>
      </ns0:MT1_FCC>
    My target file would be the text file which will look like as follows:
    abc#bcd#cde
    However at runtime the Error is thrown with BaseRuntimeException in Message Mapping which simple one to one mapping from source message to target message . the source and the target message are same.
    The Error message is as follows:
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_FCC_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
    Kindly Look into the Issue..

    Hi i think you are getting confused by the Sorce Structure...
    Ok lemme retype it for You and please then tell me the necessary parameters needed to convert the source xml file into the target text file
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT1_FCC xmlns:ns0="http://accenture.com/xi/F2F">
       <FullName>
          <Name>
             <FName>abc</FName>
             <MName>bcd</MName>
             <LName>cde</LName>
          </Name>
       </FullName>
    </ns0:MT1_FCC>

  • Java.io.IOException: Error writing to server after installing SP17

    After installing SP17 in production, we are seeing message in AE failing with com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server.
    The messages don't make it to IS and are stuck in AE.
    We've checked pipeline url / sm59 entry for INTEGRATION_DIRECTORY_HMI using user - XIISUSER, we did a full cache refresh.
    They all appear to be set correctly.
    We'll take any ideas and suggestions.
    Thank you.

    Yes...we have been working all night on this. The FM did create an entry but it does no look like its recognising.
    This is what we see in the Adapter messaging tool.
    2006-09-18 13:28:24 Error Returning synchronous error notification to calling application: Received HTTP response code 401 : Unauthorized.
    2006-09-18 13:28:24 Error Transmitting the message using connection http://host:8176/sap/xi/engine?type=entry failed, due to: Received HTTP response code 401 : Unauthorized.
    2006-09-18 13:28:24 Error The message status set to FAIL.
    2006-09-18 13:28:24 Error Returning to application. Exception: Received HTTP response code 401 : Unauthorized
    Any help?

  • SQL Server reported SQL message 547

    We are running SCCM 2012 R2 Primary site with remote sql server. We are getting following error:
    Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The INSERT statement conflicted with the FOREIGN KEY constraint "ProviderNotificationTracking_ProviderNotifications_FK".
    The conflict occurred in database "CM_NYC", table "dbo.ProviderNoti
    Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.
    Any feedback.

    Which thread of SMS_Executive is generating this error?
    Torsten Meringer | http://www.mssccmfaq.de

  • Error while activating message mapping

    Hi,
    We are trying to activate message mappings and getting error as CHECK_EXCEPTION and in error details its showing that usr/sap/server.........................../classpath_resolver/Map.......................no such file or directory.........
    What can be the issue?We can activate all other objects(DT,MT,IM,etc)
    Best Regards,
    Harleen Kaur Chadha

    Hi
    Check this thread you can find the reason for this error CHECK_EXCEPTION solved here
    Activating Object in IR - Getting Null Pointer Exception
    Re: mapping test error
    Internal error while checking object Message Mapping...
    Problem Activating Mappings in the IR
    Message Mapping activation Error
    Regards
    Abhishek

  • Error Activating Message Mapping

    HI All,
    I am getting the below error when i try to activate any message mapping in the IR. Any ideas?
    " Starting compilation  Source code has syntax error:  java.lang.NoClassDefFoundError: com/sun/tools/javac/Main Exception in thread "main"
    Thank you in Advance.
    D

    Hi,
    Is there recently been an update like WAS ABAP and WAS JAVA to SPS13(nw2004s)?
    Please check this thread there are some pointers in it:
    Re: 500 internal server error
    Best regards,
    Guido

  • While Activating  Message mapping, error.

    Hi
    While activating my message mapping  i am getting this error "JMS server failed"
    How to resolve this and whats the cause of it?
    Please do not post links.
    Thanks in advance
    Saiyog
    Points will be awarded
    Edited by: Saiyog Gonsalves on Jun 13, 2008 6:09 PM

    Hi,
    There seems to be problem with J2EE Server. Please follow the following steps and it will resolve your error.
    login to J2EE Visual aadmin ->cluster ->services ->.JMS connector ->runtime(Right side tab) ->check the factories / destinations (if anything is in red color X mark).
    Fix it and restart the server.
    Pls reward points if answer is useful
    Thanks
    Amit

  • Error when saving message mapping -

    Just upgradedto PI 7.1. System details below....
    Make Release NW07_08_REL  SPS Number 08  JDK Version jdk15
    Server Version SAP J2EE Engine 7.10.3710.43701.20090416112158
    Java Runtime Java(TM) 2 Runtime Environment, Standard Edition (version=5.1.034)
    Java Virtual Machine SAP Java Server VM (version=5.1.034)
    Operating System AIX (version=5.3, arch=ppc64)
    I've been building an interface to test the developer tools and when I save my message mapping (it's a very simple graphical mapping) I get a java popup with the text 'Internal GUI error', I'm using Java WS Version 1.5.0 (build 1.5.0_19-b02) as per the PI documentation.
    I recreated the problem timing each activity and saved the exception in a text file. I'm able to identify the relevant section of the exception biut it's meaningless to me. I searched SDN & OSS and I can't find any specific hits. Those that are similar (different SAP applications - WebDynPro for example) point towards incompatible s/w components - Java Run Time environment etc.... I've cleared the Java WS cache (Edit>Preferences>Delete Files) just to make sure, but the problem still occurs. I'm looking for advice. I've pasted some of the exception details below. I can provide more information but it's a pretty long file.
    Edited by: Rob Warde on Aug 5, 2009 4:27 PM

    Thrown:
    com.sap.aii.utilxi.swing.framework.FrameworkException: Internal problem occurred
         at com.sap.aii.utilxi.swing.toolkit.ExceptionDialog.init(ExceptionDialog.java:124)
         at com.sap.aii.utilxi.swing.toolkit.ExceptionDialog.<init>(ExceptionDialog.java:96)
         at com.sap.aii.utilxi.swing.toolkit.IBMessages$1.run(IBMessages.java:319)
         at com.sap.aii.utilxi.misc.thread.ThreadPool.assureAWTEventQueueing(ThreadPool.java:84)
         at com.sap.aii.utilxi.misc.thread.ThreadPool.assureAWTEventQueueing(ThreadPool.java:67)
         at com.sap.aii.utilxi.swing.toolkit.IBMessages.showException(IBMessages.java:309)
         at com.sap.aii.utilxi.swing.toolkit.IBMessages.showException(IBMessages.java:299)
         at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor$1.run(Guitilities.java:395)
         at java.awt.event.InvocationEvent.dispatch(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    Caused by: java.lang.NoSuchMethodError: com.sap.aii.ib.bom.mt.js.JavaSource.setMode(I)V
         at com.sap.aii.mappingtool.Project.getJavaFile(Project.java:324)
         at com.sap.aii.mappingtool.mf.MappingTool.getJavaFile(MappingTool.java:107)
         at com.sap.aii.mappingtool.fwutil.api.ViewUtil.prepareSave(ViewUtil.java:118)
         at com.sap.aii.ibrep.gui.mapping.xitrafo.XiMappingView.prepareSave(XiMappingView.java:269)
         at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.save(DefaultPersistenceHandler.java:153)
         at com.sap.aii.ib.gui.editor.XiDocument.save(XiDocument.java:335)
         at com.sap.aii.utilxi.swing.framework.cmd.SaveCommand.execute(SaveCommand.java:76)
         at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
         at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
         at com.sap.aii.utilxi.swing.framework.CommandAction.actionPerformed(CommandAction.java:82)
         at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
         at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
         at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)

  • RFC_to_File scenario: error in request message mapping

    Hi!
    I am configuring RFC_to_File scenario.
    The error at the begining is:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_Z_RFB_MATERIALEINGABE_PBU_zu_MT
    : Fatal Error: com.sap.engine.lib.xml.parser.Parser
    Exception of class CX_XMS_SYSERR_MAPPING
    When I display the request message mapping are of the message I can see:
    <Trace level="1" type="T">Interface-Mapping http://www.sap-press.de/xi/training/PBU_00 IM_Z_RFB_MATERIALEINGABE_PBU_zu_MI_Material_Async_In</Trace>
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_Z_RFB_MATERIALEINGABE_PBU_zu_MT_Material_</Trace>
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:202) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest
    Can some one help me to solve this problem?
    Thank you very much!
    regards
    Holger

    Holger,
    Message Mapping Failed.
    >com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data >sections(:main:, row:1, col:202) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
    You are Passing Char to a field, which is not as per the Message Mapping rule
    Cheers
    Agasthuri Doss

  • Compiler Process error in Message Mapping

    Hi all,
    I have recently installed an XI system.
    First time when i create simple message mapping, it was showing compilation process error.
    Please tell me what needs to be done so that message mapping works well. It is really urgent.
    Thank you all.
    Regards,
    Kavan Shah

    hi
    check the HDD space on your XI server machine
    try checking the java path on your XI machine
    if this will not work contact the SAP via an OSS note
    As this is a new XI server it probably means it
    was incorrectly installed
    Note:please reward points if solution found helpfull
    Regards
    Chandrakanth.k

Maybe you are looking for