D
David Prentice
We've been encountering a problem where users are unable to open Word
documents, either on the network or locally. When they try to do so, they
get this error message:
"The document name or path is not valid. Try these suggestions.
* Check the file permissions for the document or drive.
* Use the file open dialog box to locate the document."
This error message is detailed in knowledgebase article 224016,
http://support.microsoft.com/default.aspx?scid=kb;en-us;224016, but none of
the suggested causes or workarounds appears to be relevant. The problem only
affects Word (this includes not being able to open e-mail attachments), not
any other applications like Excel, and you can open the Word documents in
WordPad without any problems. Users initially notice when trying to open a
document on the file server, you can get round the problem either by
disconnecting and re-mapping the file share, or by opening the file using a
UNC path.
We're running a Windows 2000 network, with 2000 and XP Pro workstations (up
to date with service packs and patches) and are using Word 2000, also up to
date with patches. The problem is hard to pin down as it only affects a few
users and is fairly random, we've tried obvious solutions like replacing the
normal.dot templates for affected users, but this doesn't work, so I'd be
grateful for any suggestions.
documents, either on the network or locally. When they try to do so, they
get this error message:
"The document name or path is not valid. Try these suggestions.
* Check the file permissions for the document or drive.
* Use the file open dialog box to locate the document."
This error message is detailed in knowledgebase article 224016,
http://support.microsoft.com/default.aspx?scid=kb;en-us;224016, but none of
the suggested causes or workarounds appears to be relevant. The problem only
affects Word (this includes not being able to open e-mail attachments), not
any other applications like Excel, and you can open the Word documents in
WordPad without any problems. Users initially notice when trying to open a
document on the file server, you can get round the problem either by
disconnecting and re-mapping the file share, or by opening the file using a
UNC path.
We're running a Windows 2000 network, with 2000 and XP Pro workstations (up
to date with service packs and patches) and are using Word 2000, also up to
date with patches. The problem is hard to pin down as it only affects a few
users and is fairly random, we've tried obvious solutions like replacing the
normal.dot templates for affected users, but this doesn't work, so I'd be
grateful for any suggestions.