J
James Gregory
Guest
We installed these two updates in addition to .NET 2.0 SP1 on Sunday 2/3/08.
These were installed on two seperate, but identical Win2k SP4 servers on two
different subnets. On Monday 2/4 a user called complaining of an issue with
an Excel file they were editing on a server share. It basically stated that
the file was was in use, etc. but they had the option to save the file to a
different name.
An inspection of the problem file revealed that the only property that was
accessable was the general tab. The Security and Summary tabs were not
displayed, consequently even admin could not move or delete the file. This
occured each day with other files. A chkdsk was finally run on Thursday,
which restored the missing properties. A consistency check was also run on
the RAID array, which did not report any errors. We are seeing this occur
on the other
server but not at the same rate. Has anyone else seen this type of issue
with these updates installed? Possibly related, we are also seeing some
TMP files (versions of the office files) starting to accumulate in some of
the shared directories. All of the problems seen so far seem to be related
to Office 2003 (SP3) files.
These were installed on two seperate, but identical Win2k SP4 servers on two
different subnets. On Monday 2/4 a user called complaining of an issue with
an Excel file they were editing on a server share. It basically stated that
the file was was in use, etc. but they had the option to save the file to a
different name.
An inspection of the problem file revealed that the only property that was
accessable was the general tab. The Security and Summary tabs were not
displayed, consequently even admin could not move or delete the file. This
occured each day with other files. A chkdsk was finally run on Thursday,
which restored the missing properties. A consistency check was also run on
the RAID array, which did not report any errors. We are seeing this occur
on the other
server but not at the same rate. Has anyone else seen this type of issue
with these updates installed? Possibly related, we are also seeing some
TMP files (versions of the office files) starting to accumulate in some of
the shared directories. All of the problems seen so far seem to be related
to Office 2003 (SP3) files.