Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I'm only getting this error with instances that were spun up with Esri AMIs. And I did find one post on the AWS forums (with no resolution) regarding this issue. Does anyone know what the troubleshooting/correction steps are for this issue? I have not started any troubleshooting steps yet.

  1. Restarted instance (No effect).
  2. Checked KMS . (No KMS Issues).
  3. Turned off firewall, modified C:\Program Files\Amazon\Ec2ConfigService\Settings\config.xml by setting Ec2WindowsActivate to Enabled.
  4. Restarted Ec2Config service.
  5. Success!
  6. Turned firewall back on. on but I still need to test the KMS...I probably still need to open up a port.
  7. Firewall is back on and no issues.

EDIT: AWS Forum Link: https://forums.aws.amazon.com/thread.jspa?threadID=119200

enter image description here

share|improve this question
add comment

2 Answers

Did you try this?

http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Windows-Server-Diagnostics.html

"The AWS Diagnostics for Microsoft Windows Server tool is available free of charge and can be downloaded and installed from https://s3.amazonaws.com/ec2-downloads-windows/AWSDiagnostics/AWSDiagnostics.zip."

"One use case is diagnosing problems with Key Management Service (KMS) activations. KMS activation can fail if you have changed the DNS server, added instances to a domain, or if the server time is out of sync. In this case, instead of trying to examine your configuration settings manually and debugging the issue, run the AWS Diagnostics for Microsoft Windows Server tool to give you all the information you need on possible issues."

share|improve this answer
    
No issues being reported--the KMS Servers are present according to the diagnostics tool. –  Jay Cummins Mar 18 '13 at 20:30
add comment
up vote 0 down vote accepted

This is what worked for me, but I have a feeling this issue will come back so this answer may change:

  1. Turned off firewall, modified C:\Program Files\Amazon\Ec2ConfigService\Settings\config.xml by setting Ec2WindowsActivate to Enabled.
  2. Restarted Ec2Config service.
  3. Turned firewall back on.
share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.