I have a copy of Excel 2003 installed on a server. It is in a share were the
4 people on out team can access throuh a mapped drive. When any of us open
the workbook make some changes and attempt to save it we get a messavebox
that says the disk is full.

This in not true.
If we save the workbook to our desttop, make the edits save it and copy it
back to the server they are saved for the next person to see without a
problem.

This adds a good deal of time to the changes over the month and we would
like to know ifanyone can tell us why we cannot edit the file directly on the
server. It contains a data source to a database that populates the workbook
with some data, if that matters.

Any ideas of why we have this behavior and what we could do so that we can
simply open the file in place make the changes and then save it , would be
greatly appreciated.

Thanks

In article <076FA966-0F43-423E-B3C1-5A77AD729081@microsoft.com>, =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
>I have a copy of Excel 2003 installed on a server. It is in a share were the
>4 people on out team can access throuh a mapped drive. When any of us open
>the workbook make some changes and attempt to save it we get a messavebox
>that says the disk is full.
>
>This in not true.
>If we save the workbook to our desttop, make the edits save it and copy it
>back to the server they are saved for the next person to see without a
>problem.
>
>This adds a good deal of time to the changes over the month and we would
>like to know ifanyone can tell us why we cannot edit the file directly on the
>server. It contains a data source to a database that populates the workbook
>with some data, if that matters.
>
>Any ideas of why we have this behavior and what we could do so that we can
>simply open the file in place make the changes and then save it , would be
>greatly appreciated.

Are you really close to your disk limit (ie if you saved 2 files the same
size as the one you are talking about, would you get the message on the
second save but not the first ?). The first thing XL does when opening is
create a temp file in the directory where the original is. (copy 1).
When you try to save it, I think it creates a new version, then deletes the
temp file. (copy 2). That it works fine on the desktops is an indicator.
Suggest you have a dung out in the shared directory or ask for more disk
space. :)

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?

Thanks
"Bruce Sinclair" wrote:

> In article <076FA966-0F43-423E-B3C1-5A77AD729081@microsoft.com>, =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
> >I have a copy of Excel 2003 installed on a server. It is in a share were the
> >4 people on out team can access throuh a mapped drive. When any of us open
> >the workbook make some changes and attempt to save it we get a messavebox
> >that says the disk is full.
> >
> >This in not true.
> >If we save the workbook to our desttop, make the edits save it and copy it
> >back to the server they are saved for the next person to see without a
> >problem.
> >
> >This adds a good deal of time to the changes over the month and we would
> >like to know ifanyone can tell us why we cannot edit the file directly on the
> >server. It contains a data source to a database that populates the workbook
> >with some data, if that matters.
> >
> >Any ideas of why we have this behavior and what we could do so that we can
> >simply open the file in place make the changes and then save it , would be
> >greatly appreciated.
>
> Are you really close to your disk limit (ie if you saved 2 files the same
> size as the one you are talking about, would you get the message on the
> second save but not the first ?). The first thing XL does when opening is
> create a temp file in the directory where the original is. (copy 1).
> When you try to save it, I think it creates a new version, then deletes the
> temp file. (copy 2). That it works fine on the desktops is an indicator.
> Suggest you have a dung out in the shared directory or ask for more disk
> space. :)
>
>
>
>

In article <714162D1-1A20-4702-877C-3E64D43502B8@microsoft.com>, =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
>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?

Article ? Sorry, don't know what you mean. I do know I've had disk full
errors (particularly on a network drive) when it wasn't and the temporary
file was the problem. It's worse (obviously) for seriously large files. :)
I admit I'm not certain beyond doubt that xl does this now or with all
versions, but it is worth a look. And the dung out/ ask for more space fix
ought to work anyway. :)

