Hello The audit log will show the user and task that is submitted. It may have additional information about what is happening. The issue is likely with the service tag. The service tag is a field that is populated in the compliance report. If a null value is returned then it may be causing the compliance task to fail. If you are not being prompted to enter a service tag when the system starts up then you will likely need an onsite technician to set a service tag. Thanks
I have one server, a PowerEdge R530 with iDRAC8, that I am unable to associate a firmware baseline with.  During troubleshooting I created a test baseline targeting just this one device and the Check Compliance task fails with no data in the report.  Is there a log file somewhere that might give me a clue as to why things are failing for this one device?  In all other respects, OME is able to communicate with this device without issue including running a hardware inventory. I'm on OME 3.2, iDRAC is on the latest firmware (2.63.60.61), BIOS is not current (2.3.4).  Only apparent hardware "issue" is that the Service Tag is not being reported in either OME or iDRAC.
Check (firmware) compliance log file?