unexpected EOF on client connection connecting to PostGRE

I am attempting to connect an Access frontend to a PostgreSQL backend.  This process has been mostly painless with one exception so far.  On of the forms simply crashes when attempting to load.  There is of course no error produced by Access.  I have included a portion of the PostgreSQL log that I believe begins just before I attempt to open the form and concludes just after the error is returned.

I'm completely lost on this one.  Does anyone have a clue as to whats going wrong?

2006-07-11 17:12:30 DEBUG:  00000: forked new backend, pid=29675 socket=8
LOCATION:  BackendStartup, postmaster.c:2235
2006-07-11 17:12:30 LOG:  00000: statement: set DateStyle to 'ISO'
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: set geqo to 'OFF'
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: set extra_float_digits to 2
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: select oid, typbasetype from pg_type where typname = 'lo'
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: select pg_client_encoding()
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT Config, nValue FROM MSysConf
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 ERROR:  42P01: relation "msysconf" does not exist
LOCATION:  RangeVarGetRelid, namespace.c:193
2006-07-11 17:12:30 DEBUG:  00000: AbortCurrentTransaction
LOCATION:  PostgresMain, postgres.c:2722
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "public"."Content"."ID" FROM "public"."Content"
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "ID","RecordIDType","OtherID","DateCreated","DateModified","Collection Number","Title","Subtitle","ResourceType","Language1","Language2","Location","Abstract","TOC","ContentNotes"  FROM "public"."Content"  WHERE "ID" = 1
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "NameDetail"."ContentID","NameDetail"."Name" FROM "public"."NameDetail" "NameDetail" WHERE (("ContentID" =  1 ) AND ("ContentID" =  1 ) )
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "ContentID","Name","Role","RoleTerm"  FROM "public"."NameDetail"  WHERE "ContentID" = 1 AND "Name" = 38 OR "ContentID" = 1 AND "Name" = 37 OR "ContentID" = 1 AND "Name" = 37 OR "ContentID" = 1 AND "Name" = 37 OR "ContentID" = 1 AND "Name" = 37 OR "ContentID" = 1 AND "Name" = 37 OR "ContentID" = 1 AND "Name" = 37 OR "ContentID" = 1 AND "Name" = 37 OR "ContentID" = 1 AND "Name" = 37 OR "ContentID" = 1 AND "Name" = 37
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "ID" ,"Name"  FROM "public"."Name"
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "ID" ,"Name"  FROM "public"."Name" ORDER BY "public"."Name"."Name"
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "MS1"."ID" FROM "public"."SourceSound" "MS1" WHERE ( 1 = "Content#" )
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "ID","Form","ReelSize","DimensionNote","Disposition","Gauge","Generation","Length","SourceNote","SoundField","Speed","Stock","TapeThick","TrackFormat","RelatedItem","ItemLocation","Content#","Housing","ConservationHistory","SourceDate","PublicationDate","TransferEngineer"  FROM "public"."SourceSound"  WHERE "ID" = 32
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "MS1"."ContentID","MS1"."ConditionID" FROM "public"."ConditionDetail" "MS1" WHERE ("ContentID" =  32 )
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "ID","Form","ReelSize","DimensionNote","Disposition","Gauge","Generation","Length","SourceNote","SoundField","Speed","Stock","TapeThick","TrackFormat","RelatedItem","ItemLocation","Content#","Housing","ConservationHistory","SourceDate","PublicationDate","TransferEngineer"  FROM "public"."SourceSound"  WHERE "ID" = 32
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "ID" ,"Housing description Film"  FROM "public"."Housing" WHERE ("Housing description Film" LIKE '%sound%' ) ORDER BY "public"."Housing"."Housing description Film"
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "TechSound Subform"."ID" FROM "public"."TechSound" "TechSound Subform" WHERE ( 1 = "Content#" )
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:30 LOG:  00000: statement: SELECT "ID","Content#","FormatName","ByteOrder","CompressionScheme","FileSize","CodecCreator","CodecQuality","Methodology","BitsPerSample","SamplingFrequency","SoundNote","Duration","SoundClip","DateCaptured","FileLoc"  FROM "public"."TechSound"  WHERE "ID" = 282
LOCATION:  pg_parse_query, postgres.c:464
2006-07-11 17:12:31 LOG:  08006: could not receive data from client: Connection reset by peer
LOCATION:  pq_recvbuf, pqcomm.c:678
2006-07-11 17:12:31 LOG:  08P01: unexpected EOF on client connection
LOCATION:  SocketBackend, postgres.c:281
2006-07-11 17:12:31 DEBUG:  00000: child process (PID 29675) exited with exit code 0
LOCATION:  LogChildExit, postmaster.c:2078
whitej8Asked:
Who is Participating?
 
NetminderConnect With a Mentor Commented:
Closed, 500 points refunded.
Netminder
Site Admin
0
 
rockiroadsCommented:
its saying

msysconf  does not exist


when u issue

SELECT Config, nValue FROM MSysConf

its falling on that, as MSysConf does not exist
0
 
rockiroadsCommented:
well that could be one part of the total problem !
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
rockiroadsCommented:
the last sql is this

statement: SELECT "ID","Content#","FormatName","ByteOrder","CompressionScheme","FileSize","CodecCreator","CodecQuality","Methodology","BitsPerSample","SamplingFrequency","SoundNote","Duration","SoundClip","DateCaptured","FileLoc"  FROM "public"."TechSound"  WHERE "ID" = 282


Have u tried to run this SQL outside Access and in Postgress? How long does it take to run


When u run this in Access, does it take a while to respond? looking at your logs, it returns with a message 1 minute later

could your timeout setting be set to 60 seconds somewhere?

Have u tried increasing your timeout setting
0
 
rockiroadsCommented:
Are you using ODBC? Is there a connection timeout settng there?
Access has a timeout also Tools/Options/Advanced
0
 
whitej8Author Commented:
I am using PGSQL ODBC version 8.02.  There are many forms in this MDB and the others can access the PostGRE tables without problem.  I did execute the last SQL statement in PostGRE and it completes with data in about 600 ms.  The access form fails instantly so I doubt it is a timeout issue.
0
 
whitej8Author Commented:
I've posted this question to the PostGRE section as well so a correct answer is worth 1000 pts.
0
 
rockiroadsCommented:
Ive been trying to find a solution but cant find much on it

can u try simplify the query, perhaps its something to do with that?

e.g.

SELECT "ID", "FormatName"  FROM "public"."TechSound"  WHERE "ID" = 282

How does Postgres handle column names like Content#

0
 
rockiroadsCommented:
Is it also worth correcting the one failure u get earlier, perhaps that is impacting the result somehow
0
 
whitej8Author Commented:
After some very tedious exhaustive testing I was able to isolate the error to an OLE object field from the original database.  OLE objects are MS specific and are not supported by postGRE, removing this field has stopped the crashing problem.  In order to maintain the functionality I will replace the OLE object with a filesystem pointer.
0
 
rockiroadsCommented:
Good find, sorry I couldnt be much help. Niot having Postges is somewhat of a stumbling block!

I suggest close, no delete as this info is useful
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.