Error executing Interactive Form

I have an issue when I execute a WD that has an Adobe Document.
<br><br>
In the first place, the WD works properly in a PRD environment (in a primary and secondary instances). I made some changes to it (added another PDF, similar to the prior one) and this new version was deployed in PRD. The result was that when WD was executed, it works well on the first instance, but when you try the second instance it shows the following error:
<br><br>
I don't understand what could be happening. the server (both instances) posses the same configuration, they both work with the older WD version, but the secondary instance won't work with the new one.
<br><br>
There's something else that might be important; when the new version is deployed, ANOTHER WD (from a different project) that also uses Adobe Forms starts showing the same error (and this new application wasn't even modified). If you deploy the older version once more, everything goes back to normal without further errors.
<br><br>
Thank you!
<br><br>
com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to  UPDATEDATAINPDF
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:419)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process Render Request.
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:100)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:123)
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:340)
     ... 29 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.ConnectException: Connection refused
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:408)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.render(PDFObject.java:3944)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRenderHandler.handle(PDFDocumentRenderHandler.java:148)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
     ... 32 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
     java.net.ConnectException: Connection refused
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:84)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:94)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:385)
     ... 35 more
Caused by: java.net.ConnectException: Connection refused
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:464)
     at java.net.Socket.connect(Socket.java:414)
     at java.net.Socket.<init>(Socket.java:310)
     at java.net.Socket.<init>(Socket.java:125)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:682)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:504)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:461)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:408)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1433)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:77)
     ... 37 more

java.rmi.RemoteException: Service call exception; nested exception is: java.net.ConnectException:
This exception normally occurs when the consumer (WD application) is not able to communicate/connect to the producer (Web Service). Take help of Security/BASIS Team for further analysis. Also compare the changes are you making in your old application to new.
Chintan

