Обсуждение: Known bugs in OBDC?
Has anyone experienced problems with ODBC driver on NT4? My database server died today, and when it came back up all IIS could get out of the ODBC driver was: Microsoft OLE DB Provider for ODBC Drivers error '80004005' Could not send Query to backend; Could not send Query to backend; Socket has been closed pgAdmin II connects fine with no complaints from the same box, it just seems to be the ODBC connections that are failing big time. Yours Unwhettedly, Robert John Shepherd. Editor DVD REVIEWER The UK's BIGGEST Online DVD Magazine http://www.dvd.reviewer.co.uk For a copy of my Public PGP key, email: pgp@robertsworld.org.uk
> -----Original Message----- > From: Robert John Shepherd [mailto:robert@reviewer.co.uk] > Sent: 03 November 2002 22:35 > To: pgsql-odbc@postgresql.org > Subject: [ODBC] Known bugs in OBDC? > > > Has anyone experienced problems with ODBC driver on NT4? > > My database server died today, and when it came back up all > IIS could get out of the ODBC driver was: > > Microsoft OLE DB Provider for ODBC Drivers error '80004005' > Could not send Query to backend; Could not send Query to > backend; Socket has been closed > > pgAdmin II connects fine with no complaints from the same > box, it just seems to be the ODBC connections that are > failing big time. Hi, What are you trying to do through IIS? pgAdmin uses the ODBC for all it's connections, so I'd guess for the most part the driver installation is fine. Regards, Dave.
Robert John Shepherd wrote:
>
> Has anyone experienced problems with ODBC driver on NT4?
>
> My database server died today, and when it came back up all
> IIS could get out of the ODBC driver was:
>
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> Could not send Query to backend; Could not send Query to backend;
> Socket has been closed
Connection pooling could be the cause.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
> What are you trying to do through IIS? pgAdmin uses the ODBC for all > it's connections, so I'd guess for the most part the driver installation > is fine. My website uses IIS to connect to Postgresql, having migrated to this from MS-SQL 7 (which I had never seen this problem with). Whilst I'm happy to accept there may be issues between IIS and the pgsql ODBC driver that have caused this, I'm convinced this has nothing to do with my postgresql installation having whacked up the debug levels and logging to the max on the install and watched the logfiles during this problem. Yours Unwhettedly, Robert John Shepherd. Editor DVD REVIEWER The UK's BIGGEST Online DVD Magazine http://www.dvd.reviewer.co.uk For a copy of my Public PGP key, email: pgp@robertsworld.org.uk
> Connection pooling could be the cause. I thought that the ODBC driver currently didn't support connection pooling? Or is this a case of IIS performing the pooling? Yours Unwhettedly, Robert John Shepherd. Editor DVD REVIEWER The UK's BIGGEST Online DVD Magazine http://www.dvd.reviewer.co.uk For a copy of my Public PGP key, email: pgp@robertsworld.org.uk
> -----Original Message----- > From: Robert John Shepherd [mailto:robert@reviewer.co.uk] > Sent: 04 November 2002 11:31 > To: Dave Page; pgsql-odbc@postgresql.org > Subject: RE: [ODBC] Known bugs in OBDC? > > > > What are you trying to do through IIS? pgAdmin uses the > ODBC for all > > it's connections, so I'd guess for the most part the driver > installation > > is fine. > > My website uses IIS to connect to Postgresql, having migrated > to this from MS-SQL 7 (which I had never seen this problem with). > > Whilst I'm happy to accept there may be issues between IIS > and the pgsql ODBC driver that have caused this, I'm > convinced this has nothing to do with my postgresql > installation having whacked up the debug levels and logging > to the max on the install and watched the logfiles during > this problem. I agree, it's probably not you installation. Did you see Hiroshi's message about pooling? Can you tell IIS not to do it? Regards, Dave.
> I agree, it's probably not you installation. Did you see Hiroshi's > message about pooling? Can you tell IIS not to do it? Are there any implications for the server in telling IIS not to pool connections? Is it going to suddenly spawn more postgresql processes than the box can handle? :) Yours Unwhettedly, Robert John Shepherd. Editor DVD REVIEWER The UK's BIGGEST Online DVD Magazine http://www.dvd.reviewer.co.uk For a copy of my Public PGP key, email: pgp@robertsworld.org.uk
> -----Original Message----- > From: Robert John Shepherd [mailto:robert@reviewer.co.uk] > Sent: 04 November 2002 11:43 > To: Dave Page; pgsql-odbc@postgresql.org > Subject: RE: [ODBC] Known bugs in OBDC? > > > > I agree, it's probably not you installation. Did you see Hiroshi's > > message about pooling? Can you tell IIS not to do it? > > Are there any implications for the server in telling IIS not > to pool connections? Is it going to suddenly spawn more > postgresql processes than the box can handle? :) I wouldn't have thought so, but that is somewhat outside my area of (ahem) expertise. I try to avoid IIS whereever possible. Regards, Dave.
> -----Original Message----- > From: Robert John Shepherd [mailto:robert@reviewer.co.uk] > > > Connection pooling could be the cause. > > I thought that the ODBC driver currently didn't support connection > pooling? > > Or is this a case of IIS performing the pooling? Maybe yes. I've just put an improved version of dll on my home page http://w2422.nsk.ne.jp/~inoue/ . Please try the dll. regards, Hiroshi Inoue