Backend

Updated on Aug 22, 2024
Published on Oct 17, 2022

3 minute(s) read

PG

The sections below describe the troubleshooting steps to undertake for problems associated with the Backend modules.

ZRP

Problem	Actions
After a Backend installation, the ZRP service is stopped.	Check in the `zetalyinstall.cnf` file if the ZRP database settings (database name / user or password) are correct.

ZHB

Problem	Actions
After a Backend installation, the ZHB service is stopped.	Check that the BI Tool is launched and accessible, by accessing either https://localhost:8081 or if the installation was customized https://{BI.Host.Base}:{BI.Host.Port} , where {BI.Host.Base} and {BI.Host.Port} are the customized IP address and port that you defined in the `zetalyinstall.cnf` file.

ZCC

Problem	Actions
After a Backend installation in upgrade mode: There are many errors in the console such as `The directory is not empty.` or `The path xxxxxxx is denied.` The ZCC service can not restart.	See known issue ZETALY-3135 below Currently, during the installation script, the ZCC service is not completely stopped before attempting the upgrade. During an upgrade, manually stop the ZCC service, or relaunch the upgrade installation. As a rule, if there is a problem with the database connection, the ZCC service will not start. The database connection for the ZCC module must be checked.
Installation script - BackAndFront upgrade - Error on ZCC reinstall (ZETALY-3135)	After a Backend installation in upgrade mode: There are many errors in the console such as `The directory is not empty.` or `The path xxxxxxx is denied.` The ZCC service cannot restart Currently, during the installation script, the ZCC service is not completely stopped before attempting the upgrade. During an upgrade, stop the ZCC service, or relaunch the upgrade installation.
If the installation directory is not available when a command is used, you may receive the following error : `Remove-Item: C:\zpackages\R-2022-04-08-1119\R2022-04-08-1119\zetalyinstall.ps1:775 Line \| 775 \| Remove-Item $this.config['Backend.ZCC.TargetDir'] -Recurs … \|Access to the path 'C:\zetalySuite\ZCC\SerilogTimings.dll' is denied.`	Windows services can take several minutes to stop. Wait a few minutes and relaunch the installation. Launch the Windows Services Console. If the service is locked and cannot be removed, close any services related windows. If the error persists, check if a Windows process is locking the `C:\zetalySuite\ZCC`directory. Launch Windows Resource Monitor (press Windows Key + R, and enter `resmon.exe` in the Open field of the Run dialog box that appears). From the Windows Resource Monitor, select the CPU tab and expand the Associated Handles panel. In the Search Handle field, enter `C:\zetalySuite\ZCC` to find the process locking the directory. Right mouse click on the processes that appear, and select End Process.
ZCC (or ZSA) service will not start (even when launched with the task manager)	Your machine does not have the required specifications and the service cannot start fast enough before Windows thinks there is an error. You can work around this by rising this delay in the registry. See the official windows documentation.
A filter appears on the Budget page that is not present in the Custom Filters page.	Create the filter in Custom Filter page with the same name as on the Budget page. If you do not need it anymore, delete the filter and it will disappear from the custom page and budgets.
If the cost calculation is stopped abruptly (because of a ZCC service stopped during calculation), it remains blocked.	See known issue ZETALY-5401-ZCC-Launch calculation-if the calculation is stopped abruptly, it will remain blocked Delete the last record of the log table to restart the calculation launch, as follows: PostgreSQL : `DELETE FROM cc.configuration_log WHERE id IN (SELECT id FROM cc.configuration_log ORDER BY date DESC LIMIT 1)` MSSQL : `DELETE FROM cc.configuration_log WHERE id IN (SELECT TOP 1 id FROM cc.configuration_log ORDER BY date DESC);`

ZSA

Problem	Actions
ZSA (or ZCC) service will not start (even when launched with the task manager)	Your machine does not have the required specifications and the service cannot start fast enough before Windows thinks there is an error. You can work around this by rising this delay in the registry. See the official windows documentation.