>Thanks
>"Bruce Sinclair" wrote:
>
>> In article <076FA966-0F43-423E-B3C1-5A77AD729081@microsoft.com>,
> =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
>> >I have a copy of Excel 2003 installed on a server. It is in a share were
> the
>> >4 people on out team can access throuh a mapped drive. When any of us open
>> >the workbook make some changes and attempt to save it we get a messavebox
>> >that says the disk is full.
>> >
>> >This in not true.
>> >If we save the workbook to our desttop, make the edits save it and copy it
>> >back to the server they are saved for the next person to see without a
>> >problem.
>> >
>> >This adds a good deal of time to the changes over the month and we would
>> >like to know ifanyone can tell us why we cannot edit the file directly on
> the
>> >server. It contains a data source to a database that populates the workbook
>
>> >with some data, if that matters.
>> >
>> >Any ideas of why we have this behavior and what we could do so that we can
>> >simply open the file in place make the changes and then save it , would be
>> >greatly appreciated.
>>
>> Are you really close to your disk limit (ie if you saved 2 files the same
>> size as the one you are talking about, would you get the message on the
>> second save but not the first ?). The first thing XL does when opening is
>> create a temp file in the directory where the original is. (copy 1).
>> When you try to save it, I think it creates a new version, then deletes the
>> temp file. (copy 2). That it works fine on the desktops is an indicator.
>> 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
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.

"Bruce Sinclair" wrote:

> In article <714162D1-1A20-4702-877C-3E64D43502B8@microsoft.com>, =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
> >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?
>
> Article ? Sorry, don't know what you mean. I do know I've had disk full
> errors (particularly on a network drive) when it wasn't and the temporary
> file was the problem. It's worse (obviously) for seriously large files. :)
> I admit I'm not certain beyond doubt that xl does this now or with all
> versions, but it is worth a look. And the dung out/ ask for more space fix
> ought to work anyway. :)
>
> >Thanks
> >"Bruce Sinclair" wrote:
> >
> >> In article <076FA966-0F43-423E-B3C1-5A77AD729081@microsoft.com>,
> > =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
> >> >I have a copy of Excel 2003 installed on a server. It is in a share were
> > the
> >> >4 people on out team can access throuh a mapped drive. When any of us open
> >> >the workbook make some changes and attempt to save it we get a messavebox
> >> >that says the disk is full.
> >> >
> >> >This in not true.
> >> >If we save the workbook to our desttop, make the edits save it and copy it
> >> >back to the server they are saved for the next person to see without a
> >> >problem.
> >> >
> >> >This adds a good deal of time to the changes over the month and we would
> >> >like to know ifanyone can tell us why we cannot edit the file directly on
> > the
> >> >server. It contains a data source to a database that populates the workbook
> >
> >> >with some data, if that matters.
> >> >
> >> >Any ideas of why we have this behavior and what we could do so that we can
> >> >simply open the file in place make the changes and then save it , would be
> >> >greatly appreciated.
> >>
> >> Are you really close to your disk limit (ie if you saved 2 files the same
> >> size as the one you are talking about, would you get the message on the
> >> second save but not the first ?). The first thing XL does when opening is
> >> create a temp file in the directory where the original is. (copy 1).
> >> When you try to save it, I think it creates a new version, then deletes the
> >> temp file. (copy 2). That it works fine on the desktops is an indicator.
> >> Suggest you have a dung out in the shared directory or ask for more disk
> >> space. :)
>
>

In article <33103DC9-4477-456D-83AE-B2A200DE227E@microsoft.com>, =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
>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.

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. :)

