B
Brian Holderread
Any help with the following problems would be appreciated:
#1. Windows 98 SE computers with Excel 97 can not save to network
share. When saving, the progress bar gets to close to 100% and then
Excel hangs. If you do not end task Excel, a temp file will continue
to build in size. (20k spreadsheet's temp file grows by about 800k
every second) It is an Excel problem and not a permissions problem on
the server. The user has full permissions to the folder. The problem
occurs when logged on as administrator also. It is not an issue of
file name length because the problem occurs even with a test file
named "test.xls" is being copied to the root folder of the share. The
computer was re-installed from scratch to make sure it wasn't an issue
of file corruption. After installing Windows 98 SE and Office 97, the
problem still existed. Windows Update has been run on this computer
as of 10/10/03 and all critical patches were applied. Also, Office
SR2-b and dsclient have been applied. The problem still exists. I
can copy the file from a local drive to the same network share without
problems. The problem only occurs when trying to save to the share
through an office app.
#2. Windows 98 SE computers with Office XP have trouble saving to
network shares. It appears as if the connection to the network drives
times out. I get "Document not saved" (in Excel) or a message about
the disk being full (in Word). The user has full permissions to that
shared folder and there is plenty of drive space. If I browse to the
share via explorer or the command line, Word and Excel can save for a
while before the error occurs again. While troubleshooting the
problem, I changed the default time out for network connections on the
server from 15 minutes to 240 minutes on the server. It made no
difference and the error continues to occur. I have gotten around the
problem by creating a batch file that does a dir on each network share
that the user has access to. This seems to be enough to refresh the
connection and gets Excel and Word saving again (temporarily). I was
hoping that someone know of a real solution that would not require the
batch file. As with the problem noted above, a computer has been
re-installed from scratch to rule out file corruption on the client as
the cause of the problem. The computer is up to date with patches via
windows update that ran on 10/10/03 and has the dsclient installed.
It was tested multiple times during the re-install to insure that it
wasn't a Windows or office service pack or the dsclient causing the
problem.
#1. Windows 98 SE computers with Excel 97 can not save to network
share. When saving, the progress bar gets to close to 100% and then
Excel hangs. If you do not end task Excel, a temp file will continue
to build in size. (20k spreadsheet's temp file grows by about 800k
every second) It is an Excel problem and not a permissions problem on
the server. The user has full permissions to the folder. The problem
occurs when logged on as administrator also. It is not an issue of
file name length because the problem occurs even with a test file
named "test.xls" is being copied to the root folder of the share. The
computer was re-installed from scratch to make sure it wasn't an issue
of file corruption. After installing Windows 98 SE and Office 97, the
problem still existed. Windows Update has been run on this computer
as of 10/10/03 and all critical patches were applied. Also, Office
SR2-b and dsclient have been applied. The problem still exists. I
can copy the file from a local drive to the same network share without
problems. The problem only occurs when trying to save to the share
through an office app.
#2. Windows 98 SE computers with Office XP have trouble saving to
network shares. It appears as if the connection to the network drives
times out. I get "Document not saved" (in Excel) or a message about
the disk being full (in Word). The user has full permissions to that
shared folder and there is plenty of drive space. If I browse to the
share via explorer or the command line, Word and Excel can save for a
while before the error occurs again. While troubleshooting the
problem, I changed the default time out for network connections on the
server from 15 minutes to 240 minutes on the server. It made no
difference and the error continues to occur. I have gotten around the
problem by creating a batch file that does a dir on each network share
that the user has access to. This seems to be enough to refresh the
connection and gets Excel and Word saving again (temporarily). I was
hoping that someone know of a real solution that would not require the
batch file. As with the problem noted above, a computer has been
re-installed from scratch to rule out file corruption on the client as
the cause of the problem. The computer is up to date with patches via
windows update that ran on 10/10/03 and has the dsclient installed.
It was tested multiple times during the re-install to insure that it
wasn't a Windows or office service pack or the dsclient causing the
problem.