Re: BUG #12141: PostgreSQL cannot be started

From: Preeti Karadi <preeti(dot)karadi(at)tcs(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #12141: PostgreSQL cannot be started
Date: 2014-12-05 06:14:15
Message-ID: OFEC0047FA.7BD68FAB-ON65257DA5.002243D4-65257DA5.002243D7@tcs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Heikki,
The issue is only with Postgre Db and not the actuate. Even if we try to install the PostgreSQL 9.0 separately, then also we are getting the error message as "wsock32.dll is missing" . Could you please help us on resolving this?

Thanks,
Preeti

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

On 12/04/2014 12:51 PM, preeti(dot)karadi(at)tcs(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 12141
> Logged by: Preeti Madlur
> Email address: preeti(dot)karadi(at)tcs(dot)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 bundled
> 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
=====-----=====-----=====
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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2014-12-05 11:56:43 Re: BUG #11949: pg_basebackup creates defective tar file
Previous Message Tom Lane 2014-12-05 02:29:27 Re: BUG #12146: Crash when using UNION ALL