Failed to load sql modules into the database cluster during PostgreSQL Installation

Question

I have attempted to install PostgreSQL 9.4 and 8.4 multiple times and it is failing no matter what I have tried. I am attempting to install on Windows 7 SP1 x64. After each

Answer 1

I think this would be better as individual comments above, but I don't have the required rep. I just spent days on this, with Postgre 10 on Win 10 Creators. My "answer" was to let Postgre put the data in its default install folder instead of my User folder (where it would be automatically backed-up).

1. This problem can happen with no reported install errors at all. On my very first try, I saw:

Failed to load SQL modules into the database cluster.

But that seemed to be due to:

Executing C:\Users\loren\AppData\Local\Temp\postgresql_installer_aee8e5a76f\vcredist_x64.exe /passive /norestart
Script exit code: 3010

    MSI (s) (AC:FC) [14:21:35:341]: Product: Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.40660. 
Restart required. The installation or update for the product required a restart for all changes to take effect.  
The restart was deferred to a later time.

Restarting Windows after the failure of the rest of the Postgre installation did not let Postgre run.

Once VC was in place, uninstalling and re-installing Postgre (still with its data in my User folder) completed with no reported errors. But every attempt to access it, by any means, still resulted in something like this:

C:\Program Files\PostgreSQL\10\bin>psql
psql: could not connect to server: Connection refused (0x0000274D/10061)
        Is the server running on host "localhost" (::1) and accepting
        TCP/IP connections on port 5432?
could not connect to server: Connection refused (0x0000274D/10061)
        Is the server running on host "localhost" (127.0.0.1) and accepting
        TCP/IP connections on port 5432?

The RawCap sniffer showed TCP SYN followed immediately by RST,ACK on localhost for both v4 and v6 for each try. Netstat did not see port 5432 in use at all. All Postgre runtime logs were totally empty. In Windows Services, I could manually start the postgresql-x64-10 service, but it immediately stopped itself, with the note that some services do that normally.

2. I tried moving the data directory via the Postgre wiki procedure. Apparently for Postgre 10 it is incomplete. It does not deal with:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-10\Data Directory
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Services\postgresql-x64-10\Data Directory
C:\Program Files\PostgreSQL\10\pg_env.bat
C:\Program Files\PostgreSQL\10\scripts\serverctl.vbs

But fixing every data file instance I could find did not let it run. And even after fixing all those, and uninstalling and re-installing again with the default location, the new pgAdmin4 somehow still remembered my original User data directory location!

3. I did not try giving NETWORK SERVICE read/write permissions on my User folder. Once the default install worked I wanted to get on with my original project... Maybe that would have worked.

Answer 2

I had this issue too with 9.5 and got around it by:

1. Installing with the default data folder.
2. Making sure my new data folder had full control access for the "NETWORK SERVICE" account.
3. Then changing the default PGDATA folder as per this instruction: https://wiki.postgresql.org/wiki/Change_the_default_PGDATA_directory_on_Windows

Answer 3

I had the same experience as @gomisha. @Jeff G's solution did not work for me no matter which user ran the installer.

As long as the target data directory was anywhere under c:\users, the install or database cluster init would fail.

I was successful after creating c:\postgresql-data and ensuring that the postgres user had full access in the 'effective access' tool.

Note: I did not use control userpasswords2 to set up the postgres user; I did it through the traditional crappy Windows 10 user wizard that tries to make the user sign up for hotmail. I did run the install as postgres.

Answer 4

What worked for me is, during the install, specifying a Postgre SQL data folder that's outside of any Windows user profile directory (C:\Users), such as C:\postgres-data.

My setup:

• Win 10 Pro

• PostgreSQL 9.5 RC1

I ran into this issue when I tried setting PostgreSQL's data directory somewhere under my user profile's directory, such us somewhere under "My Documents".

I tried Jeff G's solution and it didn't work at first. It worked only when I kept the data directory as the default (C:\Program Files\PostgreSQL\9.5\data). So then I tested further and tried setting the data directory to somewhere outside of any user profile directories (i.e. somewhere that isn't under C:\Users). For example, C:\postgres-data and this worked.

I then just tried using that directory with my default user, and not bothering with the postgres temp user as outlined in Jeff G's solution and that also worked. So in the end, it had to do with my data directory being somewhere under C:\Users. As long as it was outside of that, it worked.

Answer 5

Hope It's Work.

1.)Uninstall PostgreSQL

2.)Delete the postgres user if it still exists :

net user postgres /delete

3.) Create the postgres user with a password you can remember:

net user /add postgres

4.) Add the postgres user to the Administrators group:

net localgroup administrators postgres /add

5.) Add the postgres user to the Power Users group

net localgroup "power users" postgres /add

6.) Run a command window as the postgres user:

runas /user:postgres cmd.exe

7.) Change user postgres and install postgresql

8.)Back your and remove the postgres user from the Administrators group.

net localgroup administrators postgres /delete

Answer 6

When installing PostgreSQL, do not use the following symbols in your database's admin password: %, <, and >.

Bug report and problem solution here