Too many client tasks....

[Spudhead]

We're running a fairly heavy duty IIS server that runs about 30 seperate sites. It's recently started going down with the (ODBC driver) error "Too many client tasks". (Yes, it runs all these sites off Access '97 databases. Long story, and not much we can do about it at the moment.)

The only reasons we can think of for this are:
a) Server is literally getting swamped; too many hits.
b) Some "soon-to-be-living-the-rest-of-their-short-lives-in-painful-agony" coder hasn't closed a database connection somewhere.

We've investigated both possibilities as exhaustively as we can, and don't think it's either.

Can anyone suggest either
a) some way of telling if the ODBC driver is running as a process or thread or whatever, and if so, which page has started it.
b) Anything else that might cause the error?

[Roy Sinclair]

Check into this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;154869

[Spudhead]

Yeah, I know about the connection limitations. I just don't think it's that, unless something is opening a connection and not closing it. We've been running like this for months, without errors, and suddenly the server is going down about 4 or 5 times a day without any noticeable increase in hits accross all sites. Thanks though.

[Roy Sinclair]

The article seems to indicate that it's related to the 16 bit code which I don't think should be necessary now. Maybe behind the scenes somewhere the code being used for Access databases has reverted to the 16 bit code where it was previously using some 32 bit code without that limitation. i.e The last line of that article indicates that this is not a problem with the Jet 3.0 engine.