SAPcontrol connections are used to execute checks on Operating System level. In case of issues involving a specific SAPcontrol connection please check the following items:
SAP OSS Note 1563660 - sapcontrol, user authorization issues (SUM)
Make sure the SAP kernel of the satellite system has a recent patch level, especially for old kernels 6.40 or 7.00
Make sure that the ownership of the SAP kernel executable sapuxuserchk is correct.
For access to privileged OS Commands, the user configured must be added to the host profile of sapstartsrv (often in this location: /usr/sap/hostctrl/exe/host_profile) using SAP parameter service/admin_users.
On Windows (in Unix by default) the values for parameter service/admin_users in the host_profile are case sensitive and need to be defined exactly as the user running the service. For example service running as <SMD>ADM\SAPServiceDAA cannot be defined as: <smd>adm\SAPServiceDAA in the host_profile.
The upper and the lower case letters must match.
Add the SAP parameter parameter service/admin_users to the Start- or Instance profile of the SAP satellite system.
On Windows, the error “Start service runs with administrative privileges, OSExecute disabled” might occur: the SAPService<SID> user must not be part of the Administrators group. See also:
SAP OSS Note 2480903.
On Linux: in case the error "FAIL: HTTP error, HTTP/1.1 401 Unauthorized" occurs: remove old .sapstream* files from directory /tmp . See also:
SAP OSS Note 1565645 - SAP composite note: sapcontrol
Whenever you have made changes to the file: /usr/sap/hostctrl/exe/host_profile , you must restart sapcontrol with the command: saphostexec –restart in order to activate these changes.