AUTOSOL App Manager doesn’t start because it cannot connect to port 5432
In this case AUTOSOL App Manager is unable to start because it cannot connect to the local postgres Postgres database. Result looks something like this:
...
Open Windows Services and verify that the postgresql PostgreSQL service is installed. If it is installed, start the service and the problem should resolve.
If the postgres Postgres service is not installed, the entire Postgres installation may have failed silently. In that case:
Check to see if
...
Postgres is installed and install it if it isn’t. This path will exist and contain files if Postgres is installed:
C:\Program Files\PostgreSQL\12\bin
.
If
...
Postgres is installed, verify 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
...
the Postgres server but failed to install the cluster
...
, likely due to
...
file permissions. In that case, the resolution is to create the cluster and windows service yourself. To do so:
Choose a folder on
...
the Windows filesystem where you know you have permissions. Substitute that path for:
...
C:\Users\
...
username\Documents\alternatepostgresdb
in the following
...
script.
...
Open a Windows Command Line in Administrator mode
...
and paste the following:
Code Block | ||
---|---|---|
| ||
"C:\Program Files\PostgreSQL\12\bin\initdb" -D "C:\Users\jlairdusername\Documents\alternatepostgresdb" "C:\Program Files\PostgreSQL\12\bin\pg_ctl.exe" register -N postgresql-x64-12-alt -D "C:\Users\jlairdusername\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\AUTOSOLAppManager\AutosolAppManager.exe" migrate |
AUTOSOL App Manager should now start from the shortcut.