# Troubleshoot AWS Launch Wizard for SAP Troubleshoot SAP Each application in your account in the same AWS Region can be uniquely identified by the application name specified at the time of a deployment. The application name can be used to view the details related to the application launch. **Topics** + [ ## Launch Wizard provisioning events ](#launch-wizard-sap-provisioning) + [ ## CloudWatch Logs ](#launch-wizard-sap-logs) + [ ## CloudFormation stack ](#launch-wizard-sap-cloudformation) + [ ## Pre- and post-deployment configuration scripts ](#launch-wizard-sap-troubleshooting-scripts) + [ ## Application launch quotas ](#launch-wizard-sap-quotas) + [ ## Instance level logs ](#launch-wizard-sap-instance-level-logs) + [ ## SAP application software deployment logs ](#launch-wizard-sap-application-logs) + [ ## Errors ](#launch-wizard-sap-errors) + [ ## AWS Systems Manager for SAP ](#launch-wizard-sap-troubleshoot-ssm) + [ ## Support ](#launch-wizard-sap-support) ## Launch Wizard provisioning events Launch Wizard captures events from SSM Automation and CloudFormation to track the status of an ongoing application deployment. If an application deployment fails, you can view the deployment events for this application by selecting **Deployments** from the navigation pane. A failed event shows a status of **Failed** along with a failure message. ## CloudWatch Logs Launch Wizard streams provisioning logs from all of the AWS log sources, such as CloudFormation, SSM, and CloudWatch Logs. You can access CloudWatch logs for your SAP deployment with the following steps. 1. Sign in to console.aws.amazon.com and go to AWS Launch Wizard. 1. Under **Deployments** on the left panel, go to **SAP** and you can see the list of your SAP deployments. 1. Select the failed deployment for which you want to verify the logs. 1. Choose **Actions** > **View/Manage resources** > **View CloudWatch application logs**. 1. You can now view the detailed logs and log streams that provide additional information on the SAP application type that failed during deployment. ## CloudFormation stack Launch Wizard uses CloudFormation to provision the infrastructure resources of an application. Launch Wizard launches various stacks in your account for validation and application resource creation. You can verify the stacks via AWS console or AWS CLI. ------ #### [ Console ] 1. Sign in to console.aws.amazon.com and go to AWS Launch Wizard. 1. Under **Deployments** on the left panel, go to **SAP** and you can see the list of your SAP deployments. 1. Select the failed deployment for which you want to verify the stacks. 1. Choose **Actions** > **View/Manage resources** > **View CloudFormation template **. 1. You can now view all the stacks and their current status. To see more details on any stack, select a **Stack name**. 1. You are now on the **Stack details** page of your selected stack. Choose **Events** from the top menu bar to view the cause of the failure. ------ #### [ CLI ] CloudFormation stacks can be found in your account using the CloudFormation [describe-stacks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-describing-stacks.html) API. The following are the relevant filters for the [describe-stacks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-describing-stacks.html) API. + **Application resources** `LaunchWizard-APPLICATION_NAME`. You can view the status of these CloudFormation stacks. If any of them fail, you can view the cause of the failure. ------ ## Pre- and post-deployment configuration scripts **Can't find the output of my scripts** + **Cause:** Customizations are key scripts that you want to run on the EC2 instances and the logs from script deployments are not included with the provisioning logs. + **Solution:** The logs for scripts that run on EC2 instances are included in the CloudWatch log group that Launch Wizard creates in your account for the workload. The CloudWatch log group can be identified as `LaunchWizard-APPLICATION_NAME` . You can find the following logs in this log group. + `lw-customization//preDeploymentConfiguration` — For pre-deployment configuration scripts that run on the specified EC2 instance. + `lw-customization//postDeploymentConfiguration` — For post-deployment configuration scripts that run on the specified EC2 instance. ## Application launch quotas Launch Wizard allows for a maximum of 25 active applications for any given application type. Up to three applications can be `in progress` at a time. If you want to increase this limit, contact [Support](https://aws.amazon.com/contact-us). ## Instance level logs To check the progress of a deployment, you can log in to an instance as soon its instance state is listed as **running**. When the deployment is finished, the log files are moved to `/tmp`. By default, your provisioned Amazon EC2 instances are retained when a deployment fails. If you created your Launch Wizard deployment with these default settings, you can navigate to the following paths for further evaluation. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap-troubleshooting.html) ## SAP application software deployment logs Depending on which SAP components are deployed on an instance, Launch Wizard creates a folder in `/tmp` to log all of the SAP software application deployment logs. If a database component is deployed on an instance, the folder name in the file will be `NW_ABAP_DB`. If an application server is deployed, the folder name will be `NW_ABAP_APP`. For single node deployments, there will be multiple folders, such as `NW_ABAP_DB` and `NW_ABAP_CI`, which represent the different components deployed on the instance. ## Errors **Your requested instance type is not supported in your requested Availability Zone** + **Cause:** This failure might occur during the launch of your instance, or during the validation of the instances that Launch Wizard launches in your selected subnets. + **Solution:** For this scenario, you must choose a different Availability Zone and retry the deployment from the initial page of the Launch Wizard console. **Infrastructure template already exists** + **Cause:** This failure occurs when you choose to create a new infrastructure configuration and then navigate back to the first step in the wizard to review or adjust any settings. Launch Wizard has already registered the configuration template, so choosing **Next** results in the error "Template name already exists. Select a new template name." + **Solution:** Perform one of the following actions to continue with your deployment. + Change the name of the configuration template and continue. + Choose another template and continue. + Delete the template causing the error by navigating to the **Saved Infrastructure Setting** tab under **Deployments – SAP**, and then continue with your configuration using the same configuration name. ## AWS Systems Manager for SAP **An Internal Error Occurred** + **Cause:** For users using AWS Systems Manager for the first time, the CloudFormation resource (`AWS::SystemsManagerSAP::Application`) can fail with a message `An Internal Error Occurred` due to issues during the SLR (service-linked role) `AWSSSMForSAPServiceLinkedRolePolicy` creation. + **Solution:** 1. Use the [IAM console](https://console.aws.amazon.com/iam/home) to ensure that `AWSSSMForSAPServiceLinkedRolePolicy` is in your account. 1. Retry the Launch Wizard deployment to complete the registration successfully. 1. If errors persist, contact [Support](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-case) For more information, see [Troubleshooting AWS Systems Manager for SAP](https://docs.aws.amazon.com/ssm-sap/latest/userguide/troubleshooting.html). ## Support If your deployment is failing after following the troubleshooting steps listed here, we recommend you to create a support case with the following information. ``` [Error description]: [Deployment information]: Provide information about the failed deployment. Account number: Deployment name: Deployment type: SAP HANA version: SAP application: OS type: OS version: Amazon EC2 instance family: Amazon EC2 instance type: If used proxy: AMI type: Instances retained: FailedStackID (optional): [Required logs] Provide the following logs. Based on the scenario and state of deployment, some logs may not be available. /root/install/scripts/log/ /tmp/install.log /tmp/inputs.json /var/log/cloud-init.log /var/log/hdblcm.log (If SAP HANA install is selected) /tmp/NW directory (If SAP HANA install is selected) If you haven't retained your Amazon EC2 instance, provide the logs extracted from CloudWatch logs. [Troubleshooting] Provide the details of the troubleshooting steps that you carried out and the results from them. ``` For more information, see [Creating a support case](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-case).