cancel
Showing results for 
Search instead for 
Did you mean: 

EWA report not being generated - PLEASE HELP !!!

symon_braunbaer
Participant
0 Kudos

Dear experts,

since about one week we are trying to figure out, why no EWA report on our production BW system is being generated!

In the Solution Manager, we see the session with a red flag and NO attachment!

Today I have gone very detailed through SAP note 1769513 - EWA not generated - session data is overdue (red flag status)

and all the notes that it refers to. I refreshed the service definitions of SDCCN and then I tried to generate an ad-hoc

EWA report as described here:

How to create an Ad Hoc EWA report in Solution Manager 7.1 - Solution Manager - SCN Wiki

But unfortunately it came again with a red flag and NO attachment! Please kindly help us with that, we are getting

quite desperate...

Many thanks !!

Accepted Solutions (1)

Accepted Solutions (1)

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Symon,

Is SM:EXEC SERVICES failing with a dump with OBJECTS_OBJREF_NOT_ASSIGNED - Exception - CX_SY_REF_IS_INITIAL ?

If yes, then apply 2077732 Exception 'CX_SY_REF_IS_INITIAL' occured while the background job SM: EXEC SERVICES executed"

Regards,

symon_braunbaer
Participant
0 Kudos

Hello and many thanks,

no, the header of the dump is like this:

Category           ABAP Programming Error
Runtime Errors     UNCAUGHT_EXCEPTION
Except.            CX_DSVAS_API_TEXT_PROPERTIES
ABAP Program       CL_DSVAS_PROC_CHECK_GROUP=====CP

Application Component  SV-SMG-SVD-SWB

Date and Time     

29.10.2014 12:54:04


And the body of the dump goes like this:

Short text

    An exception occurred that was not caught.

What happened?

    The exception 'CX_DSVAS_API_TEXT_PROPERTIES' 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

     'CL_DSVAS_PROC_CHECK_GROUP=====CP' has to be

    terminated.

What can you do?

    Note down which actions and inputs caused the error.

    To process the problem further, contact you SAP system

    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look

    at and manage termination messages, and you can also

    keep them for a long time.

Error analysis

    An exception occurred which is explained in detail below.

    The exception, which is assigned to class 'CX_DSVAS_API_TEXT_PROPERTIES', was

     not caught and

    therefore caused a runtime error.

    The reason for the exception is:

    Type conflict saving to check table (Value=&MAXSIZE&, Type=&R&)

How to correct the error

    If the error occures in a non-modified SAP program, you may be able to

    find an interim solution in an SAP Note.

    If you have access to SAP Notes, carry out a search with the following

    keywords:

   "UNCAUGHT_EXCEPTION" "CX_DSVAS_API_TEXT_PROPERTIES"

   "CL_DSVAS_PROC_CHECK_GROUP=====CP" or "CL_DSVAS_PROC_CHECK_GROUP=====CM00A"

   "EXECUTE_ACTION"

   If you cannot solve the problem yourself and want to send an error

   notification to SAP, include the following information:

   1. The description of the current problem (short dump)

      To save the description, choose "System->List->Save->Local File

   (Unconverted)".

   2. Corresponding system log

      Display the system log by calling transaction SM21.

      Restrict the time interval to 10 minutes before and five minutes

   after the short dump. Then choose "System->List->Save->Local File

   (Unconverted)".

   3. If the problem occurs in a problem of your own or a modified SAP

   program: The source code of the program

      In the editor, choose "Utilities->More

   Utilities->Upload/Download->Download".

   4. Details about the conditions under which the error occurred or which

   actions and input led to the error.

nirmal_konchada
Active Contributor
0 Kudos

Hi,

Apply note 2082889 and then execute the job.

Regards,

Nirmal.K

symon_braunbaer
Participant
0 Kudos

Hi Nirmal!!! Perfect !! That solved my problem and the report has been successfully generated!! Thanks a MILLION, because all the other ton of notes, which I went through, were completely useless in my case!

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

adhoc generation should work, seems you had trouble with service session itself. could you please check the below note and let us know will that helps.

1702475 - Troubleshooting service sessions

thanks

jansi

symon_braunbaer
Participant
0 Kudos

Hello Jansi,

you seem to be closest to what is really going on. It turns out, that despite when I was checking it yesterday, the SM:EXEC jobs were fine, today they are getting canceled again and there are quite a few dumps in ST22. I have checked, that all of them contain:

Error analysis

    An exception occurred which is explained in detail below.

    The exception, which is assigned to class 'CX_DSVAS_API_TEXT_PROPERTIES', was

     not caught and

    therefore caused a runtime error.

    The reason for the exception is:

    Type conflict saving to check table (Value=&MAXSIZE&, Type=&R&)

Also, I do not know anymore, but most probably the job log points to Note 700518 - SAP Service Sessions: How To Do Error Analysis

It is a very long note and I could only briefly scroll through it, as I do not have much time this week. Basically it only describes several problems, but does not offer any solution. I saw it only describing how to open an OSS message 😞

Furthermore, I see that this note only mentions Solution Manager 7.0 EHP 1 and we have Solution Manager 7.1 SPS12.

I will then try to analyze the dumps with the help of the note that you sent me.

Kindly let me know if this info lets you suggest something more about the problem, otherwise I will report back after I have checked your note. Many thanks once again!

giri_ayyagari
Active Participant
0 Kudos

Hi Symon

Ps. post screen shots.

-giri

symon_braunbaer
Participant
0 Kudos

Hi Giri, ok fine, it is not a problem to post screenshots, just kindly let me know which screenshots exactly would you like to see!

venkat_naresh2
Explorer
0 Kudos

Hi,

Make sure the Back RFC is fine from BI system(SM_<SID>CLNT<000>_BACK) before run a refresh job.

Rgds,

Venkat

symon_braunbaer
Participant
0 Kudos

Hi Venkat and thanks for your reply! The connection is fine, I have even tried both connection and authorization tests.