Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ASP script causes "Out of diskspace" message

Status
Not open for further replies.

jasonsalas

IS-IT--Management
Jun 20, 2001
480
GU
I have a feeling this is going to be a simple answer, but I've been looking at this too long, and I'm stumped.

I wrote a search script to search strings in an Access database which feeds my site. It works great locally, however, it generates an error like the following:

=============================================
Error - Temporarily Out of Disk Space
=============================================

This also happens when a page takes a long time to load...due to network traffic, slow ISP, etc.

Sometimes, refreshing the page clears the error and displays the page as normal, but other times, it seems like the server take a few minutes to clear the error (cache-dump???)

HELP!
 
U have an sample code that generate an error (in ASP)?
 
Thanks for responding.

It just happened now...I believe my Web server is Apache with the MS FrontPage Server Extensions installed onto it.

Here's the error message:

===========================================================
Microsoft OLE DB Provider for ODBC Drivers error '8007000e'

[Microsoft][ODBC Microsoft Access Driver] Not enough space on temporary disk.

<<<PATH TO FILE>>>, <<<LINE OF FILE CAUSING ERROR>>>
===========================================================

In this instance right now, the line reporting the error is the line in the ASP file which calls upon the connection string...which leads me to believe that the database query isn't being completed within the time alloted.

I e-mailed my Web host provider and asked them what the script timeout setting is on the Web server I'm on. I'm using shared hosting, and I verified with the provider that I'm one of a couple hundred sites on the same box.

Help!
 
Hi all,

The error seems to be one returned by SQL Server. I haven't found a clear explanation but apparently it occurs when the table you are using is too large. It contains to much records and/or columns for the server's memory to handle.

So basically, the most reasonable sollution seems to be either reducing the size of the table (but I guess this isn't possible) or moving to a more powerfull server.

Hope this clarifies it? B-)

Kristof

PS: this is a short description I found on MSDN:

E_OUTOFMEMORY 8007000E Out of memory.
 
Thanks much for the help. Unfortunately, the answer was one I feared the most, but at least I have confirmation now. I'm using Access 2000 as the database, and the table being queried has at the moment 1,581 records. Do you think this is too much?

I run a news-oriented site which gets about 2,700 unqieu user visitations per day, so the number of records we add per day is about 6-7. I didn't think that this would be too large.

I've seen so many advantages come out of my moving to database-driven format, but if speed and performance are going to be compromised, I'll highly consider going back to creating static pages. I might be able to reduce the size of the table

Here's my site, if you'd like to see:
If you could, try browsing to the main page, and also to individual stories, which are also queried off of the same table:


...and if you can, let me know how many seconds it takes to download each, and with what type of connection.

As you can see, the stories generated are based on stored procedures which gather the info. I did this because I wanted to improve performance on the server end, by use of a STORPROC.

It also doesn't help my case that being all the way out here in Guam, we have been having major problems with our major ISPs for the past few days, and in my building, the telecomm service going out is very bad.

Thanks so much for your help!
 
Hi,

This is just an idea but could it be possible to break up the table into smaller ones? Thus, the results returned through a query will be smaller too.

Another solution might be checking your SQL statements. Look for possibilities of reducing the number of fields you ask. For instance, (if possible), instead of using select * from ... use select field1, field2 from ... .
Basically, checking if anything is generating a lot of info, while it is not needed.

Hope it helps you find a solution? :)I

Gtz,

Kristof
 
Hi,

Maybe, instead of using Access 2000, convert it to '97 format. Strangely these mdb files are about 1/4 smaller than their 2000 counterparts. So, perhaps they also take about 1/4 less space in the memory?

Gtz,

Kristof B-)
 
Hi Kristof,

Yeah, I was thinking about reducing the size of the tables (actually, it's just one table). I've placed all of our stories in a single table, since we launched our site in the year 2000. I could move all of the 2000 stories to a new table, and just have the current table reflect the current year's stories. I just rana query on my locxal copy of the database, and there are only 866 stories for the year 2001, which I suppose would greatly speed up the query roundtrip time from the 1,586 records it currently has to page through.

I also made sure at the initial design stage that I didn't include all of the tables in my SQL statement...only those to be used. Thanks for looking out for this.

Reverting to Access '97 wouldn't be feasible, because al;l the machines on my LAN and in my production shop run Office 2000 or Office XP. I'm not too worried about the filesize...just about the speed by which the queries are executed on the server...so it isn't detrimental to our user's enjoyment of our pages.

I e-mailed my Web host provider and asked them what they thought about it....I'm thinking it may have something to do with the load on the shared server I'm on (I'm site # 192 out of about 388 on the same NT box).

Thanks again for the help...I'm thinking big-time about this one.
 
Hello,
I was just (and I mean JUST) having the same problem that you are. It was on a W2K machine running IIS and Access 2000. I managed to fix it yesterday.
This is what I did:
-Compacted and Repaired db
-Checked and set the NTFS permissions on the db and the file the db was is
-Increased the paging size for the system
-gave the anonymous user write permissions on the temporary drive

I did them all at once, trying to solve the problem in 1 swoop, and it seemed to work. I think it was the NTFS permissions though, they weren't using the account we had set up, so I had to set up the IUSR permissions from the login account they made and were using.

HTH,
Earme
 
LADIES AND GENTLEMEN...WE HAVE PROBLEM RESOLUTION!!!! (methinks)

Although my dynamic pages weren't printing the [recise error type on the page, the error code is &quot;502: Temporarily Overloaded&quot; (I checked on my server's ERROR.LOG traffic file).

Now that we've ID's the culprit, here's some background:
service temporarily overloaded


Based on those assessments, it would seem that the problem is just due to the incoming traffic to the server. This alleviates my worries that I'll have to make massive changes to my database (although I have learned through this forum that as a one-man news site manager I should be keeping my main table with the stories small, and build an archive). It's just a matter of reloading the page when the server is less busy.

Under duress, the Web server will continue to serve up static content (i.e., vanilla HTML pages), but apparently to avoid total meltdown puts server-side scripting on the backburner...and the 502 error gets caused due to script timeouts.

I guess now I have to think about owning my own server, so as not to run into the problems of sharing bandwidth with other sites...which could be causing the traffic load problems.

THANKS ALL FOR YOUR HELP! I REALLY APPRECIATE IT!
 
Thanks for the tip, EARME. My Web host company is stumped. I'm not sure in my case if the solution will be the same as yours, but it's worth a shot.

Was your temp diskspace error consistent or sporadic? Mine would happen during times of high server activity, either through the ISPs contacting the pages, OR the Web host whereupon the site sits.
 
Mine started at the same exact place in the app every single time. After the error occured there, it was causing problems else where too. My app is an intranet right now for a small company to do order entry on. There's usually only 1 person on it at a time so they can get used to it before we do a roll-over (so the constant errors were making them nervous).

Earme
 
Good to know that you resolved it. At least yours was identified and consistent.

The only time I was encountering the beast was when I tried executing a site-wide search script I wrote. The script was trying to find textstring matches using the SQL &quot;like %&quot; statement, and searching through 1,500 memo fields in a recordset in an Access 2000 database. I thought that the load was too much for the server, but then it started happening at odd times.

I found out it's mainly due to traffic loads, but I'll keep your own scenario stored in my mental rolodex for future use!

Thanks again!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top