При установке postgresql выдает ошибку

This page is intended to help people collect information to troubleshoot problems with the PostgreSQL Installers supplied by EnterpriseDB.

Many problems have already been identified and fixed, so make sure you’re using the installer for the latest point-release of PostgreSQL before reporting a problem.

Because some problems can’t be fixed in the installer, but are issues with the Windows installation or how it is being used, there is also a list of frequently asked questions and frequently encountered problems with PostgreSQL on Windows. Please read the common installation errors section, or preferably the whole document. You’ll probably save some time and hassle by doing so.

If you’ve tried all that, and you’re still having problems getting PostgreSQL installed, please read on to find out how you can collect the information we need to be able to help you with installation problems.

Make sure you’re installing on a supported platform

See the installer download page and (for Windows) the Running & Installing PostgreSQL On Native Windows for platform support details.

Please do not ask the mailing list for help with installation on unsupported Windows platforms. However, one of the paid PostgreSQL consultants, or EnterpriseDB (who make the PostgreSQL installer) may be able to help you on a paid basis.

Try again without your virus scanner or 3rd-party firewall

The Windows FAQ discusses potential issues with antivirus software and 3rd-party firewalls. If you’re encountering any installation issues, please try again with your virus scanner uninstalled (not just disabled) to see if the problem goes away. If it does, please report the fact to the mailing list and to the vendor of your antivirus product.

Read about other common installation problems

Before reporting a problem, please read the windows FAQ to see if your problem is one we’ve already seen and found a workaround or fix for.

Reporting an installation error

To be able to help you with an installation problem, we will need you to collect some basic details about your computer and the problem. Please see the instructions below.

Note down the basic information about your system

Any problem report must include:

• The exact words of any error message you see when the installation fails
• The exact version of PostgreSQL you are installing
• Whether you installed a 32-bit or 64-bit release of PostgreSQL
• The operating system and version you are using, eg:
  • «Windows XP Professional with Service Pack 3»
  • «Mac OS X 10.4.2»
  • «Fedora Core 14»
• Whether you are running a 32-bit or 64-bit version of your operating system
• How you ran the installer. Command-line arguments, what user account you ran it from, etc.
• What antivirus and/or software firewall products you have installed, if any, even if they are disabled
• Which, if any, of the troubleshooting instructions you have already tried
• Whether a previous version of PostgreSQL was installed, and if so:
  • whether you uninstalled it before running the new installer
  • If you uninstalled a previous version, whether you did it with the uninstaller or some other way
  • Whether you removed the postgres user/service account when you uninstalled
• Additional details and platform-specific information as described below

Collect the installer log file

The installer creates a log file in the system ‘temp’ directory. This will log all manner of data about the installation, and is invaluable when troubleshooting. The log will be called install-postgresql.log if the installation completed successfully. If not, the installer may not have been able to rename it, in which case the name will be either bitrock_installer.log or bitrock_installer_xxx.log, where xxx is a number (actually the process ID of the installation attempt).

On Linux and Mac systems, the logfile will almost always be found in the /tmp/ directory.

On Windows, the easiest way to find the logfile is to click Start -> Run, enter %TEMP% in the box and then click OK (these instructions apply to Windows XP and 2003 — adjust as necessary for other versions).

Get the contents of the PostgreSQL server error log

The PostgreSQL server has its own error log. This may not exist if installation failed early on, but it can be very informative for errors that happened later in installation. You can find it in the «pg_log» folder inside the data directory you chose for PostgreSQL. If it exists, please include it in any problem reports.

Windows users must collect additional Windows-specific details to help troubleshoot installation issues:

• (On Windows Vista and Windows 7): The UAC security level
• Whether you started the installer by logging in as Administrator, started it from from your own normal user account, or ran it using the «Run As Administrator» menu option.
• Whether your computer is a part of a Windows domain. Home computers usually are not, business computers usually are.
• Whether your computer and network has any Group Policy configured. If you’re on a corporate windows domain you probably have group policy and need to ask your network administrator for details about it.

Windows: Check for messages in the Windows event log

Please check the Windows Event Viewer for messages that might be related to installation problems or service startup problems.

TODO: detail on how to collect and save events.

Windows: Check what Group Policy, if any, is active on your computer

TODO: instructions for collecting domain and local group policy.

Windows: Take a copy of the environment variables set on the computer

Open a command prompt and run «set». Then copy and paste the results into your problem report.

I’d be better to collect the «all users» environment from the system control panel, but it’s not easy to just dump this information.

I’ve pulled shin’s link from the google cache:

Original link:
http://www.geekscribes.net/blog/2009/04/22/postgresql-database-cluster-initialisation-failed-solution/

Cached link:
http://webcache.googleusercontent.com/search?q=cache:RXu-5-ZzfcgJ:www.geekscribes.net/blog/2009/04/22/postgresql-database-cluster-initialisation-failed-solution/+&cd=3&hl=ro&ct=clnk

PostgreSQL Database Cluster Initialisation Failed Solution

