Previous Topic: Collect from Network DrivesNext Topic: Many Errors in the Application Event Log


Unprocessed Files

Symptom:

The files in the collection folder are not being processed. They are not being moved to the output folder as expected.

Solution:

Check that the asset collector is running. This can be done by issuing a caf status, or caf status assetcollector command.

If the Asset Collector is not running, start it with caf start assetcollector.

Check that the collection folder the asset collector is monitoring is the folder where you are placing your file. From the DSM explorer you can request a configuration report from a computer to see the configuration policy in use.

It could be that the services that the Asset Collector communicates with to register and upload inventory is not running. The asset collector relies on the Common Server plugin for registration, and the asset management server for inventory upload. You should see messages regarding failure to register or upload in your event log, if this is the case. Once the services are restarted, the Asset Collector should upload the inventory on it's next attempt, this could be up to 5 minutes after the dependent services are started.

You may have configured the Asset Collector to report inventory to an invalid scalability server. Check this in the active configuration.