Обсуждение: BUG #5572: Error Trying to connec from Crystal Reports to Sever PostgreSQL

The following bug has been logged online:

Bug reference:      5572
Logged by:          Tizziano Perea
Email address:      tizzianop@gmail.com
PostgreSQL version: 8.2.17
Operating system:   CentOS 5.4
Description:        Error Trying to connec from Crystal Reports to Sever
PostgreSQL
Details:

Regards,

Hi, i'm a System Engenieer from Clinica Vida - Cali, Colombia.
I,ve been install Crystal Reports 11 in a WinXP machine, and when i tried to
connect to PostgreSQL (CentOS 5.4) the following error appears:

La conexion no es posible
Detalles: 08001: Could not connect to the server
Could not connect to remote socket: [Codigo de proveedor de Base de Datos:
101]

I edited the pg.hba.conf and postgres.conf files, but the error persist.

Thanks for your attention and your help

Bye.

"Tizziano Perea" <tizzianop@gmail.com> wrote:

> PostgreSQL version: 8.2.17
> Operating system:   CentOS 5.4
> Description:        Error Trying to connec from Crystal Reports to
>                     Sever

> I,ve been install Crystal Reports 11 in a WinXP machine, and when
> i tried to connect to PostgreSQL (CentOS 5.4) the following error
> appears:
>
> La conexion no es posible
> Detalles: 08001: Could not connect to the server
> Could not connect to remote socket: [Codigo de proveedor de Base
> de Datos: 101]
>
> I edited the pg.hba.conf and postgres.conf files, but the error
> persist.

In the future it would be better to post such problems to the
pgsql-general list, as this doesn't really sound like a bug in
PostgreSQL; it sounds like you don't have everything configured
correctly.

Without seeing the changes you made to the .conf files and knowing
how Crystal Reports is trying to connect, it's hard to guess what
the problem may be.  Please post the contents of the postgresql.conf
and pg_hba.conf files with all comments removed.  Also, please give
any information you can about how Crystal Reports is trying to
connect.

Also something to consider: did you do the appropriate reload or
restart to get PostgreSQL to notice the changes after you edited the
.conf files?

-Kevin