[EM\Connector] Connector instance fails with error "Credentials not found, id: d13bf48c1b38e0507a5a55b61a4bcb5efailed to run 3PC java.lang.ClassCastException: org.mozilla.javascript"Issue The Event Connector Instance started failing with error "Credentials not found, id: d13bf48c1b38e0507a5a55b61a4bcb5efailed to run 3PC java.lang.ClassCastException". EVENTS-------------------------------------------------------------Credentials not found, id: d13bf48c1b38e0507a5a55b61a4bcb5efailed to run 3PC java.lang.ClassCastException On the Event Connector clicking on "Test Connection" it throws the below error, Further analyzing the MID server below traces will be identified, Worker-Interactive:ConnectorProbe-466bc5181b7820107a5a55b61a4bcbc7 Worker starting: ConnectorProbe source: XXX-vRops-view-ProdWorker-Interactive:ConnectorProbe-466bc5181b7820107a5a55b61a4bcbc7 TP_CON_DEBUG: probe calledWorker-Interactive:ConnectorProbe-466bc5181b7820107a5a55b61a4bcbc7 SEVERE *** ERROR *** Credentials not found, id: d13bf48c1b38e0507a5a55b61a4bcb5e ReleaseInstance with Event Management (com.glideapp.itom.snac) plugin enabled.CauseOrphaned records are found in the (discovery_credentials) table. This is generally caused by PRB1305469/KB0717208.This can be verified this by navigating to Discovery >> Credentials, opening the credential(s) with the "sys_id" that is thrown in error during test connection and it shows "Record not found"/"Page not fount". This the symptom that the credential record is an orphan record. ResolutionComplete details in avoiding and resolving this issue follow the KB0717208.