How To Fix CMS144 - Repository &1 not accessible by HTTP

SAP Error Message - Details

• Message type: E = Error

• Message class: CMS - KPro: Content Management Service

• Message number: 144

• Message text: Repository &1 not accessible by HTTP

What causes this issue?

The <DS:GLOS.0B31EBA16A3BD311A11A0060B0673A17>repository</> &V1& should
have been accessed using HTTP.

System Response

The operation was cancelled.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Check the Customizing for the repositories (see <DS:TRAN.OAC0>Define
repositories</>).
If you are dealing with a database repository, the
<DS:GLOS.F1143DE23961D411AE7500A0C9EAD00F>ICM</> must be running on at
least one application server, so that the repository can accessed via
HTTP. Also, logon data for the service
<ls>/DEFAULT_HOST/SAP/BC/CONTENTSERVER</> (see <DS:TRAN.SICF>Define
services</>) must be available for HTTP access in the service tree.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CMS144 - Repository &1 not accessible by HTTP ?

  The SAP error message CMS144 indicates that a specific repository (denoted by &1) is not accessible via HTTP. This error typically arises in the context of SAP BusinessObjects or SAP NetWeaver systems when there are issues with the configuration or connectivity of the repository.
  Causes:
  
  Network Issues: There may be network connectivity problems preventing access to the repository.
  Incorrect URL: The HTTP URL configured for the repository may be incorrect or malformed.
  Repository Configuration: The repository may not be properly configured to allow HTTP access.
  Service Down: The service that hosts the repository may be down or not running.
  Firewall Restrictions: Firewalls or security settings may be blocking HTTP access to the repository.
  Authentication Issues: There may be issues with user authentication or permissions that prevent access.
  
  Solutions:
  
  Check Network Connectivity: Ensure that the server hosting the repository is reachable from the client machine. You can use tools like ping or tracert to diagnose network issues.
  Verify URL: Check the