Article ID: 2617010 - View products that this article applies to.
By default, Microsoft Outlook 2010 and Outlook 2013 write the name of each connected add-in to the Windows Application Log in the Event Viewer when the add-in gets loaded by Outlook. The application event log entry includes a Boot Time value for each add-in, indicating the amount of time it took for the add-in to be loaded. This makes it easy to find out exactly what add-ins are loaded by Outlook, and how long they took to load. This can help you identify add-ins that may be causing long startup times for Outlook.
Please see the following article for details on how to manage add-ins in Outlook 2010.
Please see the More Information section of this article for details on these application event log entries.
When you start Outlook 2010 or Outlook 2013, an application event log entry (Event ID 45) is written with all of the add-ins that are being loaded in the session. The following is an example event in the Application event log, listing some of the add-ins loaded during Outlook startup and the relevant information about each add-in.
Any add-ins that are loaded after Outlook has already started also get an event added to the log. So, if you start Outlook, do some work in it, and then click a feature that starts its own add-in, your application event log would have one entry with all of the add-ins that loaded when you started Outlook, and another entry with the add-in that loaded after you clicked its associated feature.
The following example event log entry shows the loading of the Microsoft VBA for Outlook add-in that loaded only after starting the Visual Basic Editor. This event log entry occurred about two minutes after the start of Outlook (compare the Date and Time in the preceding event log entry for Outlook startup).
The Outlook 2010 and Outlook 2013 Group Policy templates includes a policy setting to control the generation of the application event log entries for add-in startup. Expand the Miscellaneous node in the policy tree to locate the Disable Windows event logging for Outlook add-ins policy setting. When you use this policy, the following registry data is applied to Outlook clients to control this feature.
Note 1: x.0 in the above path represents the version of Outlook (15.0 = Outlook 2013, 14.0 = Outlook 2010)
Note 2: The DisableAddinLogging registry value only functions under the above path (\policies). If you push out this setting (for example, using a logon script) and the DisableAddinLogging value is not under the \Policies hive, Outlook will continue to log add-in loading information in the application event log.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Contact us for more help
Connect with Answer Desk for expert help.