Maintenace certificate error while applying patches through SPAM

[Former Member]

Dear Techies,

we are trying to patch our solution manager(7.0) box to SP26.

we made a system copy to test the scenario and registered in service market place under the same system no. with a different hardware key.

On this copied new machine we are trying to patch using SPAM.

This is the message I am getting.

............

Warning

No valid maintenance certificate found for system SOL.

System ID: XXX

System Number: XXXXXXXXXXXXXXX (Same a source solution manager)

Installation Number: XXXXXXX

Certificate Name: Maintenance_ORA

.............

We have tried to renew the maintenance certificate but the same message we are getting.

Please guide me how to go about in the scenario.

Thanks in advance

Regards,

Kiran

[Former Member · Accepted solution]

Hi Kiran,

In SLICENSE tcode -> New Licenses, what is the status of the maintanence license key? It should show as valid (green).

Regards,

Srikishan

[Former Member · Accepted solution]

Hi Srikishan,

Both

NetWeaver_ORA 04.09.2011 31.12.2012

Maintenance_ORA 04.09.2011 05.12.2011 are in green status.

And the problem was solved.

As there is an issue with the permissions at user shares level.

after assigning the share permissions now system is allowing me to use SPAM for maintenance.

Thanks alot for your reply.

Kiran

[Former Member]

Thanks alot techies

[Former Member]

Suggest to close this thread if your query is answered.

Regards,

Nick Loy

[Former Member]

Now days if you apply patch it need you should update certificate .That is on slicense ,Download certificate Maintenance_MSS from service.sap.com and apply here . You can also configure through solution manager so every time solution manager will apply this .

[Former Member]

Hello,

Do not try to 'renew' the maintenance certificate but we have to request a 'new' maintenance certificate/license + standard license according to this new hardware key.

Also, better to delete all 'old' licenses before applying new ones (in new copied system).

Thanks