Universal App Manager doesn’t start because it cannot connect to port 5432
In this case Universal App Manager is unable to start because it cannot connect to the local postgres database. Result looks something like this:
Things to do:
Open Windows Services and verify that the postgresql service is installed. If it is installed, start the service and the problem should resolve.
If the postgres service is not installed, the installation may have failed silently. In that case:
Check to see if postgres was installed at all, this path should exist and it should be populated with files:
C:\Program Files\PostgreSQL\12\bin
If the path exists and it is populated with files, that means postgres server installed. Now check to make sure that the database cluster was created. By default the cluster is at this path:
C:\Program Files\PostgreSQL\12\data
If you see the path but no files, it means that the installer installed postgres server but failed to install the cluster. This case has been confirmed once, due to problems with file permissions. In that case, the resolution is to create the cluster and windows service yourself. To do so:
Choose a folder on your Windows filesystem where you know you have permissions. Substitute that path for:
C:\Users\jlaird\Documents\alternatepostgresdb
in the following steps. Steps:
Open a Windows Command Line in Administrator mode.
"C:\Program Files\PostgreSQL\12\bin\initdb" -D "C:\Users\jlaird\Documents\alternatepostgresdb" "C:\Program Files\PostgreSQL\12\bin\pg_ctl.exe" register -N postgresql-x64-12-alt -D "C:\Users\jlaird\Documents\alternatepostgresdb" net start postgresql-x64-12-alt "C:\Program Files\PostgreSQL\12\bin\psql" -d template1 template1=# CREATE ROLE postgres LOGIN SUPERUSER PASSWORD 'postgres'; template1=# CREATE DATABASE "ASIServerDB" OWNER postgres; template1=# \q "C:\Program Files\AutoSol\UniversalAppManager\UniversalAppManager.exe" migrate
Universal App Manager should now start from the shortcut.