Issue Management scenario Troubleshooting dump CX_WDR_ADAPTER_EXCEPTION

Hi,
I'm customizing img transaction to configure service desk scenario in a
Solution Manager SPS15 7.0(SID=SMG), on windows 2003 server/SQl Server
2005.
The problem is customizing Issue Management scenario at step "Troubleshooting".
When I execute this action, I go to smsy transaction->Settings -> Self-Diagnosis
and an error with this tittle appears:
Error when processing your request
What has happened?
The URL http://solution.grupotec.local:8002/sap/bc/webdynpro/sap/dswp_sd_settings/ was not called due to an error.
Note
The following error text was processed in the system SMG : Adapter error in &VIEW_ELEMENT_TYPE& "_08" of view "DSWP_SD_SETTINGS.START": Context binding of property ? cannot be resolved: The Mapping to Node COMPONENTCONTROLLER.1.LAYOUT Has Not Been Completed.
The error occurred on the application server solution_SMG_02 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: RAISE_FOR of program CX_WDR_ADAPTER_EXCEPTION======CP
Method: RAISE_BINDING_EXCEPTION of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
Method: GET_BOUND_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
Method: GET_ATTRIBUTE_INTERNAL of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L7STANDARD==============CP
Method: CONV_VIEW_INTO_VE_ADAPTER_TREE of program CL_WDR_INTERNAL_WINDOW_ADAPTERCP
Method: SET_CONTENT_BY_WINDOW of program CL_WDR_INTERNAL_WINDOW_ADAPTERCP
Method: RENDER_WINDOWS of program CL_WDR_CLIENT_SSR=============CP
Method: IF_WDR_RESPONSE_RENDERER~RENDER_USER_INTERFACE_UPDATES of program CL_WDR_CLIENT_SSR=============CP
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 SMG 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 solution_SMG_02 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 solution_SMG_02 . 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: 010 -u: SOLMANADM -l: E -s: SMG -i: solution_SMG_02 -w: 0 -d: 20080618 -t: 115252 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
This error creates a dump:
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_WDR_ADAPTER_EXCEPTION
Short text
    An exception occurred that was not caught.
What happened?
    The exception 'CX_WDR_ADAPTER_EXCEPTION' was raised, but it was not caught
     anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CX_WDR_ADAPTER_EXCEPTION======CP' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_WDR_ADAPTER_EXCEPTION', was not
     caught and
    therefore caused a runtime error.
    The reason for the exception is:
    Adapter error in &VIEW_ELEMENT_TYPE& "_08" of view "DSWP_SD_SETTINGS.START":
    Context binding of property ? cannot be resolved: The Mapping to Node
    COMPONENTCONTROLLER.1.LAYOUT Has Not Been Completed.
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_WD_CONTEXT", which was raised in the program
     "CL_WDR_CONTEXT_NODE_MAP=======CP",
    specifically in line 25 of the (include) program
     "CL_WDR_CONTEXT_NODE_MAP=======CM001".
    The cause of the exception was:
    The Mapping to Node COMPONENTCONTROLLER.1.LAYOUT Has Not Been Completed.
Information on where terminated
    Termination occurred in the ABAP program "CX_WDR_ADAPTER_EXCEPTION======CP" -
     in "RAISE_FOR".
    The main program was "SAPMHTTP ".
    In the source code you have the termination point in line 45
    of the (Include) program "CX_WDR_ADAPTER_EXCEPTION======CM004".
I've tested in sicf transaction that /sap/bc/webdynpro/sap/dswp_sd_settings/ service (right click->test service), appears a log-on popup I type usr j2ee_admin and pwd, and the same error appears.
I'm logged with user to configure Solution Manager
which was SAP_ALL, SAP_NEW profile and a Z_RFC rol with( S_RFC,
S_RFCACL authorizations object).
Please could you help me??
Thanks and Regards
Raul

I've resolved this problem with SAP Note:
1157740 - Self Diagnosis dumps when Settings is accessed from Menu
Thanks and Regards
Raul

