Licensing Issues During or After Deployment - Teradata Software for Azure

Teradata Vantage™ on Azure (DIY) Installation and Administration Guide

Product
Teradata Vantage on Azure
Release Number
5.01
Published
July 2018
Language
English (United States)
Last Update
2018-07-18
dita:mapPath
kmk1523992471627.ditamap
dita:ditavalPath
TeradataAzure_PubCloud_5.01_5.01.01.ditaval
dita:id
B035-2810
lifecycle
previous
Product Category
Cloud
If you receive any licensing errors during or after deployment, access the Summary page for more information. Following are examples of errors and possible remedies:
Errors Remedies
Cannot access the EMS Server URL Make sure port 443 is open to https://slem.teradata.com so Teradata can verify BYOL entitlement, and verify your system can access the port. See Network Security Groups for Teradata Database.
Couldn’t login to the ems server using the provided Entitlement ID. Verify the entitlement ID you entered when you deployed matches the email confirmation.
License doesn't have requested tier or term Verify the term you selected when you deployed matches the email confirmation. See Bring Your Own License.

Verify the Teradata Database license tier you chose when you deployed is correct.

Not enough TCORES available If additional TCores are needed, contact your Teradata Account Team for assistance.

During deployment, activated Teradata Database licenses are automatically revoked if a failure occurs. If activated licenses did not get revoked, you can revoke them manually. After revoking the licenses, you can delete the VM.