Article ID: 840640 - Last Review: April 7, 2006 - Revision: 2.2 "'filename.xls' cannot be accessed" error message when you open a workbook in Excel 2002 during a remote desktop sessionImportant This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows Registry On This PageSYMPTOMSWhen you run a remote desktop session, if you try to open a
workbook in Microsoft Excel 2002 from a local source (such as your hard disk
drive), you receive the following error message: 'filename.xls' cannot be accessed. The
file may be read-only, or you may be trying to access a read-only location. Or,
the server the document is stored on may not be responding. CAUSEThis issue may occur if the file is already open on your
client computer. WORKAROUNDTo work around this issue, close the Excel 2002 file on your
client computer before you open the file in the remote desktop
session. RESOLUTIONHow to obtain the hotfixThis issue is fixed in the Excel 2002 Hotfix Package that is dated May 6, 2004. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:829348
(http://support.microsoft.com/kb/829348/
)
Excel 2002 post-Service Pack 3 hotfix package: May 6, 2004 After you install this hotfix, follow the steps that are listed in the "More Information" section of this article to set the QFE_Yakima registry key and to activate the hotfix. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONWarning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own
risk. To activate this hotfix, follow these steps:
| Article Translations
|
Back to the top