Similar Messages

  • Issue management problem

    Hi all,
    I am facing a problem in issue management in transaction solman_issue_mgmt transaction when i try to open a existing message i am getting a dump. the same dump occurs when i try to create a new issue using that transaction.
    pls find the details of the dump .
    I have applied not 1397754 also but still the problem persist.
    kindly guide in this issue.
    Error when processing your request
    What has happened?
    The URL http://ty-stfd0.ty-sap.os.itelligence.de:8002/sap/bc/webdynpro/sap/dswp_ci_issue_management/ was not called due to an error.
    Note
    The following error text was processed in the system TSD : View usage MAIN_USAGE_1 does not exist in window ISSUE of component DSWP_IM_ISSUE_VIEW
    The error occurred on the application server ty-stfd0_TSD_02 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: IF_WDR_RR_VIEW_CNT_ASSIGNMENT~GET_EMBEDDED_VUSAGE of program SAPLWDR_RUNTIME_REPOSITORY
    Method: IF_WDR_RR_VIEW_CNT_ASSIGNMENT~GET_DEFAULT_VIEW_USAGE of program SAPLWDR_RUNTIME_REPOSITORY
    Method: GET_VIEW of program CL_WDR_VIEW_MANAGER===========CP
    Method: BIND_ROOT of program CL_WDR_VIEW_MANAGER===========CP
    Method: INIT of program CL_WDR_VIEW_MANAGER===========CP
    Method: INIT_CONTROLLER of program CL_WDR_INTERFACE_VIEW=========CP
    Method: INIT of program CL_WDR_CONTROLLER=============CP
    Method: GET_VIEW of program CL_WDR_VIEW_MANAGER===========CP
    Method: BIND_ROOT of program CL_WDR_VIEW_MANAGER===========CP
    Method: INIT of program CL_WDR_VIEW_MANAGER===========CP
    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 TSD 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 ty-stfd0_TSD_02 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 ty-stfd0_TSD_02 . 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: SKRISHNAN -l: E -s: TSD -i: ty-stfd0_TSD_02 -w: 0 -d: 20100203 -t: 092939 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Regards,
    Subhashini.

    Hi Rajeev ,
    Thanks for the reply.
    i have checked the service, the specified service is active and tested also. the main screen apprears, the problem is with the next screen.
    there is one more service dswp_im_issue_mgmt , the problem is coming with that service.
    In our system, two service are active with the same name(dswp_im_issue_mgmt ) in that one is active and other is not active.
    I tried to delete one but i got a message that the service is no more valid. is it because of this am getting the error
    kindly clarify.
    I tried to run the SIAC_LIST_UNPUBLISHED but it was not there in the system.
    st22 details:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_WDR_RR_EXCEPTION
    Date and Time          03.02.2010 08:11:33
    What happened?
    The exception 'CX_WDR_RR_EXCEPTION' was raised, but it was not caught anywhere
    along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program 'SAPLWDR_RUNTIME_REPOSITORY'
    has to be
    terminated.
      |Error analysis                                                                               
    |    An exception occurred which is explained in detail below.                                    
    The exception, which is assigned to class 'CX_WDR_RR_EXCEPTION', was not caught
    and
    therefore caused a runtime error.
    The reason for the exception is:
    View usage MAIN_USAGE_1 does not exist in window ISSUE of component
    DSWP_IM_ISSUE_VIEW

  • Issue management security

    Hi does anyone know how to restrict acces for certain users to approve a transport in issue management?
    We customized our issue management status screen for "transport approval " and we would like to give it to certain users only.
    Thanks Mike

    Hi,
    Application visibility to the unwanted users can be stopped by using the Authorizations per MCD i.e. Application.
    You can decide the Authorization objects which are mandatory to view the data in a perticular application. And then only those users who have the necessary authorization will be able to see the data in the application.
    You can not stop the user SAP_C from synchronizing with the server because this user is the valid user in DOE. However you can define the configuration which will avoid the data changed by user SAP_C being processed on the DOE. This scenario is called "Non-repudiation" scenario where a invalid user is trying to change the data on the mobile client. This case can be handled on the DOE and depending on the security setting, the message processing is stopped and correspondingly the admin will be notified.
    Regards,
    Ramanath.

  • Inventory Management Scenario

    Hi BW Experts,
    I was working on the Inventory Management screnario as in How to Handle Inventory Management Scenarios in BW with cumulative KFs. I read many of the forum postings but I am still little bit confused about the sequence of the loading. As per my understanding, BX goes to 0IC_C03 bus. content cube and snapshot ODS. BX load in 0IC_C03 is compressed. Then BF and UM goes to snapshot ODS, snapshot infocube and 0IC_C03 (initilized for Delta). Then the generic extractor from snapshot ODS goes to snapshot infocube as monthly load and also to ODS itself. Now the questions are:
    1-) Is the sequence above correct? If not could you pls. explain? What are reasons behind of this?
    2-) What are the functions of these objects exactly, in detailed? How do you validate data (by comparing 0IC_C03 and snapshot cube)?
    3-) Why the generic extractor goes to infocube and ODS together, what is the reason?
    4-) Is snapshot infocube loaded with BF and UM as delta daily? After initialization am I going to load the snapshot infocube every night or just the 0IC_C03?
    5-) Do I have to put 0CALDAY into Agg. Ref. char. in the maintenance screen of the defined custom KFs (Z* keyfigurs for this scenario) or just in the report enough?
    6-) Are the routines working correctly except for
      diff_month(2) type i-> "i" is going to be changed into "n"
    After I loaded in the above sequence when the bx is loaded into 0IC_C03 cube transferred data records are less than added. What is the reason?
    Contributions are highly appreciated. Thanks.
    Best Regards,
    Message was edited by: John Seker
    Message was edited by: John Seker

    Hi Loic
    Can u please see if all the steps listed below are OK.
    While setting up  the IM Scenario
    I have jotted down the steps with valuable inputs from you  and paper 'How to Hanlde IM scenarios'
    Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
    1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
    2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
    3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
    4. Save it.
    5. Go to Transaction MCNB, enter name of run ‘Stock_init’. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
    6. Execute the initialisation.
    7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
    8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
    9. Run the extraction for 2LIS_03_BX in BW.
    10. Compress the request with ‘No Marker Update’ NOT SET i.e. unticked or unchecked.
    11. Run the extraction for 2LIS_03_BF in BW.
    12. Compress the request with ‘No Marker Update’ SET i.e. ticked or checked.
    13. Run the extraction for 2LIS_03_UM in BW.
    14. Compress the request with ‘No Marker Update’ SET i.e. ticked or checked.
    Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
    Thanks in advance.
    Regards
    PB

  • Posting block Question in How to handle inventory management scenarios

    Hi all - I have a question in document
    <b>"How to...Handle Inventory Management Scenarios in BW"</b>
    can anyone please tell me what a posting block is in this document...
    also I did not understood what a Validity table is?
    thanks,
    Sabrina.

    Hi Sabrina!
    A 'posting block' period is something that now you are facing in inventory management, but you have to consider it in ALL logistic cockpit flows (what you can see in LBWE).
    This requirement can be easily explained in this way: as you know, to fill a setup table you have to activate the extract structure of the datasource for which you want to run the setup job (otherwise the system says that no active extract structure exists, do you remember ?); but, by doing so with the posting operations open (in other words, users can create new document or change the existing ones), you run the risk that these records are automatically included in the extraction queue (or in SM13 if you are using unserialized method) AND also collected in setup table ! And you will have the same records with the initial load (from setup table) and then the same from delta load (from the queue): a nice data duplication.
    To avoid this situation, a "posting block" (or a "free-posting period" or a "downtime") is requested. No one can post new document during your setup job...
    Hope now is clearer...
    Bye,
    Roberto

  • Question on "How to Handle Inv management Scenarios in BW" docuemnt.

    Hi all,
    I read the document "How to Handle inventory management scenarios in BW" and I did not understood what a snapshot scenario is?  Can anyone tell me what is the difference between snapshop and non-cumulative scenario's.
    thanks,
    Sabrina.

    In a non-cumulative scenario the current stock of any day (or month) is not stored physically in the cube. Instead the stock values over time is calculated dynamically at query runtime by the BW OLAP engine, which basically derives the stock by summing up the periodic value changes (cumulative inflow and outflow of the non-cumulative key figure), which are stored in the cube (together with a so called stock marker used as the basis of the calclation).
    In the snapshot scenario the current stock of any month is calculated in a snapshot ODS and then loaded to a cube. This means that the the stock value is physically stored in the cube in an ordinary cumulative key figure.
    Since a non-cumulative cube store value changes and not the actual stock this means that performance might be bad if there are many value changes for each characteristic combination in a month (since the stock is calculated at runtime and many records must be processed to derive the stock). So in this case the snapshot scenario is better since no runtime calculations of the stock need to occur  and since only one record, containing the actual stock value will be stored in each month for each characteristic combination having a stock value.
    I think you would be better of with an example, but with this explanation in mind looking at the scenarios in the How to again might clarify things...
    Regards,
    Christian
    / Christian
    Message was edited by: Christian

  • How to handle inventory management scenario

    Hi All,
    In How to handle inventory management scenario whitepaper, I fail to understand the basic difference between 'Inventory Management with non-cumulative Key Figures' and 'Inventory Management with Snapshots'. Can anyone please explain me the basic difference.
    Thanks
    PB

    Hi Loic
    Can u please see if all the steps listed below are OK.
    While setting up  the IM Scenario
    I have jotted down the steps with valuable inputs from you  and paper 'How to Hanlde IM scenarios'
    Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
    1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
    2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
    3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
    4. Save it.
    5. Go to Transaction MCNB, enter name of run ‘Stock_init’. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
    6. Execute the initialisation.
    7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
    8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
    9. Run the extraction for 2LIS_03_BX in BW.
    10. Compress the request with ‘No Marker Update’ NOT SET i.e. unticked or unchecked.
    11. Run the extraction for 2LIS_03_BF in BW.
    12. Compress the request with ‘No Marker Update’ SET i.e. ticked or checked.
    13. Run the extraction for 2LIS_03_UM in BW.
    14. Compress the request with ‘No Marker Update’ SET i.e. ticked or checked.
    Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
    Thanks in advance.
    Regards
    PB

  • Can I use a project/issue management software with LabVIEW?

    There are project/issue management softwares.
    I only know Redmine.
    Can I use LabVIEW with such softwares?

    I am not aware, that you can hook LabVIEW to tools like bug tracing databases in a native way.
    What you can do is performing that link in a context of requirements management. Use NI Requirements Gateway for this functionality. 
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Issue management in Solution manager

    Hi,
    We are in design phase for Solution manager 4.0. The requirement is now that we want to Internally (250 Sap experts divided in functional groups) involve other support groups or employees to the support message.
    From the theories available I would say to use Issues (SLF2 or SLFI (4.0), linked to the support message (SLFN), eventual changes can be linked to this issue as well. within the issue it is possible to assign tasks to groups and(?)/or employees.
    When a change request is available, no issue is necessary to involve (assign tasks) to employees or groups?
    Another sound here is to use the "task" message in order to involve other people.
    I am wondering what would be the smartest solution and why. Please help.
    Jos

    Nadine the only pain that I see by using the Issues Management component for project issues is that people who wont normally log into Solution Manager (project managers, integration leads, org change leads, etc) will now need a SAP user ID and training on the system. Even though this is very minimal training, and its probably good for them to use the SAP interface, it isnt as quick as using Sharepoint, an E room or spreadsheets.
    But if it is project issues associated to business processes (thats how it sounds based on your other posts), this could be very useful. Again the functionality is mature enough to deploy according to your requirements, but prepared for some whining and pushback.
    Good luck

  • Configuration of Issue Management tables

    Hello -
    I am looking to configure the tables in Issue Management  but I cannot seem to find them via the SPRO transaction.
    Is there a guide on how to do the configuration for Issue Management?
    Please let me know
    Thanks!
    Nadine

    Please look at Note 1019583. In TA SOLMAN_ISSUE_MGMT there are also the usual Wed Dynpro ALV customizing possibilities (independent of Issue Management).

  • Sol Man Issue Management

    Hi Team,
    I am configuring isssue management in Sol Man. I am using SAP EHP 1 for SAP Solution Manager 7.0, ST: SAPKITL433.
    I have created ZSSI t.code (Copy of SLFI).
    1.When i try to create issue in DSWP and in SOLAR01, i could able to create only SLFI not ZSSI. How to get my transaction type ZSSI in DSWP and SOLAR01.
    2.When i create the issue, i could not able to select the "Project" in the "Context" tab. How to link the project with an issue?
    3. While creating the issue in DSWP, i need to specify the entry in the "Subject" field. I would like to add the custom defined "Subject" entries. How to add entries in the "Subject" field apart from the standard dropdown?
    4. In the tab "Service Session", i could not able to assign any service sessions. How to assign this? How to create service session in DSWP?
    Regards
    PSK
    Edited by: psk.psg on Oct 1, 2010 1:35 PM

    Hi PSK!
    Regarding the customizing, I think that note 1019583 would be helpful for you as it brings information on customizing in issue management. Check if you have done it correctly.
    Regards,
    Daniel.

  • Business Partner for Issue Management

    Hi! Does anyone have documentation on how to create a business partner in transaction BP and have it show up in the Processor list in Issue Management?
    Thanks,
    Lonny

    Hi
    for any users of solman issue management you need BP or master data
    so you can call Tcode BP_GEN and then choose system followed users to create the BP
    Once done you can simply goto BP for that particular user in BP tcode and choose the role as Employee then save it with userID because everybody  is not processor.normally processor is the one providing solution to key users who raise incident
    Regards
    Prakhar
    Edited by: Prakhar Saxena on May 25, 2011 3:39 PM

  • Issue management - Email transmission to message processor

    Hi all,
    I am now working in issue management( solman - sp15 ). Here i am trying to create a automatice email transmission to the message process when the issue assigned to him, But its not triggering a mail.i have worked in servicee desk management to sens a automatic mail transmission.
    With that knowledge i have worked in this one also..
    Here i used the action  TASK_ACTION_PROFILE..,,but i feel the problem here is i am not able to define the condition according to the user status.. Am i missiong out anything
    Anyone have idea on this???
    regards
    Vijay

    Dear Vijay,
    Please see note : 691303 - Sending E-Mail from message after status change, i believe that help you..
    Best regards..
    Claudenir Bispo

  • How to take OIM Managed server Thread Dump

    Hi All,
    how can i take the oim managed server thread dump
    I used wlst command for this lyk follows
    kill -3<pid>
    ./wlst.sh
    connect("weblogic","password","t3://hostname:port")
    threadDump()
    but it is giving Admin server dump, i want oim managed server threadDump how can i get this

    hi kalyan,
    after connecting to wlst
    i tried these steps
    cd('Servers')
    cd('server_oim_DEV')--which is my managed server name
    threadDump()
    after this i got the threadDump but i dont think so i am getting different file
    when i open this it is mentioned lyk Admin server dump
    is this the ryt process and can i know the ryt process to take managed server thread Dump

  • Waste management scenario

    Hi Team,
    Please write me steps involved in "Waste management scenario".
    What are the T-Codes.
    What master data is required.
    Thanks

    Hi
    Steps involved in Waste Management are :
    1)     Create and maintain Waste Management Business partners :  Waste generator u2013 WAA02, Waste transporter u2013 WAA20 and Waste disposer u2013 WAA11. 
    2)     Create entry document for waste disposal : WAE02
    3)     Inventory Posting of waste material: WAE02
    4)     Create purchase order for external disposal service : WAE02, ME23N
    5)     Create disposal documents : WAM02
    6)     Verify Invoice and release for payment: MIRO, MRBR.
    7)     Print Waste manifest: WAM02, CG54
    Entire waste mamagement process is done in following different ways and all the steps mentioend above are used, based on what process has been decided for waste disposal :
    a)     Legally compliant disposal processing
    b)     Lean waste management with entry of intenal quantities
    c)     Integrated commercial disposal processing
    d)     Integrated logistics disposal processing
    Other master data required (For IDES):
    Company code : 1000
    Production plant : 1100
    Material : P182_WST / P182WST_RQ / P182_WST_PP
    Specification waste code : EWC_060102 / EWC_200129
    Specification Substance : P182_WST / P182_WST_PP
    Waste generator : IDES_0001/ IDES_0011 /  IDES_0012 / IDES_0013 / IDES_0014
    Waste disposer : IDES_0015
    Waste transporter : IDES_0065 / IDES_0025 / IDES_0035
    Contract : 4600000042/54
    Vendor: 15 (Tiedemeier Entsorgung GmbH)
    G/L: 400000
    Some of the data like Contract, vendor and G/L may be different for different IDES server. Pls. check accordingly.
    Regards,
    Niraj

Maybe you are looking for