I’ll keep this one short and sweet. For those of you that have tried to install PostgreSQL (mine was 8.3.7-1) on Windows Vista and got the error Database Cluster Initialisation Failed error at the end of the install, read this.

The problem is that Vista has some safety features associated with setting permissions on the Program Files folder. Basically, even if you are an admin, you can’t change permissions on some folders like Program Files and Windows folder itself. This causes initdb to be unable to create some folders and the database cluster. What this means for you is that you need to install PostgreSQL in another folder that is not inside Program Files.

By the way, if you have forgotten your Postgres account password while installing the first time, just open a Command Prompt in Vista (If you don’t know how, Google for it). Then type the command “net user”. You will see a list of users on your computer. Find Postgre’s account. It’s usually “postgres“. Then you need to change its password by typing “net user postgres new_password” where new_password is… well, a new password for the account. You will be needing that postgres account during install. You will need admin privileges to do this change however.

Firstly, uninstall any failed installations. Use the Control Panel or the PostgreSQL installer in the install folder.

During the install, you will be prompted to choose where you want to install the program. Just select a location in another place. Like “C:PostgreSQL” or something similar. It may even be on your desktop. But not inside Program Files. Not inside Windows folder. However, it’s not as easy. Bear with me.

After the install, you will still see that darned error message (or something like non-fatal error occured). Do not despair! (For Windows Power Users, we are just assigning Full Control permission to Postgres account on the new PostgreSQL install folder). For other users, read on if you don’t know how to do it.

Go to where you just installed PostgreSQL. In this case, the C: drive. There, right-click on the folder (usually called PostgreSQL), and go to Properties – Security tab. Click on the Edit button. You will now see some usernames and other stuff. Click on the Add button. In the “Enter the object names to select” box, enter “postgres” and press Check. Postgres’ user account should appear there. Click on Ok.

Now from the “Group or Usernames” box, select the Postgres account. In the window below, with lots of checkboxes, assign permission “Full Control” in the Allow Column to it. Note, if you don’t want to allow full control, just give it read/write. But I just went ahead and gave it Full Control. (I was tired and annoyed. The “World’s most advanced open source database” had failed to install!). Click on Ok and wait a bit for permissions to be applied.

Then, just do a re-install. Do not uninstall anything. Just run the setup again. It’ll say that a PostgreSQL install folder already exists and other stuff. Just click on Next until the install finishes. If you see “file cannot be copied” errors, click on the “ignore” button when needed.

That’s it. PostgreSQL should be up and running on Vista now. Hope it works for you too as it did for me, and that my guide is helpful to anybody. If it works, or if you have other solutions, let us know. Thanks for reading!

После Java Core очень хочу изучить БД, но не получается ее установить, не то что изучить….

Текст ошибки: «Failed to load SQL modules into the database cluster». Появляется в конце установки программы.

Уже пытался сделать некоторые вещи, находил на других форумах:
1) Давал все права пользователей к папке
2) Устанавливал программу на разные диски
3) Добавлял пользователя «postgres» и давал ему права. Добавлял в группу Администраторы
Полагаю, есть еще решения.

I’m trying to install postgreSQL on my windows 10 computer for the first time. I got two errors at the end of the installation

1) a non-fatal error occured during cluster initialisation. please check the installation log in C:usersabcAppDataLocalTemp for details

2) problem running post-install step. Installation may not complete correctly.Failed to start the database-server.

I also tried a number of other (but very dated) solutions to similar problems users experienced such as moving my data directory outside of the Postgres directory entirely. Most of these solutions date back and don’t seem to work anymore.

The one that seemed closest to working is [PostgreSQL Database Cluster Initialisation Failed Solution][1]

However, I can’t find «postgres» as a user. I get an error saying: «An object named «postgres» cannot be found. Check the selected object types and location for accuracy and ensure that you typed the object name correctly, or remove this object from the selection.»

Does anybody have any updated solutions/tips for this?

Please see the logs: I have added some more logs below this.

> Log started 09/08/2017 at 15:35:34
Preferred installation mode : qt
Trying to init installer in mode qt
Mode qt successfully initialized
Executing C:UsersskumAppDataLocalTemp/postgresql_installer_c42ee2159f/temp_check_comspec.bat 
Script exit code: 0

Script output:
 "test ok"

Script stderr:


Could not find registry key HKEY_LOCAL_MACHINESOFTWAREPostgreSQLInstallationspostgresql-x64-9.6 Data Directory. Setting variable iDataDirectory to empty value
Could not find registry key HKEY_LOCAL_MACHINESOFTWAREPostgreSQLInstallationspostgresql-x64-9.6 Service ID. Setting variable iServiceName to empty value
Could not find registry key HKEY_LOCAL_MACHINESOFTWAREPostgreSQLInstallationspostgresql-x64-9.6 Service Account. Setting variable iServiceAccount to empty value
Could not find registry key HKEY_LOCAL_MACHINESOFTWAREPostgreSQLInstallationspostgresql-x64-9.6 Super User. Setting variable iSuperuser to empty value
Could not find registry key HKEY_LOCAL_MACHINESOFTWAREPostgreSQLInstallationspostgresql-x64-9.6 Branding. Setting variable iBranding to empty value
Could not find registry key HKEY_LOCAL_MACHINESOFTWAREPostgreSQLInstallationspostgresql-x64-9.6 DisableStackBuilder. Setting variable iDisableStackBuilder to empty value
[15:35:38] Existing base directory: C:Usersskumpostgres_inst
[15:35:38] Existing data directory: 
[15:35:38] Using branding: PostgreSQL 9.6
[15:35:38] Using Super User: postgres and Service Account: NT AUTHORITYNetworkService
[15:35:38] Using Service Name: postgresql-x64-9.6
Executing cscript //NoLogo "C:UsersskumAppDataLocalTemppostgresql_installer_c42ee2159fprerun_checks.vbs"
Script exit code: 0

