DSWP > Setup System Monitoring - RAISE_EXCEPTION Short Dump!

[Former Member]

Hi All

I am on a clean up session at the moment on our Solution Manager box. Basically we have had a consultant to set it up for us and we are getting problems.

Basically I want to look a how our CCMS monitoring is set up and when ever i go into 'Setup System Monitoring' i get this:

RAISE_EXCEPTION Short Dump.

Exception condition "FAILED" raised.

A RAISE statement in the program "SAPLDSVAS_PROC" raised the exception

condition "FAILED".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

Any help would be great!

Thanks

Phil

[former_member209604 · Accepted solution]

Hi Phil,

Could you post more information from the Short Dump?

Post the following sections of the dump:

- Header information (starting with Runtime Error)

- Short text

- Error Analysis

- Active calls/events (copy the first 1-10 calls)

- Source code extract

Best regards,

Ruediger

[Former Member · Accepted solution]

Ok:

Header information (starting with Runtime Error)

Runtime Errors RAISE_EXCEPTION

Date and Time 05.03.2008 11:59:44

Short text

Exception condition "FAILED" raised.

Error Analysis

A RAISE statement in the program "SAPLDSVAS_PROC" raised the exception

condition "FAILED".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

-

Active calls/events (copy the first 1-10 calls)

15 METHOD SAPLDSVAS_PROC LDSVAS_PROCCD0 4833

LCL_ERROR=>STORE

14 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 728

LCL_SESSION=>FLUSH

13 FUNCTION SAPLDSVAS_PROC LDSVAS_PROCU02 468

DSVAS_PROC_SESSION_OPEN

12 METHOD SAPLDSVAS_SERV LDSVAS_SERVC6I 345

LCL_SESSION_DISPATCHER=>NEW

11 FUNCTION SAPLDSVAS_SERV LDSVAS_SERVU01 44

DSVAS_SERV_SESSION_OPEN

10 METHOD CL_DSMOP_HTML_SERVICE_OPEN====CP CL_DSMOP_HTML_SERVICE_OPEN====CM00R 144

CL_DSMOP_HTML_SERVICE_OPEN=>SSWB_START

9 METHOD CL_DSMOP_HTML_SERVICE_OPEN====CP CL_DSMOP_HTML_SERVICE_OPEN====CM008 6

CL_DSMOP_HTML_SERVICE_OPEN=>ACTIVITY_EDIT_SESSION

8 METHOD CL_DSMOP_HTML_SERVICE_OPEN====CP CL_DSMOP_HTML_SERVICE_OPEN====CM001 224

CL_DSMOP_HTML_SERVICE_OPEN=>HTML_GENERATE

7 FUNCTION SAPLDSWP_DSMOP_UI LDSWP_DSMOP_UIU02 179

DSWP_DSMOP_UI_DISPATCHER

6 FUNCTION SAPLDSWP_DSMOP_UI LDSWP_DSMOP_UIU01 57

DSWP_DSMOP_UI_R3_START

5 METHOD RDSMOP_MAIN DSWP_DSMOPC01 188

CL_D100_EVENT_HANDLER=>ON_SAPEVENT

4 METHOD CL_GUI_HTML_VIEWER============CP CL_GUI_HTML_VIEWER============CM00K 17

CL_GUI_HTML_VIEWER=>DISPATCH

3 METHOD CL_GUI_CFW====================CP CL_GUI_CFW====================CM001 138

CL_GUI_CFW=>DISPATCH

2 MODULE (PAI) RDSMOP_MAIN DSWP_DSMOPI01 775

USER_COMMAND_0100

1 EVENT RDSMOP_MAIN RDSMOP_MAIN 108

START-OF-SELECTION

Source code extract

4803 ps_error_info_structure-ins = ins.

4804 ps_error_info_structure-id = id.

4805 ps_error_info_structure-grp = grp.

4806 ps_error_info_structure-creation_date = creation_date.

4807 ps_error_info_structure-creation_time = creation_time.

4808 ps_error_info_structure-reference_grp = reference_grp.

4809 ps_error_info_structure-reference_versnr = reference_versnr.

4810 endmethod. "as_error_info_structure

4811

4812 * Store

4813 method store.

4814 data ls_dsvasresultserr type dsvasresultserr.

4815

4816 check state = state_new.

4817

4818 ls_dsvasresultserr-sessitype = session->session_number-sessitype.

4819 ls_dsvasresultserr-sessno = session->session_number-sessno.

4820 ls_dsvasresultserr-cntr = cntr.

4821 ls_dsvasresultserr-error_number = error_number.

4822 ls_dsvasresultserr-parameter1 = parameter1.

