Search Engine: Elastic

Article ID: 119745, created on Jan 22, 2014, last review on May 11, 2014

  • Applies to:
  • Operations Automation


This article contains general troubleshooting steps for investigating problems with Windows Azure Pack (WAP).

  1. Check POA task manager for the failed task. WAP APS related tasks are named by "Executing APS provisioning workflow 1bbc6bd6-bcfe-436b-8a41-553b19bdac7e". Uid in the task name different. Also tasks can be found by the POA subscription id.

  2. Check /var/log/poa.debug.log to get more details about the failed task.

  3. Check that WAP service is running. WAP service is running on POA Management Node.

    \# service WAP status
  4. Check that WAP is accessible from POA Management Node

  5. Check WAP log /usr/local/share/WAP/logs/wap.log for the errors. WAP application uses RESTful API for sending request to WAP portal. All requests and responses can be found in log file.

  6. Check Event Viewer on WAP infrastructure:

    Application And Services Logs > Microsoft > WindowsAzurePack

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF