Troubleshooting Websphere 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 Websphere Windows.

Issues in Server Addition using AppViewX GUI

Error Message Possible Cause Possible Solution
Device Name already exists. A device with the same name already exists in inventory. Check the Device name, it should be unique.
Details incorrect Some of the mandatory fields might be missing or might be invalid. Add all the valid information in the mandatory section.

Issues in Device communication

Error Message Possible Cause Possible Solution
Connecting to remote server ptpld123 failed with the following error message : The user name or password is incorrect. For more information, see the about_Remote_Troubleshooting Help topic. Invalid hostname/Invalid credential

Kindly check if the given host is reachable.

Kindly provide valid credentials and update the device details.
Communication to <host> failed. Windows Agent is not reachable or down Kindly check if windows agent configured and in running state.
Websphere version fetch has failed Websphere setup is not available/not configured in given device Kindly validate is Websphere configured properly

Issues in Certificate Discovery

Error Message Possible Cause Possible Solution
Received failed response from batch.

  1. No valid keystore files available in the given path.

  2. Users don't have access for the configured location/file.

  3. Web Server or WAS console is not active.

  1. Kindly Ensure the given certificate location has a valid cert.

  2. Kindly ensure users have proper access privilege to read certs.

  3. Kindly ensure WebServer is in up and running state

.

Issues in CSR generation at Endpoint

Error Message Possible Cause Possible Solution
CSR Submission Failed User may have 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
Error while pushing certificate into device. 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.
Error while pushing certificate into device : Websphere due to Unsupported bit length:4096. Websphere will support bitlength up to 2048. Kindly ensure the certificate issued is compatible with the Websphere.
Error while pushing certificate into device : Websphere due to Unsupported Key Algorithm:DSA Unsupported key Algorithm. Kindly ensure the certificate issued is compatible with the Websphere.
Error while pushing certificate in Device : <device name>.PrivateKey not available. Private key is not available to parse certs. Kindly ensure to push certs with private key. If privatekey is available in the device please select privateKeyInDevice option.