While collecting from Exchange, eDiscovery shows Hits being collected. However, when the collection completes the Hit count returns to 0 and attempts to process the collection fail immediately.
The WorkManager log reports the following error:
ERROR eDiscovery.BusinessComponents.ReportGeneration.Processor.CollectionItemProcessor [(null)] - ProcessCollectionItem()
System.NullReferenceException: Object reference not set to an instance of an object.
at eDiscovery.BusinessComponents.ReportGeneration.Processor.CollectionItemProcessor.ProcessCollectionItem(Guid resultId, String itemXmlPath)
The ReportGenerationLog in the collection's responsive folder reports the following error:
Object reference not set to an instance of an object.
Manually add the collected AD1 to the project as an Evidence job.
One or more collected emails contained an illegal XML character in its Subject line (you can run the CollectionResult XML through an XML Validator if you want to find the offending character, which will usually start with
&#x). This results in an error while generating the collect report, which then returns the Hit count to 0, which in turn causes attempts to process the collection to fail (because the reported size doesn't match the actual collected size).
The actual collected AD1 is left unharmed and can still be manually processed as an Evidence job.