Actian PSQL Not Started Automatically After Server Reboot
Release Date: 12/14/2017
Q - I restarted the server and for whatever reason the relational and transactional engines do not start, even though they are set to automatic. Have any idea why this is happening?
A - Go to PSQL services –properties -- and change the startup type to “Automatic (delayed start)” instead of “Automatic.” The system may be starting too quick to load the services. See sample screen below:
EMK
Related Articles
After Server Reboot, Elliott Stopped Working Due to PSQL Engines Not Starting
Release Date: 08/09/2022 Version: All Q - Our server has been rebooted for maintenance. Since the eboot, none of the Elliott users can use Elliott Business Software. A - This can happen if PSQL services did not start after the server reboot. We have ...
A Case Where PSQL 13 Client Is Not Compatible with PSQL 15 Server
Release Date: 02/04/2025 Version: 8.6 Do Users Need to Upgrade to PSQL 15 Client When Upgrading PSQL Server? We were often asked in the past if our users should upgrade their PSQL 13 client when they upgrade to the PSQL 15 server. In our past ...
Configure PSQL Server Memory Usage
Version: Any Release Date: 12/17/2021 Q - Can you tell us why PSQL process is taking up so much memory? Is there anything we can do? See sample screen below: A - PSQL server by default can take up about 60ish% of the server memory. This is ...
Does Elliott Support Windows Server 2019?
Release Date: 7/8/2019 Version: 8.5 Q: Does Elliott and PSQL support Windows Server 2019? A: We tested the latest Elliott 8.5 on server 2019 and it works. We can’t guarantee that the older Elliott versions will work with server 2019. In addition, per ...
Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?
In the virtual server environment, it is very easy to adjust the server's memory in order to better suit your requirements and more efficiently use the server hardware. However, it is important for you to be aware that the PSQL 11 engine license can ...