2588975 - Communication between sapstartsrv processes denied due to ACL restrictions | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2588975 - Communication between sapstartsrv processes denied due to ACL restrictions

Symptom

It is noticed that SM21, sapcontrol and SAPMMC are not correctly reporting data in their correspondent functions. Some of the possible symptoms are shown below.

  1. The process sapstartsrv no longer respond to commands. The output is similar as below:

    FAIL: NIECONN_BROKEN (Connection reset by peer), NiRawRead failed in plugin_sapfrecv()

    It is confirmed that the relevant process is running and correctly bound to http port 5$$13 where $$ stands for the instance number. Still, no luck in getting it respond to any issued commands.

  2. In the sapstartsrv.log trace file from the target instance, the following entries are written:

    Using network access control list for http: <filesystem path to file>
    First soap_accept failure

  3. Another common symptom could be that SAPMMC cannot report the correct status for the processes of a given instance, even though it is confirmed that the application server in question is running fine.

  4. In transaction SM21, when trying to read the system log for one or a group of instances of an SAP system, the error "No access to instances <instance names> (SOAP:1023" is reported.

    print.png

Read more...

Environment

  • SAP NetWeaver
  • Startup services

Product

SAP NetWeaver all versions

Keywords

security, ACL, access control lists, network, connection refused , KBA , BC-CST-STS , Startup Service , BC-OP-NT , Windows , BC-CCM-MON , CCMS Monitoring & Alerting , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.