Re: Client SDK - Oledb - ADO.Net Multi-Threaded App Problems - VS.Net 2003

I apologize if my question was a little cryptic. I am referring to the coledbp.sql script that is located in the 'etc' directory of the 2.81 CSDK. You must run this against the sysmaster database of whatever instance you plan on creating an OLE DB connection too. To find you current version of this OLE DB setup: SELECT oledbver FROM sysmaster:oledbversion; If this isn't 3 you need to run the doledbp.sql file against sysmaster to drop any existing OLE DB setup then run the coledbp.sql file against sysmaster. There are upgrade scripts as well but they won't work. --- Gregg Walker <gregorioandador@msn.com> wrote: > Thanks for your reply. > > How are you getting the oledb driver version? > > I was looking at the ifxoledbc.dll file and the > version it show after I > install CSDK 2.81 is 2.81.0.11499. You mentioned > you had a version 3.0 > driver. Where did you get it from? > > Also does anyone else have any input on this thread? > > Thanks again. > > Gregg Walker > > "DL Redden" <redden96@yahoo.com> wrote in message > news:bb00u3$aea$1@terabinaries.xmission.com... > > > > Are you sure you are running the latest oledb > version. > > I had problems that stemmed from using a 2.5 > oldedb > > driver with the 2.81 CSDK. Once I moved to the 3.0 > > driver all was well. I am running VS.NET 2002 we > have > > a few developers using VS.NET 2003 I will see if > they > > have had similar problems. > > > > > > --- Gregg Walker <gregg@rrmca.com> wrote: > > > Hi All, > > > > > > I'm trying to move my VS.Net 2002 applications > to > > > VS.Net 2003 and haven't > > > been able to find a version of CSDK that will > work. > > > > > > My Environment: > > > > > > Informix Server: IDS 9.30.UC2 on AIX > > > Client SDK Version: 2.70.TC3 and 2.81.TC1 > > > > > > I've been having some problems with a multi > threaded > > > C# application that > > > uses ADO.Net to access the informix server. > > > > > > Here's the scenarios. > > > > > > 1) CSDK 2.70.TC3 with VS.Net 2002 .Net Framework > 1.0 > > > > > > In this scenario my application works fine. No > > > errors. > > > > > > 2) CSDK 2.70.TC3 with VS.Net 2003 .Net Framework > 1.1 > > > > > > In this scenario my application returns the > > > following errors when > > > trying to execute stored procedure in thread: > > > > > > 5/23/2003 10:09:56 AM Database Error Occurred: > No > > > error information > > > available: E_FAIL(0x80004005).:Execute Procedure > > > > > > GetTimeClockLoc(pCompNum=10,pClockID='000870',pClockDescr='Rmca > > > Clocks:Device 000870',pClockDevice='Device > 000870') > > > 5/23/2003 10:09:56 AM 341836 579 7876996 000001 > > > Clock1 Rmca > > > Clocks:Clock1 > > > > > > 5/23/2003 10:09:56 AM Database Error Occurred: > > > X42000:-201:Syntax > > > error or access violation :Execute Procedure > > > > > > GetTimeClockLoc(pCompNum=10,pClockID='000001',pClockDescr='Rmca > > > Clocks:Clock1',pClockDevice='Clock1') > > > > > > 3) CSDK 2.81.TC1 with VS.Net 2003 .Net Framework > 1.1 > > > > > > In this scenario I don't get any errors. > However, > > > my app closes its > > > connection and reopens every time a new thread > is > > > started. This happens > > > about once every minute. Sometimes the > connection > > > reports that it closes > > > but it still remains open on the server. So > over > > > time the app begins to > > > accumulate a lot of open connections and > eventually > > > resource problems start > > > showing up. Whenever the app closes all the > > > connections go away. I tried > > > changing the apps threading model from STA to > MTA > > > but the same symptoms > > > occur. > > > > > > So far CSDK 2.81.TC1 seems to work fine in all > my > > > single threaded apps but > > > they don't open and close connections during the > > > apps lifetime either. > > > > > > Has anyone seen these same problems and if you > have > > > do you know how to > > > workaround or fix them. Thanks for any input. > > > > > > Gregg Walker > > > > > > > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Search - Faster. Easier. Bingo. > > http://search.yahoo.com > > __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com

