Article ID: 119765, created on Jan 23, 2014, last review on May 11, 2014

  • Applies to:
  • Operations Automation

Symptoms

Resource usage is not collected from WAP.

Empty response from WAP can be found in log file: /usr/local/share/WAP/logs/wap.log

2013-12-19 21:37:34,026 INFO  LoggingFilter [Grizzly(5)] - 283 * [WAP->AZURE] Client out-bound request
283 > GET https://WAP_IP:30022/usage?startId=45819&batchSize=10000
283 > Authorization: <hidden>
283 > X-ReqId: 27793
283 > Accept: application/json

2013-12-19 21:37:34,035 INFO  LoggingFilter [Grizzly(5)] - 283 * [WAP<-AZURE] Client in-bound response
283 < 200
283 < X-AspNet-Version: 4.0.30319
283 < Date: Thu, 19 Dec 2013 17:40:35 GMT
283 < Content-Length: 2
283 < Expires: -1
283 < Content-Type: application/json; charset=utf-8
283 < X-Powered-By: ASP.NET
283 < Server: Microsoft-IIS/8.5
283 < Pragma: no-cache
283 < Cache-Control: no-cache
283 <
 []

Cause

There is an issue on WAP side.

Resolution

Check Event View on WAP Infrastructure for the errors: Application And Services Logs > Microsoft > WindowsAzurePack

Contact Microsoft in case of unclear error.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF