Page tree
Skip to end of metadata
Go to start of metadata


When starting or stopping an instance or instance agent an exception occurs.


The host agent uses the sapcontrol program to control an SAP instance. The sapcontrol program can use a trusted connect feature to setup a local connection to an instance agent without providing a user and password. On UNIX, the trusted connect feature is implemented through a UNIX Domain Socket (UDS).

1. Unintentionally, the instance agent removes this UDS when stopping its instance.

2. The UDS file is not owned by the instances <sid>adm user and/or the <sid>adm user has no write permissions to this file.

When starting or stopping an instance or when the instance agent fails, the following messages appear in the Log Details of the ACC Operation Log:

Message Code











FAIL: HTTP error, HTTP/1.1 401 Unauthorized



Sapcontrol terminated with error



Error occured when trying to stop instance. (Operation Exception: 'Command Execution failed.' Fault Code: '127')


  1. Upgrade the instance agent. For more information: refer SAP note 877795.
  2. Shutdown the instance agent, delete the UDS file and restart the instance agent that re-creates the UDS file with the correct ownership and permissions.
    Proceed as follows:
  1. Log on with the <sid>adm user
  2. Shutdown the instance agent by executing the following command:
    sapcontrol -nr <NR> -function StopService -user <sid>adm<password>
  3. Change to the root user and remove the UDS file. The file is located in the /tmp directory and the file name convention is ".sapstream5<NR>13"
  4. Change back to the <sid>adm user and start the instance agent for example, with the following command:
    sapcontrol -nr <NR> -function StartService <SID>
  • No labels

1 Comment

  1. Former Member

    to avoid the errror:
     RunSAPcontrol: /usr/sap/hostctrl/exe/sapcontrol rc=1                   
     SAPcontrol_Start: Start Failed: FAIL: HTTP error, HTTP/1.1 401         
     StartInstance: SAPcontrol_Start() rc = 1 (ScStatus_FailStart), check   
       instance manually.        
    Autorize the directory  /tmmp to group R3GROUP
    For example:

    chgrp -R 123 tmp