Question concerning failed installation of Postgres 8.2.3 on Windows XP

From: Sven Janson <janson(at)spheron(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Question concerning failed installation of Postgres 8.2.3 on Windows XP
Date: 2007-05-10 15:58:38
Message-ID: 4643412E.9060703@spheron.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear mailing list,

I have got a problem installing Postgres 8.2.3 on Windows XP Pro having
all the latest updates.
All postgres installations, folders and the serviceaccount have been
removed before so that it was clean installation.

The following steps lead to a reproducible result on a few machines but
not on all:

I chose English as installer language and deselected all database
drivers (JDBC, NPSQL, ...) for installation.
Then I just clicked "Next" in the following installer pages leaving all
options as is. I entered passwords for both the superuser and the
serviceaccount.
I selected German (Germany) as locale and UTF8 as encoding.

Near the end of the installation a message box appears reporting the
following error:
"Failed to connect to the database. Procedural languages files are
installed, but are not activated in any databases."

These are the critical lines written by msiexec in its log file when
encountering the error:
<--------------------------------------------

MSI (s) (C0:E0) [15:17:00:531]: Executing op:
ActionStart(Name=InstallPl,Description=Activating procedural languages...,)
Action 15:17:00: InstallPl. Activating procedural languages...
MSI (s) (C0:E0) [15:17:00:531]: Executing op:
CustomActionSchedule(Action=InstallPl,ActionType=1025,Source=BinaryData,Target=InstallPl(at)4,CustomActionData=1033;postgres;kdsahp;5432;C:\Programme\PostgreSQL\8.2\share\;1;;;;;;;)
MSI (s) (C0:48) [15:17:00:593]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI77.tmp, Entrypoint: InstallPl(at)4
MSI (c) (D8:DC) [15:17:15:095]: Note: 1: 2205 2: 3: Error
MSI (c) (D8:DC) [15:17:15:095]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2867
DEBUG: Error 2867: The error dialog property is not set
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2867. The arguments are: , ,
MSI (c) (D8:DC) [15:17:15:095]: Font created. Charset: Req=0, Ret=0,
Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (D8:DC) [15:18:24:198]: Note: 1: 2205 2: 3: Error
MSI (c) (D8:DC) [15:18:24:214]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2888
DEBUG: Error 2888: Executing the TextStyle view failed
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2888. The arguments are: TextStyle, ,
MSI (c) (D8:DC) [15:18:38:028]: Note: 1: 2205 2: 3: Error
MSI (c) (D8:DC) [15:18:38:028]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2888
DEBUG: Error 2888: Executing the TextStyle view failed
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2888. The arguments are: TextStyle, ,
MSI (c) (D8:DC) [15:18:51:531]: Note: 1: 2205 2: 3: Error
MSI (c) (D8:DC) [15:18:51:531]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2888
DEBUG: Error 2888: Executing the TextStyle view failed
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2888. The arguments are: TextStyle, ,
MSI (c) (D8:DC) [15:21:42:346]: Note: 1: 2205 2: 3: Error
MSI (c) (D8:DC) [15:21:42:346]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 2888
DEBUG: Error 2888: Executing the TextStyle view failed
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2888. The arguments are: TextStyle, ,
Failed to connect to the database. Procedural languages files are
installed, but are not activated in any databases.

-------------------------------------------------->

Could you please tell me how to work around or avoid this error? Thank
you very much in advance for your help!

Best regards, Sven

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-05-10 17:33:28 Re: Seq scans roadmap
Previous Message Dave Page 2007-05-10 15:56:10 Re: Windows Vista support (Buildfarm Vaquita)