Troubleshooting Windows Weblogic Server
Issues in Device communication
| Error Message | Possible Cause | Possible Solution |
|---|---|---|
| Device communication failed |
1. The given credential is incorrect. 2. Device not reachable 3.Hostname value is incorrect |
1. Check and input the correct credential. 2. Check and input the correct hostname value 3. Ensure the device is reachable |
| Error while communicating via windows agent service | Windows agent not reachable | Ensure windows agent is running and it's accessible |
|
Version fetch failed and Fetch weblogic instance failed |
Given “Weblogic Installation directory” is in-correct | Check and ensure the given installation path is correct |
Issues in Certificate Discovery
| Error Message | Possible Cause | Possible Solution |
|---|---|---|
| Received failed response from batch |
1. Device not running or not accessible 2. No valid certificates available |
1. Ensure target device is up and running 2. Check the device has valid certificate files |
Issues in CSR generation at Endpoint
| Error Message | Possible Cause | Possible Solution |
|---|---|---|
| CSR generation got failed/User has no permission for the given location to perform the operation. | User has restricted access to the path configured for the “CSR FileName” and “Key File name” | 1.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 |
|---|---|---|
| Private key is not available. Failing the push |
Private key not available in push request certificate |
Please ensure the private key is available in request |
| Private key In device configured. But key content is available with the certificate from appview pushRequest So failing push request. | Trying to push a certificate with key when the “Private key in device” enabled | Ensure the push certificate has no key when “Private key in device” is enabled. |
| Private key is not available in device. Failing the push | Private key file not available in the given key location when “Private key in device” is enabled | Ensure the target device has key file in the given location |
| Push failed since cannot write-into/create location(s) | User does not have permission to perform the operation |
1.Ensure the user has permission. 2.For sudo user, please check the access elevation value given in device addition |
| Device is not in managed state | Device is not available in managed | Please check the device status in device inventory |
