Too many client tasks - help please

Good Morning

I am using IIS 6 on a Windows 2000 Server.

I get an error "Too many client tasks"

Microsoft KB154869 says:-

"This behavior is by design.

(This is not an issue with Jet 3.0 as used by Visual Basic 4.0 32-bit.)
"

I am using:-

vbscript.dll
version 5.6.0.7426

and

msjet40.dll
version 4.00.8618.0



How can I stop this error
with minimum effort ??

There are several hundred .ASP pages.



Is the only way to move to SQL Server ??

Thank you in anticipation (I hope)
Pete (Northolt UK)

Re: Too many client tasks - help please

1st thing to do is make sure you are not using system dsns to connect to the
access databases.
(thats bad)

2nd thing to do is use ole connection strings when connecting via dsn-less
(that is if you are not)

3rd thing to do if not have a zillion different sites accessing a zillion
different access databases because no amount of conenction string tweaking
is going to help out

4th thing to do is not expect a very busy application with a lot going on to
work well with access cause it probably wont

5th thing to is just use SQL server

6th thing to do is realize you are not using IIS6 on windows 2000 Server
cause it is not possible



"Peter Byers" wrote in message
news:42770AC8.C7471575@sst-ltd.co.uk...
> Good Morning
>
> I am using IIS 6 on a Windows 2000 Server.
>
> I get an error "Too many client tasks"
>
> Microsoft KB154869 says:-
>
> "This behavior is by design.
>
> (This is not an issue with Jet 3.0 as used by Visual Basic 4.0 32-bit.)
> "
>
> I am using:-
>
> vbscript.dll
> version 5.6.0.7426
>
> and
>
> msjet40.dll
> version 4.00.8618.0
>
>
>
> How can I stop this error
> with minimum effort ??
>
> There are several hundred .ASP pages.
>
>
>
> Is the only way to move to SQL Server ??
>
> Thank you in anticipation (I hope)
> Pete (Northolt UK)
>

Re: Too many client tasks - help please

Thank you Kyle
Pete (Northolt UK)

Kyle Peterson wrote:

> 1st thing to do is make sure you are not using system dsns to connect to the
> access databases.
> (thats bad)
>
> 2nd thing to do is use ole connection strings when connecting via dsn-less
> (that is if you are not)
>
> 3rd thing to do if not have a zillion different sites accessing a zillion
> different access databases because no amount of conenction string tweaking
> is going to help out
>
> 4th thing to do is not expect a very busy application with a lot going on to
> work well with access cause it probably wont
>
> 5th thing to is just use SQL server
>
> 6th thing to do is realize you are not using IIS6 on windows 2000 Server
> cause it is not possible
>
> "Peter Byers" wrote in message
> news:42770AC8.C7471575@sst-ltd.co.uk...
> > Good Morning
> >
> > I am using IIS 6 on a Windows 2000 Server.
> >
> > I get an error "Too many client tasks"
> >
> > Microsoft KB154869 says:-
> >
> > "This behavior is by design.
> >
> > (This is not an issue with Jet 3.0 as used by Visual Basic 4.0 32-bit.)
> > "
> >
> > I am using:-
> >
> > vbscript.dll
> > version 5.6.0.7426
> >
> > and
> >
> > msjet40.dll
> > version 4.00.8618.0
> >
> >
> >
> > How can I stop this error
> > with minimum effort ??
> >
> > There are several hundred .ASP pages.
> >
> >
> >
> > Is the only way to move to SQL Server ??
> >
> > Thank you in anticipation (I hope)
> > Pete (Northolt UK)
> >

Re: Too many client tasks - help please

Peter Byers wrote:
> Good Morning
>
> I am using IIS 6 on a Windows 2000 Server.

Not possible.

>
> I get an error "Too many client tasks"

That's the only information you have about the error? Is it a Jet, vbscript
or IIS error?

>
> Microsoft KB154869 says:-
>
> "This behavior is by design.
>
> (This is not an issue with Jet 3.0 as used by Visual Basic 4.0
> 32-bit.) "

Irrelevant.



> How can I stop this error
> with minimum effort ??
>

There is probably no way without rewriting the way you are doing things. A
web server is not the same as a desktop VB application.

> There are several hundred .ASP pages.
>

