The QUBEdocs KeepAlive service is a service that is used to keep QUBEdocs "awake" and listening for scheduled documentation requests.
Error: "Service 'QUBEdocs Keep Alive' (KeepAlive.exe) failed to start. Verify that you have sufficient privileges to start system services."
There are two possible causes for this error:
- If the application pool identity credentials are incorrect in the installation step to set up the application pool, you will see the following error when the QUBEdocs Keep Alive service is trying to be started. You will need to click on "Cancel" and restart the installation process.
- Please ensure that the user that you provide during the installation of QUBEdocs has the ability log on as a service (You can verify if a user can log on as a service by using the "Local Security Policy" tool: Control Panel -> Administrative Tools -> Local Security Policy\Local Policies\User Rights Assignment\Log on as a service).
Error: "KeepAlive | Fatal | QDLogger | Failed to send keep alive"
In the QUBEdocsServer.log, the following error is appearing every 2 minutes:
"2022-06-27 16:51:37.6143 | DEV001 | 29180 | KeepAlive | Fatal | QDLogger | Failed to send keep alive | System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:80"
For machines that are not running QUBEdocs on port 80, this error is going to occur as by default, the KeepAlive service is set to run on port 80. This can be manually changed, though.
Navigate to "C:\Program Files\QUBEdocs Ltd\QUBEdocs\api\bin" (or the directory wherever you have installed QUBEdocs) and look for a file called "KeepAlive.exe.config"
You can change the port number in here to match whatever your QUBEdocs instance is running off of by altering the "value" of the key "basePort".
Make sure to restart the QUBEdocs Keep Alive service in the Services application:
Comments
0 comments
Please sign in to leave a comment.