Menu
Microsoft Servers on AWS
Quick Start Reference Deployment Guide

Troubleshooting

When you deploy the Quick Start, if you encounter a CREATE_FAILED error instead of the CREATE_COMPLETE status code, we recommend that you relaunch the template with Rollback on failure set to No. (This setting is under Advanced in the AWS CloudFormation console, Options page.) With this setting, the stack’s state will be retained and the instance will be left running, so you can troubleshoot the issue.

Important

When you set Rollback on failure to No, you'll continue to incur AWS charges for this stack. Please make sure to delete the stack when you've finished troubleshooting.

The following table lists specific CREATE_FAILED error messages you might encounter.

Error message Possible cause What to do
API: ec2: RunInstances Not authorized for images: ami-ID The template is referencing an AMI that has expired. We refresh AMIs on a regular basis, but our updates sometimes lag behind AWS AMI changes. If you get this error message, notify us, and we’ll update the template with the new AMI ID.

If you’d like to fix the template yourself, you can download it and update the Mappings section with the latest AMI ID for your region.

We currently do not have sufficient instance-type capacity in the AZ you requested One of the instance types is currently not available. Switch to an instance type that supports higher capacity, or complete the request form in the AWS Support Center to increase the Amazon EC2 limit for the instance type or region. Limit increases are tied to the region they were requested for.
Instance ID did not stabilize You have exceeded your IOPS for the region. Request a limit increase by completing the request form in the AWS Support Center.
System Administrator password must contain at least 8 characters The master password contains $ or other special characters. Check the password parameters before you re-launch the Quick Start.

The passwords must be at least 8 characters, consisting of uppercase and lowercase letters and numbers. Follow the guidelines for complex passwords and avoid using special characters such as @ or $.

If failure is signaled or a wait condition or resource signal times out, you should remote into the affected machine and launch Event Viewer. Under Custom Views, Administrative Events or under Windows Logs, Application, look for errors of source AWSQuickStart. These will indicate the failing script, line number, and exception that was reported.

For additional information, see Troubleshooting AWS CloudFormation on the AWS website.