Custom Report is stuck in a Queued state in NFA 9.3.8 and later.
The \CA\NFA\Reporter\logs\ReportService*.log shows the following message.
Report Service - :
Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
at NetQoS.ReporterAnalyzer.Business.AgentPhysical.GetByRouterAddressInterfaceIndex(IPAddress routerAddress, UInt32 ifIndex, IFileLog iFileLog)
If you have NFA linked to DX Netops Portal you may also have Sync issues and you may see the Exception below in the \CA\NFA\Reporter\logs\ProductSyncWsLog*.log file
Pull: Checking for updated Flow Forensics Reports...
Pull - : Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at NetQoS.ReporterAnalyzer.Business.AgentPhysical.GetByRouterAddressInterfaceIndex(IPAddress routerAddress, UInt32 ifIndex, IFileLog iFileLog) at NetQoS.ReporterAnalyzer.Business.FlowForensicsReport.SetDomainId() at NetQoS.ReporterAnalyzer.Business.FlowForensicsReport.InitializeFromDataRow(DataRow row) at NetQoS.Business.DatabaseEntity.GetDatabaseEntityArrayFromDataTable[T](DataTable table) at NetQoS.ReporterAnalyzer.Business.FlowForensicsReport.GetUpdatedReports(UInt32 startTime, UInt32 endTime) at NetQoS.ReporterAnalyzer.Business.ProductSync.Sync.Pull_Item_FlowForensicsReports(PullDataHandlerState state, SyncTime syncTime, SyncUpdateState syncUpdateState) at NetQoS.ReporterAnalyzer.Business.ProductSync.Sync.PullRequest(SyncTime syncTime, SyncUpdateState syncUpdateState)
9.3.8 and later.
Fixed in NFA 10.0.2.
In 9.3.8 and later if you have a router which is linked to two Harvesters and if one or more if its interfaces are included in a Flow Forensics report it can cause this error.
This is fixed in 10.0.2, but in earlier versions you can run the script below on the NFA Console server to resolve this.
The script below will scan through your flow forensics report definitions for interfaces like this then as you if you want to delete the interface with the older timestamp which is likely no longer active.
Just unzip the file, right click and select "Run As Administrator" and follow the prompts.
https://ftp.broadcom.com/user/downloads/pub/netqos/supporttools/Scripts/FixFlowForensics.zip
Then restart the NetQos ReporterAnalyzer Report service and the NetQos ReporterAnalyzer Query service and try to run the Custom Reports again.
If on 9.3.3 or earlier see https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=32476