Try to search with Google using: "[ODBC Microsoft Access-driver] Too
many client-tasks". You'll find quite a list there. =3D)

Check that you are closing all objects properly when you are executing
those queries and doing that checking. Are you using Recordsets or
straight Command objects? If possible post some more code.

Teemu Keiski

-----Alkuper=E4inen viesti-----
L=E4hett=E4j=E4: Stephan [mailto:Stephan_bussing@h...]
L=E4hetetty: 4. kes=E4kuuta 2002 20:06
Vastaanottaja: Access ASP
Aihe: [access_asp] JET-error '80004005' unspecified error


Hi Guys, I was wondering if anyone has the solution for the following
problem:

I'm using MS Access 2000, PWS, Win 98. At the moment I'm developing a
webapp based on ASP and a MS Access DB. Everything seems to work fine
until I have to execute a few query's in one function. This function
first
checks if the record already exists, if it doesn't is does an insert
otherwise is wil go on to the next check. This works fine for, let's
say,
30 records (so 30 selects and 30 inserts), but with 50 records or more I

get the message: Microsoft JET-Database Engine Error '80004005'
Unspecified Error. The error point to a line in my code where the
connection to de db is made. But there's nothing wrong with this
connections otherwise the first few records couldn't be inserted too.

I already installed the latest MDAC version (2.7) en JET OLEDB SP. This
didn't help.

I use the following connectionstring:

"Provider=3DMicrosoft.Jet.OLEDB.4.0;Data
Source=3Dd:\project\data\access.mdb;User ID=3D;Password=3D;"

When I change te connectionstring to:
"filedsn=3DD:\projecten\data\ms_access.dsn;DefaultDir=3Dfiledsn=3DD:\proj
ecten
\da
ta;DBQ=3DD:\projecten\data\access.mdb;" 

An other error occurs:

Access Driver:

Microsoft OLE DB Provider for ODBC Drivers fout '80040e4d'
[Microsoft][ODBC Microsoft Access-driver] Too many client-tasks.
/_admin/include/ClassDataAccess.asp, line 171

But when I run my application on my providers webserver. There's no
problem. Of course there's other software installed on there system.
Windows 2000 and IIS 5. But still I'm wondering why it goes wrong on my
system. Does anyone has any suggestions.

Thx in advance.

Greetzzz

Stephan
mailto:Stephan_bussing@h...

Thx for the advice, I'm still seaching with google but with the first 
error message. There's also a lot about that, but not what I'm looking 
for. Actually I do close al the objects en open them on every request.

Here's some code you asked for, I use this code in a DataAccessClass, this 
piece of code executes the insert, update and delete-query's:

Public Property Get DbExecute

 DbCommandType = "Execute"

'		Connect, if necessary, to the database
%>
 <!--#include file="DatabaseConnectProperties.asp"-->