4823 ls_dsvasresultserr-parameter2 = parameter2.

4824 ls_dsvasresultserr-parameter3 = parameter3.

4825 ls_dsvasresultserr-con = con.

4826 ls_dsvasresultserr-ins = ins.

4827 ls_dsvasresultserr-grp = grp.

4828 ls_dsvasresultserr-id = id.

4829 ls_dsvasresultserr-creation_date = creation_date.

4830 ls_dsvasresultserr-creation_time = creation_time.

4831 insert into dsvasresultserr values ls_dsvasresultserr.

4832 if sy-subrc ne 0.

>>>>> raise failed.

4834 endif.

4835 state = state_saved.

4836 endmethod. "store

4837

4838 * Load

4839 method load.

4840 * Wird niemals geladen

4841 raise not_found.

4842 endmethod. "load

4843

4844 * Delete

4845 method delete.

4846 * Wird niemals gelöscht

4847 endmethod. "delete

4848

4849 * Register

4850 method register.

4851 call method session->register_object

4852 exporting

Hope this helps

Cheers

Phil

[former_member209604 · Accepted solution]

Hi Phil,

Much better

(ideally you would have also mentioned the installed Software Components with its Support Package Level).

You may check out this:

[SAP Note 1083685 - Runtime error FAILED in Service Session Workbench|http://www.service.sap.com/sap/support/notes/1083685 ]

Best regards,

Ruediger

[Former Member · Accepted solution]

Hi Ruediger

I have applied the Pack and I am still getting the same short dump.

I am not sure why as it only happens when I connect to our Production Landscape - if I connet to the Solution Manager on it appears to be fine!!

A strange problem - but is means we cant make changes to our CCMS monitoring!

Thanks

Phil

[former_member209604 · Accepted solution]

Hi Phil,

The Note says:

Important: After you implement the correction instructions, this runtime error still occurs for sessions in which the error was determined. Therefore, you must reset these sessions. If you cannot reset a session, to avoid loss of data, contact SAP Support to have the session repaired.

I assume, that you have not done this.

Can the Setup SysMon Data be lost for this system? If yes, continue. If not, create a message on SV-SMG-SWB.

Try to find out the session number of Setup System Monitoring, which creates the dump.

Therefore go to the place, where you can open the Setup. On Mouse Over a number is displayed (13 digits, starting with the SolMan client.), note the session number.

Run transaction DSA and enter the session number. Double click on line in left window, expand tree in right window and choose in the context menu "Session Components -> Reset". This will delete all data from Setup System Monitoring.

Afterwards you are able to run Setup Sys Mon as you have tried before.

Best regards,

Ruediger

[Former Member · Accepted solution]

Thanks for that.

I have raised an OSS call to SAP about this and I will let you know what the outcome is.

Thanks for all your help

Phil

[Former Member · Accepted solution]

Ok, I have now raised an OSS call with SAP regarding this and have had a reply.

Basically they said that I have to reset the session - so I have done this but now the 'Setup System Monitoring' is now not a link!!!

I have gone to SAP to find out how I resolve this - as I can access the session in DSA!

If anyone can tell me how to resolve this that would be great!

Cheers

Phil

[former_member209604 · Accepted solution]

Hi Phil,

you will receive very soon the solution within your message. Session has been already corrected in your system.

Ruediger

[Former Member · Accepted solution]

Dear all,

I followed the above procedure to delete the setup system monitoring refrence number and now i see it is deleted in tcode DSA but now the 'Setup System Monitoring' is now not a link!!!

How can I restore this session back or get the link in 'Setup System Monitoring' ????????

Please help asap

Thanks in advance

[Former Member · Accepted solution]

Dear all,

I followed the above procedure to delete the setup system monitoring refrence number and now i see it is deleted in tcode DSA but now the 'Setup System Monitoring' is now not a link!!!

How can I restore this session back or get the link in 'Setup System Monitoring' ????????

Please help asap

Thanks in advance

[former_member452752 · Accepted solution]

Dear Phil

I just want to know if you solved your issue? And how you solved this problem?

A similar short dump apear in our system in transaction DSWP.

Many thank

Best Regards.

Emmanuel

[Former Member · Accepted solution]

My Problem got solved..... by editting the SAP table (DSVASSESSADMIN) and removing the flag for deletion for the affected DSA session.

Hope it solves for yours.

[former_member452752 · Accepted solution]

Many thanks for your help.

we find another solution by resetting the monotoring for the entire solution in TR DSWP.

Best regads;

Emmanuel

[Former Member]

Phil,

YOu have to apply this note to solve your issue.

Note 1128026 - Runtime error RAISE_EXCEPTION when opening sessions

Thanks,

Uday