Re: Unable to connect to PostgreSQL 8.0 with any driver...

Lists: pgsql-odbc
From: jross(at)wykids(dot)org
To: pgsql-odbc(at)postgresql(dot)org
Subject: Unable to connect to PostgreSQL 8.0 with any driver...
Date: 2005-03-07 18:17:23
Message-ID: 20050307111723.esskxw68g0wc4oow@wykids.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-odbc

Hi,

This is a continuation of my problems with the original 08.00.0100 driver.
08.00.1001 now installs correctly and the driver is available to be configured
in the ODBC control panel.

However, I still cannot connect to Access with it. My PostgreSQL logs do not
even show a connection attempt. The logs on the windows box are:

mylog:

[184]globals.extra_systable_prefixes = 'dd_;'
[184]globals.extra_systable_prefixes = 'dd_;'
[184]IDOK: got ci = 686496
[184]globals.extra_systable_prefixes = 'dd_;'
[184]globals.extra_systable_prefixes = 'dd_;'
[184]IDOK: got ci = 703904

pgsqlodbc:

DSN info: DSN='PostgreSQL',server='',port='',dbase='',user='',passwd='xxxxx'
onlyread='',protocol='',showoid='',fakeoidindex='',showsystable=''
conn_settings='',conn_encoding='OTHER'
translation_dll='',translation_option=''
DSN info: DSN='PostgreSQL',server='',port='',dbase='',user='',passwd='xxxxx'
onlyread='',protocol='',showoid='',fakeoidindex='',showsystable=''
conn_settings='',conn_encoding='OTHER'
translation_dll='',translation_option=''

The logs from a different computer that successfully logs into the database are
way more voluminous than this. I'll put them up on our web site if someone
needs to see what's going on with a successful connection.

I'd appreciate any ideas.

Thanks,

Jeff Ross


From: Richard Huxton <dev(at)archonet(dot)com>
To: jross(at)wykids(dot)org
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Unable to connect to PostgreSQL 8.0 with any driver...
Date: 2005-03-08 12:25:11
Message-ID: 422D99A7.1070704@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-odbc

jross(at)wykids(dot)org wrote:
> Hi,
>
> This is a continuation of my problems with the original 08.00.0100 driver.
> 08.00.1001 now installs correctly and the driver is available to be configured
> in the ODBC control panel.
>
> However, I still cannot connect to Access with it. My PostgreSQL logs do not
> even show a connection attempt. The logs on the windows box are:
[snip]
> DSN info: DSN='PostgreSQL',server='',port='',dbase='',user='',passwd='xxxxx'
Well, you've not got a server filled in here, so it's not going to
connect. Can you think why it would be blank - what's different between
the two machines?

--
Richard Huxton
Archonet Ltd


From: jross(at)wykids(dot)org
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Unable to connect to PostgreSQL 8.0 with any driver...
Date: 2005-03-08 15:16:32
Message-ID: 20050308081632.mlu5dpetc4osogwk@wykids.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-odbc

Quoting Richard Huxton <dev(at)archonet(dot)com>:

> jross(at)wykids(dot)org wrote:
>> Hi,
>>
>> This is a continuation of my problems with the original 08.00.0100
>> driver. 08.00.1001 now installs correctly and the driver is
>> available to be configured
>> in the ODBC control panel.
>>
>> However, I still cannot connect to Access with it. My PostgreSQL
>> logs do not
>> even show a connection attempt. The logs on the windows box are:
> [snip]
>> DSN info: DSN='PostgreSQL',server='',port='',dbase='',user='',passwd='xxxxx'
> Well, you've not got a server filled in here, so it's not going to
> connect. Can you think why it would be blank - what's different between
> the two machines?
>
> --
> Richard Huxton
> Archonet Ltd
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>
> !DSPAM:422d9cc5179771587154166!
>
>

I ended up uninstalling yet again and running a registry cleaner, followed by
manually removing anything from the registry that had "psqlodbc" in it.
Reinstalled the 07_03_00 driver and I can now connect again.

So, problem solved.

Thanks for the input!

Jeff Ross