cancel
Showing results for 
Search instead for 
Did you mean: 

SAPKW70017 shows error XPRA_EXECUTION

Former Member
0 Kudos

Dear Support,

While applying SAPKW70017 it shows error.

The import was stopped, since an error occurred during the phase

XPRA_EXECUTION, which the Support Package Manager is unable to resolve

without your input.

After you have corrected the cause of the error, continue with the

import by choosing Support Package -> Import queue from the initial

screen of the Support Package Manager.

The following details help you to analyze the problem:

- Error in phase: XPRA_EXECUTION

- Reason for error: TP_STEP_FAILURE

- Return code: 0012

- Error message: OCS Package SAPKW70017, tp step R, return code

0012

This is our BI Server. On XI and ECC Server i have applied without any error.

Please revert with the helful suggetion.

Regards,

Ajit

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Also take a look at the /usr/sap/trans/log directory to check the log file of the failed import - maybe you find further information for the problem there.

Former Member
0 Kudos

Dear Sven Sören Dinter,

Please find the /usr/sap/trans logs for SAPKW70017 as it says 1AETR012XProgram terminated (job: "RDDEXECL", no.: "17383200"). and and when we check Job Logs of User DDIC the above job shows canceled. we tried to shedule that job but fail to do so.

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

1 ETP199X######################################

1 ETP162 EXECUTION OF REPORTS AFTER PUT

1 ETP101 transport order : "SAPKW70017"

1 ETP102 system : "BID"

1 ETP108 tp path : "tp"

1 ETP109 version and release : "372.04.57" "700"

1 ETP198

2 EPU126XPost-import methods for change/transport request: "SAPKW70017"

4 EPU111 on the application server: "sapbidev"

2 EPU122XPost-import method "O2_XSLT_AFTER_IMPORT" started for "XSLT" "L", date and time: "20091016173832"

3 EPU182 Post-processing for &2"XSLT" &3"RSRD_INSPECTION_DATA" was already performed successfully earlier&1"R3TR"

3 EPU123 Post-import method "O2_XSLT_AFTER_IMPORT" completed for "XSLT" "L", date and time: "20091016173832"

2 EPU122XPost-import method "CLS_AFTER_IMP_AVAS" started for "AVAS" "L", date and time: "20091016173832"

3 EPU182 Post-processing for &2"AVAS" &3"477E7C558320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7C568320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7C928320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7C938320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7CCF8320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7CD08320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7D0C8320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7D0D8320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7D498320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7D4A8320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7D868320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7D878320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7DC38320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7DC48320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7E0C8320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7E0D8320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7E498320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7E4A8320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7E868320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7E878320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7EC38320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"477E7EC48320310BE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"47817C97DADC179CE10000000A114E57" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"47817C9DDADC179CE10000000A114E57" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"47817D06DADC179CE10000000A114E57" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"47821762183F6DFDE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"47821763183F6DFDE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"4782179F183F6DFDE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"478217A0183F6DFDE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"478217E1183F6DFDE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"478217E2183F6DFDE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"47854A2E96EB48A6E10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"47854A2F96EB48A6E10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"4785FF73F99E5A0FE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"AVAS" &3"4785FF75F99E5A0FE10000000A1553FF" was already performed successfully earlier&1"R3TR"

3 EPU123 Post-import method "CLS_AFTER_IMP_AVAS" completed for "AVAS" "L", date and time: "20091016173832"

2 EPU122XPost-import method "MSS_SDBP_AFTER_IMP" started for "SDBP" "L", date and time: "20091016173832"

3 EPU182 Post-processing for &2"SDBP" &3"sap_atomic_BW_create_as_select" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"SDBP" &3"sap_atomic_BW_create_as_select 8.0A" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"SDBP" &3"sap_atomic_BW_create_as_select 9.0A" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"SDBP" &3"sap_atomic_BW_create_as_select A.0A" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"SDBP" &3"sap_atomic_BW_create_like" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"SDBP" &3"sap_atomic_BW_create_like 8.0A" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"SDBP" &3"sap_atomic_BW_create_like 9.0A" was already performed successfully earlier&1"R3TR"

3 EPU182 Post-processing for &2"SDBP" &3"sap_atomic_BW_create_like A.0A" was already performed successfully earlier&1"R3TR"

3 EPU123 Post-import method "MSS_SDBP_AFTER_IMP" completed for "SDBP" "L", date and time: "20091016173832"

2 EPU122XPost-import method "PRGN_AFTER_IMP_SUSO_SAP_ALL" started for "SUSO" "L", date and time: "20091016173832"

