No EWA'a post ST-PI & ST-A/PI Upgrade

[Former Member]

Hi,

We've upgraded ST-PI & ST A/PI to the latest - ST-A/PI 01N 700SOL (SAPKITAS1H) - Application Tools for Solman 7.0-7.1 & ST-PI 2008_1_700 (SAPKITLRD4).

Post this upgrade, we're seeing the following dumps & no EWA's are getting generated.

The EWA's have a Grey status (the 2 bottles).

Here's the dump:

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_DSVAS_API_SERVICE_SESSION

Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "RAISE_ERROR".

The main program was "RDSMOPBACK_AUTOSESSIONS_1_SOL ".

In the source code you have the termination point in line 48

of the (Include) program "LDSVAS_PROCERI".

The program "SAPLDSVAS_PROC" was started as a background job.

Job Name....... "SM:EXEC SERVICES"

Please help..

Thank you,

Saba.

[Former Member · Accepted solution]

Hi,

please check the sap note

[ Note 1615266 - EarlyWatch Alert: UNCAUGHT_EXCEPTION in ABAP_Trans|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1615266]

and proceed. before that try to delete and recreate the service definitions,this also some time works.

Thanks,

Jansi

[Former Member · Accepted solution]

Hi Jansi,

This note talks about program RDSVASAABAP_TRANS, whereas my error points out to: SAPLDSVAS_PROC & LDSVAS_PROCERI..would this work..we're currently on SP 3 for ST-SER.

There's also Note 1502573..not so sure on this one though.

Thanks,

Saba.

[Paul_Babier · Accepted solution]

Hello,

This sounds a lot like your Service Content is out of date.

I recommend you execute transaction code AGS_UPDATE and check for red traffic lights.

You should find some, because most issues with the exception CX_DSVAS_API_SERVICE_SESSION have been addressed via Service Content Update.

Service Content Update only updates the current release of ST-SER, which is 701_2010_1, any older releases will not get SCUs.

This is most likely the resolution to your issue.

Regards,

Paul

[Former Member · Accepted solution]

Hi Paul,

Thanks..I used AGS_UPDATE..however the dump still persists.

Manually I'm able to generate the EWA's; however, the scheduled SM:EXEC job always fails with the same dump..

Also, I'm able to view the EWA data in DSA.

Thank you,

Saba.

Edited by: Saba Sheikh on Jan 30, 2012 8:12 AM

[Former Member · Accepted solution]

Hi,

My SM:EXEC_SERVICES job's still failing with the same dump.

The EWA data is available in DSA & manually I'm able to generate a successful report, but the automatic generation is still a problem...the 2 bottles.

Please help.

Thank you,

Saba.

[Former Member · Accepted solution]

Hi Saba,

If your SERVICE CONTENTS are up to date, you may need to reset the sessions that are causing this DUMP through transaction DSA to see if it will process after. Have you already tried this? If not, I suggest that you do.

Regards,

Mark

[Paul_Babier · Accepted solution]

Hello Saba,

The Service Session is scheduled for a specific day, it is created on solution manager first.

You will see 1 flask.

Then the SDCCN tasks runs on the Managed system and it opens the session to read the header to obtain the session number..

Then the collected data is processed for transport and is shipped to Solution Manager via the *BACK RFC and populates the service session with the collected data.

If this doesn't happen, the session becomes overdue and it will be assigned a red flag.

If this does happen the icon turns to two flasks.

The two flasks indicate the data is available in the service session, but now needs to be processed and rated (emailed too if configured) by the job SM:EXEC SERVICES.

While you can generate an HTML or Word Report from a session you open in DSA, I don't think the report is completed yet, as there is additional processing done by SM:EXEC SERVICES.

I am tending to agree with Mark. DSA can open the session with out the dump, so its sounding like service content.

You may need to run RDSMOP_SERV_CONTENT_RESET ( keep downloads), if the reset of the session doesn't resolve.

Regards,

Paul

[Former Member · Accepted solution]

Hi Everybody,

Thanks a lot for all your suggestions & the lovely explanation, Paul.

My main issue is that since the ST patch application, SM:EXEC_SERVICES fails continously with the same dump.

I've since then applied ST-SER 2010 till patch 9 & implemented Note 1502573.

But the job still fails continuously as a result of which the reports are not populating DSWP automatically.

I've updated the service content also (AGS_UPDATE)..if I push the report from DSA, it goes to DSWP.

The dump details are as below:

Active Calls/Events

No. Ty. Program Include Line

Name

17 METHOD SAPLDSVAS_PROC LDSVAS_PROCERI 48

LCL_ERROR_HANDLER=>RAISE_ERROR

16 METHOD SAPLDSVAS_PROC LDSVAS_PROCTAI 1482

LCL_CHECK_TABLE=>UNPACKED_SET

15 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 2445

LCL_CHECK_TREENODE=>UNPACKED_TABLES_SET

14 FUNCTION SAPLDSVAS_PROC LDSVAS_PROCU49 61

DSVAS_PROC_API_TABLES_SET

13 FORM /1AGS/ASQL_OPT_DB6_________003 /1AGS/ASQL_OPT_DB6_________003 6556

ACTION_073

12 METHOD SAPLDSVAS_PROC LDSVAS_PROCCD0 2345

LCL_ACTION_SEQUENCE=>EXECUTE

11 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1836

LCL_CHECK_TREENODE=>EXECUTE

10 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1887

LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE

9 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1901

LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE

8 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1901

LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE

7 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1901

LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE

6 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 2395

LCL_SESSION=>EXECUTE

5 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1828

LCL_SESSION=>CONTEXT_INSTANCES_CREATE

4 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 2365

LCL_SESSION=>EXECUTE

3 FUNCTION SAPLDSVAS_PROC LDSVAS_PROCU02 303

DSVAS_PROC_SESSION_OPEN

2 METHOD CL_DSMOP_SOLUTION=============CP CL_DSMOP_SOLUTION=============CM01P 189

CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES

1 EVENT RDSMOPBACK_AUTOSESSIONS_1_SOL RDSMOPBACK_AUTOSESSIONS_1_SOL 147

START-OF-SELECTION

Thanks,

-S.

[Paul_Babier · Accepted solution]

Hello Saba,

Based on the additional information in the call stack, I am able to identify the problem.

I see the following response from the developer looking into it.

"A bug fix is currently in progress and will be available next week in

the next Service Content Update" .

This was dated 02.03.2012

So please keep an eye on Service Content updates that become available in the next week, and ensure updates are downloaded and activated. This will resolve this dump.

Regards,

Paul

[Former Member · Accepted solution]

Hi Paul,

Your decimal notation solution worked :):):)

Do I still need to check for next week's SCU's ?

I set the decimal notation for the background user running the job to X.XXX.XXX,XXX

Thank you,

Saba.

[daniel_nicol]

Hi,

Please provide the dump header and the list of "Active Calls/Events" you see in the dump.

Best regards,

Daniel.

Edited by: Daniel Nicol on Feb 2, 2012 10:39 PM