Microsoft Knowledge Base Email Alertz

(826488) - When you start Outlook 2003 by using a Terminal Services Client such as Remote Desktop Connection (RDC), also known as the MSTSC.exe file, you may receive the following error message: The file Path \Local Settings\Application...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You receive an error message when you use a Terminal Services Client to start Outlook 2003

Article ID: 826488 - View products that this article applies to.

SYMPTOMS

When you start Outlook 2003 by using a Terminal Services Client such as Remote Desktop Connection (RDC), also known as the MSTSC.exe file, you may receive the following error message:
The file Path\Local Settings\Application Data\Microsoft\Outlook\outlook.ost is in use and could not be accessed. Close any application that is using this file, and then try again.
If you click Cancel, the error message reappears. If you click Cancel three times, Outlook 2003 switches to online mode and starts.

CAUSE

This problem may occur if the following conditions are true:
  • You install Outlook 2003 (or Microsoft Office 2003) on a Windows Server 2003-based computer.
  • You turn off Cached Exchange Mode.
  • You leave Outlook 2003 running on the Windows Server 2003-based computer, and then connect to the server-based computer from a remote workstation by using RDC.
  • You start Outlook 2003 from the remote workstation remote session.
The error message occurs because the Outlook 2003 session that is left running on the Windows Server 2003-based computer locks the offline folder (.OST) file, and the second instance of Outlook 2003 that you started from a remote workstation by using RDC cannot open the .OST file.

WORKAROUND

To work around this problem, use one of the following methods:
  • Quit Outlook 2003 on the Windows Server 2003-based computer before you try to start Outlook 2003 by using RDC.

    -or-
  • If you prefer to leave Outlook 2003 running on the Windows Server 2003-based computer, you can connect to the console session of the server to remotely access the Outlook 2003 session. To do this, type the following on the remote workstation computer:
    mstsc /console
    Type your credentials as required, and then click Connect. When you do this, RDC opens the existing console session with Outlook 2003 running instead of opening a second session. You can then continue to use Outlook 2003.

    Note RDC is included with Microsoft Windows XP. RDC provides new terminal features when you are working with other RDP 5.1 computers (such as Microsoft Windows 2000 Server, Windows XP, and Microsoft Windows .NET Server). To install RDC on a Microsoft Windows 98, Microsoft Windows Millennium Edition (Me), or Microsoft Windows 2000-based computer, double-click the MSRDPCLI.exe file on the Windows XP CD, in the \SUPPORT\TOOLS folder. This file contains the setup for the Terminal Client Software (RDC or the MSTSC.exe file).

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Properties

Article ID: 826488 - Last Review: November 27, 2007 - Revision: 1.11
APPLIES TO
  • Microsoft Office Outlook 2003
Keywords: 
kbproductlink kbstartprogram kberrmsg kbprb kbnofix KB826488
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Anonymous User Report As Irrelevant  
Written: 10/22/2004 5:31 PM
If youre connected via a router/cable modem setup, resetting both may also correct this issue