cancel
Showing results for 
Search instead for 
Did you mean: 

LMSERVICE ISAGENT patching does not fulfill the prerequisite

former_member183984
Participant
0 Kudos

Hi

During the managed system configuration, i got the error that ISAGENT   doesnt fulfill the prerequisite,

I am using Solman 7.1 SP12

So, i downloaded the wily and LM service patch, and tried SUM for support package install. But, the SUM is not able to read the SCA files.

Please guide.

Accepted Solutions (1)

Accepted Solutions (1)

former_member185239
Active Contributor
0 Kudos

Hi Shashank,

If you check the TargetVersionReport.html then you will come to know the exact reason.

Since you are moving from ISAGENT SP23 to SP24 thats why it is not picking up the component.

Since Solman 7.1 is based on SAP Netweaver 7.02 you can deploy the same component with the help of JSPM or SDM.

You can only deploy the patches for the corresponding SUM tool not the SP level.

Also check the sapnote 1837305 - SCA provided using Manually Prepared Directory are rejected and not detected by SUM tool during validation or while scanning

With Regards

Ashutosh Chaturvedi

Answers (1)

Answers (1)

former_member183984
Participant
0 Kudos

Seems like I need to generate stack xml? as per the note 1641062?

Software Component Archives - rejected:

      • SCA files that are normally delivered with a stack configuration file, cannot be:
        • installed (Reason ID: 004, 005);
        • updated to higher release (Reason ID: 001, 005);
        • updated to higher SP level (Reason ID: 002, 005);
        • downgraded (Reason ID: 003);

Component Name/Current Version

Target Version
Archive names
TypeStatus / Required Action
ISAGENT
8.23.0
Vendor: sap.com    Provider:  SAP AG

ISAGENT24P_1-10007435.SCA

8.24.0
Vendor: sap.com    Provider: SAP AG
SC
Rejected due to following reason(s):
• 002 : Component sap.com/ISAGENT cannot be updated to higher SP level
• 005 : Component sap.com/ISAGENT is part of the following usage type: SM;
LM-SERVICE
7.10.11.0
Vendor: sap.com    Provider:  SAP AG

LMSERVICE12P_1-20006622.SCA

7.10.12.1
Vendor: sap.com    Provider: SAP AG
SC
Rejected due to following reason(s):
• 002 : Component sap.com/LM-SERVICE cannot be updated to higher SP level
• 005 : Component sap.com/LM-SERVICE is part of the following usage type: SM;
former_member185239
Active Contributor
0 Kudos

Hi Shashank,

I don't think you are using Solman 7.1 SP12 as your LMSERVICE is on SP11.

Also do check the ST component on ABAP side. If the SP level for ST component is 11 then you are on solman 7.1 SP11.

With Regards

Ashutosh Chaturvedi

bxiv
Active Contributor
0 Kudos

I have a feeling he is on ST SP12 but the java stack failed to be updated accordingly.

You will have to use JSPM or generate a stack file if you are going to use SUM.

Best option generate the stack file and fix your entire system with patches/SPs as you have other issues if ST and LM-Service are not on recommended releases.

former_member183984
Participant
0 Kudos

Hi Ashutosh

Thanks for the info.

Yes, i checkd, ST is on SP11.. :S

So, I guess I need to upgrade to SP12, perhaps that would fix the issue.

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Shashank,

Yes, get the XML generated and and use SUM to patch your solution manager system.

Make sure you read released notes for SP12.

Regards,

former_member185239
Active Contributor
0 Kudos

Hi Shawshank,

You dont need to go to sp12.

Just apply the ISAGENT SP24 with the help of SDM or JSPM.

This will solve your problem.

With Regards

Ashutosh Chaturvedi

divyanshu_srivastava3
Active Contributor
0 Kudos

In case he is not moving to SP12

Former Member
0 Kudos

I think JSPM may not work.

former_member183984
Participant
0 Kudos

yes, jspm gave errors, didnt start

Former Member
0 Kudos

Hi Shashank,

You have to check whether it is possible to upgrade only Java stack using SUM in this situation or not because I failed to do so in our scenario. I would request you to proceed with this option once you take suggestions from experts otherwise you may face issues with SUM if something goes wrong. In my situation, I regenerated mopz and upgraded both Abap and Java to SP12 using SUM tool. In my case, our  Abap was on a higher stack (SP08) level and Java on SP04.