Discussion Locked

Client32 out of disk space errors.

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I support a 700 user Novell network. I keep experiencing this error message on a hand full of user's PCs. "Client32 out of disk space while copying Proe080.tmp". After canceling the error, 3 or 4 different files give the same error message. It onlyhappens at Logon and Logoff. All users and share drives have space. Any ideas on what could be causing the error?

12 replies

by syscokid

There may be enough space on the drives and shares, but is it possible that those users' space set for their personal drive is too small?

by villafum

All the PCs are running fine. It seems to be a problem writing the users profile back to the server. (Roaming profiles don't work to well with Novell)

by isys

Put the following statement in your system login script:

SET TEMP=F:\TEMP

or whatever mapped network drive you choose. Like the previous respondent said, your user local hard disk space is probably full.

by villafum

All the PCs are running fine. It seems to be a problem writing the users profile back to the server. (Roaming profiles don't work to well with Novell)

by syscokid

I think what I was trying to say was that there may be plenty of space on the volume where the K: shares are, or whatever your user share is, but those particular users may be exceeding the space you've allotted them in user setup. (As you can tell,my NetWare is a little rusty).

by villafum

All the PCs are running fine. It seems to be a problem writing the users profile back to the server. (Roaming profiles don't work to well with Novell)

by timber

I agree with asyscokid.. Go to nwadmin check the vol that the users are on, right click select details, and User Space limitations. If you don't see it there try backing up to the root of the vol.

Hope that helps

by villafum

All the PCs are running fine. It seems to be a problem writing the users profile back to the server. (Roaming profiles don't work to well with Novell)

by whistler

Strange, I have had a Compaq Presario run out of memory while starting using client32. We raised the memory to 32mb from 16mb and the problem went away. Figured it was due to all the junk Presario's load, since the other Presario's in the departmenteither had none of Compaq's garbage and/or 32mb of memory.

by villafum

All the PCs are running fine. It seems to be a problem writing the users profile back to the server. (Roaming profiles don't work to well with Novell)

by rfraysier

How about trying something real simple 1st, on the local hdd, C:\; find the temp directory and delete everything in it. If that doesn't help (you don't say what OS the workstations are running), but try upping the virtual memory.

by villafum

All the PCs are running fine. It seems to be a problem writing the users profile back to the server. (Roaming profiles don't work to well with Novell)

This discussion is closed to new replies.