Hi,
Since yesterday Im getting this weird Error message while connection to any of my ASP Application which is backed by Access database:
Microsoft JET Database Engine error ‘80004005’
System resource exceeded.
/forum/functions/functions_common.asp, line 690
now wt happenz is that the applications are running some times & they return error message some times.
so can any 1 help me out with this issue? ?(
btw im using win6 host.
Thanx
Best Regards,
Da^Master<
The websites I host on win6 sometimes experienced the same problem today and yesterday. System resources seem to be to low.
Issue corrected
This normally happens when a large number of zombie of dead database connections are creating crashing ODBC. This happens when people dont close their DB connections properly
We normally avoid this problem is do a weekly server restart. Win6 hasn’t been restarted in 2 weeks or so.
This problem happens very occasionally and we’ll be working to prevent a reoccurance
[QUOTE=tritac]
The websites I host on win6 sometimes experienced the same problem today and yesterday. System resources seem to be to low.
[/QUOTE]
OK, we are investigating this. It seems that some website is running a loop that is creating alot of dead connections.
that problem seem to be ok now… but the loading speed is a bit slow 
any wayz thanx for solving the problem 
hi,
Well I am getting the same Error message again!. Can you please check wts wrong? ?(
This is my site on Win6 Host:
This is the Error:
Microsoft JET Database Engine error ‘80004005’
System resource exceeded.
/forum/common.asp, line 268
Thanx,
Regardsm
add me to that list as well… same issue on a few sites…
Although we corrected the issue, we investigated this. There is a site on Win6 that is eating almost 1GB of RAM very quickly that caused the sudden slowness and these errors
We are working to track down this site and we should have this issue resolved shortly
hi,
well the problem is solved now thanx a lot. 8)
Regards,
the same problem here!
Please fix this asap,
Best regards, Ignacio Marcos.
This has been fixed. The problem was a buggy script of some customer on same server, which was using too much resources.