UNCAUGHT_EXCEPTION during Transaction SPROXY

[Former Member]

Hi ,

while exectuing sproxy transaction its giving a short dump.

please see the dump below.

Runtime Errors UNCAUGHT_EXCEPTION

Except. CX_SRAPI_PRECONDITION_VIOLATED

Date and Time 13.05.2008 10:18:03

Short text

An exception occurred that was not caught.

What happened?

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

terminated.

Error analysis

An exception occurred that is explained in detail below.

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

not caught in

procedure "GET_REP_VERSION" "(METHOD)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

An exception occurred

Missing RAISING Clause in Interface

Program CL_SRAPI_SERVICE_REP_ADDRESS==CP

Include CL_SRAPI_SERVICE_REP_ADDRESS==CM004

Row 1

Module type (METHOD)

Module Name GET_REP_VERSION

Trigger Location of Exception

Program CL_SRAPI_SERVICE_REP_ADDRESS==CP

Include CL_SRAPI_SERVICE_REP_ADDRESS==CM004

Row 55

Module type (METHOD)

Module Name GET_REP_VERSION

Source Code Extract

Line SourceCde

25 im_caller_level = api_version

26 RECEIVING

27 result = l_applcomp_client.

28 CATCH cx_hmi_core_exception .

29 RAISE EXCEPTION TYPE cx_srapi_precondition_violated.

30 ENDTRY.

31

32 *-----invoke method and parse result

33

34 CREATE OBJECT l_input

35 EXPORTING

36 im_input = l_dummy_input.

37

38 TRY.

39 CALL METHOD l_applcomp_client->invoke_method

40 EXPORTING

41 im_method_id = cl_hmi_client_factory=>co_method_release

42 im_method_input = l_input

43 RECEIVING

44 result = l_output.

45

46

47 l_output_xstring = l_output->get_output( ).

48

49 *-----test

50 TRY.

51 l_output_dom = cl_proxy_xsd_node=>get_root_node( l_output_xstring ).

52 l_release_node = l_output_dom->get_first_node( ).

53 result = l_release_node->get_value( ).

54 CATCH cx_proxy_gen_error into l_proxy_gen_error.

>>>>> RAISE EXCEPTION TYPE cx_srapi_precondition_violated.

56 ENDTRY.

57

58

59 CATCH cx_srapi_rep_not_available INTO l_rep_not_available_error.

60

61 IF l_rep_not_available_error->http_status_code = 404.

62

63 " Special case: this can happen if connecting to an older

64 " ESR release which do not have the applcomp service

65 result = if_srapi_service_rep_internal=>co_rep_level_30.

66 RETURN.

67

68 ELSE.

69 RAISE EXCEPTION l_rep_not_available_error.

70 ENDIF.

71

Thanks in advance.

[jordi_escodaruiz]

Today we faced the same issue.

Here I document the root cause:

The HTTP destination (SM59) SAP_PROXY_ESR had a user with password expired.

Usually the Logon user must be C (Communication), and has no password expiration. But if this user is changed to A for whatever reason, and password is expired, when changed back to C, the system still asks for password change.