ASP and Access.... Too many client tasks.

I hv an ASP site.. and I keep getting this error frequently...
what is the cause ???
too many users?
how can I increase this?

Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'

[Microsoft][ODBC Microsoft Access Driver] Too many client tasks.

Thanks..
LVL 1
HahoAsked:
Who is Participating?
 
FRehmanCommented:
you can access the database from three ways one from without any dsn second is use file dsn and third one is system dsn the code which you paste here is use file dsn . I think you use system dsn any it also connect the database I simply correct you code and write the exact syntx of statment if you find still in accessing the database  problem then let me know at leo_faisal@yahoo.com
0
 
jkunalCommented:
Check your DSN....
It may be misconfigured to use Windows NT security instead of SQL Server standard security,pl change it.

;->
0
 
FRehmanCommented:
when you open your recordset please use cursor type "lockoptimistic"option so user can edit one record at one time and also check that no one enter with name as some one already present in your site
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
HahoAuthor Commented:
Adjusted points from 50 to 100
0
 
HahoAuthor Commented:
hi guys,

this is the code where it fails:
< this is a global include file >

DSN = "filedsn=" & sPath & f & ";DefaultDir=" & sPath & ";DBQ=" & Path & DB & ";"

Set con = Server.CreateObject("ADODB.Connection")

con.Open DSN <===== HERE!!!

I am increasing the points so that u guys can have a more accurate look..
Thanks!
0
 
FRehmanCommented:
when you make file dsn then save it where it say to save and only write that which is below for open the recordset

  Set cn = Server.CreateObject("ADODB.Connection")
  'Open a connection; the string refers to the DSN
  cn.Open  "FILEDSN=MyDatabase.dsn"
then it will not generate any error I also work it
0
 
jkunalCommented:
Try a DSN less connection.
0
 
HahoAuthor Commented:
frehman,

so are u saying that a DSNless connection has a much lower concurrent capability than one with a ODBC DSN ?? That is why u suggest to me to change from DSNless to using a DSN?

please comment.

Thanks

PS. jkunal: I am already using a DSN-less connection here.
0
 
HahoAuthor Commented:
thanks, but the problem I discovered was because of the server CPU utilization...using too many resources..
leaving other sites with not enough system resources(including connections)...

another possible reason is the limitation of earlier Jet drivers... documentated in Microsoft site.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.