/Collapse
- 1. Introduction
- 2. Frequently Asked Questions
- 2.1. When I sign in to the portal, I don't see any project spaces. What should I do?
- 2.2. I'm an administrator. What is the best way to provision resources to multiple users?
- 2.3. Can I use a virtual desktop when someone else is using it?
- 2.4. Why does my virtual desktop get disconnected after a period of inactivity?
- 2.5. Can I map selected local drives on my computer to a virtual desktop?
- 2.6. If my workflow includes geometry, do I need to use graphics-accelerated instances?
- 2.7. Can I change the name of a resource after it has been created?
- 2.8. What are the recommendations for running performance benchmarks?
- 2.9. How do I find out the specifications of the virtual machine size defined for an autoscaling cluster queue?
- 2.10. How do I know the maximum number of cores that I can specify for an autoscaling cluster job?
- 2.11. How do I specify a queue when submitting jobs to Ansys HPC Platform Services (HPS)?
- 2.12. Why isn't a VM size for which I have quota listed in resource creation wizards?
- 3. Resolving Common Issues
- 3.1. Can't access the Ansys Access on Microsoft Azure portal
- 3.2. Can't sign in to Ansys Access on Microsoft Azure
- 3.3. Insufficient capacity when creating resources
- 3.4. Resource creation is taking a long time
- 3.5. Resource creation results in a 'Failed State' error
- 3.6. Newly created resource stuck 'Waiting for services'
- 3.7. Resource has been stuck installing applications for a long time
- 3.8. Error when creating a resource: 'Unable to list VM sizes'
- 4. Troubleshooting Autoscaling Cluster Workflows
- 4.1. Debugging Application Installations on Autoscaling Clusters
- 4.2. Troubleshooting Provisioning Issues for Autoscaling Clusters
- 4.3. Troubleshooting Slurm Autoscaling Cluster Workflows (Non-HPS)
- 4.4. Troubleshooting Autoscaling Cluster Workflows that use Ansys HPC Platform Services (HPS)
- 4.5. Restoring a Connection to a Slurm Autoscaling Cluster
- 5. Known Issues and Limitations