CX_FQDN runtime error in WEBDYNPRO

Hello Gurus, I have a problem with a WebDynpro. The issue is as follows
I set the parameters in RZ10:
SAPLOCALHOST = sapexprod
SAPLOCALHOSTFULL = sapexprod.grupolarepublica.com.pe
icm / host_name_full = sapexprod.grupolarepublica.com.pe
When I try to access from within the network, asks me username / password and enter Okei
URL: http://sapexprod.grupolarepublica.com.pe:8001/sap/bc/webdynpro/sap/zwdxx_prueba1
But when I try to log off the network, asks me username / password but I get the dump:
The URL: http://200.37.36.37:8001/sap/bc/webdynpro/sap/zwdxx_prueba1
The URL http://200.37.36.37:8001/sap/bc/webdynpro/sap/zwdxx_prueba1 call has been canceled due to an error.
Note
The system has processed the following text error PRO: Die URL enthält keine vollständig Domainangabe (200.37.36.37 200.37.36.37 statt. ).
The error occurred in the application server sapexprod_PRO_00 and the work process 0.
The class of cancellation was: RABAX_STATE
The ABAP call hierarchy was:
Method: CHECK of program CX_FQDN ======================= CP
Method: STARTUP_CHECKS of program CL_WDR_UCF ==================== CP
Method: CONSTRUCTOR of program CL_WDR_UCF ==================== CP
Method: CREATE of program CL_WDR_UCF ==================== CP
Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP === CP
Method: IF_HTTP_EXTENSION ~ HANDLE_REQUEST of program CL_WDR_MAIN_TASK ============== CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER ================ CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module:% HTTPSTART of program SAPMHTTP
Please I really need your help Gurus, Thank you.
GC

