cancel
Showing results for 
Search instead for 
Did you mean: 

Patching ST-PI & ST-A/PI - SAPKITAB8K

Former Member
0 Kudos

Good Day,

I am currently trying to patch ST-PI and ST-A/PI as per my EWA report.

I have patched SPAM to Version 7.30/0050 - Latest version

I downloaded the 2 SAR files and have extracted them and added them to the New Support Package's queue.

Current files:

ST-PI 2008_1_710:0007 - SAPKITLRE7

ST-A/PI          01Q_710          0000 - Servicetools for other App./Netweaver200

The new files are:

ST-PI - SAPKITLRE8 - ST-PI 2008_1_710:SP 0008

ST-A/PI - SAPKITAB8K - Servicetools for other App./Netweaver2007

When I loaded the ST-PI file into the queue everything is green and when I import the queue I get the following error:

(Error stop)

DISASSEMBLE

Details:

Saving the current OCS Queue (09.10.2013, 10:22:46)

Import of the current OCS Queue (09.10.2013, 10:22:54)

The import is done with the Standard scenario

Import of the current OCS Queue in background (09.10.2013, 10:23:07)

The import is done with the Standard scenario

The import is continued in phase 'CHECK_REQUIREMENTS'

Import phase 'PROLOGUE' (09.10.2013, 10:23:07)

Import phase 'PROLOGUE' was successfully finished (09.10.2013, 10:23:08)

Import phase 'CHECK_REQUIREMENTS' (09.10.2013, 10:23:08)

Import phase 'CHECK_REQUIREMENTS' was successfully finished (09.10.2013, 10:23:08)

Import phase 'DISASSEMBLE' (09.10.2013, 10:23:08)

Disassemble OCS package SAPKITLRE8

Unknown OCS file format 'ô(' in OCS Package SAPKITLRE8; SPAM/SAINT Update required

Error during disassembling the EPS parcel of OCS Package SAPKITLRE8: 'PATCH_FILE_ERROR'

Abort the import due to an error situation (09.10.2013, 10:23:09)

The error for the ST-A/PI:

(Error stop)

DISASSEMBLE

Details:

Saving the current OCS Queue (09.10.2013, 10:24:45)

Import of the current OCS Queue (09.10.2013, 10:24:50)

The import is done with the Standard scenario

Import of the current OCS Queue in background (09.10.2013, 10:24:57)

The import is done with the Standard scenario

The import is continued in phase 'CHECK_REQUIREMENTS'

Import phase 'PROLOGUE' (09.10.2013, 10:24:57)

Import phase 'PROLOGUE' was successfully finished (09.10.2013, 10:24:57)

Import phase 'CHECK_REQUIREMENTS' (09.10.2013, 10:24:57)

Import phase 'CHECK_REQUIREMENTS' was successfully finished (09.10.2013, 10:24:58)

Import phase 'DISASSEMBLE' (09.10.2013, 10:24:58)

Disassemble OCS package SAPKITAB8K

Unknown OCS file format '#>' in OCS Package SAPKITAB8K; SPAM/SAINT Update required

Error during disassembling the EPS parcel of OCS Package SAPKITAB8K: 'PATCH_FILE_ERROR'

Abort the import due to an error situation (09.10.2013, 10:24:59)

Has anyone had this error and managed to resolve it.

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

former_member185239
Active Contributor
0 Kudos

Hi Dale,

I think .SAR files are not correctly downloaded.

Did you download the .SAR files by the help of SAP Download Manager.

Check the size of the .SAR file and cross checked it on SMP.

You need to follow below things.

1. Check whether the STMS is configured properly or not.

2. Check the TP tools and TP version

3. Put the .SAR files in /usr/sap/trans directory and then run the SAPCAR comamnd which will put the files automatically in ../EPS/in directory.

Then again load the files and start the process.

With Regards

Ashutosh Chaturvedi

Answers (3)

Answers (3)

Reagan
Advisor
Advisor
0 Kudos

Hello

DISASSEMBLE is the phase where the file is unpacked

Provide full access to the transport directory and then start the process again.

Regards

RB

ashish_vikas
Active Contributor
0 Kudos

DISASSEMBLE  Error can come when your source file is corrupted.

ST-PI & ST-API is usually small, try to download and load these from frontend(Support package > Load Pakg> From Front End) and then try again.

best regards

ashish

Former Member
0 Kudos

Hi Clark,

Do one thing remove files from EPS/in and again uncar files into EPS/in and try again to apply Patches.

before starting update just check to make sure required file permissions are available for files.

Thanks,

Venkat