Skip site navigation (1) Skip section navigation (2)

Re: Crystal Reports: Connection rejected: FATAL: no

From: "Prasanth" <dbadmin(at)nqadmin(dot)com>
To: "Rover, Mischa de" <mischa(dot)de(dot)rover(at)capgemini(dot)com>,"Oliver Jowett" <oliver(at)opencloud(dot)com>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Crystal Reports: Connection rejected: FATAL: no
Date: 2005-03-11 21:21:41
Message-ID: LGEKIACNKCMPMALCJMLOOEOAEBAA.dbadmin@nqadmin.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
>Logon Error: The server requested password-based authentication, but no
>password was provided.

In your code are you setting the ConnectionInfos object?
I am assuming that you are using the JRC.

-Prasanth.

-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org]On Behalf Of Rover, Mischa de
Sent: Friday, March 11, 2005 7:21 AM
To: Oliver Jowett
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Crystal Reports: Connection rejected: FATAL: no



> This means that you are passing no user information when trying to
make
> a connection (JDBC does not default to any particular user). It's a
bit
> weird that it works against 7.3, though. If you specify
> "?protocolVersion=2" in the connection URL against an 8.0 server, does

> it work?

I tried this but getting a different error message:

Logon Error: A connection could not be made using the requested protocol
2;DatabaseName=lir_nvog;user=dba;password=pw.

> Is Crystal Reports the one that eats all the stack traces? It'd be
> useful to know the call path that generated this exception.

Caused by: org.postgresql.util.PSQLException: A connection could not be
made using the requested protocol
2;DatabaseName=lir_nvog;user=dba;password=pw.
        at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.j
ava:70)
        at
org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connect
ion.java:117)
        at
org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connect
ion.java:30)
        at
org.postgresql.jdbc3.Jdbc3Connection.<init>(Jdbc3Connection.java:24)
        at org.postgresql.Driver.connect(Driver.java:235)
        ... 77 more

> You have a few of choices as to how to pass in the user info:
>
> - pass it to DriverManager.getConnection(url, user, password)
> - pass a "user" property when calling DriverManager.getConnection(url,

> properties)

This is done by CR at runtime

> - pass it in the URL:
jdbc:postgresql://host:port/database?user=username
> I'm not familiar with Crystal Reports so I don't know how you'd
> configure it to use one of these approaches. Does it let you tweak the

> connection URL directly?

The url is saved in *.rpt file. I can save the url into the rpt file in
designer mode. At runtime I get a different error message:

Logon Error: The server requested password-based authentication, but no
password was provided.

Using this url:
jdbc:postgresql://server/lir_nvog?protocolVersion=2&user=dba&password=pw

Returns following error:
Logon Error: Connection rejected: FATAL:  Password authentication failed
for user "dba"



Regards,

Mischa

-----Original Message-----
From: Oliver Jowett [mailto:oliver(at)opencloud(dot)com]
Sent: Wednesday, March 09, 2005 10:23 PM
To: Rover, Mischa de
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Crystal Reports: Connection rejected: FATAL: no
PostgreSQLuser name specified in startup packet.

Rover, Mischa de wrote:

> ERROR [datainterface]
> com.crystaldecisions.reports.reportdefinition.datainterface.h: Logon
> Error: Connection rejected: FATAL:  no PostgreSQL user name specified
in
> startup packet

This means that you are passing no user information when trying to make
a connection (JDBC does not default to any particular user). It's a bit
weird that it works against 7.3, though. If you specify
"?protocolVersion=2" in the connection URL against an 8.0 server, does
it work?

Is Crystal Reports the one that eats all the stack traces? It'd be
useful to know the call path that generated this exception.

You have a few of choices as to how to pass in the user info:

- pass it to DriverManager.getConnection(url, user, password)
- pass a "user" property when calling DriverManager.getConnection(url,
properties)
- pass it in the URL: jdbc:postgresql://host:port/database?user=username

I'm not familiar with Crystal Reports so I don't know how you'd
configure it to use one of these approaches. Does it let you tweak the
connection URL directly?

> This message contains information that may be privileged or
confidential
> and is the property of the Capgemini Group. It is intended only for
the
> person to whom it is addressed. If you are not the intended recipient,

> you are not authorized to read, print, retain, copy, disseminate,
> distribute, or use this message or any part thereof. If you receive
this
> message in error, please notify the sender immediately and delete all
> copies of this message.

You are sending this message to a public list, so the boilerplate is
pointless. (and anyway, what does "RCPT TO" mean if not "intended
recipient"?)

-O

This message contains information that may be privileged or confidential and
is the property of the Capgemini Group. It is intended only for the person
to whom it is addressed. If you are not the intended recipient,  you are not
authorized to read, print, retain, copy, disseminate,  distribute, or use
this message or any part thereof. If you receive this  message in error,
please notify the sender immediately and delete all  copies of this message.


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
      message can get through to the mailing list cleanly





In response to

pgsql-jdbc by date

Next:From: Rover, Mischa deDate: 2005-03-11 21:36:46
Subject: Re: Crystal Reports: Connection rejected: FATAL: no
Previous:From: Oliver JowettDate: 2005-03-11 21:13:37
Subject: Re: [BUGS] BUG #1523: precision column value returned from

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group