MID Server agent log shows Error: ClassUtil - class not foundIssue You might notice from the MID Server's agent log the following error message: 2024-07-25T08:43:26.542+0100 ERROR (ECCQueueMonitor.1) [ClassUtil:354] ClassUtil - class not found: or for older versions: 10/28/21 09:59:21 (546) ECCQueueMonitor.1 SEVERE *** ERROR *** ClassUtil - class not found: a specific class name may also be given. e.g. class not found: PowerShellCauseThese "class not found" errors are true, and means there is no Java class with the name within the MID Server application. The class will be the name of the probe given in the ECC Queue record's Topic field. Either the class name/Topic field will be empty, or have an invalid value. The MID Server will not be able to process the ECC Queue output record, because it doesn't contain that Probe code. The ECC Queue output record will be set to Error state.ResolutionUnless code had been deprecated in the MID Server, and something on the instance side is still trying to use it, it is likely that a custom coding/typing error is the cause. Whatever code is inserting the ecc_queue output record needs correcting, so that Topic has a value, and it is a valid value. Other fields in the ecc_queue record may give clues as to what feature/integration the ecc_queue record came from. Finding the transaction that inserted the ecc_queue record may help find the responsible code. Check the case is correct. e.g. There is a "Powershell" class, but not a "PowerShell" class. Search KB articles for the class/topic name. It is possible there is a problem with out-of-box code. This may be true if the error started happening straight after an upgrade. This article lists some ECC Topic values that are known to be good, and definitely there as Java Classes in the MID Server application:KB0727132 How to link an ECC Queue record back to a specific Feature or Job