Not enought space on temporary disk 2147024882

[earme]

Hello all,

I have an ASP app on a win 2k server that connects to an Access 2000 DB on the same server via a system DSN. On my development pc everything works fine.

However, on the 'real' pc, also a win 2k server, connecting to an Access 2000 DB on the same server via a system DSN I'm having problems. The app lets you connect to the database (using asp with vbScript) for a very little bit and then gives an error "Not enought space on temporary disk" and number "2147024882" and won't let you do anything else.
I've searched Microsoft's site and the only thing it can tell me is not to do appendchunk, but I'm not doing appendchunk, nor have I ever used it.
I would greatly appreciate any help you can give me!!!!

TIA,
Earme

 

[tlbroadbent]

Make sure that your system's TEMP and TMP variables are set.
Make sure that wherever they are set to has enough free disk space.
Terry

http://members.home.net/tlbroadbent/sqlarticles.htm

"The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge." - Daniel J Boorstin

 

[earme]

The TEMP and TMP variables are set to c:/winnt/temp, which is on the 10G hard drive.
Should they be pointing some where else? Or is something else wrong?

Earme

 

[tlbroadbent]

How much unused space is availale on the 10GB C: drive? You might also check if there are many *.TMP or other temporary files in the temp directory. Cleanup may be in order. Terry

http://members.home.net/tlbroadbent/sqlarticles.htm

"The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge." - Daniel J Boorstin

 

[earme]

Hello again,
I was slightly wrong about the size of the drive. The drive is 20G and it has 15G free. I've increased the virtual memory/paging size to 500M, but we're still getting the problem.
Should I make sure that the temp directory has certain permissions? If so what should they be? and why didn't I have to set them up for the test machine to work?

Thanks,
Earme

 

[tlbroadbent]

[ol][li]Did you find any *.tmp or other files in the temp directory? Sometimes, you can get errors if there are many TMP files even with large amounts of disk space available. You should monitor the TEMP directory while the APP is running to see what kind of activity occurs.
[li]Is the latest version of MDAC installed?
[li]IIS is probably running on the same server? What does the IIS log show? And how big is that log? If large, you could rename or delete it.[/ol]I think I'm out of ideas on this one. Except for... Nah, you wouldn't want to reboot! ;-) Not again anyway!
Terry

http://members.home.net/tlbroadbent/sqlarticles.htm

"The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge." - Daniel J Boorstin

 

[earme]

Hello all,

I went out and visited the 'real' machine yesterday. Here's the list of things I did:
-Compacted and Repaired the database
-Checked and set the db permissions
-Increased the page size
-gave the anonymous user write permissions on the temp directory (even though on the 'dev' machine it worked fine without them)

It works fine now, and I think a little faster. I think that setting the db permissions fixed it (I could be wrong). We had everything set up for the Administrator login, but they (the people we made the app for) added a login and were running the machine off of that. So, all the NTFS permissions that I had set up for the IUSR_ account weren't there anymore. So, I went through and added them all again.

Thanks for all your help!
Evie

 

[earme]

The previous steps taken in the previous message apparently didn't fix the problem. As soon as they sat down to use the machine, the next day, it returned with the same error, much to my dismay.
After posting to a couple other newsgroups and bringing a co-worker along as an extra set of eyes I had a new, but short, list of things to try.
We changed the registry as it suggests in the "Max Buffer Size Set Too Low" artical on microsoft's site, but for 4.0 instead of 3.0 (for some reason it was 0, changed it to 512). And we changed the DSN connection to a DSN-less connection. It seems to work now, but I'm not going to assume so this time. I'll wait a bit to see if I hear from them again.

Thanks!
Earme