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

Re: ODBC connection stopped working.

From: Cedar Cox <cedarc(at)visionforisrael(dot)com>
To: Neal Lindsay <neal(dot)lindsay(at)peaofohio(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: ODBC connection stopped working.
Date: 2001-08-21 21:38:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Logic would say, if you haven't changed anything then there's know reason
why the behavior should change.  I don't know why PG would be rejecting
connections as the superuser, other than if you (ie, Access) is not
actually connecting as the superuser.  It looks like you're running PG
7.1.x.. try enabling connection logging, just to make sure.  As for
MSysConf, that is something Access looks for to control things like
background population and password caching.  Notice that Access only looks
for it once per connection.  Have a look in Access help, I think the table
definition and record meanings are in there.  Also, you should read this


On Tue, 21 Aug 2001, Neal Lindsay wrote:

> I have a small (but growing) postgresql database that employees in the 
> office connect to with Access97.  I built the client application in Access 
> and distributed it, and it has been running perfectly for the past two 
> weeks or so.  The ODBC connection is set up to connect as the superuser 
> (postgres) with no password (and I have not added a password) (yeah, 
> insecure, but I'm working on a bigger database to replace it that will have 
> good security, and I'm on an internal network anyway).  Anyhow, some time 
> this morning, the datbase started rejecting connections from the clients, 
> saying "ERROR:  (tablename): Permission denied."  If I re-link the tables, 
> sometimes it will go back to working until I close the datbase and open it 
> again.  Here is a snippet from my log:
> 010821.10:55:15.935   [898] ERROR:  Relation 'msysconf' does not exist
> 010821.10:55:15.966   [898] ERROR:  client: Permission denied.
> 010821.10:58:01.806   [899] ERROR:  Relation 'msysconf' does not exist
> 010821.10:58:01.812   [899] ERROR:  client: Permission denied.
> 010821.10:58:28.961   [899] ERROR:  workorder: Permission denied.
> 010821.11:03:08.287   [936] ERROR:  Relation 'msysconf' does not exist
> 010821.11:03:20.907   [937] ERROR:  Relation 'msysconf' does not exist
> 010821.11:03:20.938   [937] ERROR:  employee: Permission denied.
> 010821.11:03:36.038   [939] ERROR:  Relation 'msysconf' does not exist
> If I re-link the tables, sometimes only some of the tables will start 
> working again.  The ones that still do not work no longer produce the 
> 'msysconf' lines in the log, but they do still give the 'Permission denied" 
> ones.
> Does anyone know what the 'msysconf' errors are, or why the database would 
> be denying me connections as the superuser?  Please help!
> Neal Lindsay
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?

In response to

pgsql-odbc by date

Next:From: Neal LindsayDate: 2001-08-22 01:30:08
Subject: Re: ODBC connection stopped working.
Previous:From: Johann ZuschlagDate: 2001-08-21 17:44:11
Subject: Re: New CVS doesn't compile

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