Thread: Can't connect to PostgreSQL 7.3 beta2

Can't connect to PostgreSQL 7.3 beta2

From
"Poul L. Christiansen"
Date:
Hi

I can't connect to PostgreSQL 7.3 beta2 (also tried beta1) using
PgAdminII alpha v1.3 build 76.

Error message from PgAdminII:
"26-09-2002 10:58:18 - Error in pgAdmin II:frmConnect.cmdConnect_Click:
-2147467259 - blank"
The description just says "blank", so I clueless :(

But PostgreSQL lgo says:
LOG:  statement: set ksqo to 'ON'
ERROR:  'ksqo' is not a valid option name

I got the same error message when I used the ODBC driver. The solution
was to turn off "ksqo" and then ODBC worked perfectly. But PgAdminII
isn't :(

Poul L. Christiansen
Dynamic Paper



Re: Can't connect to PostgreSQL 7.3 beta2

From
"Dave Page"
Date:
Hi Poul,

It sounds like an old version of the ODBC has overwritten the one that
came with pgAdmin. What version of psqlodbc.dll is on your system?

Regards, Dave.

> -----Original Message-----
> From: Poul L. Christiansen [mailto:poulc@cs.auc.dk]
> Sent: 26 September 2002 12:11
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] Can't connect to PostgreSQL 7.3 beta2
>
>
> Hi
>
> I can't connect to PostgreSQL 7.3 beta2 (also tried beta1)
> using PgAdminII alpha v1.3 build 76.
>
> Error message from PgAdminII:
> "26-09-2002 10:58:18 - Error in pgAdmin
> II:frmConnect.cmdConnect_Click: -2147467259 - blank" The
> description just says "blank", so I clueless :(
>
> But PostgreSQL lgo says:
> LOG:  statement: set ksqo to 'ON'
> ERROR:  'ksqo' is not a valid option name
>
> I got the same error message when I used the ODBC driver. The
> solution was to turn off "ksqo" and then ODBC worked
> perfectly. But PgAdminII isn't :(
>
> Poul L. Christiansen
> Dynamic Paper
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
>

Re: Can't connect to PostgreSQL 7.3 beta2

From
"Poul L. Christiansen"
Date:
My psqlodbc.dll is version 07.02.0001

After updating to version 07.02.0002 I can connect :)

Maybe the explaination "blank" should be altered to "Update your ODBC
driver".

Thanks,
Poul L. Christiansen
Dynamic Paper

Dave Page wrote:

>Hi Poul,
>
>It sounds like an old version of the ODBC has overwritten the one that
>came with pgAdmin. What version of psqlodbc.dll is on your system?
>
>Regards, Dave.
>
>
>
>>-----Original Message-----
>>From: Poul L. Christiansen [mailto:poulc@cs.auc.dk]
>>Sent: 26 September 2002 12:11
>>To: pgadmin-hackers@postgresql.org
>>Subject: [pgadmin-hackers] Can't connect to PostgreSQL 7.3 beta2
>>
>>
>>Hi
>>
>>I can't connect to PostgreSQL 7.3 beta2 (also tried beta1)
>>using PgAdminII alpha v1.3 build 76.
>>
>>Error message from PgAdminII:
>>"26-09-2002 10:58:18 - Error in pgAdmin
>>II:frmConnect.cmdConnect_Click: -2147467259 - blank" The
>>description just says "blank", so I clueless :(
>>
>>But PostgreSQL lgo says:
>>LOG:  statement: set ksqo to 'ON'
>>ERROR:  'ksqo' is not a valid option name
>>
>>I got the same error message when I used the ODBC driver. The
>>solution was to turn off "ksqo" and then ODBC worked
>>perfectly. But PgAdminII isn't :(
>>
>>Poul L. Christiansen
>>Dynamic Paper
>>
>>
>>
>>---------------------------(end of
>>broadcast)---------------------------
>>TIP 2: you can get off all lists at once with the unregister command
>>    (send "unregister YourEmailAddressHere" to
>>majordomo@postgresql.org)
>>
>>
>>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://archives.postgresql.org
>
>




Re: Can't connect to PostgreSQL 7.3 beta2

From
"Dave Page"
Date:

> -----Original Message-----
> From: Poul L. Christiansen [mailto:poulc@cs.auc.dk]
> Sent: 26 September 2002 14:56
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] Can't connect to PostgreSQL 7.3 beta2
>
>
> My psqlodbc.dll is version 07.02.0001
>
> After updating to version 07.02.0002 I can connect :)
>
> Maybe the explaination "blank" should be altered to "Update your ODBC
> driver".

:-) Not really possible 'cos the blank error comes from old driver which
gets confused when ksqo cannot be set.

Regards, Dave