D
Denard Springle
Excel (and Word) version 2000, XP(2002) and 2003 are all
producing "Disk is Full" errors followed by "Document
could not be saved". Excel in particular sometimes
presents "Document is locked" errors. I've researched this
issue in the KB and on Technet and have found several
articles with several suggestions. None of the found
articles seems to apply. Since I have tried all of the
known resolutions and checked every Microsoft KB article
relating to these issues I'm asking the question here.
Several of my users have experienced this problem, but not
all. Problem is very intermittent, though seems to be more
frequent with Office 2003 than Office XP or Office 2000.
Here is the basic scenario and what I have discovered:
Problem can exist on Windows 2000 or Windows XP.
Files are located on network shares.
Files can be saved to local drive or different network
share on the same server with the troubled network share
without incident.
Affects one share at one time, and not another (i.e. users
home directory but not a public share at one time, then
the public share but not the users home directory at
another time).
Saving as .rtf does not resolve this issue.
Saving as different file name does not resolve issue.
Rebuilding the documents does not resolve this issue.
All share and NTFS permissions are accurate and allow
users to save to those directories. Changing share or NTFS
permissions occasionally resolves the issue but not every
time, and the issue reoccurs.
Disk space is >20G on each share - plenty of space.
Disk Quotas are not being used.
Servers are Windows 2000 Server.
Latest Microsoft patches deployed by local SUS server.
Latest Office patches downloaded and deployed from Office
Update for all versions on each machine.
Active Directory domain deployment.
Affects more than one server/user.
Affects only a fraction of our users (<1%)
Began very recently (End of September 2003)
Microsoft KB articles do not apply to the situation.
Norton AV 2003 deployed on the workstations.
Norton SB 8.1 deployed on the servers.
Disabling the AV on both the workstation and the server
does not resolve this issue.
Norton has not had significant reports of this issue.
Microsoft has not had significant reports of this issue.
Issue only happens with Word and Excel, Powerpoint and
Access do not share this issue (yet).
Using standard normal.dot template local to each users
machine.
No macros are running in Excel documents.
No embedded images or links are present in Word documents
in question.
Can happen to any Excel or Word document, is not specific
to any particular document.
"Fast Saves" not enabled.
Can happen with new documents or old (one potential is
documents can only be saved X amount of times before this
issue surfaces, but this does not seem to apply under the
circumstances).
Servers are not overloaded with processes and processor
time is <50%, SCSI RAID without write cache enabled. No
significant errors are produced on the sever event logs.
Can happen to a document on a Linux SMB share as well, is
not specific to the server, seems more specific to the
client.
I've been researching this issue for almost a month now,
and I've seen many different ideas and concepts as to what
may or may not be happening. I've tried every possible
resolution I've come across without any success. This
issue is intermittent but can be reproduced given enough
time working in the same document. Given all the possible
combinations of potential errors and solutions I've seen
for this issue, mostly related to Office 2000, I've
updated to Office XP and then Office 2003 and the errors
continue to surface. This issue began in late September
which leads me to believe it is something Microsoft has
done in a security update that causes an intermittent
problem to occur under very specific circumstances which I
cannot seem to ascertain, understand or replicate. There
seems to be no rhyme or reason to this issue and I've
tested each step using a new document along the way to try
to isolate the potential fix. Doesn't seem to be one. As
stated in articles on several support sites, at the
present time the answer seems to be "there is no answer",
which is unacceptable.
Any input, ideas, suggestions, et al would be greatly
appreciated. Microsoft need to look after this issue and
try to resolve whatever may be causing this. Again, this
began in late September and is likely the result of some
update that has been released. Most likely this issue has
not reached critical mass and is therefor being passed
over by supplying users with KB articles which do not seem
to apply.
Sincerely,
Denard Springle
Senior Network Admin
MCSE, RHCE, CCIP
Edge Technologies, Inc.
producing "Disk is Full" errors followed by "Document
could not be saved". Excel in particular sometimes
presents "Document is locked" errors. I've researched this
issue in the KB and on Technet and have found several
articles with several suggestions. None of the found
articles seems to apply. Since I have tried all of the
known resolutions and checked every Microsoft KB article
relating to these issues I'm asking the question here.
Several of my users have experienced this problem, but not
all. Problem is very intermittent, though seems to be more
frequent with Office 2003 than Office XP or Office 2000.
Here is the basic scenario and what I have discovered:
Problem can exist on Windows 2000 or Windows XP.
Files are located on network shares.
Files can be saved to local drive or different network
share on the same server with the troubled network share
without incident.
Affects one share at one time, and not another (i.e. users
home directory but not a public share at one time, then
the public share but not the users home directory at
another time).
Saving as .rtf does not resolve this issue.
Saving as different file name does not resolve issue.
Rebuilding the documents does not resolve this issue.
All share and NTFS permissions are accurate and allow
users to save to those directories. Changing share or NTFS
permissions occasionally resolves the issue but not every
time, and the issue reoccurs.
Disk space is >20G on each share - plenty of space.
Disk Quotas are not being used.
Servers are Windows 2000 Server.
Latest Microsoft patches deployed by local SUS server.
Latest Office patches downloaded and deployed from Office
Update for all versions on each machine.
Active Directory domain deployment.
Affects more than one server/user.
Affects only a fraction of our users (<1%)
Began very recently (End of September 2003)
Microsoft KB articles do not apply to the situation.
Norton AV 2003 deployed on the workstations.
Norton SB 8.1 deployed on the servers.
Disabling the AV on both the workstation and the server
does not resolve this issue.
Norton has not had significant reports of this issue.
Microsoft has not had significant reports of this issue.
Issue only happens with Word and Excel, Powerpoint and
Access do not share this issue (yet).
Using standard normal.dot template local to each users
machine.
No macros are running in Excel documents.
No embedded images or links are present in Word documents
in question.
Can happen to any Excel or Word document, is not specific
to any particular document.
"Fast Saves" not enabled.
Can happen with new documents or old (one potential is
documents can only be saved X amount of times before this
issue surfaces, but this does not seem to apply under the
circumstances).
Servers are not overloaded with processes and processor
time is <50%, SCSI RAID without write cache enabled. No
significant errors are produced on the sever event logs.
Can happen to a document on a Linux SMB share as well, is
not specific to the server, seems more specific to the
client.
I've been researching this issue for almost a month now,
and I've seen many different ideas and concepts as to what
may or may not be happening. I've tried every possible
resolution I've come across without any success. This
issue is intermittent but can be reproduced given enough
time working in the same document. Given all the possible
combinations of potential errors and solutions I've seen
for this issue, mostly related to Office 2000, I've
updated to Office XP and then Office 2003 and the errors
continue to surface. This issue began in late September
which leads me to believe it is something Microsoft has
done in a security update that causes an intermittent
problem to occur under very specific circumstances which I
cannot seem to ascertain, understand or replicate. There
seems to be no rhyme or reason to this issue and I've
tested each step using a new document along the way to try
to isolate the potential fix. Doesn't seem to be one. As
stated in articles on several support sites, at the
present time the answer seems to be "there is no answer",
which is unacceptable.
Any input, ideas, suggestions, et al would be greatly
appreciated. Microsoft need to look after this issue and
try to resolve whatever may be causing this. Again, this
began in late September and is likely the result of some
update that has been released. Most likely this issue has
not reached critical mass and is therefor being passed
over by supplying users with KB articles which do not seem
to apply.
Sincerely,
Denard Springle
Senior Network Admin
MCSE, RHCE, CCIP
Edge Technologies, Inc.