asked on

Can't access word and excel files

I've checked Technet for this error and the fixes are already applied but we still get this message:
"Word failed reading from this file (AutoRecovery save of file_name.asd).
Please restore the network connection or replace the floppy disk and retry."

Almost everyday at least one user experiences this problem of trying to access a word or excel file off of our main server and it runs rampant. It's not a permissions problem I'm positive. They are running win98 and winNT workstation. Rebooting the server won't work.

fatherted

If your running office off a server (rather than a local copy on each machine) check that the install on the server isnt corrupted in anyway, check maybe that ordinary users dont have the wrong permissions, maybe someone accidently corrupted something on the network install.

ntguru

ASKER

Office 97 is not installed on the server. Just being used to store the data.

ntguru

ASKER

Office 97 is not installed on the server. Just being used to store the data.

fatherted

Also.. on the machines check the location for autorecovery in the option (say in word for example) under tools, then options, then file locations, you will see it there, maybe it's set to a drive letter that isnt always mapped (the odd time logon scripts dont run) like a home dir on network server or something like that, ive seen that before. change it to the UNC path \\servername\users\$USERNAME$ or something like that (trip me up if i got that wrong) which means as long as they are logged on and ther server is up they can access it regardless of drive letter mappings. Mapped drive letters always seem to cause havoc!!!

Tim Holman

I've seen this happen before with a dodgy card in a hub.
Can you get your network checked out ?

ASKER CERTIFIED SOLUTION

amikkelsen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ntguru

ASKER

It actually was not the gentleman amikkelsen comments that fixed it. It was the antivirus that was the culprit. Thanks for the help....