Loading

How to Collect Windows Event Viewer Logs to Troubleshoot Salesforce for Outlook (SFO) Issues

Fecha de publicación: May 1, 2026
Descripción

Windows Event Viewer for Salesforce for Outlook (SFO) Troubleshooting

Windows Event Viewer allows you to monitor events on your system and maintain logs about program, security, and system events on your computer. When Salesforce for Outlook (SFO) crashes or behaves unexpectedly, Event Viewer helps gather information about application crashes, malfunctions, errors, and other software problems. The Event Log service starts automatically when Windows starts, and all users can view application and system logs.
Important: If you are unable to start Event Viewer, make sure the service is running in Services.msc. If the Application or System log is empty, the Error Reporting and/or Event Log services are either disabled or not running. A user with local admin permission must run Services.msc from the Run command (Windows key + R), find these services one at a time, double-click each one, change the Startup type to Manual or Automatic, and click the Start button. You should see Service Status: Running below the startup type drop-down box.

Types of Windows Logs Useful for SFO Troubleshooting

Application (program) events: Events are classified as error, warning, or information depending on the severity of the event. An error is a significant problem such as loss of data. A warning is an event that is not necessarily significant but might indicate a possible future problem. An information event describes the successful operation of a program, driver, or service.
System events: System events are logged by Windows and Windows system services, and are classified as error, warning, or information.

Solución

Why Collect Event Viewer Logs

When Salesforce for Outlook (SFO) crashes or behaves unexpectedly, Windows Event Viewer logs help identify errors related to SFO (SFDCMsOl.exe — the Salesforce for Outlook application process), Microsoft Outlook, or the .NET Framework. Collecting these logs is a key diagnostic step before escalating an issue to Salesforce Support or your IT department.

Step 1: Start Windows Event Viewer

  1. Press Windows key + R to open a Run window.
  2. Type eventvwr and press Enter.

Step 2: Clear the Log, Reproduce the Issue, Then Capture

Because everything is logged continuously, there are too many events to review at once. The best approach is to clear the log first, then reproduce the issue or crash, and then capture the logs.

  1. Start Event Viewer.
  2. In the console tree, navigate to the event log you want to clear.
  3. On the Action menu, click Clear Log.
  4. Choose one of the following:
    1. To clear without saving: Click Clear.
    2. To save before clearing: Click Save and Clear, type a file name in the Save As dialog, and click Save.

Step 3: Identify and Save Relevant Error Events

  1. Expand Windows Logs and click on the Application log.
  2. Search for errors related to MS Outlook, Salesforce for Outlook (SFDCMsOl.exe), or .NET Framework that occurred at the time of the crash. These errors appear with a red exclamation mark under the Level column.
  3. Hold the CTRL key and click each relevant error to select them.
  4. Confirm the selected events are highlighted, then click Save Selected Events on the right-hand side.
  5. In the Save As pop-up window, type a file name and save it to your Desktop.
  6. Repeat the same steps for the System logs.

Step 4: Review the Errors

The errors in Event Viewer may directly explain why SFO or Outlook crashes and may be something your IT department can resolve. If there are no errors related to Outlook, .NET, or SFO (SFDCMsOl.exe) in the Event Viewer logs, proceed with additional troubleshooting steps as directed by Salesforce Support.

Número del artículo de conocimiento

000382483

 
Cargando
Salesforce Help | Article