Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 9057

SAP Cloud Appliance Library - Troubleshooting

$
0
0

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 ourSAP Cloud Appliance Library - FAQ where you find best practices for avoiding common pitfalls. In case you did not find what you were looking for, feel free to use the forum and ask your question there.

 

Common issues

 

Instance creation fails with:

AMAZON : User: abc:aws:iam::1234567890:user/username is not authorized to perform: iam:GetUser on resource: abc:aws:iam::1234567890:user/username

 

Please take a close look onto the IAM section in the AWS FAQ. Please follow the instruction there closely. If you already did it may happen that you need to wait until the changes take effect on AWS side (especially if your AWS account has just been created). Please try again 24 hours later to ensure that all your changes are deployed throughout the AWS backend

 

 

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

partner_not_reached.jpg

 

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 and check the log files. How to use ssh is explained in the SAP Cloud Appliance Library - FAQ.
  4. When you use the forum (for trial users) or the SAP ticket system (for users of the subscription), please make sure to explain all steps that lead to this issue (e.g. "this issue only occurs when I restart the instance on Mondays").

 

 

Why do I have to request a user in CAL ("You have requested a user of SAP Cloud Appliance Library...") - isn't CAL a self-service?

 

The easy access URL for SAP Cloud Appliance Library is http://cal.sap.com. Once logged onto CAL, the URL is changing and you are forwarded to your own CAL tenant.

 

This can be seen when taking a look at the browser URL before and after logon. I'm using my user as an example here:

 

1.) URL before logon

1.jpg

2.) Then logon

2.jpg

3.) URL after logon

3.jpg

 

As you can see, the tenant URL for my user is: https://cal.sap.com/console/tenant_GMPIMIXDCW7T. If another user now connects to CAL via http://cal.sap.com he/she will be forwarded to their own tenant with their own CAL tenant ID.

 

If they however connect to my CAL tenant URL they will receive a screen where they have to request access. If done so the CAL tenant owner (of the tenant the user requests access to) has to go to the USERS tab in CAL and authorize or reject the user.

4.jpg

Once this happened the approved user must be added to one of the cloud accounts. After that, the new user can use CAL – but must always ensure to use only this tenant URL and not http://cal.sap.com


Viewing all articles
Browse latest Browse all 9057

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>