ufpcit
asked on
Disk is full error when saving Excel files to network locations
I have multiple users that are getting disk is full errors when trying to save Excel (2000 and 2003) files to a network drive on Windows Server 2003 Enterprise servers from Windows XPSP2 clients. Yes, we do have Backup Exec with OFO but are on latest version of vsp.sys. Sometimes it will save the file but takes an exraordinarily long time to save it. Those that error out do so after what looks to be a very long save process. Network utilization is at a minimum (on the machine doing the saving) during the process as well (less than 1% utilization). This just started happeneing in the last 2 weeks or so. I've started to wonder if it has anyhing to do with the latest batch or two of Windows Updates.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The paths are long in most cases but in no case are they more than 256 characters even including filenames. These are different people saving different files on different servers. Currently looking into an issue with our VOIP phones which looks like it might be the problem.
ASKER
Still no permanent fix but here's what we know. Our IP phones seem to be related to the problem. If we take the phones out of the loop by connecting the PC to the incoming LAN line, they act as they should. They open and save files quickly. With the phones in the loop, browsing the network is slow and files take longer to open. The files take seemingly forever to save and sometimes they timeout and give the disk is full message followed by file not saved message. 10MB files, if they do save, take about 5 minutes to save.
In some cases, cycling the phones works to remedy the issue, but only for that boot. The issue returns upon rebooting the PC. In other cases (most actually) cycling the phones causes the PC to not reconnect to the network at all until the PC is rebooted. If you test the PC before rebooting, it shows a valid IP and will do an ipconfig /release and /renew but will do nothing else network-related until rebooting.
BTW, we're on Avaya phones... mostly model 4610SW.
In some cases, cycling the phones works to remedy the issue, but only for that boot. The issue returns upon rebooting the PC. In other cases (most actually) cycling the phones causes the PC to not reconnect to the network at all until the PC is rebooted. If you test the PC before rebooting, it shows a valid IP and will do an ipconfig /release and /renew but will do nothing else network-related until rebooting.
BTW, we're on Avaya phones... mostly model 4610SW.
ASKER
Thanks y'all! We found the answer. It was a setting on the phones. They were set for full-duplex 100Mbps and once we changed it to auto-negotiate it fixed the problem. Still not sure why only some users had the issue as everybody's phones were setup the same.
ASKER