Script output:
 The scripting host appears to be functional.

Script stderr:


Executing C:UsersskumAppDataLocalTemppostgresql_installer_c42ee2159fvcredist_x64.exe /passive /norestart
Script exit code: 0

Script output:


Script stderr:


Executing C:UsersskumAppDataLocalTemppostgresql_installer_c42ee2159fvcredist_x86.exe /passive /norestart
Script exit code: 0

Script output:


Script stderr:


Executing C:UsersskumAppDataLocalTemppostgresql_installer_c42ee2159fgetlocales.exe 
Script exit code: 0

Logs Part 1:

Failed to ensure the data directory is accessible (C:UsersskumpostgresqlData)
Executing batch file 'radB66AD.bat'...
The files belonging to this database system will be owned by user "skum".
This user must also own the server process.

The database cluster will be initialized with locale "English_United States.1252".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory C:/Users/skum/postgresqlData ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... windows
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

Success. You can now start the database server using:

    "C:Usersskumpostgres_instbinpg_ctl" -D "C:UsersskumpostgresqlData" -l logfile start


Reading:    C:UsersskumpostgresqlDatapostgresql.conf exists...
Writing:    C:UsersskumpostgresqlDatapostgresql.conf exists...
Called AclCheck(C:UsersskumpostgresqlData)
Called IsVistaOrNewer()...
    'winmgmts' object initialized...
    Version:10.
    MajorVersion:10
Executing icacls to ensure the NT AUTHORITYNetworkService account can read the path C:UsersskumpostgresqlData
    Executing batch file 'radB66AD.bat'...
    'icacls' is not recognized as an internal or external command,
operable program or batch file.

Called IsVistaOrNewer()...
    'winmgmts' object initialized...
    Version:10.
    MajorVersion:10
Granting service account access to the data directory (using icacls) to NT AUTHORITYNetworkService:
    Executing batch file 'radB66AD.bat'...
    'icacls' is not recognized as an internal or external command,
operable program or batch file.

Failed to grant service account access to the data directory (C:UsersskumpostgresqlData)
initcluster.vbs ran to completion

Script stderr:
 Program ended with an error exit code

Error running cscript //NoLogo "C:Usersskumpostgres_inst/installer/server/initcluster.vbs" "NT AUTHORITYNetworkService" "postgres" "****" "C:Usersskumpostgres_inst" "C:UsersskumpostgresqlData" 5432 "DEFAULT" 0: Program ended with an error exit code
Configuring database server startup...
Executing cscript //NoLogo "C:Usersskumpostgres_instinstallerserverstartupcfg.vbs" 9.6 "NT AUTHORITYNetworkService" "****" "C:Usersskumpostgres_inst" "C:UsersskumpostgresqlData" "postgresql-x64-9.6"
Script exit code: 0

Script output:
 startupcfg.vbs ran to completion

Script stderr:


Creating menu shortcuts...
Executing cscript //NoLogo "C:Usersskumpostgres_instinstallerservercreateshortcuts.vbs" 9.6 "postgres" 5432 "PostgreSQL 9.6" "C:Usersskumpostgres_inst" "C:UsersskumpostgresqlData" "postgresql-x64-9.6"
Script exit code: 0

Script output:
 Start FixupFile(C:Usersskumpostgres_instscriptsserverctl.vbs)...
   Opening file for reading...
   Closing file (reading)...
   Replacing placeholders...
   Opening file for writing...
   Closing file...
  End FixupFile()...
Start FixupFile(C:Usersskumpostgres_instscriptsrunpsql.bat)...
   Opening file for reading...
   Closing file (reading)...
   Replacing placeholders...
   Opening file for writing...
   Closing file...
  End FixupFile()...
createshortcuts.vbs ran to completion

Script stderr:


Starting the database server...
Executing cscript //NoLogo "C:Usersskumpostgres_instinstallerserverstartserver.vbs" postgresql-x64-9.6
Script exit code: 1

Script output:
 Starting postgresql-x64-9.6
Failed to start the database server (2)

Script stderr:
 Program ended with an error exit code

Error running cscript //NoLogo "C:Usersskumpostgres_instinstallerserverstartserver.vbs" postgresql-x64-9.6: Program ended with an error exit code
Problem running post-install step. Installation may not complete correctly
 Failed to start the database server.
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 09/08/2017 at 15:41:35