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

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