on 12-03-2008 3:50 PM
Hi, I was applying SPS 15 to our SolutionManager System, then came to a situation where it gave an error. I follwed the SAP NOTE 662441 as follows
With SP15 (SAPKITL425) SAP strictly recommends to upgrade your ST-SER to the release 700_2007_1 or higher. Therefore use transaction SAINT instead of transaction SPAM to patch your system to SAP Solution Manager 7.0 Stack 15 (01/2008). If you try to patch your system via SPAM and your ST-SER release is 700_2006_1 or less you will receive one of the following information within SPAM during phase ADDON_CONFLICTS_?:
a) Conflicts Between Add-On ST-SER 700_2005_2 and Support Packages SAPKITL425 Include CRT
b) Conflicts Between Add-On ST-SER 700_2006_1 and Support Packages SAPKITL425 Include CRT
c) Conflicts Between Add-On ST-SER 700_2006_2 and Support Packages SAPKITL425 Include CRT
Please be aware there is no physical Conflict Resolution Transport (CRT) available to solve this conflict (it is not planned to provide such a CRT). You have to patch your system via SAINT not via SPAM:
1. Delete your SPAM-QUEUE by pressing the Display/Define button within SPAM.
2. Download all ST-SER Delta-Upgrade packages from the Software Download Center into your EPS-Inbox.
3. Call transaction SAINT and press Start button.
4. Select ST-SER 700_2007_1 or higher and press Continue button
All neccessary component packages will automatically be included into a valid SAINT-queue
Now my SAINT got stuck in Import Proper phase and I can not delete the queue or can do anything.
Any suggestions to solve this problem?
Thanks in Advance.
Vikram
hello Vikram,
were you able to release the queue which was stuck ?
Update us ...
Regards,Amber S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I did. The parameters I used were SAINT, X and X to force it to delete the queue for the tool SAINT that I was stuck in. Make sure you really want to reset the queue and you cannot fix the error any other way. In my case I forgot to update the spam/saint tool first so I had to delete the queue to do that. Then I will reapply the component in full.
Hello,
FOr resetting the Queue follow the procedure.
go to Function builder transaction code.sm36
check for function module RESET_OCS_QUEUE
Pass the values and reset the queue. Hope it helps in ressetting problem
Regards,Amber S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is it hanging or you're getting an error? if you're getting an error post it here... if not then check your import monitor to see whats the status.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I've encountered exactly the same behaviour as described above. In phase IMPORT_PROPER I get a short dump:
*******************************************************
Runtime Errors TABLE_INVALID_INDEX
Date and Time 22.12.2008 15:43:13
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSLOG" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
When changing or deleting one or more lines of the internal table
"\FUNCTION=TR_READ_AND_DISPLAY_LOG\DATA=LT_LINES" or when inserting in the
table "\FUNCTION=TR_READ_AND_DISPLAY_LOG\DATA=LT_LINES", "-1" was used as
the line index. An index less than or equal to zero is not
allowed.
Source code:
225 *& reduce pt_lines to the required parts.
226
227 * delete block before required
228 IF lv_start_index <> 1 .
229 lv_delblock1_beg = 1 .
230 lv_delblock1_end = lv_start_index - 1 .
---> DELETE pt_lines FROM lv_delblock1_beg TO lv_delblock1_end
232 ENDIF.
233
******************************************************************
I can't remove nor correct the SAINT queue now. I didn't find any OSS note describing the problem. Any help would be appreciated.
Thanks
Herwig
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.