cancel
Showing results for 
Search instead for 
Did you mean: 

CX_ENH_INTERNAL_ERROR during ECC6 upgrade

Former Member
0 Kudos

Dear Experts,

I am upgrading my SAP system from ECC5 to ECC6 Enhancement Pack 4,

SPS7, right now in the downtime phase JOB_RSINDCHK, we are getting an

Error as per below.

Severe error(s) occured in phase MAIN_NEWBAS/JOB_RSINDCHK!

Last error code set: RFC_ERROR 2: DUMP_ERROR

In the system I can notice an ABAP dump.

#############################

The exception 'CX_ENH_INTERNAL_ERROR' 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_R3STANDARD_PERSISTENCE=====CP' has to be

terminated.

######################

Based on SAP notes search I can find that applying SAP Note 1483283

will help resolve the above issue, so I unlock the system using tp &

try applying the SAP Note via SNOTE & manually using SE38, but this

leads to more ABAP dumps.

As we know the system is under upgrade now, so most of the transactions dump

now. I've raise a message with SAP for this issue, but till they revert, wondering if anybody has faced similar problem.

Thanks & Rgds,

Abhishek

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi

I have the same problem with RSINDCHK JOB in EHP4 implementation.

Severe error(s) occured in phase MAIN_NEWBAS/JOB_RSINDCHK!

Last error code set: RFC_ERROR 2: DUMP_ERROR

DUIMP (ST22):

Termination occurred in the ABAP program "CL_R3STANDARD_PERSISTENCE=====CP" -

in "LOAD_SPOT".

The main program was "RSINDCHK ".

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

of the (Include) program "CL_R3STANDARD_PERSISTENCE=====CM00Z".

The program "CL_R3STANDARD_PERSISTENCE=====CP" was started as a background job.

Job Name....... "RSINDCHK"

Job Initiator.. "DDIC"

Job Number..... 10424400

The termination is caused because exception "CX_ENH_INTERNAL_ERROR" occurred in

procedure "SFW_GET_SWITCHPOS" "(FUNCTION)", but it was neither handled locally

nor declared

in the RAISING clause of its signature.

The procedure is in program "SAPLSFW_COMMON "; its source code begins in line

1 of the (Include program "LSFW_COMMONU01 ".

I tried to check SAP NOTE 1483283 but i have problem opening this note::

"Note 1483283

The requested SAP Note is either in reworking or is released internally only "

Please can you help me and tell me what manually change have i to do in step 2 (LSFW_COMMONE01 program)

1. Unlock system as Snow's reply

2. From SE38, change program LSFW_COMMONE01

3. Lock system

4. Continue EHPI process, it can continue to next phase now..

Thanks for your help

Best regards

JTAD

andreas_herzog
Active Contributor
0 Kudos

Hi, we faced the exact same error while applying EHP1 to a BI 7.0 in phase JOB_DBDIF_UPG...but without any troubles whatsoever; the phase afterwards succeeded succesfully...

How did you exactly edit the include?

Did you choose to use a new change request?

GreetZ, AH

former_member217765
Active Participant
0 Kudos

Hi,

As I replied to you in the message 0785706 2010 reported by you.

I logged on the system and found that Note 1483283 is NOT implemented in your system.

Please try to implement this note manually just as I suggested in the message.

With Best Regards

Julia

Former Member
0 Kudos

Hello Snow & Julia,

Many Thanks for your replies, but as communicated yesterday, at the time of applying changes via SE38 to the include program LSFW_COMMONE01, it's giving further ABAP dumps. (May be I didn't explained in detail).

I can execute SE38, can change LSFW_COMMONE01, but at the time of saving the changes in Transport, it gives below ABAP dump

##############

Runtime Errors

SYNTAX_ERROR

Date and Time 28.09.2010

10:47:02

Short text

Syntax error in program "% _CSCPR ".

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSCPRPR" had to be terminated because

it has come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "%_CSCPR " in

include "%_CSCPR " in

line

17:

"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also

defined in the Dictionary. . control structure introduced

with "CLASS" . . . . "

". . . . . ."

" "

The include has been created and last changed

by:

Created

by: "SAP "

Last changed

by: "SAP "

Error in the ABAP Application

Program

The current ABAP program "SAPLSCPRPR" had to be terminated because

it has come across a statement that unfortunately cannot be executed.

tomas_black
Employee
Employee
0 Kudos

Hello Abhishek Goel,

regarding the error:

"The type name "SCPR_FLDV_TAB" is ambiguous, since it is also defined in the Dictionary. . control structure introduced with "CLASS" . . . . " ". . . . . ."

The object "SCPR_FLDV_TAB" is not required in release 700 so you have to delete the same using function module DD_NAMETAB_DELETE (in transaction SE37) - enter SCPR_FLDV_TAB as tabname and choose execute.

Deleting this object SCPR_FLDV_TAB will remove the inconsistency from program "%_CSCPR", then the upgrade will be able to continue.

Best regards,

Tomas Black

Former Member
0 Kudos

Today, I got exactly same error with you in upgrade from ECC6 to ECC6 EHP4 SPS7. I got solution from this thread.

I followed Julia's reply. Implemen note 1483283 manually.

1. Unlock system as Snow's reply

2. From SE38, change program LSFW_COMMONE01

3. Lock system

4. Continue EHPI process, it can continue to next phase now..

Edited by: Fendhy Ongko on Oct 1, 2010 7:56 AM

Former Member
0 Kudos

Thanks very much to all of you.

I ran into the same error, upgrading to ECC 6.04.

I had the same dump while saving changes done on the ABAP editor to LSFW_COMMONE01.

I deleted nametab SCPR_FLDV_TAB (then I could save changes) , followed the rest of Note 1483283 and the problem was solved !

former_member215759
Active Participant
0 Kudos

Dear,

Please have a look at SAP Note #1483283, which describes that error. As you are at the phase MAIN_NEWBAS using SNOTE maybe isn't possible. Hence it is necessary to implement the corrections of that note manually after unlock the system.

To apply the note, you could unlock the system. Then try to manually apply the code instruction.

Please use the following commands to unlock the system:

tp unlocksys <SID> pf=<transport profile>

(unlocks the system for user logon)

and

tp unlock_eu <SID> pf=<transport profile>

(unlocks the system for DDIC maintenence)

After execution of these commands you can login with your usual userid and do the changes required by the above note.

After logon you might lock the system again to prevent other users from logon by using the folowing command:

tp locksys <SID> pf=<transport profile>

After finishing the changes you might use the following command to prevent user changes again.

tp lock_eu <SID> pf=<transport profile>

Regards,

Snow