Discovery logs failing schedules with error "Parameter 'password' may not be null!" - Support and Troubleshooting

Discovery logs failing schedules with error "Parameter 'password' may not be null!" Issue  Symptoms Sometimes the discovery schedule and/or quick discovery may fail with below error.

"" java.lang.IllegalArgumentException: Parameter 'password' may not be null! at com.service_now.mid.probe.shazzam.packets.ASN.getASCIIString(ASN.java:73) at com.service_now.mid.probe.shazzam.packets "" Release All releases.

Cause This issue occurs mostly when the provided or one of the credentials are invalid or empty. When discovery runs the MID Server tries to query all the credentials one after the other untill the successful query. In this process if one of the credential is empty (username or password is empty) or if the record itself orphan then the issue comes.

Mostly these kind of issues occurs after the cloning. Because, sometimes we preserve the discovery_credentails table data but not their child table data. In these scenarios the record (same record) is deleted in child table and not on parent table. Please see KB0723549 for more details.

Resolution Make sure there are no orphan credentials in the credentials table. Make all the credentials does have the username/password fields are populated based on credentials type. (Like the SNMP community credentials will not have any password) If any credentials are orphaned delete them using background scripts or table cleanup. If you are not able to delete these orphan credentials submit a ticket to ServiceNow Support. Additional Information KB0723549 Active MID Server post-cloning credential issues