License Management Troubleshooting

Introduction

You can find basic information about the process of automatic distribution and the prerequisites for the implementation in the SAP Support Portal:  https://support.sap.com/en/alm/solution-manager/processes-72/maintenance-certificate.html

The points listed there are prerequisites for a successful implementation of the automatic distribution of maintenance certificates and licenses.

The most important prerequisite is that the system data is maintained correctly and is current. Current system data is required to generate valid maintenance certificates for systems.

Frequent Problems and Questions

Check and ensure that the following points apply in the SAP Focused Run system:

  • The system data is current. The system number (18 digits) is set for the systems in the system landscape (transaction LMDB, select the system, choose the "SAP Support Portal" tab).
  • The job SAP_FRN_LIC_DISTRIBUTION in SAP Focused Run runs daily. The log does not contain errors regarding license data requests.
  • You can use report RAGS_MK_DISPLAY_FILE to check if SAP Focused Run contains a license file for the system. The field SWPRODUCTNAME=Maintenance_### declares a maintenance certificate in this file.
  • The application log (transaction SLG1) does not contain errors for object = FRUN, sub object = MAINT_KEY.

In detail: The maintenance certificate for a system is displayed in the SAP Support Portal. In the system, transaction SPAM or SAINT issues the following warning message: "No valid maintenance certificate found for system XXX." In the system in transaction SLICENSE -> Digitally Signed Licenses, the maintenance certificate (Maintenance_<DB>) is not displayed.

Automatic distribution of the maintenance certificate can take several days, the retrieval and installation is executed by a daily job.

The maintenance certificate is requested by SAP Focused Run using the job SAP_FRN_LIC_DISTRIBUTION. It is visible in the SAP Support Portal once it has been successfully generated.

During the next execution of the job SAP_FRN_LIC_DISTRIBUTION the maintenance certificate generated is retrieved from the SAP Support Portal, it is saved locally in SAP Focused Run, and it is delivered to the managed system.

In an ABAP system, in transaction SLICENSE -> Digitally Signed Licenses, the maintenance certificate (Maintenance_<DB>) is now displayed:
Transaction SPAM or SAINT no longer issue any warning message.

It may not be possible to install maintenance certificates automatically in transaction SLICENSE because the buffer is allocated to small. To solve the problem, you can set the following profile parameter to a higher value:
slic/buffer_entries_dig_sig
The benchmark is 15. You must then restart the system.

In a Java system, in the SAP NetWeaver Administrator -> Configuration -> Infrastructure -> Licenses, the maintenance certificate (Maintenance_<DB>) is now displayed:
Software Update Manager (SUM) no longer issue any warning message.

In detail: The maintenance certificate was uploaded manually in a system. However, transaction SPAM or SAINT still issue the following warning: "No valid maintenance certificate found for system XXX." In the system, the maintenance certificate (Maintenance_<DB>) is displayed in transaction SLICENSE -> Digitally Signed Licenses.

Check whether the hardware key of the maintenance certificate matches the hardware key of the system.

SAP must create the new system under an installation and license it. When the new license is implemented, the system automatically assigns and sets a new system number (18 digits). You must also change this in SAP Focused Run in the system landscape (transaction LMDB) for the relevant system. The automatic distribution process will now also request maintenance certificates for this system in future.

If there are problems, compare the system number of the system from SLICENSE/NetWeaver Administrator with the number from LMDB and the number for the system data for SAP. If the system numbers are different, generally the system number for the system data is correct. In this case, delete the incorrect system number from SLICENSE/NetWeaver Administrator in the system and install the correct one. Download from https://support.sap.com/keys-systems-installations/keys.html

Check if the system number is set for the systems in the system landscape (transaction LMDB, select the system, choose the "SAP Support Portal" tab). The system number cannot automatically be assigned in this case, as unique referencing is not possible. Maintenance certificates cannot be requested without a system number.

In detail: Due to previous errors during the license generation, there is old license data in the SAP Focused Run system. The errors are visible in the report RAGS_MK_DISPLAY_FILE. How can I update the data in the SAP Focused Run system?

The SAP Focused Run system does not execute a query in the SAP Support Portal each time the job SAP_FRN_LIC_DISTRIBUTION is run; instead, it keeps note of the time when the job was last run. This is not optimal in the case of this error. Delete the contents of the tables AGS_MAINT_KEYS and AGS_MK_LIC_EXP. The tables are filled again the next time you execute SAP_FRN_LIC_DISTRIBUTION.

Proceed as follows:

  • Call transaction SE14.
  • Enter the table name in the "Object name" field.
  • Choose "Edit".
  • Select the radio button "Delete data" to the right of the pushbutton "Activate and adjust database".
  •  Choose "Activate and adjust database".

Execute the job SAP_FRN_LIC_DISTRIBUTION again. The license data in the SAP Focused Run system should then correspond to the data in the SAP Support Portal.

In detail: In the SAP Support Portal, a new hardware key was generated for an existing system. The new maintenance certificate that is provided is not retrieved by SAP Focused Run. SAP Focused Run continues to contain only the maintenance certificates with the old hardware keys.

The maintenance certificates for a system stored in SAP Focused Run are still valid for more than 30 days. Therefore, when job SAP_FRN_LIC_DISTRIBUTION is executed, there is no request for new maintenance certificates that are provided in SAP Support Portal for this system. SAP Focused Run therefore does not obtain any information about the new hardware key that was created, and it cannot distribute the new maintenance certificate to the managed system.

By executing the report RAGS_MK_DEL_LOCAL_AND_REFRESH, you can enforce retrieval of all maintenance certificates provided in SAP Support Portal for a system. When you do this, you must fill the parameter SYSNO with the system number of the system.

During the following automatic distribution, the system is then supplied with the current maintenance certificates.

In detail: In the SAP Support Portal, a new hardware key was generated for an existing system. The new maintenance certificate that is provided is not retrieved by SAP Focused Run. SAP Focused Run continues to contain only the maintenance certificates with the old hardware keys.

The maintenance certificates for a system stored in SAP Focused Run are still valid for more than 30 days. Therefore, when job SAP_FRN_LIC_DISTRIBUTION is executed, there is no request for new maintenance certificates that are provided in SAP Support Portal for this system. SAP Focused Run therefore does not obtain any information about the new hardware key that was created, and it cannot distribute the new maintenance certificate to the managed system.

By executing the report RAGS_MK_DEL_LOCAL_AND_REFRESH, you can enforce retrieval of all maintenance certificates provided in SAP Support Portal for a system. When you do this, you must fill the parameter SYSNO with the system number of the system.

During the following automatic distribution, the system is then supplied with the current maintenance certificates.

SAP Support Portal
You have requested license data for an incorrect hardware key.

SAP Focused Run System
The system data is not maintained correctly in landscape maintenance (transaction LMDB), for example, there is an incorrect installation number or system number in the managed system. This occurs because of system copies. Consider that in landscape maintenance (transaction LMDB), the data under Software and on the software component versions tab page must be filled. For ABAP systems, in particular an entry for the software component SAP_BASIS is required.

Managed System
Data in the managed system is incorrect or incompletely maintained, for example, there is no system number or no installation number, or these numbers do not correspond to the data in the SAP Support Portal or in system landscape maintenance in SAP Focused Run.

The hardware key in transaction SLICENSE does not correspond to the hardware key requested in the SAP Support Portal.