>"Bruce Sinclair" wrote:
>
>> In article <714162D1-1A20-4702-877C-3E64D43502B8@microsoft.com>,
> =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
>> >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?
>>
>> Article ? Sorry, don't know what you mean. I do know I've had disk full
>> errors (particularly on a network drive) when it wasn't and the temporary
>> file was the problem. It's worse (obviously) for seriously large files. :)
>> I admit I'm not certain beyond doubt that xl does this now or with all
>> versions, but it is worth a look. And the dung out/ ask for more space fix
>> ought to work anyway. :)
>>
>> >Thanks
>> >"Bruce Sinclair" wrote:
>> >
>> >> In article <076FA966-0F43-423E-B3C1-5A77AD729081@microsoft.com>,
>> > =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
>> >> >I have a copy of Excel 2003 installed on a server. It is in a share were
>> > the
>> >> >4 people on out team can access throuh a mapped drive. When any of us
> open
>> >> >the workbook make some changes and attempt to save it we get a messavebox
>
>> >> >that says the disk is full.
>> >> >
>> >> >This in not true.
>> >> >If we save the workbook to our desttop, make the edits save it and copy
> it
>> >> >back to the server they are saved for the next person to see without a
>> >> >problem.
>> >> >
>> >> >This adds a good deal of time to the changes over the month and we would
>> >> >like to know ifanyone can tell us why we cannot edit the file directly on
>> > the
>> >> >server. It contains a data source to a database that populates the
> workbook
>> >
>> >> >with some data, if that matters.
>> >> >
>> >> >Any ideas of why we have this behavior and what we could do so that we
> can
>> >> >simply open the file in place make the changes and then save it , would
> be
>> >> >greatly appreciated.
>> >>
>> >> Are you really close to your disk limit (ie if you saved 2 files the same
>> >> size as the one you are talking about, would you get the message on the
>> >> second save but not the first ?). The first thing XL does when opening is
>> >> create a temp file in the directory where the original is. (copy 1).
>> >> When you try to save it, I think it creates a new version, then deletes
> the
>> >> temp file. (copy 2). That it works fine on the desktops is an indicator.
>> >> Suggest you have a dung out in the shared directory or ask for more disk
>> >> space. :)
>>
>>

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

"Bruce Sinclair" wrote:

> In article <33103DC9-4477-456D-83AE-B2A200DE227E@microsoft.com>, =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
> >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.
>
> 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. :)
>
> >"Bruce Sinclair" wrote:
> >
> >> In article <714162D1-1A20-4702-877C-3E64D43502B8@microsoft.com>,
> > =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
> >> >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?
> >>
> >> Article ? Sorry, don't know what you mean. I do know I've had disk full
> >> errors (particularly on a network drive) when it wasn't and the temporary
> >> file was the problem. It's worse (obviously) for seriously large files. :)
> >> I admit I'm not certain beyond doubt that xl does this now or with all
> >> versions, but it is worth a look. And the dung out/ ask for more space fix
> >> ought to work anyway. :)
> >>
> >> >Thanks
> >> >"Bruce Sinclair" wrote:
> >> >
> >> >> In article <076FA966-0F43-423E-B3C1-5A77AD729081@microsoft.com>,
> >> > =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
> >> >> >I have a copy of Excel 2003 installed on a server. It is in a share were
> >> > the
> >> >> >4 people on out team can access throuh a mapped drive. When any of us
> > open
> >> >> >the workbook make some changes and attempt to save it we get a messavebox
> >
> >> >> >that says the disk is full.
> >> >> >
> >> >> >This in not true.
> >> >> >If we save the workbook to our desttop, make the edits save it and copy
> > it
> >> >> >back to the server they are saved for the next person to see without a
> >> >> >problem.
> >> >> >
> >> >> >This adds a good deal of time to the changes over the month and we would
> >> >> >like to know ifanyone can tell us why we cannot edit the file directly on
> >> > the
> >> >> >server. It contains a data source to a database that populates the
> > workbook
> >> >
> >> >> >with some data, if that matters.
> >> >> >
> >> >> >Any ideas of why we have this behavior and what we could do so that we
> > can
> >> >> >simply open the file in place make the changes and then save it , would
> > be
> >> >> >greatly appreciated.
> >> >>
> >> >> Are you really close to your disk limit (ie if you saved 2 files the same
> >> >> size as the one you are talking about, would you get the message on the
> >> >> second save but not the first ?). The first thing XL does when opening is
> >> >> create a temp file in the directory where the original is. (copy 1).
> >> >> When you try to save it, I think it creates a new version, then deletes
> > the
> >> >> temp file. (copy 2). That it works fine on the desktops is an indicator.
> >> >> Suggest you have a dung out in the shared directory or ask for more disk
> >> >> space. :)
> >>
> >>
>

In article <71600679-3F3B-47D6-ADB5-6A855770B5D3@microsoft.com>, =?Utf-8?B?SmltIEFiZWw=?= <JimAbel@discussions.microsoft.com> wrote:
>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

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.