Skip to end of metadata
Go to start of metadata

This page provides additional assistance in case you are experiencing any kind of trouble with SAP Cloud Appliance Library. Please make sure that you also visit our SAP Cloud Appliance Library - FAQ where you find best practices for avoiding common pitfalls. If you are using the SAP Cloud Appliance Library to deploy free solutions, you can check the SAP community and search for the tag "SAP Cloud Appliance Library”. Note that you may also ask a question using "SAP Cloud Appliance Library” as a primary tag.

Common Issues

1. You cannot connect to the SAP system when using the Connect feature in the CAL UI.

                                                                   

There are many different root causes for this issue. In a nutshell it says that your client machine (the one from where you are accessing the CAL webpage) is not able to communicate with the SAP system that you have provisioned. Reasons are manifold:

  1. Time: when using a solution in CAL for the first time the SAP system that is started is not accessible instantly. Please make sure that you wait until the traffic light on the left side of the instance name in the CAL UI has turned green.
  2. Network: does your client machine has direct access to the SAP system (are they both in the same network)? If your client machine is behind a firewall in a corporate network, you would need to open the ports in your firewall to the system in order to connect to it via SAPGUI or RDP (if available). The ports which are open on the virtual machine in the cloud are listed in the instance details (Click on instance name and then on virtual machine).
  3. SAP System down: Another reason for such an error is that the SAP system inside the appliance did not start properly (the green light in CAL just says that the virtual machine is up and running - not the SAP system).

The best way to investigate is to ssh into the virtual machine. How to use ssh is explained in the SAP Cloud Appliance Library - FAQ. If you can't establish the ssh connection then you are in case 2 - Network. If you can't solve the problem by yourself, the best option would be to involve your IT department.

 

Once you are successfully logged in you would see one of the messages below:

SAP Appliance configuration currently in process. Please do not modify anything. - this indicates the first reason - Time. Close the ssh connection and try to connect again in 10-15 minutes.

The Appliance Agent detected an error and terminated.  - the reason is SAP System downas the initial provisioning failed unexpectedly. It is quite unlikely to fix the system in this situation so terminate the solution instance and create a new one. If the problem persists please ask a question using "SAP Cloud Appliance Library” as a primary tag to report the solution name, the cloud provider, the region, the VM size and the number of instances you created. Report an incident to BC-VCM-VAP if you have ordered the SAP CAL subscription package.

If you see neither of the two messages, it means that the system was initially OK but it went down at a later point of time. To check the current system status execute the commands below:

su - <SID>adm

sapcontrol -nr <instance number> -function GetProcessList

You can find the SID and the instance number in the solution Getting Started Guide. For example:

su - s4hadm

sapcontrol -nr 00 -function GetProcessList

and

su - hdbadm

sapcontrol -nr 02 -function GetProcessList

 

If you are behind a proxy / firewall you may check the availability of the access ports, connecting to the OS level of the instance via SSH (port 22) and executing the following commands:

lsof -i :<port>
netstat -tupan | grep <port>

If you are using the SAP CAL to deploy free solutions, try to find the root cause in the logs or create a new solution instance. If you have ordered the SAP CAL subscription package please first check whether you have installed the required license keys. If yes, report an incident to the support component of the corresponding SAP product as you would do if the system was installed on premise. If no, see the Licenses section in the solution Getting Started Guided and How to request and install product license keys for SAP solutions.

2. Instance creation fails with the following message:

Operation Start failed on step Allocate elastic IPs with message: Error creating static IPs; AMAZON: The maximum number of addresses has been reached.

Your accounts doesn't have enough free Elastic IP addresses. You need to check your Elastic IP limits within the AWS console and how to release them if they are used. Limits are regions based, so make sure that you check the limits for the region in which you chose to deploy the CAL solution.


3. Wrong master password

The SAP Cloud Appliance Library does not save your master password during creation of the solution instance. If you can not remember the password, you could terminate your instance and create a new one.

How to test HANA Connection strings using hdbsql command line interface

- for multitenant database containers (MDC)

hdbsql -i <sys nr> -n <virtualhost>:3<sysnr>41 -d <dbtenant> -u SYSTEM -p <password> 

 - for single container 

hdbsql -i <sys nr> -u SYSTEM -p <password>


Example:

If you are sure for the master password of your SAP HANA instance, connect to the instance via PuTTY client (SSH client on the port 22) using the instance private key (.PEM file) and verify it with the following commands:

 Get instance number of HDB


/usr/sap/hostctrl/exe/saphostctrl -function ListInstances

 Inst Info : ERP - 01 - vhcalerpcs - 741, patch 50, changelist 1521295

 Inst Info : ERP - 00 - vhcalerpci - 741, patch 50, changelist 1521295

 Inst Info : HDB - 02 - vhcalhdbdb - 740, patch 36, changelist 1444691

 su - -c "/usr/sap/HDB/SYS/exe/hdb/hdbsql -i 02 -u SYSTEM -p <Wrong Master Password> -o /tmp/SYSTEM 'select * from SYS.USERS'" hdbadm

* 10: invalid username or password:  SQLSTATE: 28000

su - -c "/usr/sap/HDB/SYS/exe/hdb/hdbsql -i 02 -u SYSTEM -p <Your Master Password> -o /tmp/SYSTEM 'select * from SYS.USERS'" hdbadm

9 rows selected (overall time 962 usec; server time 320 usec)


For more information how to connect to your running instance via SSH or PuTTY, see the following questions from this FAQ page:

  • How to connect to a running instance via the secure shell protocol (SSH)?

 

 

  • No labels