Quering Engine db for process exception information

Hi,
I wanted to know if there is any API or a simple db query to query to engine database and find out information about whether an independent process has entered into an exception and send this information over to another process?
How can this be done?

You shouldn't query the Engine DB directly, but you can use PAPI or the ProcessService object and execute the getInstanceByFilter method. You can find ProcessService under fuego.papi. There are some docs to get you started there. To use PAPI I wrote a getting started guide here:
http://blog.ssglimited.com/2010/02/17/creating-oracle-bpm-papi-clients/
Hope that helps,
Mark
Edited by: Mark Peterson on Mar 3, 2010 2:33 PM

Similar Messages

  • Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

    In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service. Can anyone please
    help me.
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

    In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service.
    HI Arivazhagan K,
    Could you give some explanation about what you modified? according the to error message, this is "resource is not found issue".
    Best regards,
    Angie
    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.

  • Oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters

    Dear Guru's,
    I am not able to solve the above issue for last couple of days.
    I am newbie to the webservice
    My Issue...
    I am using Jdeveloper 11.1.2.4.0 Release 2
    1. Using Jdev I built one small Web Service with two methods.
            While testing the Webservice...
                   I passed User Id as Parameter and it successfully return the values (user id, user name and description) from fnd_user table
    2. I created another application to consume the web service i created.
                   1. I added the webservice SOAP and added the method.
                   2. Created a jsf page and drag and drop the parameter and return values to the jsf page.
    3. While executing the created jsf page I received the error message as below
    "oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters are {0=Attribute, 1=UserName, 2=UserName}"
    Even I know that this issue is repeated one in our forum, I was not able to solve this issue.
    Can anybody help to solve this issue.
    Thanks and Regards,
    Durai S E

    Dear Guru's,
    I am not able to solve the above issue for last couple of days.
    I am newbie to the webservice
    My Issue...
    I am using Jdeveloper 11.1.2.4.0 Release 2
    1. Using Jdev I built one small Web Service with two methods.
            While testing the Webservice...
                   I passed User Id as Parameter and it successfully return the values (user id, user name and description) from fnd_user table
    2. I created another application to consume the web service i created.
                   1. I added the webservice SOAP and added the method.
                   2. Created a jsf page and drag and drop the parameter and return values to the jsf page.
    3. While executing the created jsf page I received the error message as below
    "oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters are {0=Attribute, 1=UserName, 2=UserName}"
    Even I know that this issue is repeated one in our forum, I was not able to solve this issue.
    Can anybody help to solve this issue.
    Thanks and Regards,
    Durai S E

  • I want to download the "FREE" iPhoto duplicate remover software, but the download process keeps asking me for my payment information.

    I want to download the "FREE" iPhoto duplicate remover software, but the download process keeps asking me for my payment information. I have tried it several times.. But it says I cannot download this app unless I give my payment information.. So I went back and looked again and again.. and it still says it's "Free"...

    You need to contact the authors re download or payment issues - we are only users like yourself and help with iPhoto for the Mac issues
    here is Old TOad's list of potential packages including his comments
    These applications will identify and help remove duplicate photos from an iPhoto Library:
    iPhoto Library Manager - $29.95
    Duplicate Annihilator - $7.95 - only app able to detect duplicate thumbnail files or faces files when an iPhoto 8 or earlier library has been imported into another.
    PhotoSweeper - $9.95 - This app can search by comparing the image's bitmaps or histograms thus finding duplicates with different file names and dates.
    DeCloner - $19.95 - can find duplicates in iPhoto Libraries or in folders on the HD.
    DupliFinder - $7 - shows which events the photos are in.
    iPhoto AppleScript to Remove Duplicates - Free
    PhotoDedupo - $4.99 (App Store) -  this app has a "similar" search feature which is like PhotoSweeper's bitmap comparison.  It found all duplicates
    Duplicate Cleaner for iPhoto - free - was able to recognize the duplicated HDR and normal files from an iPhone shooting in HDR
    Some users have reported that PhotoSweeper did the best in finding all of the dups in their library: iphoto has duplicated many photos, how...: Apple Support Communities.
    If you have an iPhone and have it set to keep the normal photo when shooting HDR photos the two image files that are created will be duplicates in a manner of speaking (same image) but there are only twp apps that detected the iPhone HDR and normal photos as being duplicates: PhotoSweeper and Duplicate Cleaner for iPhoto.  None of the other apps detected those two files as being duplicates as they look for file name as well as other attributes and the two files from the iPhone have different file names.
    iPLM, however, is the best all around iPhoto utility as it can do so much more than just find duplicates.  IMO it's a must have tool if using iPhoto.
    LN

  • Why is the Microsoft Office Access Database Engine data source looking for a workgroup information file?

    While trying to import to MSSQL2012 from SSDT using the wizard from an Access 2013 DB (.accdb) which is password protected, I get the following error with the username blank and the password field correctly populated: 
    Cannot start your application. The workgroup information file is missing or opened exclusively by another user. (MicrosoftOffice Access Database Engine)
    But according to this link:
    http://office.microsoft.com/en-us/access-help/what-happened-to-user-level-security-HA010342116.aspx
    MSA10 and beyond shouldn't need workgroup information files, although it's not clear to me if they are
    created/used or not.
    I can point the wizard to some local version of system.mdw at Advanced -> All -> Jet OLEDB:System Database, and then the error becomes:
    Not a valid account name or password. (Microsoft Office Access Database Engine)
    for any username I can think of.
    Questions:
    1.  Why does this data source insist on looking for a workgroup information file even though user-level security should be disabled?
    2.  Why does the Open dialog box for the Microsoft Access Database Engine have *.mdb as the only selectable filetype?
    3.  How can I get around these errors for an .accdb that is password protected?
    Thanks!

    Hi JordanPG,
    To connect to Access 2007 or later database, we need the Microsoft ACE 12.0 OLE DB driver. SQL Server only installs the Microsoft Jet 4.0 OLE DB driver which can be used to connect to Access 2003 or earlier database. Besides, the Microsoft Jet 4.0 OLE DB
    driver only has 32-bit version, but the Microsoft ACE 12.0 OLE DB driver has both 32-bit and 64-bit version. However, the 32-bit and 64-bit Microsoft ACE 12.0 OLE DB drivers cannot be installed on a single server.
    According to your description, you can use the 64-bit SQL Server Import and Export Wizard to load data from the Access database, so the 64-bit Microsoft ACE 12.0 OLE DB driver is installed on your computer. Since the BIDS/SSDT is a 32-bit application, the
    64-bit Microsoft ACE 12.0 OLE DB Provider is not visible in BIDS/SSDT. So, when you said that you select “Microsoft Access (Microsoft Access Database Engine)" in the SQL Server Import and Export Wizard (it is actually the 32-bit version) started by the SSDT,
    I think it should be “Microsoft Access (Microsoft Jet Database Engine)”. Because the Microsoft Jet 4.0 OLE DB driver only supports Access 2003 or earlier format, it threw the error “Test connection failed because of an error in initializing provider. Unrecognized
    database format 'C:\myDB.accdb'”.
    In this situation, you have two approaches to avoid this issue:
    Launch the SQL Server Import and Export Wizard (64-bit), and select “Save SSIS Package” to “File System” on the “Save and Run Package” page. Then, the package will be saved to a specified directory. After that, you can add this existing package to a SSIS
    project. The status of the corresponding OLE DB Connection Manager should be Work Offline, or the OLE DB Source will throw an error about 32-bit driver if the Connection Manager is not in Work Offline status, you can ignore that and the package can run successfully
    in SSDT as long as the project is set to run in 64-bit runtime mode.
    However, for the SSDT 2012 integrated with Visual Studio 2012, the 64-bit runtime mode is disabled. In this situation, to run the package in SSDT, you have to uninstall the 64-bit Microsoft ACE 12.0 OLE DB drivers and install the 32-bit one. Here is the
    download link:
    http://www.microsoft.com/en-in/download/details.aspx?id=13255 
    Regards,
    Mike Yin
    TechNet Community Support

  • Help! External hard drive (WD) doesn't show up anywhere (except for in System Information)...

    Hi,
    My WD hard drive (160 gb, 3-4 years old) all of a sudden won't show up in Disk Utility or Finder.
    Prior to this, I got an error message, saying something like "back up your data and reformat the disk", and I bought myself a new hard drive (a Verbatim) for this. When I connected the two hard drives, the WD wouldn't show up anywhere, except for in System Information, where the following message is displayed under "USB":
    External HDD    :
      Product ID: 0x0702
      Vendor ID: 0x1058  (Western Digital Technologies, Inc.)
      Version: 1.02
      Serial Number: ????????????????????????
      Speed: Up to 480 Mb/sec
      Manufacturer: Western Digital
      Location ID: 0x14200000 / 9
      Current Available (mA): 500
      Current Required (mA): 0
    My Macbook Pro is a 11.1, with Mavericks installed.
    I have all the recordings of my band's new album on this drive, so any help would be greatly appreciated.
    Thanks!

    I'd have to agree with WZZZ. That sounds like either a bad connection, bad cable, or faulty supply. The port could be bad as well but the cable either being bad or not properly plugged in or maybe even worn out. When the "disk ejected" message shows up it's usually because somehow the cable was yanked out of the system while it was plugged in. Intermittenet connections in the cable, particularly in supply lines between the drive and the unit can cause this to happen as well...it's as if you unplugged the external hard drive from the system for a very short time, but the system still picks it up and sees it as bad.
    If worse comes to worse, download the hard drive troubleshooting book in the downloads section at:
    http://scsc-online.com

  • Return code (SY-SUBRC) for the EXCEPTION will not be processed

    Hi,
    when I was doing the EPC check i have approached this messgae.
    Return code (SY-SUBRC) for the EXCEPTION will not be processed after CALL FUNCTION
    'CU_READ_RGDIR'
    (You can turn off this check by setting all EXCEPTIONS to 0)
    (The message can be hidden with "#EC *)
    Any pointers on how to handle this.
    Regards
    Rohini.

    Hi Rohini,
    Try doing something like this.
    TYPE-POOLS: hrpay.
    DATA: w_pernr              TYPE          p0000-pernr ,
          w_buffer             TYPE          hrpay_buffer,
          w_no_authority_check TYPE          xfeld       ,
          w_molga              TYPE          t500l-molga ,
          t_in_rgdir           TYPE TABLE OF pc261.
    CALL FUNCTION 'CU_READ_RGDIR'
      EXPORTING
        persnr             = w_pernr
        buffer             = w_buffer
        no_authority_check = w_no_authority_check
      IMPORTING
        molga              = w_molga
      TABLES
        in_rgdir           = t_in_rgdir
      EXCEPTIONS
        OTHERS             = 0.

  • Com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:

    Hi Subhra/ Asit,
    The following is the main information form the log file and attched logfile with full info for your reference.
    #1.5#00188B874AFD00320000000A000007B4000447710E97B363#1204450808802#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
    usr
    sap
    SPP
    JC01
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.portal.layouts.default
    jsp
    fullWidth.jsp [email protected]a6d4d7#
    #1.5#00188B874AFD00320000000B000007B4000447710E97BD23#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]a6d4d7#
    #1.5#00188B874AFD00200000000B000007B4000447710E97C15A#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
    usr
    sap
    SPP
    JC01
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.portal.layouts.framework
    jsp
    WAandNavPanel.jsp [email protected]16c192#
    #1.5#00188B874AFD00200000000C000007B4000447710E97CCCC#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]16c192#
    #1.5#00188B874AFD002900000049000007B4000447710EA4FBF8#1204450809677#com.sap.tc.webdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.
    [EXCEPTION]
    #2#fonterra.com/cmtuwlcmir~dispform/CMIRCreateNotificationDisplay#java.lang.NullPointerException
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
                at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
                at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
                at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
                at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
                at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
                at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
                at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
                at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
                at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
                at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
                at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
                at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
                at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
                at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
                at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
                at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
                at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
                at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
                at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
                at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
                at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
                at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
                at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
                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: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)
    #1.5#00188B874AFD00290000004A000007B4000447710EA7E5F6#1204450809865#com.tssap.dtr.client.lib.protocol.session.Cookies#sap.com/tcwddispwda#com.tssap.dtr.client.lib.protocol.session.Cookies.setCookie(Cookie)#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Java###rejecting invalid cookie for domain "": #2#.fonterra.com#JSESSIONID#
    #1.5#00188B874AFD00290000004B000007B4000447710EA8000D#1204450809880#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: java.lang.NullPointerException
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
                at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
                at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
                at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
                at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
                at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
                at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
                at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
                at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
                at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
                at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
                at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
                at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
                at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
                at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
                at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
                at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
                at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
                at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
                at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
                at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
                at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
                at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
                at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
                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: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)
    #1.5#00188B874AFD00290000004D000007B4000447710EA803B8#1204450809880#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: java.lang.NullPointerException: null
    Exception id: [00188B874AFD00290000004B000007B4000447710EA8000D]#
    #1.5#00188B874AFD00290000004E000007B4000447710EA82DD2#1204450809896#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
                at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:168)
                at javax.servlet.ServletOutputStream.print(ServletOutputStream.java:135)
                at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.sendBodyText(HttpServletResponseFacade.java:957)
                at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:948)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
                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: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)
    #1.5#00188B874AFD002900000050000007B4000447710EA82F56#1204450809896#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)].The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
    Exception id: [00188B874AFD00290000004E000007B4000447710EA82DD2]#
    Regards
    Krishna K

    kinldy let me know what was the solution to this problem

  • Error whit PDF Generation Processing exception during a "UsageRights" opera

    Hi experts,
    I have a problem when I wanna generate a PDF Form in a WebDynpro application. The log error is:
    <br>
    com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Interactive Form Operation Failed
      at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:700)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1041)
      at com.sap.tc.webdynpro.clientserver.phases.RespondPhase.execute(RespondPhase.java:60)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseLoop(WindowPhaseModel.java:101)
      at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:547)
      at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:66)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1547)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1361)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:523)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:270)
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:729)
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:256)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
      at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
      at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process RenderRequest Due to the following Reason
    Processing exception during a "UsageRights" operation.
    Request start time: Tue Jan 10 11:31:14 COT 2012
    com.adobe.ProcessingException: com.adobe.ProcessingException: Credential login error while applying usage rights to PDF: /usr/sap/CND/J02/j2ee/cluster/server0/temp/adobewa_CND_27241950/DM3888098661083088935.dir/DM5190493105499627278.tmp
    <br>
    Specific error information:
    error while logging into credential ^0
    GeneralError: Operation failed.
    SecurityHandler.login:-1:
    Could not create temporary file
    <br>
    but in other application webdynpro I can generate the PDF without error. So, I read many forums in the SDN but my system its Ok with the ADS Configuration.
    <br>
    Please help me, I don't know how solved this problem and is very urgent.
    <br>
    NetWeaver CE 7.1 Ehp 1
    <br>
    Thank you,
    Jim Gledward

    There can be several reasons for getting this Error.
    1.ADS problem.
    2. Binding problem.
    3. Value node, Cardinality problem(1-n)
    4. Not mapping PDF Source problem
    5.PDFSource - type-Binary
    Please check it once. If you can post the total error it would be better.

  • PDFObjectRuntimeException: Processing exception during a "UsageRights"...

    Hi,
    I have CE 7.11. I developed a web dynpro application with interactive forms but when I try to run it I get such error. Do You have any ideas how to resolve this problem? I have installed credencial, I used Configuration Wizard for ADS configuration, I have made ADS test and result is OK. I have ADSUser roles and groups assigned to it. I also made ConfigPort_Document. But mayby I made mistake somewhere. Could You tell me step by step how to configure ADS to resolve my error?
    My error:
    com.sap.tc.adobe.pdfobject.base.core.PDFObjectRuntimeException: Processing exception during a "UsageRights" operation. Request start time: Tue Sep 29 10:56:36 CEST 2009 com.adobe.ProcessingException: com.adobe.ProcessingException: Credential login error while applying usage rights to PDF: D:\usr\sap\CE1\J20\j2ee\cluster\server0\temp\adobewa_CE1_206643050\DM-4713501506708271711.dir\DM-273461308253569844.tmp Specific error information: alias ^0 was not found ReaderRights Exception Stack Trace: com.adobe.ProcessingException: com.adobe.ProcessingException: Credential login error while applying usage rights to PDF: D:\usr\sap\CE1\J20\j2ee\cluster\server0\temp\adobewa_CE1_206643050\DM-4713501506708271711.dir\DM-273461308253569844.tmp Specific error information: alias ^0 was not found ReaderRights at com.adobe.ads.request.ADSRequest.processOperations(Unknown Source) at com.adobe.ads.request.ADSRequest.process(Unknown Source) at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source) at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source) 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:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) 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:585) at com.sap.engine.services.ejb3.util.BeanMethods.executeReflectMethod(BeanMethods.java:314) at com.sap.engine.services.ejb3.jacc.ExecuteMethodPrivilegedAction.run(ExecuteMethodPrivilegedAction.java:38) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:396) at com.sap.engine.services.ejb3.jacc.ContainerJ2EESecurityProviderBaseImpl.doAs(ContainerJ2EESecurityProviderBaseImpl.java:262) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_RunAs.invoke(Interceptors_RunAs.java:24) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203) at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:456) at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:430) at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:232) at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:156) at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:96) at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:66) at SoapServlet.doPost(SoapServlet.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314) Caused by: com.adobe.ProcessingException: Credential login error while applying usage rights to PDF: D:\usr\sap\CE1\J20\j2ee\cluster\server0\temp\adobewa_CE1_206643050\DM-4713501506708271711.dir\DM-273461308253569844.tmp Specific error information: alias ^0 was not found ReaderRights at com.adobe.ads.operation.UsageRights.execute(Unknown Source) at com.adobe.ads.operation.ADSOperation.doWork(Unknown Source) at com.adobe.ads.operation.CachableOperation.doWork(Unknown Source) ... 81 more 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.ads.remote.EJB_PDFAgent.setUsageRights(Unknown Source) ...
    Thanks,
    Pawel

    Hi
    Refer the following threads
    Re: "UsageRights issue"
    Re: Exception during ADS deplopyment
    Kind Regards,
    Mukesh

  • PI 7.11 - Alert creation for RFC Exceptions does not work

    Hi folks!
    In our PI 7.11 SP04 system we have created an Alert Category as well as an Alert Rule to be informed about errorneous messages in the Integration Engine (ABAP).
    The scenario is synchronous SOAP Axis to sRFC, where the RFC answers with an exception that is transferred to a SOAP Fault response message.
    Now we see messages with Application Errors in the Integration Engine, but no alert is created. Having a look at the alert creation log using report SXMSALERT_LOGREADER shows us that the system even does not try to create an alert for these messages.  Alerts are only created for errors in the Adapter Engine.
    Question:
    Why does the system not create alerts in this case and how can we achieve this?
    Thanx for any hint!
    Kind Regards,
    Volker

    Hi!
    Additional information for all:
    When forcing an error like "receiver not found" both kinds of alerts are created: AE Alert and IE Alert. Thus in general the alert configuration and the alert rule for IE errors are correct and working - only not for RFC exceptions ....
    Regards,
    Volker

  • Com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException in sap pi

    Hi all,
    I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
    <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Category>XIAdapterFramework</SAP:Category>  
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>  
    <SAP:P1 />  
    <SAP:P2 />  
    <SAP:P3 />  
    <SAP:P4 />  
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>  
    <SAP:Stack />  
    <SAP:Retry>M</SAP:Retry>  
    </SAP:Error>
    The entire trace is as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Inbound Message
    --> 
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"> 
    <Trace level="1" type="T">Party normalization: sender</Trace>  
    <Trace level="3" type="T">Sender scheme external =</Trace>  
    <Trace level="3" type="T">Sender agency external =</Trace>  
    <Trace level="3" type="T">Sender party external =</Trace>  
    <Trace level="3" type="T">Sender party normalized =</Trace>  
    <Trace level="1" type="T">Determining the sender agreement</Trace>  
    <Trace level="3" type="T">##### DG: 3</Trace>  
    <Trace level="3" type="T">##### TO: 3</Trace>  
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>  
    <Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>  
    <Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>  
    <Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>  
    <Trace level="1" type="T">Remote address = 10.66.10.160</Trace>  
    <Trace level="1" type="T">User = SFUSER</Trace>  
    <Trace level="1" type="T">Process ID: 760</Trace>  
    <Trace level="1" type="T">Work Process ID: 10</Trace>  
    <Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"> 
    <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>  
    <Trace level="3" type="T">##### DG: 3</Trace>  
    <Trace level="3" type="T">##### TO: 3</Trace>  
    <Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>  
    <Trace level="1" type="T">Hop engine type = IS</Trace>  
    <Trace level="1" type="T">Hop adapter name = XI</Trace>  
    <Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV"> 
    <Trace level="3" type="T">No triggers found. OK.</Trace>  
    </Trace>
    <Trace level="3" type="T">system-ID = PD1</Trace>  
    <Trace level="3" type="T">client = 001</Trace>  
    <Trace level="3" type="T">language = E</Trace>  
    <Trace level="3" type="T">user = SFUSER</Trace>  
    <Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>  
    <Trace level="1" type="T">ACL Check is performed</Trace>  
    <Trace level="1" type="T">XML validation is executed</Trace>  
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />  
    - <!-- ************************************
    -->   
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>  
    <Trace level="1" type="T">QOS = BE</Trace>  
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />  
    - <!-- ************************************
    -->   
    <Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>  
    <Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>  
    <Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>  
    <Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>  
    <Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>  
    <Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>  
    <Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>  
    <Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>  
    <Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>  
    <Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>  
    <Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>  
    <Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>  
    <Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>  
    <Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>  
    <Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>  
    <Trace level="3" type="T">system-ID = PD1</Trace>  
    <Trace level="3" type="T">client = 001</Trace>  
    <Trace level="3" type="T">language = E</Trace>  
    <Trace level="3" type="T">user = SFUSER</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST"> 
    <Trace level="2" type="T">Persisting original message</Trace>  
    <Trace level="3" type="T">Message-Version = 000</Trace>  
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>  
    </Trace>
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>  
    - <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB"> 
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>  
    <Trace level="3" type="T">PLSRVTYPE =</Trace>  
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>  
    <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>  
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>  
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>  
    <Trace level="3" type="T" />  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"> 
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV"> 
    <Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">Skip Inbound Validation =</Trace>  
    <Trace level="3" type="T">Skip Outbound Validation =</Trace>  
    <Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>  
    <Trace level="1" type="T">Reading sender agreement</Trace>  
    <Trace level="1" type="T">Message does not contain a sender agreement</Trace>  
    <Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>  
    </Trace>
    </Trace>
    </Trace>
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST"> 
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>  
    <Trace level="3" type="T">Message-Version = 001</Trace>  
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>  
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"> 
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>  
    <Trace level="3" type="T

    HI,
    Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
    Patch level of XIAF:
    1. customers SAP PI level is
    Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
    Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
    2. our SAP PI level is
    Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
    Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
    Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
    Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding  AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
    What do you think ?
    Thanks

  • SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception

    Hi,
    I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like
    https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderService=DEMO&interface=si_os_GETLIST&interfaceNamespace=<namespace>
    This is the error that I get when sending a message to the interface
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
    <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
         at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?
    Thanks,
    Rashmi.

    Hi Rashmi,
    I also think your problem is data related.
    Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?
    Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.
    Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.
    Best Regards, Trevor

  • Integrated Configurations com.sap.engine.interfaces.messaging.api.exception

    Hi guys,
    we are using PI 7.11.
    With this release local processing on the advanced adapter engine is possible, when using integrated configurations.
    This works fine.
    Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.
    I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.
    Afterwards I treied to restart the message.
    Following error occurs.
    com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.
    I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache
    trying restart the failed message ends up in the error specified aboce.
    Anyone faced the same issue already?
    Kind regards
    Jochen

    HI Jochen,
    I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.
    To do a CPA Cache Refresh from the Adapter Engine:
    To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:
    http://<host>:<port>/CPACache/refresh?mode=delta|full
    The Monitoring url is like this:
    http://<host>:<port>/CPACache
    Check this How-to Guide on Cache, it will be useful:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&overridelayout=true
    Thanks
    Dhwani

  • Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

    Hello,
    I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
    Iam reading a flat file and trying to write into an XML in the same FTP server
    I have a 1 to 1 Mapping as follows
    And my Content Conversion at Sender side Looks like this
    After running the configuration Iam getting following error message
    Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
    My System is the SAP Netweaver Process Intgration 7.4 single Java stack
    Do you have any idea how to fix this issue?
    Many thanks in advance
    Khadim

    Hi evrybody
    I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
    <ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
    <Recordset>      
    <header> 
         <gesellschaft>03</gesellschaft> 
         <filiale>000</filiale>
         <satzart>11</satzart>
         <datum>00000000</datum>
         <kennzeichen>1</kennzeichen>
    </header>
    </Recordset>
    </ns:hartgeldbest_ERP_KT>
    The issue is on detrmining the RECEIVER in the Main-XML
    <sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
    <sap:MessageClass>ApplicationMessage</sap:MessageClass> 
    <sap:ProcessingMode>asynchronous</sap:ProcessingMode>
    <sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
    <sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
    <sap:Sender> 
    <sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/> 
    <sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
    </sap:Sender>
    <sap:Receiver> 
    <sap:Party agency="" scheme=""/> 
    <sap:Service/>
    </sap:Receiver>
    <sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
    </sap:Main>
    Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
    Any idea?
    Thx
    Khadim

Maybe you are looking for