6956

The Portal un-install process on a Windows platform may not remove all the files in the Storage Viewer package.

13723

The Storage Viewer for File Analytics File List Export feature has an issue where the number of files exported does not match the number of files shown in the File Categories report. This occurs only if the File Categories have been modified and the user running the report belongs to more than one Domain.

17287

Occasionally, tabular reports will display mis-aligned column headings. To avoid this issue, wait for the report to finish rendering before clicking on another tab.

18953

A report template exported from an earlier Storage Viewer version can be imported into a later Portal software version, but the template may experience some loss of formatting when imported.

21948

When running checkinstall for VMware collection, error messages may not accurately reflect the cause of the error. Inspect the collector logs for the actual cause of the error.

22582

For SAN Fabric collection, in certain cases, the database may contain aliases that actually do not exist, but they appear to be associated with a zone.

23604

For very large Datastores, VMware Datastore and Performance collection may encounter an out-of-memory condition, causing incomplete data collection. Choose one of the following workarounds:

23620

Due to browser caching, there may be times when the data in a drilldown report is out of synch with the data reflected in its parent report. To ensure synchronized data, refresh the parent report and click the drilldown link as soon as the parent report fully renders.

23943

VMware performance collection may fail with an error: specified parameter was not correct. querySpec.size. A workaround can be found in this VMware KB article:

24159

Some versions of vCenter (e.g., 5.5.0) have a hard-coded limit of 25,000 files and directories that can be listed for a directory in a Datastore. This limit may be different for different versions of vCenter. If any directory in a Datastore collected via vCenter has >25,000 files/subdirectories, the contents of that directory (and subdirectories) will not be collected and will be classified as Unknown in the Datastore Usage Breakdown report. Collecting directly from an ESX host does not appear to suffer from this issue, but that may also be version-dependent.

24210

In the Inventory for Backup Servers, in the Backup Master Server Overview, the mouse-over tooltips in the Job Status SLA report display job counts that do not match the underlying data shown in the Job Summary report.

24290

In the Inventory for VM Servers, the VM Cluster Summary report does not list any data. To view this report with data, search the reports and generate the report from the report template in the search results.

24349

EMC Isilon SMB shares in access zones are not being collected and reported in the EMC Isilon SMB Share Summary report.

29091

Reduces the occurrence frequency of an issue with a Microsoft Azure billing data collector probe failure. This error is raised by Microsoft Azure when the data being requested is not ready to be consumed by the Data Collector, as it is still being processed by Microsoft Azure.

Reference: "Response Code" section in https://msdn.microsoft.com/en-us/library/azure/mt219001#Response

When a failure occurs, the data will be collected during the next scheduled collection time.