Troubleshooting Windows JBoss Server

This section helps you troubleshoot the common problems that you might encounter when using certificate server functionalities. Effective troubleshooting documents depend on the availability of useful, detailed information. This guide will give more troubleshooting processes on server addition, deletion, import, export, push, bind, rollback, and other actions associated with Windows JBoss server.

Issues in Windows JBoss 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 Communicating to Windows JBoss Server


Error Message	Possible Cause	Possible Solution
Device name cannot be null or empty.	Device name is empty.	Provide device name as it is a mandatory field.
Invalid device name.	Device Name is not valid.	The Device name can only contain alphanumeric characters, '-' , '_' , '.' , '*' , '\|' , '!' and spaces.
Communication to <hostname> has failed	Hostname / Username / Password of the device added might be wrong.	Click on the device name in the Inventory Page. Update the correct details and click Save.
Communication to <Hostname> has failed due to Error while communicating via windows agent service	Windows agent provided is not reachable	Check Windows agent is Up and running and update the valid agent in the device addition page.
Error on fetching JBoss instance, config fetch process failed due to No configuration file found. Check installation directory path.	Provided installation directory path does not have JBoss configuration files like server.xml /standalone.xml	Login manually into the windows server and find the installation directory path which has the JBoss configuration files ( server.xml or standalone.xml) and provide the same directory path in JBoss device addition page.
Error on fetching JBoss instance, config fetch process failed due to df9cbf67-e1af-4d8c-8a7c-fe88bb83e0b3: PowerShell ScriptExecution Error in PTPLD178 : Cannot find path 'C:\tmp_1615504487924.tmp' because it does not exist.	Invalid installation directory path	Login manually into the windows server and find the installation directory path which has the JBoss configuration files ( server.xml or standalone.xml) and provide the same directory path in JBoss device addition page.
JBoss version fetch is failed	No JBoss server running in the target device / something wrong in the JBoss installation	Login manually into the windows server and find the JBoss server bin directory and run the below command to validate the JBoss version For JBoss 4.0.5 `<JBoss_server_Directory>/bin/run.bat -V` For JBoss 6.4 and 7.0 `<JBoss_server_Directory>/bin/standalone.bat -V` Currently only JBoss 4.0.5, 6.4 and 7.0 versions are supported in AppViewX.

Issues in Accessing Server

Access Issues might be reproduced when communicating with servers while discovering or fetching configuration files. These errors can be collected either from logs, API responses, or in the status field for the particular server.


Error Message	Possible Cause	Possible Solution
Permission denied for file/location.	File might not be present in the environment. User might not have permission to read in the given source location. Device communication might not be established when service has started.	Check whether someone deleted the file from the environment. Verify if read permission is given for the location. Verify the device connection and restart the service.

Issues in Config Fetch


Error Message	Possible Cause	Possible Solution
Communication to <hostname> has failed	Hostname / Username / Password of the device added might be wrong.	Verify the input details and check for device status error messages in the Issues in Communicating to Windows JBoss Server section.

Issues in Certificate Discovery


Error Message	Possible Cause	Possible Solution
Please provide information as required	Discovery name is not given or length is less than 2 characters. Interval between batches info. is missing when execution type is sequential.	Enter a valid name with a minimum of 2 characters. Provide a time interval between batches in minutes.
Please select a device	No device is selected in the “Discover By” section.	Select at least one device to discover certificates from.

Issues in CSR generation


Error Message	Possible Cause	Possible Solution
Problem while generating csr on target server	General Failure - SSH/SFTP communication failure	Provide correct credentials and make sure device communication is successful.
Invalid key type specified in the request	Given key type might not be supported by open SSL in the target machine.	Provide valid key type.
Problem while generating csr on the target server.	Location might not have permission.	Check the permission and provide it.
CSR and Private key has been failed	Open SSL configuration might be wrong in the target machine.	Check and correct open SSL configuration in the device.
CSR generation got 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 Push and Rollback


Error Message	Possible Cause	Possible Solution
Unable to initiate request.	Pushing to device when certificate is unavailable, i.e, in a new state. Previous work order is in progress and not completed. AppConnector might not be in sync.	Push to device after certificate has been retrieved from CA. Initiate push after previous work order is finished. Synchronize the AppConnector and retry.
Unable to initiate request, template is in disabled state	Given workflow is not in enabled state	Enable the push/rollback workflow from the Workflow section.
User is not authorized	User does not have required permissions to push to the device.	Retry after getting the access for required action.
Private key content is unavailable.	Private key content is not available for the certificate.	Private key is mandatory for the certificate to be pushed.
Application connector(s) not found	Application connector info was not found.	Provide the correct connectorId if not pushing using AppViewX UI.
Request associated with the application connector is in progress	Previous work order is in progress and not completed.	Initiate this request after the previous work order is finished.
Push not triggered or succeeded or No existing data available for backup process.	Rollback couldn’t proceed because push was not successful.	Only successfully pushed certificates can be rolled back.
Certificate not found.	Pushing to device when certificate is unavailable, i.e, in a new state.	Push to device after certificate has been retrieved from CA.
Certificate Push failed	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.
Certificate push failed due to Private key In device configured. But key content is available with the certificate from appview pushRequest So failing push request.	“Private key in Device” is enabled in application connector and also private key is available in the certificate	Ensure to uncheck “Private key in Device” attribute in application connector
PrivateKey in device push invalid	“Private key in Device” is enabled in application connector, but key is not available in device.	Ensure to enable “Private key in Device” attribute in application connector, if the certificate does not have the key and the certificate is generated using CSR gen option from Device.