[PORTS] Failed to run initdb: 128!

[anthony herve]

--0-1347277098-1170331097=:27699
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello,

I am trying to install postgresql-8.2.1-1 on a VPS server (via Remote Desktop) with Windows Server 2003 (pack 1).

I use the postgresql-8.2.msi installer with:
- installation language = english
- national language support, PL/java, Development files selected
- install a service option checked with postgres user
- initialise database cluster option checked with port 5432, accept connection on all adresses not just localhost option checked, locale English UK, encoding Latin1 and superuser postgres
- PL/pgsql, PL/perl, PL/python selected
- Adminpack selected as contrib module.

I execute the installation as Administrator (usergroup Administrators).
I get the error " Failed to run initdb: 128! " with an error log that is empty.

Googling this error, I can see it is probably something to do with authorisations but I can't figure out what is wrong exactly.

Have you ever encountered this error message? How did you finally fix it?

Thanks a lot for your help.
Best regards,
Anthony


---------------------------------
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses.
--0-1347277098-1170331097=:27699
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello,<br><br>I am trying to install postgresql-8.2.1-1 on a VPS server (via Remote Desktop) with Windows Server 2003 (pack 1).<br><br>I use the postgresql-8.2.msi installer with:<br>- installation language = english<br>- national language support, PL/java, Development files selected<br>- install a service option checked with postgres user<br>- initialise database cluster option checked with port 5432, accept connection on all adresses not just localhost option checked, locale English UK, encoding Latin1 and superuser postgres<br>- PL/pgsql, PL/perl, PL/python selected<br>- Adminpack selected as contrib module.<br><br>I execute the installation as Administrator (usergroup Administrators).<br>I get the error " Failed to run initdb: 128! " with an error log that is empty.<br><br>Googling this error, I can see it is probably something to do with authorisations but I can't figure out what is wrong exactly.<br><br>Have you ever encountered this error message? How did you finally
fix it?<br><br>Thanks a lot for your help.<br>Best regards,<br>Anthony<br><p>&#32;
<hr size="1">
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur <a href="http://fr.rd.yahoo.com/evt=42054/*http://fr.answers.yahoo.com">Yahoo! Questions/Réponses</a>.
--0-1347277098-1170331097=:27699--

[Magnus Hagander]

Post by anthony herve
Hello,
I am trying to install postgresql-8.2.1-1 on a VPS server (via Remote Desktop) with Windows Server 2003 (pack 1).

What VPS technology is being used?

Also, beware that there are known issues when installing from Terminal
Services. Most of them are not current anymore, but there seems to be at
least one problem still there. However, that usually shows a log.
Anyway, make sure you try to install it from the console session (using
mstsc /console and connecting to the RDP service)

Post by anthony herve
- installation language = english
- national language support, PL/java, Development files selected
- install a service option checked with postgres user
- initialise database cluster option checked with port 5432, accept connection on all adresses not just localhost option checked, locale English UK, encoding Latin1 and superuser postgres
- PL/pgsql, PL/perl, PL/python selected
- Adminpack selected as contrib module.
I execute the installation as Administrator (usergroup Administrators).
I get the error " Failed to run initdb: 128! " with an error log that is empty.

Unfortunatly, error 128 is a very "catch-all" like error :-(
What you should try is to install it without initdb:ing (just uncheck
the box), and then try to manually run the initdb command (don't forget
to set your locale and encoding). If that also fails, it shuld at least
be able to give you a better error message since it's not running under
the limited environment in the Windows Installer executor.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ***@postgresql.org so that your
message can get through to the mailing list cleanly