If the issue is related to licensing or activation, go to the “Licensing” section.
For unidentified issues, refer to the “Troubleshooting” section.
We recommend involving an IT specialist/system administrator to perform the instructions below.
After device reboot, the PACS Server service does not start.
The logs contain errors such as:
Error during selecting enabled Storage Devices. Cannot open connection (no connection)Error getting list of pending events. Can not execute query(no connection)DatabaseConnectionPool: Closing invalid connection #1.DatabaseConnectionPool: Establishing database connection #1DatabaseConnectionPool: Unable to connect to the database.If the dependency on the DBMS service startup is not configured, the PACS service may attempt to start before the database is ready and fail to connect.
The dependency is set during server deployment via the installation script at the step: “Add dependency from DBMS service? [Y,N]?”
Configure a dependency on the DBMS service startup.
Command:
sc config PACSServer depend= DBMS-NAME
Where PACSServer is the default service name, and DBMS-NAME is the DBMS service name.
Examples:
sc config PACSServer depend= MySQL
sc config PACSServer depend= postgreSQL-x64-15
Edit the service file /etc/systemd/system/pacsserver.service:
In the [Unit] section, add or replace the line:
After=network.target DBMS-NAME
Where pacsserver is the default service name, and DBMS-NAME is the DBMS service name.
Example [Unit] section:
[Unit]
Description=Inobitec DICOM Server (PACS)
After=network.target postgresql-14