Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 > Collecting, transforming, and publishing > Microsoft Windows Azure Pack > Troubleshooting Windows Azure Pack collection

Troubleshooting Windows Azure Pack collection

Use the following sections to help resolve issues with Windows Azure Pack data collection.

VM usage data not collected

If Cloud Cruiser jobs are completing without errors but are failing to collect data for virtual machine usage, it’s possible that the data is not available in Windows Azure Pack to collect. There are several components that provide data on VM usage to Windows Azure Pack, and if they are not configured correctly this data is not placed in Windows Azure Pack’s usage database where it can be collected by Cloud Cruiser.

The following series of Microsoft blog articles explains the components involved and how to configure them:

  1. IaaS Usage and Service Reporting using System Center 2012 R2 and Windows Azure Pack
  2. Configuring VMM and OM for IaaS usage and metering
  3. Configuring SPF and Windows Azure Pack for IaaS usage and metering

The series contains four articles, but only the three listed here are relevant to making data available to Cloud Cruiser.

Additionally, see the following Microsoft blog articles for troubleshooting Windows Azure Pack and the collection of usage data:

  1. Troubleshooting Windows Azure Pack & Usage (Part 1)
  2. Troubleshooting Windows Azure Pack & Usage (Part 2) 

If, after you install an update for Microsoft System Center Virtual Machine Manager or Microsoft System Center Operations Manager, no usage information or only partial usage information is available through WAP Service Reporting, your "Run As" account settings for Virtual Machine Manager and Operations Manager might be unsynchronized. See the following Microsoft Support article for more information and a solution:​.

Warnings in data load logs

When monitoring your jobs, you might occasionally see one or both of the warning messages Plan not found and Subscription not found. To troubleshoot this problem:

  1. Perform the procedure in Recovering after a period with no data collection.
    If you are able to complete this procedure without errors or warnings, then the problem was caused by a job not running successfully on a previous day, and you have fixed the problem. Otherwise, continue to the next step.
  2. Contact Cloud Cruiser Support.
    These warnings can also be caused by plans or subscriptions that are not available in Windows Azure Pack for Cloud Cruiser to collect. We can help you determine where the problem is originating within your Windows Azure Pack ecosystem.

Recovering after a period with no data collection

Because the collection process maintains a list of active plans and subscriptions by adding and removing items based on each day’s collected events, collection of Windows Azure Pack must run continuously to be successful. When this job doesn’t run successfully for a day or more, subscriptions and plans created during that period are never added to the list. Simply resuming scheduled execution produces warnings because some usage can’t be associated with a subscription or plan, and charges for this usage are not loaded.

Before you begin

Fix any outage or error that was causing collection to fail.

To recover after a gap in collection

  1. Go to Data > Processing > Published Loads.
  2. Find the most recent load group for your Windows Azure Pack workbook and note its Accounting Date.
    This is the last date for which your collection ran successfully.
  3. Go to Data > Processing> Scheduling.
  4. Select your Windows Azure Pack schedule and click Run.
  5. Set the Start Date to the day after the date you noted, and set the End Date to yesterday's date.
  6. Click OK.
    The collect job collects all usage and events since the last time it successfully ran, storing them in files based on the date they ended.

Charges for the gap period are now viewable, and you can resume a nightly schedule of collection.

Recovering after collecting event data out of sequence

Cloud Cruiser stores information about the most recently collected Windows Azure Pack event in a feedState file located in your Cloud Cruiser <workingDirectory>\processing\<workbookName> directory. This file serves as a pointer to a location in the Windows Azure Pack database. If the feedState file contains a later event than the event you want to collect, Cloud Cruiser might not collect data for the time span specified in your collection. This might happen, for example, if you collect current data and then try to collect data from an earlier date.

If your collected event data is out of sequence, open the Microsoft Windows Azure Pack Properties area of the Edit Collection dialog box, set the Reset Feed State field to Yes, and then run collection.

Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP