Postgresql an error occurred executing the microsoft vc runtime installer

Обсуждение: PostgreSQL 9.0 (x86-64) and Windows 7 (x86-64) — Unable to install

PostgreSQL 9.0 (x86-64) and Windows 7 (x86-64) — Unable to install

Re: PostgreSQL 9.0 (x86-64) and Windows 7 (x86-64) — Unable to install

We tried to reproduce this issue but could not do so. We have tried both the cases but both were not reproducible. Can you please provide more information which can help us in reproducing the issue,

From: Dr. Peter Voigt
Date: Tue, Sep 28, 2010 at 11:53 PM
Subject: [GENERAL] PostgreSQL 9.0 (x86-64) and Windows 7 (x86-64) —
Unable to install
To:

I cannot install PostgreSQL 9.0 (x86-64) under Windows 7 (x86-64). The
installer fails right after starting the installation process with the
message:

«An error occurred executing the Microsoft VC++ runtime installer».

I am using the installer from EnterpriseDB
http://www.enterprisedb.com/products/pgdownload.do. Installation file
is postgresql-9.0.0-1-windows_x64.exe.

Unfortunately there is no %TEMP%install-postgresql.log.

When scanning the mailing lists under
http://www.postgresql.org/community/lists/ and under
http://forums.enterprisedb.com/forums/show/9.page I can see that this
error has been described for several times with PostgreSQL 8.3 and 8.4
under different Windows variants. A common hint was to activate the
Windos Scripting Host (WSH) allthough it obviously does not help in
all cases. On my machine the WSH is activated and working.

Under
http://www.enterprisedb.com/learning/pginst_guide.do#troubleshooting
you can read about the command line options of the EnterpriseDB
PostgreSQL Installer. An attempt with «—install_runtimes 0» fails again
but with the different error message:

«Unknown error while running C:UsersAdministratorLokale
Einstellungenpostgres_installergetlocales.exe»

Again there is no %TEMP%install-postgresql.log.

As the second message is suggesting I am working as local
Administrator while installing PostgreSQL.

Maybe it is worth to be mentioned that I have installed Microsoft
Visual Studio 2008 Pro DE. Therefore the installation of the VC++
runtime should not be neccessary.

I am using now MySQL for serveral years and would like to compare it
with a current PostgreSQL version. The installation of PostgreSQL
under Windows is really disappointing but the same worked without
problems under Linux x86-64 (openSUSE 11.0). Under Linux I have used
the EnterpriseDB Installer of PostgreSQL 9.0 (x86-64) as well. The
installation file is postgresql-9.0.0-1-linux-x64.bin.

Is this problem already known and is there a solution for it?

—
Dharmendra Goyal
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +91-20-30589493
Mobile: +91-9552103323

This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.

Источник

postgresql-9.6.11-1-windows-x64.exe VC++ runtime installer

I searched the mailing list archive for
«postgresql-9.6.11-1-windows-x64.exe» and Google with
«site:postgresql.org postgresql-9.6.11-1-windows-x64.exe». Neither
turned up anything so I’m reporting it.

First problem — I tried to install PostgreSQL using the EnterpriseDB
postgresql-9.6.11-1-windows-x64.exe installer on 2 different Windows
10 laptops. On both, I get the following error message in a dialog
box.

Error
There has been an error.
An error occured executing the Microsoft VC++ runtime installer.

A suggested workaround (posted on https://oviedo.mx/tag/windows-10/ —
I did not try it myself) is to run the installer with the
«—install_runtimes 0» option.

The postgresql-9.6.10-2-windows-x64.exe,
postgresql-10.6-1-windows-x64.exe and
postgresql-11.1-1-windows-x64.exe installers work without problems.

Second problem — the word «occured» should have 2 r’s — occurred. I
don’t know if the message is coming from the PostgreSQL installer or
the VC++ runtime installer.

Источник

1stopIT blog

Mostly random thoughts about «IT stuff». mostly

Thursday, January 6, 2011

PostgreSQL Installation Problem on Windows without WSH

PostgreSQL 8.3 and 8.4 may fail to install on Windows with the following error message: «An error occurred executing the Microsoft VC++ runtime installer». PostgreSQL 9.x may fail with a different message: «Unable to write inside TEMP environment variable path», but the actual reason appears to be the same.

It turns out that the installer requires Windows Script Host to be enabled (there might be other reasons, but this is the problem I have stumbled upon).

Before you start messing with the registry, check if WSH is actually disabled or not. To do that run wscript.exe in the DOS box.

• If you see a dialog box called «Windows Script Host Settings», WSH is enabled, and your problem with PostgreSQL installation must be related to something else.
• If you get an error box that says «Windows Script Host access is disabled on this machine. Contact your administrator for details», WSH is disabled, and your problem with PostgreSQL installation may be related to it (or may be not).

Here is how to enable Windows Script Host for the current user (assuming he/she has administrator rights, of course):

1. Start Registry Editor (Start =>Run. =>regedit).
2. In the Registry Editor open HKEY_CURRENT_USERSoftwareMicrosoftWindows Script HostSettings
3. Make sure you actually are «inside» the Settings «folder».
4. Right-click anywhere in the right pane of the Registry Editor and select New =>DWORD Value and call it «Enabled». Then, double-click it and set the «Value data» field to «1».
5. Check if WSH is now enabled by running wscript.exe in the DOS box (see above).
6. If WSH is enabled, try installing PostgreSQL. If not, see below how to enable WSH system-wide.
7. Once the installation is complete, you can disable WSH by setting the «Enabled» value to «0».

The above may not work if Windows Script Host has been disabled system-wide. Here is how to enable it:

1. Start Registry Editor (Start =>Run. =>regedit).
2. In the Registry Editor open HKEY_LOCAL_MACHINESoftwareMicrosoftWindows Script HostSettings . Note that it is HKEY_LOCAL_MACHINE this time.
3. Make sure you actually are «inside» the Settings «folder».
4. Right-click anywhere in the right pane of the Registry Editor and select New =>DWORD Value and call it «Enabled». Then, double-click it and set the «Value data» field to «1».
5. Check if WSH is now enabled by running wscript.exe in the DOS box (see above).
6. If WSH is enabled, try installing PostgreSQL. If not, you may be using some third-party script blocker or something (I give up).
7. Once the installation is complete, you can disable WSH by setting the «Enabled» value to «0».

Again, if Windows Script Host is enabled, and PostgreSQL installation still fails, it must be related to something else that I have not encountered.

The above instructions are for Windows XP. They have been tested with PostgreSQL 8.3., 8.4 and 9.0.

They also have been tested on Windows 7 32-bit, but only PostgreSQL 8.4 has been installed.

The procedure should be similar on other versions of Windows.

I have received several reports about failed installation attempts on Windows 7 64-bit and none from Windows 7 32-bit users (or users of any other versions of Windows for that matter), which makes me suspect that this might be something specific to Windows 7 64-bit. Unfortunately, I do not have access to a machine with 64-bit Windows 7 needed to try to re-create the problem. See UPDATE at the very end of this post.

P.S. It had not occurred to me that WSH may be enabled, but the association between WSH and *.vbs files may be missing. It is indeed a possibility. Thanks to DIego, Rain and anonymous commenters for pointing it out.

P.P.S. If you are planning to use the serverctl.vbs script that comes with the Windows installation of PostgreSQL 8.x, you might want to keep WSH enabled. This script allows you to conveniently start and stop PostgreSQL database server directly from the Windows menu, an option that is not critical, but nice to have, especially if you run PostgreSQL on a laptop and do not really want it to run in the background all the time. On the other hand, you can achieve exactly the same simply by running
NET START postgresql_service_name
and
NET STOP postgresql_service_name
without WSH. So, there is hardly any real need to keep Windows Script Host enabled unless you need it for something else..

UPDATE
On a 64-bit Windows 7 system, when you right-click inside HKEY_CURRENT_USERSoftwareMicrosoftWindows Script HostSettings or HKEY_LOCAL_MACHINESoftwareMicrosoftWindows Script HostSettings and select New, there are two DWORD Value options: DWORD (32-bit) Value and DWORD (64-bit) Value. Somewhat counterintuitively, DWORD (32-bit) Value is the one you should select.

Источник

Thread: An error occured executing the MIcrosoft VC++ runtime installer

Thread Tools

Display

An error occured executing the MIcrosoft VC++ runtime installer

i just reinstalled W7 on my ssd and i can’t install HEM2,i didn’t installed antivirus or anything else just a few poker platforms ,chrome and that’s it.

«An error occured executing the MIcrosoft VC++ runtime installer» and after and PostgreSQL didn’t installed.

Make sure that you are running on an administrator account. What is your antivirus?

Please try these steps:

1) Download PostgreSQL 8.4 from Download PostgreSQL | EnterpriseDB
2) Put the file into C: folder
3) run cmd.exe «as Admin» (either search or go to start — programs — accessory — command prompt and right-click, run as administrator
4) in cmd window run following command: C:postgresql-8.4.22-1-windows.exe —install_runtimes 0
please be careful with spaces in command, it is particular with characters and spacing

may you live long and prosper,worked like a charm

You are very welcome. Thank you for letting us know it solved your problems. It helps us when crafting future replies to other customers with similar problems.

Good luck at the tables. If you have any further questions or problems do not hesitate to ask us.

Sarek will agree with your post!

Источник

Roman Patutin

В поисках названия для блога.

вторник, 14 июля 2009 г.

Postgres 8.4 и VC++ runtime error

Собрался я тут было перевести рабочий сервер на Postgres 8.4. Для проверки решил поставить на своей машине, а он сволочь выдает сообщение «An error occured executing the Microsoft VC++ runtime installer».
Немного покрутив пальцем у виска обнаружил, что в этом случае следует пускать инсталяху с ключом «—install_runtimes 0».

А вот полный список ключей:

• —prefix : директория в которую инсталировать postgres (по умолчанию %PROGRAMFILES%PostgreSQL8.X в Windows, /opt/PostgreSQL/8.X в Linux и/Library/PostgreSQL/8.X в Mac OS X);
• —datadir : определеяет где создавать диретокрию для храниня данных (по умолчанию $PREFIX/data) ;
• —superpassword : определяет пароль суперюзера (postgres который). Для Windows заодно и пароль пользователя от которого пускается сервис;
• —port : определяет номер порта, по умолчанию 5432, но если порту уже занят установленым посгрисом то 5433 и тд;
• —locale : локаль по умолчанию;
• —create_shortcuts [1|0]: определяет создавать ли ярлыки в меню «Пуск». По умолчанию 1;
• —install_plpgsql [1|0]:определяет устанавливать ли pl/pgsql в template1. По умолчанию 1 ;
• —install_runtimes [1|0]: (только Windows): определяет устинавливать или нет Microsoft Visual C++ runtimes перед установкой.По умолчанию 1.

В принципе все данные по инсталции можно посмотреть на сайте EnterpriseDB

3 комментария:

Big thanks chyvak! 🙂

а как пользоваться этими ключами? Я о них в первые услышал здесь. Распиши плиз, как пошагово запустить этот posgreql. У меня windows 7 и выдает, такую же ошибку. Спасибо

Источник

PostgreSQL 8.3 and 8.4 may fail to install on Windows with the following error message: «An error occurred executing the Microsoft VC++ runtime installer». PostgreSQL 9.x may fail with a different message: «Unable to write inside TEMP environment variable path», but the actual reason appears to be the same.

It turns out that the installer requires Windows Script Host to be enabled (there might be other reasons, but this is the problem I have stumbled upon).

Before you start messing with the registry, check if WSH is actually disabled or not. To do that run wscript.exe in the DOS box.

• If you see a dialog box called «Windows Script Host Settings», WSH is enabled, and your problem with PostgreSQL installation must be related to something else.
• If you get an error box that says «Windows Script Host access is disabled on this machine. Contact your administrator for details», WSH is disabled, and your problem with PostgreSQL installation may be related to it (or may be not).

Here is how to enable Windows Script Host for the current user (assuming he/she has administrator rights, of course):

1. Start Registry Editor (Start => Run… => regedit).
2. In the Registry Editor open HKEY_CURRENT_USERSoftwareMicrosoftWindows Script HostSettings
3. Make sure you actually are «inside» the Settings «folder».
4. Right-click anywhere in the right pane of the Registry Editor and select New => DWORD Value and call it «Enabled». Then, double-click it and set the «Value data» field to «1».
5. Check if WSH is now enabled by running wscript.exe in the DOS box (see above).
6. If WSH is enabled, try installing PostgreSQL. If not, see below how to enable WSH system-wide.
7. Once the installation is complete, you can disable WSH by setting the «Enabled» value to «0».

The above may not work if Windows Script Host has been disabled system-wide. Here is how to enable it:

1. Start Registry Editor (Start => Run… => regedit).
2. In the Registry Editor open HKEY_LOCAL_MACHINESoftwareMicrosoftWindows Script HostSettings. Note that it is HKEY_LOCAL_MACHINE this time.
3. Make sure you actually are «inside» the Settings «folder».
4. Right-click anywhere in the right pane of the Registry Editor and select New => DWORD Value and call it «Enabled». Then, double-click it and set the «Value data» field to «1».
5. Check if WSH is now enabled by running wscript.exe in the DOS box (see above).
6. If WSH is enabled, try installing PostgreSQL. If not, you may be using some third-party script blocker or something (I give up).
7. Once the installation is complete, you can disable WSH by setting the «Enabled» value to «0».

Again, if Windows Script Host is enabled, and PostgreSQL installation still fails, it must be related to something else that I have not encountered.

The above instructions are for Windows XP. They have been tested with PostgreSQL 8.3., 8.4 and 9.0.

They also have been tested on Windows 7 32-bit, but only PostgreSQL 8.4 has been installed.

The procedure should be similar on other versions of Windows.

I have received several reports about failed installation attempts on Windows 7 64-bit and none from Windows 7 32-bit users (or users of any other versions of Windows for that matter), which makes me suspect that this might be something specific to Windows 7 64-bit. Unfortunately, I do not have access to a machine with 64-bit Windows 7 needed to try to re-create the problem.

See UPDATE at the very end of this post.

P.S. It had not occurred to me that WSH may be enabled, but the association between WSH and *.vbs files may be missing. It is indeed a possibility. Thanks to DIego, Rain and anonymous commenters for pointing it out.

P.P.S. If you are planning to use the serverctl.vbs script that comes with the Windows installation of PostgreSQL 8.x, you might want to keep WSH enabled. This script allows you to conveniently start and stop PostgreSQL database server directly from the Windows menu, an option that is not critical, but nice to have, especially if you run PostgreSQL on a laptop and do not really want it to run in the background all the time. On the other hand, you can achieve exactly the same simply by running
NET START postgresql_service_name
and
NET STOP postgresql_service_name
without WSH. So, there is hardly any real need to keep Windows Script Host enabled unless you need it for something else..

UPDATE

On a 64-bit Windows 7 system, when you right-click inside HKEY_CURRENT_USERSoftwareMicrosoftWindows Script HostSettings or HKEY_LOCAL_MACHINESoftwareMicrosoftWindows Script HostSettings and select New, there are two DWORD Value options: DWORD (32-bit) Value and DWORD (64-bit) Value. Somewhat counterintuitively, DWORD (32-bit) Value is the one you should select.