BUG #4503: failed to run initdb: 1! - Mailing list pgsql-bugs

From Stephen
Subject BUG #4503: failed to run initdb: 1!
Date
Msg-id 200810291813.m9TIDqsb037127@wwwmaster.postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged online:

Bug reference:      4503
Logged by:          Stephen
Email address:      oconnor1986@gmail.com
PostgreSQL version: 8.3.4
Operating system:   Vista Home Premium
Description:        failed to run initdb: 1!
Details:

I get the error: failed to run initdb: 1! in the windows installer.

When checking the log file it has the following:
The application has failed to start because its side-by-side configuration
is incorrect.

A detailed log file gives:
Action 18:00:30: RunInitdb. Initializing database cluster (this may take a
minute or two)...
MSI (s) (9C:3C) [18:00:30:603]: Executing op:
CustomActionSchedule(Action=RunInitdb,ActionType=3073,Source=BinaryData,Targ
et=_RunInitdb@4,CustomActionData=1033;C:\Program
Files\PostgreSQL\8.3\;C:\Program Files\PostgreSQL\8.3\data\;C:\Program
Files\PostgreSQL\8.3\share\;5432;;English_United
Kingdom;WIN1252;postgres;stephenoc;STEPHEN-PC;postgres;stephenoc;;)
MSI (s) (9C:34) [18:00:30:618]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSI81D0.tmp, Entrypoint: _RunInitdb@4
MSI (c) (34:5C) [18:00:31:975]: Note: 1: 2205 2:  3: Error
MSI (c) (34:5C) [18:00:31:975]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2835
DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDlg
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2835. The
arguments are: ErrorIcon, ErrorDlg,


It's a fresh install of vista, and have tried installing the Microsoft C++
Redistrib package but no use. Any help is appreciated.

pgsql-bugs by date:

Previous
From: "Dave Page"
Date:
Subject: Re: BUG #4502: pgAdmin Display Refresh Rate cannot be less that 7 secs
Next
From: Joe
Date:
Subject: Bug #3924: Create Database with another encoding as the encoding from postgres