Le Café Central de

                 ... Deva blogs!!

  • Le Café Central de DeVa

    Troubleshooting Outlook : Command line switches for Outlook 2010


    Outlook 2010 provides the command line switches for our handy troubleshooting.


    You can use some of these switches that are recommended for solving problems.

    If you do hit an unexpected issue and want to run one of these switches. During these times, these switches can also been used when you need to restore Outlook settings to the default settings. 

    Let we try to use the switches in Windows 7 and Outlook 2010:

    a) You can use either one of the 3 options:

    1) Open the Run command via Start-> Run

    2) Press the Windows Logo + R on your keyboard

    3) Open the Start Menu and use the Search field to type in for the next step. (see the pic)

    b) In the box you opened in option 1/2/3 and just type: outlook.exe

    c) Press the spacebar once, and then type a forward slash mark (/) followed by the switch you want to use (see the list given below).

    d) Let we take example using the command line CleanReminders switch. 
    The command you type in the Open box should look like this:

    outlook.exe /cleanreminders

    e) To run the command, click OK.

    List of command line switches for Outlook 2010:

    Switch Description


    Creates an item with the specified file as an attachment.

    Example: "C:\Program Files\Microsoft Office\Office11\Outlook.exe" /a "C:\My Documents\labels.doc"
    Note: If no item type is specified, IPM.Note is assumed. Cannot be used with message classes that aren't based on Outlook.

    /altvba otmfilename

    Opens the VBA program specified in otmfilename, rather than %appdata%\Microsoft\Outlook\VbaProject.OTM.

    /c messageclass

    Creates a new item of the specified message class (Outlook forms or any other valid MAPI form). Some of the related examples:

    • /c ipm.activity creates a Journal entry
    • /c ipm.appointment creates an appointment
    • /c ipm.contact creates a contact
    • /c ipm.note creates an e-mail message
    • /c ipm.stickynote creates a note
    • /c ipm.task creates a task


    Prompts for the default manager of e-mail, news, and contacts.


    Starts Outlook and deletes client-based rules.


    Deletes the logging records saved when a manager or a delegate declines a meeting.


    Removes Search Folders from the Microsoft Exchange server store.


    Clears and regenerates free/busy information. This switch can only be used when you are able to connect to your Microsoft Exchange server.


    Removes invalid profile keys and recreates default registry keys where applicable.


    Launches Outlook with a clean Personal Folders file (.pst).


    Clears and regenerates reminders.


    Starts Outlook and deletes client- and server-based rules.


    Deletes all Schedule+ data (free/busy, permissions, and .cal file) from the server and enables the free/busy information from the Outlook Calendar to be used and viewed by all Schedule+ 1.0 users.


    Starts Outlook and deletes server-based rules.


    Deletes duplicate reminder messages.


    Deletes the subscription messages and properties for subscription features.


    Restores default views. All custom views you created are lost.


    Starts Outlook without figuring out if Outlook should be the default client in the first run.


    Opens the specified message file (.msg) as an OLE embedding. Also used without command-line parameters for standard OLE co-create.

    /f msgfilename

    Opens the specified message file (.msg) or Microsoft Office saved search (.oss).


    Starts Outlook as if it were run for the first time.

    /hol holfilename

    Opens the specified .hol file.

    /ical icsfilename

    Opens the specified .ics file.

    /importprf prffilename

    Launches Outlook and opens/imports the defined MAPI profile (*.prf). If Outlook is already open, queues the profile to be imported on the next clean launch.

    /l olkfilename

    Opens the specified .olk file.

    /launchtraininghelp assetid

    Opens a Help window with the Help topic specified in assetid.

    /m emailname

    Provides a way for the user to add an e-mail name to the item. Only works in conjunction with the /c command-line parameter.

    Example: Outlook.exe /c ipm.note /m emailname


    Starts Outlook without loading outcmd.dat (customized toolbars) and *.fav file.


    Starts Outlook with extensions turned off, but listed in the Add-In Manager.


    Starts Outlook without checking mail at startup.


    Starts Outlook with the Reading Pane off.

    /p msgfilename

    Prints the specified message (.msg). Does not work with HTML.

    /profile profilename

    Loads the specified profile. If your profile name contains a space, enclose the profile name in quotation marks (").


    Opens the Choose Profile dialog box regardless of the Options setting on the Tools menu.


    Starts Outlook using an existing Outlook window, if one exists. Used in combination with /explorer or /folder.


    Resets default folder names (such as Inbox or Sent Items) to default names in the current Office user interface language.

    Note: If you first connect to your mailbox Outlook using a Russian user interface, the Russian default folder names cannot be renamed. To change the default folder names to another language such as Japanese or English, you can use this switch to reset the default folder names after changing the user interface language or installing a different language version of Outlook.


    Restores missing folders for the default delivery location.


    Clears and regenerates the Navigation Pane for the current profile.


    Opens Outlook and displays the remote procedure call (RPC) connection status dialog.

    /s filename

    Loads the specified shortcuts file (.fav).


    Starts Outlook without extensions, Reading Pane, or toolbar customization.


    Starts Outlook with the Reading Pane off.


    Starts Outlook without checking mail at startup.


    Starts Outlook with extensions turned off, but listed in the Add-In Manager.


    Starts Outlook without loading Outcmd.dat (customized toolbars) and *.fav file.

    /select foldername

    Starts Outlook and opens the specified folder in a new window.
    For example, to open Outlook and display the default calendar use: "c:\Program Files\Microsoft Office\Office11\Outlook.exe" /select outlook:calendar


    Starts Outlook and forces a detection of new meeting requests in the Inbox, and then adds them to the calendar.

    /t oftfilename

    Opens the specified .oft file.

    /v vcffilename

    Opens the specified .vcf file.

    /vcal vcsfilename

    Opens the specified .vcs file.

    /x xnkfilename

    Opens the specified .xnk file.

    Happy troubleshooting with Outlook 2010!!
  • Le Café Central de DeVa

    Outlook: How to compact my PST/OST file in Outlook 2010?


    I listed some of the regular questions that we see from our customers from PST/OST are,

    1) How to reclaim the space from PST?
    2) How to compact my PST file?
    3) How to compact PST/OST files to eliminate deleted item space in Outlook?
    4) My PST is filling my hard disk?

    To conserve space on your hard disk, you can delete unwanted items from the various .pst/.ost files, and then compact the files to make them smaller. If you use Outlook 2002, 2003, 2007 and 2010 then try the following steps specified in the support KB.

    Try this out and reclaim more room in your PC!!

  • Le Café Central de DeVa

    Monitoring Event Sink # 32 - Best Practices: Performance related issues with Event sinks


    I would like to share certain best practices - in order to improve the performance or overcome performance related issues associated with event sink and Programming guidelines for event sinks before you develop for your reference.

    • Exchange store events do not by themselves generate Windows Event Log entries. The underlying ExOLEDB provider generates performance counters for each event sink. The code that executes in response to an Exchange store event code can also generate Windows Event Log events and information for Windows Performance Counters.
    • Exchange store events that can be misused, or that can cause problems if installed incorrectly, should implement the ICreateRegistration interface, and programmatically prevent the event sink from being improperly registered. Cross-store access from within an event sink is not possible. Once registered and wrapped as COM+ applications, any user who knows the name of the event sink can register it in a folder to which they have write permissions.
    • If you have to register an event sink for all mailboxes in a store, you should register the event sink for store-wide events.
    • When Exchange starts up, it looks for and loads all registered event sinks, which takes some time.
    • Using many individual event sink registrations instead of a single store-wide event registration item significantly increases server startup time.
    • Always use care when running store event sinks, especially when using synchronous event sinks.
    • A synchronous event sink is triggered after a data request to the Exchange store but before the item is committed to the store.
    • The synchronous event sink has exclusive control over the item while it is processing. Therefore, a complex or poorly written sink can lock a resource for some time, or even bring an Exchange server to its knees.
    • But, I would recommend you to go through the Programming guidelines for event sinks before you develop:

      • For optimal performance, create an in-process Component Object Model (COM) class that supports execution in a multi-threaded apartment (MTA). The event dispatcher threads execute from within the Microsoft Internet Information Services (IIS) MTA. If your sink supports the single-threaded apartment (STA) only, then all interfaces will be marshaled across the MTA apartment and STA apartment boundaries.
      • Provide an implementation of the IEventIsCacheable interface by your sink. If you implement the IEventIsCacheable interface and the IsCacheable method returns S_OK, the event dispatcher will cache the sink and will use the same object for subsequent events; otherwise, each event will create a new instance of the sink.
      • Never install an untested sink on a production server, especially a sink that runs in- process. Exceptions thrown from within these in-process sinks may disable the IIS (inetinfo.exe) process or cause it to stop responding.
      • Do not place Microsoft Collaboration Data Objects (CDO) interface definitions in your sink’s interface definition language (IDL) file (if you use one directly) when working in C or C++. Information about CDO types—including all classes, interfaces, enumerations, and modules—can be found in the supplied headers. If you do place IDL information in your IDL file, and any of these types are referenced from within your library statement, you will re-map various Interface IDs (IIDs) from the CDO dynamically link library (DLL) to your DLL. This will not cause immediate harm because your DLL contains the necessary type library information required for the universal marshaller to function properly; however, if you subsequently remove the sink from the registry, the CDO libraries will function improperly.

    Happy programming !!

  • Le Café Central de DeVa

    Monitoring Event Sink # 31: Why Exchange Explorer doesn’t work ?


    One of my customer reported that in one of his machine, the exchange explorer (available part of Exchange SDK) stop responding. But the same work in his rest of the machines. During the research, we found the following known issues (stop responding, doesn’t display etc) with exchange explorer:

    Cannot set member server schema scope using Exchange Explorer

    On a computer where Microsoft Internet Explorer 6 is installed, the schema scope for a non-MAPI folder can only be set on the first server connected to the domain. The schema scope for non-MAPI folders cannot be changed for other servers that are members of that domain. Attempting to edit the schema-collection-ref or base schema fields can cause the Exchange Explorer to stop responding.

    Exchange Explorer may stop responding when viewing a folder on a different server

    When using the Exchange Explorer on a computer with Internet Explorer 6 installed, selecting a folder that is located on a different server in the domain may cause the Exchange Explorer to stop responding.

    Exchange Explorer obtains the code page from the machine configuration

    When using the Exchange Explorer on a computer running the US-English version of Microsoft Windows® server operating systems, the Exchange Explorer displays information using the code page setting of the machine. If the user has chosen a different locale for display, for example Japanese (JPN), the Exchange Explorer may incorrectly display characters from the user-specified locale as "??".

    Exchange Explorer does not display all property namespaces

    Exchange Explorer does not display schema properties in the http://schemas.microsoft.com/mapi/ Namespace.

    Hope this helps.

  • Le Café Central de DeVa

    Troubleshooting: Why Windows Mobile is connecting to my PC?

    There are several things that may prevent your device from connecting: If Windows Live OneCare is installed on your computer, it may be blocking device connectivity. For the steps to configure Windows Live OneCare to allow the device to connect, visit...
Page 1 of 1 (5 items)