Similar Messages

  • Got deploment error with Interactive forms

    Hi Frnds,
    Jus now i instelled ADS(Acrobat designer lifcy), n i did't made any changes in sld r vis admin ,i want to genrate a reports in PDF formate , so i designed a view with Interactive forms n i deployed ,igot this error
    com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found. The request URL was:"<http://localhost:50000/AdobeDocumentServices/Config?style=document>". Check, whether the URL is correct, and the Web Service that you are requesting is up and running
    is it necessary to made a changes @ SLD n visual admin
    thanks & regards

    Hi
    Open the j2ee engine web page and go to web service navigator --
    http://<servername>:<port>/wsnavigator.
    there should be a ADS webservice there. you should be able to execute it successfully. if it is not present then it means ADS service is not installed on your server.

  • Adobe error with interactive forms

    Hello,
    we are trying to make a customer interactive form on the SAP Discovery system, everthing works fine until we try to run a preview with interactive and changeble parameters turned on. By the way there is a SAP provided credential on the system.
    the following error occurs while calling the ADS;
    <b>first error message:</b>
    error while logging into credential 'GeneralError: Operation failed.
    SecurityHandler.login:-1:
    The Digital ID specified is unknown.
    Date : 03/23/2007
    Time : 16:04:56:997
    Message : error while logging into credential 'GeneralError: Operation failed.
    SecurityHandler.login:-1:
    The Digital ID specified is unknown.
    Severity : Error
    Category :
    Location : com.adobe.document.PDFManipulation
    Application :
    Thread : SAPEngine_Application_Thread[impl:3]_30
    Datasource : 103929350:D:\usr\sap\ERP\DVEBMGS10\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 0018FEFB4E8F00710000013D0000160000042C5960F15BB3
    Source Name : com.adobe.document.PDFManipulation
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : dcf0bd50d94f11db8e950018fefb4e8f
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives :
    Resource Bundlename :
    Session : 0
    Source : com.adobe.document.PDFManipulation
    ThreadObject : SAPEngine_Application_Thread[impl:3]_30
    Transaction :
    User : J2EE_GUEST
    <b>second eror message:</b>
    Date : 03/23/2007
    Time : 16:04:57:013
    Message : Processing exception during a "UsageRights" operation.
    Request start time: Fri Mar 23 16:04:53 CET 2007
    com.adobe.ProcessingError: Credential login error while applying usage rights to PDF: C:\WINDOWS\Temp\adobewa_ERP_103929350\DM-8398477217709800775.dir\DM-8673971829680153343.tmp
    Specific error information:
    $$$/PDF/PDFCredentialLoginFailure2=error while logging into credential '^0'
    GeneralError: Operation failed.
    SecurityHandler.login:-1:
    The Digital ID specified is unknown.
    General error information:
    IDL:com/adobe/document/pdf/CredentialLoginFailure:1.0
    Severity : Error
    Category : /System/Server
    Location : com.adobe.AdobeDocumentServicesWorker
    Application : com.adobe/AdobeDocumentServices
    Thread : SAPEngine_Application_Thread[impl:3]_27
    Datasource : 103929350:D:\usr\sap\ERP\DVEBMGS10\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 0018FEFB4E8F0067000001290000160000042C5960F1B348
    Source Name : com.adobe.AdobeDocumentServicesWorker
    Argument Objs :
    Arguments :
    Dsr Component : IWDFVM2160.wdf_ERP_103929350
    Dsr Transaction : d5fe2cd2d94f11db90b20018fefb4e8f
    Dsr User : ADSUSER
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : /System/Server
    Resource Bundlename :
    Session : 11645
    Source : com.adobe.AdobeDocumentServicesWorker
    ThreadObject : SAPEngine_Application_Thread[impl:3]_27
    Transaction : SAP J2EE Engine JTA Transaction : [631ffffffd66002b7d]
    User : ADSUSER
    <b>third error message:</b>
    Date : 03/23/2007
    Time : 16:04:57:013
    Message : Client: 200 SystemId: ERP AppName: SAFP
    Processing exception during a "UsageRights" operation.
    Request start time: Fri Mar 23 16:04:53 CET 2007
    com.adobe.ProcessingError: Credential login error while applying usage rights to PDF: C:\WINDOWS\Temp\adobewa_ERP_103929350\DM-8398477217709800775.dir\DM-8673971829680153343.tmp
    Specific error information:
    $$$/PDF/PDFCredentialLoginFailure2=error while logging into credential '^0'
    GeneralError: Operation failed.
    SecurityHandler.login:-1:
    The Digital ID specified is unknown.
    General error information:
    IDL:com/adobe/document/pdf/CredentialLoginFailure:1.0
         at com.adobe.ads.request.UsageRights.execute(Unknown Source)
         at com.adobe.BaseADSRequest.doWork(Unknown Source)
         at com.adobe.AdobeDocumentServicesWorker.execute(Unknown Source)
         at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source)
         at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source)
         at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0.java:120)
         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.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.adobe.document.pdf.CredentialLoginFailure: IDL:com/adobe/document/pdf/CredentialLoginFailure:1.0
         at com.adobe.document.pdf.CredentialLoginFailureHelper.read(CredentialLoginFailureHelper.java:67)
         at com.adobe.document.pdf._PDFDocumentStub.setUsageRights(_PDFDocumentStub.java:284)
         at com.adobe.EJB_PDFAgent.setUsageRights(Unknown Source)
         ... 31 more
    Severity : Fatal
    Category :
    Location : com.adobe.AdobeDocumentServices
    Application : com.adobe/AdobeDocumentServices
    Thread : SAPEngine_Application_Thread[impl:3]_27
    Datasource : 103929350:D:\usr\sap\ERP\DVEBMGS10\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 0018FEFB4E8F00670000012A0000160000042C5960F1B5C1
    Source Name : com.adobe.AdobeDocumentServices
    Argument Objs :
    Arguments :
    Dsr Component : IWDFVM2160.wdf_ERP_103929350
    Dsr Transaction : d5fe2cd2d94f11db90b20018fefb4e8f
    Dsr User : ADSUSER
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives :
    Resource Bundlename :
    Session : 11645
    Source : com.adobe.AdobeDocumentServices
    ThreadObject : SAPEngine_Application_Thread[impl:3]_27
    Transaction : SAP J2EE Engine JTA Transaction : [631ffffffd66002b7d]
    User : ADSUSER
    Hopefully these messages will ring a bell and some of you have a solution for this problem.
    Manny thanx in advance
    Jasper Brugman

    Hi Jasper,
    The Adobe credential on your NetWeaver seems to be expired or not applied.
    Go to the quick guide :  https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b22d4e44-0e01-0010-ffa4-fe9c59939e5e
    On page 33-34 , it explains you how to applied again the adobe credentials.
    Regards,
    Gilles

  • Error in Interactive form

    Trying to explore interactive forms on ECC 5.0 as very new to this field.
    Used T-code 'SFP' to view the standard Form 'MEDRUCK_PO'.
    When executing, during print previw provided the the default printer name in out put device but got following Error message
    "Device type unsuitable for ADS documents"
    Further function module gave message
    'Cannot find PDL type for output device '.
    what could be the reason do i have to do some settings for output device.
    Checked SPAD also
    Sapscript Handling : SWIN
    check box : Page printer is ticked
    Printer Deriver : Do not print ABAP lits
    Kindly resolve
    thanks
    anu

    hi all
    im also facing the same problem as above.
    ive read the sap note and did the following.
    1. went to se38 and ran report RSPO0022.
    2. in the o/p screen: activity to be performed -> Create/change XDC entry
        SAP Device Type->HPPCL5E.
    3. F8
    4. Open filename ->hppcl5e.xdc (from the Adobe folder)
    5. asks to create a new transport request. which i did.
    6. go back to SFP and Execute. Gave printer name as HPPCL5E. but error says: Device HPPCL5E doesnot exist.
    am i missing anythin here guys??
    pls suggest.
    pk

  • Error for Interactive Forms

    Good Day Experts,
    We are experiencing a problem in deploying a Web DynPro Java Application with Adobe Interactive Forms.
    Here is the error:
    "Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://nw2004s:50100/AdobeDocumentServices/Config?style=document"
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:985)"
    What are the possible causes of this error? Can someone please help solve this error. Thanks!

    Hi Shaira Madhu
    I am having problem with Submit button in Online Adobe Form. Please help. When i click on Submit button its giving an error
    which is Error code : WSDL file( i am calling Web services)
    Thanks

  • Error in Interactive Forms

    Hi,
    I m trying out the tutorial "Interactive Forms Integration into Web Dynpro for Java". When I deploy the application i am getting the following error :
    java.lang.Exception: Incorrect content-type found 'text/html'
    Can anyone pls help me solve it?
    Thanks,
    Malita

    hi
    your server is not properly configured for the adobe interactive form...........
    contact the basis people and check the configuration with the appropriate SAP note
    xxxxxxxxxxxxxx
    Warm Regards
    Shanto Aloor
    Edited by: Armin Reichert on Apr 26, 2008 6:59 PM

  • Execute Interactive form with JSPDynPage component

    Hi all,
    I need to use interactive forms in my project.
    Can i use interactive forms in my JSPDynpage components?
    Regards
    Gabriel García.

    Hi,
    A Presentation from tech ed
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/26e9dc90-0201-0010-a790-a7048c8bba95
    A blog
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/88e7ea34-0501-0010-95b0-ed14cfbeb85a
    Adobe Online Interactive Forms Integration into Web Dynpro for Java Applications - Webinar Details
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cf8dc795-0801-0010-ae97-af93a0795b3f
    Regards
    Ayyapparaj

  • ACF ActiveX error Adobe Interactive Forms

    my enviornment
    server:  windows 2003
    WebAS 6.40 SR1 SP9
    ADS 1.00 SR1 SP9
    (all configured according to ads installation
    and configuration guides, installed adobe
    credentials file and checked password,
    ADSCallers group, ADSUser security role
    assigned, basic authentication set up)
    client(s)
    windows XP home SP2
    windows XP professional SP2
    windows 2000 SP4
    all clients have ACF installed from xACF.exe
    file dated 2-2-2005
    Adobe Reader 6.0.2
    IE 6.0 (all ActiveX options enabled)
    get the same error on all clients
    from Microsoft script debugger
    CSF.api.acf.notifyHooked("EGPD.InteractiveView.InteractiveForm2")
    are there different versions of xACF.exe out there
    i know the xACF_11.exe will not work with SR1 SP9

    If you are at a point in your development cycle where it is feasible, I recommend that you update to SP11.  There were several issues that you may come across later in your testing that were resolved with sp10 and sp11.  (I would have to dig through our list of bugs/fixes if you would like specifics.)Also, with the 7.0.0 client, the client interaction with IE is much more stable.  We had many issues with Reader 6.0.2.  6.0.3 seemed to correct some, but not all. (IE would abnormally terminate when submitting forms or when cancelling forms).
    We have not worked with SP9 since before the beginning of the year. We implemented SP10 in late December/early January, and saw improvement. We upgraded to sp11 in March (actually had an early version to test with prior to that) and have seen much improvement in the behavior of the client pieces as well as some server side issues with both 6.0.3 clients and especially with 7.0.0 clients.  (I understand that your issues now appear to be compatibility between client and ads server, so they may or may not be resolved this way).  We are currently running SP11 (with additional note 766191 for the latest xacf files), Reader 7.0.0 and 7.0.1, IE 6 on a combination of XP SP1/SP2 and win2k clients.   The added bonus is that the client dll's are automatically downloaded at runtime as of SP10.  (and are signed controls, so you can tighten up your browser security). This is a recommedation from a fellow tester, Matthias is the ultimate guru.

  • Multi language support for Adobe interactive form

    Hi ,
      I translated the adobe form in multi language in SE63, If i execute the form with passing LANGU(language) parameter, form supports for multi language.
    I created XML schema based interface and if a execute interactive form in Webdynpro, i am unable to pass launguage(LANGU) parameter.  because InteractiveForm element property does not have language key parameter.
    Apart from creating different language dependent forms, is there any alternate way we can pass the LANGU key parameter to Interactive Adobe form???

    Hi Thomas
    Let me share my few more investigation on the same, I chaged form each element property to login language.
    and translated form to other languages. If directly execute form in sfp with loging in different language i am getting right result. it means even no need to pass the LANGU parameter.
    But same thing if i execute from Webdynpro i am getting default 'EN' language form, even though i login in 'DE' language.

  • Multi language support for Adobe interactive form in ABAP WD

    Hi ,
    I translated the adobe form in multi language in SE63, If i execute the form with passing LANGU(language) parameter, form supports for multi language.
    I created XML schema based interface and if a execute interactive form in ABAP Webdynpro, i am unable to pass launguage(LANGU) parameter. because InteractiveForm element property does not have language key parameter.
    Apart from creating different language dependent forms, is there any alternate way we can pass the LANGU key parameter to Interactive Adobe form???

    Hi,
    As far as i know when you use Adobe forms in a WD4A application, language is your "web" connection language.
    You can have a look at standard class CL_WD_ADOBE_SERVICE, it's used when generating an adobe forms from WD4A. , more particulary look at method DETERMINE_DOCPARAMS.
    regards

  • Error while executing WebDynpro Application with Adobe interactive forms.

    I have created a webDynpro application which involves an adobe interactive form. When i deploy and run the application, i am able to deploy it on the J2EE engine on the EP server but while executing it, i get the following exception -
    <b>Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error during call to AdobeDocumentServer: Processing exception during a "UsageRights" operation. Request start time: Thu Oct 12 17:30:39 GMT+05:30 2006
        at com.sap.tc.webdynpro.clientserver.adobe.AdobeFormHelper.createPDFDocumentForUIElement(AdobeFormHelper.java:486)
        at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:185)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1154)
        at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:402)
        at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649)
        ... 21 more</b>
    I would appreciate any help in this matter.
    Thanks...

    Hi,
    Check the note in this site...
    https://websmp204.sap-ag.de/notes
    Regards,
    <i><b>Raja Sekhar</b></i>

  • Error while executing WD Application with a Interactive Form

    Hello All,
    I am trying to run an WD application on my local j2ee engine in which i have added an Interactive form( i have added only static text in that ), but when i test the application it is throwing an error like:
    The initial exception that caused the request to fail, was:
       java.net.ConnectException: Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:461)
    And i am able to run the rpData webservice individually with the same user name (administrator )
    Could any one suggest me how to run my application on my local engie.
    Thanks & Regards,
    Trikanth

    Dear Trikanth,
    are you sure you have added the Administrator user to the ADSCaller Security role?
    Visual Admin -> Server node -> Services -> Security Provider -> com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar
    Best regards,
    Dezso

  • Error while executing ADobe Interactive form

    Hi
    I had created TRAVEL REQUEST interactive form as per the document.   Im successful till deployment.  But then while running the application Im getting the below stack
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to created delegate
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:51)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doInit(ClientComponent.java:748)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:333)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:341)
         at com.sap.tc.webdynpro.clientserver.task.Task.createApplication(Task.java:181)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:494)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:49)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:239)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:130)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:92)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:35)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:373)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:250)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:321)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:299)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:698)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:223)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:146)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
    Caused by: java.lang.reflect.InvocationTargetException
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:43)
         ... 26 more
    Caused by: java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.context.Node.<init>(Lcom/sap/tc/webdynpro/progmodel/context/NodeInfo;Lcom/sap/tc/webdynpro/progmodel/context/Node;)V
         at com.sap.demo.travelrequest.wdp.IPublicTravelRequestComp$IContextNode.<init>(IPublicTravelRequestComp.java:29)
         at com.sap.demo.travelrequest.wdp.InternalTravelRequestComp.wdInitContextNode(InternalTravelRequestComp.java:49)
         at com.sap.demo.travelrequest.wdp.InternalTravelRequestComp.<init>(InternalTravelRequestComp.java:89)
         ... 31 more
    Can any bode tell me whether it is Version incompatibility or any other specific reason ?
    thanks
    raj

    Hi Raja,
    something is wrong with your context in the component controller. Please verify your context structure with the structure in the document, which you mentioned. Do you really use value nodes and attributes? Is the mapping to the view correct and also the binding between the interactive form ui-element and the context nodes of the view?
    Regards, Carsten
    Message was edited by: Carsten Brandt

  • No such method error when launching the Interactive form

    Hi Experts,
    I have developed a simeple Java Webdynpro application and added an Interactive form without any controls in it. Created the context with one value node and a binary value attribute.
    I have assigned  value node to datasource and binary attribute to pdfSource. When I launch the application I am getting the following no such method error.
    java.lang.NoSuchMethodError: com/sap/tc/webdynpro/clientserver/uielib/adobe/api/IWDInteractiveForm.setTemplateSource(Ljava/lang/String;)V
    The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.
    If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.
    My NWDS is of Version 7.0.06
    and J2EE Engine is of Version 6.40.
    any guess why I am getting this error.
    Thanks
    Chinna.

    Issue solved. Compatablility issue NWDS 2.0 Version should use for NW 2004.

  • Error while running webdynpro application with an Interactive form

    Hi all,
    I am getting the following defect when I run a adobe interactive form (webdynpro application). Any pointers?
    Regards,
    Deepak
    500   Internal Server Error
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.net.ConnectException: Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:464)
        ... 47 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1)
    Version null
    DOM version null
    Client Type msie7
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Wed Oct 10 10:17:00 EDT 2007
    J2EE Engine 7.00 patchlevel 109044.44
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en_US
    Time of Failure Thu Oct 18 17:39:22 EDT 2007 (Java Time: 1192743562661)
    Web Dynpro Code Generation Infos
    local/NIBCOSecurityFormWD
    SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:26:06[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates (unknown)
    SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:13:54[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:11[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:42[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:35[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:23:29[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:28:49[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
    SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:21[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to  UPDATEDATAINPDF
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:418)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process Render Request.
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:100)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:123)
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:340)
         ... 29 more
    Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
         java.net.ConnectException: Connection refused: connect
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:408)
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.render(PDFObject.java:3948)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRenderHandler.handle(PDFDocumentRenderHandler.java:148)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
         ... 32 more
    Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
         java.net.ConnectException: Connection refused: connect
         at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:85)
         at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:95)
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:385)
         ... 35 more
    Caused by: java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
         at java.net.Socket.connect(Socket.java:464)
         at java.net.Socket.connect(Socket.java:414)
         at java.net.Socket.<init>(Socket.java:310)
         at java.net.Socket.<init>(Socket.java:125)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:648)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:470)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:427)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:355)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
         at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
         ... 37 more

    Hi Deepak,
    If you have solved the issue could you kindly close the thread with the solution as this will help others as well. If not kindly update the thread with the status.

Maybe you are looking for