Summary: some troubleshooting techniques for specific issues that may be encountered when using CAST Storage Service/PostgreSQL

An existing connection was forcibly closed by the remote host

This error may be be accompanied by the following in the CAST Storage Service/PostgreSQL log:

FATAL: terminating connection due to idle-in-transaction timeout

If this situation occurs, you can try increasing the following value in the postgresql.conf file and then restarting the instance:


See for more information.

Windows Service fails to start

If your CAST Storage Service Windows Service fails to start, it may be due to multiple instances of the postgres.exe running in background. To resolve the issue, kill all instances of the postgres.exe that are visible in Windows Task Manager, then try restarting the Windows Service.