Thanks for clarifying. Yes. I ran the oledb setup scripts on my server and the version there is 3. Whenever I use the 2.81 version of oledb driver and my app connects and disconnects while a process is running the connection object is closed on the client side but remains open on the server (onstat -u still shows session). This happens with VS.Net 2002 and VS.Net 2003. This is not a problem when the connection stays open for the duration of the process since the session on the server goes away when the process ends. But when a process open and closes and reopens a connection I see that eventually more than one session is used on the server side. Seems like a bug to me. It greatly irrates me because I can't find a version that will work reliably with my apps that open and reopen connections during their lifetime using VS.Net 2003 and Framework 1.1. With the 2.70 oledb driver I get E_FAIL generic error messages just running any query against the database using VS.Net 2003. Anyway I appreciate your help. Gregg Walker "DL Redden" <redden96@yahoo.com> wrote in message news:bb59m9$1n1$1@terabinaries.xmission.com... > > I apologize if my question was a little cryptic. > > I am referring to the coledbp.sql script that is > located in the 'etc' directory of the 2.81 CSDK. You > must run this against the sysmaster database of > whatever instance you plan on creating an OLE DB > connection too. > > To find you current version of this OLE DB setup: > > SELECT oledbver FROM sysmaster:oledbversion;> > If this isn't 3 you need to run the doledbp.sql file > against sysmaster to drop any existing OLE DB setup > then run the coledbp.sql file against sysmaster. > > There are upgrade scripts as well but they won't work. > > --- Gregg Walker <gregorioandador@msn.com> wrote: > > Thanks for your reply. > > > > How are you getting the oledb driver version? > > > > I was looking at the ifxoledbc.dll file and the > > version it show after I > > install CSDK 2.81 is 2.81.0.11499. You mentioned > > you had a version 3.0 > > driver. Where did you get it from? > > > > Also does anyone else have any input on this thread? > > > > Thanks again. > > > > Gregg Walker > > > > "DL Redden" <redden96@yahoo.com> wrote in message > > news:bb00u3$aea$1@terabinaries.xmission.com... > > > > > > Are you sure you are running the latest oledb > > version. > > > I had problems that stemmed from using a 2.5 > > oldedb > > > driver with the 2.81 CSDK. Once I moved to the 3.0 > > > driver all was well. I am running VS.NET 2002 we > > have > > > a few developers using VS.NET 2003 I will see if > > they > > > have had similar problems. > > > > > > > > > --- Gregg Walker <gregg@rrmca.com> wrote: > > > > Hi All, > > > > > > > > I'm trying to move my VS.Net 2002 applications > > to > > > > VS.Net 2003 and haven't > > > > been able to find a version of CSDK that will > > work. > > > > > > > > My Environment: > > > > > > > > Informix Server: IDS 9.30.UC2 on AIX > > > > Client SDK Version: 2.70.TC3 and 2.81.TC1 > > > > > > > > I've been having some problems with a multi > > threaded > > > > C# application that > > > > uses ADO.Net to access the informix server. > > > > > > > > Here's the scenarios. > > > > > > > > 1) CSDK 2.70.TC3 with VS.Net 2002 .Net Framework > > 1.0 > > > > > > > > In this scenario my application works fine. No > > > > errors. > > > > > > > > 2) CSDK 2.70.TC3 with VS.Net 2003 .Net Framework > > 1.1 > > > > > > > > In this scenario my application returns the > > > > following errors when > > > > trying to execute stored procedure in thread: > > > > > > > > 5/23/2003 10:09:56 AM Database Error Occurred: > > No > > > > error information > > > > available: E_FAIL(0x80004005).:Execute Procedure > > > > > > > > > > GetTimeClockLoc(pCompNum=10,pClockID='000870',pClockDescr='Rmca > > > > Clocks:Device 000870',pClockDevice='Device > > 000870') > > > > 5/23/2003 10:09:56 AM 341836 579 7876996 000001 > > > > Clock1 Rmca > > > > Clocks:Clock1 > > > > > > > > 5/23/2003 10:09:56 AM Database Error Occurred: > > > > X42000:-201:Syntax > > > > error or access violation :Execute Procedure > > > > > > > > > > GetTimeClockLoc(pCompNum=10,pClockID='000001',pClockDescr='Rmca > > > > Clocks:Clock1',pClockDevice='Clock1') > > > > > > > > 3) CSDK 2.81.TC1 with VS.Net 2003 .Net Framework > > 1.1 > > > > > > > > In this scenario I don't get any errors. > > However, > > > > my app closes its > > > > connection and reopens every time a new thread > > is > > > > started. This happens > > > > about once every minute. Sometimes the > > connection > > > > reports that it closes > > > > but it still remains open on the server. So > > over > > > > time the app begins to > > > > accumulate a lot of open connections and > > eventually > > > > resource problems start > > > > showing up. Whenever the app closes all the > > > > connections go away. I tried > > > > changing the apps threading model from STA to > > MTA > > > > but the same symptoms > > > > occur. > > > > > > > > So far CSDK 2.81.TC1 seems to work fine in all > > my > > > > single threaded apps but > > > > they don't open and close connections during the > > > > apps lifetime either. > > > > > > > > Has anyone seen these same problems and if you > > have > > > > do you know how to > > > > workaround or fix them. Thanks for any input. > > > > > > > > Gregg Walker > > > > > > > > > > > > > > > > > __________________________________ > > > Do you Yahoo!? > > > The New Yahoo! Search - Faster. Easier. Bingo. > > > http://search.yahoo.com > > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to Outlook(TM). > http://calendar.yahoo.com