Troubleshooting MQServer Windows

This section helps you troubleshoot the common problems that you might encounter when using certificate server functionalities. This guide will give more troubleshooting processes on server addition, deletion, import, export, push, bind, rollback, and other actions associated with MQServer Windows.

Issues in Device communication


Error Message	Possible Cause	Possible Solution
Communication to <hostname> failed	Gateway agent not reachable. Device not reachable from the gateway agent	Ensure gateway is configured properly and the APIs are accessible from AppViewX. Ensure device and gateway agent are in the same domain and device is accessible from gateway agent.
Communication to <hostname> failed Device version fetch has failed.	Hostname or Credentials configured is wrong	Ensure hostname and the device credentials configured while device addition is valid.

Issues in Certificate Discovery


Error Message	Possible Cause	Possible Solution
Received failed response from batch	MQServer QManager is not up and running.	Login to the target device Switch to user which has mqm group access start the QManager Command: strmqm <qname>
Received failed response from batch	No valid KDB files available in the path configured to the QManager	Ensure the path configured in QManager has valid KDB files and KDB has certs. Command to find path: echo "DIS QMGR SSLKEYR" \| runmqsc.

Issues in CSR generation at Endpoint


Error Message	Possible Cause	Possible Solution
Failure response obtained on consuming REST API. CSR submission failed	User has restricted access to the path configured for the “CSR FileName” and “Key File name”	Kindly ensure the user configured for device addition has read/write access to the path configured.

Issues in Certificate Push


Error Message	Possible Cause	Possible Solution
Push Failed. CTGSK3026W The key file "D:/mtest/mtest.kdb" does not exist or cannot be read.	User has restricted access to the path configured to push the certificate in the application connector	Kindly ensure the user is configured while device addition has the read/write access to the path configured in application connector to certificate push.
Push Failed due to KDB push got failed.	Target KDB file does not exist in the device	Ensure the target KDB file, for which certificate push configured is available and has read/write access.