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

Basic ODBC Connect Problem

From: "Stuart" <stuart(at)theallisons(dot)freeserve(dot)co(dot)uk>
To: <pgsql-odbc(at)postgresql(dot)org>
Subject: Basic ODBC Connect Problem
Date: 2002-01-06 16:27:36
Message-ID: 003a01c196cf$0f4bb120$7d7a7d7a@saahome (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc

Apologies for a rather basic query:

Having stripped out my old SuSE 6.2 and replaced this with SuSE 7.3 (note everything was reformatted), I now cannot connect to my newly created database via ODBC from Paradox.

ODBC version: 07_01_0008
PostgreSQL version 7.1.3 (as installed from SuSE 7.3)

Windows psqlodbc log file shows:

Global Options: Version='07.01.0008', fetch=1, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=8190

disable_optimizer=1, ksqo=1, unique_index=1, use_declarefetch=0

text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1

extra_systable_prefixes='dd_;', conn_settings='' conn_encoding='OTHER'

CONN ERROR: func=PGAPI_DriverConnect, desc='Error from CC_Connect', errnum=101, errmsg='Could not connect to the server'


henv=92802928, conn=91701824, status=0, num_stmts=16

sock=92802880, stmts=92802800, lobj_type=-999

---------------- Socket Info -------------------------------

socket=-1, reverse=0, errornumber=4, errormsg='Could not connect to remote socket.'

buffer_in=91712708, buffer_out=91716808

buffer_filled_in=0, buffer_filled_out=0, buffer_read_in=0

How can I check the remote socket? The postmaster has been started with the '-i' option. 
Is/will there be a PAM issue here as well, which is/will reject the connection? I haven't figured out PAM yet and can't ftp or telnet (at least in SuSE 6.2 I got telnet to work!)

Thanks for ANY help on this rather basic issue.


pgsql-odbc by date

Next:From: Hannu KrosingDate: 2002-01-06 22:32:40
Subject: Re: LWLock contention: I think I understand the problem
Previous:From: Ashley CambrellDate: 2002-01-06 12:01:44
Subject: Re: LWLock contention: I think I understand the problem

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