3 EPU182 Post-processing for &2"SUSO" &3"S_RS_RSFC" was already performed successfully earlier&1"R3TR"

3 EPU123 Post-import method "PRGN_AFTER_IMP_SUSO_SAP_ALL" completed for "SUSO" "L", date and time: "20091016173832"

2 EPU122XPost-import method "RS_AFTER_IMPORT" started for "WWPA" "L", date and time: "20091016173832"

1AETR012XProgram terminated (job: "RDDEXECL", no.: "17383200")

1AEPU320 See job log"RDDEXECL""17383200""BID"

1 ETP162 EXECUTION OF REPORTS AFTER PUT

1 ETP110 end date and time : "20091016173847"

1 ETP111 exit code : "12"

1 ETP199 ######################################

Regads,

Ajit

former_member204746
Active Contributor
0 Kudos

read your error message, it clearly says:

See job log"RDDEXECL""17383200""BID"

so, go in SM37, find job logs for job RDDEXECL. look for the one that ran at 17:38.32.

Former Member
0 Kudos

Dear Eric,

Thanks for the reply.

I have checked the Job log for RDDEXECL. pl find below the details.

Job log overview for job: RDDEXECL / 10224000

Date Time Message text Message class Message no. Message type

20.10.2009 10:22:40 Job started 00 516 S

20.10.2009 10:22:40 Step 001 started (program RDDEXECL, variant , user ID DDIC) 00 550 S

20.10.2009 10:22:40 All DB buffers of application server sapbidev were synchronized PU 170 S

20.10.2009 10:22:45 ABAP/4 processor: SYNTAX_ERROR 00 671 A

20.10.2009 10:22:45 Job cancelled 00 518 A

Actualy when we run SAPKW70017 it get Error in phase: XPRA_EXECUTION. and at the same time Job RDDEXECL shows cancel pl find the Error Message.

The import was stopped, since an error occurred during the phase

XPRA_EXECUTION, which the Support Package Manager is unable to resolve

without your input.

After you have corrected the cause of the error, continue with the

import by choosing Support Package -> Import queue from the initial

screen of the Support Package Manager.

The following details help you to analyze the problem:

- Error in phase: XPRA_EXECUTION

- Reason for error: TP_STEP_FAILURE

- Return code: 0012

- Error message: OCS Package SAPKW70017, tp step R, return code

0012

Pl help us, i have allready send a message to SAP and waiting for the reply.

Regards,

Ajit

former_member204746
Active Contributor
0 Kudos

Have you read SAP note 822379? It says:

Procedure for termination in the phase XPRA_EXECUTION

Symptom: The importing of Support Packages terminates in the phase XPRA_EXECUTION with return code 0012. In the related import log, you are referred to the job log of the XPRA job, in which runtime errors (for example, SYNTAX_ERROR) are listed as the cause of the termination.

Solution: It is possible that the errors are caused by note corrections that were implemented before you imported the Support Packages and that were partially deimplemented when you imported the Support Package queue. You can correct such problems by performing a modification adjustment and by implementing the notes that are still valid (yellow or green traffic light in SPAU) again. The modification adjustment is already prepared at this point and it can be called easily in the Support Package Manager by choosing the menu path 'Extras'->'Modification Adjustment'.

To avoid such problems when you subsequently import in the production system, you can include the modification adjustment transports that were created in the development system in the Support Package queue. For more information, see the online documentation of the Support Package Manager ('i' button).

Former Member
0 Kudos

Dear Eric,

We have never implemented any snotes as it is a new server and we are applying patches only.

MrRafael Martín-Maestro

SAP Active Global Support - Netweaver Web Application Server

said to implement notes 1139041 and 1139461 then only we applied sucessfully however still same error, we are waiting for the reply from SAP.

Kindly revert with some helpful tips.

Regards,

Ajit

Former Member
0 Kudos

Can you check via SE09 whether there are any open transports?

Kind regards.

former_member204746
Active Contributor
0 Kudos

Are you also applying other supportpacks at the same time or is SAPKW70017 all alone in its queue?

if it is not alone in its queue, read the SAP note I gave you and search iside that note for the word SYNTAX to find more helpful notes.

Answers (2)

Answers (2)

Former Member
0 Kudos

Dear All,

Thanks for your support.

Our manager said to Reinstall the Server as we are running late. Hence we are closing this message.

Thanks to all.

markus_doehr2
Active Contributor
0 Kudos