<%
  Set objConn = Server.CreateObject("ADODB.Connection")
  objConn.Open ConnectString

  Set cmdSP = Server.CreateObject("ADODB.Command")
  cmdSP.CommandText = strStoredProcedure
  cmdSP.CommandType = adCmdStoredProc
  cmdSP.ActiveConnection = objConn
  for RecordTeller = 0 to (ParamCounter -1)
    if arrayParamIO(Recordteller) = "i" then
      if arrayParamTypes(RecordTeller) = adVarChar then
	set parSP(RecordTeller) = cmdSP.CreateParameter( arrayParamNames  
(RecordTeller), arrayParamTypes(RecordTeller), adParamInput,  
arrayParamSizes(RecordTeller))
      elseif arrayParamTypes(RecordTeller) = adChar then
	set parSP(RecordTeller) = cmdSP.CreateParameter( arrayParamNames
(RecordTeller), arrayParamTypes(RecordTeller), adParamInput, 
arrayParamSizes(RecordTeller))
      else
	set parSP(RecordTeller) = cmdSP.CreateParameter( arrayParamNames
(RecordTeller), arrayParamTypes(RecordTeller), adParamInput)
      end if
      cmdSP.Parameters.Append parSP(RecordTeller)
      parSP(RecordTeller).Value = arrayParamValues(RecordTeller)
	elseif arrayParamIO(Recordteller) = "o" then
          if arrayParamTypes(RecordTeller) = adVarChar then
	    set parSP(RecordTeller) = cmdSP.CreateParameter( 
arrayParamNames(RecordTeller), arrayParamTypes(RecordTeller), 
adParamOutput, arrayParamSizes(RecordTeller))
	  elseif arrayParamTypes(RecordTeller) = adChar then
	    set parSP(RecordTeller) = cmdSP.CreateParameter( 
arrayParamNames(RecordTeller), arrayParamTypes(RecordTeller), 
adParamOutput, arrayParamSizes(RecordTeller))
	  else
	    set parSP(RecordTeller) = cmdSP.CreateParameter( 
arrayParamNames(RecordTeller), arrayParamTypes(RecordTeller), 
adParamOutput)
	  end if
	  cmdSP.Parameters.Append parSP(RecordTeller)
	end if
   next

   cmdSP.Execute
		
   Set objRecordSet  = objConn.Execute("SELECT @@IDENTITY")
   intReturnValue = objRecordSet(0)

   If IsObject(cmdSP) Then
     Set cmdSP = nothing
   End If	
		
   If IsObject(objConn) Then
     Set ObjConn = nothing
   End If	
End Property

Well, that's it.

Thx


> Try to search with Google using: "[ODBC Microsoft Access-driver] Too
many client-tasks". You'll find quite a list there. =3D)

Check that you are closing all objects properly when you are executing
those queries and doing that checking. Are you using Recordsets or
straight Command objects? If possible post some more code.

Teemu Keiski

-----Alkuper=E4inen viesti-----
L=E4hett=E4j=E4: Stephan [mailto:Stephan_bussing@h...]
L=E4hetetty: 4. kes=E4kuuta 2002 20:06
Vastaanottaja: Access ASP
Aihe: [access_asp] JET-error '80004005' unspecified error


Hi Guys, I was wondering if anyone has the solution for the following
problem:

I'm using MS Access 2000, PWS, Win 98. At the moment I'm developing a
webapp based on ASP and a MS Access DB. Everything seems to work fine
until I have to execute a few query's in one function. This function
first
checks if the record already exists, if it doesn't is does an insert
otherwise is wil go on to the next check. This works fine for, let's
say,
30 records (so 30 selects and 30 inserts), but with 50 records or more I

get the message: Microsoft JET-Database Engine Error '80004005'
Unspecified Error. The error point to a line in my code where the
connection to de db is made. But there's nothing wrong with this
connections otherwise the first few records couldn't be inserted too.

I already installed the latest MDAC version (2.7) en JET OLEDB SP. This
didn't help.

I use the following connectionstring:

"Provider=3DMicrosoft.Jet.OLEDB.4.0;Data
Source=3Dd:\project\data\access.mdb;User ID=3D;Password=3D;"

When I change te connectionstring to:
"filedsn=3DD:\projecten\data\ms_access.dsn;DefaultDir=3Dfiledsn=3DD:\proj
ecten
\da
ta;DBQ=3DD:\projecten\data\access.mdb;" 

An other error occurs:

Access Driver:

Microsoft OLE DB Provider for ODBC Drivers fout '80040e4d'
[Microsoft][ODBC Microsoft Access-driver] Too many client-tasks.
/_admin/include/ClassDataAccess.asp, line 171

But when I run my application on my providers webserver. There's no
problem. Of course there's other software installed on there system.
Windows 2000 and IIS 5. But still I'm wondering why it goes wrong on my
system. Does anyone has any suggestions.

Thx in advance.

Greetzzz

Stephan
mailto:Stephan_bussing@h...