Determining the cause of data files being rejected by the Information Warehouse
search cancel

Determining the cause of data files being rejected by the Information Warehouse

book

Article ID: 339496

calendar_today

Updated On:

Products

VMware

Issue/Introduction

The files shown on the Dashboard are marked rejected in Dashboards > Collection Dashboard > Performance Files, or Inventory Files.


Environment

VMware Capacity Planner 2.6.x
VMware Capacity Planner 2.5.x

Resolution

The files are marked as Rejected if the file is truncated, the file is corrupted, or if a network issue is causing the corruption.
If a file is large and the network upload speed is relatively slow, it may not complete within the 300 second timeout default. This causes the task to be rejected mid-file by the Collector and the resulting file at the Dashboard is truncated.
 
To prevent files being marked as rejected:
  1. Verify that the files are not truncated. Download any available file that was marked rejected and open it in a text editor. The last line of the file must only contain a 32 character checksum. If it is missing, the file is truncated and is rejected.
  2. If the file is truncated, adjust the Data Synchronization job timeout. For more information, see Adjusting the Data Synchronization task timeout values (1005507) .
  3. Verify the files are not corrupted. From the text editor check the first line of the file. It must contain the System ID, Database ID, and version number. The rest of the file is human readable as clear text from start to end.
  4. If the rejected file is an inventory file, ensure that the setting to Export System Information is enabled. From the Data Manager click Admin > Options > Modules > Inventory > Export. Deselect System Information.

    Note: Selecting this option excludes this item from export.

     
  5. Migrate the Collector to another host or to another part of the network.
  6. If you are still unable to successfully send files without corruption, see Uploading Collected Data when Collector cannot Access the Information Warehouse (Dashboard) Directly (1896).

For additional information related Dashboard troubleshooting, see Troubleshooting when no data or no new data appears on the Dashboard (1005942).