> The import was stopped, since an error occurred during the phase

> XPRA_EXECUTION, which the Support Package Manager is unable to resolve

> without your input.

Check for dumps in the system and also for job logs of user DDIC.

Markus

Former Member
0 Kudos

Dear Markus,

Thanks for the reply.

Dump says--

Runtime Errors SYNTAX_ERROR

Date and Time 19.10.2009 09:53:15

-


-


Short text

Syntax error in program "CL_RS_UTILITIES===============CP ".

-


-


What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLRSMANDT" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"CL_RS_UTILITIES===============CP " in include

"CL_RS_UTILITIES===============CM00K " in

line 1:

"Method "GET_FORCE_RELOAD" is not declared or inherited in class "CL_RS"

"_UTILITIES". -"

" "

" "

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 "SAPLRSMANDT" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

-


-


|

-


Error analysis

The following syntax error was found in the program

CL_RS_UTILITIES===============CP :

"Method "GET_FORCE_RELOAD" is not declared or inherited in class "CL_RS"

"_UTILITIES". -"

" "

" "

-


System environment

SAP-Release 700

Application server... "sapbidev"

Network address...... "192.168.51.36"

Operating system..... "HP-UX"

Release.............. "B.11.31"

Hardware type........ "9000/800"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 1

Shortdump setting.... "full"

Database server... "sapbidev"

Database type..... "ORACLE"

Database name..... "BID"

Database user ID.. "SAPSR3"

Terminal................. "HP30476773175"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Apr 2 2009 21:10:20"

create on........ "HP-UX B.11.11 U 9000/800"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 201

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "HP-UX B.11"

Memory consumption

Roll.... 16192

EM...... 8379696

Heap.... 0

Page.... 40960

MM Used. 999440

MM Free. 3187808

-


-


User and Transaction

Client.............. 400

User................ "BASIS"

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

Transaction......... "RSA1 "

Transactions ID..... "4AD8C0A35B1F0DF6E1000000C0A83324"

Program............. "SAPLRSMANDT"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

-


-


Information on where terminated

Termination occurred in the ABAP program "SAPLRSMANDT" - in "RS_MANDT_CHECK".

The main program was "RSAWBN_START ".

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

of the (Include) program "LRSMANDTU01".

-


-


Job overview from: 19.10.2009 at: : :

to: 19.10.2009 at: : :

Selected job names: *

Selected user names: DDIC

Scheduled X Released X Ready X Active X Finished X Canceled

Event controlled Event ID:

ABAP program Program name :

-


Job

Ln

Job CreatedB

Status

Start date

Start time

Duration(sec.)

Delay (sec.)

-


SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Released

0

0

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

00:00:58

3

58

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

01:00:58

3

58

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

02:00:59

4

59

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

03:00:59

3

59

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

04:00:00

25

0

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

05:00:00

12

0

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

06:00:01

10

1

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

07:00:01

16

1

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

08:00:01

4

1

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

09:00:02

3

2

SAP_COLLECTOR_FOR_PERFMONITOR

DDIC

Finished

19.10.2009

10:00:02

3

2

SAP_RSICFDLT

DDIC

Finished

19.10.2009

00:30:58

0

58

SAP_RSICFDLT

DDIC

Finished

19.10.2009

01:30:58

0

58

SAP_RSICFDLT

DDIC

Finished

19.10.2009

02:30:59

0

59

SAP_RSICFDLT

DDIC

Finished

19.10.2009

03:31:59

1

59

SAP_RSICFDLT

DDIC

Finished

19.10.2009

04:30:00

0

0

SAP_RSICFDLT

DDIC

Finished

19.10.2009

05:30:00

0

0

SAP_RSICFDLT

DDIC

Finished

19.10.2009

06:30:01

0

1

SAP_RSICFDLT

DDIC

Finished

19.10.2009

07:30:01

0

1

SAP_RSICFDLT

DDIC

Finished

19.10.2009

08:30:02

0

2

SAP_RSICFDLT

DDIC

Finished

19.10.2009

09:30:02

0

2

SAP_RSICFDLT

DDIC

Finished

19.10.2009

10:30:03

0

3

SAP_SLD_DATA_COLLECT

DDIC

Released

0

0

SAP_SLD_DATA_COLLECT

DDIC

Finished

19.10.2009

05:07:00

1

0

SDB_MONITORING_DATA_AUTO_ACTIONS

DDIC

Finished

19.10.2009

01:00:59

0

0

-


*Summary

88

484

-


Regards,

Ajit