I had the same problem..
I set a external debugger in the method "CHECK" of CX_FQDN where it hits the dump.
Turns out SAP does not allow IP address (not Sure why..may be there is a note for this..I'll post if I find anything)
Check out the logic..
METHOD check.
  DATA: lv_host    TYPE string,
        lv_port    TYPE string.  "#EC NEEDED
  lv_host = request->get_header_field( name = 'host' ).
  IF lv_host NA '.' OR lv_host CO '0123456789.:'.
    IF NOT lv_host CS 'localhost'.
      SPLIT lv_host AT ':' INTO lv_host lv_port.
      RAISE EXCEPTION TYPE cx_fqdn
        EXPORTING host   = lv_host
                  domain = '.<domain>.<ext>'. "#EC NOTEXT recommend security group
    ENDIF.
  ENDIF.
ENDMETHOD.
Sorry..Just found a note "1403326".. SAP makes it official that we cannot use IP.
Here is what the note says.
Symptom
You start a Web Dynpro ABAP application and immediately receive an error message due to the exception: CX_FQDN.
Other terms
Fully qualified domain name
Reason and Prerequisites
You can start Web Dynpro ABAP applications only if
the name of the server with a fully qualified domain name (FQDN) was specified in the URL. The specification of an IP address or a host name without a domain is not possible.
The requirements of a fully qualified domain name are described in Note 654982.
Solution
Start Web Dynpro ABAP applications only with a suitable server name.
Edited by: Sudharshan on Aug 1, 2011 3:39 AM

Similar Messages

  • CX_FQDN runtime error

    Hisdn team,
    I am getting the following runtime error while testing my webdynpro application.
    I try one time to solve it by adding a new parameters in RZ10
    icm/host_name_full = $(SAPLOCALHOST).domain.ext
    but itI dump all my SAPserver when I restart.
    now I get back my profi and my sapserver, but till have same probleme.
    can any one help me work together to solve it!!!
    Thanks
    Adil
    Edited by: adil chikhaoui on Dec 23, 2010 4:41 AM

    Hi jagdal,
    it looks like work for few seconde and after that another error pop up:
    The following error text was processed in the system DM0 : Lower-Level Node with Name MAINVIEW.sflight_node Does Not Exist Iꯂ
    When  activate m web dynpro everythings i good
    if any one can how me a way I appreciate
    The following error text was processed in the system DM0 : Lower-Level Node with Name MAINVIEW.sflight_node Does Not Exist Iꯂ
    The error occurred on the application server sapserver_DM0_01 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: GET_CHILD_NODE_INTERNAL of program CL_WDR_CONTEXT_ELEMENT========CP
    Method: IF_WD_CONTEXT_ELEMENT~GET_CHILD_NODE of program CL_WDR_CONTEXT_ELEMENT========CP
    Method: IF_WD_CONTEXT_NODE~GET_CHILD_NODE of program CL_WDR_CONTEXT_NODE_VAL=======CP
    Method: WDDOINIT of program /1BCWDY/2WK3XWKOCLBKF7E5TWGR==CP
    Method: IF_WDR_VIEW_DELEGATE~WD_DO_INIT of program /1BCWDY/2WK3XWKOCLBKF7E5TWGR==CP
    Method: DO_INIT of program CL_WDR_DELEGATING_VIEW========CP
    Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP
    Method: INIT_CONTROLLER of program CL_WDR_VIEW===================CP
    Method: INIT of program CL_WDR_CONTROLLER=============CP
    Method: GET_VIEW of program CL_WDR_VIEW_MANAGER===========CP

  • Runtime error in webdynpro for abap

    hi every one,
        The ASSERT condition was violated.
    in webdynpro abap can any one help . im getting this error when im inserting customer master in KNA1
    and also when i m giving name in customer name field its give error as
    Unable to interpret RA as a number  in case of customer name i m pretty confused can any one help.

    Which assert condition was violated?  Think of this as a CHECK statement that evaluated as NOT TRUE.  Also, are you sure your data elements/domains are correct from customer name?  The error fires when you put non-digit characters into numeric fields or NUMC fields.

  • Runtime error for webdynpro

    Hi All,
    i am getting "java.lang.UnsupportedClassVersionError: Bad version number in .class file " error in 7.1 server which is using jre 1.5 when i compiled a webdynpro application in nwds7.1 using jdk1.5 version.
    webdynpro not using any external lib its a simple hello word application.
    can any body help me on this
    Thanks
    Gaurav

    Check this topic https://forums.sdn.sap.com/click.jspa?searchID=27051702&messageID=7550229 respectively this FAQ https://www.sdn.sap.com/irj/scn/wiki?path=/display/java/netweaver%252bdeveloper%252bstudio%252b(NWDS)
    (Attention: the (NWDS) is part o the link!)

  • Runtime error in WebDynpro - Access via 'NULL' object reference not possibl

    Hi,
        Structure of the CONTEXT in the VIEW::
         WDSCREEN1
              --> IMPORTING
                         --> S_KUNNR   <- its a select option
              --> EXPORTING
                        --> T_REPORT  <- Which is table to hold the output data (with 4 fields)
       In the context area i have root node (WDSCREEN1) and Sub nodes are IMPORTING and EXPORTING and child nodes as shown above. When i am referring them everything is fine except T_REPORT.
    * Declaration
      DATA:  node                  TYPE REF TO if_wd_context_node,
                  node_exporting TYPE REF TO if_wd_context_node,
                  node_importing  TYPE REF TO if_wd_context_node,
                  node_report       TYPE REF TO if_wd_context_node,
      node           = wd_context->get_child_node( wd_this->wdctx_wdscreeb1 ).
      node_exporting = node->get_child_node( wd_this->wdctx_exporting ).
      node_importing = node->get_child_node( wd_this->wdctx_importing ).
    * Bind the data to the context
      node_report = node_exporting->get_child_node( name = 'T_REPORT` ).
      node_report->bind_elements( lt_report ).
    Its giving run time error 'Access via 'NULL' object reference not possible. ' when it comes to ' node_report->bind_elements( lt_report ).' I checked the content while debugging and found that it was initial. Not sure why Node_report is initial. all others have data.
    node ->
    node_exporting ->
    node_importing ->
    node_report ->

    http://wiki.sdn.sap.com/wiki/display/EP/PointersforTroubleshootingPortalRuntime+Errors
    Hope this helps.
    -Veer

  • Webdynpro application runtime error CX_FQDN

    Hi experts,
    I am encountering following error when running a sample webdynpor application from SE80. I have included details of my Hosts file entries and profile parameter in the details below.
    My SAP system is installed on my desktop computer as a standalone on a wrkgroup. Name of the host is 'ecc6'.
    Step by step instructions preferably with some example will be greatly appreciated.
    Thanks in advance. AP
    What has happened?
    The URL http://ecc6:8006/sap/bc/webdynpro/sap/z_tutorial_1 was not called due to an error.
    Note
    The following error text was processed in the system ECC : Die URL enthält keine vollständige Domainangabe (ecc6 statt ecc6.).
    The error occurred on the application server ecc6_ECC_06 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    ST22 dump is:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_FQDN
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_FQDN', was not caught and
        therefore caused a runtime error.
        The reason for the exception is:
        Die URL enthält keine vollständige Domainangabe (ecc6 statt
        ecc6.).
    System environment
        SAP-Release 700
        Application server... "ecc6"
        Network address...... "192.168.100.1"
        Operating system..... "Windows NT"
        Release.............. "5.2"
        Hardware type........ "4x Intel 801686"
        Character length.... 16 Bits
        Pointer length....... 32 Bits
        Work process number.. 0
        Shortdump setting.... "full"
        Database server... "ECC6"
        Database type..... "ORACLE"
        Database name..... "ECC"
        Database user ID.. "SAPSR3"
    User and Transaction
        Client.............. 001
        User................ "SAPUSER"
        Language Key........ "E"
        Transaction......... " "
        Program............. "CX_FQDN=======================CP"
        Screen.............. "SAPMHTTP 0010"
        Screen Line......... 2
        Information on Caller ofr "HTTP" Connection:
        Plug-in Type.......... "HTTP"
        Caller IP............. "192.168.100.1"
        Caller Port........... 8006
        Universal Resource Id. "/sap/bc/webdynpro/sap/z_tutorial_1"
    Information on where terminated
        Termination occurred in the ABAP program "CX_FQDN=======================CP" -
         in "CHECK".
        The main program was "SAPMHTTP ".
        In the source code you have the termination point in line 10
        of the (Include) program "CX_FQDN=======================CM002".
    Entries in C:WINDOWSsystem32driversetchosts
    127.0.0.1                 localhost
    192.168.100.1     ecc6
    Instance Profile in SAP transaction RZ10 is ECCDVEBMGS06_ECC6_
                Parameter Name                                      Parameter value
    login/no_automatic_user_sapstar                      0
    login/system_client                                            001
    SAPSYSTEMNAME                                           ECC
    SAPGLOBALHOST                                           ecc6
    SAPSYSTEM                                                    06
    INSTANCE_NAME                                             DVEBMGS06
    DIR_CT_RUN                                                 $(DIR_EXE_ROOT)$(OS_UNICODE)NTI386
    DIR_EXECUTABLE                                         $(DIR_INSTANCE)exe
    PHYS_MEMSIZE                                             512
    rdisp/wp_no_dia                                             6
    rdisp/wp_no_btc                                            3
    icm/server_port_0                                          PROT=HTTP,PORT=80$$
    ms/server_port_0                                          PROT=HTTP,PORT=81$$
    rdisp/wp_no_enq                                   1
    rdisp/wp_no_vb                                    1
    rdisp/wp_no_vb2                                  1
    rdisp/wp_no_spo                                   1
    DIR_CLIENT_ORAHOME                              $(DIR_EXECUTABLE)

    HI ,
    SAP has recommended it like that
    for accessing SAP web dynpro abap application you have to give the full FQDN i.e. host name with domain.
    simply hostname alone wont work.
    http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/content.htm
    Pls go through the link.This mite help
    Thanks,
    Aditya.

  • Runtime Error While executing the WebDynpro Application

    I am getting the Runtime Error While executing the WebDynpro Application. The error message is "TSV_TNEW_OCCURS_NO_ROLL_MEMORY".
    It says like "
    Short text
        No roll storage space of length 9728 available for OCCURS area.
    What happened?
        Each transaction requires some main memory space to process
        application data. If the operating system cannot provide any more
        space, the transaction is terminated.
    But while executing some other Web Dynpro Applications, i am not facing this problem.

    Generally this error is a result of an infinite loop on internal table or select endselect statement where by severs  temporary memory gets full. With no memory to insert new records in temporary memory system generates the dump.
    Check your application or ask basis consultant to look at the memory parameters in instance profile.
    Regards
    Rohit Chowdhary

  • Runtime error webdynpro in portal

    Hi Friends,
    I have created a webdynpro and I want to show it in the Portal.
    For this I have a webdynpro iview.
    But when I call the webdynpro in portal, it shows portal runtime error.
    But when I assign the user to admin role it works.
    Can I use the user without to assign admin role.
    I have created a own role (standard user role) and mapped the user to an user in backend system.
    Any help would be apreciated.
    RG. Jimbob

    Hi Jimbob,
    As Sandeep said correctly, enduser permission on the respective portal objects would help.
    Regards,
    Biroj Patro.

  • Runtime Error during FileUpload to KM through webdynpro java

    Hi All,
    When i try to upload a file using webdynpro java. I was using referring this blog.
    /people/rohit.radhakrishnan/blog/2005/05/27/uploading-files-to-km-repository-using-webdynpro-apis
    But when i deploy my application, it throws me a runtime error
    " java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/IResourceContext".
    I have given the sharing reference as "Portal:sap.com/com.sap.km.aaplication". in webdynpro reference.  and have added all the required jar files. What else needs to be done for this. Can anyone please help me out in this issue?
    Regards,
    Divya

    Please notice that this is case sensative-
    "PORTAL:sap.com/com.sap.km.application"
    Edit - I also see that you have two a instead of two p - please check for spelling errors
    Edited by: Aviad Levy on Feb 4, 2008 9:16 AM

  • Erecuitment- Webdynpro - Portal Runtime Error When Clicked On Page Or Iview

    Hi Guys,
    I am getting error for every link on recruiter tab in portal as below: 
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 02:52_07/11/09_0292_3408050
    Refer to the log file for details about this exception.
    We are on EPH4 with web dynpro ABAP.
    Any clues?
    Thanks.

    Hi Ron,
    basically there can be 2 different reasons.
    If there is something wrong with the portal settings / connection to e-recruiting you will probably need your portal guys to have it checked.
    While the portal guys are checking the connection you should check if there is anything with the e-recruiting server. As a first step log on to the backend and check TCode SLG1 for any error entries. Perhaps it is something very basic like a missing candidate for your user you have to create using report RCF_CREATE_USER so you can solve on your own. If you encounter a message you cannot handle on your own, just post it again here, we will probably able to offer some guidance. In addition to checking SLG1 having a look into SM21 and ST22 can be always useful.
    Best Regards
    Roman

  • Error in webdynpro application

    Dear gurus.
    Im getting following error how to rectify it ?
    we don't have Basis guy so im also doing the basis stuff and im new in it .
    Error when processing your request
    What has happened?
    The URL http://sapr3dq:8000/sap/bc/webdynpro/sap/zsaptechnical_demo was not called due to an error.
    Note
    The following error text was processed in the system R3D : Die URL enthält keine vollständige Domainangabe (sapr3dq statt sapr3dq.<domain>.<ext>).
    The error occurred on the application server sapr3dq_R3D_00 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: CHECK of program CX_FQDN=======================CP
    Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
    Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
    Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
    Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
    Module: %_HTTP_START of program SAPMHTTP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system R3D in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server sapr3dq_R3D_00 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server sapr3dq_R3D_00 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 100 -u: ABAPDEV -l: E -s: R3D -i: sapr3dq_R3D_00 -w: 0 -d: 20100225 -t: 140212 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team

    |Error analysis                                                                                |
    |    An exception occurred which is explained in detail below.                                     |
    |    The exception, which is assigned to class 'CX_FQDN', was not caught and                       |
    |    therefore caused a runtime error.                                                             |
    |    The reason for the exception is:                                                              |
    |    Die URL enthält keine vollständige Domainangabe (sapr3dq statt                                |
    |    sapr3dq.<domain>.<ext>).                                                                      |
    |                                                                                |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "CX_FQDN=======================CP" -                 |
    |     in "CHECK".                                                                                |
    |    The main program was "SAPMHTTP ".                                                             |
    |                                                                                |
    |    In the source code you have the termination point in line 10                                  |
    |    of the (Include) program "CX_FQDN=======================CM002".                               |

  • Portal runtime error while trying to run a MSS report

    Hello gurus!!
       I setup the MSS reports launchpad and now I am seeing all the list of reports on the reports launchpad. I am able to click on all the links and each link opens up the relevant page and the selection criteria also comes up. However, on the last screen, I get a portal runtime error after I click on the report result button.
    The trace file shows the following errors:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[17, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.16.trc]/>
    <!NEXTFILE[defaultTrace.18.trc]/>
    <!LOGHEADER[END]/>
    #1.5 #0050568444360067000005D2000005D400049F27DC8DD843#1300893459438#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#SSUBBARAO#113523##n/a##ae3b7a53556011e0cd95000000191d7e#SAPEngine_Application_Thread[impl:3]_23##0#0#Fatal#1#/Applications/Xss#Java###null
    [EXCEPTION]
    #1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:453)
         at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:820)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:280)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:353)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:268)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:542)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         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:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:245)
         at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 64 more
    Could anybody please guide me how to fix this error and get the reports working properly?
    Any help with this is much appreciated.
    Thank you!
    ~Maria Kutty~

    Hi,
    Please refer to note 878440.
    Thanks
    Prashant

  • Runtime error in web dynpro java

    Hi friends,
    i have designed and run the project for adobe pdf form,compliation is ok...but it produce runtime error please tel me what is error how to rectify that...
    The error is
    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.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"https://<name>.us:443/AdobeDocumentServices/Config?style=document"
        at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:980)
        at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
        at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
        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
    Thanks in advance
    Manee R

    Hi Mani,
    To be able to use PDF forms in Web Dynproapplications:
    &#56256;&#56442;SAPNetWeaverDeveloper Studio(minimum SPS 11) is installed
    &#56256;&#56442;Adobe LiveCycleDesigner7.0 is installed
    &#56256;&#56442;Adobe Reader7.0.x is installed
    &#56256;&#56442;SAP NetWeaverWeb AS Javacompatible with the DevStudiois installed
    &#56256;&#56442;The Adobe Document Servicesare deployed and configured on the SAP J2EE Engine.
    &#56256;&#56442;The Active Component Framework(ACF) of the Interactive Forms integration is installed. (not mandatory)
    Check this.
    reg errors in webdynpro runtime
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2b6db1c4-0801-0010-faa5-ff4b4df55b45
    Regards,
    Mithu

  • Runtime error while executing WD Application

    Hi All,
    I have developed a sample application with one text view and when i am executine the application, I am getting the runtime error.
    The description is like:
    Note
    The following error text was processed in the system EC6 : Die URL enthält keine vollständige Domainangabe (numbers12 statt numbers12.).
    The error occurred on the application server numbers12_EC6_00 and in the work process 2 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: CHECK of program CX_FQDN=======================CP
    Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
    Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
    Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
    Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
    Module: %_HTTP_START of program SAPMHTTP
    Error code: ICF-IE-http -c: 800 -u: SANJEEV -l: E -s: EC6 -i: numbers12_EC6_00 -w: 2 -d: 20080814 -t: 133813 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
    Can anyone suggest me the solution for this? Please le tme know if you need more details about this to findout the problem.
    Thanks,
    Raz

    Hello,
    I got this kind of problem, too and  it was necessary to configure the FQDN to run web dynpro abap. You can do it in RZ10 transaction.
    If you take a good look at the document, you'll see that it's necessary to configure the [FQDN|http://help.sap.com/saphelp_nw04s/helpdata/en/67/be9442572e1231e10000000a1550b0/content.htm].
    Regards.

  • Portal Runtime Error : Any ideas?

    Hello There,
    Please help. I'm having a 'Portal Runtime Error' and would appreciate any lead: This is appearing in the MSS overview Page..
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 10:37_27/03/08_0005_7368050
    See the details for the exception ID in the log file.
    Here's what i cld get from the log file: Notice the exception id in bold.
    Thanks.
    #1.5 #001CC4D8C23E005F000000370000145000044968C5923ABE#1206614246811#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#MANAGER1#102##LBBEPDEV_EPD_7368050#MANAGER1#a6d16470fbe711dcc1bd001cc4d8c23e#SAPEngine_Application_Threadimpl:3_24##0#0#Error#1#/System/Server#Java###Exception ID:10:37_27/03/08_0005_7368050
    EXCEPTION
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.work_overview/com.sap.pct.erp.mss.workoverview/com.sap.pct.erp.common.key_figure_monitor
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : MANAGER1
    at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    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.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESIDURL_ENCODE>?sap-ep-iviewhandle=007<ESIDHASH>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.AccessibilitySAP_BOOL>&sap-rtl=<LAF.RightToLeftSAP_BOOL>&sap-ep-version=<Portal.VersionURL_ENCODE>&<ProducerInfo>&sap-explanation=<User.ExplanationSAP_BOOL>&<StylesheetIntegrationIF_true PROCESS_RECURSIVE>&<Authentication>&<DynamicParameterPROCESS_RECURSIVE>&<ForwardParametersQUERYSTRING>&<ApplicationParameterPROCESS_RECURSIVE>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
    System: &\#39;SAP_LocalSystem&\#39;,
    Attribute: &\#39;client&\#39;.
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    ... 29 more
    #1.5 #001CC4D8C23E005F000000390000145000044968C5924083#1206614246811#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#MANAGER1#102##LBBEPDEV_EPD_7368050#MANAGER1#a6d16470fbe711dcc1bd001cc4d8c23e#SAPEngine_Application_Threadimpl:3_24##0#0#Error##Java###10:37_27/03/08_0005_7368050
    EXCEPTION
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESIDURL_ENCODE>?sap-ep-iviewhandle=007<ESIDHASH>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.AccessibilitySAP_BOOL>&sap-rtl=<LAF.RightToLeftSAP_BOOL>&sap-ep-version=<Portal.VersionURL_ENCODE>&<ProducerInfo>&sap-explanation=<User.ExplanationSAP_BOOL>&<StylesheetIntegrationIF_true PROCESS_RECURSIVE>&<Authentication>&<DynamicParameterPROCESS_RECURSIVE>&<ForwardParametersQUERYSTRING>&<ApplicationParameterPROCESS_RECURSIVE>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
    System: &\#39;SAP_LocalSystem&\#39;,
    Attribute: &\#39;client&\#39;.
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    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)

    Looks like the issue is related to the system that is referencing the ERP System. Check if the connection tests of the system is passing.
    Verify the hostname and ports of the R3 System. Also check the system referencing the Netweaver Application Server.
    Also check if SSO is working fine.
    Regards,
    Abhishek

Maybe you are looking for