I have discovered some more information with this issue. I believe that the
disk is full error is false the drive has 50 GB free. When doing some trial
and error I found that sometimes I could get the changes to save and other
times I could not. I keep expanding the workbook until I consistamtly got
the error to occur@3MB in size. What I noticed was that the time it took got
significantly longer for it to save to the network location. I am now
thinking that there may be a timeout issue or that the network drops the save
operation. I will further investigate this avenue and see if I can find
something along those lines.
> >Thanks Bruce, I am unclear as to where I look for this reference. Can you
> >add some more detail as to where I can get to this article?
[quoted text clipped - 40 lines]
> >> Suggest you have a dung out in the shared directory or ask for more disk
> >> space. :)
>I have discovered some more information with this issue. I believe that the
>disk is full error is false the drive has 50 GB free. When doing some trial
[quoted text clipped - 5 lines]
> operation. I will further investigate this avenue and see if I can find
>something along those lines.
Does sound promising. Note that a network drive usually shows all it's space
as free even if there are many users and your allocated share of it is a lot
less. Can you check your disk quota allocation on that drive ? Users would
usually have a lot less than 50 GB allocated to them.
Good luck. :)
>> In article <714162D1-1A20-4702-877C-3E64D43502B8@microsoft.com>,
> =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
[quoted text clipped - 49 lines]
>> >> Suggest you have a dung out in the shared directory or ask for more disk
>> >> space. :)
Jim Abel - 24 Jul 2008 15:42 GMT
I was generlizing when I said that were are on a network drive. The Desktops
connect to at server that is entirely for the teams use that also servers as
a wer server and the hard drive is entirely for out use, so there are no
segments allocated to individuals. Its simply a client server situation. we
were able to use a word docunebt as well and get it to generate the same
error messages. We also tried mapping the drive instead of using the UNC to
the file the result was the same error. Looks like the group will just
change the process and save to their desktops and then copy the saved files
back to the server. We just could not find anything unusual (monitoring task
manager for processor, memory and network) that would cause the behavior.
I appreciate your help, Thanks
> >I have discovered some more information with this issue. I believe that the
> >disk is full error is false the drive has 50 GB free. When doing some trial
[quoted text clipped - 66 lines]
> >> >> Suggest you have a dung out in the shared directory or ask for more disk
> >> >> space. :)
Bruce Sinclair - 29 Jul 2008 00:28 GMT
>I was generlizing when I said that were are on a network drive. The Desktops
>connect to at server that is entirely for the teams use that also servers as
[quoted text clipped - 8 lines]
>
>I appreciate your help, Thanks
We try. Sometimes we fail. :)
Only other thing I can think of is file permissions. Asumme you have checked
those, so I'm stumped. Best of luck, and do report if you find a fix.