Re: BUG #12141: PostgreSQL cannot be started - Mailing list pgsql-bugs

From Preeti Karadi
Subject Re: BUG #12141: PostgreSQL cannot be started
Date
Msg-id OFEC0047FA.7BD68FAB-ON65257DA5.002243D4-65257DA5.002243D7@tcs.com
Whole thread Raw
In response to Re: BUG #12141: PostgreSQL cannot be started  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: BUG #12141: PostgreSQL cannot be started
List pgsql-bugs
Heikki,
The issue is only with Postgre Db and not the actuate. Even if we try to in=
stall the PostgreSQL 9.0 separately, then also  we are getting the error me=
ssage as "wsock32.dll is missing" . Could you please help us on resolving t=
his?

Thanks,
Preeti =



-----Heikki Linnakangas <hlinnakangas@vmware.com> wrote: ----- =

To: <preeti.karadi@tcs.com>, <pgsql-bugs@postgresql.org>
From: Heikki Linnakangas <hlinnakangas@vmware.com>
Date: 12/04/2014 07:14PM
Subject: Re: [BUGS] BUG #12141: PostgreSQL cannot be started


On 12/04/2014 12:51 PM, preeti.karadi@tcs.com wrote:
> The following bug has been logged on the website:
>
> Bug reference:      12141
> Logged by:          Preeti Madlur
> Email address:      preeti.karadi@tcs.com
> PostgreSQL version: 9.0.0
> Operating system:   Windows 2003
> Description:
>
> We are getting the error as "PostgreSQL cannot be started" during
> installation of Actuate 11 software on windows 2003 server which has bund=
led
> POstgreSQL 9.0. Please do the needful

This mailing list is for reporting bugs in PostgreSQL. This is almost =

not a bug in PostgreSQL, and there isn't anywhere near enough =

information here to debug it anyway. You'll have to contact the Actuate =

for support.

- Heikki
=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D
Notice: The information contained in this e-mail
message and/or attachments to it may contain =

confidential or privileged information. If you are =

not the intended recipient, any dissemination, use, =

review, distribution, printing or copying of the =

information contained in this e-mail message =

and/or attachments to it are strictly prohibited. If =

you have received this communication in error, =

please notify us by reply e-mail or telephone and =

immediately and permanently delete the message =

and any attachments. Thank you

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #11949: pg_basebackup creates defective tar file
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #12088: pg_upgrade 9.3 -> 9.4rc1 - implicit cast not ported