File to RFC - error while processing message to remote system:com.sap.aii.

Hi
i m working on File to RFC scenario. the records are getting displayed in sender CC and receiver CC. But in receiver CC i m also getting the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:      Screen output without connection to user.    
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC in remote system (RfcClient[CC_RIS_STC_PIMASTER_RECEIVER]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:      Screen output without connection to user.   
It was working fine few hours earlier but showing this error now. i was giving a SUBMIT program , but stopped that now.
But still facing the same problem. and in SXMB_MONI its showing recorded for Outbound processing.
could anyone help.

Hi
I am Facing  Following Error When I am trying to call SAP Screen through JCO.jar
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user
Please Guide Whethere it is possible to call SAP screen Through JCO.jar  ot NOT
Please HELP if it is possible to Call SAP screen through JCO.jar with step and Code
Thanks
Vivek

Similar Messages

  • Error while processing message to remote system

    Hi,
    I am trying to load the data from flat file to R/3. I am using the file adapter to pick the file and RFC adapter to transfer into R/3. I am getting the success status in the sxmb_moni and adapter framework(green for both the adapters). But when i check the status in the RWB message monitoring, I am getting the error.
    I am using the message interface defined in the software component for R/3 system which has a different namespace. When i am trying to upload data, i am getting the error as namespace missing in RWB. The detailed error in RWB is as follows:
    Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declara
    Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declara.
    The previous thread relating this is:
    Process Integration (PI) & SOA Middleware
    Requesting for a solution.
    Regards,
    Raghavendra

    Hi,
    >>><i>So i tried creating a RFC(using sm59)in the R/3,
    When i try to import the RFC i have created, I am not able to see the one i have created.</i>
    In your R/3 system, go to se38, enter your RFC name. Go to attributes tab, and click on the radio button named "remote enabled"
    This will enable your RFC to be called by an application outside the R/3 system.
    >>><i>Can you please let me know as to what is it that it is connecting to the R/3(destination) and why am i not able to find my RFC.</i>
    You are tyring to log on to your R/3 system, from xi, in order to import the RFC that you have created. Hence you are asked for user id and password.
    You are not able to find your RFC since it has not been remotely enabled or has not been activated.
    Regards,
    Smitha.

  • Error while processing message

    I have WS2RFC interface that use to work. I recieve in the RWB this error message from the RFC Reciever.
    10/6/08 1:20:10 PM aa98b6f0-9398-11dd-94cf-0017a43cc516 Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[RFC_Reciever]07cef9b030ce3c398f109f93020feffb is exhausted. The current pool size limit (max connections) is 1 connections.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[RFC_Reciever]07cef9b030ce3c398f109f93020feffb is exhausted. The current pool size limit (max connections) is 1 connections.
    any ideas?
    Kfir

    In RFC channel increase the maximum connections paramter value to 5. Save and activate.
    Thanks,
    Gujjeti

  • Exception caught by adapter framework: error while processing message to ..

    URGENT:
    <b>Legacy >XI>R3 interface</b>
    <b>SAP XI (file_adapter --> RFC_adapter)</b>
    Friends.
               I need your help for next problem above:
    Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
    Thanks very much for your helps
    Nota: This error is XIPRO environment.
    Message was edited by:
            Cristian Alejandro Toro Salazar
    Message was edited by:
            Cristian Alejandro Toro Salazar

    Hi Cristian,
    >>>>functiontemplate from repository was
    this SAP note 730870 - describes your issue
    let me know if it helped
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Error while processing message payload Element 'CategoryCode&#39

    Hi Experts,
    I am trying to integrate SAP ECC with TM. I have transferred the sales order from ECC to TM, but its not triggering order based transportation requirement (OTR) instead giving an error Error while processing message payload Element &#39;CategoryCode&#39 and all the xml messages are stuck in inbound queue. The screen shot of the issue is as appended herewith. Please advise.
    Thanks & Regards,
    Aunkur De

    Hi Aunkur,
    The issue will generally  come when a mandatory field in XML which you are not sending either or missed.
    Please check if all mandatory fields are mapped properly.
    Best regards,
    Rohit

  • Error while processing message payload Element PI SXMB_MONI (ECC to TM)

    Dear Experts,
    while processing an XML message in TM using receiver interface IntracompanyTransportationRequestRequest_In , we encounter an error message.
    <SAP:Stack>Error while processing message payload Element &#39;StockTransportOrderReferenceIndicator&#39; missing</SAP:Stack>  
    <SAP:Retry>M</SAP:Retry>
    ssee screenshot attached.
    The field StockTransportOrderReferenceIndicator cannot be located in ECC and I cannot find what the system is expecting to populate here.
    Can somebody propose an approach on how to investigate into this error message for the solution?
    thanks a lot
    Salvador

    Hi Salvador,
    Thanks for your reply. We were able to fix that issue. As of now we have managed to send sales order to TM but getting the following error. Messages are getting failed in SAP TM. Even if the product exists in the system (TM) still the error message persists. I have CIFed location, business partner, product from ECC and everything exists in SAP TM with the same business system group. Kindly advise. Did you happen to face any similar kind of issue during your implementation ?
    Thanks & Regards,
    Aunkur De

  • FTP error-Unable to create new pooled resource: com.sap.aii.adapter.file.ft

    Hi,
    We have a scenario where XI receives a Idoc and based on the contents of Idoc, It will generate 5 different files and send it to the external FTP server.We configured 5 receiver channels for these 5 files.
    When this interface runs, most of the files will be delivered but some of the messages will be errored out.
    The receiver channel has shown the following error-
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: com.sap.aii.adapter.file.ftp.FTPEx
    I tried to resend them by temperorily stopping other channels to reduce connections to this FTP server.But these messages again resulted with same error.
    Can someone suggest what might be the cause for this error.
    Thanks in advance.

    Hi ,
    As I am not sure about the problem so U just try all of the option I am writing below. It may help u as these are the probable solutions for this problem.
    1.perform Full CPA cache refresh using PIDIRUSER
    2.The problem seems to be in establishing the connection with the File server . This could be due to
    a. Wrong user name or password in receiver adapter .
    b. Firewall connection are not open
    actually you are saying that some files are being delivered so all the file has to be deliverd on same server on diffrent directory or all files are going on diffrent server at present I am assuming that all files are going on diffrent server so please check UID & PWD properly.if they are on same server but diff. directory it can be easily done using one Communication channel only.
    3. Finally please check the errorneous communication channel .
    to check your communication channels are working fine or not you can check in channel monitoring in PI7.0, adapter monitoring in Xi3.0.
    if you are on PI7.0, goto RWBCache monitoring select AE and cilck disply-select the date todays--check everything is greent here
    4.Please check your maximal connection pool .
    Regards,
    Saurabh

  • Error While processing Message-Message no. VL086

    Dear All,
    While Processing Outbound delivery in VL02N i am getting the below following error message.
    Please help me out.
    Error msg - output could not be issued.
    Message no. VL086
    Diagnosis
    An error occurred in the message processing program.
    Regards,
    Nagaraj S

    Hi AP,
    It is giving output in all other login, we check the authorization also.It is not having anyproblem with all others.
    Pls help me out.
    Regards,
    Nagaraj S

  • Readtimeout error while generating JCA from remote system usingoraclestudio

    Please anyone give the solution to the following query
    when i tried to generate the JCA file using oracle studio which is in remote system, it gives the timeout exception.
    Please any one give the reason.
    Thanks
    amar
    Edited by: 897448 on Nov 16, 2011 11:04 PM

    You are trying to use a custom class as a return type?
    The return type needs to be JAX-B compatible
    see: http://download.oracle.com/docs/cd/E17802_01/webservices/webservices/docs/2.0/tutorial/doc/JAXWS3.html
    You should avoid using user defined complex types as much as possible because they require the clients to be able to process them as well making your webservice less portable and thus defeating the main advantages of webservices.

  • Out of memory error occurred while processing message at RFC receiver

    Hi Experts
    Hi Experts
    i have a scenario file to RFC BPM bridge Sync/Async,
    i´m getting this error when this BPM is trying to read  the RFC
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: Out of memory error occurred while processing message at RFC receiver
    please somebody can you help me

    Hi,
    No need to restart the server. In PI there is a parameter 'java Heap' indicating the size of data processed adapters. Check if it is necessary to increase the size of this parameter.
    Check the note: 1173398
    I hope to help you
    Regards,

  • File to RFC Error

    Hi,
      I done File->RFC scenario. It was showing WAITING in
    Message Monitoring. But in CC Monitoring showing error
    like <b>No suitable sender agrement found</b>. Y it is
    showing like this? even I done Sender Agrement?
    thx and regards,
    Ansar.

    Hi,
         Now I gone through this link
    Re: Unable to find the processed message
      Here they mentioned to check  in  http://<host>:<port>/mdt
      I checked it. Then I found the error in Audit Log
    as <i>Delivery of the message to the application using
    connection AFW failed, due to: error while processing
    message to remote
    system:com.sap.aii.af.rfc.core.client.RfcClientException:
    could not convert request from XML to
    RFC:com.sap.mw.jco.JCO$ConversionException: (122)
    JCO_ERROR_CONVERSION: Date '25.09.2006' has a wrong
    format at field DELIV_DATE: Unparseable
    date: "25.09.2006".</i>
        Now how to give the date format?
    thx.

  • Error message com.sap.aii.af.ra.ms.api.DeliveryException: error while proce

    hello experts
    I am sending a message WS2RFC and recieve an error message that return from the RFC.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing the request to rfc-client: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Date '03042008' has a wrong format at field DATUM: Unparseable date: "03042008"</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    any ideas what it is and how to solve it?

    Hi,
    Looks like you have passed data in wrong format to RFC input parameter.
    Your format: DDMMYYYY (03042008)
    Expected: YYYYMMDD
    I would use a graphical mapping function "DataTrans" to convert date format from DDMMYYYY to YYYYMMDD.
    Regards,
    Jakub

  • HTTP to RFC Mapping error:com.sap.aii.utilxi.misc.api.BaseRuntimeException:

    hi all,
              I am doin a http to rfc scenario.In moni it is showing a mapping error in the request mapping and showing this error.In IR my mapping is working fine but in payload runtime i found the error is because it is showing <?xml version="1.0" encoding="UTF-8" ?> twice.Below is the payload message
    <i><?xml version="1.0" encoding="UTF-8" ?>
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:Lspm_Request_SampledueGrid_MT xmlns:ns0="http://satyam.com/xi/LSPM">
      <KUNNR>100000</KUNNR>
      <FROM_DATE>15.11.2006</FROM_DATE>
      <TO_DATE>10.12.2006</TO_DATE>
    - <EQUIPMENTID>
    - <item>
      <EQUIPID>wb</EQUIPID>
      </item>
      </EQUIPMENTID>
    + <LOCATIONID>
    - <item>
      <LOCID>1</LOCID>
      </item>
      </LOCATIONID>
    - <OILID>
    - <item>
      <OILID>BP260</OILID>
      </item>
      BP260
      </OILID>
      </ns0:Lspm_Request_SampledueGrid_MT></i>
    I tested using view source code and removing the extra ]<?xml version="1.0" encoding="UTF-8" ?> in IR and it is working fine.
    Now my problem is how to rectify this error can anyone help me out please??
    thanks,
    Nisheeta

    hi,
         I tried to post the XML in the http page without the header and now it it showing a new error
    Result:
    <SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon)</SAP:AdditionalText></SAP:Error>
    http://cgnsap27:8000/sap/xi/adapter_plain?namespace=http%3A//satyam.com/xi/LSPM&interface=Lspm_SampledueGrid_Syn_MI&service=SATYAM_LSPM_BS&party=&agency=&scheme=&QOS=BE&sap-user=shailesh&sap-password=shailesh&sap-client=100&sap-language=EN
    wat does this mean??
    nisheeta

  • Error while sending message.

    Hi,Could anyone explain the below error message and tell me how can we solve this?
    Error while sending message: com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=NDE_CLNT200;TS=;AN=Z_FI_OUTBOUND_SAP_TO_SIP;ANS=urn:sap-com:document:sap:rfc:functions;
    Regards,
    sai.

    Hello,
    I have the same problem here. I already did many times redefine the wohle szenario and also tried out many different adapters. But any time I get the same error message. I checked the agreements and determinations very carefully. The Test in IDR said this:
    Senderagreement
    <not found>
    <Trace level="1" type="B">SENDER AGREEMENT SIMULATION</Trace> <Trace level="1" type="T">Simulating Adapter Engine...</Trace> <Trace level="1" type="T">Simply trying to loolup for the most specific Sender Agreement object</Trace> <Trace level="1" type="T">no objects found</Trace> <Trace level="1" type="T">Note that real results may differ</Trace>
    Receiverdetermination
    | BusSys_A | MI_HTTPtoJDBC_HTTP
    <Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace>... (4 Zeilen)
    Interface-determination
    | BusSys_A | MI_HTTPtoJDBC_HTTP | | BusSys_B
    <Trace level="1" type="B">CL_ID_PLSRV-ENTER_PLSRV</Trace>... (4 Zeilen)
    Interface-Mapping
    <not found>
    Runtimeerror
    com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_HTTPtoJDBC_Input_: RuntimeException in Message-Mapping transformatio~
    <Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>... (152 Zeilen)
    I hope you can help me getting it working. thank you

  • Error while processing CMP beans

    Hi,
    I have been trying to deploy my EAR on SunONE 7 since quite some time but still not successful.
    I feel the classpath being printed on the log is not complete, it gets truncated, i can see some special characters at the end of the classpath e.g. D:\Sun\studio5_se\appserver7\domains\domain1\MeterCent-�
    The error log is as follows,
    FINE: Compiling D:\Sun\studio5_se\appserver7\domains\domain1\MeterCentralServer\generated\ejb\j2ee-apps\meterCentralSunO
    NEEJB\com\pb\meterCentral\entity\ModelSerialRangeEntityBean1689415024_JDOState.java ....
    FINE: [EJBC] JAVAC COMMAND:
            -g
            -d
            D:\Sun\studio5_se\appserver7\domains\domain1\MeterCentralServer\generated\ejb\j2ee-apps\meterCentralSunONEEJB
            -classpath
            D:/Sun/studio5_se/appserver7/lib/appserv-rt.jar;D:/Sun/studio5_se/appserver7/jdk/lib/tools.jar;D:\Sun\studio5_se\
         appserver7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\meterCentral.jar;D:
         \Sun\studio5_se\appserver7\domains\domain1\MeterCentralServer\applica
    tions\j2ee-apps\meterCentralSunONEEJB_1\BusKeySessionEJB_jar;D:\Sun\studio5_se\appserver7\domains\domain1\MeterCentralSe
    rver\applications\j2ee-apps\meterCentralSunONEEJB_1\dataPackage.jar;D:\Sun\studio5_se\appserver7\domains\domain1\MeterCe
    ntralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\meterCentral.jar;D:\Sun\studio5_se\appserver7\domains\domain1
    \MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\SessionInfoDetailEntityEJB_jar;D:\Sun\studio5_se\apps
    erver7\domains\domain1\MeterCentralServer\applications\j
    FINE: JDK Directory: D:\Sun\studio5_se\appserver7\jdk
    FINE: fastExe: null
    FINE: javacExe: D:\Sun\studio5_se\appserver7\jdk\bin\javac.exe
    FINE: jdkDir: D:\Sun\studio5_se\appserver7\jdk
    FINE: DPL5302:Process creation failed.
    java.io.IOException: CreateProcess: D:\Sun\studio5_se\appserver7\jdk\bin\javac.exe -g -d D:\Sun\studio5_se\appserver7\do
    mains\domain1\MeterCentralServer\generated\ejb\j2ee-apps\meterCentralSunONEEJB -classpath D:/Sun/studio5_se/appserver7/l
    ib/appserv-rt.jar;D:/Sun/studio5_se/appserver7/jdk/lib/tools.jar;D:/Sun/studio5_se/appserver7/lib/appserv-ext.jar;D:/Sun
    /studio5_se/appserver7/lib/appserv-cmp.jar;D:\Sun\studio5_se\appserver7\imq\lib/imq.jar;D:\Sun\studio5_se\appserver7\imq
    \lib/imqadmin.jar;D:\Sun\studio5_se\appserver7\imq\lib/imqutil.jar;D:/Sun/studio5_se/appserver7/lib/appserv-admin.jar;D:
    /Sun/studio5_se/appserver7/lib/appserv-ideplugin.jar;;D:/Sun/studio5_se/appserver7/pointbase/client_tools/lib/pbclient42
    RE.jar;D:\Sun\studio5_se\appserver7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\Me
    terFinInfoEntityEJB_jar;D:\Sun\studio5_se\appserver7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCent
    ralSunONEEJB_1\dataPackage.jar;D:\Sun\studio5_se\appserver7\domains\domain1\MeterCent-�
            at java.lang.Win32Process.create(Native Method)
            at java.lang.Win32Process.<init>(Win32Process.java:63)
            at java.lang.Runtime.execInternal(Native Method)
            at java.lang.Runtime.exec(Runtime.java:566)
            at java.lang.Runtime.exec(Runtime.java:491)
            at java.lang.Runtime.exec(Runtime.java:457)
            at com.iplanet.ias.ejb.codegen.ProcessRunner.run(ProcessExecutor.java:257)
            at java.lang.Thread.run(Thread.java:536)
    SEVERE: DPL5103: EJBC - compilation failed
    com.iplanet.ias.ejb.codegen.JavaCompilerException: com.iplanet.ias.ejb.codegen.ProcessExecutorException: Abnormal proces
    s termination -- process threw an Exception.
    Attempted command: D:\Sun\studio5_se\appserver7\jdk\bin\javac.exe -g -d D:\Sun\studio5_se\appserver7\domains\domain1\Met
    erCentralServer\generated\ejb\j2ee-apps\meterCentralSunONEEJB -classpath D:/Sun/studio5_se/appserver7/lib/appserv-rt.jar
    ;D:/Sun/studio5_se/appserver7/jdk/lib/tools.jar;D:/Sun/studio5_se/appserver7/lib/appserv-ext.jar;D:/Sun/studio5_se/appse
    rver7/lib/appserv-cmp.jar;D:\Sun\studio5_se\appserver7\imq\lib/imq.jar;D:\Sun\studio5_se\appserver7\imq\lib/imqadmin.jar
    ;D:\Sun\studio5_se\appserver7\imq\lib/imqutil.jar;D:/Sun/studio5_se/appserver7/lib/appserv-admin.jar;D:/Sun/studio5_se/a
    ppserver7/lib/appserv-ideplugin.jar;D:\Sun\studio5_se\appserver7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJ
    WARNING: DPL5035:Error while running ejbc
    com.iplanet.ias.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- -- Error while processing CM
    P beans.
            at com.iplanet.ias.deployment.backend.EJBCompiler.wrapException(EJBCompiler.java:589)
            at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:186)
            at com.iplanet.ias.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:215)
            at com.iplanet.ias.deployment.backend.AppDeployer.deploy(AppDeployer.java:98)
            at com.iplanet.ias.deployment.backend.AppDeployer.doRequest(AppDeployer.java:50)
            at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(
    ManagedServerInstance.java:745)
            at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInsta
    nce.java:667)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:324)
            at com.iplanet.ias.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:188)
            at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:137)
            at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
            at com.iplanet.ias.admin.servermodel.controllers.SOMRequestDispatcher.invoke(SOMRequestDispatcher.java:88)
            at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.doDeploy(AppServerInstanceControlle
    r.java:2244)
            at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.deployApplication(AppServerInstance
    Controller.java:1099)
            at com.iplanet.ias.admin.servermodel.AppServerInstance.deployApplication(AppServerInstance.java:249)
            at com.iplanet.ias.admin.server.gui.jato.DeployEARApplicationViewBean.add(DeployEARApplicationViewBean.java:111)Please help me out in deploying my EAR.
    Thanks,
    Sankate

    I am attaching the error from the server.log
    [29/Nov/2003:13:43:41] FINE ( 1764): DPL5302:Process creation failed.
    java.io.IOException: CreateProcess: C:\JDK1.4\bin\javac.exe -g -d D:\Sun\AppServer7\domains\domain1\MeterCentralServer\generated\ejb\j2ee-apps\meterCentralSunONEEJB -classpath D:/Sun/AppServer7/lib/appserv-rt.jar;C:/JDK1.4/lib/tools.jar;D:/Sun/AppServer7/lib/appserv-ext.jar;D:/Sun/AppServer7/lib/appserv-cmp.jar;D:\Sun\AppServer7\share\lib/mail.jar;D:/Sun/AppServer7/lib/appserv-ideplugin.jar;D:\Sun\AppServer7\imq\lib/imq.jar;D:\Sun\AppServer7\imq\lib/jaxm-api.jar;D:\Sun\AppServer7\imq\lib/imqadmin.jar;D:\Sun\AppServer7\imq\lib/imqutil.jar;D:/Sun/AppServer7/lib/appserv-admin.jar;D:\Sun\AppServer7\share\lib/jaxrpc-impl.jar;D:\Sun\AppServer7\share\lib/jaxrpc-api.jar;D:\Sun\AppServer7\share\lib/jaxr-impl.jar;D:\Sun\AppServer7\share\lib/jaxr-api.jar;D:\Sun\AppServer7\share\lib/activation.jar;D:\Sun\AppServer7\share\lib/saaj-api.jar;D:\Sun\AppServer7\share\lib/saaj-impl.jar;D:\Sun\AppServer7\share\lib/commons-logging.jar;D:\Sun\AppServer7\imq\lib/fscontext.jar;D:\Sun\AppServer7\imq\lib/providerutil.jar;D:/Sun/AppServer7/lib/appserv-jstl?
         at java.lang.Win32Process.create(Native Method)
         at java.lang.Win32Process.<init>(Win32Process.java:67)
         at java.lang.Runtime.execInternal(Native Method)
         at java.lang.Runtime.exec(Runtime.java:566)
         at java.lang.Runtime.exec(Runtime.java:491)
         at java.lang.Runtime.exec(Runtime.java:457)
         at com.iplanet.ias.ejb.codegen.ProcessRunner.run(ProcessExecutor.java:257)
         at java.lang.Thread.run(Thread.java:536)
    [29/Nov/2003:13:43:41] SEVERE ( 1764): DPL5103: EJBC - compilation failed
    com.iplanet.ias.ejb.codegen.JavaCompilerException: com.iplanet.ias.ejb.codegen.ProcessExecutorException: Abnormal process termination -- process threw an Exception.
    Attempted command: C:\JDK1.4\bin\javac.exe -g -d D:\Sun\AppServer7\domains\domain1\MeterCentralServer\generated\ejb\j2ee-apps\meterCentralSunONEEJB -classpath D:/Sun/AppServer7/lib/appserv-rt.jar;C:/JDK1.4/lib/tools.jar;D:/Sun/AppServer7/lib/appserv-ext.jar;D:/Sun/AppServer7/lib/appserv-cmp.jar;D:\Sun\AppServer7\share\lib/mail.jar;D:/Sun/AppServer7/lib/appserv-ideplugin.jar;D:\Sun\AppServer7\imq\lib/imq.jar;D:\Sun\AppServer7\imq\lib/jaxm-api.jar;D:\Sun\AppServer7\imq\lib/imqadmin.jar;D:\Sun\AppServer7\imq\lib/imqutil.jar;D:/Sun/AppServer7/lib/appserv-admin.jar;D:\Sun\AppServer7\share\lib/jaxrpc-impl.jar;D:\Sun\AppServer7\share\lib/jaxrpc-api.jar;D:\Sun\AppServer7\share\lib/jaxr-impl.jar;D:\Sun\AppServer7\share\lib/jaxr-api.jar;D:\Sun\AppServer7\share\lib/activation.jar;D:\Sun\AppServer7\share\lib/saaj-api.jar;D:\Sun\AppServer7\share\lib/saaj-impl.jar;D:\Sun\AppServer7\share\lib/commons-logging.jar;D:\Sun\AppServer7\imq\lib/fscontext.jar;D:\Sun\AppServer7\imq\lib/providerutil.jar;D:/Sun/AppServer7/lib/appserv-jstl.jar;;D:/Sun/AppServer7/pointbase/client_tools/lib/pbclient42RE.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\MeterFinInfoEntityEJB_jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\dataPackage.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\meterCentral.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\AgreementLineEntityEJB_jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\dataPackage.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\meterCentral.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\CometSignedRegisterEntityEJB_jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\dataPackage.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\meterCentral.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\AccountExchRateEntityEJB_jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\dataPackage.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\meterCentral.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\JobControlEntityEJB_jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\dataPackage.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\meterCentral.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\CometBoxCertificateEntityEJB_jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\dataPackage.jar;D:\Sun\AppServer7\domains\domain1\MeterCentralServer\applications\j2ee-apps\meterCentralSunONEEJB_1\meterCentral.jar;D:\Sun\AppServer7\domains\domain1
    Output from command:
    -- CreateProcess: C:\JDK1.4\bin\javac.exe -g -d D:\Sun\AppServer7\domains\domain1\MeterCentralServer\generated\ejb\j2ee-apps\meterCentralSunONEEJB -classpath D:/Sun/AppServer7/lib/appserv-rt.jar;C:/JDK1.4/lib/tools.jar;D:/Sun/AppServer7/lib/appserv-ext.jar;D:/Sun/AppServer7/lib/appserv-cmp.jar;D:\Sun\AppServer7\share\lib/mail.jar;D:/Sun/AppServer7/lib/appserv-ideplugin.jar;D:\Sun\AppServer7\imq\lib/imq.jar;D:\Sun\AppServer7\imq\lib/jaxm-api.jar;D:\Sun\AppServer7\imq\lib/imqadmin.jar;D:\Sun\AppServer7\imq\lib/imqutil.jar;D:/Sun/AppServer7/lib/appserv-admin.jar;D:\Sun\AppServer7\share\lib/jaxrpc-impl.jar;D:\Sun\AppServer7\share\lib/jaxrpc-api.jar;D:\Sun\AppServer7\share\lib/jaxr-impl.jar;D:\Sun\AppServer7\share\lib/jaxr-api.jar;D:\Sun\AppServer7\share\lib/activation.jar;D:\Sun\AppServer7\share\lib/saaj-api.jar;D:\Sun\AppServer7\share\lib/saaj-impl.jar;D:\Sun\AppServer7\share\lib/commons-logging.jar;D:\Sun\AppServer7\imq\lib/fscontext.jar;D:\Sun\AppServer7\imq\lib/providerutil.jar;D:/Sun/AppServer7/lib/appserv-jstl?
         at com.iplanet.ias.ejb.codegen.Compiler.c
    [29/Nov/2003:13:43:46] SEVERE ( 1764): ompile(Compiler.java:69)
         at com.iplanet.ias.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:344)
         at com.iplanet.ias.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:188)
         at com.iplanet.ias.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:806)
         at com.iplanet.ias.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:346)
         at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:177)
         at com.iplanet.ias.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:215)
         at com.iplanet.ias.deployment.backend.AppDeployer.deploy(AppDeployer.java:98)
         at com.iplanet.ias.deployment.backend.AppDeployer.doRequest(AppDeployer.java:50)
         at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:745)
         at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:667)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.iplanet.ias.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:188)
         at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:137)
         at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
         at com.iplanet.ias.admin.servermodel.controllers.SOMRequestDispatcher.invoke(SOMRequestDispatcher.java:88)
         at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.doDeploy(AppServerInstanceController.java:2244)
         at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.deployApplication(AppServerInstanceController.java:1099)
         at com.iplanet.ias.admin.servermodel.AppServerInstance.deployApplication(AppServerInstance.java:249)
         at com.iplanet.ias.admin.server.gui.jato.DeployEARApplicationViewBean.add(DeployEARApplicationViewBean.java:112)
         at com.iplanet.ias.admin.server.gui.jato.IASViewBean.handleOkRequest(IASViewBean.java:235)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.iplanet.jato.view.command.DefaultRequestHandlingCommand.execute(DefaultRequestHandlingCommand.java:183)
         at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:299)
         at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:811)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:749)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:596)
         at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:772)
         at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:446)
         at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:324)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
         at org.apache.catalina.core.StandardWrapperV
    [29/Nov/2003:13:43:46] SEVERE ( 1764): alve.access$000(StandardWrapperValve.java:118)
         at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
         at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)

Maybe you are looking for