Microsoft KB Archive/114799

{|
 * width="100%"|

WD6X: "Cannot Open File" During Conversion on Novell Network

 * }

Q114799

-

The information in this article applies to:


 * Microsoft Word for Windows, versions 6.0, 6.0a, 6.0c

-

SYMPTOMS
When you run a workstation installation of Word on a Novell network, you may receive the following error message when you try to save a Word document as any format for which Word uses an external converter (other than Text With Layout):

"Cannot open file"

This error occurs if your MS-DOS TEMP variable is set to either the true root directory of a Novell server volume or to a mapped root, regardless of where you choose to save the file.

If you instead try to open a file from any other format for which Word uses an external converter, you may receive the following error message

"Cannot open file"

followed by:

"Word cannot open the document. ... "

In either case, conversion is unsuccessful.

CAUSE
If a TEMP variable which points to the Novell root directory exists in either your local workstation Autoexec.bat file, or in your Novell login script, this problem may occur.

WORKAROUND
To avoid this problem, quit Word and quit Windows and reset your MS-DOS TEMP variable to point to any other location than the root directory on the Novell server volume. Having done so, Word can now open from or save to all supported foreign file formats without issue. You can make this change permanently to your Autoexec.bat file to avoid having to make the change during future Word sessions.

STATUS
Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION
File formats affected in Word 6.0 and 6.0a include: Word for Windows 1.0, Word for Windows 2.0, Word for MS-DOS, Word for Macintosh, Works for MS-DOS, Works for Windows, Windows Write, Publisher 2.0, MultiMate, Multiplan, RFT-DCA, DisplayWrite, WordPerfect, WordStar, Excel BIFF, and Lotus 1-2-3.

This problem has also been reported to occur when running Word 2.x on an equivalent network configuration and using the Word 6.0 for Windows converter to read a Word 6.0 for Windows file. The problem reportedly does not occur when opening or saving any other foreign format in Word 2.x.

Additional query words: conversion converted converts transfer transfers translation translate problem maproot mapped netware

Additional query words:

Keywords : kb3rdparty kberrmsg kbinterop kbnetwork winword

Issue type : kbbug

Technology : kbWordSearch kbWordWSearch