Not enough temporary disk space in ASP.net application

I have recently switch a classic ASP application to an ASP.net version.  The application seems to work well, except for one issue that seems to be occurring(mostly at night/early morning).

I begin receiving the following messages in the event log:
Event code: 3001
Event message: The request has been aborted.

Followed by:
Event code: 3005
Event message: An unhandled exception has occurred.
Exception information:
    Exception type: OleDbException
    Exception message: Unspecified error

Then followed by:
Event code: 3005
Event message: An unhandled exception has occurred.
Exception information:
    Exception type: OleDbException
    Exception message: Not enough space on temporary disk.

The database in question is an access database.  Unfortunately for business reasons we are not able to use another database(mysql, mssql, etc).  We never had an issue with using access for the old ASP sight.

I checked the C:\WINDOWS\Temp directory on the server and there are a few Jet*.tmp files out there, none of them are larger than 4kb.  There is 2+ gigs left on the drive.  The only thing that seems to fix the issue is to restart IIS.  After that, everything works great for a few more days/weeks, then  the same issue begins to occur.  

My only thought is that there was some type of long query being run against the database, but I am unable to reproduce the error on my own(even querying all 22,000 records doesn't seem to cause the issue).

I have tried changing a few registry settings(altering the number of table locks, etc) for JET, but none of them seem to work.  The only other thing that is happening around this time are File indexing and Virus scanning, but even when those end, the problem persists until IIS is restarted.

Any help is appreciated.  I'm tired of getting up at 3:00 am to restart the services.
LVL 18
MorcalavinAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Refael AckermannCommented:
In my opinion it is related to the I/O access perfomed by either the file-indexing-service, or the anti-virus.
OleDB+Jet has known issues with handling failed connection (One failed connection can lock the service out).
0
MorcalavinAuthor Commented:
I don't understand why this would only be present in the .net app.  The classic ASP application ran for years and we never had this issue, even with indexes and virus scans going on.
0
MorcalavinAuthor Commented:
I've also found a few instances where this has happened when indexing and virus scanning was not running, although it seems to happen in the early morning more often than during the day.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

MorcalavinAuthor Commented:
I've come to the conclusion that this isn't related to the IO access of the disk, as it appears to be happening at other times when virus scan and catalogue isn't running.

Are there any knowlegebase entries or articles I can gleam from to better understand this "known issues with handling failed connections"

All of my connections are made via accessdatasources.  Is there any way to trap and cleanup connection errors in a way that won't lock out the service?

I've scoured the web and implemented pretty much every workaround for this issue and still nothing.
0
Refael AckermannCommented:
This seems to be a very comprehensive article:
http://aspalliance.com/14
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MorcalavinAuthor Commented:
I converted the database over to an sql express database.  This should eliminate the access issues.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.

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.