Exception in method when trigger PDFObject WS

Hi,
wonder anyone do before the PDFObject Tutorial.
as i try to create a new Web Services the concept is about the same but different types...
but somehow i encounter errors...
as the WS has 4 methods
createPdf (test.types.p1.CreatePdf parameters)
extractData (test.types.p1.ExtractData parameters)
getData (test.types.p1.GetData parameters)
getItemValue (test.types.p1.GetItemValue parameters)
but then when i trigger the createPDF methods i get this error
Exception in method com.sap.tut.ejb.pdfobjectservices.PdfObjectLocalLocalObjectImpl0_0.createPdf(java.lang.String,java.lang.String,java.lang.String,java.lang.String).
extractData
Exception in method com.sap.tut.ejb.pdfobjectservices.PdfObjectLocalLocalObjectImpl0_0.extractData(java.lang.String).
getData
Exception in method com.sap.tut.ejb.pdfobjectservices.PdfObjectLocalLocalObjectImpl0_0.getData(java.lang.String).
so wonder how to overcome it.. is there any mistake i have done or errors i have make so have this results
Regards
Jia Jun

now is i alway have exception on Exception in method createPDF.
so what should i do?

Similar Messages

  • ***Is there any listener which trigger the method when KEYUP?

    Hi,
    Is there any listener which can trigger the backingBean method when KEYUP!!!!
    Basically, I got 2 input box in the UI where the 2nd box getting enabled when user enters some value in the first box and tab out. I am doing this via valueChangeListener which has attached with first inputBox. But now I want to enable the 2nd input box as soon as the user start enter the value in the first box, how to do this plz..
    thanks
    kln

    Hi klogube,
    If you want to call method in backingbean from javaScript you should use both clientListener And serverListener as:
    1- Add clientListener inside your inputText as :
    <af:clientListener type="KeyUp" method="keyUp"/>2- write javaScript function as :
    <af:resource type="javascript">
        function keyUp(event) {
           var source = event.getSource();
           AdfCustomEvent.queue(source,"callServerListener", {}, false);
    </af:resource>3-Add serverListener inside your inputText as :
    <af:serverListener type="callServerListener" method="#{backingBeanScope.txnBean4.keyUpMethod}"/>Your InputText will be like:
    <af:inputText label="Label 1" id="it1">
          <af:clientListener type="KeyUp" method="keyUp"/>             
          <af:serverListener type="callServerListener" method="#{backingBeanScope.txnBean4.keyUpMethod}"/>
    </af:inputText>4- The java method:
    public void keyUpMethod(ClientEvent event){
    // do whatever u want
    }Sameh Nassar

  • Java Proxy error: Exception in method methodExists

    Hello all!
    We are doing the following synchronous scenario:  CRM->XI->JavaProxy--->Third party....
    Here is the process we are following to deploy our Proxy:
    1.Created EJB Module Project in NWDS
    2.Import the files generated by XI into ejbModule folder from ZIP file.
    3.Renamed *PortTypeImpl.template to *PortTypeImpl.java
    4.Compiled all code (no errors)
    5.Added all the references to the SAP libraries required (taken from our XI server):
    com.sap.aii.proxy.xiruntime
    com.sap.xi.util.misc
    com.sap.aii.messaging.runtime
    com.sap.guid
    6.Codified Java Proxy – codified the method <interfacename> in the <intefacename>_PortTypeImpl class.
    7.Edited ejb_jar.xml to add EJBs.
    8.Provided a JNDI name in the file ejb-j2ee-engine.xml.
    9.Built EJB archive (no errors).
    10.Created a new Enterprise Application Project and pointed build path to our EJB Project.
    11.Added our EJB to the Enterprise Application project.
    12.Created the references to the SAP libraries in the Enterprise Application Project in the application-j2ee-engine.xml file:
    com.sap.aii.proxy.xiruntime
    com.sap.xi.util.misc
    com.sap.aii.messaging.runtime
    com.sap.guid
    13.Within the Enterprise Application Project we built an EAR file.
    14.We deployed our .ear file to the J2EE Engine via Visual Admin (no errors).
    15.We registered our Java Proxy  on the ProxyServer, using
    /register?ns=<interface_namespace>&interface=<XI_Interface_Name>&bean=<EJB_JNDI_name> &method=<name of the method implemented by you on the _PortTypeImpl>
    Actually, we did the following:
    url for registering the EJB:
    http://ithpsrq0:50200/ProxyServer/register?ns=http://banco.popular.com.pr/xi/crm&interface=mi_AccountInfo_is&bean=popularinc.com/MiAccountInfoIs_Default&method=miAccountInfoIs
    Message displayed when listing interfaces (http://ithpsrq0:50200/ProxyServer/listAll)
    http://banco.popular.com.pr/xi/crm#mi_AccountInfo_is = popularinc.com/MiAccountInfoIs_Default:miAccountInfoIs
    1 interfaces found
    When running the interface we get the following error:
    com.sap.aii.af.ra.ms.api.DeliveryException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.
    Does anyone have any suggestions?
    What causes a "methodExists" Exception?
    Please help us,
    Thanks a lot!!!

    Hi,
      Is this a runtime of "com.sap.aii.proxy.xiruntime.core"
    please check the jars used, adding this jars will solve this i guess.
    aii_utilxi_misc.jar
    ejb20.jar
    exception.jar
    jARM.jar
    sapj2eeclient.jar
    sapxmltoolkit.jar
    aii_msg_runtime.jar
    aii_proxy_xirt.jar
    Also check, application-j2ee-engine.xml  and see if,
    com.sap.aii.proxy.xiruntime
    com.sap.aii.messaging.runtime
    com.sap.xi.util.misc
    com.sap.guid
    You wil get the jars in XI servers, you can ftp and get the jars, but you may need to search them.
    Anotherthing, always take the jars from the xi servers to be sure you are compatible with the upgrades .
    Hope this solves your problem.
    Anirban.

  • Getting Inbound Java Proxy Exception in method "onMessage"

    I have built an Inbound Java proxy, deployed the EJB, viewed it in the J2EE admin tool, registered the JPR settings (also listAll, reviewed results, looks OK), configure the XI scenario.  When I run the XI scenario using the Runtime workbench I get the following error in the BPM Synchronous Send step (calling the Java Proxy)
    "com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method onMessage".
    Does anyone have any suggestions?
    What causes an "onMessage" Exception?

    Thanks Sudhir  Here is the process I am following to deploy my Proxy, would you please validate it.  Created EJB Project in NWDS, unziped XI gened proxies into ejbModule folder, renamed *PortTypeImpl.template to *PortTypeImpl.java (will add real code later), compiled all code (no errors), edited ejb_jar.xml to match your suggested format, can view EJB Candidates (and see my Proxy Bean), built EJB.JAR file (via Wizard), created new Enterprise Application Project and pointed build path to my EJB Project, within the Enterprise Application Project  I built an EAR file (which includes the "EJB Project JAR File",  Deployed Enterprise Application Project to the XI J2EE Engine.  I can log into XI J2EE Admin and see my EJB Project and the Proxy Bean I am trying to execute.  Is this the process you used to deploy the proxy bean?
    Also you you turn on JPR Tracing to see what parameters are passed into the JPR engine?

  • Session bean "Exception in method create()"

    Hello,
    I have a session bean which is consuming entity bean and session bean is published as webService now when I call create method of entity bean from session bean it says "Exception in method com.syntel.exam_tool.entityBeans.tabExamTable.TabExamLocalHomeImpl0.create()."
    But my create method of entity bean is blank I am not getting from where this exceptions is being thrown.
    below is the code from session bean wehre I am calling entity bean
    javax.naming.Context ctx;
    ctx = new InitialContext();
    TabExamLocalHome tabExamLocalHome = (TabExamLocalHome) ctx.lookup("java:comp/env/ejb/TabExamBean1");
    TabExamLocal tabExam = tabExamLocalHome.create();
    Please help me ins this problem.
    Thanks

    Hi Janeth,
    below is the stack trace
    com.syntel.exam_tool.entityBeans.tabExamTable.TabExamLocalHomeImpl0_0.create(TabExamLocalHomeImpl0_0.java:343)
    com.syntel.exam_tool.sessionBeans.examTool.ExamToolBean.findByPassingScore(ExamToolBean.java:126)
    com.syntel.exam_tool.sessionBeans.examTool.ExamToolLocalLocalObjectImpl0_0.findByPassingScore(ExamToolLocalLocalObjectImpl0_0.java:247)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    java.lang.reflect.Method.invoke(Method.java:324)
    com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
    com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
    com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
    com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
    SoapServlet.doPost(SoapServlet.java:51)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    java.security.AccessController.doPrivileged(Native Method)
    com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    please help me in this as I am not getting where the problem is
    Edited by: new to netweaver on Sep 9, 2009 11:15 AM

  • Receiving Error "Exception Occurred !" when attaching files to Test Manager

    We are receiving the error "Exception Occurred!" when attaching files to Test Manager under issues.
    Error Message:
    +"Exception Occurred !"+
    No Permission to perform this action
    I'm not sure if this is a permission issue or not on our end.
    Here are the log entries from the debug and server logs.
    Error Message from debugweb_07_16_09.log file:
    +11:57:02:523 - TMJava addAttachment(): Unknwon exception thrown - avoiding program exit during save attachment of Issue node '42'+
    Error Message from server.log file:
    +2009-07-16 11:57:02,523 INFO [STDOUT] oracle.oats.otm.util.TMException+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at oracle.oats.otm.web.util.AttachmentAction.addAttachment(Unknown Source)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at java.lang.reflect.Method.invoke(Unknown Source)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at oracle.oats.otm.web.OracleActionBase.execute(Unknown Source)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at oracle.oats.otm.web.ActionServlet.process(Unknown Source)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at oracle.oats.otm.util.RequestEncodingFilter.doFilter(Unknown Source)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:138)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)+
    +2009-07-16 11:57:02,523 INFO [STDOUT]      at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)+
    +2009-07-16 11:57:02,601 INFO [STDOUT]      at java.lang.Thread.run(Unknown Source)+
    +2009-07-16 11:57:02,601 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: Forward Name = failure, Path =/jsp/Exception.jsp+
    +2009-07-16 12:05:32,926 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: --Action=/displayAttachment.do: AttachmentAction.displayAttachment()+
    +2009-07-16 12:05:33,082 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: Forward Name = success, Path =/jsp/AttachmentForm.jsp+
    +2009-07-16 12:05:34,645 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: --Action=/displayUploadAttachment.do: AttachmentAction.displayUploadAttachment()+
    +2009-07-16 12:05:34,645 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: Forward Name = success, Path =/jsp/UploadFileForm.jsp+
    +2009-07-16 12:05:53,067 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: --Action=/addAttachment.do: AttachmentAction.addAttachment()+
    +2009-07-16 12:05:53,067 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: File NameC:\Documents and Settings\dfitzgerald\Desktop\TestErrorPleaseDelete.jpg+
    +2009-07-16 12:05:53,067 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: File size12683+
    +2009-07-16 12:05:53,208 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: nodeId returned : -1+
    +2009-07-16 12:05:53,208 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[otm]] action: null+

    Alex,
    We're using SQL Server and OTM 8.50.0233.
    I've tried uploading jpg and bmp images.
    Thanks

  • Transaction Aborted Exceptions are seen when service downloading data

    Hi,
    We are getting two different types of exceptions while one service trying to download data from another service
    There are two scenarios where we are getting these transaction exceptions that are seen when client's service downloads data from server's service.
    1. The first kind of transaction exception is seen when service is trying to send the message to messaging queue in the InitialReceiveNext() method. The queue.send method throws this exception and the stack trace is as mentioned below:
    04 Jun 2014 19:16:12,805 [BridgeExchanger] TRACE - Sending queue message 00000000-0000-0000-0000-000000000000\0 to queue private$\msgqueue
    04 Jun 2014 19:16:12,806 [ClientBridgeEndpoint] ERROR - Error occurred during Receive!
    System.Transactions.TransactionException: The operation is not valid for the state of the transaction. ---> System.TimeoutException: Transaction Timeout
    — End of inner exception stack trace —
    at System.Transactions.TransactionState.Promote(InternalTransaction tx)
    at System.Transactions.Transaction.Promote()
    at System.Transactions.TransactionInterop.ConvertToOletxTransaction(Transaction transaction)
    at System.Transactions.TransactionInterop.GetDtcTransaction(Transaction transaction)
    at System.Messaging.MessageQueue.StaleSafeSendMessage(MQPROPS properties, IntPtr transaction)
    at System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransaction internalTransaction, MessageQueueTransactionType transactionType)
    at CI.Platform.Bus.Bridge.Client.BridgeExchanger.InitialReceiveNext(DownloadEndpoint endpoint)
    at CI.Platform.Bus.Bridge.Client.BridgeExchanger.ReceiveNext()
    at CI.Platform.Bus.Bridge.Client.ClientBridgeEndpoint.Exchange(Object state)
    2. The second kind of exception is seen at the transaction.complete statement in the InitialReceiveNext() method. The stack trace is as shown below:
    04 Jun 2014 23:15:59,152 [BridgeExchanger] DEBUG - Skipping the download message as the message is already downloaded..No new message is added to queue private$\msgqueue
    04 Jun 2014 23:15:59,153 [ClientBridgeEndpoint] ERROR - Error occurred during Receive!
    System.Transactions.TransactionAbortedException: The transaction has aborted. ---> System.TimeoutException: Transaction Timeout
    — End of inner exception stack trace —
    at System.Transactions.TransactionStateAborted.BeginCommit(InternalTransaction tx, Boolean asyncCommit, AsyncCallback asyncCallback, Object asyncState)
    at System.Transactions.CommittableTransaction.Commit()
    at System.Transactions.TransactionScope.InternalDispose()
    at System.Transactions.TransactionScope.Dispose()
    at CI.Platform.Bus.Bridge.Client.BridgeExchanger.InitialReceiveNext(DownloadEndpoint endpoint)
    at CI.Platform.Bus.Bridge.Client.BridgeExchanger.ReceiveNext()
    at CI.Platform.Bus.Bridge.Client.ClientBridgeEndpoint.Exchange(Object state)
    If anybody has any insight please reply.
    Thanks in advance!!!

    Hello,
    Your two questions are both related to MSMQ forum. Please post threads on that forum for more effective response. Please refer to
    http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=msmq. Thank you for understanding.
    Regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Error Connecting to database URL jdbc:oracle:oci:@rmsdbtst as user rms13 java.lang.Exception:UnsatisfiedLinkError encountered when using the Oracle driver

    Trying to Install RMS application 13.2.2 and I get past the pre-installation checks and when I get to the Data Source details and enter the data source details with the check box checked to validate the schema/Test Data Source I get the following error:
    Error Connecting to database URL jdbc:oracle:oci:@rmsdbtst as user rms13 java.lang.Exception:UnsatisfiedLinkError encountered when using the Oracle driver. Please check that the library path is set up properly or switch to the JDBC thin client oracle/jdbc/driver/T2CConnection.getLibraryVersioNumber()
    Checks performed:
    RMS Application code location and directory contents:
    [oracle@test-rms-app application]$ pwd
    /binary_files/STAGING_DIR/rms/application
    [oracle@test-rms-app application]$ ls -ltr
    total 144
    -rw-r--r-- 1 oracle oinstall   272 Dec 7  2010 version.properties
    -rw-r--r-- 1 oracle oinstall   405 Jan 16 2011 expected-object-counts.properties
    -rw-r--r-- 1 oracle oinstall   892 May 13 2011 ant.install.properties.sample
    -rw-r--r-- 1 oracle oinstall 64004 Jun  6  2011 build.xml
    drwxr-xr-x 9 oracle oinstall  4096 Jun 16 2011 rms13
    drwxr-xr-x 3 oracle oinstall  4096 Jun 16 2011 installer-resources
    drwxr-xr-x 3 oracle oinstall  4096 Jun 16 2011 antinstall
    drwxr-xr-x 2 oracle oinstall  4096 Jun 16 2011 ant-ext
    drwxr-xr-x 5 oracle oinstall  4096 Jun 16 2011 ant
    -rw-r--r-- 1 oracle oinstall 11324 Dec 18 09:18 antinstall-config.xml.ORIG
    -rwxr-xr-x 1 oracle oinstall  4249 Dec 18 10:01 install.sh
    drwxr-xr-x 4 oracle oinstall  4096 Dec 18 10:06 common
    -rw-r--r-- 1 oracle oinstall 16244 Dec 19 10:37 antinstall-config.xml
    -rw-r--r-- 1 oracle oinstall   689 Dec 19 10:37 ant.install.log
    [oracle@test-rms-app application]$
    Application installation:
    [oracle@test-rms-app application]$ ./install.sh
    THIS IS the driver directory
    Verified $ORACLE_SID.
    Verified SQL*Plus exists.
    Verified write permissions.
    Verified formsweb.cfg read permissions.
    Verified Registry.dat read permissions.
    Verified Java version 1.4.2.x or greater. Java version - 1.6.0
    Verified Tk2Motif.rgb settings.
    Verified frmcmp_batch.sh status.
    WARNING: Oracle Enterprise Linux not detected.  Some components may not install properly.
    Verified $DISPLAY - 172.16.129.82:0.0.
    This installer will ask for your "My Oracle Support" credentials.
    Preparing installer. This may take a few moments.
    Your internet connection type is: NONE
    Integrating My Oracle Support into the product installer workflow...
         [move] Moving 1 file to /binary_files/STAGING_DIR/rms/application
    Installer preparation complete.
    MW_HOME=/u01/app/oracle/Middleware/NewMiddleware1034
    ORACLE_HOME=/u01/app/oracle/Middleware/NewMiddleware1034/as_1
    ORACLE_INSTANCE=/u01/app/oracle/Middleware/NewMiddleware1034/asinst_1
    DOMAIN_HOME=/u01/app/oracle/Middleware/NewMiddleware1034/user_projects/domains/rmsClassDomain
    WLS_INSTANCE=WLS_FORMS
    ORACLE_SID=rmsdbtst
    JAVA_HOME=/u01/app/oracle/jrockit-jdk1.6.0_45-R28.2.7-4.1.0
    Launching installer...
    To make sure I have connectivity from the app server to the database (on a database server) here are the steps followed:
    [oracle@test-rms-app application]$ tnsping rmsdbtst
    TNS Ping Utility for Linux: Version 11.1.0.7.0 - Production on 19-DEC-2013 10:41:40
    Copyright (c) 1997, 2008, Oracle.  All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = test-rms-db.vonmaur.vmc)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SID = rmsdbtst)))
    OK (0 msec)
    [oracle@test-rms-app application]$
    [oracle@test-rms-app application]$ sqlplus rms13@rmsdbtst
    SQL*Plus: Release 11.1.0.7.0 - Production on Thu Dec 19 10:46:18 2013
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Enter password:
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@test-rms-app application]$
    [oracle@test-rms-app application]$ ping test-rms-db
    PING test-rms-db.vonmaur.vmc (192.168.1.140) 56(84) bytes of data.
    64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=1 ttl=64 time=0.599 ms
    64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=2 ttl=64 time=0.168 ms
    64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=3 ttl=64 time=0.132 ms
    64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=4 ttl=64 time=0.158 ms
    64 bytes from test-rms-db.vonmaur.vmc (192.168.1.140): icmp_seq=5 ttl=64 time=0.135 ms
    --- test-rms-db.vonmaur.vmc ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4001ms
    rtt min/avg/max/mdev = 0.132/0.238/0.599/0.181 ms
    [oracle@test-rms-app application]$
    [oracle@test-rms-app application]$ uname -a
    Linux test-rms-app.vonmaur.vmc 2.6.18-128.el5 #1 SMP Wed Jan 21 08:45:05 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
    [oracle@test-rms-app application]$
    [oracle@test-rms-app application]$ cat /etc/*-release
    Enterprise Linux Enterprise Linux Server release 5.3 (Carthage)
    Red Hat Enterprise Linux Server release 5.3 (Tikanga)
    [oracle@test-rms-app application]$
    The database is created and all the batch file scripts have been successfully deployed.  Now working on the application server.  The  Weblogic server is installed and 11g forms and reports are installed successfully.
    Any help would be helpful.
    Thanks,
    Ram.

    Please check MOS Notes:
    FAQ: RWMS 13.2 Installation and Configuration (Doc ID 1307639.1)

  • I used an American Express card to purchase my Ipad from Apple online. I have an Apple ID. why can't I use Amex as my payment method when signing in to Itunes?

    I have an Apple ID, created when I recently purchased an ipad from Apple online. I used my Amex as payment method. Why can I not use my Amex as payment method when signing in to iTunes for the first time?

    Yup, I'm a Kiwi, living in sunny Blenheim. Just seems odd that I can use Amex for purchasing in the Apple store but not in the iTunes store. Perhaps the higher charge set by Amex is not  economic for small purchases? Anyway,
    I know now what to do now - buy an iTunes gift card and enter the activation code to redeem and sign up. Sorted! Thanks Kappy for taking an interest in my query.

  • Xi 3.0: Mail adapter fails with "exception in method process"

    Hi.
    I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
    Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
    I tried both async and sync case with the same result. In the sync case, the response contains:
    <!--  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="PARSING">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Any idea???

    Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
    Anyway, in my server i get a 404 for the link you suggested.
    In the async case i don't get any error on the SXMB_MONI but only on the A.F.
    I attach the audit log for the async case:
    Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
    Time Stamp Status Thread ID Sequence No. Description
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
    2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
    2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
    2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
    2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint 
    2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
    2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
    2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint 
    2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
    2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
    2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
    2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
    2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
    2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
    2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint 
    2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
    2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
           Total: 33 Entries   1020304050 messages displayed per page; this is page 1 of  1 page(s)     

  • How to pick consignment stock @ FIFO method when involved multiple vendors

    Dear Guru s ,
    I need some information/ logic  on how to pick consignment stock @ FIFO method when involved multiple vendors (who supplies consignement goods) .
    1)We have tried to determine the vendor @ FIFO method from the material document date & time   with 101 K  mvmt type
    2) when we check MSEG table we are unable to get the current stock updates .For example Vendor A stock is showing 60 KG in MMBE , but MSEG is showing only 45 KG for the same vendor & storage location  .
    Can anyone provide me the logic / info on the same.
    Thanks
    Anil

    Hi Anil
    MMBE will show you total stock, your logic is correct , you can go for MSEG , but you need to add opening stock for that material for the period.
    Suppose you are looking for report between 2nd august to 10 august , then you need to take opening stock on 2nd august and then add all goods receipt( 101 k) between 2nd to 10th and you will get correct stock on 10th ( same as MMBE)
    Note : I am assuming that current date is 10th august. If you want to see stocks on particular date then go for MB5B.
    Now as per your requirement , you can identify goods movement based on FIFO , follow same logic , pick time and date from MSEG for 101 k movement type.
    Regards
    Ravi.

  • When we have to go for session method, when we have to go for call transact

    when we have to go for session method, when we have to go for call transaction method if i have a 3000 records in flat file. which is better? why

    Data Transfer
    During the process of data transfer, data is transferred into the SAP R/3 System. This transfer is from an external system to SAP R/3 system. Whenever you transfer data from an external system into an R/3 System, you can use data transfer because it is installed and regularly transfers data from an external system into an R/3 System.
    As discussed, with the help of BDC, you can transfer the required data from a non-SAP system to an SAP system. For this kind of data transfer you are required to write an ABAP program. This ABAP program would help to export the concerned data to a sequential dataset file. The data in this file has to be stored. This should be stored in a format, which is acceptable to SAP batch input program. But, to transfer data from a SAP system to another SAP system, you can take the aid of RFC or CPI-C.
    SAP application supports the data transfer of numerous SAP business objects. The said data transfer program specifies the data format definition, which is necessary to import the data into the R/3 System. There are three methods available for transferring data:
    Direct Input:
    In this method the SAP function modules execute the consistency checks. However, there are other means of checking with the help of screens. The Direct Input Method has considerable performance advantages.
    Call Transaction:
    In this method you can check the data consistency with the help of screen logic.
    Batch Input Session:
    In this method data consistency is checked with the help of screen logic.
    Direct Input Method
    Among the methods of data transfer through BDC, direct input method is the one that is used, especially in case of transferring large amount of data. In order to enhance the batch input procedure, the system offers you with the direct input technique.
    There is a distinction between the batch input technique and this technique. Unlike batch input technique, this technique does not create sessions. Instead, it stores the data directly. Moreover, it does not process screens. The data has to be entered directly into the corresponding database tables. The system calls a number of function modules which execute necessary checks, if any required. In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.
    Call Transaction Method
    Call Transaction method is another method used for Data Transfer. In this type of method your program will use the ABAP statement CALL TRANSACTION USING in order to run a SAP transaction. In this type external data need not be deposited in a session for being processed later on. Instead, the entire batch input process takes place inline in your program.
    Here, the data transfer program must convert the data that has to be transferred into the SAP system. This is as per requirement by the SAP data structure or the transaction which is using it. It is to be remembered that a conversion of the data types may be necessary at different times during the process.
    Suppose there is a data type mismatch then you have to convert the data types to type C. In this regard the data transfer program should be capable of exporting the data in SAP format to the sequential file. At the time of uploading the data into the SAP system, the BDC program reads the data from the abovementioned sequential file.
    Batch Input Session Method
    This is the third method for data transfer. If you use the batch input method to transfer data, then you should remember that an ABAP program has to read the external data which is to be entered in the R/3 System. Subsequently, it stores the concerned data a "batch input session." The batch Input session records the actions which are required in the process of transferring data into the system. This can be done by using normal SAP transactions.
    As soon as the program generates the said session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:
    System à Services à Batch input. Moreover, you can have the session run in the background processing.
    Writing a Data Transfer Program
    If you want to write a data transfer program, you have to follow the steps mentioned below.
    Firstly, you will analyze the structure of the existing data. Subsequently, your job is to specify the conversions, which are essential to fill the SAP data structures.
    Secondly, you have to generate the SAP data structure. In case the program is written in ABAP, you will require only the required tables in the concerned program with the help of TABLES statement.
    Thirdly, you will have to initialize the SAP data structure.
    Fourthly, fill the structure with data, performing any conversions and error checking that are required.
    Finally, you will write the sequential file. In the SAP system this sequential file is typically required for making the data available to the batch input program.
    Batch Input Method
    Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.
    There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.
    The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.
    The process flows for a batch input are discussed below.
    Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.
    Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).
    Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.
    Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.
    Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need to be involved.
    Error Handling in Batch Input Method
    It is found that most problems usually fall into one of the following two categories discussed below.
    In this case either required data is missing from the batch-input session or invalid data has been included in the session. Errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database are the possible external causes of this type of problem. Within R/3, the causes for this type of problem include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.
    This case mainly includes technical/programming problems. The data is entered by a batch input session by running R/3 transactions non-interactively. Therefore, a typical technical or programming problem is the incorrect identification of one of the data fields in a transaction. Thus, the conversion program may not fill a required data field or may have provided invalid values.
    Conclusion
    I have gone through the details of batch data communication and various methods used to transfer data. One can make use of BDC to transfer data from a SAP to SAP system. In addition, it can transfer data from a non SAP system to SAP system too. I have discussed the various methods of BDC and the error handling in the respective methods.
    Thanks,
    Shankar

  • Exception in method process

    Hi all,
    I am configuring a scenario RFC -> XI -> Webservice. In my SOAP adapter trace, i found an error :
    <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: Exception in method process.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can any body please suggest me the possible reasons?
    Thanks and best regards,
    Kulwant

    try this too
    com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process
    and  this
    com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process ?
    Edited by: Lawrence on Apr 22, 2008 8:17 AM

  • SOAP Adapter:  Exception in method process

    Hello Experts,
    We are getting from time to time on the Receiver SOAP Communication Channels the folowing error:
    Delivery of the message to the application using connection AFW failed, due to: Exception in method process.
    We are getting this error on both types of messages - sync  and async.
    I did a search on SDN and Notes, but didn't found any description or solution for this error.
    Can someone please help with this error?
    Thanks in advance!

    Here are some details extracted from the log:
    Date : 07/30/2008
    Time : 8:44:15:783
    Message : Error during processing local bean: localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    Severity : Error
    Category :
    Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
    Application : sap.com/com.sap.aii.af.app
    Thread : output
    Datasource : 1217412862462:/usr/sap/xxx/xxx/j2ee/cluster/server1/log/defaultTrace.trc
    Message ID : 001CC4B7988E00A5000268B100000CB3000453381549AFAE
    Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
    Argument Objs :
    Arguments :
    Dsr Component : xxx
    Dsr Transaction : 989219405e0211ddc88b001cc4b7988e
    Dsr User : Guest
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives :
    Resource Bundlename :
    Session : 0
    Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
    ThreadObject : output
    Transaction : SAP J2EE Engine JTA Transaction : [2dffffff91ffffffbdffffffe3040ffffffb0]
    User : J2EE_GUEST
    Hope this will help somebody to get the clue what is causing this error.

  • SRT Framework exception: ICF: Error when creating service node. [rc:wrong_icf_name] No special characters allowed in name

    Hi,
    I have created a web service in SAP ECC from a RFC.
    While configuring the web service in SOA management to publish it, getting error SRT Framework exception: ICF: Error when creating service node. [rc:wrong_icf_name] No special characters allowed in name
    How to resolve the same.
    Thanks
    Tanmay

    Hello Tanmay,
    Are you including quotes (') in the name, I assume not?
    Regards,
    Siddhesh

Maybe you are looking for