>
> Is the only way to move to SQL Server ??

It depends on how much bad coding practices are contributing to your
problem.

In ASP, especially when using a Jet backend, it is critical to minimize the
time each page is connected to the database, either using disconnected
recordsets, or by using GetRows and GetString where appropriate:
http://www.aspfaq.com/show.asp?id=2467

Don't use recordsets for data modification. Recordsets should only be used
to retrieve read-only data for display purposes (this is a different
recommendation than the one I would be making for a desktop VB application).
Use sql statements instead. Here is some reading material:
http://www.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&sel m=e6lLVvOcDHA.1204%40TK2MSFTNGP12.phx.gbl

http://groups-beta.google.com/group/microsoft.public.inetser ver.asp.db/msg/72e36562fee7804e

Don't use "selstar": http://www.aspfaq.com/show.asp?id=2096

It is also critical to close and destroy your connection objects as soon as
you are finished with them. This means: on each page open your connection
just before the first time you need to use it, and close it immediately
after the last time it is used.

Don't store ADO objects in Session or Application:
http://www.aspfaq.com/show.asp?id=2053

Do not disable connection (session) pooling by:
1. using varying connection strings
2. using implicit connections - this can be done inadvertantly by failing to
use the Set keyword when setting the ActiveConnection property to an open
connection object. It can also be done deliberately by using connection
strings instead of open connection objects when opening recordsets.
(http://support.microsoft.com/?kbid=271128)

Avoid the old ODBC technology. Use the newer OLE DB technology:
http://www.aspfaq.com/show.asp?id=2126


Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Re: Too many client tasks - help please

Thank you
It looks like changing from ODBC to OLE DB may have cured it.

It will delay the change to SQL Server at any rate

Thank you
Pete (Northolt UK)

"Bob Barrows [MVP]" wrote:

> Peter Byers wrote:
> > Good Morning
> >
> > I am using IIS 6 on a Windows 2000 Server.
>
> Not possible.
>
> >
> > I get an error "Too many client tasks"
>
> That's the only information you have about the error? Is it a Jet, vbscript
> or IIS error?
>
> >
> > Microsoft KB154869 says:-
> >
> > "This behavior is by design.
> >
> > (This is not an issue with Jet 3.0 as used by Visual Basic 4.0
> > 32-bit.) "
>
> Irrelevant.
>
>
>
> > How can I stop this error
> > with minimum effort ??
> >
>
> There is probably no way without rewriting the way you are doing things. A
> web server is not the same as a desktop VB application.
>
> > There are several hundred .ASP pages.
> >
>
> >
> > Is the only way to move to SQL Server ??
>
> It depends on how much bad coding practices are contributing to your
> problem.
>
> In ASP, especially when using a Jet backend, it is critical to minimize the
> time each page is connected to the database, either using disconnected
> recordsets, or by using GetRows and GetString where appropriate:
> http://www.aspfaq.com/show.asp?id=2467
>
> Don't use recordsets for data modification. Recordsets should only be used
> to retrieve read-only data for display purposes (this is a different
> recommendation than the one I would be making for a desktop VB application).
> Use sql statements instead. Here is some reading material:
> http://www.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&sel m=e6lLVvOcDHA.1204%40TK2MSFTNGP12.phx.gbl
>
> http://groups-beta.google.com/group/microsoft.public.inetser ver.asp.db/msg/72e36562fee7804e
>
> Don't use "selstar": http://www.aspfaq.com/show.asp?id=2096
>
> It is also critical to close and destroy your connection objects as soon as
> you are finished with them. This means: on each page open your connection
> just before the first time you need to use it, and close it immediately
> after the last time it is used.
>
> Don't store ADO objects in Session or Application:
> http://www.aspfaq.com/show.asp?id=2053
>
> Do not disable connection (session) pooling by:
> 1. using varying connection strings
> 2. using implicit connections - this can be done inadvertantly by failing to
> use the Set keyword when setting the ActiveConnection property to an open
> connection object. It can also be done deliberately by using connection
> strings instead of open connection objects when opening recordsets.
> (http://support.microsoft.com/?kbid=271128)
>
> Avoid the old ODBC technology. Use the newer OLE DB technology:
> http://www.aspfaq.com/show.asp?id=2126
>
> Bob Barrows
>
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"