run time error in RFC

[Former Member]

Hi,

run time error occur in RFC when i try to create,change and opening the rfc connections(like abap connections).its showing run time error : RAISE_EXCEPTION. SHORT DECCRIPTION :EXCEPTION CONDITION DP _ERROR RAISED.

PLEASE HELP ME TO SOLVE THIS PROBLEM.

[Former Member · Accepted solution]

Hi,

This is may be a problem with your GUI version or patch level. Please check and update the same.

incase if its not work than please inform us.

With Regards,

CSK

[Former Member · Accepted solution]

Hi,

I Installed the Latest Patches of Sapgui but the run time error is not cleared.help me as soon as possible to solve this error.

[Former Member]

Thanks to all for supporting me to solve this error.

[Former Member]

Hi,

The problem is solved by uninstalling the sapgui7.10 and sapgui latest patches and reinstalled the sapgui and their patche and by restarting the run time error is solved. Thanks to all for supporting me to solve this error.

[Former Member]

So, that is the cause..inturrupted your program.

Debug this program with Abaper and know the result, where and why it is getting struck.

Paste the details here....

Is it asked for SPDD/SPAU corrections(at the time of patch upgrade)

Regards

Nick Loy

[Former Member]

Take help from ABAPer in debugging....paste the debug resulsts here.

Have you upraded any patch on this system?

Regards

Nick Loy

[Former Member]

Hi,

yes i upgraded the BI ADD ON PATCHES.

[Former Member]

Hi,

Please post the RFC trace. go to SM59 -- RFC-->Display error.

With Regards,

CSK

[Former Member]

HI,

THIS THE ERROR DETAILS IN RFC.

Runtime Errors RAISE_EXCEPTION

Date and Time 18.03.2007 10:56:07

Short text

Exception condition "DP_ERROR" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

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.

Edited by: pugazh raj on Dec 18, 2009 11:42 AM

[Former Member]

Error analysis

A RAISE statement in the program "CL_ALV_TREE_BASE==============CP"

exception

condition "DP_ERROR".

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.

-

w to correct the error

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

find an interim solution in an SAP Note.

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

keywords:

"RAISE_EXCEPTION" " "

"CL_ALV_TREE_BASE==============CP" or "CL_ALV_TREE_BASE==============

"GET_FRONTEND_FIELDCATALOG"

or

"CL_ALV_TREE_BASE==============CP" "DP_ERROR"

or

"SAPMCRFC " "DP_ERROR"

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 whic

actions and input led to the error.

[Former Member]

tem environment

SAP-Release 700

Application server... "e0215"

Network address...... "192.168.1.215"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "2x Intel 801586"

Hardware type........ "2x Intel 801586"

Character length.... 8 Bits

Pointer length....... 32 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "mail"

Database type..... "ADABAS D"

Database name..... "NSP"

Database user ID.. "SAPNSP"

Char.set.... "English_United State"

SAP kernel....... 700

created (date)... "Jan 29 2007 00:33:09"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "SQLDBC 7.6.0.036 CL 140088 "

Patch level. 95

Patch text.. " "

Database............. "MaxDB 7.6, MaxDB 7.7"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

Memory consumption

Roll.... 8112

EM...... 6271776

Heap.... 0

Page.... 49152

MM Used. 1765968

MM Free. 1368360

User and Transaction

Client.............. 000

User................ "BCUSER"

Language key........ "E"

Transaction......... "SM59 "

Program............. "CL_ALV_TREE_BASE==============CP"

Screen.............. "SAPMCRFC 0100"

Screen line......... 0

Edited by: pugazh raj on Dec 18, 2009 11:48 AM

[Former Member]

Information on where terminated

Termination occurred in the ABAP program "CL_ALV_TREE_BASE==========

in "GET_FRONTEND_FIELDCATALOG".

The main program was "SAPMCRFC ".

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

of the (Include) program "CL_ALV_TREE_BASE==============CM00D".

Trigger Location of Runtime Error

Program CL_ALV_TREE_BASE==============CP

Include CL_ALV_TREE_BASE==============CM00D

Row 23

Module type (METHOD)

Module Name GET_FRONTEND_FIELDCATALOG

Source Code Extract

Line SourceCde

1

2 method get_frontend_fieldcatalog.

3

4 * exit in batch mode

5 if not m_batch_mode is initial.

6 et_fieldcatalog[] = mt_fieldcatalog[].

7 exit.

8 endif.

9

10 * get column orders

11 data l_columns type treev_cona.

12 call method mr_column_tree->get_column_order

13 changing

14 columns = l_columns

15 exceptions

16 cntl_system_error = 1

17 dp_error = 2

18 failed = 3.

19 case sy-subrc.

20 when 1.

21 raise cntl_system_error.

22 when 2.

>> raise dp_error.

24 when 3.

25 raise failed.

26 endcase.

27

28 * get columns

29 types: begin of lt_width_type,

30 h_col_key type lvc_s_fcat-h_col_key,

31 width type i,

32 end of lt_width_type.

33 data: lt_width type table of lt_width_type,

34 l_width type lt_width_type.

35 field-symbols: <ls_fieldcatalog_wa> type lvc_s_fcat.

36 l_width-width = 0.

37 loop at mt_fieldcatalog assigning <ls_fieldcatalog_wa>

38 where no_out <> 'X' and

39 tech is initial.

40 l_width-h_col_key = <ls_fieldcatalog_wa>-h_col_key.

41 append l_width to lt_width.

42 endloop.